This resource seems to be a good starting point (all service manuals / schematics) :
https://www.synthxl.com/manufacturers/
DSP563xx Emulator (Access Virus, Nord Lead, Waldorf MW...)
-
- KVRian
- 1154 posts since 17 Feb, 2010
https://www.synthxl.com/manufacturers/
-
- KVRist
- 112 posts since 13 Aug, 2019
No Access, no Waldorf, no Clavia, no Novation...xhunaudio wrote: ↑Wed Jun 02, 2021 6:49 amThis resource seems to be a good starting point (all service manuals / schematics) :
https://www.synthxl.com/manufacturers/
Why is it a good starting point?
It has Korg MS 2000 and stop counting
-
- KVRian
- 1154 posts since 17 Feb, 2010
... ...
My sincere apologies, Sir.
Last edited by xhunaudio on Thu Jun 03, 2021 8:31 am, edited 1 time in total.
-
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia
Could go either way, but it's probably more logical to have one plugin per synth, for organizational purposes in the DAW.
-
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia
You would first need to load the ROM, then a preset. Or rather, the plugin won't even do anything unless ROM is supplied.
-
- KVRian
- 821 posts since 14 May, 2014
Probably! that would be no different than loading any old session and repopulating with the same sounds. But I do agree that it's impossible to point the Emulator toward a specific preset without loading the proper ROM first. The video game emulator/rom analog holds true as always
-
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia
Yeah path to ROM would be stored in plugin's data chunk. Probably cannot store the whole ROM as part of DAW project, since that might end up being redistributed (i.e. sending a project to somebody) and that's illegal.
Another option is storing the path to ROM in registry/plist. That's less portable but safer in the long run (plus it's easier to tweak the path to the ROM in registry/plist if it's moved, rather than updating a bajillion DAW projects one by one to update the path)...
Another option is storing the path to ROM in registry/plist. That's less portable but safer in the long run (plus it's easier to tweak the path to the ROM in registry/plist if it's moved, rather than updating a bajillion DAW projects one by one to update the path)...
-
- KVRAF
- 7890 posts since 12 Feb, 2006 from Helsinki, Finland
One option would be to store a hash of the ROM into the preset. That would let you reliably check that you have the correct ROM available without having to store the ROM itself into the preset.EvilDragon wrote: ↑Fri Jun 11, 2021 8:19 pm Yeah path to ROM would be stored in plugin's data chunk. Probably cannot store the whole ROM as part of DAW project, since that might end up being redistributed (i.e. sending a project to somebody).
Another option is storing the path to ROM in registry/plist. That's less portable but safer in the long run (plus it's easier to tweak the path to the ROM in registry/plist if it's moved, rather than updating a bajillion DAW projects one by one to update the path)...
-
- Banned
- 10732 posts since 17 Nov, 2015
I guess if it's a separate. dll for each synth/ROM, when you load the synth, it would ask you to load the relevant ROM.... or if its a legacy load, it will automatically load it from previous state? dunno, seems easy but could be complicated..... depends on implementation
-
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia
Indeed, that's a very good idea, run an MD5 checksum on it, store the result in plugin extra state chunk, verify on load.mystran wrote: ↑Fri Jun 11, 2021 8:47 pmOne option would be to store a hash of the ROM into the preset. That would let you reliably check that you have the correct ROM available without having to store the ROM itself into the preset.EvilDragon wrote: ↑Fri Jun 11, 2021 8:19 pm Yeah path to ROM would be stored in plugin's data chunk. Probably cannot store the whole ROM as part of DAW project, since that might end up being redistributed (i.e. sending a project to somebody).
Another option is storing the path to ROM in registry/plist. That's less portable but safer in the long run (plus it's easier to tweak the path to the ROM in registry/plist if it's moved, rather than updating a bajillion DAW projects one by one to update the path)...
