Collection of Audio Renderer fixes for 1.3.0 beta (1 Viewer)

[tourettes]

Don't use MPAR, found it to be unstable as it is vey much beta.

And it will stay like that if no one will tell what breaks it. Please report the MPAR issues, it is not beta anymore and it is part of the MP builds (has been half years already). Of course no one should be using it to speed up the live tv if that is the case.

 

[SciDoctor]

Don't use MPAR, found it to be unstable as it is vey much beta.

And it will stay like that if no one will tell what breaks it. Please report the MPAR issues, it is not beta anymore and it is part of the MP builds (has been half years already). Of course no one should be using it to speed up the live tv if that is the case.

I applaud anyone who works on improving any aspect of MP and help where I can.

As an aside to this threads main theme MPAR causes this on the whole with my set-up (could be ATI drivers as ths seems to be the main thrust of pointed fingers for problems everywhere) and I tend to not use it or test it, whch I apologise for.



EDIT. something amiss I think! or should it look like this.(EDIT cured by removing MP audioswitcher)


And when it does connect it fails on media switching. second logs (EDIT cured on the whole due to use of GRAPHSTUDIO and lock on MPAR ?)

FOUND one problem that is easy to fix MPAR isn't connecting to AUDIO switcher and when dissabled MPAR is connected and improves matters.

I will continue some more MPAR testing and post feedback.

If MPAR is present and in usein MP and also in connections in GRAHSTUDIO then MP freezes on media change unless you disconnect GRAPHSTUDIO.

Volume control breaks on BLURay playback and then requires MP restart to get it back. third logs This is a baffling one. EDIT infact volume control isn't working at all ? should there be a different setting to choose in mpconfig ?
EDIT. switching to 'master volume' in mp config brought back volume control.( Wave was default) Although this has obvious drawback as the volume control is now sytem global. obviously.

 

[mhoogenbosch]

Don't use MPAR, found it to be unstable as it is vey much beta.

lots of text

Volume control breaks on BLURay playback and then requires MP restart to get it back. third logs This is a baffling one. EDIT infact volume control isn't working at all ? should there be a different setting to choose in mpconfig ?

Volume control doesn't work because of what i know it passes the RAW audio, so you should adjust the volume at your receiver or TV. I don't use a receiver and my son broke my harmony so i only use the mediacenter remote. Not convienent to use the TV remote for only the volume. For this i don't use (and have never tried) mepo audio render.
I also think we're getting a bit offtopic

 

[mhoogenbosch]

Back on topic.

From very recent testing.

If using MPAR you may find AV sync not spot on, if so then the reg setting ' EnableDWMAudioDelayComp ' set to '1' cures this completely.

I have this set to '0' with default directsound normaly without issues so ensure you try this reg setting if you experince AV syn not so good.

ive changed to the mepo audorender, as i was saying it passes the raw audio, i'm not entirly right. ... in my memory ive tested it and it was like that. but now ive enabled the mepo audiorender but i can change the volume with my remote control. Maybe it has something to do with the setting within mepo, ive set it to master volume control.

 

[SciDoctor]

Back on topic.

From very recent testing.

If using MPAR you may find AV sync not spot on, if so then the reg setting ' EnableDWMAudioDelayComp ' set to '1' cures this completely.

I have this set to '0' with default directsound normaly without issues so ensure you try this reg setting if you experince AV syn not so good.

ive changed to the mepo audorender, as i was saying it passes the raw audio, i'm not entirly right. ... in my memory ive tested it and it was like that. but now ive enabled the mepo audiorender but i can change the volume with my remote control. Maybe it has something to do with the setting within mepo, ive set it to master volume control.

Yes 'wave out' must/maybe output raw and switching to the sytem global volume control via 'master volume' in mp config works around this. Odd and possibly a deal breaker if you use the system for more than MP causing mismatched volume across different running apps. Not a real problem as I see it on a dedicated HTPC but an area which MPAR possibly could address.

 

