jRiver 19.0.17 is available for down load now


#1

Yes I’m running jriver version 19 and sounding good


#2

@johno@datacom.co.nz Did you have reset the optimizing options? Are your updates configured “Latest (may be less stable)” or “Stable (recommended)”? The 19 update does not show on my JRMC set on Stable. Christopher



#3

Guys…



When upgrading to version 19, did all of your files transfer properly? Also, are there as many optimizing adjustments that need to be performed as there are/were with version 18? Can someone please list what the recommended “new” optimizing options are…?



Is this a noticeable upgrade from version 18 (platform, operations, features…); and is there any improvement in the sound quality?



Thank you.



_Ben


#4

I upgraded to 19.0.27. All is good except replay gain tags are not there even though Volume Leveling is checked in Media Network (audio>advanced). ???


#5

birddogthecat, this is a beta version. Looks like they have not yet released a stable 19 version yet. I have not tried it. I’m not sure that it would show up in 18 as an upgrade even if your settings were not set on Stable as it is a full version upgrade (for which they make you pay again).


#6
birddogthecat, this is a beta version. Looks like they have not yet released a stable 19 version yet. I have not tried it. I'm not sure that it would show up in 18 as an upgrade even if your settings were not set on Stable as it is a full version upgrade (for which they make you pay again).


.27 is a stable version. Its all good IMO. My previous comment about not having RG tags was wrong. It turns out to have been changed to Volume Level (replay gain).

#7

@birddogthecat



No it does not show up you have to go to the forum site and down load it, yes it is stated to be possible less stable than the seasoned build of 18.



http://files.jriver.com/mediacenter/channels/v19/latest/MediaCenter190027.exe



I just backed up the library the ran the executable, it showed 30 days trial until I applied my $16.00 key code



I have not experienced any issues and WaveStream displays as pictured



Cheers

John

<fieldset class="gc-fieldset">
							<legend> Attached files </legend> <a href="/wp-content/uploads/attachments/58059=2019-1d86a2c9bb06a81ef2f7f3b30b41d7.jpg"><img src="/wp-content/uploads/attachments/58059=2019-1d86a2c9bb06a81ef2f7f3b30b41d7.jpg" class="gc-images" title="/FileUpload/c8/1d86a2c9bb06a81ef2f7f3b30b41d7.jpg" style="max-width:300px" /></a> </fieldset>

#8

Hi Ben



When going to v19 everything went fine no trouble on win8 nothing really new to report yet on optimising apart from some enhancements made in play direct from memory



I don’t detect any sound difference from 18 to 19



Cheers

John



--------------------------------------------------------------------------------

NEW: Improved memory playback

Overview from jriver forum

Memory playback now holds decoded data in memory instead of encoded data.



This means playing any form of lossless (WAV, FLAC, APE, ALAC, etc.) will have identical data in memory and identical resource usage.



Benefits

The theoretical benefits of memory playback are that no disk or network I/O occurs while playing and that CPU load during playback could be reduced.



Technical Considerations

With a modern computer, playback of a standard CD-quality file will have the fully decoded file in memory in around one second.



Memory playback will use up to 1GB of memory for cache (capped at 80% of available system memory to avoid swap usage).



In some cases, the work of decoding and caching a file quickly as a track starts could lead to other problems. For example, when playing over Wi-Fi some machines exhibit high resource usage when reading a file quickly. This resource usage as a track starts could lead to audio playback glitches.



Some files like DSD played as PCM have very large decoded data so that they might require more memory to cache than (most) any system has. In these cases, the program will cache 1GB, play it mostly out, then cache another 1GB, etc.



With memory playback enabled, the player will no longer report a real-time bitrate (ie. 872 kbps) during playback. This is because asking the decoder its current bitrate is not possible when the decoder has finished with the current track completely in the first couple seconds of playback.



Sound Quality

JRiver is unaware of any test that shows a sound quality advantage to memory playback.



The option was added due to popular demand.



How to Use

You enable or disable memory playback in Options > Audio > Play files from memory instead of disk.



It is off by default.


#9

A Cautionary Tale:



Re: JRMC 19.0.27



"CAUTION – This is an early build of MC19. Please read what others say before downloading. It may be less stable than MC18 for some time to come. Back up your current MC library before installing. Please use the Problems and Questions thread if you need help."



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



I will wait until it is out of Beta.



Christopher


#10
A Cautionary Tale:

Re: JRMC 19.0.27

"CAUTION -- This is an early build of MC19. Please read what others say before downloading. It may be less stable than MC18 for some time to come. Back up your current MC library before installing. Please use the Problems and Questions thread if you need help."

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


I will wait until it is out of Beta.

Christopher


Its fine in my system.

#11

Yes it is pre beta



Been playing for may hours switched between WASAPI and Kernal Steaming.



Even had a power cut in the house everything restarted and resumed play



got to say I’m impressed for a pre beta for simple audio usage not one issue encountered



Cheers

John


#12

Has anyone who had SQ issues after 18.194 confirmed that the SQ degrade has been fixed in version 19.027?


#13

@birddogthecat

Downloaded it today. Sounds great. I suspect the change to the way the RAM holds decoded data instead of encoded data sounds better. My Flac files sound like they caught the WAV!

Very good sounding and stable for a beta version. Too bad Paul couldn’t persuade the jRiver guys to write the WaveStream programs and eLyric. You know they’d be right and quickly done. I’ve heard tales of custom work done by the jRiver guys in less than 24 hours. Yikes!

Try it you’ll like it says Stevie!

B-)


#14

@magicknow



I cant be certain what caused the issue from version following 194 yes they were dead sounding in comparison. however some weeks later in versions after 194 the problem was resolved after using the recommended audio output setting. Then I could not replicate the issue either, I put it down to something going wrong in setting audio output.



the change to version 19 has been good no issues detected and the SQ I cant say its better or worse than 18 was in my system.


#15

@sgrowan We tried. They declined and said it was not what they do - but were very interested in seeing what we came up with.


#16

Paul,

Too bad for them. They sure could have gotten a new revenue stream. They should think about a new department. They do seem a bit touchy though for example the jRiver 18 versions that sounded flat to many of us, yet jRiver denied it and their continued dissing of jPlay.

Steven


#17

@sgrowan OK Steven - You are the one that always advises caution over latest update. But, since you downloaded so did I.



Download went smoothly and JRMC 19 “took” the registration key automatically. I am fairly sure most options remained set as they were from 18 under the PS Audio setting.



Another rainy day here at the beaches of North Carolina (a week now) so I will have time to play and listen.



Christopher







#18

Birddogthecat,

I figured I had nothing to lose since version 18 was not being over written.

I believe it preserved all of your settings. Mine did.

Steven


#19

@sgrowan I did the same. I kept 18 as my back up. SQ update: 19 does sound better than 18. I am looking out my window at the Atlantic Ocean and all I see is endless rain. Christopher


#20

problem solved. can’t delete post.