Good to hear all those plugins work !Nice, I will keep it in mind about that bridging. It's true you can do that. Well we can't stop the future anyway, one day we will look back at 32 bit like we look now back at 8 or 16 bit...
For me it was also the reason considering 64 bit to pass the 4GB limit (actually sg like 3.2-3.5GB usable). But since I was installing a new pc from scratch I stayed at the safe side and installed a dual boot system XP 32/WIN 7 64.
The thing is that if you indeed don't use big sample libraries the ...
But I also have a session in Windows 7 64 bit, but where Cubase is run in 32 bit. It should work there. But if it can make you feel better, XTC is nice but the Scope VSTi's are not "that" special (the synths are pretty thin in sound, tested them all yesterday ...
I learned alot the last couple of days, especially getting the XTC mode to work properly. Wouldn't have done it without the help of you guys and believe me I googled alot on the subject before posting to this forum. But everybody has their own way of working, which is also ...
Thx bear ! Your last tip actually works. I used my old template changed the 1632.dev file to a 1632.mdl file, enabled xtc put back the VST folder to the Cubase folder and everything seems to work now like in a normal Scope mode AND I have access to the synths and effects directly ...
I will do some furher testing next monday, maybe i'm overseeing something. I was wondering why sequenser vst integration would only be possible in xtc mode. I mean, the scope vst plugin folder is in the Cubase vst folder anyway, so why wouldnt it work in normal scope mode. Is this a ...
Thats what I all tried before. The last scheme I sent does work when scope is open, so i save this as an xtcproject with xtc enabled. I close scope and open Cubase and this time no sound. I do see asio sources getting in to Cubase channels. That is to say, if i use a softsynth and i play on a ...
Ok, getting there but not 100% yet, so need some extra help.
What I did is adjust the XTCproject file, didn't change the name but did my own routing scheme like in example. I enabled XTC mode AND I closed Scope. Started Cubase and yes the plugins are nicely there and effects and synths starting. No ...
I admit, I'm completely guilty here :roll: The scope has the XTC marked and is INDEED open. I always read in the manual to close the scope program when running in XTC mode, but I could never really figure out how can I route things than the way I want it so Cubase can see the ...
To be honnest, I don't have much time to dig this one out and I could manage to route the VST's within Scope so I can use them in Cubase via the Scope platform. Can't load more than 1 synth anyway since I only have a 3 DSP board. So at this point not a crucial error for me.Of course it ...
Windows 7 64 bit , cubase 5 32 bit windows XP SP 3 32 bit, Cubase 5 32 bit
Both crash and gave the same registery windows on every plugin found. So I have the feeling it has got something to do with that question for registering. Cubase on both systems runs without ...
Just passed over to Scope 5.1 and when I read the installation notes I thought the integration of VSt's into my sequenser would be a breeze but it isn't :-(
I followed the mail Sonic sent me. They gave me a keyfile for Scope, so that's the first I did, installation of the soft. Scope card ...
That's it ! I recall that audio release check box, but I thought it had to be marked. So stupid, I was with my noze on it just not telling to me : hey uncheck me ! Well I did, and works perfectly now. By the way I still run in XTC mode, never really understood that much the difference between XTC ...
wasn't really sure I could do this, but it works they way you told me, thx ! It does make sense to me to work this way. If I only use 1 mono channel I can also only use mono effects, if I use a stero channel I get the extra stereo effects like Chorus, stereo delays and others. If I use a ...
I have this z-link analogue in/out box for a luna II card running on scope 4.5 (actually just bought the 5.1 but waiting for my new keys now). And since my normal mixing desk was getting a bit full I was thinking to connect some monosynths to the Z-link which I was never really using before. My ...
First of all, all problems are solved by now. I wasn't even running anything besides the scope when my system froze, didn't even open a project, just the standard one. By now I am 100% sure it was just a driver problem. Combination with a new motherboard and CPU (Quad core 2600K)
After 3-4 days of trial and error I can finally say that my problem is FIXED :-) pc was running for almost 18 hours without any freeze so I'm at a point where it's safe to say now that I can continue with all my VST installations :-)
I don't have any doubt in your experience. I was an IT service technician for 10 years and still working in IT on another level but where I also have to deal with support questions. So I know the feeling you might have because I have it as well when you feel maybe the answer was close but ...