105 great BUT?

[~+?]

The 105 update has fixed most of the sync problems for me and it?s a major improvement.

BUT some things I have noticed that are not right.
Things slip out of sync when changing patches, then it catches up again so not a major problem.

Not able to export my mix from cubaseSX without virus tracks loosing timing, even in real time export. I did not have this problem in the last O.S.! This is a major problem.. Am i the only one with this since 105?

Still no remote mode! I rather the bugs get fixed first... But are we going to get Remote mode for this?

[nutekk]

yes the remote mode was a major selling point for me.
hope it will be soon :twisted:

[marc]

The 105 update has fixed most of the sync problems for me and it?s a major improvement.

BUT some things I have noticed that are not right.
Things slip out of sync when changing patches, then it catches up again so not a major problem.

Not able to export my mix from cubaseSX without virus tracks loosing timing, even in real time export. I did not have this problem in the last O.S.! This is a major problem.. Am i the only one with this since 105?

Still no remote mode! I rather the bugs get fixed first... But are we going to get Remote mode for this?

hi,

which version of cubase do you use?

we consider the remote mode to be less important than fixing the bugs reported over the last week. i think 1.05 is a big step in the right direction and hopefully most of the problems are ironed out now.

best, marc
access music

[~+?]

Hi marc m8

It's CubaseSX version 3.0.2. I'm using RME multiface with a Polar and Virus control in cubase!

Agree bugs should be sorted before remote is implemented. But can you assure us that remote mode will be implemented into control in the near future?

Thanks for your reply,

8)

[ten]

You should update to SX 3.1.1. Its a LOT more stable than 3.0x and has a ton of fixes and tweaks that could make using the TI a lot better.

ten

[DIGITAL SCREAMS]

Was the Cubase update specifically to help the TI to integrate better? If so thats awesome collaboration.....

DS

[nutekk]

not!

[~+?]

Export worked ok for me before the 105 virus update.

[~+?]

Now its f.kd..

Its lost complete sync with cubase for some bizarre reason.
Closed down cubase reloaded it back up and all buffer settings latency settings changed. I can?t sync the virus at all now, even when I hit a key it takes 2 secs for the note to play. Reinstalled cubase and virus to see if it was that but its still all over the place. All this happened after I tried to export a mix without using real-time. It was all working fine before I did this. Now it?s all over the place and i have lost my buffer settings, what a mess. wtf happened?

:cry:

[ben crosland]

To get the buffer settings back, you might have to go into the Device Manager>Devices>VstAudiobay>Expert Panel first. The settings in here override the Application Priority settings in the ASIO control panel.

BTW - Why did you try exporting in non-realtime?

[~+?]

To get the buffer settings back, you might have to go into the Device Manager>Devices>VstAudiobay>Expert Panel first. The settings in here override the Application Priority settings in the ASIO control panel.

BTW - Why did you try exporting in non-realtime?


To see if the 105 update had fixed it!

Changing the buffer settings is not giving me any luck with latency now.

[ben crosland]

To get the buffer settings back, you might have to go into the Device Manager>Devices>VstAudiobay>Expert Panel first. The settings in here override the Application Priority settings in the ASIO control panel.

BTW - Why did you try exporting in non-realtime?


To see if the 105 update had fixed it!

I think if this was ever 'fixed' they'd make it pretty clear in the release notes! ;)

[ben crosland]

Changing the buffer settings is not giving me any luck with latency now.

Have you tried restarting your PC?

[DIGITAL SCREAMS]

Id shutdown the computer and do a hard boot.....its more likely to clear problems (dont ask my how or why)

DS

[~+?]

Well the other reason i tried on the fly export was that i was having no luck with real-time export with the 105 update, but i was able to real-time export with the 103 version!

Yeah rebooted, still no luck..

[ten]

BTW - Why did you try exporting in non-realtime?


To see if the 105 update had fixed it!

You do realise this will more than likely never be possible. The Virus creates the sound in realtime itself, so it cannot be mixed down in the quicker non-realtime mode because its only creating the sound in realtime....like you are recording it from the synth itself. Its not like a normal vsti where everything is calculated inside the computer.

ten

[~+?]

Yeah i know what ur saying dude. but the real-time export was not exporting in real-time its was a bit slower of time and the results came out the same. In 103 I did not have this problem so never needed to try on the fly export. I needed to share my mix with someone im working with over the net, so had no choice but give it a go.

