MrMC

Everbrave wrote: 20 Jul 2019, 15:24 Actually, The new .33 Server Version on Windows, solved the problem I had with all previous versions. Now, the Movies library behaves loads and behaves correctly (it didn’t load at all before).

More details please, like your Video Settings for Flatten Hierarchy, so we know what behaves normally or not and with what settings

Because latest MrMC beta doesn't change anything in the behavior I described in my previous post with Emby beta Server 4.2.0.33 and tvOS 12.3, which is current stable tvOS version.

Everbrave wrote: 20 Jul 2019, 15:24 As for the Amber skin, pressing on Movies, shows all movies nodes on all Plex and Emby servers. Collections show up with the artwork as you mentioned.

Define Nodes, so we are talking about the same thing.
Below the Nodes (or how it's called) I was talking about : *Screenshot from iOS version, but tvOS version shows same
Notice the inconsistency in number of "Nodes" shown, I talked about earlier.

Define Artwork, because I was talking about the Box Set artwork and NOT the individual Movie Artwork.
Individual Movie Artwork is shown, but the Box Set/Collection Artwork like below, is NOT:

Not sure if beta related. When downloading subtitles, stopping the movie/show, hitting play again, I have to re-download them.

Everbrave wrote: 20 Jul 2019, 10:14
TvOS 13 beta 4
Atmos Test media playback but Atmos is not indicated by the receiver.

EDIT: I have to take that back; it happened only once and I cannot reproduce this now; it doesn’t playback Atmos media at all, no video no sound!

EDIT 2: Plex tvOS plays the Atmos EAC3 Media correctly and the receiver shows the audio format correctly too.

Tried it too:
Tested Leaf and Amaze from here; https://www.dolby.com/us/en/guide/dolby ... ilers.html

Current beta of MrMC: no Audio and Video on TvOS 13 Beta 4.
But with original Plex client Video and (e)AC3 is played but my Atmos Soundbar doesn't identify it as Atmos for me

sahara wrote: 20 Jul 2019, 19:39 Not sure if beta related. When downloading subtitles, stopping the movie/show, hitting play again, I have to re-download them.

Debuglog please when you download and when you have to re-download

kolbem wrote: 20 Jul 2019, 20:36

Everbrave wrote: 20 Jul 2019, 10:14
TvOS 13 beta 4
Atmos Test media playback but Atmos is not indicated by the receiver.

EDIT: I have to take that back; it happened only once and I cannot reproduce this now; it doesn’t playback Atmos media at all, no video no sound!

EDIT 2: Plex tvOS plays the Atmos EAC3 Media correctly and the receiver shows the audio format correctly too.

Tried it too:
Tested Leaf and Amaze from here; https://www.dolby.com/us/en/guide/dolby ... ilers.html

Current beta of MrMC: no Audio and Video on TvOS 13 Beta 4.
But with original Plex client Video and (e)AC3 is played but my Atmos Soundbar doesn't identify it as Atmos for me

So on 3.8.* all is ok and issue is only showing on 3.9.0 TestFlight?

Chances are it’s tvOS beta related, difficult to troubleshoot tvOS beta moving target

Plex client transcodes it to something friendlier that tvOS can handle

amet wrote: 20 Jul 2019, 21:44

kolbem wrote: 20 Jul 2019, 20:36

Everbrave wrote: 20 Jul 2019, 10:14
TvOS 13 beta 4
Atmos Test media playback but Atmos is not indicated by the receiver.

EDIT: I have to take that back; it happened only once and I cannot reproduce this now; it doesn’t playback Atmos media at all, no video no sound!

EDIT 2: Plex tvOS plays the Atmos EAC3 Media correctly and the receiver shows the audio format correctly too.

Tried it too:
Tested Leaf and Amaze from here; https://www.dolby.com/us/en/guide/dolby ... ilers.html

Current beta of MrMC: no Audio and Video on TvOS 13 Beta 4.
But with original Plex client Video and (e)AC3 is played but my Atmos Soundbar doesn't identify it as Atmos for me

So on 3.8.* all is ok and issue is only showing on 3.9.0 TestFlight?

Chances are it’s tvOS beta related, difficult to troubleshoot tvOS beta moving target

Plex client transcodes it to something friendlier that tvOS can handle

Tried the 3.8.x from the Appstore.
Same Result.
Well - TvOS is still Beta so maybe no thing to care about now.

Btw. The Preview image while scrubbing shows the Videoframe.

Houston we have a problem....
*Filenames describes when it happened

amet wrote: 20 Jul 2019, 21:44

kolbem wrote: 20 Jul 2019, 20:36

Everbrave wrote: 20 Jul 2019, 10:14
TvOS 13 beta 4
Atmos Test media playback but Atmos is not indicated by the receiver.

EDIT: I have to take that back; it happened only once and I cannot reproduce this now; it doesn’t playback Atmos media at all, no video no sound!

EDIT 2: Plex tvOS plays the Atmos EAC3 Media correctly and the receiver shows the audio format correctly too.

Tried it too:
Tested Leaf and Amaze from here; https://www.dolby.com/us/en/guide/dolby ... ilers.html

Current beta of MrMC: no Audio and Video on TvOS 13 Beta 4.
But with original Plex client Video and (e)AC3 is played but my Atmos Soundbar doesn't identify it as Atmos for me

So on 3.8.* all is ok and issue is only showing on 3.9.0 TestFlight?

Chances are it’s tvOS beta related, difficult to troubleshoot tvOS beta moving target

Plex client transcodes it to something friendlier that tvOS can handle

Yes, it is definitely tvOS 13 beta related as well as Emby server as far as loading the Movies library (the issue I reported earlier) is concerned.
Plex is direct streaming (not direct playing) up to 4K, HEVC, HDR, mkv media files without using the enhanced player, i.e. using the native player. Atmos is indicated by the receiver, so, I assume that Plex is passing through the audio to the receiver. All these indicated that the native player in tvOS 13 has been greatly improved.

Montoya wrote: 20 Jul 2019, 22:38 Houston we have a problem....

Switching_Skins_01.png
Switching_Skins_02.png
*Filenames describes when it happened

I don’t understand, did this happen when you switched the skins?

Did this go away ? Debuglog please

Montoya wrote: 20 Jul 2019, 22:38 Houston we have a problem....

Switching_Skins_01.png
Switching_Skins_02.png
*Filenames describes when it happened

I’ve seen this too a few times. Quitting app resolves