Topic: Media Center 18.0.191: Any playback / WASAPI issues left? (Read 12016 times)

Matt · « **on:** May 29, 2013, 09:17:14 am »

If you are experiencing playback issues using 18.0.191, please post in this thread with details.

Please include:

Output mode you have selected in Options > Audio

Settings in Options > Audio > Output mode settings.

Audio device

OS

Thanks for any help.

walkman666 · « **Reply #1 on:** May 29, 2013, 06:09:52 pm »

I now have the blue icon indicating bitperfect like in former builds, no more "not using enough bits to output the input directly."

Boy, those HDTracks sound very good, too!

thanks!

F1 fan · « **Reply #2 on:** May 29, 2013, 07:26:52 pm »

Still have ticking sound with 24 bit files.16 bit work fine.

Settings ,24bit int in 32bit pack>event style disabled >buffer 100ms

Matt · « **Reply #3 on:** May 29, 2013, 07:29:04 pm »

Quote from: F1 fan on May 29, 2013, 07:26:52 pm

Still have ticking sound with 24 bit files.16 bit work fine.

Settings ,24bit int in 32bit pack>event style disabled >buffer 100ms

It doesn't make sense to me that one input bitdepth would work and another would not, since input bitdepth should be completely detached from output bitdepth. It could even be some file specific issue.

What happens if use the default bitdepth setting of 'Automatic' and leave event style enabled?

Does buffer size matter?

F1 fan · « **Reply #4 on:** May 29, 2013, 07:36:39 pm »

Automatic doesn't help and nothing even 16 bit won't work with event style enabled.Previous to the auto update to .189 the same 24 bit files played flawlessly.

F1 fan · « **Reply #5 on:** May 29, 2013, 07:56:10 pm »

If it's any help the 24 bit files play fine when direct sound instead of WASAPI is selected.

JimH · « **Reply #6 on:** May 29, 2013, 07:58:23 pm »

Quote from: F1 fan on May 29, 2013, 07:36:39 pm

Automatic doesn't help and nothing even 16 bit won't work with event style enabled.Previous to the auto update to .189 the same 24 bit files played flawlessly.

Did you try disabling event style?

F1 fan · « **Reply #7 on:** May 29, 2013, 08:04:57 pm »

Quote from: JimH on May 29, 2013, 07:58:23 pm

Did you try disabling event style?

Yes my post previous to the one you quote shows my settings.

With event style disabled 16 bit works fine 24 bit does not.With event style enabled neither 16 or 24 bit work correctly.

Matt · « **Reply #8 on:** May 29, 2013, 08:21:15 pm »

Quote from: F1 fan on May 29, 2013, 08:04:57 pm

Yes my post previous to the one you quote shows my settings.

With event style disabled 16 bit works fine 24 bit does not.With event style enabled neither 16 or 24 bit work correctly.

If event style doesn't work, reducing the buffer size (try 10ms, etc.) might work.

Do you remember your settings before the recent changes that were working?

Finally, what audio hardware do you have?

rjm · « **Reply #9 on:** May 29, 2013, 08:51:35 pm »

I do not understand WASPI but I tried it. Sound in MC was fine but while MC is running sound from OS and other apps is blocked until I exit MC. I went back to Direct Sound and all ok again.

F1 fan · « **Reply #10 on:** May 29, 2013, 08:56:22 pm »

Quote from: Matt on May 29, 2013, 08:21:15 pm

If event style doesn't work, reducing the buffer size (try 10ms, etc.) might work.

OK looks like 10 ms is the only buffer setting that seems to work with both 16 and 24 bit files.I may still be hearing very periodic ticking but I will give it a full test and report back tomorow.Thanks Matt.

Quote

Do you remember your settings before the recent changes that were working?

Finally, what audio hardware do you have?

Pre update settings ,it was definately WASAPI (non event style) and IIRC correctly 24 bit in 32 pack and what ever the recommended buffer was (100ms?).The hardware is just an HP multi media desk top (running Vista)and using the SPDIF coaxial out of the stock sound card to a stand alone 24bit 96k dac.

6233638 · « **Reply #11 on:** May 29, 2013, 09:36:12 pm »

Quote from: rjm on May 29, 2013, 08:51:35 pm

