Could there just be a cut for iOS 5-7 to only have 4 badges per line? Seems like there is room unless it would still have an issue depending on the size of the badge(s). In that case maybe 3 per line for the lower iOS revisions? Just thinking out loud...
Firmware is the same as wahlman so yes maybe they did change the space (maybe it’s time for me to upgrade)
I noticed the link address months ago when setting a new instance up for a friend and forgot to raise it when I got home, it’s only when I saw the page in the video that jogged my memory
Could there just be a cut for iOS 5-7 to only have 4 badges per line? Seems like there is room unless it would still have an issue depending on the size of the badge(s). In that case maybe 3 per line for the lower iOS revisions? Just thinking out loud...
Yep.... the badges aren't supported in firmware 5 at all, so I guess we cut completely for firmware 5, limit the number for firmware 6 and display them all for firmware 7.
Now on firmware 6, which do we display? Resolution, video codec and audio codec?
Not sure what would be the best solution im not a XML pro by any means. I was thinking just keep it 3 per line just to keep it easy but I'm not to sure what would be the best solution for iOS 6 (7) badge wise. I would be willing to test any changes when I get some time later which I'm basically out of today currently.
Edit - Ah I see what you mean now, limit it to three but which three badges. What I meant was create an additional line for another set of badges under the existing badge line (if possible of course) after limiting the first badge line to 4 or 3 since there seems to be room (space) under the initial line.
Roidy, can you limit 4 badges per row? so next badge would be on next row below the first one. so they won't be cut truncated due to texts next to it.
Yep, I guess a good solution would be on firmware 6 place the video badges on one line and the audio badges on another.
I tried spreading the badges over two lines and to be honest it looks kind of odd... This is the solution I've come up with, give this version of XMLConverter.py a try and let me know if it displays correctly. Basically it just limits the number of badges to 4.
File removed
When I try the new XMLConverter.py and delete the old XMLConverter.pyc then restart PlexConnect to generate a new .pyc it says this in the settings tab and I cannot access any libraries using the latest commit as of this post signed into myplex or not:
Discover Plex Media Servers: -1
Yeah... changes in XMLConverter plus the JS stuff won't always be compatible with older files...
I did notice on a movie when having four badges the last one is still cut off even without using the test file using the latest commit. The badges in use were as follows for the movie I tested.
1080P MP4 H264 AAC
The acc badge was just barely cut off. So maybe limit it to three to avoid this or create a separate line/row for the lower iOS revision. If you decide to go with three and not the separate row my personal preference would be resolution, video container and audio codec but I would imagine it would differ preference wise per user. Maybe another solution would be to enable/disable which badges are in use in the settings tab so everyone could decide which ones they would like to use which would enable them to also limit the number of badges in use. Just throwing ideas out there…
Ah, you pushed a newer commit that is why the test file wouldn’t work, that makes sense.
>>enable/disable which badges are in use in the settings tab
Really? An setting for each badge? Come on...
Questions:
- What happens for a file containing multiple audio streams? How is shown badge selected?
- Which badges are helpful for the user? I understand that the casual watcher might be interested in SD, 720, 1080, because it will affect his video quality. Same with mono, stereo, 5.1 audio. But why would he care about the container or codecs? That's stuff PMS/Plex/the aTV is supposed to handle...
You could have a setting for each group of badges such as:
Resolution badges: On/Off
Video Container badges: On/Off
Video Codec badges: On/Off
Audio codec badges: On/Off
Audio channels bages: On/Off
This would solve the issue for iOS 6 since you could simply disable which ever group of badges you don't desire/require and also give the end user more flexibility on what they prefer to be displayed on their aTV's. Again just to be clear, just trying to assist in solving this iOS 6 cut off issue by throwing ideas out there that could also be solved by removing them completely as well. What I meant by enable/disable was by badge group type not individual badges themselves which obviously makes no sense.
Questions:
- What happens for a file containing multiple audio streams? How is shown badge selected?
Same as the web player, it reports the audio track from the element. As to how PMS picks which audio stream to use in the element I'm not sure, it looks as if it's the stream with the highest number of channels.
- Which badges are helpful for the user? I understand that the casual watcher might be interested in SD, 720, 1080, because it will affect his video quality. Same with mono, stereo, 5.1 audio. But why would he care about the container or codecs? That's stuff PMS/Plex/the aTV is supposed to handle...
I find the codecs useful to determine weather or not the file will be transcoded.
You could have a setting for each group of badges such as:
No, I agree with Baa.... 5 different options just for a media badge feature is ridiculous.
Some thing more along the lines of one option like:-
Media Badges: Off/Simple/Full
With Simple being:- Resolution - Audio Codec - Number of Channels, this would then be the same as the PMS web interface.
And Full being all of the badges.
>>I find the codecs useful to determine weather or not the file will be transcoded.
Well, then you have to add a note about the bandwidth, too. And compare that to the settings of either local or remote.
I don't know... using the transcoder (or not) shouldn't affect your evening movie, should it?
I don't know... using the transcoder (or not) shouldn't affect your evening movie, should it?
I guess not... but some people like to know this information.
I guess you could also say that having half the nice features that PlexConnect currently has doesn't affect your evening movie either does it, but we have them anyway :)
Sounds even better. Like I said it was just an idea but in the end you guys know best, just trying to mainly give feedback since you had asked.
H.265 codec, and 2K and 4K resolution badges please. After all, future proofing is a wise idea.
3D
the XVID badge was added and then taken away again.
why?
