@@virgildanica2372 PW supports e.g., changing buffer size and sample rate in the middle of session, which definitely breaks Jack clients. I know this because I've implemented some LV2 plugins myself and know for a fact that they can't handle such changes dynamically. Apparently PW was also doing some automatic buffer size changes based on DSP load, so this was definitely introducing a lot of random stability issues with Jack clients. Latest version of PW has at least some of these fixed via jack specific configuration, however, I still had some jack connection related issues using Ubuntu Studio 24.04 Beta. I don't want to be PW-hater, but for my use cases it adds zero value while of course not being mature like Jack is. I know the reason for its existence and it makes perfect sense. But I just can't recommend it for stable, professional and/or embedded system usage, yet.
@@SudoMetalStudio This kind of thing is the reason I abandoned (a few years ago) my attempt at using Linux for home recording. In Linux-land, things change all the time. You get a new update, and now some command you've been using for years is gone and replaced with something else. Jack is now mature and probably really good, but a few years ago when I tried to get to grips with U-Studio, and then AV Linux, it was a royal pain in my butt. Now it's apparently mature and working, and of course the upstream devs are gonna replace it... 🤦♂ If I get some time over the weekend I'll install U-Studio on a spare disk on my hackintosh, and see what's what. Thanks for your video, I'll try to follow your example as a test. Cheers.
Yes! Buffer size must be 128 or below. 256 is still somewhat playable but annoying. If you can't do 128 without sound starting to crack and pop, then the CPU is the bottle neck. That's the whole recipe; no more, no less 🙂
Question: how to remap midi device in Ardour? I’m fingerdrumming on Presonus ATOM 4x4 and this crap can’t be remapped internally (not other). In reaper there is JS plugin to remap devices. How to map for example pad 1 to 36, 2 to 38 to match favourite drum pad layout to general midi map?
I have never really used them, but there seems to be several "MIDI Note Transpose" or "MIDI Note Mapper" type of plugins that I believe can be configured to trigger MIDI note X when MIDI note Y is played. Just drop that as first plugin and configure it :) Note that it will still record the original note but the recorded (or played) note is actively transposed. If you are looking to actually record the mapped notes, you might need to use 2 tracks. So you'd then link the pad to track 1 that has the "transpose/mapper plugin" and then output that to another track which records the translated note. There might also be some better ways to do that; this is definitely not familiar area for me.
@@SudoMetalStudio This could be really important for people playing e-kits where the midi map doesn't follow a known standard, and is uneditable on the drum module. I have a 2box kit, that I migrated to from a Roland TD-9 and I remember all sorts of issues trying to record midi (especially the hats position IIRC, that was a pain).
Hi, thanks for the video Just for eference, what's your CPU and how much RAM do you have? I'm using Ardour with a FX8300 and 16 gigs, but I believe that the old tractor can't hold it anymore. I'm thinking about building a PC for it, but I don't want to spend too much.
@@moroboshidan7960 I have Ryzen 7 5700X and 32Gb RAM. But everything I do in this video is not that hardware intensive at all. All the same steps with all the same plugins, buffer sizes etc are also doable with my old gaming laptop, MSI Apache from ~10yrs ago.
@SudoMetalStudio Thanks. In a first search I found the ryzen 5 5500 and the core i5 12400 at reasonable prices here (I live in Brazil, nothing is reasonable here, but you got it). I guess both would suffice, but I'll research a bit more. My computer really fights with that drum gizmo plugin, and It start getting buffer overruns when I load some plugins. Several people told me that there's no relation between buffer overruns an CPU load, but the repeated experiment says the opposite. Maybe I have some timing problem, caused by the display card or whatever. I just have up on trying to find out. Well, thanks for the info, great channel btw. Subscribed.
@@moroboshidan7960 I'm pretty confident those several people are wrong. It's definitely CPU intensive task to run plugins. And it's exactly when the CPU can't handle the signal processing workload that you start having buffer overruns. You can go easier on CPU by increasing buffer size but this introduces latency. RAM or HDD speed doesn't have that much factor, because plugins can't do memory allocation during signal processing (i.e. they don't consume any memory after initial load thus they do not benefit even if you'd had 1TB of RAM). Buffer size 128 is generally good what it comes to latency. It should give about 10ms round trip. RAM size and HDD speed become factor when you start recording, and more so when you record multiple channels at the same time.
@@moroboshidan7960 Oh and in this video I'm using Hydrogen. It's not as heavy as DrumGizmo is but it's also not as professional. I moved into using DrumGizmo and it's definitely the most CPU intensive plugin I have in my mixes. You can actually see the plugin load very nicely in Ardour: Window -> Plugin DSP load.
@@SudoMetalStudio Didn't knew about this feature in Ardour. It has so many configurations and options, I guess I didn't do my homework. But thanks for the tip, I'll definitely check it up. When I use that other plugin with the red drum kit (can't remember its name now) things go better, but drumgizmo sounds a lot more natural to me. I'll check the load, if it is really overloading the cpu, I'll go for a "new" a-hem cough computer. That's for the consult, man, you helped a lot!
![Звукозапись без пафоса [Что нужно для начала]](/img/n.gif)
yeeess Linux Rocks! just bought my first Eletronic Drums, will follow your videos! So excited!
It’s so exciting that Linux music production is gaining traction and attention :)
Well done man. Simple, quick and easy to understand. Thumbs up! 👍🏻
Please keep making these videos!
Dude, are you Finnish?
I just discovered your channel and the content seems great. Nice pacing and you go nicely to the depths of Linux audio 👍
@@puuhapeteification jeps jeps, kiitos 🤘😉
Nice work! Thanks for sharing it.
Linux Rocks On Mate
By the way, i used since earlys 2023 pipewire 100% in my machine to produce and record rock staff and 0 bugs with pipewire 🙏
@@virgildanica2372 PW supports e.g., changing buffer size and sample rate in the middle of session, which definitely breaks Jack clients. I know this because I've implemented some LV2 plugins myself and know for a fact that they can't handle such changes dynamically. Apparently PW was also doing some automatic buffer size changes based on DSP load, so this was definitely introducing a lot of random stability issues with Jack clients. Latest version of PW has at least some of these fixed via jack specific configuration, however, I still had some jack connection related issues using Ubuntu Studio 24.04 Beta.
I don't want to be PW-hater, but for my use cases it adds zero value while of course not being mature like Jack is. I know the reason for its existence and it makes perfect sense. But I just can't recommend it for stable, professional and/or embedded system usage, yet.
@@SudoMetalStudio This kind of thing is the reason I abandoned (a few years ago) my attempt at using Linux for home recording. In Linux-land, things change all the time. You get a new update, and now some command you've been using for years is gone and replaced with something else. Jack is now mature and probably really good, but a few years ago when I tried to get to grips with U-Studio, and then AV Linux, it was a royal pain in my butt. Now it's apparently mature and working, and of course the upstream devs are gonna replace it... 🤦♂
If I get some time over the weekend I'll install U-Studio on a spare disk on my hackintosh, and see what's what. Thanks for your video, I'll try to follow your example as a test. Cheers.
Really great workflow vid! Thanks! I always struggle with latency issues, could you give an advise how to tackle them?
Yes! Buffer size must be 128 or below. 256 is still somewhat playable but annoying. If you can't do 128 without sound starting to crack and pop, then the CPU is the bottle neck. That's the whole recipe; no more, no less 🙂
@@SudoMetalStudio Damn. I was hoping for some magic trick🙄. Thanks for the harsh truth!😁
Question: how to remap midi device in Ardour?
I’m fingerdrumming on Presonus ATOM 4x4 and this crap can’t be remapped internally (not other).
In reaper there is JS plugin to remap devices.
How to map for example pad 1 to 36, 2 to 38 to match favourite drum pad layout to general midi map?
I have never really used them, but there seems to be several "MIDI Note Transpose" or "MIDI Note Mapper" type of plugins that I believe can be configured to trigger MIDI note X when MIDI note Y is played. Just drop that as first plugin and configure it :) Note that it will still record the original note but the recorded (or played) note is actively transposed.
If you are looking to actually record the mapped notes, you might need to use 2 tracks. So you'd then link the pad to track 1 that has the "transpose/mapper plugin" and then output that to another track which records the translated note. There might also be some better ways to do that; this is definitely not familiar area for me.
@@SudoMetalStudio This could be really important for people playing e-kits where the midi map doesn't follow a known standard, and is uneditable on the drum module. I have a 2box kit, that I migrated to from a Roland TD-9 and I remember all sorts of issues trying to record midi (especially the hats position IIRC, that was a pain).
Hi, thanks for the video Just for eference, what's your CPU and how much RAM do you have?
I'm using Ardour with a FX8300 and 16 gigs, but I believe that the old tractor can't hold it anymore. I'm thinking about building a PC for it, but I don't want to spend too much.
@@moroboshidan7960 I have Ryzen 7 5700X and 32Gb RAM. But everything I do in this video is not that hardware intensive at all. All the same steps with all the same plugins, buffer sizes etc are also doable with my old gaming laptop, MSI Apache from ~10yrs ago.
@SudoMetalStudio Thanks. In a first search I found the ryzen 5 5500 and the core i5 12400 at reasonable prices here (I live in Brazil, nothing is reasonable here, but you got it).
I guess both would suffice, but I'll research a bit more.
My computer really fights with that drum gizmo plugin, and It start getting buffer overruns when I load some plugins. Several people told me that there's no relation between buffer overruns an CPU load, but the repeated experiment says the opposite. Maybe I have some timing problem, caused by the display card or whatever. I just have up on trying to find out.
Well, thanks for the info, great channel btw. Subscribed.
@@moroboshidan7960 I'm pretty confident those several people are wrong. It's definitely CPU intensive task to run plugins. And it's exactly when the CPU can't handle the signal processing workload that you start having buffer overruns. You can go easier on CPU by increasing buffer size but this introduces latency. RAM or HDD speed doesn't have that much factor, because plugins can't do memory allocation during signal processing (i.e. they don't consume any memory after initial load thus they do not benefit even if you'd had 1TB of RAM). Buffer size 128 is generally good what it comes to latency. It should give about 10ms round trip.
RAM size and HDD speed become factor when you start recording, and more so when you record multiple channels at the same time.
@@moroboshidan7960 Oh and in this video I'm using Hydrogen. It's not as heavy as DrumGizmo is but it's also not as professional. I moved into using DrumGizmo and it's definitely the most CPU intensive plugin I have in my mixes. You can actually see the plugin load very nicely in Ardour: Window -> Plugin DSP load.
@@SudoMetalStudio Didn't knew about this feature in Ardour. It has so many configurations and options, I guess I didn't do my homework. But thanks for the tip, I'll definitely check it up. When I use that other plugin with the red drum kit (can't remember its name now) things go better, but drumgizmo sounds a lot more natural to me.
I'll check the load, if it is really overloading the cpu, I'll go for a "new" a-hem cough computer.
That's for the consult, man, you helped a lot!