INTERACT FORUM
More => Old Versions => JRiver Media Center 18 for Windows => Topic started by: JimH on May 31, 2013, 05:02:15 pm
-
We recently changed the terminology for WASAPI.
It's just WASAPI now. To get the old WASAPI (non Event Style), you must check the option called "Disable Event Style". It's in the second section of Audio Settings.
We made an error at the same time that caused a lot of DAC's not to work. Ticking, etc. That is fixed in build 193.
Please tell us what you find. Thanks.
-
193 working fine now with 100ms buffer on both 16 and 24 bit files.Thanks Gents.
-
Thanks for the report. And thanks also for your patience.
-
Tried Wasapi event style unchecked (and checked), 100ms (and10ms), no good, same problem. No sound...., see meters moving, counting of seconds of the song,
and flickering lights on my DAC. Got to go to work now, be back monday evening.
-
I have an Audio-gd NFB-15.1 DAC with USB interface (Tenor TE8802).
With event style disabled, changing audio tracks with different sampling rates makes the player stay stopped while showing it is in play mode but no sound is heard and the time indicator remains in zero. Clicking on stop and play buttons makes the song be played.
Foobar has no such a problem. I am using WASAPI support component V2.1 which, I believe, is not event style.
Movies don't play any sound with event style disabled. The movie image is shown running normally but the audio is mute.
This was already happening with previous MC releases and still happens with 18.0.193.
I'm using Audio-gd driver V1.0.
Thanks.
-
What's worth trying if your having Wasapi problems, is making sure windows services AudioEndpointBuilder and
Audiosrv are enabled.
-
Gents,
(New to Forums - doing my best . . .)
My computer suffered incredible static with build 189, as you addressed in the "Humble Apology" post. I changed my update channel settings to "Latest" and tried the 193 build. Oops, I still have the same problem. :(
The "Humble Apology" post said I could change settings myself, but the provided instructions "It's in Audio options in the second section, called "Output Mode Settings" are vague at best. Under TOOLS, OPTIONS, AUDIO, I don't find any place to set bit-depth. Could you please post some more explicit point-and-click directions to the window I'm looking for?
I've turned off auto updates, and reverted to Build 175. But I guess I'm stuck here for now.
------------------
I'm running Win XP SP3 with all the updates, using a Soundblaster Audigy 2 card. There's nothing special about the machine that I can imagine would be causing MC to trip up.
Mike
-
Try setting MC to "24 bits in a 32 bit package" in the audio options.
-
Could you please post some more explicit point-and-click directions to the window I'm looking for?
(http://www.abload.de/img/audio1btrtv.png) (http://www.abload.de/img/audio-22yoqs.png)
EDIT: Sorry, I just realized that you said you were on Windows XP - you will not have WASAPI available. But the settings are roughly the same no matter what your output mode is.
-
I'm running Win XP SP3 with all the updates, using a Soundblaster Audigy 2 card. There's nothing special about the machine that I can imagine would be causing MC to trip up.
Welcome.
Could you describe your audio settings and details in 'Audio Path' when using the older build?
Since XP does not have WASAPI, I'm guessing you're using DirectSound. Is that correct?
-
I have an Audio-gd NFB-15.1 DAC with USB interface (Tenor TE8802).
With event style disabled, changing audio tracks with different sampling rates makes the player stay stopped while showing it is in play mode but no sound is heard and the time indicator remains in zero. Clicking on stop and play buttons makes the song be played.
Foobar has no such a problem. I am using WASAPI support component V2.1 which, I believe, is not event style.
Movies don't play any sound with event style disabled. The movie image is shown running normally but the audio is mute.
This was already happening with previous MC releases and still happens with 18.0.193.
I'm using Audio-gd driver V1.0.
Thanks.
Updating Foobar2000 and WASAPI support component makes Foobar having similar issues.
May be the issue I reported is related to the driver not to MC.
Thanks.
-
Since the update WASAPI to start,There is no good used of WASAPI.I did not get anything useful from the Administrator Help.The answer is only a problem on your setup.Now the question:
WASAPI Mode:Right speaker no sound,Pause Noise appears on the right speaker.Replaced direct sound everything is normal.The problem is obviously WASAPI.
Sound Card:VIA VT2021
Drive:1700
System:windows 7 64bit SP1
-
Since the update WASAPI to start,There is no good used of WASAPI.I did not get anything useful from the Administrator Help.The answer is only a problem on your setup.Now the question:
WASAPI Mode:Right speaker no sound,Pause Noise appears on the right speaker.Replaced direct sound everything is normal.The problem is obviously WASAPI.
Sound Card:VIA VT2021
Drive:1700
System:windows 7 64bit SP1
Please confirm that you have installed MC 18.0.193.
-
This may not be an issue specific to this with this version, but the Audio Analyzer does not work with DSD content. I noticed this on the previous version as well.
I am now able to play DSD content remotely with version 18.0.193 (using a Wyred 4 Sound DAC2-SE, WASAPI/32bit Integer).
There is @ 1 second of static when switching tracks remotely. If I switch the DSD tracks locally, there is no static at track switch time.
-
This may not be an issue specific to this with this version, but the Audio Analyzer does not work with DSD content. I noticed this on the previous version as well.
If you play as PCM, Analyzer works.
If you bitstream, you are bypassing any audio processing or analysis, including Analyzer.
-
The bit depth setting “automatic” suggest the system will take care of the right bit depth.
When playing to a Bluetooth device I didn’t get any sound with this setting.
Had to set it to 16 bit integer manually
-
Welcome.
Could you describe your audio settings and details in 'Audio Path' when using the older build?
Since XP does not have WASAPI, I'm guessing you're using DirectSound. Is that correct?
Yes. I'm using DirectSound. WASAPI is not listed as an option.
Under "Output Mode Settings . . ." , all I have is a drop-down box under "Device", and a slider for "Buffering". Bit-depth isn't included in that dialog box.
I've tried to paste a cropped screensot of my dialog box, but the "insert image" button doesn't work intuitively, and I can't figure it out. I "attached" the jpg, but it doesn't show when I "Preview" my response, so maybe it's just not my day . . :(
Mike
-
Just a feedback on the inability to playback DSD with Meitner MA-1 using build JRiver 18 189.
Now loaded with Build 193, switch from Kernal Streaming to WASAPI. Now everything working again.
Thank you for your support.
(Audio)
-
Try setting MC to "24 bits in a 32 bit package" in the audio options.
This setting won't play 24/192! ,for me that is.
-
Yes. I'm using DirectSound. WASAPI is not listed as an option.
Under "Output Mode Settings . . ." , all I have is a drop-down box under "Device", and a slider for "Buffering". Bit-depth isn't included in that dialog box.
I've tried to paste a cropped screensot of my dialog box, but the "insert image" button doesn't work intuitively, and I can't figure it out. I "attached" the jpg, but it doesn't show when I "Preview" my response, so maybe it's just not my day . . :(
Please make sure 18.0.193 is installed, then close MC18 and download this file:
http://files.jriver.com/temp/out_main.dll
Overwrite the out_main.dll in this folder:
C:\Program Files\J River\Media Center 18\Plugins
Then run the program and try playback using Direct Sound.
Does that work any better?
Thanks for your help.
-
When i use DSP studio--Output format--Channels--source number channels,every thing working fine with any DTS-CD.But it will show Source:44.1kHz 24bit 1ch and lost center chanel's volume when i use any other up or down mixing option such like Jrss 7.1 or 5.1,Not all of my DTS-CD will broken like this,I can not find any difference between the fine wav file and the bad file.If i played the fine files and no stop to keep going to play the bad file,it will correct the errors of source' info and center chanel mute problem.
I don't know if it's my own problem,sure it is not a big problem,but i want to get some help if anyone can.
Win8 X64,MC 18.0.193,ASIO firewire sound card 8 channels.
-
When i use DSP studio--Output format--Channels--source number channels,every thing working fine with any DTS-CD.But it will show Source:44.1kHz 24bit 1ch and lost center chanel's volume when i use any other up or down mixing option such like Jrss 7.1 or 5.1,Not all of my DTS-CD will broken like this,I can not find any difference between the fine wav file and the bad file.If i played the fine files and no stop to keep going to play the bad file,it will correct the errors of source' info and center chanel mute problem.
I don't know if it's my own problem,sure it is not a big problem,but i want to get some help if anyone can.
Win8 X64,MC 18.0.193,ASIO firewire sound card 8 channels.
You should use DSP Studio > Output Format > Channels to deliver a consistent channel arrangement. Pick whatever matches your actual hardware / connection.
-
Installed .193 and still can't reliably play 192/24 files. Problems occur when switching sampling rates to 192. If a 44.1 file plays and the next file is 192, MC will either hang while the song plays or it won't output sound at all.
-
You should use DSP Studio > Output Format > Channels to deliver a consistent channel arrangement. Pick whatever matches your actual hardware / connection.
Yes,i picked 7.1 chnnels and that maches my 8 channels' sound card.But it will consider with the parts of my DTS CD 5.1 WAV files,The normal files should be (SOURCE:44.1kHz 24bit 6ch and OUTPUT:96kHz 64bit 8ch),the bad files just shown(source:44.1kHz 24bit 1ch and output:96kHz 64bit 8ch,and i found the center channel is mute now).I ALSO FOUND IT WILL BE :(SOURCE:44.1KHZ 24BIT 7CH AND OUTPUT:96KHZ 64BIT 8CH) ON MY ANOTHER HTPC WITH WASAPI 7.1 REALTEK SOUND CARD SETTINGS,THE ''7CH'' DOES NOT MATCH THE 5.1 DTS-CD TOO,I WAS CONFUSED ABOUT THIS.
-
Please make sure 18.0.193 is installed, then close MC18 and download this file:
http://files.jriver.com/temp/out_main.dll
Overwrite the out_main.dll in this folder:
C:\Program Files\J River\Media Center 18\Plugins
Then run the program and try playback using Direct Sound.
Does that work any better?
Thanks for your help.
I got into a situation where my local laptop would not play (DirectSound), but it would serve to any of my other clients. I tried the above out_main.dll on Win7/64 in Program Files(x86) and I have local audio again.
Thanks,
Tim
-
Installed .193 and still can't reliably play 192/24 files. Problems occur when switching sampling rates to 192. If a 44.1 file plays and the next file is 192, MC will either hang while the song plays or it won't output sound at all.
When you post, please include the device you're playing to, the output mode you use, and the connection type.
-
18.0.194=No audio (with DVB-S card playback) and MC freezes/crashes, cannot access any options. Using Directsound with the internal sound device on Win 8 x64... and it seems there's a system mess-up because other applications that output sound also freeze. Please revert/fix this.
-
because other applications that output sound also freeze
MC can't make other programs freeze, so I think this points to some underlying system / driver issue.
-
Blue Light discussion split (http://yabb.jriver.com/interact/index.php?topic=81159.0)
-
Sorry to inform you that updating to .195 did not change any of the problems (mentioned before) I,m having with the ,,new Wasapi.
-
When you post, please include the device you're playing to, the output mode you use, and the connection type.
Sorry, here is the info:
MC 18.0.193 WASAPI
Mac Mini 2012 (Win 7 via Boot Camp) HDMI out >
OPPO BDP-103
I've tried disabling Event Style, exclusive control on/off, and a variety of buffer settings.
-
Upgraded to .194 today. WASAPI is now working fine, no flutter/ticking sounds.
Schiit Bifrost
Event Style Disabled
Bithdepth and Buffering at default values.
-
.195 just be installed
Win8 X64
Focusrite saffire pro 40 firewire soundcard (64sample via medium firewire driver latency)
24bit 7.1chs 96Khz windows settings
New wasapi 25ms working fine (.193 needs 100ms)
Wavpack files info in audio path>changes> ... was right now
Because some of my DTS wav files were shown as 24bit 1ch in DSP studio but 24bit 6ch in audio path info window,Though i hope the new version can fix the "1ch" problem
thanks for all the improvement
-
Matt,
Care to explain how the bit depth setting “Automatic” is supposed to work?
In case of Bluetooth and SPDIF it doesn’t
Bluetooth has to be set to “16 bit integer”
SPDIF to "24 bits integer (in a 32 bit package)"
-
Matt,
Care to explain how the bit depth setting “Automatic” is supposed to work?
If you have to ask, it's not working :P
Could you provide more details about the hardware you are testing (make / model) and also the OS? Also, could you mail a log showing 'Automatic' fail to start playback to logs (at) jriver _dot_ com?
Thanks.
-
Will do.
Thanks
Vincent
PS: downloaded 195 first, Automatic now works with Bluetooth
-
I noticed it's not as loud as it used to be and there's distortion that was never there before. I like to boost @ 33hz with a 12 bandwidth and set the level at 16 and that was fine. Before 193 I wasn't getting any audio and can see the visualizers going, now everything seems fine.
-
I' m experienceing similar problems with WASAPI. I'm using a Bifost DAC. When playing, the DAC relay freaks out, and the sound is massively distorted. WASAPI worked fine on previous version. Direct works fine. I've tried all the various settings mentioned on these threads with no luck, I've also rebuilt the OS from a clean hard drive, and reinstalled JRiver, no luck. Any thoughts on how to get this to work? The DAC works fine with other sources.
-
As a note to my post above, I'm using SPDIF output, with .wav files, ripped from CD, I have not tried my HD files, since the bulk of my music is in the 44.1/16 format. When I first start the application, and a song, the DAC apprears to work, but I get silence, when stopping the song, and restarting is when I get the multiple relay clicks and severe distortion.
And yes, it is a Bifrost, not a Bifost
-
And yes, it is a Bifrost, not a Bifost
That's OK Mr Smeee, in my book you're allowed to do a sneaky "Modify" re-post and not tell anyone.
-
I' m experienceing similar problems with WASAPI. I'm using a Bifost DAC. When playing, the DAC relay freaks out, and the sound is massively distorted. WASAPI worked fine on previous version. Direct works fine. I've tried all the various settings mentioned on these threads with no luck, I've also rebuilt the OS from a clean hard drive, and reinstalled JRiver, no luck. Any thoughts on how to get this to work? The DAC works fine with other sources.
Did you try this? (From above)
To get the old WASAPI (non Event Style), you must check the option called "Disable Event Style". It's in the second section of Audio Settings
-
To get the old WASAPI (non Event Style), you must uncheck the option called "Disable Event Style". It's in the second section of Audio Settings
Confused.
I believe:
check the option called "Disable Event Style" = old WASAPI
uncheck the option called "Disable Event Style" = WASAPI Event Style
hifi_fan
-
darn double negatives! lol
I believe you are correct hifi_fan.
-
I think Jim made a typo. He's entitled to one per year.
-
You're right. Thanks. Corrected above.
-
Just downloaded .195.
With WASAPI, Event Style NOT disabled, 24 bit integer bitdepth, 100ms buffer get clicks and ticks like old fashioned scratched record, using Benchmark DAC2 HGC via USB1.0 with uptodate Windows 8. This uses standard Windows drivers.
Using ASIO and Benchamarks own USB2.0 driver (Thesycus) no issues.
Clicks seem to happen more (mebbe) when I'm using laptop for other things, including typing this and scrolling the MC albums screen.
-
Just downloaded .195.
With WASAPI, Event Style NOT disabled, 24 bit integer bitdepth, 100ms buffer get clicks and ticks like old fashioned scratched record, using Benchmark DAC2 HGC via USB1.0 with uptodate Windows 8. This uses standard Windows drivers.
Using ASIO and Benchamarks own USB2.0 driver (Thesycus) no issues.
Clicks seem to happen more (mebbe) when I'm using laptop for other things, including typing this and scrolling the MC albums screen.
FYI, Benchmark's Driver defaults to a 2048 sample buffer, but 4096 samples is required with the default "safe" streaming mode and high sample rate files. (176/192/DoP) You need to either lower the streaming mode to "relaxed" or increase the buffer size. (I use Extra Safe and 8192)
Never used it in USB1 mode, as ASIO is generally preferred when there is a native driver.
However, one thing I did notice is that if I am outputting 192kHz via ASIO (I upsample all videos to 192kHz to reduce latency) I can still hear system sounds, if the system is also set to 192kHz. I don't think that should be happening? I thought ASIO was supposed to be "exclusive". Can someone (Matt?) comment on that? Is it even a Media Center issue?
-
FYI, Benchmark's Driver defaults to a 2048 sample buffer, but 4096 samples is required with the default "safe" streaming mode and high sample rate files. (176/192/DoP) You need to either lower the streaming mode to "relaxed" or increase the buffer size. (I use Extra Safe and 8192)
Never used it in USB1 mode, as ASIO is generally preferred when there is a native driver.
However, one thing I did notice is that if I am outputting 192kHz via ASIO (I upsample all videos to 192kHz to reduce latency) I can still hear system sounds, if the system is also set to 192kHz. I don't think that should be happening? I thought ASIO was supposed to be "exclusive". Can someone (Matt?) comment on that? Is it even a Media Center issue?
Cheers. As it happens I've bumped the buffer size to 4096 and streaming mode to Extra Safe already.
But my real point of posting was to say that WASAPI and .195 MC gives clicks and scratches for me when used with standard USB1.0 drivers and redbook material. This doesn't concern me greatly as I use ASIO and Benchmarks custom USB2.0 driver, but it might alert JRiver to some remaining issues, which is what the thread title asks folk to do. Surely you would expect WASAPI to work for me if I chose to use it?
-
Cheers. As it happens I've bumped the buffer size to 4096 and streaming mode to Extra Safe already.
If you're using Extra Safe, I think 8192 is required, rather than 4096. (it will complain if you try to play back 176/192/DoP and try changing to 4096)
But my real point of posting was to say that WASAPI and .195 MC gives clicks and scratches for me when used with standard USB1.0 drivers and redbook material. This doesn't concern me greatly as I use ASIO and Benchmarks custom USB2.0 driver, but it might alert JRiver to some remaining issues, which is what the thread title asks folk to do. Surely you would expect WASAPI to work for me if I chose to use it?
Generally ASIO is better than WASAPI on devices that have a native driver, and what you are reporting just seems like the settings need tweaked. I'll look up how to switch back to USB1 mode and report back later tonight.
-
OK, it's way easier to switch between USB1 and USB2 modes by simply holding down the USB button on the remote - and I'm impressed by how seamless it was as far as Media Center and the OS were concerned, on Windows 8. (though I did need to restart MC before I could use ASIO again after switching back to USB2)
When I first got the DAC2, I used the "switch to USB input and hold input up/down on the front of the DAC" method, which took several tries before it worked.
I haven't done extensive testing, but I can confirm what you are hearing. Playing 24/96 music, switching to a 25ms WASAPI buffer seemed to clear things up on my system.
-
Re: my earlier post - my problems with WASAPI 'appear' to be related to using the automatic bit depth with the Bifrost. Setting bitdepth manually to match the .wav seems to work - more testing will be needed by me to confirm fully.
-
But my real point of posting was to say that WASAPI and .195 MC gives clicks and scratches for me when used with standard USB1.0 drivers and redbook material.
I do also have this issue, JRiver 194, Windows 8 (64) native or DAC drivers (Grace Design m903), WASAPI Event Style. For me it's important to use USB 1.0. You can not assume, that everyone uses USB 2.0 ?
-
Please re-read the first post. It can't be the version of USB.
-
Please re-read the first post. It can't be the version of USB.
Yes, exactly speaking: USB Audio Class 1 over USB 1.1 vs USB Audio Class 2 over USB 2.0. I know it.
So: I have issues using USB Audio Class 1 over USB 1.1
-
I do also have this issue, JRiver 194, Windows 8 (64) native or DAC drivers (Grace Design m903), WASAPI Event Style. For me it's important to use USB 1.0. You can not assume, that everyone uses USB 2.0 ?
Try changing the buffer size. Sometimes larger values work best, sometimes smaller values.
With my Benchmark DAC2-HGC, only 25ms seems to work correctly when using USB 1.1.
Sending audio over HDMI via my Nvidia graphics card, it doesn't seem to matter what size the WASAPI buffer size is. (but small buffers may have pops and clicks with high CPU usage)
-
I have JRiver set to auto update and most recent. The sound has definitely changed with the very latest, 180201. I went back two updates to 180194 and the effortless sound quality is there again and no more noise. 180201 has harsh hi frequencies and sounds very digital to me. Something has definitely changed for the worse. I'm a beta tester for PS Audio and several others have remarked on the difference. The earlier version is so much more liquid and powerful.
Steven
-
Try changing the WASAPI settings.
-
Hi,
To what? I tried both Wasapi and kernal streaming. Both sounded equally different and bad in latest version.
Thanks,
Steven
-
I am having trouble viewing Fuji raw RAF image files from my Fuji X10 camera, it seems they are not supported in JRiver V18, last several versions since I bought it. How do I get them working, is there a way to use a different RAW viewing engine (Outside of JRiver I use FastPictureViewer which will display just about every image format known...)? Thanks.
-
I am having trouble viewing Fuji raw RAF image files from my Fuji X10 camera, it seems they are not supported in JRiver V18, last several versions since I bought it. How do I get them working, is there a way to use a different RAW viewing engine (Outside of JRiver I use FastPictureViewer which will display just about every image format known...)? Thanks.
I think we may switch to this for RAW decoding at some point:
http://www.libraw.org/
However, I'm not sure when.
-
EDIT. It is now back to normal. I switched the Ayre to USB 2 and loaded their driver, and it didn't work. I shut down then restarted the PC and then it did all work. phew!!!!
Ayre QB-9 USB DAC, Win 7 64 bit, MC18.0.206, drivers for 192 not loaded.
I was away last week and the PC and indeed whole system was off. I think when I first turned on the PC and ran MC it installed an update, before I played anything. Then when I tried to play (using a dCS Debussy at the time) everything appeared to be working, sound meters bouncing up and down, blue light for direct came on, sample rate indicators changed on DAC according to selected music but no sound. I isolated a problem in the DAC (at least I thought I did), so switched to the Ayre DAC, but still have exactly the same symptoms. Other programs play sound and so will MC if I select Direct Sound, but no sound at all from WASAPI.
What has happened while I was away??!! More importantly, what do I need to do about it? I have tried just about every combination of settings, but they ether make no difference or produce an error message that the format cannot be played.
-
Dear JRiver,
MC doesn't seem to 'release' the exclusive lock on the soundcard when I press pause or stop in WASAPI Exclusive Mode.
Exclusive mode is important for me as I want to have bitperfect streaming for my CD Rips and high res downloads. However for casual listening I also use Spotify installed on the same PC which is a headless PC so has no keyboard/mouse/screen connected to it. I remote control both Spotify (using Remoteless) and JRiver (using JRemote) both installed apps on my iPad.
When JRiver starts after a reboot of the PC I can use the Spotify client but after playing a song in JRiver I have to close/shutdown JRiver first before I can use Spotify.
I'm using the official Spotify client, most recent version and MC 18.0.206. Both are installed on a Windows 8 Pro 64 bit PC.
I've set the pause and stop commands to 'immediately' but this has no effect.
As I am a new user I'm not sure if it's a bug (although I did read on the forum 'stop' should the release the lock) or if I need to make a feature request but I hope you can help me.
Thank you in advance for any response!
Best regards,
Antoine.
-
Exclusive mode means that one program has total control of the interface. That's how it works.
-
Exclusive mode means that one program has total control of the interface. That's how it works.
Thank you JimH for your very quick reply! I fully understand this but when I press 'pause' or 'stop' shouldn't the program release the exclusive lock and try to reacquire it when I press 'play' again? When I start MC it also doesn't immediately acquire the lock. I does so only after I start playing a song.
Best regards,
Antoine.
-
Media Center (or any player) won't take exclusive control over the device unless it's playing audio.
Pausing does not stop playback and release the device - it plays silence.
WASAPI Exclusive not working as you would hope is not a problem exclusive to Media Center. No matter what I have used in exclusive mode, I have always run into a situation where it is necessary to re-open another piece of software (often a web browser playing a video) after stopping exclusive playback somewhere else.
In my experience, WASAPI Event Style is significantly better for this. It is far rarer that I have to re-open other software after WASAPI playback has stopped when using Event Style.
If you stop exclusive playback and the Spotify app is unable to play audio until it is restarted, it's an issue with Spotify.
The other option is, of course, to use a non-exclusive output. This requires you to resample everything to the current mixer settings though. (or switch to DirectSound, which lets the Windows Mixer handle it)
-
Thank you 6233638 for your reply. After reading the Wiki on WASAPI on the JRiver site I now understand that pause indeed plays silence. However MC doesn't release it's exclusive lock on the soundcard when I press stop as well. Other programs like Foobar do. I really have to shut down MC first before I can use Spotify, if I don't Spotify will fail. I am using the WASAPI Event Style setting in 18.0.206 (so haven't disabled that option).
Actually I don't want to use the non-exclusive output as I'd like to play back my music (CD Rips and high res downloads) bitperfect and in it's original bitdepth and sample frequency.
On another forum I wrote about the issue and someone confirmed this behaviour of MC and offered me two possible workarounds (use the livestream/WASAPI loopback option for Spotify or create a dummy playback zone to which I have to switch first so that MC will release the exclusive lock) that I will test later but these are still workarounds that require additional actions. So I would prefer if MC would just release it's exclusive lock on 'stop' like other programs do.
@JRiver, would you care to comment on this one more time and share your views/possible options? If you do thank you in advance! :)
-
Thank you 6233638 for your reply. After reading the Wiki on WASAPI on the JRiver site I now understand that pause indeed plays silence. However MC doesn't release it's exclusive lock on the soundcard when I press stop as well. Other programs like Foobar do. I really have to shut down MC first before I can use Spotify, if I don't Spotify will fail. I am using the WASAPI Event Style setting in 18.0.206 (so haven't disabled that option).
Try disabling Event Style and see if that helps at all.
So I would prefer if MC would just release it's exclusive lock on 'stop' like other programs do.
It should be doing that, but maybe you can create a log and see if that helps. (Help > Logging, and then email the file it creates on your desktop to logs [at] jriver.com)
Windows can get a bit "confused" when dealing with this sort of thing in my experience though. (not a problem exclusive to Media Center)
In my setup, I actually have two sound devices in use - HDMI to my display, and USB to my DAC.
The HDMI output is the Windows default, so that nothing is trying to send audio to my DAC except Media Center.
However to watch a video in my web browser, I have to switch the default device over to the DAC.
Nine times out of ten, it works correctly, the other time I have to quit the browser and re-open it to get sound sent to the DAC.
Loopback isn't an option for video playback because there's too much latency, so sound is very out of sync.
-
I originally posted this issue in the TV tuner section but I think it belongs here.
I am using MC 18 with WASAPI (not-event) and HDMI bit streaming.
The data format is 24-bit in a 32-bit package.
After watching TV programming and listening to music, Amazon streaming fails.
When I load a file from Amazon with Chrome, one of two things happens:
1) Audio is not decoded and the bitstream sends noise through my speakers.
2) Amazon reports a playback error and does not even play the file.
This error occurred with MC 18 loaded and remained even when I shut it down.
However, after playing a TV show with Windows Media Center, everything works fine.
-
A second problem has just occurred on my system with .206.
I have a playlist with several different file formats. Most songs are 24/48 stereo WMA and play just fine. However I also included some 24/48 6 channel FLAC files and those don't play. I see a spinning "star" on the screen and the bit rate of the file (viewed from JRemote) fluctuates between 1700 and 2100. There is audio but it is very garbled. The FLAC files played just fine when I first installed MC a few days ago.
Once this happens I can't even play the same WMA files through WMC or foobar. The sound is garbled just like it was for FLAC files through MC. Unloading MC does not help either. After reloading MC, the FLAC files are still garbled but I can play the WMA files as usual.
I believe my Internet connection is working just fine.
-
I played around with bit streaming options but could not get WASAPI to work. Then I switched to ASIO (using ASIO4ALL) and the 6 channel files played perfectly. I switched backed to WASAPI and now they are playing fine in that mode as well.
-
Since the update WASAPI to start,There is no good used of WASAPI.I did not get anything useful from the Administrator Help.The answer is only a problem on your setup.Now the question:
WASAPI Mode:Right speaker no sound,Pause Noise appears on the right speaker.Replaced direct sound everything is normal.The problem is obviously WASAPI.
Sound Card:VIA VT2021
Drive:1700
System:windows 7 64bit SP1
I have having the exact same problem, except I am using a Bifrost DAC connected by optical cable. Currently running 18.0.209.Any fix?
-
Try the WASAPI settings.
-
Thank you 6233638 for your reply. After reading the Wiki on WASAPI on the JRiver site I now understand that pause indeed plays silence. However MC doesn't release it's exclusive lock on the soundcard when I press stop as well. Other programs like Foobar do. I really have to shut down MC first before I can use Spotify, if I don't Spotify will fail. I am using the WASAPI Event Style setting in 18.0.206 (so haven't disabled that option).
Actually I don't want to use the non-exclusive output as I'd like to play back my music (CD Rips and high res downloads) bitperfect and in it's original bitdepth and sample frequency.
On another forum I wrote about the issue and someone confirmed this behaviour of MC and offered me two possible workarounds (use the livestream/WASAPI loopback option for Spotify or create a dummy playback zone to which I have to switch first so that MC will release the exclusive lock) that I will test later but these are still workarounds that require additional actions. So I would prefer if MC would just release it's exclusive lock on 'stop' like other programs do.
@JRiver, would you care to comment on this one more time and share your views/possible options? If you do thank you in advance! :)
Dear JRiver, would you please comment on my post above? I have already paid $50 for MC and received a license valid for both MC 18 and 19. Will 19 exhibit this same behaviour?
-
Using stop should release the sound card. But WASAPI exclusive is meant to be exclusive. You can set it to be non-exclusive if that's what you want.
-
Thank you Jim, it doesn't release the soundcard when pressing 'stop' so I guess this is a bug. Could this be "fixed" after maybe you guys first confirm this behaviour in combination with Spotify? I want to keep using exclusive mode (bit perfect playback). With Foobar it does work but I like MC more.
-
please help!
just installed mc18 on a 19 license. windows 7. anyways, everything was fine with mc17, but now mc18 won't play anything! the only mode that works is direct, when before i was WASAPI event style
i've tried everything i read in this thread, but nothing is helping. the files are "playing" but i can't hear anything!
EDIT: if i uncheck "exclusive access" then it plays over my hi-fi (optical) and my DAC (usb). i want exclusive access, but at least WASAPI is working...i can live with this for now but i really appreciate any thoughts on this
-
Have you tried disabling Event Style for WASAPI?
-
yup, tried everything. the ONLY way WASAPI will play anything is with exclusive access disabled. otherwise no sound, no matter whether i use my onboard or my DAC
-
yup, tried everything. the ONLY way WASAPI will play anything is with exclusive access disabled. otherwise no sound, no matter whether i use my onboard or my DAC
Hmm, I'm not sure what it could be then if you have tried all the WASAPI output options. (e.g. setting it to output 16-bit only)
You were definitely using WASAPI Exclusive in MC17, and exclusive access is enabled in the Windows control panel for that device?
What output format is Windows set to? I seem to recall that some hardware requires you to set it to the maximum supported output for this to work correctly.
-
Hmm, I'm not sure what it could be then if you have tried all the WASAPI output options. (e.g. setting it to output 16-bit only)
You were definitely using WASAPI Exclusive in MC17, and exclusive access is enabled in the Windows control panel for that device?
What output format is Windows set to? I seem to recall that some hardware requires you to set it to the maximum supported output for this to work correctly.
yup, exclusive before.
hardware settings are exactly what they were with mc17 (my card and DAC support 24/96 so everything is set here, worked fine with 17). i have played around with all the settings both hardware and MC18 and the only way i can get sound through WASAPI is by not allowing exclusive access.
-
Event style is now the default. Please confirm that you tried disabling Event Style.
-
Event style is now the default. Please confirm that you tried disabling Event Style.
First thing I tried was disabling event style, no dice
I've now spent several hours going through settings and I believe I've hit almost every permutation of hardware / software options possible
If I turn off exclusive access, the sound will play at a very wide range of other options (output formats etc) but with it enabled it will never play regardless of other settings. Seems odd I know...
-
Maybe another program also has exclusive access. That won't work.
-
I have tried all the option in WASAPI setting, disable event style, changing bitdepth, buffering, even reinstalling . The problem remain the same, whenever i pause or skip tracks, i can only hear white noise from the right speaker. This didnt happen to me when i was using the MC18 trial few months ago. And i just purchased the license for MC19..
-
ok so i found Mr Smeee's solution works as I also have a non-usb Bifrost. Most of my source are flac ripped from CD, however I tried playing some 24 96 WAV using 16 bit integer and it plays effortlessly, strange.
-
Feedback
-
With JRiver 18.0.212 on Windows Server 2012 WASAPI is not working.
The song start playing but I can't get any sound.
Already tried to uncheck "Disable event style..."
-
Does any sound work? DirectSound?
Try Control Panel/Sounds and see if you can learn anything.
-
Does any sound work? DirectSound?
Try Control Panel/Sounds and see if you can learn anything.
DirectSound and KS worked fine...
I tried with foobar2000 and also worked...
-
Hi
I'm having a problem with 5.1 audio and movies. back channels (L and R) are muted when WASAPI is used.
I've tried changing event style and bitdepth and always get the same result (some bitdepths doesn't work at all but that's normal).
Audio path shows:
Input: 96KHz 24 bit 6ch from source format FLAC
Changes: No changes are being made
Output: 96KHz 24 bit (padded) 6ch using WASAPI (direct connection)
I'm using MC 18.0.212
Sound Card: IDT 92HD73C1
Receiver Denon AVR-789
Same 5.1 audio file with Foobar + Wasapi works fine
Same 5.1 audio file with MC + Direct Sound works fine
-
With JRiver 18.0.212 on Windows Server 2012 WASAPI is not working.
The song start playing but I can't get any sound.
Already tried to uncheck "Disable event style..."
Does any sound work? DirectSound?
Try Control Panel/Sounds and see if you can learn anything.
DirectSound and KS worked fine...
I tried with foobar2000 and also worked...
Any help?
-
If WASAPI is set to exclusive in another program, it won't work for a second program.
-
If WASAPI is set to exclusive in another program, it won't work for a second program.
I only tried foobar2000 after... ;)
This is an issue with JRiver...
-
I know of no current MC problems with WASAPI. Maybe foobar is set to use exclusive.
-
I know of no current MC problems with WASAPI. Maybe foobar is set to use exclusive.
As I said, I tried KS, DS and WASAPI before tried with foobar2000 portable, and only WASAPI didn't work...
I also removed foobar2000 and the issue continues...
-
Hi guys
Any idea what causes this problem?
I'd really like to get wasapi working :)
Thanks
Hi
I'm having a problem with 5.1 audio and movies. back channels (L and R) are muted when WASAPI is used.
I've tried changing event style and bitdepth and always get the same result (some bitdepths doesn't work at all but that's normal).
Audio path shows:
Input: 96KHz 24 bit 6ch from source format FLAC
Changes: No changes are being made
Output: 96KHz 24 bit (padded) 6ch using WASAPI (direct connection)
I'm using MC 18.0.212
Sound Card: IDT 92HD73C1
Receiver Denon AVR-789
Same 5.1 audio file with Foobar + Wasapi works fine
Same 5.1 audio file with MC + Direct Sound works fine
-
As I said, I tried KS, DS and WASAPI before tried with foobar2000 portable, and only WASAPI didn't work...
I also removed foobar2000 and the issue continues...
The problem program could be MC18 or any other software that accesses the sound card.
-
Given there doesn't seem to be a solution to my problem I'd like to install a version that doesn't have the new wasapi implementation.
Could somebody post the link to the last version before 18.0.193.
Thanks
-
There was no change to WASAPI that could cause this in the latest build.
The terminology did change, so that what was "WASAPI Event Style" is now just WASAPI. If you used the old "WASAPI", you might need to set the option to "Disable Event Style".
-
I still can't use WASAPI....