Issues with audio when synchronizing Roms with prodatum

[DaliborCruz]

Synchronizing command station roms with prodatum causes the audio to glitch out and not work until I factory reset the command station.

[neil-briscombe]

that's worth knowing! What version of the is your system ROM?

[DaliborCruz]

that's worth knowing! What version of the is your system ROM?

E-MU MP7 is the latest OS. After the fact, I saw that my CS was sending tiny, glitched-out midi signals that I could visualize in Ableton. Thought it could have been that.. I reinstalled the OS and it fixed the midi glitch problem, but didn't fix the Prodatum problem. Have yet to try it out on one of my P2K modules. Going to try that out to see if the problem persist beyond the CS. Something I didn't mention before is that my ROMs do sync, but other than that it's a bust.

[unityconstruct]

@DaliborCruz .. hey brother...

RE:Prodatum

• I had issues sync'ing recently, with Prodatum crashing or getting through the Sync Process, but there was clearly data corruption.
  • At least once it was unrecoverable, so I deleted the config files it creates to 'reset' it.

Environments [ XL7 ]

• Linux/WINE
  • My main box is on linux and the M-Audio FastTrack USB comms are super flaky on nearly all my editors. ( I run winapps in WINE)
• Linux/VirtualBox/Win7
  • I also have VirtualBox running Win7 with windows taking the FastTrack with marginally improved comms, but still too flaky to trust.
• Win7/Win10 direct
  • Life is better on Windows, but results vary when trying to grab EVERYTHING in one go
  • I was able to get through the sync process by only selecting 1-2 items in the Menu > Synchronize options
  • Even then the Presets/Patterns lists get corrupted around #150-200
  • Possible that names containing ( ' ) and ( " ) aren't handled well & if they are on the ROM, not much can be done that I know of.

Tips:

• increase the MIDI Sysex Delay to Max
• only sync on thing at a time
• once successfully sync'd zip up the entire prodatum directory ( though I think only prodatum-config is volatile )
  • i've had success with iterative syncing after the initial dumps
• the CS memory could very well be corrupted & before FactoryReset, you can try CompactFlash:
  • Save/Copy > Manually Compact Now! ( 2nd to last option )
• also dumping presets/arps/etc to sysex via MIDIOx or some other sysex tool, then pushing them back over might straighten things out.
• There are several differences between Proteus2000, Audity, PKeys, CS's and Prodatum, while gracefully handling much of it, doesn't quite address them all. This said, I have all the CSs and don't think I ran into it...
• Might suggest testing with Prodatum previous version to see if anything was introduced.
• I think prodatum won't try to immediately sync once it successfully sync's the first time. I maintain dedicated prodatum instances for each unit so I don't destroy setups for MP7 by connection XL7.

NOTE: I'm assuming Prodatum sync is A READONLY affair, so its curious it is leaving it in a jacked up state.

Hope some of this helps!