Samsung D series TV won't play transcoded H263-VP6 .flv files

[Former user]

Well after a lot of analysis and testing, I've finally pinned this problem that I refered to in ticket 425 and the lost connection post http://forum.serviio.org/viewtopic.php?f=10&t=3490&start=40 to the following. I hope you can fix it.

The default profile for Samsung C/D contains the following lines, that remux h264.flv to h264/AC3.ts and reencode all other .flv files to mpeg2video/AC3.ts for both local and online files. {{{ #!python

<Video targetContainer="mpegts" targetACodec="ac3"> <Matches container="flv" vCodec="h264" /> </Video>
<Video targetContainer="mpegts" targetACodec="ac3" targetVCodec="mpeg2video"> <Matches container="flv" /> </Video> }}}

I have verified these transcodings work correctly on both the Samsung D series BR and TV, by observing the creation of the transcoded files, and their playback with one exception: When the source .flv file contains a VP6 or Sorenson Spark H263 video stream, the TV refuses to play the transcoded file and issues a non supported video codec message. The BR however plays the transcoded file correctly. This happens for both local and on-line VP6 or H263.flv files.

Both the TV and the BR are using the same Samsung C/D profile and the created transcoded file is identical on both devices.

This impacts the ability to play "low quality" (VP6 and H263) you-tube videos, and to play the on-line abc-news feeds http://abclocal.go.com/kgo/xml?id=7095531&param1=mrss which use VP6/mp3.flv files, on the Samsung D series TV, which the BR plays correctly..

Attached are logs of the playback of an abc online file on both devices. As you can see the TV log contains a "[WebServer] I/O error: Connection reset by peer: socket write error" message.

[Petr Nejedly]

Does this still happen even after your change in #432 ? The online config used to include FLV (all) to mpegts, it's now gone so the online files should use the local configuration above only (where before they took the online config as a priority)

This ticket also must retrofit all current profiles and generic profile with the vp6f codec online config.

[Former user]

"Does this still happen even after your change in #432 ? The online config used to include FLV (all) to mpegts, it's now gone so the online files should use the local configuration above only (where before they took the online config as a priority)"

Yes, this bug is after the transcoding has been done, per the local configurations which transcode all flv's, and it applies to both online and local flv files. The transcoded file is correct and I can play it on the TV as a file in serviio but it will not play on the TV automatically after it is transcoded.

"This ticket also must retrofit all current profiles and generic profile with the vp6f codec online config"

I'm not sure what this means but the all vp6.flv files are converted to mpeg2video and remuxed to ts per the second local rule:

<Video targetContainer="mpegts" targetACodec="ac3" targetVCodec="mpeg2video">
           <Matches container="flv" />

I'm not aware of other containers that contain VP6.

[Petr Nejedly]

what if you change it to mpeg instead of mpegts for the vp6 fvl files?

[Former user]

I will test that and report back, but as I reported the problem is not in the transcoding. The files transcode correctly and if I grab the .stf and rename it to .mpg, I can play that file on the TV, so the break is in the passing of the correctly transcoded file to the TV. I have also determined that the problem is more widespread because avc/vorbis.mkv files are also transcoding correctly and playing with the BR but not the TV. I'm in the process of building a set of test files to test each of the Samsung C/D profile transcoding rules in an effort to pin this down completely.

[Former user]

Eureka! The problem turns out to be bitrate. If maxbitrate is not set when transcoding to mpeg2video, the samsung D series TV will issue an unsupported video codec message, regardless of the actual file bit rate. So every transcode to mpeg2video, whether h264L5.1, h263, or VP6 fails. Adding maxVBitrate="8192" to each transcoding statement fixed it.

I also added a rule to force a reencription of any mpeg2video.ts to a maxVBitrate="8192"

Only problem is that files with valid bitrates will get rencoded too, so I'll raise a separate request for a new "VBitrate Exceeds" attribute for use with matches.

I'll also raise a request for a revised Samsung C/D profile that will work for D series TV's and BR's as per the attached.

[Former user]

Zip this bug remains in 6.1 beta3 . It is still necessary to add maxVbitrate to the transcode rule to get these h263.vp6 transcoded videos to play on D series TV's using the latest 1019 firmware just released.

[newyear2016happy]

iDealshare VideoGo is just the right FLV to Samsung TV converter which can convert downloaded FLV videos to Samsung TV supporting formats. It also can directly download FLV from YouTube to Samsung TV supported video format. Besides iDealshare VideoGo can also convert FLV to play on Samsung Galaxy S5, S4, S3, S2, Grand, Trend, Core, Note, Tab and etc. Moreover, this ideal FLV Samsung TV Converter also can convert Samsung TV unsupported other video formats like WebM, WTV, MOV, F4V, MVI, AVCHD, MTS, Apple ProRes, and etc to play on Samsung TV

[Former user]

Spam????