INTERACT FORUM

More => Old Versions => JRiver Media Center 18 for Windows => Topic started by: JimH on May 26, 2013, 05:51:31 pm

Title: We owe you a humble apology
Post by: JimH on May 26, 2013, 05:51:31 pm
We made a mistake that has caused a fair bit of trouble the last couple of days, and I want to apologize.

We pushed build 189 to stable before we had received enough feedback to find a serious problem.  

I believe it only affects people who have DAC's that need input at 24 bits.  Though this is probably a small minority by percentage, it's still a large number of people.

To compound this mistake, we did it just before a long weekend, so we will be a day slower in correcting it.

I'm very sorry.

If you have had the problem, you can try setting the bitdepth manually.  It's in Audio options in the second section, called "Output Mode Settings".

If that doesn't work, download and install this build:

http://files.jriver.com/mediacenter/channels/v18/stable/MediaCenter180175.exe

You can turn off the auto update option in the Help menu under Update Channels.

We should have a fix for this by mid week.
Title: Re: We owe you a humble apology
Post by: F1 fan on May 26, 2013, 06:43:10 pm
No worries Jim.As in the past I had full confidence you would be working to correct the issue.
Title: Re: We owe you a humble apology
Post by: hulkss on May 26, 2013, 07:28:07 pm
No problem here with Lynx Aurora, ASIO, USB connected.

I have checked "device uses only most significant 24-bits"
Title: Xlint Customer service
Post by: down4jazz on May 26, 2013, 08:34:14 pm
this is why I am confident in not only using JRiver MC, but also in recommending it to virtually everybody that wants a solid music player/manager. Thanks!
Title: Re: We owe you a humble apology
Post by: J-a-k-e on May 26, 2013, 08:55:35 pm
Hi Jim, while I'm not one of those personally affected; you guys have always made it clear that the latest version of media center available is also the version currently being worked on. So I feel most users here understand and accept that this process of adding, changing or fixing a feature doesn't always work out exactly as planned the first time around.
Title: Re: We owe you a humble apology
Post by: Peter_RN on May 27, 2013, 04:00:48 am
+1 to all the above sentiments.

You chaps are quick to help even when a reported problem is clearly not a MC issue.

Thanks to you all.

Peter
Title: Re: We owe you a humble apology
Post by: JJJ on May 27, 2013, 07:55:16 am
EDIT - will open separate thread
Title: Re: We owe you a humble apology
Post by: JazzDoc on May 29, 2013, 06:07:42 am
How does the problem manifest?
Title: Re: We owe you a humble apology
Post by: JimH on May 29, 2013, 07:34:13 am
If you don't see it, you don't have it.
Title: Re: We owe you a humble apology
Post by: syn-ack on May 29, 2013, 07:43:04 am
You can turn off the auto update option in the Help menu under Update Channels.

My suggestion, is to treat software updates the way BIOS updates were/are treated.

You read the release notes for specific update details. If there is an update that fixes a specific issue you have, then you apply the update. Otherwise, you stay at your current/stable/working version.

However, I depart from this strategy at times when it comes to security updates, in which case, most of the time, they should be applied immediately.
Title: Re: We owe you a humble apology
Post by: cleeds on May 29, 2013, 08:32:51 am
I had a few problems related to the latest build, especially when using it with a 160 GB iPod Classic, which worked fine with MC previously. So, thanks for providing a link to the previous build. Very helpful!
Title: Re: We owe you a humble apology
Post by: JimH on May 29, 2013, 09:13:01 am
Please try 18.0.191:
http://yabb.jriver.com/interact/index.php?topic=80999.0

Please report what you find here:
http://yabb.jriver.com/interact/index.php?topic=81000.msg551301#msg551301
Title: Re: We owe you a humble apology
Post by: JimH on May 31, 2013, 05:07:14 pm
Please download 18.0.193 and use this thread for any problems.
http://yabb.jriver.com/interact/index.php?topic=81052.0