Cannot export midi as audio in Cubase 5 - serious errors

[achintya]

Hi

Oh oh... my first major problem with Cubase 5. I am trying to export to audio a midi track with a bass line that is reading from Trilogy, a VST instrument. In Cubase 4.* I have exported many bass lines using this VST and never had a problem.

In Cubase 5, at various points in the export process, sometimes near the beginning and sometimes near the end, the transport bar freezes up, the cursor jumps to a random place in the midi track, and I get the error message "Disk Overload Occurred during the export".

I have 38gb space on my hard disk, and it has never posed any speed or capacity problems before?

I tried an alternative hard disk on my PC, same error

I tried not inserting XML Chunk, not using extensible format, same error

I tried importing into project (presumably not recording to disk???), same error

I tried exporting just a small part of the midi track, same error

I have noticed, when everything freezes, my 6 minute piece of music is given a running time of 12h 22m remaining!

I am unable, currently to export any midi files to audio

I am export using Stereo Out.

Just tried to change the bit rate to 16 bits and a very short piece of bass midi exported ok. Tried the whole track, same error.

Then, when I tried to save the project, got the famous 'going to save as backup, system in unstable state'.

Have not had that error message for months.

I cannot export Midi as Audio from Cubase 5


Serious glitch here, so any help would be appreciated.



achintya
_________________
PaQ 5U-560 case inc 500W PSU, CPU cooler
and case fans etc.
Gigabyte EX58-UD4P Intel i7 920
6GB (3x2GB) Corsair XMS3 DDR3, (1600MHz)
3 x 1TB Samsung HD103UJ Spinpoint F1, SATA 3Gb/s, 7200 rpm
512MB Palit 9500 GT, PCI-E 2.0 (x16),
Pioneer DVR-216DBK
Microsoft Windows Vista
Home Premium SP1* 64Bit
RME HDSP 9632

[achintya]

quick update: I went out of Cubase after 'unstable condition etc message' and managed to get a midi export by turning off Real Time monitoring?

I will try again with Real Time on again later, to see if there was an 'unstable state' somehow and if everything is ok. Just lost 2 hours of recording time, so need to press on, even if it means not being able to hear the export live.

But I think something is amiss....


ac

[quote="achintya"]Hi

Oh oh... my first major problem with Cubase 5. I am trying to export to audio a midi track with a bass line that is reading from Trilogy, a VST instrument. In Cubase 4.* I have exported many bass lines using this VST and never had a problem.

In Cubase 5, at various points in the export process, sometimes near the beginning and sometimes near the end, the transport bar freezes up, the cursor jumps to a random place in the midi track, and I get the error message "Disk Overload Occurred during the export".

I have 38gb space on my hard disk, and it has never posed any speed or capacity problems before?

I tried an alternative hard disk on my PC, same error

I tried not inserting XML Chunk, not using extensible format, same error

I tried importing into project (presumably not recording to disk???), same error

I tried exporting just a small part of the midi track, same error

I have noticed, when everything freezes, my 6 minute piece of music is given a running time of 12h 22m remaining!

I am unable, currently to export any midi files to audio

I am export using Stereo Out.

Just tried to change the bit rate to 16 bits and a very short piece of bass midi exported ok. Tried the whole track, same error.

Then, when I tried to save the project, got the famous 'going to save as backup, system in unstable state'.

Have not had that error message for months.

I cannot export Midi as Audio from Cubase 5


Serious glitch here, so any help would be appreciated.



achintya[/quote]
_________________
PaQ 5U-560 case inc 500W PSU, CPU cooler
and case fans etc.
Gigabyte EX58-UD4P Intel i7 920
6GB (3x2GB) Corsair XMS3 DDR3, (1600MHz)
3 x 1TB Samsung HD103UJ Spinpoint F1, SATA 3Gb/s, 7200 rpm
512MB Palit 9500 GT, PCI-E 2.0 (x16),
Pioneer DVR-216DBK
Microsoft Windows Vista
Home Premium SP1* 64Bit
RME HDSP 9632

[vic_france]

Try increasing the buffer size?
_________________
Cubase 5.1.1 | Cubase 4.5.2 | SX3.1.1 | Mac OSX 10.6.4 and 10.5.8 | Mac Quad-Core 2.66gHz | 6GB RAM | MOTU PCI-424/2408mk3 | MOTU MidiTimepice AV

[achintya]

just about maxed out on buffer size...