[~+?]

In VST Audiobay my total input latency is 119.167ms and total output latency is 625.000ms.

Asio is showing I have 32 outputs from my RME Multiface now, wtf? :lol:

Just when I was starting to fall in love with it, this shit happens.
Is it only me or does shit like this only happen when you got something good going?

What can I do?

[ben crosland]

What can I do?

I'd start by re-installing some drivers..

[~+?]

I have reinstalled RME drivers and Virus drives and cubase. All i can think to do now is clean Asio from the reg, that or reinstall windows.

I'm a bit lost with what to try next now?

[ben crosland]

When you restarted your PC, did you actually power it down? I have found this can make a difference to how effective a reboot is - a normal restart just isn't enough sometimes.

[~+?]

Yep did a cold boot!

Now im not gettings any sound from the usb outs in control main outs. I have to change it's to outs 1 and 2 and the sound is all over the place!

Its well messed up. sounds like broken R2D2 8O and the bPM light on the Polar is flashing at warp speed captain, is she going to blow?

Is my Polar broke or do you think its my system?



:roll:

[~+?]

Good news.. i sussed it.

For some reason master {Asio driver) must have changed when i tried to export the mix on the fly rather than real-time export. Changed to Asio multimedia driver when it should have been Asio Hammerfull DSP driver!

Latency is back down to 6ms now :D

My hunch was right about the Asio at least.

Now i can get back to my Psy and beat the shit out of my Asio

:)

Thanks Ben for helping :D

Still drops out of time on real-time mixdown though?

[ben crosland]

Still drops out of time on real-time mixdown though?

Yes, I'm finding that mixdown in SX3 comes out 458 samples early. It is odd that this should be the case, as why would SX give different signals to the TI during mixdown, compared to playback?

[ben crosland]

Still drops out of time on real-time mixdown though?

Yes, I'm finding that mixdown in SX3 comes out 458 samples early. It is odd that this should be the case, as why would SX give different signals to the TI during mixdown, compared to playback?

OK - I think I've solved this.

Firstly, for whatever reason, I find that I get dropouts in SX3 unless I first go the the ASIO Control Panel, and re-apply the default settings.

These drop-outs, when they occur, will *always* make the arp run out of sync until the track is restarted. If the drop-out occurs during a silent section, it will pass unnoticed - it is in fact only the arpeggiator which will give you any clue that it happened!

Secondly, you need to put a pre-roll of at least a bar at the beginning of the sequence you wish to mixdown for the TI to get the information it requires for sample accuracy.

I had forgotten to do this!

Once I adressed these two points, I took a sample-accurate mixdown with both a 'normal' part and and arpeggiator. :)

[~+?]

Hi Ben,

Thats good news. Will have to give this a try.
Where do i find pre-roll in SX? do you mean Preload Amount in expert settings? or record placement offset? or is it in another place?

[ben crosland]

Hi Ben,

Thats good news. Will have to give this a try.
Where do i find pre-roll in SX? do you mean Preload Amount in expert settings? or record placement offset? or is it in another place?

I simply make sure that there is an empty bar at the beginning.

[~+?]

Yeah i did all that, but its still laggin on mixdown export.

[ben crosland]

Yeah i did all that, but its still laggin on mixdown export.

hmm.. strange. I'll look into it some more.

[ben crosland]

Have you checked Plug-in Information in the Devices menu?

Is 'Use Delay Compensation' checked for the Virus TI?

[ben crosland]

Actually, upon further investigation, I've been getting strange behaviour with SX3, too.

I set up a brand new project, and put down two tracks - one playing single notes, the other playing alongside, but with an arpeggiator instead.

Playback absolutely tight as.

Tried an Audio Mixdown - same.

Subsequent attempts however, were not - the arp did indeed play behind.

Every time I just play the sequence though, the timing is absolutely perfect.

I have to wonder whether this is something weird about SX, myself? It suggests to me that the midi clock signal is being affected by the export process.

[ten]

Strange, the arps seem a lot better for me since 1.05 using sx 3.1.1.

ten

[~+?]

Yep Use Delay Compensation is ticked for Virus TI and all other plugins. For virus TI it says under (Delay Sample) 2560. dont know if that?s relevant or not?

[~+?]

Actually, upon further investigation, I've been getting strange behaviour with SX3, too.

