JPLAY for iOS Is Now Available

11 hours ago, Le dom said:

Hi concerning Minimserver I've noticed for a long time yet that we have to tag multiple album like that, for example:

 

"Album title - Disc 1" instead of "Album title (Disc 1)".

 

Result I have no problem in Jplay iOS with multiple albums.

 

 

Thank you, that worked great!

I hadn't noticed the LMS logos. 

Here is a possible explanation, though:  When I reinstalled JPlay this morning, it saw LMS (but not JRiver) when I started it up. Surprised, I tried to load the library. It very slowly got to 3% indexing, then stopped with "error" being the only error message. I then removed LMS as the server. As usual when removing a server, JPlay stalled, so I closed JPlay out.

I restarted JPlay and LMS, as I expected, was nowhere to be found. I therefore reinstalled Minim as before.  

I believe that, logo notwithstanding, this is the Minim database, not the LMS. I say this because that is the only connected library shown in the settings.  Also, there are a couple of anomalies in the Minim database that don't appear in my other libraries.  They are present in JPlay's, as well. My criticisms of JPlay don't extend to its display of these anomalous entries, which are in the original Minim database. 

Here is something interesting, though: JRiver showed up in the server pick list after I double checked whether I searched My Library rather than the local database. Unlike LMS, in its brief shiny moment, JRMC completed its indexing and now is scanning. If it completes the scan, I will remove the Minim server so that I don't have double entries and then will look at what JRiver presents. The JRMC database, for me, is the gold standard, so I would not expect the little bit of Minim weirdness to be present in JPlay when JRMC is the only library in the database. Will let you know how it completes. 

18 minutes ago, Mike Rubin said:

I hadn't noticed the LMS logos. 

 

Here is a possible explanation, though:  When I reinstalled JPlay this morning, it saw LMS (but not JRiver) when I started it up. Surprised, I tried to load the library. It very slowly got to 3% indexing, then stopped with "error" being the only error message. I then removed LMS as the server. As usual when removing a server, JPlay stalled, so I closed JPlay out.

 

I restarted JPlay and LMS, as I expected, was nowhere to be found. I therefore reinstalled Minim as before.  

 

I believe that, logo notwithstanding, this is the Minim database, not the LMS. I say this because that is the only connected library shown in the settings.  Also, there are a couple of anomalies in the Minim database that don't appear in my other libraries.  They are present in JPlay's, as well. My criticisms of JPlay don't extend to its display of these anomalous entries, which are in the original Minim database. 

 

Here is something interesting, though: JRiver showed up in the server pick list after I double checked whether I searched My Library rather than the local database. Unlike LMS, in its brief shiny moment, JRMC completed its indexing and now is scanning. If it completes the scan, I will remove the Minim server so that I don't have double entries and then will look at what JRiver presents. The JRMC database, for me, is the gold standard, so I would not expect the little bit of Minim weirdness to be present in JPlay when JRMC is the only library in the database. Will let you know how it completes. 

Interesting. 
 

I hope JRMC works. Then you can edit metadata if you wish, at any time, in a nice interface (JRMC). I like Minim because it runs on my NAS, but it isn’t without faults that’s for sure. 

20 minutes ago, The Computer Audiophile said:

I like Minim because it runs on my NAS, but it isn’t without faults that’s for sure

Could be … but since now, more or less 7 years, the few supposed “faults” were due to incomplete/incorrect tagging. “Unfortunately” a quite deep knowledge of Minimserver rules is strongly needed, the user guide is very exhaustive but sometimes it’s better to ask Simon the right solution, he is very responsive.

Throw a veiled discredit on something that works well until proven otherwise, because there is no clear proof of malfunctions, it seems really unfair ... better to look at cases where the anomalies are there for all to see
... my two cents

4 minutes ago, stefano_mbp said:

Could be … but since now, more or less 7 years, the few supposed “faults” were due to incomplete/incorrect tagging. “Unfortunately” a quite deep knowledge of Minimserver rules is strongly needed, the user guide is very exhaustive but sometimes it’s better to ask Simon the right solution, he is very responsive.

Throw a veiled discredit on something that works well until proven otherwise, because there is no clear proof of malfunctions, it seems really unfair ... better to look at cases where the anomalies are there for all to see
... my two cents

 

As this isn’t a Minim thread, I’d rather not go into my issues with the app. 
 

I’ve never used an app without faults. Given the audience for apps usually has very different use cases, it’s impossible to deliver a perfect app. 

P.S. I really like Simon and think he does a great job. I can’t believe he didn’t start charging for his app for so long. 

2 hours ago, The Computer Audiophile said:

Interesting. 
 

I hope JRMC works. Then you can edit metadata if you wish, at any time, in a nice interface (JRMC). I like Minim because it runs on my NAS, but it isn’t without faults that’s for sure. 

Well, good news.  JRiver indexed and scanned and now it is playing into HQPlayer Embedded in my living room. I am not betting a single penny that JPlay will remain connected to it for five more minutes after three weeks of failing to discover it, but all is right at the moment, except for the slow mirroring thing in the various search keystroke contexts. 

The album/track display anomalies about which I posted are gone. Discs in multi-volume sets are shown as separate albums, as I prefer. Album listings are of actual albums, not that unholy mixture of albums and unplayable tracks. 

This suggests to me that the problems I had are Minim issues or if you prefer my own fault for not giving Minim what it wants to see.  However, JPlay itself plays a role in this because, as I pointed out, Minim doesn't have the album/track issues in any other controller app that I have. 

I am happier - for the moment, at least. Let's see if this holds. 

10 hours ago, Mike Rubin said:

Well, good news.  JRiver indexed and scanned and now it is playing into HQPlayer Embedded in my living room. I am not betting a single penny that JPlay will remain connected to it for five more minutes after three weeks of failing to discover it, but all is right at the moment, except for the slow mirroring thing in the various search keystroke contexts. 

 

The album/track display anomalies about which I posted are gone. Discs in multi-volume sets are shown as separate albums, as I prefer. Album listings are of actual albums, not that unholy mixture of albums and unplayable tracks. 

 

This suggests to me that the problems I had are Minim issues or if you prefer my own fault for not giving Minim what it wants to see.  However, JPlay itself plays a role in this because, as I pointed out, Minim doesn't have the album/track issues in any other controller app that I have. 

 

I am happier - for the moment, at least. Let's see if this holds. 

As I suspected, too good to be true.   JPlay worked without incident all afternoon, but I added a couple of albums and revised some metadata, so I wanted to do an update scan.  I get an error message telling me that JRiver is offline and that I should so a new scan to connect it.  Trying to run a new scan results in the same message.

I can use JPlay with the JRiver database that I loaded today, but I guess I won't be able to update it or, if I remove it, to recreate the database from scratch.

Very disappointing, but, honestly, with this server's spotty discovery history, I wasn't expecting anything different. 

Unfortunately, it seems to me that you have some chaos in your settings, try to clarify where you are on which platform and try again. I am not experiencing any of the problems you describe in my setup.

@mnuno10, thank you. I will wait for the next update before trying to do more troubleshooting my email.

I remain concerned that your app does not reliably find and retain JRiver on my network when other DLNA controllers can. (My network uses the ISP's own simple router, my UniFi access points are connected to that router only through dumb switches, and the JRiver server PC is connected by copper directly to that router, so it should be a simple enough network to navigate and other products can. I acknowledge, though, that I don't understand networking at a very technical level.) 

It remains important to me that I be able to use JRiver or Logitech Media Server as this thread has taught me that my metadata practices are not what Minimserver prefers.  Unfortunately, it is only to Minimserver (which is on a NAS, not a PC) that JPlay regularly detects.  LMS now detects regularly, but JPlay does not seem able to index its library successfully. 

I eagerly await the next update. 

On 12/23/2022 at 9:58 PM, Marcin_gps said:

No, you will have to update via AppStore. I will inform here when the update is available. 

 

This is not possible at the moment. 

 

Not yet, but I know someone who has that combo. We have to investigate. 

 

Best regards,
Marcin
 

Yes thanks for looking into this Marcin. As you know, the issue is that JPlay can't find the Chord Poly (or 2go) as a wifi hotspot and says that Jplay cannot launch the app since it can't see the Poly's wifi hotspot. Consequently, it says that there is no active internet connection is available. MConnect, 8Player, and Glider all connect with the Poly's wifi hotspot without any difficulty.

