Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Djeayzonne]

There was a message that there was an update available in the corner, so I clicked on that to update.
Everything was working fine until that moment, now playback will not start for any type of file of format output settings.
DAC is Renaissance Labs Herus, so I normally do PCM to DSD real-time conversion, but turning this off, and turning off the output settings in studio completely does not fix the problem.

Error message is something went wrong with playback
could not be started on output WASAPI using format 44.1 2ch
etc.

Again, was working fine until the second I clicked to update.

[glynor]

It is possible that something is broken in the current build, but let's verify a few things first...

Can you:

1. Confirm what version you have installed now?  If it is the latest, it should be 19.0.128.
2. If you aren't running 19.0.128, then please download it and install it and try again.
3. If you are running 19.0.128, then please try rolling back to a previous version or three and see if the problem goes away.  Here are the threads for the last few versions:

19.0.127: http://yabb.jriver.com/interact/index.php?topic=88624.0
19.0.125: http://yabb.jriver.com/interact/index.php?topic=88507.0
19.0.121: http://yabb.jriver.com/interact/index.php?topic=88012.0

You can just install the older builds "on top of" the one you have.

And, lastly, you may want to make sure your settings didn't get messed up again.  Check through this:
http://wiki.jriver.com/index.php/Audio_Setup

And make sure everything looks as it should.

Thanks.

[Djeayzonne]

Going back to .125 restored playback with Output Format turned off.
Then tried reinstalling .128, playback still works with Output Format turned off, but still unable to do PCM to DSD conversion, which is how I normally listen.
Please help me fix this.

[glynor]

Going back to .125 restored playback with Output Format turned off.
Then tried reinstalling .128, playback still works with Output Format turned off, but still unable to do PCM to DSD conversion, which is how I normally listen.
Please help me fix this.

You didn't explain enough.

What you said is this:

* I went back to 125 and it worked with the Output Format DSP turned off.
* I then reinstalled 128 and it still worked with the Output Format DSP turned off.
* When I turn on some option (that might be completely misconfigured) in 128, then it doesn't work.

So.... It works, but then you changed stuff and it doesn't?  That wasn't a valid test.

What we need to see, to determine if there was a regression in the new build is: Do the EXACT same settings that worked on build 125 suddenly not work on build 128? Any other test is invalid and useless.

PS. I should add, it is possible you did test it properly, and just explained poorly.  That's fine, but explain.  We don't want to chase a rabbit down an irrelevant hole.

[Djeayzonne]

I believe this will be the third time, but I normally (i.e. always) listen to my library using the real-time PCM to DSD option.
I bought this software specifically for this reason, along with the EQ flexibility of the DSP studio.

I was listening in this mode this morning when I noticed a message saying there was an update available. I clicked to update while content was playing in my default mode.

This software updated.

After the software relaunched, and I clicked play (NO SETTINGS CHANGES), I started receiving the error.
I turned off the Output Format option in DSP studio, and turned off DSD bitstreaming for the device.
No change.

I tried reconnecting the USB cable to the DAC, no change.
I tried rebooting the PC, no change.

I then created this thread.

I then did as you suggested, PCM playback with no Output Format options enabled restored, THOUGH THIS IS NOT MY DEFAULT

I then tried my default, which did not work.

Since some kind of playback was restored, I switched back to .128, no change - meaning my DEFAULT PLAYBACK SETTINGS NO LONGER WORK

Does that provide the info you were needing?

[Djeayzonne]

PS. I do not know what the exact version was prior to this morning's update.

[glynor]

I then tried my default, which did not work.

You did not say this in your earlier post, and it was the single most important detail of the whole thing.  In fact, the other stuff is all noise.  I don't care about what modifications you made to the DSP, right now.  The initial point is to figure out if there is a difference in versions of MC, or if something else happened (upon which we can investigate the other tack).  So, the rest hurts, doesn't help, because it introduces variables.

Not trying to be a pain, that's just the way it is if you want to solve problems.

So...

Then, to be clear...

1. When you made the initial post, you were running 19.0.128.  (I verify this because it is possible that the updater could have downloaded an older build, and then installed that, even though 128 was released.  This happens.)

2. Prior to the update, you had settings in the DSP and they worked.  Post-update, they didn't work.

3. Normal stuff like rebooting and whatnot didn't solve it.

4. You rolled back to 125, and that didn't fix the issue.

Are all of those things true?

Then, either:

1. The timing of the upgrade and the failure to play back were either coincidental, or it somehow triggered a condition external to MC.

2. The change in behavior of MC is older than build 125 (which is a fairly recent version, and you might not have had it yet).

3. You aren't accurately replicating your settings, or some setting changed and you didn't realize it is the cause.

#3 is easy to address.  MC makes automatic Library Backups.  Restoring one of these backups, including settings, will put the DSP back exactly as it was.  So, make a new Library backup (to save where you are now).  Then, look in your Library Backup directory (which is in My Documents\J River by default) and find a backup from when you know it worked, and restore the Settings (you don't have to restore the Library which isn't related here).

#2 might entail going back further.

#1 let's not worry about until we eliminate #2-3 as potential causes.

[Djeayzonne]

OK, will try that and update later.

[Djeayzonne]

Restoring just the library settings fixed the issue.
I took a quick look at the settings (I actually have most everything default actually), and the only thing I noticed that was changed was the option Open device for exclusive access.
I turned this off two days ago so I could listen to JRiver and play a game at the same time.

This (PCM to DSD output from JRiver while playing Diablo 3, specifically) did work though for the two days until I updated. But, the update itself is obviously not the problem, so do you have any idea about this?
I would prefer not to have this option checked if possible, but I value the DSD conversion more if I have to make a choice.

[glynor]

This (PCM to DSD output from JRiver while playing Diablo 3, specifically) did work though for the two days until I updated. But, the update itself is obviously not the problem, so do you have any idea about this?
I would prefer not to have this option checked if possible, but I value the DSD conversion more if I have to make a choice.

That basically explains everything.

Whether it would work or not with Exclusive Mode disabled depends on the particular settings you have enabled in Windows, and the particular files you were trying to play at any given time.

Read:
http://wiki.jriver.com/index.php/Exclusive_access

[Djeayzonne]

Thanks for that link.
Hmm... after reading that, I think I will just leave this enabled. Not doing so kind of defeats the purpose.

I still wonder why it worked for the first few days before updating just out of curiosity, but I guess it doesn't really matter.

Thanks for your help mate.

[glynor]

Here's how you solve the problem:

1. Make a second Zone (just make a duplicate of the one you have) and name it something like "Non-Exclusive" (or whatever you'll remember easily).
2. Switch to that zone, and then open Tools > Options > Audio
3. Change your audio device to More > [Direct Sound version of your Device].

Then, you can use that zone, through the Windows mixer with all the regular automatic resampling that Windows does, and it'll work non-exclusively.  Alternately, you could still use WASAPI, but disable Exclusive, and then set the Output Format DSP to resample all audio to match the Windows Default format (that just takes a little more elbow grease, but it will use MC's better-quality resampler).

In any case, then you can easily switch to this "alternate zone" when you want to do something like play a game with some music on in the background, or whatever.  One would assume that, during these activities, you'll probably not be too concerned with sound quality.  But, then your "standard mode" can still be the "nice way".

[Djeayzonne]

Sorry for getting back late on this, just wanted to say thanks for that extra help.
Man this software is sweet. Definitely worth every penny.