Posted
After installation I ran the program and experimented with audio & MIDI setup and various plug-ins. Having got in a bit of a mess I decided to close the program without saving anything, On restart, there were some of the earlier setups still there. I tried deleting these, and then closed the program. On trying to restart, the program hung. I then uninstalled the program from Windows Control panel, and reinstalled. The program still stalled on startup with the message as shown in the attached pdf.
Any ideas anyone ?
Di., 10.02.2015 - 21:34 Permalink
At which point in the startup process does it hang?
If it's very early, before the splash screen and console shows up, you might need to reinstall also the latest version of the iLok License Manager.
If it's later while the messages are rolling through the startup screen, let me know what the last message is that you can see.
Mi., 11.02.2015 - 12:05 Permalink
Thanks for your reply Andre.
Attached is a screen capture after the program hangs.
The plugin ARIA is a 32bit sample player with Garritan library samples I was trying to use for the Global Rack. On reflection I think the problem may be due to conflict between the two ASIO drivers (One for M-Audio Delta 1010LT Audio card, and one supplied with my Yamaha MOX6 synth). Also I'm not sure whether I should have a 32bit and a 64bit engine open at the same time. (I'm running on Windows 7 Professional 64bit)
I've even tried uninstalling and re-downloading the installer and re-installing so any advice would be helpful
Mi., 11.02.2015 - 14:01 Permalink
Running both engines at the same time may be difficult on Windows (due to ASIO conflicts).
A plugin would never hang SynfirePro.exe, because Engine.exe ist doing all audio alone. I wonder why SynfirePro.exe is mentioned in your crash report.
Be sure you update ARIA Player to the latest version.
Also check if you possibly have similar problems with a DAW using this plugin.
Mi., 11.02.2015 - 17:54 Permalink
Thanks for your response Andre
The Aria player (can be used in 32bit and 64bit systems) works fine in my DAW (Cubase 7.5 64bit) and is the latest version.
It seems that both engine 1.01 and engine 2.01 attempt to start automatically. I assume these correspond to 32bit and 64bit engines. If there is a driver conflict how can it be avoided? I've removed the Aria plugin entirely from the VST plugins folder, but as you say, this is unlikely to be the cause of the problem.
I believe the ASIO driver I am using in Cubase (M-Audio Delta 1010LT) is the latest version and I think is multi-client, but the M-Audio website does not confirm this. I have downloaded the ASIO4ALL 64bit driver which works ok in Cubase and might be useful.
Any further thoughts ?
Jimledge
Do., 12.02.2015 - 11:45 Permalink
I have already tried uninstalling both audio engines and the synfire program and then reinstalling . When I do this, the installer describes the audio engines as "prerequisites" and installs both the "Audio Engine" and the "Audio Engine (x64)" before installing the program. When run, the program still hangs at the same place.
Do you mean I should just uninstall the "Audio Engine" (not the "Audio Engine (x64)" )? Do I need to uninstall the progam as well before reinstalling? Should I download again the installer ? Please clarify
Jimledge
Fr., 13.02.2015 - 12:47 Permalink
andre :
I have tried an uninstall, fresh download, and re-install. Audio Engine and Audio Engine (x64) are mandatory and are both v. 2.1.0. When I start Synfire the program hangs in the same place as before. You will see from my earlier screenshot that the program is trying to "restore" engine 1.01 and engine 2.01 when it crashes. These are obviously not Audio engine version numbers - I don't know what they refer to. Where do these engines come from ? Is the program somehow remembering some settings I made when I first ran the program ? If so, how can these be reset ?
How can I get this program to run ?
Jimledge
Fr., 13.02.2015 - 14:00 Permalink
You can rename the file CurrentRack.cogsetup in the Config folder under 'Racks'. This is what Synfire loads on startup, unless you last saved your rack to another filename. If so, just rename that file and Synfire will come up with an empty default rack. In any case, renaming the file that it is trying to load will bypass it on startup.
The numbers are port numbers. It tries to load pugins on both 32 and 64 bit Engine (Engine1 and Engine2), which may be the culprit.