Mayor Cubase 5 issues [Unsolved]

[HostileReality]

Originally Posted by L.F.

and it appears some of my older SX3 projects using the Ti are not compatible with cubase 5.
I've Also noticed one other alarming Ti Bug; when reopening a cubase project file my Ti filter envelope sometimes resets to zero. Same thing sometimes happens to the cutoff..
I've checked cubase automation and it's off. So it's not supposed to move..

hey i'm also using cubase 5 and with songs from SX3, all my songs were made on sx3. So far i havnt' got that far with the whole process of installing the software and getting everything working, because i'm having this issue which sound quite similar to yours. Actualy i have been contactin access support about the issue, but the confusing thing is that they say that it doesnt happen with 2.7.5, but for me it does. I have tried the newer betas aswell. So thats odd. but from the description it sounds like the same problem, that is:

Certain patches, their cuttoff and filter env settings will change slightly when i save cubase and reopen it. So when i open the song, i see that the cuttoff and filter env has changed, and i have to reload the patch from off of the virus. However they arnt resetting to zero like you said, rather for me they just change to a differnt setting ( though that number seems to allways be the same each time) but it is only the filter 1 cuttoff, and filter 1 env, and also just on one of my patches ( i've found 4 which are doing this), the key flw changes.

So does this happen on all your patches? or just certain ones like mine seems to?

example of mine:

patch 1:
filter1 original: changes to:
env amount: 0 73
reso: 17 29

patch 2:
filter1 original: changes to:
env amount: 29 84
reso: 83 65


the other thing that you mentioned which im curious about... you said that certain SX3 songs arn't compatable with cubase 5? could you please explain that more.. so far i've only tried 2 or 3 songs.

Im on windows vista, and have reinstalled everything. so all my SX3 songs came from a hard drive with xp installed.

[L.F.]

Originally Posted by HostileReality

So does this happen on all your patches? or just certain ones like mine seems to?

example of mine:

patch 1:
filter1 original: changes to:
env amount: 0 73
reso: 17 29

patch 2:
filter1 original: changes to:
env amount: 29 84
reso: 83 65

I've noticed a similar thing happening to me. Usually, only the filter cutoff of just one of the virus channels resets it's filter envelope to zero. Unfortunately, on rare occasions it can happen to more than one patch, but AFAIK it's always cutoff or envelope. Nothing else.

the other thing that you mentioned which im curious about... you said that certain SX3 songs arn't compatable with cubase 5? could you please explain that more.. so far i've only tried 2 or 3 songs.

Im on windows vista, and have reinstalled everything. so all my SX3 songs came from a hard drive with xp installed.

I've got 2-3 tracks which either crash the cubase 5 on startup or shortly after... And I have no idea what could be causing this.
Most SX3 projects work, however.

You should try the '3gb switch'. I think it might help you hear. I don't know exactly, but without it, cubase may only be able to use 1.5 gb, and with it 2.5 or so.. something like that. But either way it works for me. just google for 'how to add /3gb switch xp' for example.

I had no idea about this.. never thought I'd need to worry about ram
Just hope it won't cause any problems with my raid 0 array..
I'll look it up. Thanks

[HostileReality]

It shouldnt cause any issues. deffainlty give it a go! i think a lot of people use this on DAW's. it works on vista 32bit aswell.

[L.F.]

still having the same problem

Originally Posted by HostileReality

It shouldnt cause any issues. deffainlty give it a go! i think a lot of people use this on DAW's. it works on vista 32bit aswell.

I've got a GPU problem when using the /3GB switch. It's sort of like before you install your gpu; the picture is there but moving/opening windows is very sluggish. I even upgraded to 4GB od ddr2 ram in the hope that might help... but still having the same problem.