Waveform 12 records with minutes of delay/offset with Jack on Linux
-
- KVRer
- 26 posts since 13 Oct, 2004 from Berlin/Germ
Most strange bug I ever have seen: when recording Audio or MIDI I get clips with several minutes of delay before the signal.
As in: start recording and play the signal, the clip shows nothing(no waveform for audio, no notes for MIDI) after 1-2 minutes of playing, the signals show up in the clip, obviously in all the wrong position on the timeline.
If you look at the clips in the project browser, you see the correctly recorded material after up to 6 minutes silence, though of course I started playing a second after the clip started being recorded.
This is with Jack on Linux (Ubuntu Studio 20.04 as is officially recommended by Tracktion)
Of course all other applications(Ardour, Muse etc) work perfectly correct on the very same machine with the same settings.
It also works in Waveform if I select Alsa via Pulse Audio instead of Jack. But that would be 3rd class: I would get thrice the latency and could not record from Jack then...
As in: start recording and play the signal, the clip shows nothing(no waveform for audio, no notes for MIDI) after 1-2 minutes of playing, the signals show up in the clip, obviously in all the wrong position on the timeline.
If you look at the clips in the project browser, you see the correctly recorded material after up to 6 minutes silence, though of course I started playing a second after the clip started being recorded.
This is with Jack on Linux (Ubuntu Studio 20.04 as is officially recommended by Tracktion)
Of course all other applications(Ardour, Muse etc) work perfectly correct on the very same machine with the same settings.
It also works in Waveform if I select Alsa via Pulse Audio instead of Jack. But that would be 3rd class: I would get thrice the latency and could not record from Jack then...
nostrum fungitur
- KVRian
- 764 posts since 25 Jul, 2010 from Northern Ireland
@zettberlin Waveform has never given me trouble with jack running on Ubuntu 20.04 , low latency kernel, although I do have a few system hacks going on to make latency as low as possible for all audio apps , but generally you should still be good to go with the stock Ubuntu Studio settings.
Can you also give some more details on your soundcard and what settings that you are using in both jack and Waveform ?
Just to work from a clean slate, would it also be possible to reboot 1st ?
Thanks
Can you also give some more details on your soundcard and what settings that you are using in both jack and Waveform ?
Just to work from a clean slate, would it also be possible to reboot 1st ?
Thanks
- KVRian
- 1294 posts since 3 May, 2005 from Victoria, BC
I've received one other report of this issue, but as soon as the person created a new project, it went away. So far I haven't been able to reproduce the exact setting that cause it. If you create a new project, do you still see it? Are you recording with punch, loop, etc?
-
- KVRer
- Topic Starter
- 26 posts since 13 Oct, 2004 from Berlin/Germ
Thanks to all.
@mikoatkvr I also never had trouble running Waveform 11(or any Tracktion DAW before) with Jack, its 12 specific...
I use a Soundcraft USB 4-channel interface(a mixer called Notepad 12FX) set up with Ubuntu Studio Controls as the Jack Master device with 128/2/48 no trouble whatsoever with Carla, Ardour, Muse etc
Kernel is: 5.13.0-37-lowlatency no xruns.
@FigBug I restarted Waveform several times, deleted the existing projects and set up new ones... And I THINK, there was a little less offset (30 seconds instead of 4 minutes... but nothing better than that.
I may restart the machine tho and look, if it helps...
@mikoatkvr I also never had trouble running Waveform 11(or any Tracktion DAW before) with Jack, its 12 specific...
I use a Soundcraft USB 4-channel interface(a mixer called Notepad 12FX) set up with Ubuntu Studio Controls as the Jack Master device with 128/2/48 no trouble whatsoever with Carla, Ardour, Muse etc
Kernel is: 5.13.0-37-lowlatency no xruns.
@FigBug I restarted Waveform several times, deleted the existing projects and set up new ones... And I THINK, there was a little less offset (30 seconds instead of 4 minutes... but nothing better than that.
I may restart the machine tho and look, if it helps...
nostrum fungitur
-
- KVRian
- 657 posts since 12 Mar, 2013 from Vladivostok
Did you try to reset "Low Latency Mode" in "Advanced" settings and/or "Trigger Level" with "Time Adjust" in input settings?
You do not have the required permissions to view the files attached to this post.
- KVRian
- 1294 posts since 3 May, 2005 from Victoria, BC
Can you email me at roland@tracktion.com and I will get you a build with additional logging so I can see what is going on.
-
- KVRer
- 4 posts since 24 Mar, 2022
I'm getting something similar.
I'm using Waveform 12.0.53 on a windows PC.
I open an edit created in Waveform 11 .
I record new audio into an existing track.
It puts silence at start of track so what I have recorded doesn't align - in my case its 1.5 beats of silence in a track at 112BPM. Cutting the space at the start of the track and shifting it left until its in time makes it correct.
I have the same issue recording midi.
I haven't tried a new edit in Waveform 12 to see whether it is also a issue there. I'll give it a bash tomorrow.
I'm using Waveform 12.0.53 on a windows PC.
I open an edit created in Waveform 11 .
I record new audio into an existing track.
It puts silence at start of track so what I have recorded doesn't align - in my case its 1.5 beats of silence in a track at 112BPM. Cutting the space at the start of the track and shifting it left until its in time makes it correct.
I have the same issue recording midi.
I haven't tried a new edit in Waveform 12 to see whether it is also a issue there. I'll give it a bash tomorrow.
-
- KVRer
- Topic Starter
- 26 posts since 13 Oct, 2004 from Berlin/Germ
Tried this, it gets even more wild. Now the clip does not show up while recording and at stop it jumps 30 second ahead in the timeline:Kott wrote: Thu Mar 24, 2022 10:16 pm Did you try to reset "Low Latency Mode" in "Advanced" settings and/or "Trigger Level" with "Time Adjust" in input settings?

nostrum fungitur
-
- KVRer
- Topic Starter
- 26 posts since 13 Oct, 2004 from Berlin/Germ
Ha!!Kott wrote: Thu Mar 24, 2022 10:46 pm I had this issue until I reset "Low Latency Mode" to default in WF12.
That sorted it out: all looks just as it should now!!!
Thanks a lot
nostrum fungitur
-
- KVRer
- Topic Starter
- 26 posts since 13 Oct, 2004 from Berlin/Germ
I did start with a clean new install.Kott wrote: Thu Mar 24, 2022 11:02 pm wow...
I'd try to backup (rename) config (.config/Tracktion/Waveform/Waveform.settings or whole .config/Tracktion) and run with clean profile.
Anyway, I just had fiddeled with the trigger level and time adjust, which gave me that crazy 30 second jumps.
I had actually not pushed the reset Latency to default Button... sorry, my bad...
nostrum fungitur
- KVRian
- 764 posts since 25 Jul, 2010 from Northern Ireland
I think the problem is that you were not hitting the db level that the trigger level was set to.
I can reproduce this easily. The clip is then trimmed to exactly the point where the threshold is met, which is the intended behaviour I guess as you don't need the silence anyway.
I can reproduce this easily. The clip is then trimmed to exactly the point where the threshold is met, which is the intended behaviour I guess as you don't need the silence anyway.
-
- KVRer
- 4 posts since 24 Mar, 2022
I've retested today.markyk65 wrote: Thu Mar 24, 2022 10:37 pm I'm getting something similar.
I'm using Waveform 12.0.53 on a windows PC.
I open an edit created in Waveform 11 .
I record new audio into an existing track.
It puts silence at start of track so what I have recorded doesn't align - in my case its 1.5 beats of silence in a track at 112BPM. Cutting the space at the start of the track and shifting it left until its in time makes it correct.
I have the same issue recording midi.
I haven't tried a new edit in Waveform 12 to see whether it is also a issue there. I'll give it a bash tomorrow.
The issue does not occur for me when I create a new edit in Waveform 12 and record into this.
It does occur when I open an edit created in Waveform 11 and add to this. I have tried adding to an existing track and creating a new track within the edit and both have the issue with a Waveform 11 edit.
For me I cannot see that the low latency mode is the issue because this is a global setting that applies to all edits, and it is only Waveform 11 edits that give me the problem.
- KVRian
- 1294 posts since 3 May, 2005 from Victoria, BC
Can you please make an archive of the edit that is causing problems and send to roland@tracktion.com
