Hi Gary,
So first, thanks again for the suggestions.
I really appreciate it. I spent the evening diligently trying them out. I did not succeed.
I think you are on to something that there is something in the particular studio setup of some of the old files that makes SVP crash. That said, I haven’t managed to crack it.
So I tried the different ideas you suggest, summarized here:
First: Do the songs that trigger the errors ever open after retry, or do they absolutely crash every time?
It crashes every time. Oddly, the “SVP Demo” opened them but SVP PPC won’t. The problem is that the demo does not allow exporting SMF files.
Second: Where are your "new" OMS prefs? They should be in a folder inside an OMS folder inside the system folder - NOT inside the system folder preferences folder but just inside the system folder itself. Yes, the are in System Folder/OMS Folder/OMS Preferences
If the "bad" tunes absolutely will not open without a crash, you need a different approach. Ok!
1. A newer version of OMS. Preferably from the same era as the version of SVP. That will most likely be 2.3.8
Installing 2.3.8 fails in the middle of installation saying an unexpected error occurred installing the Proteus 2000. :-(
2. Decreasing the RAM to SVPSame result.
3. Try to open them in SVP without making the setup currentType 2 error
Now we're getting more frustrated - take a break. ![Grin ;D](http://macos9lives.com/smforum/Smileys/default/grin.gif)
True that.
4. Create an OMS studio setup file from scratch that matches the original setups from the 1.4 era. In trying this it hung while searching for drivers after I clicked the modem and serial ports.
5. Create a new SVP setup file using the fake OMS setup. When you next try to open a "bad" file, start SVP first, then try to open a "bad" file.See above.
I tried creating a fresh OMS setup that approximated what I thought might have been the configuration tied to the old files that are crashing. I remembered I used an Emax II on the modem port in addition to the Proteus 1 on the serial port. I tried doing a setup that used the MT4 over USB but told it there was a Proteus on port 1 and an Emax II on port 2.
Upon launching SVP PPC it asked:
Make a new set of instruments from the output devices and channels in the current Studio Setup?
Instruments which are currently in use and custom instruments (for example with bold face names that you typed in) will be preserved. This operation is not undoable.
[]Always make from Studio Setup which I left unchecked. Check this to remind you to update your instruments whenever the current Studio Setup changes.
[Don’t make][Make]
I tried [Make]
And left the []Always...box unchecked.
SVPPPC launched without problem.
I opened one of the files that have been working without a problem.
OMS threw a dialogue box:
The patches “All Proteus” do not match those in your current setup.
[Don’t][Make Current]
I chose [Don’t]
OMS: Would you like to keep patches that are saved with “All Proteus”? If not “All Proteus” will be permanently changed.
[Go Back][Change][Keep]
I chose [Keep]
This file that had opened in the past without problem opened again without problem.
I now tried opening a “bad” file.
When the File/open dialogue opened I left []Use setup instruments unchecked.
OMS threw a dialogue box:
The patches “All Proteus” do not match those in your current setup.
[Don’t][Make Current]
I chose [Don’t]
OMS: Would you like to keep patches that are saved with “All Proteus”? If not “All Proteus” will be permanently changed.
[Go Back][Change][Keep]
I chose [Keep]
It threw a type 2 error and had to reboot the machine.
I tried variations including:
checking the
- Use setup instruments in the File Open dialogue
[Make Current} in the patches don’t match dialogue
(At this point OMS reported: In order to make the names in “All Proteus” current please be sure to manually load these patches into these devices: (It displayed two icons, one was the icon of the Proteus 1 instrument from the OMS current setup, the other icon looked like the icon of an OMS document and had the name of one of the old OMS setup files (from v1.4) called “All Proteus/Proteus 1”.
It once again threw a type 2 error.
Summary:I feel like I have tried the permutations of the different choices available.
Would I be a quitter if I just worked to actually recreate the original hardware environment the files were built under? (get Vision 1.4 running on a MacClassic under OS7 using a serial Midi interface) and try it there? :-[