gabriels
2009-12-24 20:54:28
Florian,
I've discovered the root cause of my problem with a corrupted Project file. All is well until I try to remove an aliased port. If there is still a reference to it in the MT code, deleting the aliased port in MIDI SETUP somehow scrambles the code and creates the dreaded "ERROR: Wrong string format" when I try to load the code after saving it. Strangely, the code seems to work fine until I save. After that, I can't load the file successfully. What does load is all Presets up to the first offending Preset (one with a deleted aliased port), but all subsequent presets disappear.
Thankfully, the "Save Project as text" utility came in handy, since I was able to easily search through the text file and find all "offending" references to the aliased files. This is rather laborious when doing it in MT itself.
In my case, I had some aliased ports used as default input and output for several of the presets and for some of the translators. When I went through the code and redirected the ports to the original (unaliased) ports, I was then able to delete the unneeded aliased ports using MIDI SETUP.
True, there is notification that you are about to delete an alias that is used in the Project, but I think I got that message even after I had reassigned all presets and translators to use the unaliased ports.
In any case, if I'm right about this, it would help to explain this situation more clearly in the manual to keep other people out of trouble.
Gabriel
I've discovered the root cause of my problem with a corrupted Project file. All is well until I try to remove an aliased port. If there is still a reference to it in the MT code, deleting the aliased port in MIDI SETUP somehow scrambles the code and creates the dreaded "ERROR: Wrong string format" when I try to load the code after saving it. Strangely, the code seems to work fine until I save. After that, I can't load the file successfully. What does load is all Presets up to the first offending Preset (one with a deleted aliased port), but all subsequent presets disappear.
Thankfully, the "Save Project as text" utility came in handy, since I was able to easily search through the text file and find all "offending" references to the aliased files. This is rather laborious when doing it in MT itself.
In my case, I had some aliased ports used as default input and output for several of the presets and for some of the translators. When I went through the code and redirected the ports to the original (unaliased) ports, I was then able to delete the unneeded aliased ports using MIDI SETUP.
True, there is notification that you are about to delete an alias that is used in the Project, but I think I got that message even after I had reassigned all presets and translators to use the unaliased ports.
In any case, if I'm right about this, it would help to explain this situation more clearly in the manual to keep other people out of trouble.
Gabriel
