Hi everybody,
i've tried to use xtc mode today, but failed.
I managed to have the devices included into cubase menus.but whenever i want to use an effekt or synth, then cubase freezes.only if i kill the vstbridge prozess through taskmanager cubase comes to life again.but. this is kind of weird,'cause i thought that vstbridge is only necessary to bridge 32bit plug-ins into 64bit cubase and that by installing scope/64 it wouldn't be necesary to bridge.
I scanned planetz to find some hints, but nothing helped or things were to confusing (rebuild xtcproject.pro...what theh heck).
Anybody with a working xtc setup in comparable env? Any hints for me?
peter
scope 5.1/64 xtc freezes cubase 6/64 on win7
-
soylent.green
- Posts: 97
- Joined: Sun Jan 04, 2004 4:00 pm
- Location: Munich, Germany
Re: scope 5.1/64 xtc freezes cubase 6/64 on win7
I think only the ASIO and wav drivers are 64 bits in scope v5.1, the plug-ins maybe are still in 32 bits, someone could confirm ?soylent.green wrote:Hi everybody,
i've tried to use xtc mode today, but failed.
I managed to have the devices included into cubase menus.but whenever i want to use an effekt or synth, then cubase freezes.only if i kill the vstbridge prozess through taskmanager cubase comes to life again.but. this is kind of weird,'cause i thought that vstbridge is only necessary to bridge 32bit plug-ins into 64bit cubase and that by installing scope/64 it wouldn't be necesary to bridge.
I scanned planetz to find some hints, but nothing helped or things were to confusing (rebuild xtcproject.pro...what theh heck).
Anybody with a working xtc setup in comparable env? Any hints for me?
peter
Did you try with jbridge (another bridge for 32 bits plugs) ?
Sonic Core Luna II + Pulsar II scope v5.1.2709-x64, Cubase 9.0.20 (64), Pro Tools 12.7, Wavelab element 9 (64), windows 8.1 pro (64), Asus P6T 18Go RAM core i7 920, SSL Duende Native - Lexicon PCM Reverb Bundle - Waves - Sonnox
-
soylent.green
- Posts: 97
- Joined: Sun Jan 04, 2004 4:00 pm
- Location: Munich, Germany
Re: scope 5.1/64 xtc freezes cubase 6/64 on win7
Hi guys,
after going through literaly "thousands" of upload-key-file dialogs for each and any of the plug-ins once, I'm still not able to use xtc mode. I thought I'm made a step forward but that's not true...
When starting cubase 6 again "as administrator" and the trying to create an instrument track, I don't see the xtc plug-ins in the list of available instruments. What I then tried is to refresh the list of vst plug-ins within cubase. This leads to a lock up of cubase: The damn VstBridgeProcess starts and builds up some memory, but then nothing more happens. When using Win7 Resource Monitor I see that VstBridge has already loaded some Scope DLLs and stuff and I see Cubase 6 went read (in the list of processes in resource monitor). Using context menu option "Warteschlange analysieren" (must be something like "Wait Chain Traversal" in english) then the system tells me "Mindestens ein thread von cubase 6 wartet auf die fertigstellung von Netzwerk E/A" (= "At least one thread of cubase 6 waits for network E/A"). Analysing further I see that cubaes6 process connects with VstBridge via TCP, yeah why not, but why are they not talking to each other? what the heck? this is all weird...and I hate it. I finally kill the VstBridge and guess what...the damn registration import loop starts again.
Why is the network traffic between cubase and VstBridge disturbed? Any hints?
Cheers
Peter
after going through literaly "thousands" of upload-key-file dialogs for each and any of the plug-ins once, I'm still not able to use xtc mode. I thought I'm made a step forward but that's not true...
When starting cubase 6 again "as administrator" and the trying to create an instrument track, I don't see the xtc plug-ins in the list of available instruments. What I then tried is to refresh the list of vst plug-ins within cubase. This leads to a lock up of cubase: The damn VstBridgeProcess starts and builds up some memory, but then nothing more happens. When using Win7 Resource Monitor I see that VstBridge has already loaded some Scope DLLs and stuff and I see Cubase 6 went read (in the list of processes in resource monitor). Using context menu option "Warteschlange analysieren" (must be something like "Wait Chain Traversal" in english) then the system tells me "Mindestens ein thread von cubase 6 wartet auf die fertigstellung von Netzwerk E/A" (= "At least one thread of cubase 6 waits for network E/A"). Analysing further I see that cubaes6 process connects with VstBridge via TCP, yeah why not, but why are they not talking to each other? what the heck? this is all weird...and I hate it. I finally kill the VstBridge and guess what...the damn registration import loop starts again.
Why is the network traffic between cubase and VstBridge disturbed? Any hints?
Cheers
Peter