Issue Converting 'Decent Sampler' to 'MPC' about convertwithmoss

[git-moss]

What is the unknown trigger type in the file? Can you send me an example?

[fallynnknivez]

Sure thing, So I make libraries w/ SampleRobot (it's more reliable than the MPC's AutoSampler). I then export a 'Bitwig.multisample' file that gets converted (w/ ConvertWithMoss) to a Decent Sampler file. I then edit them w/ Sublime Text, save it, then convert to MPC where I get the error (I'm rather new to Bitwig, so I haven't figured out how to edit multisample libraries there. As well; moving keygroups in the MPC is a pain in the ass) I should note; when I edit the Decent Sampler file in Sublime Text, I delete the loop related stuff (I do all the loop points and rimming on the mpc). Being a file ready to be converted to MPC, is why you don't see it in the file. Also of note; I have tried converting a program, 100% created on the MPC, to Decent Sampler (no errors this direction). However, when converting back to MPC it still reflects the same "issue". ZIP File Contents: 1. 'SLFrozen Strings Cello.dspreset' is the Decent Sampler file i am starting with 2. 'Settings.jpg' is what i have the convertwithmoss set to 3. 'Error.jpg' is the error 4. 'SLFrozen Strings Cello.xpm' is what i end up The output xpm file seems fine; It loads and plays in the MPC Live II. I'm sure the error has to mean something is wrong (or it wouldn't be there). I'm just not seeing what it is from an "end user" view point, that is to say it's not 100% obvious right way. I DO have to fix a couple things in the MPC Program Editor: like changing it from 'One Shot' to 'Note On', and other things like that. (FYI; For this particular one, I also forgot to set the high velocity range to 127 as well. That's not a conversion issue) One other 'not-really-related' thing; the output of the MPC option drops all the files into a folder (with the name of the original folder), but it wont allow you to export those into a folder that has another folder in it. So you have to create a folder, for it to make a folder in, then move THAT folder where you want it. I am not sure if there is a reason for this, and it's a minor thing, but thought i would mention it. (I'm guessing the reasoning for this is due to some other output options that don't make their own folder? Or maybe with the "preserve folder structure" button unchecked, it would cause issues?) Sorry, one other thing... somewhere in the conversion process, it also doubles up the note entries. You can see this in the 'Decent Sampler' file where it goes from "Samples/SLFrozen Strings Cello - Velocity 127 - 024 - c-c0.wav" to 077, and then restarts again. Not sure if this is related, even if i remove them before converting to MPC i still get the same error. [Issue.zip](https://github.com/git-moss/ConvertWithMoss/files/10375251/Issue.zip)

[git-moss]

Where did you upload the ZIP?

Why are you converting to Decent Sampler when you can directly convert from Bitwig Multisample to MPC keygroups with ConvertWithMoss?

[fallynnknivez]

It totally just occured to me that the email replies dont come to you as emails, sorry... I attached it here as well as the original post (and cleaned up all the email bs) I am converting to Decent Sampler so i can edit the program via a text editor. I am not very versed in Bitwig, and moving notes around is a pain in the ass on the mpc itself. For instance, moving a multi-layer keygroup from pad D1 to A1 on the MPC requires four steps, on three different screens. When in decent sampler form i can open the file in Sublime Text editor and run an arithmetic in hinote and lonote fields and be done. Converting it takes way less time then it would to move a piano instruments key on the MPC itself. I wish sample robot could export to decent sampler, and eventually i will learn bitwig enough to just edit it there, but for now this is pretty quick. After the sampling is done, if i dont have to do any loop points, it takes maybe 30 minutes to finish a sampled instrument. Most of that time is spent in Audacity normalizing and truncating silence on the samples themselves. [Issue.zip](https://github.com/git-moss/ConvertWithMoss/files/10375249/Issue.zip)

[git-moss]

The error will be fixed in the next update. However, the output will be the same.

I could also find the bug with the duplicated layers which was caused by a bug handling the old layer-format used by SampleRobot.

Both will be fixed in the next update.