Automatic configuration from Nuvola of Sample Format and Sample Rate in PulseAudio.

[bordelaque]

For Qobuz it would be fantastic. Volumio gets there why not Nuvola

Thanks

Damien

[jiri-janousek]

Hello @bordelaque. I have no idea what exactly do you request and why it that needed. Could you elaborate more? Thanks.

[bordelaque]

Hello Jiri,

Today, when i listen music on my system, each tracks are differents ! Some tracks are 24bits, 192Khz, some tracks are 24bits, 96Khz, some track are 24bits 48Khz, some tracks are 16bits, 44,1Khz, ...... For exemple: if I'm listening a track 16bits 44,1Khz. Before i need to configure the File \etc\pulse\daemon.conf with : default-sample-format = s16le default-sample-rate = 44100 and after I write in console : pulseaudio -k pulseaudio -D If the next track is 24bits 192Khz Before i need to change the configuration of the file daemon.conf like this : default-sample-format = s24le default-sample-rate = 192000 and after I write in console : pulseaudio -k pulseaudio -D

In fact, it's not easy.... If Nuvola would can configure automaticaly the file daemon.conf ....it would be fantastic !!! Perhaps ,there are others solutions.... Firefox make this option but only 44,1Khz and 48Khz 😥 Look in attachment, there are some photos. Thank you for your work.

Best regards

Damien GRIMAUD

Le lun. 22 mars 2021 à 08:40, Jiří Janoušek @.***> a écrit :

Hello @bordelaque https://github.com/bordelaque. I have no idea what exactly do you request and why it that needed. Could you elaborate more? Thanks.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tiliado/nuvolaplayer/issues/717#issuecomment-803839537, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQPX4HZJKAME3ZKBXEP4BJTTE3X77ANCNFSM4ZRWY7LA .

[jiri-janousek]

Hello @bordelaque. Could you attach the photos via GitHub website? It cannot be done via e-mail

[bordelaque]

[jiri-janousek]

I'm closing this ticket as Nuvola Player has discontinued active development. We are going to provide only integration bug fixes on a best-effort basis until the final End-of-Life on December 31, 2022. I'm sorry that I haven't managed to resolve this ticket in time.