Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow selecting In and Out points in a sample #16

Closed
unfa opened this issue Mar 21, 2018 · 8 comments
Closed

Allow selecting In and Out points in a sample #16

unfa opened this issue Mar 21, 2018 · 8 comments

Comments

@unfa
Copy link

unfa commented Mar 21, 2018

I'd like to load up a long sample and select just a short part from it to be played back.
I tried using the loop markers but they do a different thing. I first thought the are just for that.

I think it'd be great to have a separate "In/Out" range markers to select a part in the sample to be used.

Also being able to zoom in/out in the sample waveform preview could be a great help to precisely select the In/Out points.

I know I could prepare precisely cut samples to be loaded into Samplv1, but being able to do this live is adding much versatility to the plugin, also be cause one could automate the In/Out point positions to effectively change the sound between each played note.

@rncbc
Copy link
Owner

rncbc commented Mar 21, 2018

hello unfa, this has been asked indeed way too many times, but the same answer and only goes in return: nope :)
please edit your sample before loading into samplv1; use an audio file editor for just that, audacity comes always in first. but you can choose any other to trim the sample--you even get resource (read memory aka. ram) savings with that procedure, coz samplv1 loads the whole sample image into live memory anyway.
hyu.
cheers

@unfa
Copy link
Author

unfa commented Mar 22, 2018

Thank you. I understand that approach, but I still think that this functionality would be beneficial to creative freedom, especially with automation.

Also I think that loading 30 or 100 more MB of PCM data into RAM is not big deal in modern systems boasting 8 GB of RAM or even more. If low memory usage is key - sure but why force that on the users?

@rncbc
Copy link
Owner

rncbc commented Mar 22, 2018

sorry, but that setting (as the loop points) cannot be automateable--if there are some host or DAW that you know that does it, then it's doing it wrong, glitch-prone and above all it won't ever be sample accurate as it probably advertises ;)
byee

@unfa
Copy link
Author

unfa commented Mar 23, 2018

The problem is - even when I try to truncate the sample before loading it into Samplv1 - I sill often have to redo that a few times as in real use it works differently than I expected.

In such case I also have to reset my loop marker swich might be tricky.

I think LSP's Sampler has the truncation options but it doesn't have looping functionality on the other hand. Which makes it not suitable for sustained melodic instruments.

@mxmilkiib
Copy link

mxmilkiib commented Jun 25, 2018

Start and end points would be handy for faff free topping and tailing. The Akai S900 has a Discard feature that "...eliminates those portions of the sample before the start point and after the end point. Since you do not hear these parts of the sample, discarding the sample past these points will save memory." Possibly a similar system, manual or automatic, could work in samplv1?

Start/end point automation is nice and all but hard and not so old-school.

@rncbc
Copy link
Owner

rncbc commented Jul 17, 2018

hi,

starting from today's latest v0.9.1.14git.f98e37, sample start point (offset) support is now a reality.

cheers

@unfa
Copy link
Author

unfa commented Jul 17, 2018

Yay! Many thanks, @rncbc !

@rncbc
Copy link
Owner

rncbc commented Jul 19, 2018

things are getting better (hopefiully)... just check 0.9.1.21git.667a8 and beyhond... ;)

@rncbc rncbc closed this as completed Feb 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants