For me this workaround does not work.
Also with samples many random clicks are silent.
I really hope that this will be fixed soon, as I don’t want to create a Miditrack first and load an instrument for this.
The more that I work on my Vdrums with an computerkeyboard. The internal click I can switch of with that.
A miditrack with a vsti not.
I’ve never had the problem using samples… but that leads to another bewilderment: why don’t they include decent click samples with the program? I’ve imported my Urei click and other basic, industry standards from Digital Performer, which comes with them.
I couldn’t get samples to work and midi won’t work if you are using the studio headphone mixes. So far the only solution for me has been to turn off multi-processing, which seems to solve the problem. I believe I read this on the Cubase site?
Of course, without multi-processing I run higher CPU’s. I’m thinking I’ll turn off multi-processing when I start a piece, put in a metronome track with BFD, and as the piece demands more resources, turn on multi-processing again, relying on BFD for the click. I shouldn’t have to do this, folks!
For what is worth it appears that the latest Cubase 6.03 update has fixed the metronome problem for me. At least using .wav files. Since I don’t have Nuendo 5 (still on N3), I cannot verify if 5.5 has the same fix as well.
I stand corrected the problem is still there with Cubase 6.03 (and therefore I understand that it’s probably there with N5.5). In combination with the inability of the program to remember the VSTi assigned to MIDI click, I would say that the whole metronome portion of Cubendo is currently broken.
It is ultra-lame that there is no way to have the Nuendo/Cubase Click in an Audio-Mixdown.
How often I have to export playalongs from a roughmix for training or a playback version of the final mix for live, featuring keys or something AND a clicktrack… Surely as much as often as I export final mixes.
And I have to set up lame midi-tracks to route to the VSTi because there is no f*ckin way to include the damn internal click (even when genereated by a VSTi) in an audio-export. How shitty is that. This bugs me since years. Setting up a midi track can be nasty if you have truckloads of metric changes and you need click with an accentuated “one”. Otherwise it is fast…
The Cubendo-Click (even when used via a VSTi) is from very poor concept…
Yeap, I verified that in Nuendo 3 the buildin beep doesn’t skip beats.
It shouldn’t be that hard for Steinberg to track the metronome related changes between Nuendo 3 and 4. Come on this is too basic to be broken!
Great!! But its Not only a problem from latest version as well as there I’d a serious issue with “click to vsti” since a long time. Please fix that as well. And add a checkbox to include clickttack in audioexport!! thanks a lot!