I do not understand WASPI but I tried it. Sound in MC was fine but while MC is running sound from OS and other apps is blocked until I exit MC. I went back to Direct Sound and all ok again.

That's part of the reason to use WASAPI in Exclusive Mode.

rjm · « **Reply #12 on:** May 29, 2013, 10:16:37 pm »

Quote from: 6233638 on May 29, 2013, 09:36:12 pm

That's part of the reason to use WASAPI in Exclusive Mode.

thanks, never really thought about it but I guess not having Outlook chiming to announce new emails while listening to music could be a good thing

Matt · « **Reply #13 on:** May 29, 2013, 10:42:25 pm »

As mentioned above, WASAPI exclusive mode provides a hardware direct connection. This means the audio hardware will be locked during playback.

More on this here:
http://wiki.jriver.com/index.php/Audio_Output_Modes#Hardware_Direct

Matt · « **Reply #14 on:** May 29, 2013, 10:48:24 pm »

Quote from: F1 fan on May 29, 2013, 08:56:22 pm

OK looks like 10 ms is the only buffer setting that seems to work with both 16 and 24 bit files.I may still be hearing very periodic ticking but I will give it a full test and report back tomorow.Thanks Matt.

Unfortunately some devices will succeed on open, then stall on play with buffers that are too large.

It seems like a driver bug to me, since I would expect the open to fail or playback to work.

I haven't figured out how to auto-configure buffer sizes to work around the problem, so it means there's a manual setting needed with some hardware.

Sorry for the trouble, and thanks for helping pin down the solution.

Matt · « **Reply #15 on:** May 30, 2013, 09:12:14 am »

maid's S/PDIF bitstreaming issue split here:
http://yabb.jriver.com/interact/index.php?topic=81023.0

syn-ack · « **Reply #16 on:** May 30, 2013, 10:00:53 am »

I use ASIO by default, so this isn't really a problem for me, but...

If I use WASAPI now, since .183 and still with .191, I get a ticking/flutter while playing anything.

Schiit Bifrost
Event Style Disabled
Bitdepth Automagic
Buffer 100

Now then, the buffer setting of 100 is the recommended, so that is where I started out. If I increase buffer to 500, the ticking/flutter goes away. That said, this was not a problem in previous builds, I could leave the default WASAPI settings when using non-event style.

Matt · « **Reply #17 on:** May 30, 2013, 10:02:17 am »

@syn-ack
Does WASAPI with event style and 10ms of buffering work?

syn-ack · « **Reply #18 on:** May 30, 2013, 10:30:56 am »

Matt,

No it does not, but I do not believe the Schiit Bifrost is compatible at all with Event Style, as I have never been able to make it work with any player, JRiver or Foobar2000.

Stax · « **Reply #19 on:** May 30, 2013, 10:42:01 am »

Hallo,
Since update .189 Wasapi is not working anymore. Update.191 makes no difference. Only working option
is direct sound.

I'm running windows 7, spdif output to firestone fubarIV (via firestone Bravo) external
DAC.

Now funny thing is, Media Center 17, which is still on my computer is having no problems. I've read this
thread but can't find the cure. Any suggestions?

I'm playing .wav and .flac only.

Thanks in advance

JimH · « **Reply #20 on:** May 30, 2013, 10:48:07 am »

Quote from: Stax on May 30, 2013, 10:42:01 am

Hallo,
Since update .189 Wasapi is not working anymore. Update.191 makes no difference. Only working option
is direct sound.

I'm running windows 7, spdif output to firestone fubarIV (via firestone Bravo) external
DAC.

Now funny thing is, Media Center 17, which is still on my computer is having no problems. I've read this
thread but can't find the cure. Any suggestions?

I'm playing .wav and .flac only.

Thanks in advance

Try both WASAPI's. The terminology changed. The new WASAPI is the old WASAPI Event Style. This is documented in a thread here called "New WASAPI".

Try reducing the buffer size.

Stax · « **Reply #21 on:** May 30, 2013, 12:56:52 pm »

Hi Jim,
Thanks for your fast reply!!
Both Wasapi,s?? I only see one in ,,18,,. Minimal hardware size won,t do! I can check allmost all the options with ,,17,, but all I see that ,,18,, is giving output (meters) but
I hear nothing?! See that my DAC is having troubles by the changing of the ,,lights,, But then again media center 17 is giving no problems,Wasapi (not event style) - spdif direct.