would my PC processor limitation be a problem?

Processor Intel(R) Pentium(R) 4 CPU 3.00GHz, 2992 Mhz, 1 Core(s), 1 Logical Processor(s)

???


ac

[quote="vic_france"]Try increasing the buffer size?[/quote]
_________________
PaQ 5U-560 case inc 500W PSU, CPU cooler
and case fans etc.
Gigabyte EX58-UD4P Intel i7 920
6GB (3x2GB) Corsair XMS3 DDR3, (1600MHz)
3 x 1TB Samsung HD103UJ Spinpoint F1, SATA 3Gb/s, 7200 rpm
512MB Palit 9500 GT, PCI-E 2.0 (x16),
Pioneer DVR-216DBK
Microsoft Windows Vista
Home Premium SP1* 64Bit
RME HDSP 9632

[MasterT]

I got the same problem here!

As I tried to export a piece, completely with midi files, I also got the error message "Disk Overload Occurred during the export".
Then, after a few more tries, cubase actually started exporting the song, but first stopped with a crash of cubase and after a second try, it stopped with the error message "CPU Overload".
In Cubase 4, I NEVER had this problem. I was able to export the exact same song, with no problems whatsoever.

Please - how can I solve that?!

[achintya]

Hi

It is supportive to know I am not alone in this frustration. I 'solved' it temporarily by switching off 'Real Time Export' and for some reason this allowed the midi to export as audio. Another post here suggests buffer size increase, but I am maxed out.

So it may just come down to the fact that Cubase 5 needs quite a bit more CPU power than we were expecting?

God knows what would happen if I tried to export a WHOLE SONG... the computer would probably melt and become a little blob of silver mercury on the floor?

I sympathise, and hope we get some suggestions here? I suspect we are going to get a load more folk saying they are experiencing the same problem.

Cubase 5.01 here we come?


achintya

[quote="MasterT"]I got the same problem here!

As I tried to export a piece, completely with midi files, I also got the error message "Disk Overload Occurred during the export".
Then, after a few more tries, cubase actually started exporting the song, but first stopped with a crash of cubase and after a second try, it stopped with the error message "CPU Overload".
In Cubase 4, I NEVER had this problem. I was able to export the exact same song, with no problems whatsoever.

Please - how can I solve that?![/quote]
_________________
PaQ 5U-560 case inc 500W PSU, CPU cooler
and case fans etc.
Gigabyte EX58-UD4P Intel i7 920
6GB (3x2GB) Corsair XMS3 DDR3, (1600MHz)
3 x 1TB Samsung HD103UJ Spinpoint F1, SATA 3Gb/s, 7200 rpm
512MB Palit 9500 GT, PCI-E 2.0 (x16),
Pioneer DVR-216DBK
Microsoft Windows Vista
Home Premium SP1* 64Bit
RME HDSP 9632

[musicsound]

I have got the "Disk Overload Occurred during the export" message as well. However during the second try to export, no message and no problems.
_________________
i7 920, Gigabyte X58-UD5, 3 * 2GB RAM, Gainward GeForce 9400 GT passiv, XP32 Pro SP3, Cubase 5, Wavelab 5.01b, UAD-2 Quad, TC Powercore MKII, Duende FW, MOTU 424 PCI audio card + HD192, 1296, 308 interface, Isochrone OCX, Lavry Blue

[Beryliam]

The Dell 8400 is 5 years old which is fairly long in the tooth for using with powerful DAWs and I think you may have been lucky or very skillful to get C4 working without problems on it. The usual computer life is typically about 2 to 3 years when using any highly strung programs as the annual / bi-annual rewrites always take advantage of the latest processors available. There are exceptions but not that many. The trade-off with writing for the latest or even future computers is that older platforms will suffer in some way in most cases.
I'm using a Core 2 Duo but I'm expecting a wallet battering sometime in the next year if the updates go the way I think they are. Bugger!

[achintya]

Hi

You have confirmed what I suspected, thanks for your comments. I have had burp and fart problems with Cubase since 4.0 came out, and didn't with 3.0, so I guess if must be PC related?

What would you suggest as a really good spec to run Cubase; I was thinking of going over to a high spec MAC PRO, most of my VST software is compatible, but happy to invest in a really good PC. Can you suggest an ideal specification re. CPU, processor, graphic card, internal sound card etc?


ac

[quote="Beryliam"]The Dell 8400 is 5 years old which is fairly long in the tooth for using with powerful DAWs and I think you may have been lucky or very skillful to get C4 working without problems on it. The usual computer life is typically about 2 to 3 years when using any highly strung programs as the annual / bi-annual rewrites always take advantage of the latest processors available. There are exceptions but not that many. The trade-off with writing for the latest or even future computers is that older platforms will suffer in some way in most cases.
I'm using a Core 2 Duo but I'm expecting a wallet battering sometime in the next year if the updates go the way I think they are. Bugger![/quote]
_________________
PaQ 5U-560 case inc 500W PSU, CPU cooler
and case fans etc.
Gigabyte EX58-UD4P Intel i7 920
6GB (3x2GB) Corsair XMS3 DDR3, (1600MHz)
3 x 1TB Samsung HD103UJ Spinpoint F1, SATA 3Gb/s, 7200 rpm
512MB Palit 9500 GT, PCI-E 2.0 (x16),
Pioneer DVR-216DBK
Microsoft Windows Vista
Home Premium SP1* 64Bit
RME HDSP 9632

[MasterT]

Okay, I'm getting frustrated. This problem still exists here! I run Cubase 5 64bit on Vista 64bit - I have a Quad Core, 8GB Ram, RME Fireface 400 ... there should be no problems with that hardware...
Just to let you guys know, what I want to export: It's a big orchestral piece entirely made with East West / Quantum Leap Symphonic Orchestra Platinum PLAY.

Please help!

[vic_france]

As a workaround, instead of exporting, why don't you take advantage of the free routing available since Cubase 4.1? Just create a new stereo audio track, and set your main outputs as its input (remembering of course not to route this new track to the main outputs!), and put that track into Record.
_________________
Cubase 5.1.1 | Cubase 4.5.2 | SX3.1.1 | Mac OSX 10.6.4 and 10.5.8 | Mac Quad-Core 2.66gHz | 6GB RAM | MOTU PCI-424/2408mk3 | MOTU MidiTimepice AV

[lanter]

[theblindpew]

[achintya]

Thanks for all the recommendations to get around this continual problem.

My solution so far, aside from clicking a few times and going in and out of Cubase a few times, is to turn off Real Time Export. This has, on my system, resulted in perfect export each time, short and long tracks, but I have yet to try to export a complete audio track.

I appreciate the 'non-workaround workaround' which depends on having external hardware, which I don't, unless I have misunderstood what is being recommended?

It does seem a tad retro that a new version of Cubase makes it impossible to do something pretty simple, like export a midi track as an audio track using real time export, and then getting these kinds of error messages, when CB 4.* and probably earlier did it without a hitch?

I appreciate the suggestions, but so far there has been no Steinberg acknowledgment that this may be a bug, which judging from how many of us so far have experience this, and some with very high spec PCs, which negates the hardware cause mentioned in another email in this thread. I was actually freaked out enough to contact P&Q systems recommended in a number of the threads in the hardware section of this forum, http://www.paqt.co.uk I have been really impressed with Peter's very long and very expert response to my request for specifications he would recommend for a good audio PC. He specialises in 'quiet cases' but seems to build very good audio PCs also. And not a bad quote either. But I would rather not have to spend £2k or so on a new PC, if actually the problem is just a glitch in the software. The fact that people with high spec PCs are getting the same problem does seem to indicate.

Any more advice, thoughts etc. It is ok bouncing down without Real Time Export, but I still feel a bit short changed after being able to do this simple operation seamlessly in CB 4.* for years.

As a matter of interest I am also noticing that bouncing midi down to midi takes AGES longer in CB 5 than CB4. And also, the screen menu's during bounce down don't fully display during the process, at least on my PC. I am, in the back of my head, relating this to the fact that when I turn off Real Time Export to get midi to audio to work, then of course the screen stops moving.

I wonder if this is related to some kind of clash with the video card in both cases? Somehow the Video card is causing the CB 5 software to have a spasm and issue an error mesage and crash? Just a thought.

I have, for a long time, been noticing that a lot of my burps and farts playing on playback and recording in CB often coincided with movements of sliders and menus on screen and that something is amiss in how CB is speaking to my video card?


achintya



[quote="theblindpew"][quote]I have got the "Disk Overload Occurred during the export" message as well. However during the second try to export, no message and no problems.
_________________[/quote]

I am exactly the same here. Brand new computer, plenty of power, plenty of ram and hard drive space. Says that frist time, click again and it's fine.

