JRiver Media Center

[balala]

Balala is running version 25 on his system, and it is still working fine for him.

Right:

JRiver.png

JRiver2.png

And the skin created based on the previously posted code:

JRiver3.png

[eclectic-tech]

"Ditto!"

I installed J.River Media Center 25 (x86) and used Soita skin also. I had no problem having the skin show info and control J. River functions.

jriver25.png

So there is something on your end.

What skin(s) are you trying that you say "Don't work"?

I do not find anything wrong with Rainmeter or NowPlaying..
Specs:
Rainmeter 4.3.0.3298 (64-bit)
Language: English (1033)
Build time: 2019-03-18 11:00:34
Commit Hash: 3593c281
Windows 10 Pro 1903 64-bit (build 18356) - English (1033)
Path: C:\Program Files\Rainmeter\
SkinPath: C:\Users\John\Rainmeter\Skins\
SettingsPath: C:\Users\John\AppData\Roaming\Rainmeter\
IniFile: C:\Users\John\AppData\Roaming\Rainmeter\Rainmeter.ini

[jsmorley]

See my last post on the previous page. Can you guys confirm that behavior?

[eclectic-tech]

See my last post on the previous page. Can you guys confirm that behavior?

I could not duplicate that issue on my system... the skin responded immediately whether a song was playing or not.
I tried it with skin loaded first, no player... okay
Media player playing, then load skin... okay.

It simply worked every time.

[balala]

Ah, I see an issue. If you have a song playing in JRiver and then load the Soita skin, it doesn't work until you change songs in JRiver. It's not enough to refresh the skin, you have to cause JRiver to send out some kind of "I've changed" signal. Once it is working then it works fine, you can refresh the skin, unload and load the skin, change songs in the player, exit and restart JRiver, all works fine. You just can't seem to start JRiver and start playing a song before loading the skin, or it will not be properly seen until you "poke" JRiver in some way.

You can start JRiver before the skin, that's fine, when you load the skin and THEN start playing a song in JRiver, it's ok with that. It only seems to hate it if you start JRiver, start playing a song, then load the skin. It will ever see "that song".

Yep, that's right. That's exactly what's going on here.
So, probably you found the issue Gregory2001 is having.
So, solved, I think...

[jsmorley]

I could not duplicate that issue on my system... the skin responded immediately whether a song was playing or not.
I tried it with skin loaded first, no player... okay
Media player playing, then load skin... okay.

It simply worked every time.

Hm... I definitely get that behavior. With Soita, or with the example code from the NowPlaying documentation. Let's see what balala gets, assuming he is running the 64bit version. I'd like be sure it's apples and apples.

Edit. Sorry balala. Missed your post. Ok, so that feels like the issue.

[balala]

Media player playing, then load skin... okay.

Are you sure? Because it doesn't for me. If the media player is playing and load the skin after this, doesn't work. When I change the song, it starts working.
Same working if the skin is loaded before the player starts playing.

assuming he is running the 64bit version.

No, I'm running a 32-bit version on an older computer.

[jsmorley]

Are you sure? Because it doesn't for me. If the media player is playing and load the skin after this, doesn't work. When I change the song, it starts working.
Same working if the skin is loaded before the player starts playing.

No, I'm running a 32-bit version on an older computer.

Hm... So I'm at a bit of a loss why it works differently for ecectic-tech. By "older computer", you don't mean a 32bit computer running 32bit Windows and 32bit Rainmeter do you?

[balala]

Hm... So I'm at a bit of a loss why it works differently for ecectic-tech.

Me too. But here what you've described applies perfectly.

[jsmorley]

Me too. But here what you've described applies perfectly.

Yeah, the way I would describe the behavior is that NowPlaying needs to get some kind of "I've started playing a song" signal from JRiver. All the cases I described where it "works", that is the case. NowPlaying is running when a song is "started". In the one instance where I find it "doesn't work", that signal is never received by NowPlaying. It's not "I'm playing a song", but "I've started playing a song".