MP2 - V2.1 [MP2-563] WASAPI not working for sample rates > 48 kHz (5 Viewers)

[HTPCSourcer]

But i think, it makes sense. OK, it isn't a big task to edit the .xml file, but i think for the most cases 500ms is to much.

I am not saying that it doesn't, however, the effort to add configuration settings to the GUI is significant. I would rather identify a working buffer figure and roll it out with the next MP2 version.

 

[aspik]

the effort to add configuration settings to the GUI is significant

I disagree There is nothing easier than adding a config setting in MP2! Either in the GUI or only in a xml settings file.

 

[HTPCSourcer]

There is nothing easier than adding a config setting in MP2!

OK. May I then put your name in for this for the Final?

 

[aspik]

OK. May I then put your name in for this for the Final?

Ha, ha. No I'm sure hwahrmann can handle this

 

[HTPCSourcer]

Ha, ha. No

Never give up.

I'm sure hwahrmann can handle this

Hhm, I doubt that Helmut will add code for GUI settings.

The most straightforward solution is to identify a working buffer figure and add this to the xml to be rolled in the final. A issue is that this will not overwrite the existing setting for anybody upgrading from Pre or Pre2 - we would need a Wiki entry. But first Helios61 needs to confirm that he can now listen to music sources > 48 kHz.

 

[Helios61]

But first Helios61 needs to confirm that he can now listen to music sources > 48 kHz.

As i said before, unfortunately reducing the buffer doesn't solve the bug. So, we have to wait for Helmut.

 

[hwahrmann]

Have configured the same buffer size (221ms) as in MP1, unfortunately the same issue. Logs are attached.

It is hard coded in MP2, so how did you configure it?
But using the 500ms on MP1 and WASApi failing, confirms my theory.

Seems we need to introduce a configurable buffer.
Maybe not expose it in the UI, but at least allow to set it via a config file (don't know if such exists in MP2 tough)

 

[Helios61]

(don't know if such exists in MP2 tough)

In 'C:\ProgramData\Team MediaPortal\MP2-Client\Config\MediaPortal.UI.Players.BassPlayer.Settings.BassPlayerSettings.xml' you can configure the buffer size. But unfortinately the issue isn't solve.

 

[hwahrmann]

Maybe you can enter it there, but the program is not using it.
the buffer on wasapi init is hard coded.

 

[HTPCSourcer]

So you would need to add a readout of this setting file entry to the code.

I trust that this would be sufficient if we adjusted the buffer value in the xml file in parallel to something that we find to work. GUI setting capabilities can be added later.