Good to know I'm not the only one. Hopefully someone from Steinberg will acknowledge this.

Andrew[/quote]
_________________
PaQ 5U-560 case inc 500W PSU, CPU cooler
and case fans etc.
Gigabyte EX58-UD4P Intel i7 920
6GB (3x2GB) Corsair XMS3 DDR3, (1600MHz)
3 x 1TB Samsung HD103UJ Spinpoint F1, SATA 3Gb/s, 7200 rpm
512MB Palit 9500 GT, PCI-E 2.0 (x16),
Pioneer DVR-216DBK
Microsoft Windows Vista
Home Premium SP1* 64Bit
RME HDSP 9632

[lanter]

[vic_france]

[achintya]

This is nudging the edges of my expertise, so going into stunned rabbit mode when reading this.

I have a midi track I want to export to audio, and currently if I export it with Real Time Export switched on, I am getting the error message 'disk overload etc'

I have control room set up with Output, Input and Studio/monitor all set up for my soundcard, which is being drivern by AsioforAll, latest version as I can't get my Edirol external sound card driver to install.

So can you just give me step by step what I need to set up this alternative method of getting the midi track onto my PC as an audio track, and hopefully being able to monitor in headphones?

thanks


ac

[quote="lanter"][quote]I appreciate the 'non-workaround workaround' which depends on having external hardware, which I don't, unless I have misunderstood what is being recommended? [/quote]
Does not depend on external hardware, rather realtime export or record on track is the only option when one uses external stuff.
That does not mean that it not an option when not using external hardware.
Just create an audio track and set its input to record from your main out, as Victor said, and see what it will do...[/quote]
_________________
PaQ 5U-560 case inc 500W PSU, CPU cooler
and case fans etc.
Gigabyte EX58-UD4P Intel i7 920
6GB (3x2GB) Corsair XMS3 DDR3, (1600MHz)
3 x 1TB Samsung HD103UJ Spinpoint F1, SATA 3Gb/s, 7200 rpm
512MB Palit 9500 GT, PCI-E 2.0 (x16),
Pioneer DVR-216DBK
Microsoft Windows Vista
Home Premium SP1* 64Bit
RME HDSP 9632

[Beryliam]

This looks the way to go for a few years: http://3xs.scan.co.uk/images/awards/PowerDAW_SoundOnSound.pdf

[lanter]

[achintya]

HI

Thanks for your help here

Can I check something out (then I am going to try this out)... will this produce a wav copy of the recording on my hard disk which I can use to burn to CD etc.?

If not, then I am still in the same boat, as I will need to export the audio track, and currently cannot do that?


ac

[quote="lanter"][quote="achintya"]This is nudging the edges of my expertise, so going into stunned rabbit mode when reading this.

I have a midi track I want to export to audio, and currently if I export it with Real Time Export switched on, I am getting the error message 'disk overload etc'

I have control room set up with Output, Input and Studio/monitor all set up for my soundcard, which is being drivern by AsioforAll, latest version as I can't get my Edirol external sound card driver to install.

So can you just give me step by step what I need to set up this alternative method of getting the midi track onto my PC as an audio track, and hopefully being able to monitor in headphones?[/quote]

OK, assuming your main output [i]channel[/i] is called 'Main Output'
- create an audio track
- in inspector, select 'Main Output' as the input for the track, set output to none.
- record enable track and press record to record your complete project to that track (or solo any channel you want to record seperately first)
- recording done, set input of track to none, now you can select 'Main Output' as its output
- solo the audio track to listen to the result[/quote]
_________________
PaQ 5U-560 case inc 500W PSU, CPU cooler
and case fans etc.
Gigabyte EX58-UD4P Intel i7 920
6GB (3x2GB) Corsair XMS3 DDR3, (1600MHz)
3 x 1TB Samsung HD103UJ Spinpoint F1, SATA 3Gb/s, 7200 rpm
512MB Palit 9500 GT, PCI-E 2.0 (x16),
Pioneer DVR-216DBK
Microsoft Windows Vista
Home Premium SP1* 64Bit
RME HDSP 9632

[achintya]

Hi

In Control Room, my 'main mix' output is called Stereo Out. I have clicked above the fader in my Audio Channel and in the input section, see a list of choices:

No Bus
In 1
Stereo In
Groups
Fx
Outputs >>>> Bus 1 and Stereo Out (but this is greyed out)