11 minutes ago, vlomdmdiv said:

Yes thanks for looking into this Marcin. As you know, the issue is that JPlay can't find the Chord Poly (or 2go) as a wifi hotspot and says that Jplay cannot launch the app since it can't see the Poly's wifi hotspot. Consequently, it says that there is no active internet connection is available. MConnect, 8Player, and Glider all connect with the Poly's wifi hotspot without any difficulty.

Technically the apps don’t connect to any network, including WiFi. Your operating system connects to that network. The apps use the networks available from the operating system. 

@Marcin_gps @mnuno10 … about Composers (using Minimserver)

I have albums were tracks are from different Composers, why are they shown as:

• composer 1
• composer 2
• composer 1, composer 2

this is unuseful and a little bit confusing, in my opinion it should be just

• composer 1
• composer 2

see examples from different views here

1 hour ago, stefano_mbp said:

@Marcin_gps @mnuno10 … about Composers (using Minimserver)

I have albums were tracks are from different Composers, why are they shown as:

• composer 1
• composer 2
• composer 1, composer 2

this is unuseful and a little bit confusing, in my opinion it should be just

• composer 1
• composer 2

see examples from different views here

 

 

It seems that MinimServer is returning "composer1, composer 2" in the same artist role="Composer" tag, and without any splitter active app will assume "composer1, composer 2" as a single composer name. But to debug, please enable logs, navigate to that album using "By Folder" navigation and send us the logs. With them we should be able to know for sure what is happening.

13 hours ago, vlomdmdiv said:

Yes thanks for looking into this Marcin. As you know, the issue is that JPlay can't find the Chord Poly (or 2go) as a wifi hotspot and says that Jplay cannot launch the app since it can't see the Poly's wifi hotspot. Consequently, it says that there is no active internet connection is available. MConnect, 8Player, and Glider all connect with the Poly's wifi hotspot without any difficulty.

Your Poly hotspot has an active internet connection? App needs internet connection to validate your subscription status.

14 hours ago, Mike Rubin said:

@mnuno10, thank you. I will wait for the next update before trying to do more troubleshooting my email.

 

I remain concerned that your app does not reliably find and retain JRiver on my network when other DLNA controllers can. (My network uses the ISP's own simple router, my UniFi access points are connected to that router only through dumb switches, and the JRiver server PC is connected by copper directly to that router, so it should be a simple enough network to navigate and other products can. I acknowledge, though, that I don't understand networking at a very technical level.) 

 

It remains important to me that I be able to use JRiver or Logitech Media Server as this thread has taught me that my metadata practices are not what Minimserver prefers.  Unfortunately, it is only to Minimserver (which is on a NAS, not a PC) that JPlay regularly detects.  LMS now detects regularly, but JPlay does not seem able to index its library successfully. 

 

I eagerly await the next update. 

In the next update app should find faster previous connected devices as long as they keep their IP addresses. This should help with JRiver issue.

Do you use some "custom" MinimServer configuration or do you use the default ones? Its odd that app is not able to index MinimServer correctly, but when the new version came out please give it a shot and report your results to us. 

10 minutes ago, mnuno10 said:

It seems that MinimServer is returning "composer1, composer 2" in the same artist role="Composer" tag, and without any splitter active app will assume "composer1, composer 2" as a single composer name. But to debug, please enable logs, navigate to that album using "By Folder" navigation and send us the logs. With them we should be able to know for sure what is happening.

Here it is, thanks

logFile.txt

On 12/31/2022 at 12:05 PM, Norton said:

In principle I like the app and want it to succeed; when playback works it’s nice to use, to have  Qobuz/ local integration, and somehow, the SQ seems better than with JRiver or MConnect UPNP options.

 

However, in practice (1.0.2) it’s still unusable with my Oppo205 as renderer- first track plays fine, second track usually also plays, but shortly after track 2 starts the loading symbol appears and play then stops after track 2 and can’t be restarted.  Have tried various combinations of settings.  Mainly trying with Qobuz, but same seems  to be true with local library.  My Oppo is 100% solid with JRemote and much better, if not perfect, with MConnect. Have tried various combinations of settings, usually with gapless  disabled as per MConnect, but with no luck.  Log file sent.  
 

