Quote:
Originally Posted by richiebee  Is it writing the MIDI data in Cubase accurately?
If its only a monitoring issue, I would turn off the monitoring of the track you're recording (you can do this in the track inspector), and be done with it. If its not writing the data correctly in Cubase, you need to take it further.
Have you tried re-starting your computer/Cubase and try starting a new project?
Is it a desktop or laptop computer? Do you know how fast the hard drive spins? I don't suspect that has anything to do with your problem here, but its handy to know. |
Thanks for your reply.
Ok, the way I'm monitoring is the line out from my keyboard is going into the mixer then straight out to my monitors without any sound going into Cubase (unless I press Alt 3-4 for recording)
I followed your advice and shut down Cubase, opened it up and started a new project. I started a loop again and the problem soon showed itself. I tried my best to ignore the delay and hit some beats, these recorded fine and in the right place. So the Midi in is fine, it's the Midi out triggering the sound on the Triton that's late. The problem with that is why does pre recorded Midi out events trigger the sounds in the Triton ok? It's only the live keyboard presses that are late. A problem somewhere with the settings of my Triton maybe? But I've checked everything I can think of. Besides, it's one of those confusing intermittent faults. Sometimes it's fine.
I thought of a dodgy Midi cable, but there again, the midi out from Cubase carries the pre recorded data fine....always.
This hurts my brain, I hate intermittent problems!
My PC is a desktop, and my HD are 7200rpm.
Many thanks.