Closed tanno1 closed 1 year ago
can you see if anything is in the log file (should be in the LMN-3 config directory somewhere)
Yes, there is a ton of stuff here. Mainly consisting of Controller [#]: 1, or Note on D3 and Note off D3 (or other notes). Should I be seeing what is at the top or the bottom of the file?
Here is what I see at the bottom of log.txt before having opened the drum sampler:
After I crash the program opening drum sampler and open up log.txt again, this is what I see:
alright doesnt look like anything helpful in the log then. Can you try starting the LMN-3 application in its own terminal window (ie run ./LMN-3 yourself in the terminal, not on startup) and see if anything helpful in printed in the terminal window after the crash
Here is what it looks like after starting it from the terminal
And here is what I get when I open drum sampler and crash it:
ok so youve got some badly formatted yaml in your drum kit somewhere, run your yaml through something like yamllint and it should point you to what could be wrong
Ok got it, first time working with yaml stuff. Thanks! Has anyone started working on a JUCE application to make this easier?
There is this which is python based. I have not used it but looks like some folks have.
Hey! I just finished my build, however when I go to the drum sample and press in on the second encoder, the whole software shuts down. Not sure where to start with debugging this one, if there are any ideas let me know. I added a photo of the contents of my folders all the way up to a sample pack as well as my .yaml file for one of the kits I made.
As an experiment, I placed one of my kits in the samples area, and I can access that and go through the directory to choose one noise, but that isn't exactly ideal. I will look into this more on my own as well and update this issue if I find any answers. If anyone doesn't know the solution, recommendations on where I can look are great as well.
Thanks tanno