VE2 and DP5.13: hang issue
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
VE2 and DP5.13: hang issue
I've seen this issue over at the VSL site, but thought I'd check here to see if there was anyone who had found a workaround for this one.
I have a DP project which has VE instantiated in a V-Rack, and the saved version of the DP project calls up a VE project with several instruments already loaded. The problem happens on the first startup of the day: DP opens fine, I choose the project to open and all goes smoothly until the VE window appears. I see the VE Service window, but I don't get the Server Interface "connected" window, I don't get the 'loading data please wait', and instead of the 6 instrument setup that should appear, I get a default 2 instrument VE window, but DP has hung in the background without going on to load the other VIs in the project.
The first time it happened I re-installed VE and re-scanned the Directory Manager; Everything loaded fine in DP. But when I started up the next day, I was back to square 1.
Anyone have a clue as to whether this is a DP/AU issue, or a VE servr issue? I ran Disk Warrior and it solved the problem on the first re-start, but back to square one again when I did a subsequent shutdown/restart.
I have a DP project which has VE instantiated in a V-Rack, and the saved version of the DP project calls up a VE project with several instruments already loaded. The problem happens on the first startup of the day: DP opens fine, I choose the project to open and all goes smoothly until the VE window appears. I see the VE Service window, but I don't get the Server Interface "connected" window, I don't get the 'loading data please wait', and instead of the 6 instrument setup that should appear, I get a default 2 instrument VE window, but DP has hung in the background without going on to load the other VIs in the project.
The first time it happened I re-installed VE and re-scanned the Directory Manager; Everything loaded fine in DP. But when I started up the next day, I was back to square 1.
Anyone have a clue as to whether this is a DP/AU issue, or a VE servr issue? I ran Disk Warrior and it solved the problem on the first re-start, but back to square one again when I did a subsequent shutdown/restart.
DP7.22, MacPro 2.26ghz Quad Xeon, 32GB RAM, OS10.6.6, ViennaInstr/VEPro (crrnt), Waves NPP, PSP (various), Ozone4, Kontakt3 (crrnt), SymphChoirs, Omnisphere/Trillian/Stylus RMX (all current), TruePiano, 2408mk1, 828mk1, Yamaha 01V96
I believe it's at least partially a VE problem-- as VE on the Mac has always presented one interesting challenge or another such as the one you've mentioned. I was having odd issues with all versions of VE in Finale and in Logic as well. I'm not sure it's isolated to DP entirely.
Granted, MOTU has suggested that DP6 would have expanded AU support-- but that makes me wonder what aspects of AU compatibility might be lacking in DP5.13 to warrant a special announcement of expanded AU support in DP6 and whether or not such improvements would even address these particular issues. Hmm.
I've had to remove VE from my active components folder just to keep the VE server from instantiating itself (whenever Finale was booted), but I need to wait until my current scoring project is over before replacing VE to continue testing.
That's about all I know at the moment.
Granted, MOTU has suggested that DP6 would have expanded AU support-- but that makes me wonder what aspects of AU compatibility might be lacking in DP5.13 to warrant a special announcement of expanded AU support in DP6 and whether or not such improvements would even address these particular issues. Hmm.
I've had to remove VE from my active components folder just to keep the VE server from instantiating itself (whenever Finale was booted), but I need to wait until my current scoring project is over before replacing VE to continue testing.
That's about all I know at the moment.
6,1 MacPro, 96GB RAM, macOS Monterey 12.7.6, DP 11.33
Thanks Frodo, I was dreading the Finale experience after this so I'll look at your solution when it comes to Finale.
Believe it or not, I seem to have found something that works for me in DP. Seems to un-scientific to work but...
After trying all manner ore re-start/shutdown>re-scan Directory Manager>re-open DP project combinations, I've now had about 6 successful opens of the VE project with no hang from DP. During one of the re-starts I noticed that VRacks load VI's in order from left to right (which makes sense but I never realised it before).
After moving the VE to position 1 in the VRack, I haven't had any problems. Used to get hung up when it was sitting between Kontakt2 and Symphonic Choirs.
I'm sure there is some other unseen coincidence that has happened to create the stability, but so far so good.
Believe it or not, I seem to have found something that works for me in DP. Seems to un-scientific to work but...
After trying all manner ore re-start/shutdown>re-scan Directory Manager>re-open DP project combinations, I've now had about 6 successful opens of the VE project with no hang from DP. During one of the re-starts I noticed that VRacks load VI's in order from left to right (which makes sense but I never realised it before).
After moving the VE to position 1 in the VRack, I haven't had any problems. Used to get hung up when it was sitting between Kontakt2 and Symphonic Choirs.
I'm sure there is some other unseen coincidence that has happened to create the stability, but so far so good.
DP7.22, MacPro 2.26ghz Quad Xeon, 32GB RAM, OS10.6.6, ViennaInstr/VEPro (crrnt), Waves NPP, PSP (various), Ozone4, Kontakt3 (crrnt), SymphChoirs, Omnisphere/Trillian/Stylus RMX (all current), TruePiano, 2408mk1, 828mk1, Yamaha 01V96
V-Rack order. Who would have guessed? (I suppose that would be you!
)
Yes, I'm trying to get around V-Racks isues-- have had some issues with crashing after the first open and I try to do anything at all to it.
Do you not have any problems with VE when you are not running V-Racks?