So what to do? Go back to ,,17,, or is it possible to undo these ,,updates? Mind you, I,m not sarcastic, love this player!!

syn-ack · « **Reply #22 on:** May 30, 2013, 01:12:32 pm »

Stax,

Did you Disable Event Style in Options > Audio > Audio Output > Output mode settings?

JimH · « **Reply #23 on:** May 30, 2013, 01:23:01 pm »

http://yabb.jriver.com/interact/index.php?topic=80614.0

jmschnur · « **Reply #24 on:** May 30, 2013, 02:37:24 pm »

I just installed an hrt media streamer plus in a windows 7 64 bit system. I am using JC river version MC 18 version 191.

Using direct sound the JR river volume control works. Waspi gives me full volume with no control.
I am outputting the streamer directly to my Hafler amp and then to my speakers.

Any advice?

JimH · « **Reply #25 on:** May 30, 2013, 02:39:07 pm »

It's WASAPI, not Waspi.

Try a different volume setting. Click on the speaker icon in the upper left corner.

Stax · « **Reply #26 on:** May 30, 2013, 02:50:27 pm »

Jim ,
Disabled, abled, tried both, no good. The link you gave is a long read, read it later, but.....
am I the only one??? If so , it guess must be the DAC,
Thanks again, I,ll be back...

JimH · « **Reply #27 on:** May 30, 2013, 04:34:28 pm »

Try System and Internal.

Chauncey · « **Reply #28 on:** May 30, 2013, 06:38:22 pm »

WASAPI (Event Style enabled; exclusive access)
Player: OPP1103-RPT (Intel Display Audio); from HDMI out on Mac Mini
OS: Win 7 (via Bootcamp)

I cannot reliably play 192/24 audio files. I've posted a log here: http://yabb.jriver.com/interact/index.php?topic=80700.0
I'm not sure if I did the log file correctly; it gets weird toward the end.

Matt · « **Reply #29 on:** May 30, 2013, 07:35:05 pm »

Quote from: Chauncey on May 30, 2013, 06:38:22 pm

WASAPI (Event Style enabled; exclusive access)
Player: OPP1103-RPT (Intel Display Audio); from HDMI out on Mac Mini
OS: Win 7 (via Bootcamp)

I cannot reliably play 192/24 audio files. I've posted a log here: http://yabb.jriver.com/interact/index.php?topic=80700.0
I'm not sure if I did the log file correctly; it gets weird toward the end.

Please try different buffer size settings in Options > Audio > Output mode settings, and let us know if it helps at all.

F1 fan · « **Reply #30 on:** May 30, 2013, 09:21:11 pm »

Quote from: Matt on May 29, 2013, 10:48:24 pm

Unfortunately some devices will succeed on open, then stall on play with buffers that are too large.
It seems like a driver bug to me, since I would expect the open to fail or playback to work.

I haven't figured out how to auto-configure buffer sizes to work around the problem, so it means there's a manual setting needed with some hardware.

Yeah so far the 10ms buffer size seems to be operating fine for both 16 and 24 bit.

Quote

Sorry for the trouble, and thanks for helping pin down the solution.

Thank you for the solution and the continued development of this great media player.

Stax · « **Reply #31 on:** May 31, 2013, 03:09:55 am »

