Samples can currently only be played starting from the beginning. This is problematic for samples with a few milliseconds of silence at the beginning, or samples where only a portion is of interest. It would be helpful to be able to select a starting position.
again, use the force luke!
samplv1 has no audio sample editor whatsoever and it will never have one. sorry.
edit and make it stand as your audio sample file before-hand--audacity is a popular choice, why not use something that is dang proven as ugly perfect? ;)
cheers
Last edit: Rui Nuno Capela 2018-01-04
we do not ask for an audio sample editor.
We are asking for a locater that represents the start of the sample playback on that location.
i have attached a screenshot of the sampler (Grace) that we are working with now. It has 4 locators: the blue ones are for the loop, the green one is the Playback start locator. This is the one i am talking about. This start locator makes it easy to, on-the-fly, find a start of our liking without going several times back to Audacity before finding the right playback start spot, but stay within Samplv1.
We prefer working with Linux programs instead of the Linux/Wine combination which are more CPU intensitive. Even much more because now Samplv1 supports microtonal scales and Grace does not...
Last edit: Menno 2018-03-23
noted.
Now that Samplv1 has the 2 looping methods in place, we like to address the issue of the start locator again.
It is non-intuitive to go to Audacity, cut the sample, go back to Samplv1, load that sample and find out that after all that sample start is not what we are looking for, so going back to Audacity, cut, load, not good, back to Audacity etc. etc...
Having a start locator should not be too difficult on the level of math. In pseudo-code:
start sample = start sample + locator_start_sample
things are getting better (hopefiully)... just check 0.9.1.21git.[667a81] and beyhond... ;)
Related
Commit: [667a81]
they certainly do :) already built and testing...
On Thu, Jul 19, 2018 at 5:54 PM, Rui Nuno Capela rncbc@users.sourceforge.net wrote:
Related
Commit: [667a81]
Tickets:
#8great stuff
But some feedback:
it may be on my system only (Linux Mint 19), but it is hard to see the loop lines under the sample. Please look at the attachment.
Can these lines become more apparent somehow?
hi,
starting from today's latest v0.9.1.14git.[f98e37], sample start point (offset) support is now a reality.
cheers
Related
Commit: [f98e37]