Open editor for electribe sampler
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Hi there,
got myself the sampler now and just want to thank you,Brakio,for the editor and especially to make it available on mac as well!
It runs on my old mountain lion although it`s still a little wonky.It crashes quite often and this seems somehow related to my mouse(wheel).Whenever i scroll thru a list or just the sample/preset page i can count the seconds until it crashes.Nonetheless,better than nothing of course.I should just save often.
I would appreciate an iOS editor as well but i don`t see how this would work without a jailbreak because you can`t access the file system on the card (and you need a special cardreader adapter of course).Afair you can just import/export photos to/from a card.
Such a pitty that you can`t access the Sampler (and card in the sampler)via USB.Especially since Volca Sample can do this.Bummer.
got myself the sampler now and just want to thank you,Brakio,for the editor and especially to make it available on mac as well!
It runs on my old mountain lion although it`s still a little wonky.It crashes quite often and this seems somehow related to my mouse(wheel).Whenever i scroll thru a list or just the sample/preset page i can count the seconds until it crashes.Nonetheless,better than nothing of course.I should just save often.
I would appreciate an iOS editor as well but i don`t see how this would work without a jailbreak because you can`t access the file system on the card (and you need a special cardreader adapter of course).Afair you can just import/export photos to/from a card.
Such a pitty that you can`t access the Sampler (and card in the sampler)via USB.Especially since Volca Sample can do this.Bummer.
Hi, thank you,Crabman wrote:Hi there,
got myself the sampler now and just want to thank you,Brakio,for the editor and especially to make it available on mac as well!
It runs on my old mountain lion although it`s still a little wonky.It crashes quite often and this seems somehow related to my mouse(wheel).Whenever i scroll thru a list or just the sample/preset page i can count the seconds until it crashes.Nonetheless,better than nothing of course.I should just save often.
I would appreciate an iOS editor as well but i don`t see how this would work without a jailbreak because you can`t access the file system on the card (and you need a special cardreader adapter of course).Afair you can just import/export photos to/from a card.
Such a pitty that you can`t access the Sampler (and card in the sampler)via USB.Especially since Volca Sample can do this.Bummer.
If you could make a bug report on GitHub it would be nice.
Attach the a zip of the Oe2sSLE.log file to it. I will have a look. If it is too big, delete it, launch the app and makes it crash. Then attach the new Oe2sSLE.log file.
For Mac OS I'm developing on a Snow Leopard in order to be compatible with old OS versions. It runs well on it but I can't test on more recent versions.
If I cannot solve the issue, i'll just disable the mouse scroll handling on this os version...
Thanks for your reply,i`ll make it crash the next time and upload the file.
It also crashes always when i preview a new sound before the one i prelistened before is completely silent.Same in the (wave)editor (hitting the"play"button again before the sample finished playing)
Crashing seems not only related to mousewheel but also swiping on the touchpad.
Though I can use it mostly without crashes if i avoid the mentioned things.
A question about file handling:i deleted about half of the factory samples and kept the rest for now.But after reloading the"all"file the empty slots were used by samples that follwed...sorry,my english.I give you an example
If i delete sample number 345 and i have a kick on 346,after saving and reopen the"all"file that kick will be on 345 instead of leaving the slot empty.That leaves a lot of the(factory)pattern in a messy state.Is that normal,intended behavior or a bug?I`ve read somewhere that deleting samples should just leave the slot"empty"but maybe i`m wrong...
edit:where can i find the log file?
It also crashes always when i preview a new sound before the one i prelistened before is completely silent.Same in the (wave)editor (hitting the"play"button again before the sample finished playing)
Crashing seems not only related to mousewheel but also swiping on the touchpad.
Though I can use it mostly without crashes if i avoid the mentioned things.
A question about file handling:i deleted about half of the factory samples and kept the rest for now.But after reloading the"all"file the empty slots were used by samples that follwed...sorry,my english.I give you an example

If i delete sample number 345 and i have a kick on 346,after saving and reopen the"all"file that kick will be on 345 instead of leaving the slot empty.That leaves a lot of the(factory)pattern in a messy state.Is that normal,intended behavior or a bug?I`ve read somewhere that deleting samples should just leave the slot"empty"but maybe i`m wrong...
edit:where can i find the log file?

just came across another sample manager
http://www.appification.de/ElectribeSampleManager/
don't know if it's been mentioned in the forum before.
http://www.appification.de/ElectribeSampleManager/
don't know if it's been mentioned in the forum before.
Ok, maybe it is a bug that was introduced during the refactoring. I will have a look at this.Crabman wrote: A question about file handling:i deleted about half of the factory samples and kept the rest for now.But after reloading the"all"file the empty slots were used by samples that follwed...sorry,my english.I give you an example![]()
If i delete sample number 345 and i have a kick on 346,after saving and reopen the"all"file that kick will be on 345 instead of leaving the slot empty.That leaves a lot of the(factory)pattern in a messy state.Is that normal,intended behavior or a bug?I`ve read somewhere that deleting samples should just leave the slot"empty"but maybe i`m wrong...
edit:where can i find the log file?
The log file should be in the folder from where is run the application. It may be THE bug if it can't write to the log file

I think so.Otherwise it would mess up all pattern that use samples past 345 (to stay in my example)Brakio wrote: Ok, maybe it is a bug that was introduced during the refactoring. I will have a look at this.
Yep,there is no log fileBrakio wrote: The log file should be in the folder from where is run the application. It may be THE bug if it can't write to the log fileI will look at this also.

For that issue, I can't reproduce your problem. To load the saved file, do you use the "Open" button? If you use the "Import e2sSample.all", yes it does not keep the order, it just import the samples of another e2sSample.all file and append them to the current one. But open should do the job (it does in my tests)Crabman wrote: If i delete sample number 345 and i have a kick on 346,after saving and reopen the"all"file that kick will be on 345 instead of leaving the slot empty.That leaves a lot of the(factory)pattern in a messy state.Is that normal,intended behavior or a bug?I`ve read somewhere that deleting samples should just leave the slot"empty"but maybe i`m wrong...
Brakio wrote:For that issue, I can't reproduce your problem. To load the saved file, do you use the "Open" button? If you use the "Import e2sSample.all", yes it does not keep the order, it just import the samples of another e2sSample.all file and append them to the current one. But open should do the job (it does in my tests)Crabman wrote: If i delete sample number 345 and i have a kick on 346,after saving and reopen the"all"file that kick will be on 345 instead of leaving the slot empty.That leaves a lot of the(factory)pattern in a messy state.Is that normal,intended behavior or a bug?I`ve read somewhere that deleting samples should just leave the slot"empty"but maybe i`m wrong...
aaah,that`s a very good tip.I always used the"import e2s etc.all" (right after i open/reopen your app for example)an not the"open"function.I thought it does not make a difference.I´ll try that,thanks!
Are you sure? Folder starting with a dot are hiden on unix systems. Can you try to open a terminal and type 'ls ~/.Oe2sSLE/Oe2sSLE.log'. If the file does not exists it means it is a more serious problem related to python itself or maybe tkinter. Because any error should be reported in the log or a popup window should be seen if log cannot be writen to the file.Crabman wrote:I downloaded the new version and made it crash (a two finger swipe will always shut it down) but i`m still unable to find the log file.Tried it via"search"function as well but...nothing.
Nevermind,i can avoid most of the crashes if i take care.Don`t waste your time to make it run on such an old OS but thanks for trying
More important to me was the info about the difference between import vs.open the".all" file.
Maybe i`ll buy the other editor but for now your one is good enough.Currently I`m even not 100% sure if i keep the sampler or return it to get the Electribe Synth instead.

More important to me was the info about the difference between import vs.open the".all" file.
Maybe i`ll buy the other editor but for now your one is good enough.Currently I`m even not 100% sure if i keep the sampler or return it to get the Electribe Synth instead.
Hi Crabman,
I have updated tcl/tk on my mac and used another more recent version of python to generate a new build (Oe2sSLE-0.1.2-osx-x64-build2.zip) could you try it and say me if it still crash?
I think that if you have the problem, others have too... so it is better to solve it
If this release still not work I will generate another build, but this time to be run from a terminal, and there will probably be outputs to the term that will explain why it crash.
I have updated tcl/tk on my mac and used another more recent version of python to generate a new build (Oe2sSLE-0.1.2-osx-x64-build2.zip) could you try it and say me if it still crash?
I think that if you have the problem, others have too... so it is better to solve it

If this release still not work I will generate another build, but this time to be run from a terminal, and there will probably be outputs to the term that will explain why it crash.