MediaPortal Audio renderer - better video playback quality (1 Viewer)

[disaster123]

AW: MediaPortal Audio renderer - better video playback quality

tourettes
has anything changed in the build requirements?
I'm getting:
Error 1 error C2065: 'PKEY_AudioEndpoint_Supports_EventDriven_Mode' : undeclared identifier Accurate_sync\audio renderer\source\MpAudioRenderer.cpp 1461 AudioRenderer

 

[tourettes]

Re: AW: MediaPortal Audio renderer - better video playback quality

@tourettes
has anything changed in the build requirements?
I'm getting:
Error 1 error C2065: 'PKEY_AudioEndpoint_Supports_EventDriven_Mode' : undeclared identifier Accurate_sync\audio renderer\source\MpAudioRenderer.cpp 1461 AudioRenderer

Seems so

DEFINE_PROPERTYKEY(PKEY_AudioEndpoint_Supports_EventDriven_Mode, 0x1da5d803, 0xd492, 0x4edd, 0x8c, 0x23, 0xe0, 0xc0, 0xff, 0xee, 0x7f, 0x0e, 7);

Is defined in mmdeviceapi.h, make sure that is found in there. If not the SDK is most likely too old.

 

[red5goahead]

note : a new WASAPIPreferredDeviceForBitstreaming registry key would be useful.

Yes, but that would require new code as well (bitstreaming or at least detecting the bitstreanable content). This depends highly how ffdshow has been implemented and if it is providing enough information.
But it wll come later...

No no. I'll explain better. a WASAPIPreferredDeviceForBitstreaming that audio renderer use when EnableAC3Encoding=1 and the
WASAPIPreferredDevice when EnableAC3Encoding is disabled. Much much simple you've undestand .

 

[disaster123]

AW: Re: AW: MediaPortal Audio renderer - better video playback quality

@tourettes
has anything changed in the build requirements?
I'm getting:
Error 1 error C2065: 'PKEY_AudioEndpoint_Supports_EventDriven_Mode' : undeclared identifier Accurate_sync\audio renderer\source\MpAudioRenderer.cpp 1461 AudioRenderer

Seems so

DEFINE_PROPERTYKEY(PKEY_AudioEndpoint_Supports_EventDriven_Mode, 0x1da5d803, 0xd492, 0x4edd, 0x8c, 0x23, 0xe0, 0xc0, 0xff, 0xee, 0x7f, 0x0e, 7);

Is defined in mmdeviceapi.h, make sure that is found in there. If not the SDK is most likely too old.

and my environment variable was set to the wrong path.

 

[tourettes]

note : a new WASAPIPreferredDeviceForBitstreaming registry key would be useful.

Yes, but that would require new code as well (bitstreaming or at least detecting the bitstreanable content). This depends highly how ffdshow has been implemented and if it is providing enough information.
But it wll come later...

No no. I'll explain better. a WASAPIPreferredDeviceForBitstreaming that audio renderer use when EnableAC3Encoding=1 and the
WASAPIPreferredDevice when EnableAC3Encoding is disabled. Much much simple you've undestand .

Oh, now I see. I think it would be better to allow three different WASAPI devices to be set

1) for LPCM
2) for AC3
3) for true bitstreaming

...since who knows how the drivers (or the audio renderer) itself behave with some devices

 

[red5goahead]

My tests are over. I will continue from August 30.

 

[tourettes]

My tests are over. I will continue from August 30.

Any new findings / issues spotted?

 

[red5goahead]

My tests are over. I will continue from August 30.

Any new findings / issues spotted?

None, waiting for the ac3 multichannel encoding and an extended audio format support to keep going on after vacation.

 

[robyf]

I just get back from vacation, I will make some more tests of current builds next week to give additional feedback.

 

[red5goahead]

I just get back from vacation, I will make some more tests of current builds next week to give additional feedback.

Ue paisà... Are we switching the duty? MP looks really a serious stuff...