For some reason when I "record" MIDI, MuLab is putting notes slightly ahead of where they are played in real time. Generally this is one slot ahead of where it should be. I.e., if I intend a note to begin on beat 2 and I have it set for 16th notes, it is recording the start of the note on "ah" of beat 1. I have tested to make sure that I am not playing ahead...it happens consistently all across the board.
I am using an M-Audio Keyrig 49 plugged directly into USB. PC based with Intel Core Duo P8600 @ 2.40Ghz.
Any ideas to what the problem is? Thanks in advance.
Help! MIDI events "recording" slightly ahead of time
-
- KVRer
- 14 posts since 1 Dec, 2012
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Turn off snap to grid.
(Right-click the record button, "Setup record events", "Event recording grid": no grid)
(Right-click the record button, "Setup record events", "Event recording grid": no grid)
-
- KVRer
- Topic Starter
- 14 posts since 1 Dec, 2012
Thanks for the response but I have already tried that and it doesn't solve the problem.
-
- Banned
- 897 posts since 8 Jan, 2005 from Detroit
that is weird, ive never experienced this. your os? midi interface? general age of your computer? configuration of your cpu(s)? ammount of ram youre working with? other software running while you make music? viruses/malware? general overhead to system resources?
-
- KVRer
- Topic Starter
- 14 posts since 1 Dec, 2012
I find it strange as well. I can't really think of a reason that it is happening, other than some kind of "correct" that isn't really needed on MuLab's part. Almost like a MIDI latency correction, if there is such a thing. The M-Audio Keyrig 49 is a direct plug and play USB MIDI device. Perhaps there is a driver somewhere that would correct the problem rather than relying on plug and play? Live audio playback does not present any latency, that's what's odd. When I press keys, I instantly hear sound. And then it "backs up" time when recording the MIDI event. More info on my setup:
Windows 7 x64
4 GB RAM
USB 2.0
Pretty much a clean system dedicated to MuLab and various VST's. I am able to record audio through a USB interface super clean with no latency whatsover. As a matter of fact I'm currently working on a 16+ track song (mix of audio and MIDI) than is running fine on the system.
So yeah, interesting problem. Would love to hear some feedback from MuLab on this. It's not a HUGE deal, I generally just go into the sequence and select all and then move it all forward "absolute" since every single key pressed records with the same time weirdness. Would be nice to not have to do that, though! I'm loving everything else about the software.
Windows 7 x64
4 GB RAM
USB 2.0
Pretty much a clean system dedicated to MuLab and various VST's. I am able to record audio through a USB interface super clean with no latency whatsover. As a matter of fact I'm currently working on a 16+ track song (mix of audio and MIDI) than is running fine on the system.
So yeah, interesting problem. Would love to hear some feedback from MuLab on this. It's not a HUGE deal, I generally just go into the sequence and select all and then move it all forward "absolute" since every single key pressed records with the same time weirdness. Would be nice to not have to do that, though! I'm loving everything else about the software.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Can you record audio input alongside your MIDI input? Are they aligned?
When you say 'the "ah" of beat 1' can you quote the actual time line bars/beats/ticks positions - that would make it clearer, too. I took it to mean it's snapping events exactly to a particular position - is that the case?
If you write a MIDI sequence then play this back as MIDI straight out, can you loop it back to MuLab and record it to a new track? Does the same thing happen?
When you say 'the "ah" of beat 1' can you quote the actual time line bars/beats/ticks positions - that would make it clearer, too. I took it to mean it's snapping events exactly to a particular position - is that the case?
If you write a MIDI sequence then play this back as MIDI straight out, can you loop it back to MuLab and record it to a new track? Does the same thing happen?
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Are you only using MIDI without using any audio out from MuLab? Please describe in detail your music setup.
-
- KVRer
- Topic Starter
- 14 posts since 1 Dec, 2012
I have not tried recording both audio and MIDI at the same time, and don't really have a need to. Most of the time it's me by myself and it would be tough to pull that off!
When I said "ah" of the 1 I mean this (hopefully this makes sense):
If I have the grid set to 16th notes (1-e-&-ah, 2-e-&-a, etc.) it always places the recorded note one "notch" back from where I (audibly even) pressed the physical note on the keyboard. So, if I press a note (or chord) on the 2, it always records it behind where the event actually happened in real time. This is even if I press a note (or chord) on the very first beat of the sequence. It places the event "behind" the actual sequence...I have to physically edit it forward for MuLab to even play that note on playback.
As far as audio setup, generally when doing MIDI I am just using the on board sound on my laptop (MME Audio), either to external speakers or headphones. When recording audio I use a Behringer UControl device, which surprisingly enough to me because of how inexpensive it was, works flawlessly.
Hopefully that explains everything about what is happening and what I am using when it happens. It seems that it has to be with something on my end, as obviously this issue has not come up before.
When I said "ah" of the 1 I mean this (hopefully this makes sense):
If I have the grid set to 16th notes (1-e-&-ah, 2-e-&-a, etc.) it always places the recorded note one "notch" back from where I (audibly even) pressed the physical note on the keyboard. So, if I press a note (or chord) on the 2, it always records it behind where the event actually happened in real time. This is even if I press a note (or chord) on the very first beat of the sequence. It places the event "behind" the actual sequence...I have to physically edit it forward for MuLab to even play that note on playback.
As far as audio setup, generally when doing MIDI I am just using the on board sound on my laptop (MME Audio), either to external speakers or headphones. When recording audio I use a Behringer UControl device, which surprisingly enough to me because of how inexpensive it was, works flawlessly.
Hopefully that explains everything about what is happening and what I am using when it happens. It seems that it has to be with something on my end, as obviously this issue has not come up before.
-
- KVRer
- Topic Starter
- 14 posts since 1 Dec, 2012
Oh, and I'm not using a MIDI out, so I haven't tried playing it out and re-recording it. As I stated above it's a USB board, so only input as far as MIDI goes.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Earlier today i also did a specific MIDI recording test and all was fine here. The only thing i can think of at this point is that the audio driver on your system is reporting a wrong output latency to the host, MuLab in this case. Strange 
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
If you record one MIDI sequence of you playing, then have it playing back whilst you record yourself playing in time with the first MIDI sequence, are the two sequences offset?
It does sound like some odd combination of snap-to-grid and buffer sizes...
Can you give a specific example of a synth you're using to turn MIDI to Audio where this happens? Does it happen with the MuLab built in instruments?
It does sound like some odd combination of snap-to-grid and buffer sizes...
Can you give a specific example of a synth you're using to turn MIDI to Audio where this happens? Does it happen with the MuLab built in instruments?
-
- KVRer
- Topic Starter
- 14 posts since 1 Dec, 2012
It's definitely not a snap-to-grid issue, as I have the problem regardless of having that feature on or off. Not sure how to go about messing with buffering but I'll start poking around and see what I can find. I'm also going to try installing another DAW and see if I have the same problem in that one with the same setup.
Thanks for everyone's input so far.
Thanks for everyone's input so far.