Thu Oct 13, 2011 4:10 am by jhb50
I've had a lot of experience with the extraction of You-Tube videos and so your post intrigued me and caused me to analyse what is happening. I too have a D series Samsung that produced the same result. What you have run into is a bug in the youtube.groovy that is allowing files greater than 1080p to try and play, and since the TV is limited to 1080p you get a video codec unsupported message.
Your "noah in the park" video is a 1280p video in its original form as a result of turning thye camera sideways so you get a 720x1280 video rather than a 1280x720 video, which Youtube stores as fmt=38. When played on a computer, Youtube offers resolutions from "original (1280p), 1080p, 720p, 480p, 360 and 240, and all will play. When played with Serviio, and "High quality", groovy will select the highest quality (in this case fmt=38) which will fail. "Medium Quality" will select fmt=34 which is a 360p AVC.flv file which Serviio will mux to AVC.ts per the C/D profile and play correctly."Low quality" will always select fmt=5 wich is a 240 Sorenson Spark H263.flv file which Serviio will reencode to an mpeg2video in a ts container mpeg2.ts per the C/D profile which will play correctly on Series D BR players, but due to a bug (see ticket #249) will not play on series D TV's and will give the same video codec unsupported message.
Attached is a modified youtube.groovy file that will only use youtube formats up to 1080p when requesting high quality, and will play your files, so your wife may continue to take her great videos any way she wants and play them back in top quality. Enjoy!
I've opened a ticket #431 refering to this post and the groovy fix.
- Attachments
-
Youtube.groovy
- Max 1080p groovy
- (6.19 KiB) Downloaded 552 times