Nice breakdown here. This made a lot of things make sense for me. When I started recording I used 96khz sample rate because I didn't know any better. I thought "oh cool I get a really low latency and my CPU isn't maxed out constantly", but then I saw my hard drive space getting eaten right up. Another thing I noticed is if you have a lot of cuts and edits in Ardour, that can cause a lot of xrun errors if you don't adjust the buffer size. Or just bounce the edited tracks so they're all one region. Anyway, great video! \m/
Thanks man, that will help a lot of guy like me that have a randomly working setup (yes, this kind of setup that finally works, but I can"t say why ;) )
Good stuff! For measuring latency caused by hardware and drivers with a minimal dsp load you can use jack_iodelay (jack-tools) or LSP latency meter (lsp-plugins) paired with cable from line/headphone out to line in. Both of these plugins basically output a ping and measure the time spent between plugin->output buffer->analog->input buffer->plugin.
@@ospifi True! I always use LSP Latency Meter and at the end of this video you can see some of my RTP results: th-cam.com/video/0BdxSFbIGc8/w-d-xo.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 :)
Nice breakdown here. This made a lot of things make sense for me. When I started recording I used 96khz sample rate because I didn't know any better. I thought "oh cool I get a really low latency and my CPU isn't maxed out constantly", but then I saw my hard drive space getting eaten right up.
Another thing I noticed is if you have a lot of cuts and edits in Ardour, that can cause a lot of xrun errors if you don't adjust the buffer size. Or just bounce the edited tracks so they're all one region.
Anyway, great video! \m/
Thanks again. Added to my channel's playlist. Happy New Year.
Useful summary -- thanks for posting this video!
Hey ! Thanks for this very useful video. So glad I finally found a YT channel that talks about music on Linux !
Thank you for that very good and informative video!
Thanks for making these videos man, watched all of them, really helpful 🤝
Thanks man, that will help a lot of guy like me that have a randomly working setup (yes, this kind of setup that finally works, but I can"t say why ;) )
Thanks a lot for your kind and thorough explanation. Happy holidays~~~
Thank you for the explanation.
Great conclusion!
Good stuff! For measuring latency caused by hardware and drivers with a minimal dsp load you can use jack_iodelay (jack-tools) or LSP latency meter (lsp-plugins) paired with cable from line/headphone out to line in. Both of these plugins basically output a ping and measure the time spent between plugin->output buffer->analog->input buffer->plugin.
@@ospifi True! I always use LSP Latency Meter and at the end of this video you can see some of my RTP results:
th-cam.com/video/0BdxSFbIGc8/w-d-xo.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 🙂👍