This morning, waking the PC via JRemote, and picking a whole album for the ODroid/Kodi to play, playback stopped after the 5m52s first track.
So, I was able to repeat the experiment this morning with a bit more patience. Don't know if the symptoms below help point to anything or not, but I'll describe them nevertheless...
After waking the PC with JRemote, I kept hitting refresh on the device list, waiting for the (just turned-on) AVR to appear. For one of these refreshes, the ODroid/Kodi box
did drop out (leaving just "This Device" and "Player" in JRemote's list).
When this happened, ODroid was still the selected device within JRemote. It had previously been showing (down in the lower corner) the Mozart album that was indeed the last item played on that renderer. When the ODroid/Kodi dropped out of JRemote's shown device list, that album cover disappeared, to be replaced with the typical "blank, no cover" display.
Shortly after that, the ODroid and the AVR both appeared in the device list. So, I thought I would start playing (back to the Bach album of piano inventions that has that 1 minute+ first track).
Playback started. The first track finished and the second track started playing. Looking at JRemote, though, the playback status during this second track was quite odd! It showed playing "0 of 1", with an accurate time for that second track, but all of the remaining info still reflecting the
first track.
Going over to JRiver on the PC, it's overview of the ODroid/Kodi renderer was pretty similar -- playing 0 of 1. The playlist for that renderer was somewhat "broken" in the GUI as well, with the name of the first track appearing at the bottom of a short list of repeated text.
Following the conclusion of that second track, playback then went back to the
first track. Now, both JRemote and the JRiver GUI showed playing "1 of 1". Playback stopped after this repeat of the album's first track.
Hopefully, the above might give some clue what's going on regarding both JRiver & JRemote's joint state regarding that renderer.
There's definitely something to be said for waiting for "network stability" after waking the PC. I thought I did that this morning, though, and ended up with even weirder results than before!