I'm curious how you're determining this? The only thing that comes to mind, which may support your claim, is a scenario I see from time to time where I'll add a Calf Vintage Delay and then notice the sync won't work. I know restarting the session will result in the plugin's sync working but I'll tend to work around it by using Automation to set the BPM for the time being. Eventually (days later?), after having restarted the session, I'll see that sync is indeed working and I'll just remove the silly automation I used to overcome the initial issue.
Is there something more obvious you can walk us through that results in the scenario you're describing?
If you're just talking about the metronome itself, I haven't seen (or heard) any issues as it works reliably on my end. The sync issue I described above may be something else entirely. Just for giggles, I figured I'd show you my MIDI settings which clearly show I have NOT enabled the MIDI metronome. I can't remember what enabling it would do but I want to say it would SEND MIDI events. If I'm correct, I'd think this would be intended for use with external hardware which doesn't fit my workflow.
In this audio file you hear
1.) drum arrangement
2.) with audio metronome - good sync
3.) with audio and midi metronome (fluidsynth connected via Qtractor's dedicated midi metronome output) - a mess
The standard Qtractor metronome sound, logically corresponds to the audio metronome. I have assigned a piano sound to the midi metronome to better differentiate it.
The problem occurs both in the installed version and compiled as an AppImage.
Related:
I already reported months ago that the input counting option did not work correctly in Debian. Now I have verified that it does not work in Ubuntu either.
Curiously, it does work correctly in AppImage.
but yes, the MIDI metronome is not sample accurate whatsoever; it's mostly suited for outboard equipment and not an option or ever comparable to its internal audio counterpart...
however, it is very likely to be a bug in there :) as this thing hasn't been touched for ages, ever since and before the deep high-resolution inception that started on 0.9.29 and up :S...
Hi Rui, in my case it's way out of sync, not only a bit delayed or early. See attachment. First drums, then drums + audio metronome, then drums + audio metronome + midi metronome.
I played arount with timers and drift correction on/off – no difference. The MIDI metronome does always exactly the same but has nothing to to with the song's timing and measure.
I'm curious how you're
I'm curious how you're determining this? The only thing that comes to mind, which may support your claim, is a scenario I see from time to time where I'll add a
Calf Vintage Delayand then notice thesyncwon't work. I know restarting the session will result in the plugin'ssyncworking but I'll tend to work around it by usingAutomationto set theBPMfor the time being. Eventually (days later?), after having restarted the session, I'll see thatsyncis indeed working and I'll just remove the silly automation I used to overcome the initial issue.Is there something more obvious you can walk us through that results in the scenario you're describing?
If you're just talking about the metronome itself, I haven't seen (or heard) any issues as it works reliably on my end. The
syncissue I described above may be something else entirely. Just for giggles, I figured I'd show you my MIDI settings which clearly show I have NOT enabled the MIDI metronome. I can't remember what enabling it would do but I want to say it would SEND MIDI events. If I'm correct, I'd think this would be intended for use with external hardware which doesn't fit my workflow.Audio example attached
In this audio file you hear
1.) drum arrangement
2.) with audio metronome - good sync
3.) with audio and midi metronome (fluidsynth connected via Qtractor's dedicated midi metronome output) - a mess
Same here. Attached recording
The standard Qtractor metronome sound, logically corresponds to the audio metronome. I have assigned a piano sound to the midi metronome to better differentiate it.
The problem occurs both in the installed version and compiled as an AppImage.
Related:
I already reported months ago that the input counting option did not work correctly in Debian. Now I have verified that it does not work in Ubuntu either.
Curiously, it does work correctly in AppImage.
re. Qtractor's MIDI metronome not in sync...
noted!
but yes, the MIDI metronome is not sample accurate whatsoever; it's mostly suited for outboard equipment and not an option or ever comparable to its internal audio counterpart...
however, it is very likely to be a bug in there :) as this thing hasn't been touched for ages, ever since and before the deep high-resolution inception that started on 0.9.29 and up :S...
seeya, next year and beyond! and merry x-mas ofc.
I guess there is a bug
Hi Rui, in my case it's way out of sync, not only a bit delayed or early. See attachment. First drums, then drums + audio metronome, then drums + audio metronome + midi metronome.
Merry Christmas
re. Qtractor's MIDI metronome not in sync
can you try with different MIDI timer settings? and with or without the MIDI queue drift correction?
thanks
no difference
I played arount with timers and drift correction on/off – no difference. The MIDI metronome does always exactly the same but has nothing to to with the song's timing and measure.
re. Qtractor's MIDI metronome not in sync...
JIT x-mas present alert!
prolly fixed in qtractor >= 1.5.0.2git.127fa3
please test && tell, thanks
happy holidays!
It works now
Tested and approved. Thanks Rui.
That fixed both the MIDI metronome and MIDI clock, see also my results with mididings and my Grid TEK2 controller:
my posting at Linuxmusicians
Add new comment