Networks and Remotes > Remotes

JRemote (iOS) 3.37 beta

<< < (2/4) > >>

bob:

--- Quote from: AllanM on May 03, 2023, 04:54:44 pm ---Hello. I was told to put beta reports here.

Using iOS 16.4.1 in iPhone 14 Pro Max
Also using same OS on iPad Air 4

Both devices: Trying to add server with access key doesn't work. App shows a response from the server, but will not connect. Adding with IP Address works. All devices on the same home subnet/network.

--- End quote ---
Check the debug messages when adding by access key fails, you should get a good reason why.
I'm going to assume that your server access key is out of date. It shouldn't be since it updates periodically while MC is running.
You can find out by going to the access key in media network on the server and clicking test on it.

--- Quote ---iPhone:
-tap My Smartlists - Sorry, cannot recall if I created this folder, or if it's stock
- Tap a Smart Playlist
Tap the three bar menu in the upper right,
- when icon view is shown, the album header area at the top covers the text header at the top
- this seems to happen with Top Hits too. Just open Top Hits, then drag down on the page

--- End quote ---
I can duplicate that, thanks for the report.

--- Quote ---Both
- Trying to play any music file (All ALAC) on the device gives the error: "Audio Streaming Error" There was a problem playing the current audio file.

--- End quote ---
I can play ALAC untranscoded fine. So yours must be either
1) Protected or
2) Too high of a sample rate in which case you'll need to turn on transcoding. My iPhone XS will play 24 bit 48k ALAC.

--- Quote ---In JRiver Windows, there is a section call Streaming and a section called CloudPlay. In the app there is a section called Streaming, but I believe this is CloudPlay. It should likely be labeled CloudPlay.

--- End quote ---
In the App streaming means CloudPlay or RadioParadise. I agree it's a bit confusing.

AllanM:

--- Quote from: bob on May 04, 2023, 10:36:18 am ---Check the debug messages when adding by access key fails, you should get a good reason why.
I'm going to assume that your server access key is out of date. It shouldn't be since it updates periodically while MC is running.
You can find out by going to the access key in media network on the server and clicking test on it.

--- End quote ---
I deleted the server from the iPhone app and tried again with 3.37.423 and connecting via access key worked

--- Quote from: bob on May 04, 2023, 10:36:18 am ---I can play ALAC untranscoded fine. So yours must be either
1) Protected or
2) Too high of a sample rate in which case you'll need to turn on transcoding. My iPhone XS will play 24 bit 48k ALAC.In the App streaming means CloudPlay or RadioParadise. I agree it's a bit confusing.

--- End quote ---

Transcode on the JRemote settings is off. Turning it on, the music plays.
That said, JRemote should be able to play ALAC files natively.
None of my ALAC files are protected. Most are 44.1/16, and that's what I tried to play.
I tried the Files app with the same files, and they play fine, so the iPhone can play the files.
M4A is not checked in "Audio Formats to Convert" as the iPhone and iPad can play all my ALAC files.
Adding M4A to the list and changing the setting to always convert audio, and I still get the same error.
Any ideas or suggestion for the Audio Conversion options? Is there another place to check for transcoding settings?

bob:

--- Quote from: AllanM on May 04, 2023, 06:03:26 pm ---I deleted the server from the iPhone app and tried again with 3.37.423 and connecting via access key worked
Transcode on the JRemote settings is off. Turning it on, the music plays.
That said, JRemote should be able to play ALAC files natively.
None of my ALAC files are protected. Most are 44.1/16, and that's what I tried to play.
I tried the Files app with the same files, and they play fine, so the iPhone can play the files.
M4A is not checked in "Audio Formats to Convert" as the iPhone and iPad can play all my ALAC files.
Adding M4A to the list and changing the setting to always convert audio, and I still get the same error.
Any ideas or suggestion for the Audio Conversion options? Is there another place to check for transcoding settings?

--- End quote ---
The audio conversion options in MC don't affect remotes when they are playing back on the remote.
Not sure what's going on with your ALAC files. Like I said 48k 24 bit ones play fine on my JRemote.
Perhaps try converting format of one on the MC server back to ALAC (in other words, just making MC redo the ALAC file) and try that.
I suspect perhaps your ALAC files aren't formatted with the MOOV atom at the front which is required for streaming.
Converting in MC will do that.
You can also find utilities to do that in place with your files.

AllanM:

--- Quote from: bob on May 04, 2023, 07:10:57 pm ---I suspect perhaps your ALAC files aren't formatted with the MOOV atom at the front which is required for streaming.
Converting in MC will do that.
You can also find utilities to do that in place with your files.

--- End quote ---

Yep, this was the issue.
I could write a script to use ffmpeg or “mp4box -inter 0 in.mp4 -out out.mp4” to repair the issue, but given the size of my ALAC library, any suggestion for an easy to use "in-place" conversion utility (windows) is greatly appreciated.

Update: When I converted my entire FLAC library to ALAC (when I was using iTunes), I used MediaHuman Audio Converter (a front end for ffmpeg). It worked very well for my needs then. I have since used Picard and tagged all my files. They have a checkbox (off by default) for "Optimize for Streaming". I didn't think I needed that, so didn't check it. Ug. Now I simply need to run it through the same program, which I just tested will fix the issue. I just have to do it little by little, or my cloud back up will use up all my data for the month since all my music files will change!

Note, I'm trying "ffmpeg Batch AV Converter" as it allows for more control. I'm liking it.

Just thought I update here. Thanks for the help with the ALAC streaming.

 

vallemanden:

--- Quote from: bob on April 28, 2023, 12:14:21 pm ---We are getting ready to release version 3.37 as we believe that the problems with the API in versions > iOS13 are fixed.
If you are a beta tester and are still having issues with the 3.37 beta build please send feedback via the app or post it to this thread.

--- End quote ---
How to become betatester?

Navigation

[0] Message Index

[#] Next page

[*] Previous page