-
Notifications
You must be signed in to change notification settings - Fork 18
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
Crop sample #28
Comments
I will add a first simple implementation of this feature (also called "trim" in some wave editors) soon. Until then, if you do not use slices (which as I said are currently slightly buggy) you can load your current sample in the electribe and export them into wav file (or just export the e2sSample.all file). The electribe will automatically trim the sample between the start and the end markers. Latter I think I'll propose some tools to help users to save some memory, with supervised automatic detection of trimming location, or with re-sampling functionality. |
Fantastic, thank you for your answer and your work. With cropping: users
could go back to your software and then change the length of a sample. But
when exporting it could send only cropped part to the electribe. maybe
that's the solution?
Czw., 6.12.2018, 00:33: JonathanTaquet <notifications@github.com>
napisał(a):
… I will add a first simple implementation of this feature (also called
"trim" in some wave editors) soon.
I found some little existing bugs with slices when developing it, and will
fix them first. But it should be OK in a few days.
Until then, if you do not use slices (which as I said are currently
slightly buggy) you can load your current sample in the electribe and
export them into wav file (or just export the e2sSample.all file). The
electribe will automatically trim the sample between the start and the end
markers.
Note that I think that this systematic cropping of the electribe is not
really a good implementation choice. Because, if I want to be able to later
lengthen my sample I can't...
That is why the cropping I will add to the software will be only done on
user request.
Latter I think I'll propose some tools to help users to save some memory,
with supervised automatic detection of trimming location, or with
re-sampling functionality.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AficPPteTG-abXieximlwqW6IHZ8th-tks5u2FeygaJpZM4YOWuc>
.
|
A release with a trim function is published. |
Fantastic - thank you :)
niedz., 9 gru 2018 o 23:55 JonathanTaquet <notifications@github.com>
napisał(a):
… A release with a trim function is published.
We will see for other more advanced functions later.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AficPLo6BCIOeZdTCDVSxZxEPpIzJcyxks5u3ZTegaJpZM4YOWuc>
.
--
Michał Rusnarczyk
+48 500 657 300
|
If I have a long sample and want to use just a looped part of it, it still uses a lot of limited E2S memory. It would be very nice to have an option to crop sample and save onto sdcard only that part we use!
The text was updated successfully, but these errors were encountered: