Print

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

[boot77]

After running jriver problem free for several years I ran into a problem I can't figure out what causes it.

After playing several songs from a playlist the audio stops, jriver tries to play the next tack, which in most cases in unsuccesfull and then skipping a few more songs and picks up 5-8 songs futher down the playlist. jriver also might freeze.

I have upgrade the client and server to the latest version (20.0.80). Rebooted the server and client, but no luck. I don't now it is the client or the server.

I hope you can help me out or advise.

[coolfriend693]

Reinstall the program

[boot77]

I uninstalled JRiver on the server side, I left the reg keys and settings in place. Reinstalled the latest version from the form. Imported the library backup same result. I can now repeat the problem on more than one client.
I created a new library and imported only the audio files. All files needed files where imported correctly. I tested the same album and the problem still exists.

Repeatable example

600MB wav file with cue file. JRiver uses the cue file for the song index.
If I play track 3 it stops at 1:28 but the song is 1:36 sec long.
All next tracks are skipped after JRiver tried to play them, only the last track starts to play.

The wav file it self plays without a problem, so it's not corrupt or unplayable.

If I try to interact with JRiver during the hang-up, JRiver freezes and the program needs to be killed.

I added a log file. Please advice.
This log file is from a client running on my laptop with wifi. The log file above are from my htpc wired. I can repeate the problem on both clients.

[Hendrik]

There was an issue with CUE files in recent builds, which was fixed in 20.0.82. Can you confirm that you run a build newer than that?
You can find the latest on the top of the forums: http://yabb.jriver.com/interact/index.php?topic=96480.0

[boot77]

okay, after installing 20.0.80 and having the problem I switched to stable updates so did not upgrade to 20.0.82 on the client side, only the server recently hoping to solve the problem. But will upgrade the clients to see if it fixes the problem.

[boot77]

Jep the new version solved the problem, thanks