I have cancelled my subscription before end of trial period.  In case these issues can be addressed, will I be able to access a further trial period via the app?  Thanks.
 

 

We will allow users to have a new Trial period. We are make some improvements and bug fixes before it. We will make an announcement when that happen, but it should not take that long. But contact us using "[email protected]" so we can help you debugging.

11 minutes ago, stefano_mbp said:

Here it is, thanks

logFile.txt

MinimServer is returning all composers in the same tag, so app is assuming as a unique composer name.

From your debug file: "<upnp:artist role=\"Composer\">Gregorio Allegri (1582-1652), Giovanni Pierluigi da Palestrina (1525-1594)</upnp:artist>".

In MinimServer's "upnpCustom" field do you have composer for multiTag property? Something like this: "multiTag={artist,genre,composer,albumArtist}". That should fix your issue.

9 minutes ago, mnuno10 said:

"multiTag={artist,genre,composer,albumArtist}". That should fix your issue.

It does indeed! Thanks

5 hours ago, mnuno10 said:

We will allow users to have a new Trial period. We are make some improvements and bug fixes before it. We will make an announcement when that happen, but it should not take that long. But contact us using "[email protected]" so we can help you debugging.

Thanks.  Have sent emails with  log files. 

6 hours ago, mnuno10 said:

In the next update app should find faster previous connected devices as long as they keep their IP addresses. This should help with JRiver issue.

Do you use some "custom" MinimServer configuration or do you use the default ones? Its odd that app is not able to index MinimServer correctly, but when the new version came out please give it a shot and report your results to us. 

Thank you. 

Standard Minim server configuration, but I tag multi-disc volumes as "Album Name (Disc x)" rather than "Album Name - Disc x," which, I learned in this thread, Minim supposedly prefers.  (For some reason, though, Minim has no problem creating separate entries for hi-res volumes that are tagged as "Album Name (Disc x) [resolution].") 

JRiver always is at the same IP address. I will watch for the next release. 

17 minutes ago, Mike Rubin said:

Thank you. 

 

Standard Minim server configuration, but I tag multi-disc volumes as "Album Name (Disc x)" rather than "Album Name - Disc," which, I learned in this thread, Minim supposedly prefers.  (For some reason, though, Minim has no problem creating separate entries for hi-res volumes that are tagged as "Album Name (Disc x) [resolution].") 

 

JRiver always is at the same IP address. I will watch for the next release. 

MinimServer seems to allow "Album Name (Disc x)", check it here:

https://minimserver.com/ug-browsing.html -> "Multidisc albums" section

Are your tracks tagged with correct TRACKNUMBER and DISCBUMBER? Have you tried to add "showAllDiscs=true" to serverOptions field in "MinimServer Properties" -> "Advanced"? 

There is also a "mergeFolderAlbums" that you can change to false.

https://minimserver.com/ug-properties.html 

To easily test it, create a small library with albums that are not correctly indexed, make this folder the only ContentDir in MinimServer. And try to change these properties, do a MinimServer rescan and a "Sync" in JPLAY app and check what you get in the app.

21 minutes ago, mnuno10 said:

MinimServer seems to allow "Album Name (Disc x)", check it here:

https://minimserver.com/ug-browsing.html -> "Multidisc albums" section

 

Are your tracks tagged with correct TRACKNUMBER and DISCBUMBER? Have you tried to add "showAllDiscs=true" to serverOptions field in "MinimServer Properties" -> "Advanced"? 

 

There is also a "mergeFolderAlbums" that you can change to false.

https://minimserver.com/ug-properties.html 

 

To easily test it, create a small library with albums that are not correctly indexed, make this folder the only ContentDir in MinimServer. And try to change these properties, do a MinimServer rescan and a "Sync" in JPLAY app and check what you get in the app.

Thank you. I will try these suggestions. I will am not religious about inserting the disc number into the "disc number" metadata field as other apps have no trouble keeping the discs separated by the album title, but I will test to see if this is the reason for the differences in visibility.