I have changed my main mix to Bus 1 as the Stereo Out I usually use is greyed out, and this is available as a choice in the Inspector, so I have chosen that.

My midi channel is set up linked to the VST I am using, and is Solo'd ready to play.

I have armed and solo'd my audio channel for record and solo'd my midi channel for output. I have stayed in the audio channel and started to record.

When the midi starts playing, I can hear it in my earphones, but nothing is being recorded to the track, although a 'blank' recording is made?

Seems I have not done something?

any thoughts?


ac



[quote="lanter"][quote="achintya"]This is nudging the edges of my expertise, so going into stunned rabbit mode when reading this.

I have a midi track I want to export to audio, and currently if I export it with Real Time Export switched on, I am getting the error message 'disk overload etc'

I have control room set up with Output, Input and Studio/monitor all set up for my soundcard, which is being drivern by AsioforAll, latest version as I can't get my Edirol external sound card driver to install.

So can you just give me step by step what I need to set up this alternative method of getting the midi track onto my PC as an audio track, and hopefully being able to monitor in headphones?[/quote]

OK, assuming your main output [i]channel[/i] is called 'Main Output'
- create an audio track
- in inspector, select 'Main Output' as the input for the track, set output to none.
- record enable track and press record to record your complete project to that track (or solo any channel you want to record seperately first)
- recording done, set input of track to none, now you can select 'Main Output' as its output
- solo the audio track to listen to the result[/quote]
_________________
PaQ 5U-560 case inc 500W PSU, CPU cooler
and case fans etc.
Gigabyte EX58-UD4P Intel i7 920
6GB (3x2GB) Corsair XMS3 DDR3, (1600MHz)
3 x 1TB Samsung HD103UJ Spinpoint F1, SATA 3Gb/s, 7200 rpm
512MB Palit 9500 GT, PCI-E 2.0 (x16),
Pioneer DVR-216DBK
Microsoft Windows Vista
Home Premium SP1* 64Bit
RME HDSP 9632

[lanter]

[achintya]

I usually use the default 24 bit, not comfortable about compromising the quality of the recording from midi? I guess it will make quite a difference as I usually process the results for CD recordings?

Where would the recordings be stored?


ac

[quote="lanter"][quote]will this produce a wav copy of the recording on my hard disk which I can use to burn to CD etc.? [/quote]
If you recorded 44.1 kHz, 16 bit, yes.[/quote]
_________________
PaQ 5U-560 case inc 500W PSU, CPU cooler
and case fans etc.
Gigabyte EX58-UD4P Intel i7 920
6GB (3x2GB) Corsair XMS3 DDR3, (1600MHz)
3 x 1TB Samsung HD103UJ Spinpoint F1, SATA 3Gb/s, 7200 rpm
512MB Palit 9500 GT, PCI-E 2.0 (x16),
Pioneer DVR-216DBK
Microsoft Windows Vista
Home Premium SP1* 64Bit
RME HDSP 9632

[lanter]

First set the output of the audio track to NONE!
Else you will not be able to choose it as an input, a track set to the same in and out would create a loop, that is why it is greyed out!!!
_________________
Jan

MIDI Timing problems?
C5.5, WL7 , XP Pro SP2, NI VSTi's
P5WD2 Premium, P D940, 2Gb, PNY Quadro NVS 290 PCIex16, 2x UAD-1, 2x UAD-2 Solo, MOTU 828mk3, Layla24, RME ADI 4-DD, Midisport 8x8s
Alphatrack, Outboard MIDI & FX

[achintya]

I did that, and got the option for Stereo Out, which I selected.

I armed my audio track and solo'd my midi track with a short bit of vibes on it, for testing.

I stayed on my audio track and started the recording. I heard the vibes in my earphones, but nothing is showing on the recorded track?

any thoughts?


ac

[quote="lanter"]First set the output of the audio track to NONE!
Else you will not be able to choose it as an input, a track set to the same in and out would create a loop, that is why it is greyed out!!![/quote]
_________________
PaQ 5U-560 case inc 500W PSU, CPU cooler
and case fans etc.
Gigabyte EX58-UD4P Intel i7 920
6GB (3x2GB) Corsair XMS3 DDR3, (1600MHz)
3 x 1TB Samsung HD103UJ Spinpoint F1, SATA 3Gb/s, 7200 rpm
512MB Palit 9500 GT, PCI-E 2.0 (x16),
Pioneer DVR-216DBK
Microsoft Windows Vista
Home Premium SP1* 64Bit
RME HDSP 9632

