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

[tourettes]

I'm trying to play 25 fps PAL live TV with this patch. Setting the monitor to 60 Hz is OK but when trying 50 Hz the audio is all messed up. It's looping every second about three times. When watching tennis is sounds like he hits the ball three times.

Does switching between:

13-07-2010 17:00:41.745 [960]Audio endpoint 0: "SPDIF Out (2- Creative SB X-Fi)" ({0.0.0.00000000}.{55bdf35f-5e03-4b0f-9fb6-e31b6a4e848f})
13-07-2010 17:00:41.745 [960]Audio endpoint 1: "Speakers (2- Creative SB X-Fi)" ({0.0.0.00000000}.{bd3bb6f7-7189-4fdb-b62e-6d19f1aa659c})

Change anything? You can change the "WASAPIPreferredDevice" value in registy to contain either

{0.0.0.00000000}.{bd3bb6f7-7189-4fdb-b62e-6d19f1aa659c} or {0.0.0.00000000}.{bd3bb6f7-7189-4fdb-b62e-6d19f1aa659c}

Or with more ease just to change the default audio device in control panel.

 

[OnkelChris]

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

Oh, now I see... please don't post test results with modified binaries unless you are explicitly stating in the posting exactly what has been modified. It is already too hard for me to guess from peoples error descriptions what might be happening (describing audio / video issues with a written language is not an easy task. Let alone understanding it).

So, for you it is working nicely currently? Could you share your codec and HW setup? We need to try to collect some information on the setups that are currently working and the ones that are failing.

Of course.. I'm sorry... It's not my day... :sorry:

as mentioned before, nothing changed inside the dshowhelper except the stats, that they are ION compatible! (and the refresh rate estimation, which doesn't affect your renderer, I guess)

Everything was fine. So no error reported by me

My Hardware:
ION 330
graphic, audio & co onboard

Codecs used:
Audio: MPC (audio 2 channel stereo, 16 bit)
Video: MS DTV-DVD

 

[red5goahead]

Could you 1) provide the EVR and audio renderer logs for 75Hz and 50Hz cases 2) test how it behaves on 50Hz

on the 50HZ the problem is the same. maybe less adj and in this case showed by the info screen I choosed to play about 10K frames .

note in this case the desynch is about 3-4 seconds.

attach another test log of 50HZ. case and 75 hz. (1 min. and an half each)

could be usefull the reclock system clock correction during this test?

 

[tourettes]

13-07-2010 22:07:59.124 [f94]DoRenderSampleWasapi Output buffer is NULL
13-07-2010 22:08:00.984 [f94]DoRenderSampleWasapi Output buffer is NULL
13-07-2010 22:08:05.924 [f94]DoRenderSampleWasapi Output buffer is NULL
13-07-2010 22:08:08.194 [f94]DoRenderSampleWasapi Output buffer is NULL
13-07-2010 22:08:13.575 [f94]DoRenderSampleWasapi Output buffer is NULL
13-07-2010 22:08:40.625 [f94]DoRenderSampleWasapi Output buffer is NULL
13-07-2010 22:08:48.060 [f94]DoRenderSampleWasapi Output buffer is NULL
13-07-2010 22:08:51.355 [f94]DoRenderSampleWasapi Output buffer is NULL
13-07-2010 22:09:07.355 [f94]DoRenderSampleWasapi Output buffer is NULL
13-07-2010 22:09:29.633 [f94]DoRenderSampleWasapi Output buffer is NULL
13-07-2010 22:09:30.460 [f94]DoRenderSampleWasapi Output buffer is NULL

Both logs are showing that there isn't audio buffer available to be rendered. Basicly meaning that the WASAPI device provides a buffer than won't exists (dont ask from me how it could happen).

Update: in addition to that there is different results with the refresh rate detection on reclock and the EVR presenter. EVR presenter detects the refresh rate as 75 Hz, where as reclock as 75.09 Hz. That would cause 1.002 x difference in the durations (but that is not as much as you are seeing).

