Sorry for the delay. I’ve conducted a series of tests and I think I’ve solved the problem. The problem comes from the “link” function. I’m listening — not exclusively but mainly — to classical music. In classical music, we don’t generally listen “track by track” but “work by work” and a work is generally comprised of a series of movements (i.e. tracks). Hence the use of the “Link start” function that allows one to choose works randomly, without disrupting the succession of the movements.
Now, when you’re about to rip a CD, you can edit all the metadata — which is absolutely necessary in classical music, because all the online data is pure
rubbish —
before starting the actual rip and that’s what I generally do. But
don’t — absolutely
don’t — use the “link start” function at this point. Otherwise happens what happened to me : when you’ll want to play your ripped tracks,
JRiver will have kept the link pointing to the CD and, as it won’t find the CD, it will tell you it can’t find the track to be played ! So unless this behaviour is corrected in a future version, proceed like this for ripping your CDs :
- insert the CD
- edit the metadata at will, but don’t use the link start function
- rip the CD
- eject the CD
- now you can group tracks (movements) in works with the link start function.
Have a nice day !
PS : maybe this could be considered as a bug and corrected in a future update ?