Thanks for making the video. Saved me a lot of time when I configured my Ubuntu audio machine and Bitwig. Now to move along to the keyboards and synth and guitars 😊
Thanks for this tutorial, one of the most awesome that I have found on the net on how to configure Ubuntu just for Bitwig (and not only). Great trick increasing the sample rate up to 96,000hz, even my M-Audio card doesn't go above 48,000 but adjusting it this way I can go down to 128KB buffer on Cadence without xruns. I can't explain why it works but ... It works! Thank you very much!
Wow, if only I could see your actions on the terminal and keep up. But this moves too fast for me to comprehend or follow. Perhaps one day you could break it down into bite size vids for us new linux folks trying to find a way to move from Windows to linux for audio production. But thank you for showing there may be a hopeful future in that direction. Best to you.
@@MrGamelover23 Bitwig is the same file download and install whether you are trialling it, or are a licenced user. So if you want to trial it, all you need to do is click "Demo" when you run Bitwig. And if you own a licence all you need to do is sign in and it will register your licence.
I followed this video using Debian. there's no "lowlatency" kernel in the repo so I used one with the "rt" in the package alias. This seems to have worked since cadence reports realtime. However now when I boot up I get loads of errors because nvidia modules aren't loading. I dunno how to fix that yet. Anyway, long story short, I can;t get jack audio to work. I know this laptop has sound because thats how I watched your video, but for some reason, no dice with JACK. The jack server starts and everything seems okay but BW doesn't see any audio output devices under JACK and whilst the sound engine initialises, playback doesn't ever get triggered. I used hw0 interface and left everything as default. I feel like I am nearly there. The video was extremely helpful. If you ever decide to do a refresh of this tutorial with Debian as the distro, I won't cry about it :)
True, when Pipewire reaches maturity we almost certainly won't have to worry about JACK. I have been evaluating Pipewire on Arch, Ubuntu, and Fedora over the last month. For almost all consumer use cases Pipewire is ready to replace Pulseaudio. For most pro audio cases it will work too, however there are a few edge cases that aren't working.
Great Video. Thanks for the help. Just one question: What are the downsides of the low latency kernel vs the generic one? I guess if it didn't have any, the low latency one would just be the default
Hey thanks so much for these videos and the scripts! I saw you keep on updating them, you're doing god's work. Can you do a video on the process in manjaro/arch?
That's fantastic to hear that you're getting benefit from the scripts. I have heaps of videos I want to get done soon, and an Arch video guide is definitely on my list!
@@linuxaudiotips Yeah they say it's all about creating value, and no one is doing a better job than you at filling this niche for implementing pro audio setups with Linux. The scripts are immensely useful. Really grateful for your videos, they're also entertaining to watch.
I use bitwig and reaper on pop os using jack and studio controls, which I guess is essentially cadence. Reaper runs flawlessly and I can use Carla fx to bridge vst's with no issues, and midi works great when switching between alsa on/ off. Bitwig on the other hand produces spikes and pops no matter the buffer size, using only native plugins, etc, is driving me nuts. I have tried cpu control to no avail. The whole reason was to avoid windows, but Bitwig may as well be ableton as I have to go back to windows, separate drive, to use it, Any pointers appreciated, good content btw!
Sorry to hear that. I've never had problems like that with Bitwig. The only problems I had with Bitwig were when there was an issue with Alsa and Midi in the kernel, but they have been resolved now. Are you using the native DEB package to install Bitwig, or using a Flatpak? Use the DEB if you aren't already. Otherwise, check the DSP graph within Bitwig - is it peaking near max usage, or staying relatively flat and with lots of headroom? You mentioned you've tried different buffer sizes - are you using an external audio interface or system audio? What sample rate are you using? I'd make sure the Bitwig DSP graph is stable first. Then try the usual, lower the sample rate (try 44.1 or 48) and increase the buffer size (max it out to 1024 if necessary during troubleshooting).
Little bit offtopic - but I had a hard time figuring out how to get a midi-controller working in Bitwig with this setup. Disabling the ALSA-midi bridge finally did the job. Perhaps an idea for a follow-up video.
Hi @MarcusBvS. It's funny that you comment on MIDI, because I've just spent all day yesterday experimenting with the different ways to get MIDI to work (and not to work!) and I'm creating a video on it today. You are 100% correct - when using Cadence, in the "Jack Bridges" section under "ALSA MIDI" you need to press the STOP button and UNCHECK the "Start with Jack" checkbox. I'm glad you figured it out :) Things are slightly different when using qjackctl instead of Cadence, and things are slightly different again (it seems) when using pipewire-jack. It's a bit of a minefield, but it can be done!
"and things are slightly different again (it seems) when using pipewire-jack" Oh yes, please do a video about that! I watched the "live switching" video from @unfa and although it was real fun to watch (he couldn't believe how well it worked) I am hestiant to to pull the plug on my ubuntu system now that jack is running smoothly. Btw thanks for your efforts - this tut is by far the best I could find for installing jack on Ubuntu!
@@marcusbvs3043 would you prefer to know how to run Pipewire on your existing Ubuntu installation, or see how it's done with a different distro like Fedora or Arch? What Ubuntu version are you on?
@@linuxaudiotips I am running Ubuntu LTS 20.04 (which is I think the most widespread distro) and yes, I would like to add Pipewire to the running system. Generally speaking I would like to have a system where low latency audio runs as unobstrusive and smoothly as possible, whatever it takes. I also use a macos laptop, so I am accustomed to something quite different ;) and although I like the tinkering in Linux, the audio configuration is a real pita!
Hi, I can't start Jack, it gives me this error. However, the configurations are all ok, do you know how I can fix it? Sat Apr 29 12:01:35 2023: ERROR: Failed to open server Sat Apr 29 12:03:06 2023: ------------------ Sat Apr 29 12:03:06 2023: Controller activated. Version 1.9.20 ([]) built on Sun Jan 23 17:38:32 2022 Sat Apr 29 12:03:06 2023: Loading settings from "/home/gianluca/.config/jack/conf.xml" using expat_2.4.7 ... Sat Apr 29 12:03:06 2023: setting parameter 'engine':'driver':'(null)' to value "alsa" Sat Apr 29 12:03:06 2023: Listening for D-Bus messages Sat Apr 29 12:03:10 2023: Starting jack server... Sat Apr 29 12:03:10 2023: JACK server starting in realtime mode with priority 10 Sat Apr 29 12:03:10 2023: self-connect-mode is "Don't restrict self connect requests" Sat Apr 29 12:03:10 2023: Acquired audio card Audio0 Sat Apr 29 12:03:10 2023: creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit Sat Apr 29 12:03:10 2023: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode Sat Apr 29 12:03:10 2023: Released audio card Audio0 Sat Apr 29 12:03:10 2023: ERROR: Cannot initialize driver Sat Apr 29 12:03:10 2023: ERROR: JackServer::Open failed with -1 Sat Apr 29 12:03:10 2023: ERROR: Failed to open server
I got most of the way through this tutorial, up until 8:55 -- when I restarted the second time and opened Cadence, all I see is the "Dummy" driver. There's no ALSA driver listed. I don't understand this stuff well enough to know how to troubleshoot or how to undo all the steps in this tutorial. Any advice?
Hi Pete. That will work fine when you only want audio to be consumed or generated by one application. However ALSA exclusively locks the audio device. Lots of people will want to have Firefox, or VLC, or Discord etc open while creating music so that they can watch tutorials when they get stuck, or play along with a song. In this case, ALSA won't work, because only one application is allowed access to the sound card at a time. JACK/Pulse (and now Pipewire) allow multiple applications to access the audio device simultaneously.
Great tutorials. Thank you fellow aussie :) I recently started using MX linux and plan on fully migrating to linux for audio production but have encountered some problems with controllers. 1. The Arturia keylab49 mk1 had too many broken keys to be usable - despite the integration. 2. I bought a 2nd hand NI Komplete Kontrol a61 which is a beautiful machine but has no integration on linux.. That i know of.. Can you suggest a workaround for the KK, or suggest a mid-priced controller that works on linux (+bitwig & reaper). Much appreciated. Cheers.
I have a Yamaha CP88 stage piano that I use as a MIDI controller. It works perfectly, however I only use it for playing the keys, not for controlling the transport or other devices. I had a Nektar Impact 49 that worked fine on Linux with both Bitwig and REAPER. Basic MIDI control should work on most keyboards, regardless of the fact it's running on Linux. Advanced functions that require Windows or Mac drivers and application software (potentially what the Komplete Kontrol requires) might be more problematic, but basic notes, velocity, aftertouch, transport control, pads, knobs, faders etc should all work - it's more up to the DAW to support the controller than it is the OS.
Care to explain how do you come up with the number 524288 for max user watches? Do you have any suggestion where can I learn about this? Thank you for your work. You're a godsend brother.
Thanks :) The value should be 600000 (I have corrected all the scripts), and it was obtained by following the advice here: wiki.linuxaudio.org/wiki/system_configuration
Is it normal that once Jack server is running some things don't work properly? for instance, I can't watch youtube videos with jack server running, I need to stop it if I want to watch any
This hasn't happened to me. Have a look in your /etc/security/limits.d/01-audio.conf file and make sure it is configured correctly, and that your user has been added to the audio group. If those things are OK, then it's not an issue.
Hi Son. Yes, absolutely this can be applied to any distro based off Ubuntu 20.04. I've actually improved this video recently, and I have also created some scripts so that people don't have to manually type and run the commands themselves. I have scripts for Ubuntu, Mint, Zorin, Debian etc. Check out the new video here (it has links to the scripts on Github): czcams.com/video/cG6ipmOyfw0/video.html
@@angelrivera8013 No worries! Pipewire is the way of the future (well it's the way of the NOW on Arch, Manjaro, and Fedora) so I have to keep up to date with everything! If you haven't already, check out the install scripts I've prepared - they make things a lot easier: github.com/brendaningramaudio/install-scripts
Hey Brendan, Thank for you video. I really appreciate it. I installed the software according to your explanations but when I run the software and play I hear only white noise. If I connect a USB headset it does not happen. Only from the computer speakers. Do you know what the problem is?
Hi Eran. What operating system (Ubuntu, elementary, other?) are you using? And when you say "run the software", what software are you running, is it Bitwig or Ardour or something else?
@@linuxaudiotips I use Ubuntu, I found out when I use JACK with the laptop speakers as output it just does not work, only through the Pulse Audio When I connect the sound card the JACK works great! This is my solution, Thank :-)
Hi Jelle. Are those xruns when you first start Cadence/JACK? If so, it's OK to get a few xruns when first starting. The main thing to keep an eye on is that you don't get an increasing count of xruns while you are recording.
Thanks@@linuxaudiotips ! They are going up while using Bitwig Studio... i am now on 257. Could it be because of my soundcard? Its an old USB IO2 from Alesis (really ancient)
@@jellewever1225 Yep 257 xruns is too high. What sample rate and buffer size are you using? Are you working only within Bitwig or are you recording live instruments through the Alesis as well?
My other question is... why install a demo of Bitwig to make music when you can' save it? I use Ardour, but there are other DAWS you can use for free and they let you save you projects, like LMMS and Tracktion.
They're also all great DAW's. I love Ardour (and the commercial derivative MixBus). The main reason(s) that this video features Bitwig is that a) there are lots of Ableton users currently on MacOS or Windows that are looking to move to Linux (for philosophical reasons related to their OS) and Bitwig is the closest DAW to Ableton that can be run on Linux and b) I personally love using Bitwig because it offers a fun "playground" experience to creating music. My musical passion was re-invigorated when I found Bitwig, as it really made me feel like I was having fun and experimenting again, after feeling like I was locked into rigid musical structures for some time prior. There are certainly other amazing DAW's around, and I will happily create videos for those when I have the time! I'm currently feeling musically inspired by Bitwig, so I wanted to share some of that inspiration :)
Ardour is horrible for MIDI centric projects, as it was originally meant as an alternative to ProTools. They only started adding MIDI support in version 6.
@@BrunodeSouzaLino You don't know what you are talking about. Ardour has had midi support since it's inception. It just hasn't been a priority until version 6.
@@BoDiddly Not quite. Ardour was meant to be a ProTools copycat, as it's creator was a ProTools user originally. ProTools was never meant to be a midi writing tool even to this day and it shows. And I wouldn't be surprised if many of the early suggestions for better midi support were put down by the creator himself, as he won't implemented anything he wouldn't use or doesn't mak sense to him.
@@BrunodeSouzaLino Actually, midi has been included in Ardour, and the developer is currently working to improve the midi functions in Ardour. Do you think MixBus doesn't have midi support? Of course it does!
Let me start by saying amazing tutorial but follow up by saying i always have so many issues when following linux turorials because there are so many case specific errors that require hours of wiki and forum navigation. for example mine would not apt update && apt upgrade because of a “/var/lib/dpkg/lock” Error . literally 2 hours that took me. Not your fault, Not linux's just what happens when you are an intermediate at best trying to wrestle with the big boys.
Yep, no argument there! Linux certainly does have a decent learning curve. That lock error is likely because Gnome Software had locked dpkg, which meant apt couldn't use it (apt uses dpkg behind the scenes). If you haven't seen it already, perhaps my more recent video would be more helpful? I have written a script that does all the hard work for you. You can find the video at czcams.com/video/cG6ipmOyfw0/video.html and the script(s) at github.com/brendaningram/install-scripts - let me know how you go, and if you have any questions, send them through :)
Jack? Eek, no thank you. Unless of course it's become even somewhat more user friendly. But I don't have any hope for that. Why? Okay, here's the problem. I am no noob when it comes to running Linux, am intimately familiar with kernel compilation and other fun things. And when it comes to music, I gave up trying on Linux a decade ago. When inspiration strikes, I don't have time to worry about all this extra nonsense, I just want to record before the idea's lost. And I can do that with my Mac or iPad. Bully for you if you've got it working, and can deal with it, but a person only has so much meaningful time alive to do what they love, and I love making music, not setting up devices, drivers, editing configs, etc. But Jack? Are we kidding with that? I have never once had any luck getting it to work consistently for longer than an hour or so, with and without external pro audio devices, which, by the way, is the sort of device a musician would be using. Has the situation changed? I still love using Linux for many things (increasingly tired of MacOS) so I would be interested in hearing sucess stories here.
Great video. I wish this was around when I made my initial switch to Ubuntu/Bitwig. I still learned a lot.
Glad it was helpful!
Thanks for making the video. Saved me a lot of time when I configured my Ubuntu audio machine and Bitwig. Now to move along to the keyboards and synth and guitars 😊
Thanks for this tutorial, one of the most awesome that I have found on the net on how to configure Ubuntu just for Bitwig (and not only).
Great trick increasing the sample rate up to 96,000hz, even my M-Audio card doesn't go above 48,000 but adjusting it this way I can go down to 128KB buffer on Cadence without xruns. I can't explain why it works but ... It works! Thank you very much!
Thanks! I'm glad it helped!
Wow, if only I could see your actions on the terminal and keep up. But this moves too fast for me to comprehend or follow. Perhaps one day you could break it down into bite size vids for us new linux folks trying to find a way to move from Windows to linux for audio production. But thank you for showing there may be a hopeful future in that direction. Best to you.
Thank you so much, this was put together so incredibly well. Fantastic stuff.
Thank you, that's really lovely to hear :)
@@linuxaudiotips so is this like the trial version of bitwig that stops working after 30 days or...
@@MrGamelover23 Bitwig is the same file download and install whether you are trialling it, or are a licenced user. So if you want to trial it, all you need to do is click "Demo" when you run Bitwig. And if you own a licence all you need to do is sign in and it will register your licence.
Infinite love bro! You saved my life!
Im happy that bitwig works on Linux.
It works really well. However I recommend running it natively from the DEB packages, and not using it as a Flatpak.
Спасибо огромное! Вы мне очень помогли! Thx wery much!
Is this stil acurate/relevant in 2024??
Super thanks
nice👍
I followed this video using Debian. there's no "lowlatency" kernel in the repo so I used one with the "rt" in the package alias. This seems to have worked since cadence reports realtime. However now when I boot up I get loads of errors because nvidia modules aren't loading. I dunno how to fix that yet. Anyway, long story short, I can;t get jack audio to work. I know this laptop has sound because thats how I watched your video, but for some reason, no dice with JACK. The jack server starts and everything seems okay but BW doesn't see any audio output devices under JACK and whilst the sound engine initialises, playback doesn't ever get triggered. I used hw0 interface and left everything as default. I feel like I am nearly there. The video was extremely helpful. If you ever decide to do a refresh of this tutorial with Debian as the distro, I won't cry about it :)
fantastic tutorial, thanks!!
I'm glad it was helpful!
please make a tutorial how to install and configure pipewire properly on ubuntu.
for pro audio and bitwig use
No worries. Keep an eye out and I'll post it soon :)
Subscribed. Thank you!
thank you :)
You're welcome!
Jack audio wouldn't connect but ALSA is working. Bitwig is up and running. Will give it a test out this evening.
With pipewire starting to gain some ground, we may not need to worry about JACK configs anymore.
True, when Pipewire reaches maturity we almost certainly won't have to worry about JACK. I have been evaluating Pipewire on Arch, Ubuntu, and Fedora over the last month. For almost all consumer use cases Pipewire is ready to replace Pulseaudio. For most pro audio cases it will work too, however there are a few edge cases that aren't working.
Great Video. Thanks for the help. Just one question:
What are the downsides of the low latency kernel vs the generic one? I guess if it didn't have any, the low latency one would just be the default
Hey thanks so much for these videos and the scripts! I saw you keep on updating them, you're doing god's work. Can you do a video on the process in manjaro/arch?
That's fantastic to hear that you're getting benefit from the scripts. I have heaps of videos I want to get done soon, and an Arch video guide is definitely on my list!
@@linuxaudiotips Yeah they say it's all about creating value, and no one is doing a better job than you at filling this niche for implementing pro audio setups with Linux. The scripts are immensely useful. Really grateful for your videos, they're also entertaining to watch.
I use bitwig and reaper on pop os using jack and studio controls, which I guess is essentially cadence. Reaper runs flawlessly and I can use Carla fx to bridge vst's with no issues, and midi works great when switching between alsa on/ off. Bitwig on the other hand produces spikes and pops no matter the buffer size, using only native plugins, etc, is driving me nuts. I have tried cpu control to no avail. The whole reason was to avoid windows, but Bitwig may as well be ableton as I have to go back to windows, separate drive, to use it, Any pointers appreciated, good content btw!
Sorry to hear that. I've never had problems like that with Bitwig. The only problems I had with Bitwig were when there was an issue with Alsa and Midi in the kernel, but they have been resolved now. Are you using the native DEB package to install Bitwig, or using a Flatpak? Use the DEB if you aren't already. Otherwise, check the DSP graph within Bitwig - is it peaking near max usage, or staying relatively flat and with lots of headroom? You mentioned you've tried different buffer sizes - are you using an external audio interface or system audio? What sample rate are you using? I'd make sure the Bitwig DSP graph is stable first. Then try the usual, lower the sample rate (try 44.1 or 48) and increase the buffer size (max it out to 1024 if necessary during troubleshooting).
systemctl disable ondemand not working it says Failed to disable unit: Unit file ondemand.service does not exist.
Little bit offtopic - but I had a hard time figuring out how to get a midi-controller working in Bitwig with this setup. Disabling the ALSA-midi bridge finally did the job. Perhaps an idea for a follow-up video.
Hi @MarcusBvS. It's funny that you comment on MIDI, because I've just spent all day yesterday experimenting with the different ways to get MIDI to work (and not to work!) and I'm creating a video on it today. You are 100% correct - when using Cadence, in the "Jack Bridges" section under "ALSA MIDI" you need to press the STOP button and UNCHECK the "Start with Jack" checkbox. I'm glad you figured it out :) Things are slightly different when using qjackctl instead of Cadence, and things are slightly different again (it seems) when using pipewire-jack. It's a bit of a minefield, but it can be done!
"and things are slightly different again (it seems) when using pipewire-jack" Oh yes, please do a video about that! I watched the "live switching" video from @unfa and although it was real fun to watch (he couldn't believe how well it worked) I am hestiant to to pull the plug on my ubuntu system now that jack is running smoothly.
Btw thanks for your efforts - this tut is by far the best I could find for installing jack on Ubuntu!
@@marcusbvs3043 would you prefer to know how to run Pipewire on your existing Ubuntu installation, or see how it's done with a different distro like Fedora or Arch? What Ubuntu version are you on?
@@linuxaudiotips I am running Ubuntu LTS 20.04 (which is I think the most widespread distro) and yes, I would like to add Pipewire to the running system. Generally speaking I would like to have a system where low latency audio runs as unobstrusive and smoothly as possible, whatever it takes. I also use a macos laptop, so I am accustomed to something quite different ;) and although I like the tinkering in Linux, the audio configuration is a real pita!
Does not work. As soon as I install the kxstudio package, it says it didn't work and that no plugin could handle it??????
Hi, I can't start Jack, it gives me this error. However, the configurations are all ok, do you know how I can fix it?
Sat Apr 29 12:01:35 2023: ERROR: Failed to open server
Sat Apr 29 12:03:06 2023: ------------------
Sat Apr 29 12:03:06 2023: Controller activated. Version 1.9.20 ([]) built on Sun Jan 23 17:38:32 2022
Sat Apr 29 12:03:06 2023: Loading settings from "/home/gianluca/.config/jack/conf.xml" using expat_2.4.7 ...
Sat Apr 29 12:03:06 2023: setting parameter 'engine':'driver':'(null)' to value "alsa"
Sat Apr 29 12:03:06 2023: Listening for D-Bus messages
Sat Apr 29 12:03:10 2023: Starting jack server...
Sat Apr 29 12:03:10 2023: JACK server starting in realtime mode with priority 10
Sat Apr 29 12:03:10 2023: self-connect-mode is "Don't restrict self connect requests"
Sat Apr 29 12:03:10 2023: Acquired audio card Audio0
Sat Apr 29 12:03:10 2023: creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
Sat Apr 29 12:03:10 2023: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
Sat Apr 29 12:03:10 2023: Released audio card Audio0
Sat Apr 29 12:03:10 2023: ERROR: Cannot initialize driver
Sat Apr 29 12:03:10 2023: ERROR: JackServer::Open failed with -1
Sat Apr 29 12:03:10 2023: ERROR: Failed to open server
for those who want fantastic virual synth : uhe is making is synth fully fonctionnal with linux (hive 2 and diva ...😝)
and they are very cheap
I got most of the way through this tutorial, up until 8:55 -- when I restarted the second time and opened Cadence, all I see is the "Dummy" driver. There's no ALSA driver listed. I don't understand this stuff well enough to know how to troubleshoot or how to undo all the steps in this tutorial. Any advice?
have you been able to solve this problem?
@@jackgreen9917 no, I ended up uninstalling cadence altogether. Currently I'm using pipewire + helvum as a virtual patchbay and it works nicely.
I just installed Bitwig and selected ALSA in devices on my old machine, everything runs fine no need for all the config.
Hi Pete. That will work fine when you only want audio to be consumed or generated by one application. However ALSA exclusively locks the audio device. Lots of people will want to have Firefox, or VLC, or Discord etc open while creating music so that they can watch tutorials when they get stuck, or play along with a song. In this case, ALSA won't work, because only one application is allowed access to the sound card at a time. JACK/Pulse (and now Pipewire) allow multiple applications to access the audio device simultaneously.
uptalk
Great tutorials. Thank you fellow aussie :) I recently started using MX linux and plan on fully migrating to linux for audio production but have encountered some problems with controllers. 1. The Arturia keylab49 mk1 had too many broken keys to be usable - despite the integration. 2. I bought a 2nd hand NI Komplete Kontrol a61 which is a beautiful machine but has no integration on linux.. That i know of.. Can you suggest a workaround for the KK, or suggest a mid-priced controller that works on linux (+bitwig & reaper). Much appreciated. Cheers.
I have a Yamaha CP88 stage piano that I use as a MIDI controller. It works perfectly, however I only use it for playing the keys, not for controlling the transport or other devices. I had a Nektar Impact 49 that worked fine on Linux with both Bitwig and REAPER. Basic MIDI control should work on most keyboards, regardless of the fact it's running on Linux. Advanced functions that require Windows or Mac drivers and application software (potentially what the Komplete Kontrol requires) might be more problematic, but basic notes, velocity, aftertouch, transport control, pads, knobs, faders etc should all work - it's more up to the DAW to support the controller than it is the OS.
Care to explain how do you come up with the number 524288 for max user watches? Do you have any suggestion where can I learn about this? Thank you for your work. You're a godsend brother.
Thanks :) The value should be 600000 (I have corrected all the scripts), and it was obtained by following the advice here: wiki.linuxaudio.org/wiki/system_configuration
Is it normal that once Jack server is running some things don't work properly? for instance, I can't watch youtube videos with jack server running, I need to stop it if I want to watch any
You will need to ensure the JACK -> Pulseaudio bridge is running.
it did not ask me to select Yes for real time processing priority, is this an issue?
This hasn't happened to me. Have a look in your /etc/security/limits.d/01-audio.conf file and make sure it is configured correctly, and that your user has been added to the audio group. If those things are OK, then it's not an issue.
Thank you very much for the detailed guide. Could this video be applied to other Ubuntu-based Distros like Linux Mint or POP_OS?
Hi Son. Yes, absolutely this can be applied to any distro based off Ubuntu 20.04. I've actually improved this video recently, and I have also created some scripts so that people don't have to manually type and run the commands themselves. I have scripts for Ubuntu, Mint, Zorin, Debian etc. Check out the new video here (it has links to the scripts on Github): czcams.com/video/cG6ipmOyfw0/video.html
Nice to know you've updated this video recently!
@@angelrivera8013 No worries! Pipewire is the way of the future (well it's the way of the NOW on Arch, Manjaro, and Fedora) so I have to keep up to date with everything! If you haven't already, check out the install scripts I've prepared - they make things a lot easier: github.com/brendaningramaudio/install-scripts
Hey Brendan, Thank for you video.
I really appreciate it.
I installed the software according to your explanations but when I run the software and play I hear only white noise.
If I connect a USB headset it does not happen. Only from the computer speakers.
Do you know what the problem is?
Hi Eran. What operating system (Ubuntu, elementary, other?) are you using? And when you say "run the software", what software are you running, is it Bitwig or Ardour or something else?
@@linuxaudiotips I use Ubuntu, I found out when I use JACK with the laptop speakers as output it just does not work, only through the Pulse Audio
When I connect the sound card the JACK works great! This is my solution, Thank :-)
Thanks a lot for taking the time, i have 7 Xruns, should i fix that somehow?
I got it back to 3 after enabling the lowlatency kernel. Should i improve on it even more?
Hi Jelle. Are those xruns when you first start Cadence/JACK? If so, it's OK to get a few xruns when first starting. The main thing to keep an eye on is that you don't get an increasing count of xruns while you are recording.
Thanks@@linuxaudiotips ! They are going up while using Bitwig Studio... i am now on 257. Could it be because of my soundcard? Its an old USB IO2 from Alesis (really ancient)
I increased my buffer-size, and its much better now.. Xruns stay at 6 now. \o/
@@jellewever1225 Yep 257 xruns is too high. What sample rate and buffer size are you using? Are you working only within Bitwig or are you recording live instruments through the Alesis as well?
My other question is... why install a demo of Bitwig to make music when you can' save it?
I use Ardour, but there are other DAWS you can use for free and they let you save you projects, like LMMS and Tracktion.
They're also all great DAW's. I love Ardour (and the commercial derivative MixBus). The main reason(s) that this video features Bitwig is that a) there are lots of Ableton users currently on MacOS or Windows that are looking to move to Linux (for philosophical reasons related to their OS) and Bitwig is the closest DAW to Ableton that can be run on Linux and b) I personally love using Bitwig because it offers a fun "playground" experience to creating music. My musical passion was re-invigorated when I found Bitwig, as it really made me feel like I was having fun and experimenting again, after feeling like I was locked into rigid musical structures for some time prior. There are certainly other amazing DAW's around, and I will happily create videos for those when I have the time! I'm currently feeling musically inspired by Bitwig, so I wanted to share some of that inspiration :)
Ardour is horrible for MIDI centric projects, as it was originally meant as an alternative to ProTools. They only started adding MIDI support in version 6.
@@BrunodeSouzaLino You don't know what you are talking about. Ardour has had midi support since it's inception. It just hasn't been a priority until version 6.
@@BoDiddly Not quite. Ardour was meant to be a ProTools copycat, as it's creator was a ProTools user originally. ProTools was never meant to be a midi writing tool even to this day and it shows. And I wouldn't be surprised if many of the early suggestions for better midi support were put down by the creator himself, as he won't implemented anything he wouldn't use or doesn't mak sense to him.
@@BrunodeSouzaLino Actually, midi has been included in Ardour, and the developer is currently working to improve the midi functions in Ardour. Do you think MixBus doesn't have midi support? Of course it does!
Let me start by saying amazing tutorial but follow up by saying i always have so many issues when following linux turorials because there are so many case specific errors that require hours of wiki and forum navigation. for example mine would not apt update && apt upgrade because of a “/var/lib/dpkg/lock” Error . literally 2 hours that took me. Not your fault, Not linux's just what happens when you are an intermediate at best trying to wrestle with the big boys.
Yep, no argument there! Linux certainly does have a decent learning curve. That lock error is likely because Gnome Software had locked dpkg, which meant apt couldn't use it (apt uses dpkg behind the scenes). If you haven't seen it already, perhaps my more recent video would be more helpful? I have written a script that does all the hard work for you. You can find the video at czcams.com/video/cG6ipmOyfw0/video.html and the script(s) at github.com/brendaningram/install-scripts - let me know how you go, and if you have any questions, send them through :)
Jack? Eek, no thank you. Unless of course it's become even somewhat more user friendly. But I don't have any hope for that. Why?
Okay, here's the problem. I am no noob when it comes to running Linux, am intimately familiar with kernel compilation and other fun things.
And when it comes to music, I gave up trying on Linux a decade ago.
When inspiration strikes, I don't have time to worry about all this extra nonsense, I just want to record before the idea's lost. And I can do that with my Mac or iPad. Bully for you if you've got it working, and can deal with it, but a person only has so much meaningful time alive to do what they love, and I love making music, not setting up devices, drivers, editing configs, etc.
But Jack? Are we kidding with that? I have never once had any luck getting it to work consistently for longer than an hour or so, with and without external pro audio devices, which, by the way, is the sort of device a musician would be using.
Has the situation changed? I still love using Linux for many things (increasingly tired of MacOS) so I would be interested in hearing sucess stories here.