So i installed my new copy of Cubase studio 4 today , although its been causing me problems all night ..
First up , the installer crashed 3 times , took me ages to actually get it installed , applied the 4.1 patch and got
syncrosoft problems , fixed them and now im in ..
Im setting up bus's and routing , and it looks like its on the verge of crashing , white screen , and app hangs for upto 15 seconds
then just comes back , everything seems to have a latency, click to open something , and a second or two later it opens.
I used SX3 for about a year and it ran smooth , crashed occationaly , but I figured that would of been fixed in C4 ..
ALSO , I opened a few recent projects iv been working on , and they sound COMPLETELY different .. like .. they suck.
Basslines are fucked , all tracks are clipping badly , and small level redlines causes crackling ..
Almost appears as though all my presets from previous projects are different .. so many synths and sounds now just sound shit ..
like a tearing detuned saw lead is now replaced with some cheesy brass clone preset .. yet other presets are fine.
Only half of my VST's showed up in the plugins list , yet I can see them all being scanned on start up, and they are in my instruments list... restart windows and they show up.
Everytime I go to close a project and open another , cubase crashes , giving me an error about an incorrect file name ...
Eh .. It seems iv gone back about 10 fold in terms of stability , and half the reason I bought the new one was to eliminate the random crashes, yet i havnt even begun yet and it keeps crashing ..
Is there something im missing ? was there some insiders only critical software update that i need to apply or something ? ..
Using:
Latest MOTU Ultralight Drivers
Cubase Studio 4.1 Build 749
Clean SOE Windows XP (Production Built OS - Only Audio Use)
#1
Posted 01 February 2008 - 10:58 PM
#2
Posted 01 February 2008 - 11:07 PM
Also , my audio device now shows up as "ASIO DIRECTX FULL DUPLEX DRIVER" yet in the ASIO setup I can see MOTU ultralight.. Theres no other options ...
Im sure it used to say Ultralight in SX3..
Im sure it used to say Ultralight in SX3..
#3
Posted 01 February 2008 - 11:11 PM
and its crashed again ... blank project , single instrument track impOscar ... crash
#4
Posted 02 February 2008 - 09:57 AM
damn dude, you having some serious bad luckage there...
my upgrade was flawless and i've only had 1 crash!
really wish i could help you bud... perhaps some conflicts onboard somewhere???
my upgrade was flawless and i've only had 1 crash!
really wish i could help you bud... perhaps some conflicts onboard somewhere???
#5
Posted 02 February 2008 - 10:09 AM
Yea, its been a bit rocky .. I did manage to fix some of the smaller stability problems , I removed a few demo VST's id been using , which seemed to help ... But iv still got plenty of other problems ..
I suppose the real test will be when I start from scratch on a new project ...
I suppose the real test will be when I start from scratch on a new project ...
#6
Posted 02 February 2008 - 01:39 PM
Synchrosoft drivers have to be updated along with the cubase update...welcome to the world of dongle protection
CS4 will only read VST 2.4 plug ins check your version numbers. but before you do that check for a file called vstblacklist.xml and remove any plug ins on that list .. move your plug in folder onto the desktop trash any preferences .. install the v 4.03 or what ever is on the DVD and run it barebones to start with ... see if it's stable then move your plug in folder back and select it as your 3rd party locale the restart cubase see if it crashes.. if it's stable then install the synchrosoft update then install the 4.1 update .. it's a process of elimination .. usually it's plug ins that cause issues ... another thing to try is renaming the rewire.dll to something else. the try to restart apparently rewire is giving a bit of grief according to the forums... when you select the asio driver does sound come out your ultralite? in the vst connections panel under the devices menu give you access to all your I/O ( press the + button to add ) might be a naming bug . have you got the latest drivers and what not?
try removing SX and see if that helps ( keep your preferences and song files in a safe place)
try here for help aswell http://forum.cubase....pic.php?t=82851
try removing SX and see if that helps ( keep your preferences and song files in a safe place)
try here for help aswell http://forum.cubase....pic.php?t=82851
#7
Posted 02 February 2008 - 02:01 PM
And thats why your the cubase mod
lol
Yea i started the process of elimination last night , I remembered doing that with SX2 a while ago .. It does appear to be a lot stabler now , although I can help but wonder why a single VST thats not even loaded into a project can cause the entire sequencer to become unstable , just by simply being on the file system.
I wasnt aware of any VST Black list though ?? thanks ill check for that ..
Rewire seems to work fine , I rewired Ableton 7 into a cubase project last night and played for a bit , although was unable to insert or use any VST's from the ableton project ... Only the cubase .. I cant remember if thats normal or not.. ( i dont rewire often )
In the VST connections , the actual device name (Audio Device Name) is shown as "ASIO DirectX Full Duplex" ... It used to say MOTU Ultrlight ..
Although , when I add new buses , I can see all my MOTU bus's .. so it IS working ... but I cant help but wonder if its setup wrong.
Aside from that , iv had a play with some of the new VST3 plugins , pretty cool .. and the HALionOne plugin that comes with CS4 is quite good .. The native side chaining is great too ... No more Side Kick for me ..
Iv removed SX3 , and its syncrosoft instance completely .. Im going to cull my VST's back a bit .. down to only my essentials ..
Yea i started the process of elimination last night , I remembered doing that with SX2 a while ago .. It does appear to be a lot stabler now , although I can help but wonder why a single VST thats not even loaded into a project can cause the entire sequencer to become unstable , just by simply being on the file system.
I wasnt aware of any VST Black list though ?? thanks ill check for that ..
Rewire seems to work fine , I rewired Ableton 7 into a cubase project last night and played for a bit , although was unable to insert or use any VST's from the ableton project ... Only the cubase .. I cant remember if thats normal or not.. ( i dont rewire often )
In the VST connections , the actual device name (Audio Device Name) is shown as "ASIO DirectX Full Duplex" ... It used to say MOTU Ultrlight ..
Although , when I add new buses , I can see all my MOTU bus's .. so it IS working ... but I cant help but wonder if its setup wrong.
Aside from that , iv had a play with some of the new VST3 plugins , pretty cool .. and the HALionOne plugin that comes with CS4 is quite good .. The native side chaining is great too ... No more Side Kick for me ..
Iv removed SX3 , and its syncrosoft instance completely .. Im going to cull my VST's back a bit .. down to only my essentials ..
#8
Posted 02 February 2008 - 02:16 PM
yes thats normal behavior in rewire only the host can use 3rd party plugs ... is the latency correct for the driver? in the asio device set up if it is then you have no probs it's just a naming bug ...
halion one is pretty cool for what it is beats owning a motif hey
i actually like prolouge alot .. the side chain is cool BUT it mutes the key track and you can only use vst 3 plugs which is a bit of a pain but i shouldn't complain too much at least we finally have it now..
vstblacklist is like AU validation in logic only it runs on startup. i guess the way the plugins are coded into the audio engine in C4 probably causes issues if they aren't up to scratch
halion one is pretty cool for what it is beats owning a motif hey
vstblacklist is like AU validation in logic only it runs on startup. i guess the way the plugins are coded into the audio engine in C4 probably causes issues if they aren't up to scratch
#9
Posted 02 February 2008 - 03:32 PM
Quote
the side chain is cool BUT it mutes the key track and you can only use vst 3 plugs which is a bit of a pain but i shouldn't complain too much at least we finally have it now..
?? How do you mean ... You mean it mutes the trigger track ? It didnt mute any tracks for me. I had 2 tracks , 1 drum , 1 bass .. I ran the compressor on the bassline as an insert , enabled side chain , then selected the sidechain as a send from the drum track ..
The bassline track was FabFilter Twin .. not VST3?.
#10
Posted 02 February 2008 - 03:50 PM
another question aswell , my x-station now has massive latency ... iv tried enabling system time stamping on MIDI but it only made it a little better , it still sucks ... Any suggestions where I should be looking for this ? .. the novation forums havnt been a whole lot of help ..
#11
Posted 02 February 2008 - 03:59 PM
yeah, my X25 has the same prob...
its fine when running with MIDI cables, but USB gets me almost 2 secs of latency
its fine when running with MIDI cables, but USB gets me almost 2 secs of latency
#12
Posted 02 February 2008 - 04:27 PM
hmmm ... i run a comp on a bass line using an audio channel as a key trig and it mutes the audio channel weird!!! i will look into this further ....the sidechain processor has to be VST 3 not the destination which means steinberg plugs only at the moment but the sdk has been launched so it wont be too long till it's available on a heap of plugs
cant help you on the novation front though
cant help you on the novation front though
#13
Posted 02 February 2008 - 08:18 PM
really ? .. that is wierd .. The sidechain worked like any other sidechain for me .. I used it in the same way I used Side kick .. I "sent" my signal though , it wasnt routed into it ... im assuming your doing the same ?
I like the sound of the VST3 format turning its self off when not in use
CT: 2 secs latency ?!?! how the hell do you use it ?? .. mines only milliseconds , but it still fucks you up when your trying to record lead MIDI ..
I like the sound of the VST3 format turning its self off when not in use
CT: 2 secs latency ?!?! how the hell do you use it ?? .. mines only milliseconds , but it still fucks you up when your trying to record lead MIDI ..
#14
Posted 04 February 2008 - 08:20 PM
Well after some hassles , it all seems to be working fine now ... no crashes , all drivers working ... Just took some serious toying around ...
So im back ... cubasing again , legally ... w00t for me ..
So im back ... cubasing again , legally ... w00t for me ..
#15
Posted 05 February 2008 - 04:21 PM
YAY!!!! 4.1.2 update is available now aswell
#16
Posted 05 February 2008 - 05:18 PM
I think thats the one I got .. I downloaded the latest as of last friday.
#17
Posted 06 February 2008 - 04:01 PM
new update available tuesday morning
#18
Posted 06 February 2008 - 04:28 PM
I just applied 4.1.2 last night ..
#19
Posted 12 February 2008 - 05:54 PM
i figured what i did wrong on my side chain issue i selected the actual track output as a key trigger not the auxillary :derrr:
#20
Posted 12 February 2008 - 07:09 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users



Back to top









