home.social

#rodecaster — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rodecaster, aggregated by home.social.

  1. Crazy world: I'm now running my whole #podcast setup including #ultraschall and my #rodecaster on #fedora #silverblue #linux and it just works 🤩

  2. Crazy world: I'm now running my whole #podcast setup including #ultraschall and my #rodecaster on #fedora #silverblue #linux and it just works 🤩

  3. Crazy world: I'm now running my whole #podcast setup including #ultraschall and my #rodecaster on #fedora #silverblue #linux and it just works 🤩

  4. Crazy world: I'm now running my whole #podcast setup including #ultraschall and my #rodecaster on #fedora #silverblue #linux and it just works 🤩

  5. Crazy world: I'm now running my whole #podcast setup including #ultraschall and my #rodecaster on #fedora #silverblue #linux and it just works 🤩

  6. today's rabbit hole:

    Giving pipewire a third chance to do my audio routing for me

    I think it clicked today, and I have the solution I was hoping for in the first place!

    I have an USB audio interface with a built in mixer (so that I can for example control the volume of music and a game independently with a physical fader) and it obviously doesn't have any first party linux software support - all my computer sees is a single device with 10 input channels, with no way of knowing that channels 4 and 5 are meant for "music"

    My first attempt at this was with qpwgraph which technically worked, but failed to start about once a week, and it really didn't like me unplugging the interface. The 2nd one involved two null-audio-sinks and still qpwgraph - that at least made it so that I only had to reconnect four channels when the config got screwed up again, but it didn't do anything about the occasional crash

    Today's success involved the loopback module, which has the neat option of specifying a preferred target device to pipe the audio to - and apparently that just does not care if the preferred device disappears, it reconnects just fine when available

    So now I have two new virtual audio devices that are there no matter what, can do all my routing through the system's native audio settings, and the whole thing doesn't go belly-up when I turn off the interface, and the whole thing only needs a single config file and no external dependencies other than pipewire! Wohoo!

    In case anyone's interested (or I need this again in four years), here's the config: gist.github.com/Sirs0ri/5f18c2

    #pipewire #RodeCaster #AudioInterface

  7. today's rabbit hole:

    Giving pipewire a third chance to do my audio routing for me

    I think it clicked today, and I have the solution I was hoping for in the first place!

    I have an USB audio interface with a built in mixer (so that I can for example control the volume of music and a game independently with a physical fader) and it obviously doesn't have any first party linux software support - all my computer sees is a single device with 10 input channels, with no way of knowing that channels 4 and 5 are meant for "music"

    My first attempt at this was with qpwgraph which technically worked, but failed to start about once a week, and it really didn't like me unplugging the interface. The 2nd one involved two null-audio-sinks and still qpwgraph - that at least made it so that I only had to reconnect four channels when the config got screwed up again, but it didn't do anything about the occasional crash

    Today's success involved the loopback module, which has the neat option of specifying a preferred target device to pipe the audio to - and apparently that just does not care if the preferred device disappears, it reconnects just fine when available

    So now I have two new virtual audio devices that are there no matter what, can do all my routing through the system's native audio settings, and the whole thing doesn't go belly-up when I turn off the interface, and the whole thing only needs a single config file and no external dependencies other than pipewire! Wohoo!

    In case anyone's interested (or I need this again in four years), here's the config: gist.github.com/Sirs0ri/5f18c2

    #pipewire #RodeCaster #AudioInterface

  8. today's rabbit hole:

    Giving pipewire a third chance to do my audio routing for me

    I think it clicked today, and I have the solution I was hoping for in the first place!

    I have an USB audio interface with a built in mixer (so that I can for example control the volume of music and a game independently with a physical fader) and it obviously doesn't have any first party linux software support - all my computer sees is a single device with 10 input channels, with no way of knowing that channels 4 and 5 are meant for "music"

    My first attempt at this was with qpwgraph which technically worked, but failed to start about once a week, and it really didn't like me unplugging the interface. The 2nd one involved two null-audio-sinks and still qpwgraph - that at least made it so that I only had to reconnect four channels when the config got screwed up again, but it didn't do anything about the occasional crash

    Today's success involved the loopback module, which has the neat option of specifying a preferred target device to pipe the audio to - and apparently that just does not care if the preferred device disappears, it reconnects just fine when available

    So now I have two new virtual audio devices that are there no matter what, can do all my routing through the system's native audio settings, and the whole thing doesn't go belly-up when I turn off the interface, and the whole thing only needs a single config file and no external dependencies other than pipewire! Wohoo!

    In case anyone's interested (or I need this again in four years), here's the config: gist.github.com/Sirs0ri/5f18c2

    #pipewire #RodeCaster #AudioInterface

  9. today's rabbit hole:

    Giving pipewire a third chance to do my audio routing for me

    I think it clicked today, and I have the solution I was hoping for in the first place!

    I have an USB audio interface with a built in mixer (so that I can for example control the volume of music and a game independently with a physical fader) and it obviously doesn't have any first party linux software support - all my computer sees is a single device with 10 input channels, with no way of knowing that channels 4 and 5 are meant for "music"

    My first attempt at this was with qpwgraph which technically worked, but failed to start about once a week, and it really didn't like me unplugging the interface. The 2nd one involved two null-audio-sinks and still qpwgraph - that at least made it so that I only had to reconnect four channels when the config got screwed up again, but it didn't do anything about the occasional crash

    Today's success involved the loopback module, which has the neat option of specifying a preferred target device to pipe the audio to - and apparently that just does not care if the preferred device disappears, it reconnects just fine when available

    So now I have two new virtual audio devices that are there no matter what, can do all my routing through the system's native audio settings, and the whole thing doesn't go belly-up when I turn off the interface, and the whole thing only needs a single config file and no external dependencies other than pipewire! Wohoo!

    In case anyone's interested (or I need this again in four years), here's the config: gist.github.com/Sirs0ri/5f18c2

    #pipewire #RodeCaster #AudioInterface

  10. today's rabbit hole:

    Giving pipewire a third chance to do my audio routing for me

    I think it clicked today, and I have the solution I was hoping for in the first place!

    I have an USB audio interface with a built in mixer (so that I can for example control the volume of music and a game independently with a physical fader) and it obviously doesn't have any first party linux software support - all my computer sees is a single device with 10 input channels, with no way of knowing that channels 4 and 5 are meant for "music"

    My first attempt at this was with qpwgraph which technically worked, but failed to start about once a week, and it really didn't like me unplugging the interface. The 2nd one involved two null-audio-sinks and still qpwgraph - that at least made it so that I only had to reconnect four channels when the config got screwed up again, but it didn't do anything about the occasional crash

    Today's success involved the loopback module, which has the neat option of specifying a preferred target device to pipe the audio to - and apparently that just does not care if the preferred device disappears, it reconnects just fine when available

    So now I have two new virtual audio devices that are there no matter what, can do all my routing through the system's native audio settings, and the whole thing doesn't go belly-up when I turn off the interface, and the whole thing only needs a single config file and no external dependencies other than pipewire! Wohoo!

    In case anyone's interested (or I need this again in four years), here's the config: gist.github.com/Sirs0ri/5f18c2

    #pipewire #RodeCaster #AudioInterface

  11. Videotuotanto- ja livestriimauslaite RØDECaster Video sai tuoreen ohjelmistopäivityksen myötä uusia kaivattuja ominaisuuksia. Laite on ollut minulla testissä tammikuusta asti ja lähetin RØDElle keväämmällä palautetta toive- ja puutelistan kera. Noin puolet omista toiveista toteutui tänään julkaistussa päivityksessä. Erinomaista palvelua, näin sitä pidetään asiakkaat tyytyväisenä. 👍🏻

    youtu.be/I5lUU-D6rmA?feature=s

    #videotuotanto #videoproduction #striimaus #streaming #Cascadeus #RØDE #RØDECaster

  12. Falls jemand mal mit seinem #Rødecaster Duo nicht mehr weiterkommt (bei mir war es konkret: Der Fortschrittsbalken beim Hochfahren hing bei ~99%, nichts weiter passiert) - diese Methode zum Hard Reset hat tatsächlich funktioniert 🎚️

    #Rodecaster #Podcast

    Quelle: reddit.com/r/rode/comments/18w

  13. Falls jemand mal mit seinem #Rødecaster Duo nicht mehr weiterkommt (bei mir war es konkret: Der Fortschrittsbalken beim Hochfahren hing bei ~99%, nichts weiter passiert) - diese Methode zum Hard Reset hat tatsächlich funktioniert 🎚️

    #Rodecaster #Podcast

    Quelle: reddit.com/r/rode/comments/18w

  14. It's been frustrating and fun -- mostly fun -- configuring my MacBook Pro and my new Rodecaster Duo for recording a multi-location #podcast. But with a little #Loopback magic I've finally got it set up to record audio in #AudioHijack, audio and video in #OBS, and audio on the #Rodecaster, all while my cohost is coming in via #Discord. All with no echo or appreciable lag.

  15. It's been frustrating and fun -- mostly fun -- configuring my MacBook Pro and my new Rodecaster Duo for recording a multi-location #podcast. But with a little #Loopback magic I've finally got it set up to record audio in #AudioHijack, audio and video in #OBS, and audio on the #Rodecaster, all while my cohost is coming in via #Discord. All with no echo or appreciable lag.

  16. "Despite its miniature size, Rodecaster Duo mixers offers multiple microphone inputs, an intuitive touchscreen, and the ability to connect your smartphone via Bluetooth, marking its strength as a powerful, mobile podcasting utility." lttr.ai/ANYxn

    #Rode #Rodecaster #ProClassic #Podcasting #PodcastMixers #ExcellentSoundQuality #SuperiorSoundQuality #RodecasterPro2

  17. The Rodecaster Duo Streaming Podcast Mixer is the ideal partner for podcast creators and content builders on the run.

    Read the full article: Rode Podcast Mixer Comparison
    lttr.ai/AHaD6

    #Rode #Rodecaster #ProClassic #Podcasting #PodcastMixers #ExcellentSoundQuality #SuperiorSoundQuality #RodecasterPro2

  18. The Rodecaster Pro II, Pro Classic, and Duo Streaming Console each offer their unique advantages to cater to a wide range of podcasting needs.

    Read the full article: Rode Podcast Mixer Comparison
    lttr.ai/AETwG

    #Rode #Rodecaster #ProClassic #Podcasting #PodcastMixers #ExcellentSoundQuality #SuperiorSoundQuality #RodecasterPro2

  19. In this episode, we explore the Rodecaster Pro II, Pro Classic, and Duo Streaming Mixer – three audio production consoles that promise to take your podcasting journey to all new heights.

    Read more 👉 lttr.ai/AETwB

    #Rode #Rodecaster #ProClassic #Podcasting #PodcastMixers #ExcellentSoundQuality #SuperiorSoundQuality #RodecasterPro2

  20. I do enough consulting and helping clients with it, I should probably actually own a #Rodecaster Pro so I actually know what I'm talking about. 😆 rode.com/en/interfaces-and-mix #podcasting

  21. I do enough consulting and helping clients with it, I should probably actually own a #Rodecaster Pro so I actually know what I'm talking about. 😆 rode.com/en/interfaces-and-mix #podcasting

  22. I do enough consulting and helping clients with it, I should probably actually own a #Rodecaster Pro so I actually know what I'm talking about. 😆 rode.com/en/interfaces-and-mix #podcasting

  23. I do enough consulting and helping clients with it, I should probably actually own a #Rodecaster Pro so I actually know what I'm talking about. 😆 rode.com/en/interfaces-and-mix #podcasting

  24. I do enough consulting and helping clients with it, I should probably actually own a #Rodecaster Pro so I actually know what I'm talking about. 😆 rode.com/en/interfaces-and-mix #podcasting

  25. Before this gets listed on Trademe. Does anyone in NZ want to buy a Rodecaster Pro or PodMic or Both? They are surplus to requirements now. Rodecaster Pro has the latest firmware installed.

    $750 for Rodcaster Pro - Couriered NZ wide.
    $135 for Podmic - Couriered NZ wide.
    $850 for Both - Couriered NZ wide.
    #NZTwits #NZToots #Rodecaster #Podmic

  26. Before this gets listed on Trademe. Does anyone in NZ want to buy a Rodecaster Pro or PodMic or Both? They are surplus to requirements now. Rodecaster Pro has the latest firmware installed.

    $750 for Rodcaster Pro - Couriered NZ wide.
    $135 for Podmic - Couriered NZ wide.
    $850 for Both - Couriered NZ wide.
    #NZTwits #NZToots #Rodecaster #Podmic

  27. Before this gets listed on Trademe. Does anyone in NZ want to buy a Rodecaster Pro or PodMic or Both? They are surplus to requirements now. Rodecaster Pro has the latest firmware installed.

    $750 for Rodcaster Pro - Couriered NZ wide.
    $135 for Podmic - Couriered NZ wide.
    $850 for Both - Couriered NZ wide.
    #NZTwits #NZToots #Rodecaster #Podmic