JPLAY for iOS

[sjj]

@Marcin_gps I downloaded the update and now I’m receiving the message Error sending action to renderer when I try to play something. I rebooted my iPad and uninstalled and reinstalled JPlay but still get the error. Previous to this had no issues. Currently using Qobuz and Moode as my renderer. Also Mconnect still works with no issues. Thanks

[sjj]

19 hours ago, sjj said:

@Marcin_gps I downloaded the update and now I’m receiving the message Error sending action to renderer when I try to play something. I rebooted my iPad and uninstalled and reinstalled JPlay but still get the error. Previous to this had no issues. Currently using Qobuz and Moode as my renderer. Also Mconnect still works with no issues. Thanks

I swapped Ropieee/XL for Moode on my renderer and everything works. Local files also work. For some reason Moode no longer works. I tried various JPlay settings and still doesn’t work. To help with troubleshhoting I Enabled Logs then tried Send Logs but nothing appears to happen?

[sjj]

2 hours ago, sjj said:

I swapped Ropieee/XL for Moode on my renderer and everything works. Local files also work. For some reason Moode no longer works. I tried various JPlay settings and still doesn’t work. To help with troubleshhoting I Enabled Logs then tried Send Logs but nothing appears to happen?

I discovered the issue with Moode is related to a UPNP option labeled Check Content. If set to Yes, I get the JPlay Error sending action to renderer. If set to No JPlay works and music plays. The description of this UPNP option in Moode is “Check that the input format is supported. Set this option to No if a control point or media server sends good audio data with bad metadata.”. I did notice now when playing music from JPlay that if I open Moode the Album cover and all related info such as track, album name, song name, bit info…is all set to Unknown. JPlay version 1.07 didn’t have this problem and I didn’t need to set this option in Moode to No and all related song info in Moode was displayed correctly.

[sjj]

6 hours ago, mnuno10 said:

Please do as @stefano_mbp pointed out and "Enable log, reproduce the issue, go back to log and send it before disabling it.".

Send them to our support email: [email protected]. 

Thanks. 

@mnuno10 I’ve tried this numerous times and whenever I select Send Logs nothing happens.

[sjj]

1 minute ago, mnuno10 said:

Are you using an iPad? If so can you put in landscape position and then click in send logs? It should appear one popover.

If it still does not work, please let me know.

@mnuno10 yes using iPad. Just tried again in landscaoe and portrait position and nothing happens when I select Send Logs. 

[sjj]

11 minutes ago, mnuno10 said:

That's odd. Can you click in "Delete logs", then "Enable logging", try to play some track and try to "Send logs" option again?

@mnuno10 same result, nothing happens.

[sjj]

1 minute ago, stefano_mbp said:

Are you clicking on the arrow on the right of the line?

I’ve tried clicking the arrow, clicking the wording Send Logs, clicked all over the Send Logs line nothing happens.

[sjj]

@mnuno10  I just updated JPlay to 1.08 on my M1 Mac and was able to reproduce the error and send the logs to the email address you provided. Can't send logs from my iPad.

[sjj]

 

On 2/3/2023 at 1:18 PM, sjj said:

I discovered the issue with Moode is related to a UPNP option labeled Check Content. If set to Yes, I get the JPlay Error sending action to renderer. If set to No JPlay works and music plays. The description of this UPNP option in Moode is “Check that the input format is supported. Set this option to No if a control point or media server sends good audio data with bad metadata.”. I did notice now when playing music from JPlay that if I open Moode the Album cover and all related info such as track, album name, song name, bit info…is all set to Unknown. JPlay version 1.07 didn’t have this problem and I didn’t need to set this option in Moode to No and all related song info in Moode was displayed correctly.

@Marcin_gps @mnuno10  Just installed version 1.09 and it fixed my issue as mentioned above. Thanks