[tourettes]

Off topic / MPAR related discussion should be moved to other thread.

Few notes about MPAR:
1) it doesn't currently implement volume control at all. This is because you get better audio quality when you do the volume control as close as possble to the speakers (amp in this case) and also I haven't had enough free time to implement that.
2) Audio switcher is not compatible with MPAR. It will try to push always the bitstreamed formats as far as I remember. I did debug that few years ago in the beginning of MPAR development, but I didn't figure out how to fix it properly.

Could some moderator move the MPAR related talk to different thread? More specific issues (like Blu-ray causing a complete failure should be discussed there).

update: in @SciDoctor's MPAR logs there is a fatal failure. WASAPI device is not initialized ok - CWASAPIRenderFilter::Render thread Error, device not initialized . Probably a bug in MPAR, but surely it will cause huge amount of issues (basicly nothing should work ).

 

[mhoogenbosch]

Off topic / MPAR related discussion should be moved to other thread.

Few notes about MPAR:
1) it doesn't currently implement volume control at all. This is because you get better audio quality when you do the volume control as close as possble to the speakers (amp in this case) and also I haven't had enough free time to implement that.
2) Audio switcher is not compatible with MPAR. It will try to push always the bitstreamed formats as far as I remember. I did debug that few years ago in the beginning of MPAR development, but I didn't figure out how to fix it properly.

Could some moderator move the MPAR related talk to different thread? More specific issues (like Blu-ray causing a complete failure should be discussed there).

update: in @SciDoctor's MPAR logs there is a fatal failure. WASAPI device is not initialized ok - CWASAPIRenderFilter::Render thread Error, device not initialized . Probably a bug in MPAR, but surely it will cause huge amount of issues (basicly nothing should work ).

But master volume appearently works. Planning to upgrade to 1.3b tonight, i know there is a lot of work done since 1.3a so my experience at the moment isn't representive. Seems to work fine though, i'll switch to mepo audio render completely tonight ( as long as master audio control keeps working and i dont need another remote to control the volume). My amp is planned for the second half of 2013 ))

 

[tourettes]

But master volume appearently works. Planning to upgrade to 1.3b tonight, i know there is a lot of work done since 1.3a so my experience at the moment isn't representive. Seems to work fine though, i'll switch to mepo audio render completely tonight ( as long as master audio control keeps working and i dont need another remote to control the volume). My amp is planned for the second half of 2013 ))

Master volume cannot work with WASAPI exclusive mode. OS or drivers aren't allowed to touch the audio signal at all. So if volume control seems to work either there is a bug in OS (very unlikely), bug in drivers (not so likely) or MPAR is not connecting in the graph (most likely).

 

[SciDoctor]

Master volume works here to . VISTA 32. MPAR selected and shown connected in graph.



If this is a bug (a good bug) in MPAR then the source of it may help in getting 'wave out' working in the future, although this is not paramount in your design premise.

 

[tourettes]

Master volume works here to . VISTA 32. MPAR selected and shown connected in graph.

View attachment 118202

If this is a bug (a good bug) in MPAR then the source of it may help in getting 'wave out' working in the future, although this is not paramount in your design premise.

Not a bug in MPAR, but most likely in drivers which aren't working as MS specification says they should be. The bad thing is that those drivers are now able to run the audio quality - if we were passing a real bitstream with WASAPI exclusive mode they would be causing the signal to be pure noise. WASAPI exclusive mode is defined to pass 1:1 audio stream from the application that uses. OS nor drivers aren't allowed (by design) altering it in any way.

Wave out cannot be used as device for WASAPI. WASAPI will communicate the drivers directly.

About volume control, it will be implemented at some point to the MPAR itself as that is the only way how it can be done on correctly working drivers.

from logs

29-12-2012 12:08:30.858 [ e34] WASAPIExclusive: 1