Hi All,
ok, this is really a frustrating problem, it happend to me many years ago and
i do not remember how i fixed it. Cubase went totally nuts. The Audio does not
line up to Grid anymore. No matter what you do it feels like the Latency is
completely Bypassed. At 2048 Buffer Size the Audio is even faster then the Clic
it self and is recorded way before it supposed to be, instead of being late.
At even 32 Buffer Size when you play live notes there is no Latency, once you
recorded to Audio the Audio is late on the grid...by up to ...20...i don't know
what you would call the measurement in the Wave Editor. I tried the MIDI on the
TC Impactm, i tried USB MIDI Sport, both of them the same. To save time to you
there is no need of explaining Audio Latency, i already know how that works, the
problem is what i am experiencing now it is not suposed to be like this. I know
for a fact that even working with 20-30 ms Latencies when recording to Audio
the Audio lines up, Latency is there only when plaqying live. This is weird, any
help would be apreciated. I can't evem work like this now and i do not remember
doing anything speciffic except i guess some updates and the GFX Drivers Update.
This is my Config:
Cubase Pro 8.5.20 x64
Win 7 x64 and Win 10 x64
TC Impact Twin
USB MIDI Sport Uno
MOBO: ASUS SaberTooth X99 USB 3.1
GFX: ASUS GTX 960 Strix OC Edition 2GB
CPU: Intel I7 5820K
RAM: 4x8 GB G.SKILL Ripjaws 4 Series, PC4 21300
Recording Audio in Cubase 8.5 not aligning to Grid!
-
- KVRian
- 1339 posts since 25 Sep, 2011 from New York
Reality is a Condition due to Lack of Weed!
-
- KVRian
- Topic Starter
- 1339 posts since 25 Sep, 2011 from New York
Here is an image of the DCP Latency Checker:
You do not have the required permissions to view the files attached to this post.
Reality is a Condition due to Lack of Weed!
-
- KVRian
- Topic Starter
- 1339 posts since 25 Sep, 2011 from New York
This is totally weird, on every take of recording is different, not even late
the same every time...if you open the wave editor and keep clicking on and
off musical mode it keeps pushing the wave forward on each click...wtf?
the same every time...if you open the wave editor and keep clicking on and
off musical mode it keeps pushing the wave forward on each click...wtf?
Reality is a Condition due to Lack of Weed!
-
- KVRian
- Topic Starter
- 1339 posts since 25 Sep, 2011 from New York
Dear Friends, i really need help with this, it is already proven that it is not Cubase, AudioCard,
or MIDI Interfaces. The same thing happens with 3 different Audio Interfaces, 4 MIDI Interfaces,
Cubase 8.5 Pro, Reason 9.1, 2 different Computers with different Components, Win 7 and 10,
both PCs and OSs right after brand new Installations...they are both equiped with a FW card.
I know for a fact it is MIDI Related, if you Loop MIDI each time you rerecord it just keeps going
forward...i don't know what else to do or where to turn to.
or MIDI Interfaces. The same thing happens with 3 different Audio Interfaces, 4 MIDI Interfaces,
Cubase 8.5 Pro, Reason 9.1, 2 different Computers with different Components, Win 7 and 10,
both PCs and OSs right after brand new Installations...they are both equiped with a FW card.
I know for a fact it is MIDI Related, if you Loop MIDI each time you rerecord it just keeps going
forward...i don't know what else to do or where to turn to.
Reality is a Condition due to Lack of Weed!
-
- KVRAF
- 6323 posts since 30 Dec, 2004 from London uk
It must be the way youre setting up the PCs. Try a stock unmodified Windows install with NO additional software. What happens with just one midi interface? Updates can kill setups. Once you get it working - make an image of the setup.
-
- KVRian
- Topic Starter
- 1339 posts since 25 Sep, 2011 from New York
Hi Ultra, i just did that exactly now, wiped out the whole hard drive, installed fresh Win 7
from DVD. Not a single update installed no settings touched, installed Cubase 8.5.20 Pro
and plugged the iConnect MIDI Interface, NOTHING ELSE! Went to Cubase, opened a MIDI
Track, drew few notes inside, created another, the out of the first was routed into the in
of the second and record on the second one. The Second track notes were pushed forward.
Same problem. until 2 years ago this was a perfectly working machine, then i abandon it
until now because i built another one. Now when i took it for testing it does not work anymore,
same hardware, same interfaces same everything, nothing changed on it. I don't know WTH.
Now i did it only with just a MIDI interface connected not eve Audio Card. will try with the other
Devices and see what happens but i doubt it will be any different. Even Virtual MIDI Cables
internally without anything to do with the outside world still Jitter. I don't know if timing
went off in the BIOS somewhere but can not think of anything.
from DVD. Not a single update installed no settings touched, installed Cubase 8.5.20 Pro
and plugged the iConnect MIDI Interface, NOTHING ELSE! Went to Cubase, opened a MIDI
Track, drew few notes inside, created another, the out of the first was routed into the in
of the second and record on the second one. The Second track notes were pushed forward.
Same problem. until 2 years ago this was a perfectly working machine, then i abandon it
until now because i built another one. Now when i took it for testing it does not work anymore,
same hardware, same interfaces same everything, nothing changed on it. I don't know WTH.
Now i did it only with just a MIDI interface connected not eve Audio Card. will try with the other
Devices and see what happens but i doubt it will be any different. Even Virtual MIDI Cables
internally without anything to do with the outside world still Jitter. I don't know if timing
went off in the BIOS somewhere but can not think of anything.
Reality is a Condition due to Lack of Weed!
-
- KVRer
- 2 posts since 23 Dec, 2016
I am having the exact problem!
Changing buffer size in my soundcard settings puts audio late on grid when lowering and come in late when entering higher values. The delay varies, aprox 550 samples late on grid when chosing 128 buffer size - 3 ms in and 4 out. Recording midi and plugging out from either my Minilogue or my Microbrute get delayed on recorded track in Cubase 9. Also in Cubase 8.5. Worked like a charm before I upgraded and was on Cubase 5.5. Maybe something got screwed up in bios?
Chat with Focusrite one hour to elininate problem with my Focusrite Liquid-saffire 56 soundcard.
I'm having a clean install with Windows 10, only Cubase installed. I3 2.67 ghz 24 Gb ram.
Really don't know what to do next...
Changing buffer size in my soundcard settings puts audio late on grid when lowering and come in late when entering higher values. The delay varies, aprox 550 samples late on grid when chosing 128 buffer size - 3 ms in and 4 out. Recording midi and plugging out from either my Minilogue or my Microbrute get delayed on recorded track in Cubase 9. Also in Cubase 8.5. Worked like a charm before I upgraded and was on Cubase 5.5. Maybe something got screwed up in bios?
Chat with Focusrite one hour to elininate problem with my Focusrite Liquid-saffire 56 soundcard.
I'm having a clean install with Windows 10, only Cubase installed. I3 2.67 ghz 24 Gb ram.
Really don't know what to do next...
-
- Banned
- 5357 posts since 7 May, 2015
I can't remember the issue (though the OP hasn't been around for a while) but it has something to do with midi timing. Check all the options, it's a known issue from a decade ago.
-
- KVRist
- 280 posts since 13 May, 2004 from Italy
Hi
Try to check the voice "midi time stamp" in the peripheral settings, it's a flag; i don't remember exactly in which submenu is.
Luciano
Try to check the voice "midi time stamp" in the peripheral settings, it's a flag; i don't remember exactly in which submenu is.
Luciano
-
- KVRer
- 2 posts since 23 Dec, 2016
My midi is not off track, midi to recorded audio is. Found a solution, changing track delay on the midi channel when recording to audio track.
-
- KVRAF
- 4340 posts since 8 Mar, 2005
Right click on the main toolbar and enable "Constrain Delay Compensation". Now there's a clock icon - make sure its clear (i.e. you WANT delay compensation, you don't want to constrain it).