[lanter]

Is the VSTi audio channel routed to the Stereo Out?
_________________
Jan

MIDI Timing problems?
C5.5, WL7 , XP Pro SP2, NI VSTi's
P5WD2 Premium, P D940, 2Gb, PNY Quadro NVS 290 PCIex16, 2x UAD-1, 2x UAD-2 Solo, MOTU 828mk3, Layla24, RME ADI 4-DD, Midisport 8x8s
Alphatrack, Outboard MIDI & FX

[achintya]

In VST Connections, Output, I have Bus 1 set up and Stereo Out, and Stereo Out is set as 'main mix' if this is what you mean?

I have Control Room set up, so I can monitor my playbacks etc. I tried disabling that, just in case it was effecting anything, but no recording was made.


ac



[quote="lanter"]Is the VSTi audio channel routed to the Stereo Out?[/quote]
_________________
PaQ 5U-560 case inc 500W PSU, CPU cooler
and case fans etc.
Gigabyte EX58-UD4P Intel i7 920
6GB (3x2GB) Corsair XMS3 DDR3, (1600MHz)
3 x 1TB Samsung HD103UJ Spinpoint F1, SATA 3Gb/s, 7200 rpm
512MB Palit 9500 GT, PCI-E 2.0 (x16),
Pioneer DVR-216DBK
Microsoft Windows Vista
Home Premium SP1* 64Bit
RME HDSP 9632

[lanter]

No, that is not what I mean.
Your Trilogy is using a VSTi audio channel. This is routed to somewhere, check that.

And what is your Bus 1 for?
_________________
Jan

MIDI Timing problems?
C5.5, WL7 , XP Pro SP2, NI VSTi's
P5WD2 Premium, P D940, 2Gb, PNY Quadro NVS 290 PCIex16, 2x UAD-1, 2x UAD-2 Solo, MOTU 828mk3, Layla24, RME ADI 4-DD, Midisport 8x8s
Alphatrack, Outboard MIDI & FX

[achintya]

Hi

Thanks for staying with me on this. The Bus has always been there, can it cause a problem?

I am using a Kompakt screen running Eastwest Symphonic Orchestra, and am seeing no routing options in it.

It is connected to my midi channel, and the Input is set for All Midi, and my output routing is set for the Kompakt VST, which has to be in order for the midi notes to play the orchestra?

Not sure sure else to look, unless there is another midi setting I have missed? Is there anywhere else to look for the VST Audio Channel?


ac

[quote="lanter"]No, that is not what I mean.
Your Trilogy is using a VSTi audio channel. This is routed to somewhere, check that.

And what is your Bus 1 for?[/quote]
_________________
PaQ 5U-560 case inc 500W PSU, CPU cooler
and case fans etc.
Gigabyte EX58-UD4P Intel i7 920
6GB (3x2GB) Corsair XMS3 DDR3, (1600MHz)
3 x 1TB Samsung HD103UJ Spinpoint F1, SATA 3Gb/s, 7200 rpm
512MB Palit 9500 GT, PCI-E 2.0 (x16),
Pioneer DVR-216DBK
Microsoft Windows Vista
Home Premium SP1* 64Bit
RME HDSP 9632

[vic_france]

(I am merely going to repeat what Jan is saying here, but maybe just reading it, worded differently, may help. Just follow the instructions, add nothing else of your own! )..
You don't need to worry about your VST connections, nor about the Control Room.
Before trying to bounce, when you play Cubase, you can hear your VSTi, yes? It is currently routed to "Stereo Out" (which happens to be the output that feeds the Control Room, although that is not important here).
So, create a new Audio channel (let's call it "Bounce"), and, set its input to "Outputs>Stereo Out". Set the "Bounce" channel's output to "No Bus" (or in fact to any other output than Stereo Out). Now all you should need to do is set the Project cursor to the start of where you wish to record, and put "Bounce" into Record (solo the VSTi if you wish). When you've finished, route "Bounce" to Stereo Out, solo it, and you should hear it.
_________________
Cubase 5.1.1 | Cubase 4.5.2 | SX3.1.1 | Mac OSX 10.6.4 and 10.5.8 | Mac Quad-Core 2.66gHz | 6GB RAM | MOTU PCI-424/2408mk3 | MOTU MidiTimepice AV