Yes, I'm trying to get around V-Racks isues-- have had some issues with crashing after the first open and I try to do anything at all to it.
Do you not have any problems with VE when you are not running V-Racks?
6,1 MacPro, 96GB RAM, macOS Monterey 12.7.6, DP 11.33
Good point, I will try and check later on today (once I make up for the lost loading times over the past couple of days!)
BTW I did have luck opening the VE project initially by re-installing VE. Later I had similar results by removing the VI folders from the Directory Manager, adding them back, and re-scanning before launching DP. Eventually I could get it to open with just a re-scan, but I only had the strings to worry about, so this might be an onerous task if you've got loads.
This was early on in the troubleshooting, and the VE was still in the VRack. I'll post back on the non-VRack front
BTW I did have luck opening the VE project initially by re-installing VE. Later I had similar results by removing the VI folders from the Directory Manager, adding them back, and re-scanning before launching DP. Eventually I could get it to open with just a re-scan, but I only had the strings to worry about, so this might be an onerous task if you've got loads.
This was early on in the troubleshooting, and the VE was still in the VRack. I'll post back on the non-VRack front
DP7.22, MacPro 2.26ghz Quad Xeon, 32GB RAM, OS10.6.6, ViennaInstr/VEPro (crrnt), Waves NPP, PSP (various), Ozone4, Kontakt3 (crrnt), SymphChoirs, Omnisphere/Trillian/Stylus RMX (all current), TruePiano, 2408mk1, 828mk1, Yamaha 01V96
I've read this on the VSL forum-- maybe it was your thread, doodles?doodles wrote:i notice that a lot of the time (i don't use v-racks), it will load up VE, but not the actual sounds. For some weird reason, if I double click on the VE plug-in on the mixer window, and then click on the reconnect button on the VE server, it then reloads all the sounds and all is good in the world.
Glad there's a reasonable workaround, but it just makes me wonder why VE kicks in with Finale when I don't want it to and then why it must be manually coaxed to life in a DP project containing VE/VSL instances on "allegedly" audio-active instrument tracks.
6,1 MacPro, 96GB RAM, macOS Monterey 12.7.6, DP 11.33
LOL!cmm wrote:Obviously it's all the bad karma from closing the VIP upgrade path
I've decided not to get too twisted about that until I see what the new upgrade path is. I can't upgrade to anything any more, and any other volumes would be full price for me anyway. It's like starting over as if I'd never bought any VSL products at all, but it's been this way for a while.

6,1 MacPro, 96GB RAM, macOS Monterey 12.7.6, DP 11.33