Відео

Basically all modern distros come with PipeWire as default. It works as both PulseAudio and Jack server, uniting them under the same audio subsystem. Previously, installing Jack was recommended for pro audio, but that is no longer the case as PipeWire serves also for jack applications. Some still prefer the og jack server as it's more mature and might serve specific use cases better, but PipeWire will likely be the only future for Linux audio. Audio routing wise PipeWire is just objectively better, and based on my own benchmarks it's slightly better also performance-wise (lower latency than with jack). I've heard good things about AVLinux but I find Ubuntu Studio to be my favourite. TLDR; Install Ubuntu Studio, all defaults and everything just works 🙂

@@SudoMetalStudio Thanks, I have dabbled a bit with ubuntu back in the day, but I think I'll be giving ubuntu studio a go. Another question. I wanna do some basic desktop stuff and light gaming too. Is it possible on ubuntu studio or should I pick up another distro on the side for that?

@@inso80 I'm gaming a bit (Steam) and all works well in Ubuntu Studio; except that with multiple display -setup many games tend to "leak" the mouse to other displays while gaming full screen. So, I always disable all extra displays before gaming. Ubuntu Studio comes with KDE Plasma desktop environment so it might be related to that too. Otherwise I really like KDE! Also no issues with NVIDIA RTX (using proprietary driver), except that Wayland wasn't working at all last time I checked. X11 works great and it's also the default.

@@inso80 Oh and you can also go fully standard Ubuntu and just run the Ubuntu Studio Installer! I haven't tried it but apparently it does all the pro audio tweaks for you and installs recommended packages. ubuntustudio.org/ubuntu-studio-installer/

@@SudoMetalStudio Thanks for the info. Is a big help.

@@beefyjoe Since 24.04 it defaults to PipeWire. Or maybe since 23.10. There is/was a configuration tool for switching audio configuration included (Ubuntu Studio Audio Configuration), but I believe it's strongly discouraged to switch back.

@@ospifi True! I always use LSP Latency Meter and at the end of this video you can see some of my RTP results: ua-cam.com/video/0BdxSFbIGc8/v-deo.html&si=6KqJ4BIJV-al-v9a

@@SudoMetalStudio No prkl siellähän se luuraski. Pitäs melkeen muovata kommentti muotoon "one can use jack_iodelay..." Nyt oma kommenttini kuulostaa hirveältä viisastelulta :-D Ehkä tuosta joku osaa poimia avainsanoja pakettihallinnalle ja kokeilla jos tarvis :)

@ospifi ihan hyvä vaan et tulee kertauksia ja samojakin vinkkejä eri videoiden alle 🙂👍

@@Durkhead Really? You mean the null-testing setup with 3 waveform tracks? That awesome but superweird to have a button for such specific task.

@SudoMetalStudio you click a button and you can hear only wat the plugin is adding its super usefull esp when using a clipper

@@Durkhead cool! I'll have to check if Ardour has something similar.

@@SudoMetalStudio it should say something like delta signal

@@caiojbvguimaraes yes, I have Focusrite Scarlett 18i20 3rd gen.

@@SYnTs-MuSic I'd love to, but my wife and kids wouldn't 😅 This is just a hobby that keeps me sane, and creating videos is surprisingly time-consuming. Still, it definitely gets me pushing the extra mile when people ask for more 😉🎶

@@ghostpepper3585 yea so some NAM captures are very CPU intensive. You might have better luck using models tagged with Lite or Feather. Or go higher with buffer size (=easier on CPU, but more latency)

@SudoMetalStudio I'll try that

This video is designed to be watched 7 times, after which the tingling sensation hits and the brave new world opens up for you.

Which Linux distro are you using? Check that Carla's audio driver is configured as JACK with Multiple Clients (Carla -> Settings -> Configure- > Engine).

@SudoMetalStudio Yess! Kiitos! The right hint from you.

@@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!

@@tool-jf7vz Of course I can't ignore my favourite people i.e. my viewers 😂 I haven't seen that error but it sounds like privilege issue. Which Linux distribution are you using? Did you clone the NAM repository under home (~) directory or somewhere else?

​@@SudoMetalStudio Hi! I use AV Linux MX Edition and clone in /opt. Before this I used Ubuntu-like distributions and everything was fine. AV Linux turned out to be more gentle to my PC and...THANK YOU VERY MUCH for answering me. The guitar is very important in my projects...probably as in others. )

Did you manage to get around the issue? I've never tried AVLinux yet but I might at some point.

@@SudoMetalStudio )) I didn't rack my brains and installed the version for Windows (it's good that AV Linux is packed with everything necessary for this).

@@mr.mastermind4840 You request, I deliver! 😉 ua-cam.com/users/shorts6IWf2KlCeiI?si=5qE80CFLpQeFGeZA

32 buffer size sounds completely unneccessary for me. Even 64 is mostly overkill but well-trained drummer could probably notice jump from 64 to 128. I personally use 128 and have absolutely no issues with latency. Buffer size 128 @ 48kHz = 2,7ms x 2 = 5,4ms DSP latency, and buffer size 32 @ 48kHz similarly 1,3ms. Plus hardware latency constant of ~3ms for both so you have approx 9ms vs 4ms roundtrip latency. Sound travels 1,7m in 5ms, so unless you can hear difference in latency standing 2m vs 4m away from amp, there's should be no audible difference in 32 vs 128 buffer size (and this was very generously rounded). But there is huge difference in CPU load. This is why you should use highest reasonable buffer size in DAW, and switch even higher (1024) once you go from recording to mixing. Also note that jack uses triple buffering (2,6ms x3= 7,8ms) instead of double buffering, unless it's configured to be in synchronous mode.

​@@SudoMetalStudiobest analyse and explanation about latency measurement i've ever seen !

Ardour has been extremely stable for me. Past 2yrs I've had only 2-3 crashes. I'd rather believe it's some faulty plugin that causes it.

@@SudoMetalStudio Yeah, it's possible, of course. Not tried yet out of ardour, but if you want to reproduce: browsing for nam file, in list mode, scroll on long list (like the github repo you mention) > crash at 75% of the scroll bar. Anyway, it works well, seems not too heavy load cpu/ram, thanks again !

@@archloy Oh it was not Ardour related! I can actually reproduce that crash exactly like you said also in Carla. Do you want to report the bug or would you like me to do that?

@@SudoMetalStudio Nice, it's not me the fault ! :D If you can report it, you're welcome (I suppose your english way better than mine ;)), but if you do not have a github account, I can do it, no problem. I will try to get more info/debug on that (I was thinking a night with my guitar and bass, finally, it will be with my compiler and some code x) )

@@archloy It's on the GUI and not in the actual NAM plugin. I can report, all credit for you :) ua-cam.com/video/Jsfu-YpCu00/v-deo.html

@@eranddroory9987 No. I'm using Ubuntu Studio 24.04 in this video. E.g. AVLinux which is also meant for studio work is very different. The "audio core" (PipeWire) is mostly the same for many distros now-a-days but not always. Some users still prefer the older but more techy audio framework (Jack).

@@marcink3198 I mostly use Carla because of its plugin loading capability. But Patchance has more polished view that is more wow-effect 🙂 It also handles stereo linking, and it's pinned to Task Bar in Ubuntu Studio by default so Patchance is what new users see first.