I set up a brand new project, and put down two tracks - one playing single notes, the other playing alongside, but with an arpeggiator instead.

Playback absolutely tight as.

Tried an Audio Mixdown - same.

Subsequent attempts however, were not - the arp did indeed play behind.

Every time I just play the sequence though, the timing is absolutely perfect.

I have to wonder whether this is something weird about SX, myself? It suggests to me that the midi clock signal is being affected by the export process.


I have the exact same symptoms with my Polar as Ben!

[ben crosland]

For the record, a comparative test in Logic 5.5.1 showed no such anomalies.

Arp remained perfectly in time during multiple exports.

[ben crosland]

Strange, the arps seem a lot better for me since 1.05 using sx 3.1.1.

ten

Same here - the arps are spot on during playback. SX3 must be doing something strange with the midi clock during export, if you ask me. Non-arpeggiated sounds are just as tight during export as playback - it's only the arps, which rely on midi clock to stay in sync.

[~+?]

Been using Cubase since version 1 back on the Atari. I would be a bit lost if I had to change to logic now. Midi clock is loosing sync on SX3 for sure but there must be a reason? find the reason and the fix cant be far.

[ben crosland]

Been using Cubase since version 1 back on the Atari. I would be a bit lost if I had to change to logic now. Midi clock is loosing sync on SX3 for sure but there must be a reason? find the reason and the fix cant be far.

No - I wasn't suggesting you change to Logic. TBH that would be crazy unless you went to Mac, as it is unsupported on the PC.

I mentioned it simply because the fact that there is no difference in arp sync between playback and export (or bounce as it is called in Logic) suggests that the problem most likely lies with SX3 itself and not with the TI.

At any rate, wherever the problem lies, we can only wait while it is addressed by whomever is responsible.

In the meantime - how about a workaround? :)

Since it looks to me like the arp offset is pretty consistent, I would suggest for now that you export the arp track(s) separately, and then realign them with the rest of the mix afterwards.

[~+?]

Well at least we can work around it for now; this was not possible in v103 it sounds like a fixable problem. BTW does access sell wooden sides for the Polar? :P Wooden and more flush with the keys would be good. like on moogs, more protection for the keys!

[grs]

Been using Cubase since version 1 back on the Atari. I would be a bit lost if I had to change to logic now. Midi clock is loosing sync on SX3 for sure but there must be a reason? find the reason and the fix cant be far.

No - I wasn't suggesting you change to Logic. TBH that would be crazy unless you went to Mac, as it is unsupported on the PC.

I mentioned it simply because the fact that there is no difference in arp sync between playback and export (or bounce as it is called in Logic) suggests that the problem most likely lies with SX3 itself and not with the TI.

At any rate, wherever the problem lies, we can only wait while it is addressed by whomever is responsible.

In the meantime - how about a workaround? :)

Since it looks to me like the arp offset is pretty consistent, I would suggest for now that you export the arp track(s) separately, and then realign them with the rest of the mix afterwards.

Just use a recording plug in the main outputs, ie voxengo recorder - free.
If your forced to do real time exports anyway why not just do that. It would be 1 to 1 the same thing.

[Midi_Glider]

I mentioned it simply because the fact that there is no difference in arp sync between playback and export (or bounce as it is called in Logic) suggests that the problem most likely lies with SX3 itself and not with the TI.

Well, in the end, its still most likely a Ti problem. numerous VST`is I use (such as Reaktor) relay on receiving a precise midi clock from the sequencer while bouncing different internal arps and sequences. and they all do it with sample accurate precision...

Best,
midi.

[guyur]

One thing I just recently noticed and I can't believe I didn't notice it before, but that strange static type noise I've reported in other posts coincides with the BPMs. Increase the tempo...increase the static rate. For whatever that was worth... :?

[~+?]

This is from the Access site!

"Thanks to Access? proprietary driver technology the VIRUS becomes the first hardware synthesizer with sample-accuracy timing with a delay-compensated audio/MIDI connection to your favourite software sequencer. Forget about sloppy arpeggiators and basses you can?t decide are playing before or behind the beat.
Sound editing and management has never been easier."

Thats what we all paid for. Hurry up Access and fix it please :roll:

[blay]

Secondly, you need to put a pre-roll of at least a bar at the beginning of the sequence you wish to mixdown for the TI to get the information it requires for sample accuracy.

Took me a little while but I had already sussed this out - it helps but it certainly doesnt fix the problem...