Hi Jim,
Back and trying again. System or internal? You mean spdif or default? Makes no difference, see that
media center ,,opens,, the song (counting seconds and ,,meters moving,, but no sound and the light
on my DAC flickering. 16/44 , 24/96 etc. nothing. I haven,t got a clue......, you?

Stax · « **Reply #32 on:** May 31, 2013, 03:37:37 am »

OK I,m halfway through the thread you named and found that Wasapi (event style checked or not) works with 16/44 and 24/96 using 24bit integer in a 32bit
package. 192 files won,t play. Using the 16bit option gives sound with 24/96 no sound with 24/192 and horrible sound with 16/44 files.
I,m out of my (bit) depts ......

Stax · « **Reply #33 on:** May 31, 2013, 04:41:42 am »

OK I,m through reading the complete thread. Nice to know I,m not the only one with this problems. Guess I switch back to Media Center 17 as default and wait for a next update.
If I (my case) can be of any assitance, let me know. For now I start listening to music again...........

digi340 · « **Reply #34 on:** May 31, 2013, 05:10:21 am »

OS WINDOWS 8 PRO
I have problems after the update to version 18.0.191

Wasapi settings:

Device: Soundmax
Disable event Style - unchecked

Bitdepth: automatic

1. from internet radio (radio extra MP3 STREAM 320 KBS)

- output: 44.1khz 24bit 2ch using WASAPI direct conection

Audio Path

input: 44.1khz 2ch from source format MP3

output: 44.1khz 24bit 2ch using WASAPI direct connection

From DTS CD or native DTS file or AC3 file

input: 48khz 32 bit 6ch from source format DTS
output: 48khz 24bit 6ch using WASAPI (not using enough bits to output the input directly)

In previous version listen DTS CD, DTS native file and AC3 file in Wassapi Event style, hardware direct connection, and AAC stream and MP3 stream not in hardware direct connection "not using enough bits to output the input directly' .
In latest version listen DTS CD, DTS native file and AC3 file in Wassapi Event style not hardware direct connection "not using enough bits to output the input directly' , and AAC stream and MP3 stream hardware direct connection .

JimH · « **Reply #35 on:** May 31, 2013, 06:27:52 am »

Quote from: Stax on May 31, 2013, 04:41:42 am

OK I,m through reading the complete thread. Nice to know I,m not the only one with this problems. Guess I switch back to Media Center 17 as default and wait for a next update.
If I (my case) can be of any assitance, let me know. For now I start listening to music again...........

Did you try reducing the buffer size?

JimH · « **Reply #36 on:** May 31, 2013, 06:35:29 am »

Quote from: F1 fan on May 30, 2013, 09:21:11 pm

Yeah so far the 10ms buffer size seems to be operating fine for both 16 and 24 bit.Thank you for the solution and the continued development of this great media player.

We're seeing this a lot now. For whatever reason, the very small buffer seems to help.

Thanks for the report.

Snafujg · « **Reply #37 on:** May 31, 2013, 07:07:41 am »

Quote from: Stax on May 30, 2013, 02:50:27 pm

Jim ,
Disabled, abled, tried both, no good. The link you gave is a long read, read it later, but.....
am I the only one??? If so , it guess must be the DAC,
Thanks again, I,ll be back...

You're not the only one. I have the same issue. Windows 7, Emotiva XDA2 DAC. All was working great till .189. Now, all I get is jitter/flutter and can't even listen to my music. Only way it works is if I have Output Mode as Direct Sound. WASAPI, with event style disabled, flutters. I've tried each Bitdepth setting, none of them resolved the issue. I changed the Buffering to 50ms, that made it even worse.

Can I go back to a different release? It was perfect before. Now, I can't use JRiver MC. Listening in Direct Sound just isn't the same quality as listening in WASAPI. I only have FLAC and WAV files.

JimH · « **Reply #38 on:** May 31, 2013, 07:51:51 am »

Try a very small buffer size. 10ms seems to work for several people.

Stax · « **Reply #39 on:** May 31, 2013, 07:56:16 am »

Jim tried all buffer settings nothing changes. I,m back on 17 now hopefully for the time beeing...

JimH · « **Reply #40 on:** May 31, 2013, 08:08:46 am »

Did you try 10 ms?

Stax · « **Reply #41 on:** May 31, 2013, 08:17:50 am »

YES! Both event checked and unchecked!

Snafujg · « **Reply #42 on:** May 31, 2013, 09:51:57 am »

I had to do a system restore due to Windows 7 crash. This happened to restore MC to 18.0.175 with all the settings I had before. Now MC is performing flawlessly.

Matt · « **Reply #43 on:** May 31, 2013, 10:36:17 am »

I believe the WASAPI (non event mode) issues will be fixed next build:
Fixed: WASAPI with event style disabled could buffer shortfall unnecessarily in the last few builds (normally sounds like ticks).

I'm very sorry for the problems.

JimH · « **Reply #44 on:** May 31, 2013, 05:03:59 pm »

Please download 18.0.193 and use this thread for any problems.
http://yabb.jriver.com/interact/index.php?topic=81052.0

INTERACT FORUM

Author Topic: Media Center 18.0.191: Any playback / WASAPI issues left? (Read 12016 times)