volroon 1.0.4

[charliesjc]

No description provided.

[charliesjc]

@balbuze can we move my plugin to stable channel?

[balbuze]

hello!
Can you re explain me why you don't use 'volumio' as output device?

[charliesjc]

Hello! I don't use 'volumio' as the output device because it's physically impossible when using the Bridge software provided by Roon. As per their blurb they insist on using direct hardware access to the audio device. I.e. they address hw:0, hw:1 etc. It's the same way as the RoonBridge plugin on Volumio. The only way it will change is if Volumio talks to Roon and works something out with them to change it (licensing).

I do find it weird though that Volumio's new streamers etc are shown as Roon Ready when to be able to do that means that Volumio's control of the audio device has to be completely ignored by the Roon software.

[charliesjc]

@balbuze ```
https://help.roonlabs.com/portal/en/kb/articles/audio-on-linux

[charliesjc]

@balbuze Bump

[charliesjc]

@balbuze I saw this previously had a merge conflict on the gitignore. Should be sorted now.

[LarsGrootkarzijn]

Hello! I don't use 'volumio' as the output device because it's physically impossible when using the Bridge software provided by Roon. As per their blurb they insist on using direct hardware access to the audio device. I.e. they address hw:0, hw:1 etc. It's the same way as the RoonBridge plugin on Volumio. The only way it will change is if Volumio talks to Roon and works something out with them to change it (licensing).

I do find it weird though that Volumio's new streamers etc are shown as Roon Ready when to be able to do that means that Volumio's control of the audio device has to be completely ignored by the Roon software.

In a Roon Ready client one can select the output device which in the case of those devices is 'volumio'. The Roon Ready Client differs a lot regarding device handling compared to Roon Bridge.

[charliesjc]

Hello! I don't use 'volumio' as the output device because it's physically impossible when using the Bridge software provided by Roon. As per their blurb they insist on using direct hardware access to the audio device. I.e. they address hw:0, hw:1 etc. It's the same way as the RoonBridge plugin on Volumio. The only way it will change is if Volumio talks to Roon and works something out with them to change it (licensing).

I do find it weird though that Volumio's new streamers etc are shown as Roon Ready when to be able to do that means that Volumio's control of the audio device has to be completely ignored by the Roon software.

In a Roon Ready client one can select the output device which in the case of those devices is 'volumio'. The Roon Ready Client differs a lot regarding device handling compared to Roon Bridge.

Well either way it looks like my plugin will never make it to stable. The silence is deafening.

[volumio]

@balbuze can we resume works on this plugin? it seemed very promising!

[balbuze]

how do you want to proceed?

[charliesjc]

how do you want to proceed?

Is this directed at me? The last comment I received was to ask me why I don't use 'volumio' as the output. You and I both know it's because Roon won't allow anything else. This was followed by almost a year of radio silence. You made it clear how this will go.

[balbuze]

hello,
Sorry for the delay... We misunderstood.
v1.0.4 as beta is available since september 22th 2022.
Most of the time, after beta and feedback from users, if the author says my plugin is ready, it can be release as stable, then we go! Maybe I missed this.
So, now is it ok for you and users? https://community.volumio.com/t/plugin-volroon-roon-bridge-plugin-with-metadata-and-control/58119/27

[charliesjc]

I stopped using Volumio shortly after no response regarding this. I will need to try the latest version on a rPi in the coming weeks and see if and what changes my plugin might need before requesting you move it to stable...