Update #2: "Because of an error in the implementation, the WASAPI may return an invalid pointer." http://kbalertz.com/957569/application-WASAPI-crash-GetBuffer-function.aspx - could you check if that OS update has been installed? Most likely it is installed since you seem to have SP2.

 

[tourettes]

on the 50HZ the problem is the same. maybe less adj and in this case showed by the info screen I choosed to play about 10K frames .

Could you test the attached .ax? (no one else should try this one ). It adds some polling if the WASAPI device does return a NULL buffer (which it shouldn't return).

 

[red5goahead]

on the 50HZ the problem is the same. maybe less adj and in this case showed by the info screen I choosed to play about 10K frames .

Could you test the attached .ax? (no one else should try this one ). It adds some polling if the WASAPI device does return a NULL buffer (which it shouldn't return).

Yes. Doesn't work. Start play but after 5-10 second the sound stop. and I unable to use stop or exit MP normally (i kill the process). in attach the log.

 

[tourettes]

on the 50HZ the problem is the same. maybe less adj and in this case showed by the info screen I choosed to play about 10K frames .

Could you test the attached .ax? (no one else should try this one ). It adds some polling if the WASAPI device does return a NULL buffer (which it shouldn't return).

Yes. Doesn't work. Start play but after 5-10 second the sound stop. and I unable to use stop or exit MP normally (i kill the process). in attach the log.

Oh, my bad. I did create an infinite loop if no buffer is available. I'll try to provide a new binary, which would try to release the invalid buffer before asking for the new one, later this evening.

I think the drivers are a bit broken, since GetBuffer call to WASAPI is returning no error and still it manages to produce invalid buffer for the driver side that the actual audio data should be written. Good thing is that even MS thinks the GetBuffer should always provide a valid buffer since their example code is assuming that if no errors are reported the buffer will be valid.

In the mean time could you check if there are new audio drivers available and another thing would be to try a different audio chip if possible.

 

[red5goahead]

In the mean time could you check if there are new audio drivers available and another thing would be to try a different audio chip if possible.

Ok. the chip is the C-Media CMI8768+ (brand Terratec). There is no update avaiable but I'll try to use the Auzentech ones (that is older)

 

[vuego]

Does switching between:

13-07-2010 17:00:41.745 [960]Audio endpoint 0: "SPDIF Out (2- Creative SB X-Fi)" ({0.0.0.00000000}.{55bdf35f-5e03-4b0f-9fb6-e31b6a4e848f})
13-07-2010 17:00:41.745 [960]Audio endpoint 1: "Speakers (2- Creative SB X-Fi)" ({0.0.0.00000000}.{bd3bb6f7-7189-4fdb-b62e-6d19f1aa659c})

Change anything? You can change the "WASAPIPreferredDevice" value in registy to contain either

{0.0.0.00000000}.{bd3bb6f7-7189-4fdb-b62e-6d19f1aa659c} or {0.0.0.00000000}.{bd3bb6f7-7189-4fdb-b62e-6d19f1aa659c}

Or with more ease just to change the default audio device in control panel.

Yeh, I'm using a Creative SoundBlaster X-Fi Platinum with latest driver 2.18.0015.

I already have Speakers set as default but I tried setting the value in the registry anyway. Unfortunately it didn't help.

 

[red5goahead]

I think the drivers are a bit broken, since GetBuffer call to WASAPI is returning no error and still it manages to produce invalid buffer for the driver side that the actual audio data should be written. Good thing is that even MS thinks the GetBuffer should always provide a valid buffer since their example code is assuming that if no errors are reported the buffer will be valid.
In the mean time could you check if there are new audio drivers available and another thing would be to try a different audio chip if possible.

Please note this: I tried to install the wasapi plugin for FooBar2000 to test that kind of framework. It work .