Forums

This is the issue. I turn on Jack connected to my audio interface which is an M-Audio M-Track... I run Ableton Live 9 32 bit using playonlinux... I go to preferences and I set up my audio through WineAsio.... and the CPU goes over 100% and the sound sounds really bad, super distorted.

I have no idea what it could be. The funny thing is that yesterday when I set everything up, it was running no problem.

Any ideas?

I would see if  you did any updates or anything. Make sure you have real-time access enabled (an rt or low-latency kernel is best). If it worked before and doesn't now, then I don't know what could have happened. If you CPU goes up that high, it is basically having buffer-underruns until it floors the CPU. Check dmesg in a terminal and see if it is showing anything. Also check the Jack logs and see if it is saying anything in there. 

This is the messages on Jack.. IDK if this would help..
 

(qjackctl:6837): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed

(qjackctl:6837): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed

(qjackctl:6837): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed

(qjackctl:6837): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed

11:46:38.641 D-BUS: JACK server is starting...

Cannot connect to server socket err = No such file or directory

Cannot connect to server request channel

jack server is not running or cannot be started

(qjackctl:6837): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed

(qjackctl:6837): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed

11:46:38.663 D-BUS: JACK server was started (org.jackaudio.service aka jackdbus).

Mon Feb 9 11:46:38 2015: Starting jack server...

Mon Feb 9 11:46:38 2015: JACK server starting in realtime mode with priority 10

Mon Feb 9 11:46:38 2015: self-connect-mode is "Don't restrict self connect requests"

Mon Feb 9 11:46:38 2015: Acquired audio card Audio2

Mon Feb 9 11:46:38 2015: creating alsa driver ... hw:MTrack,0|hw:MTrack,0|128|2|44100|0|0|nomon|swmeter|-|32bit

Mon Feb 9 11:46:38 2015: Using ALSA driver USB-Audio running on card 2 - M-Audio M-Track at usb-0000:00:1d.0-1.2, full speed

Mon Feb 9 11:46:38 2015: configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 2 periods

Mon Feb 9 11:46:38 2015: ALSA: final selected sample format for capture: 24bit little-endian

Mon Feb 9 11:46:38 2015: ALSA: use 2 periods for capture

Mon Feb 9 11:46:38 2015: ALSA: final selected sample format for playback: 24bit little-endian

Mon Feb 9 11:46:38 2015: ALSA: use 2 periods for playback

Mon Feb 9 11:46:38 2015: graph reorder: new port 'system:capture_1'

Mon Feb 9 11:46:38 2015: New client 'system' with PID 0

Mon Feb 9 11:46:38 2015: graph reorder: new port 'system:capture_2'

Mon Feb 9 11:46:38 2015: graph reorder: new port 'system:playback_1'

Mon Feb 9 11:46:38 2015: graph reorder: new port 'system:playback_2'

Mon Feb 9 11:46:39 2015: Saving settings to "/home/xtian/.config/jack/conf.xml" ...

11:46:40.903 JACK connection change.

11:46:40.905 Server configuration saved to "/home/xtian/.jackdrc".

11:46:40.906 Statistics reset.

11:46:40.917 Client activated.

11:46:40.923 JACK connection graph change.

Mon Feb 9 11:46:40 2015: New client 'qjackctl' with PID 6837

Does your sample rate in Ableton match the sample rate in Jack?

Yes it's 44100 on both.

Do you have real-time enabled in qjackctl? It should be. If that doesn't work, try a low-latency or realtime kernel. I am not sure what changed. Did you do any updates on you system since the last time it worked? Delete any software? Install anything?

Okay I brought down the sample rate to 3200, and now it's working better. It's about 50% on the CPU, which is still a lot, and there is still lots of crackling. What exactly is a realtime kernel?

Oh. I almost forgot. Set your sample rate back, and try to toggle the option for Multi-Core Support in Ableton. That might fix it. 

Here is a link:

https://www.ableton.com/en/articles/reduce-cpu-load/

Now that I remember it was never working with my Audio Interface. It was only working with my headphone jack. I got it working with my headphone jack again. But that's useless since I need to use the Audio Interface to record vocals. This is what happes.

I make sure I select my M-Audio M-Track in Jack, and then I once I open Ableton Live, it starts buzzing. And as soon as I play any notes through a midi keyboard, it makes a really loud beep, and it won't stop until I disconnect the audio interface.

But I can use the headphone jack from my laptop just fine when I select that in Jack. I have no idea why that is. Any ideas?

This is not a POL or Wine issue. It is a jack issue with how you have Jack configured to work with your interface. You will need to troubleshoot that in the Jack or KXStudio forums. I can tell you that you need to first make sure that your audio interface works fine through Linux by itself and through Jack on Linux. Then, you need to make sure your user is in the audio group, you should have real-time enabled, you should have a lowlatency or real-time kernel installed, as well as your sound buffers and sample rate set correctly. You will also need pulseaudio-module-jack (or something like that), as well as a plulse-alsa lib to get it working correctly. If you have that, and it still doesn't work, you will have to check KXStudio's forums (which would be the best place for that in your particular case.). The buzzing is from buffer-underruns and it is pegging your CPU until it dies, which means that Jack is not set up correctly.