Ksd Converter3/25/2021
Thats handy considering Im about 14 of the way thru making a preset pack.There is however no way to save to anything other than.nmsv with 1.3 which is kinda annoying.Any.ksd you load into 1.3 is converted into.nmsv on load.So if your collabing with anyone and your using 1.3 and they are using a previous version, Im guessing its gonna cause problems.
I kinda wanna know if its now safe to move all the.ksd files to a different folder not associated with Massive cause Im kinda OCD an they look a right state If I moved all the.ksd files then open something in my DAW that calls for one of them, whats gonna happen. Ksd Converter Dll And KeepI would suggest maybe sound designers keep using the earlier version of the plugin (you can rename the dll and keep both versions side-by-side) so they can keep saving as Koresounds. Im by no means a sound engineer or anything, just learnt various aspects of Massive by messing around with it so thought Id try and contribute or help peeps new to production. The new files Ive moved them into the Native InstrumentsMassiveSounds folder also in my documents. This has kept things tidy in the Massive browser everything is still working as expected here. ![]() I saw a post in the Absynth forum about.ksd files being converted to.nab. Just a guess tho, and yeah it is kinda annoying. Were the 500.ksd files that couldnt be converted definitely for Massive I did nearly 4000 and they all converted over fine. Ksd Converter Manual Addendum EnglishTheres more info about it in the Massive Manual Addendum English.pdf in the MassiveDocumentation folder that explains all the info about the new patch format. I think NI should have either included an option in the installer to keep your older version of Massive as well as have 1.3 installed or given a pulldown in the Save As option for a choice between.nmsv or.ksd, or even just a little batch tool you can run to convert.nmsv back to.ksd. Yeah, Im sure maybe some parameter info might be lost going backwards but it would give much better compatibility when releasing presets. And Ruari, yeah I made a dupe of my patch folder, renamed the one with both.ksd and.nmsv with OLD on the end, then deleted all the.ksd files out of the folder Massive usually looks for. Did a DB rebuild in the standalone, then started loading random projects in Ableton and it all seemed to work fine. Thats my OCD part sorted and my preset folders looking a little less insane Quick question, was anyone actually expecting this whole file format change or did it come as a surprise I dont remember reading anything about it in the Upcoming thread, but maybe I missed it. But if they are having to do that it shows the whole idea is badly implemented - they simply should have continued with the ksd format and just either let anyone who actually has Maschine convert them into Maschine format (as no-one else probably cares anyway) or even better let Maschine load ksd too. Ive kinda abandoned the whole preset pack idea for the time being now, which is no biggie cause it was just gonna be a freebie anyhow but its still irritating either way. Speaking of the new NMSV format, I would still love to see some kind of batch parameter editing tool because a lot of the Bank names have been duplicated or messed up in conversion and its a hassle to change each one in Massive.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |