INTERACT FORUM
Networks and Remotes => Remotes => Topic started by: bob on August 15, 2023, 08:27:04 pm
-
Changes in this build (436):
1) Work around for WakeOnLan not working by using the local network broadcast address when multicast broadcast fails.
Report results please.
-
Build 437 contains a new iPad feature that will update the cover art in the full screen cover art view on track change.
-
On both JRemote 3.41 and 3.40, if browsing a set of albums in cover art view, long-pressing an album to start playback then results in the album cover remaining at a reduced size (compared to the neighboring albums) when the cover rotates back to its neutral position. The change in cover art size goes away with a refresh of the view, but one can get multiple albums into that state.
[Edit: wording]
-
Changes for build 438:
Added Opus playback support for the device zone.
Fix for long-pressing an album to start playback resulting in the album cover remaining at a reduced size.
-
Sorry if this is not the right place for my issue/inquiry but here it is.
I have several iOS devices running JRemote 3.40. On devices with iOS version 16.7 or above, JRemote won't wake up the computer running JRiver anymore, but if I manually turn on the computer, JRemote will connect though.
There are no issues waking up the computer with JRemote iOS 12.x.x and 15.x.x devices.
I checked the firewall/router and do not see anything abnormal.
Is this an actual issue with 3.40?
Thanks in advance.
-
Sorry if this is not the right place for my issue/inquiry but here it is.
I have several iOS devices running JRemote 3.40. On devices with iOS version 16.7 or above, JRemote won't wake up the computer running JRiver anymore, but if I manually turn on the computer, JRemote will connect though.
There are no issues waking up the computer with JRemote iOS 12.x.x and 15.x.x devices.
I checked the firewall/router and do not see anything abnormal.
Is this an actual issue with 3.40?
Thanks in advance.
Yes, see the top post in this thread. The fix is in the current beta.
-
Thank you. Looking forward for the fix.
-
New in build 438:
Volume buttons control remote zone volume if selected.
-
How can I deactivate this? I have constant volume changes since then and it’s a bit annoying, thanks!
-
If I may ask, how can I try test this beta version? Thanks
-
How can I deactivate this? I have constant volume changes since then and it’s a bit annoying, thanks!
Re-install beta build 438 from testflight
-
If I may ask, how can I try test this beta version? Thanks
You have mail.
-
I can confirm that WOL (w/ JRemote V3.41) is working on a device running iOS 16.7. Good work. Thanks
-
Re-install beta build 438 from testflight
Thanks, that works.
So if you keep this feature I would always have to use an old built? Or do you plan a toggle?
-
I usually keep the volume level of the DLNA renderer through which I play at 100% (adjusting it instead at the pre-amplifier).
With the latest JRemote beta, I notice the initial volume setting changing from run to run. It's never as low as the iPad's volume (which I generally keep quite low), but it certainly is varying from 100%.
Is JRemote trying to "transfer" the iPad's volume level to the DLNA renderer, even though no button presses have occurred?
-
Changes in this build (436):
1) Work around for WakeOnLan not working by using the local network broadcast address when multicast broadcast fails.
Report results please.
Are there openings for beta testers?
-
Changes in build 442:
Volume buttons when changing a remote zone volume no longer affect system volume.
-
I usually keep the volume level of the DLNA renderer through which I play at 100% (adjusting it instead at the pre-amplifier).
With the latest JRemote beta, I notice the initial volume setting changing from run to run. It's never as low as the iPad's volume (which I generally keep quite low), but it certainly is varying from 100%.
Is JRemote trying to "transfer" the iPad's volume level to the DLNA renderer, even though no button presses have occurred?
Are you using build 442?
There shouldn't be an issue with that one.
Also, make sure optimize volume isn't on in MC for that zone.
-
Are you using build 442?
There shouldn't be an issue with that one.
Well, not yet. :) I'll give it a try when I return home this evening.
Also, make sure optimize volume isn't on in MC for that zone.
I'll double-check, but I don't think I've ever enabled that (for either the player itself or any zone). Just to clarify, the volume change I'm referring to was for the DLNA renderer itself.
Thanks,
Matt
-
Are you using build 442?
There shouldn't be an issue with that one.
I was only able to test it briefly last night, but it does seem better. The DLNA renderer's volume was at 100% and remained there.
-
JRemote should tell you, somewhere, how much time is left in the queue….IMHO.