Early adoption of new technologies is usually mired by complications, but what’s been shitting me lately is the trend manufacturers seem to have of pushing tech to market that doesn’t even support the main draw card of the product. I purchased a Samsung UA55F9000 UHD TV in December 2013: the month they were released, solely for the 4k capability. Fast forward a year later and I’m still fighting with the upper echelons of Samsung tech support concerning the absolute necessity of being able to use my 4k TV to play 4k content.
You see, the manual states the TV will play a
.S4ud file: essentially a
H.264 video and an
AC3 audio stream multiplexed into a
TS container. No firmware update since the TVs manufacture has actually allowed this. A second possibility is to use QFHD - four separate HD streams that are then joined together to yield a 4K stream. After quite a conversation with Samsung tech support it was elucidated that this is actually happening in-store when you see these TVs in action with those amazing demos.
So off I went and cut up a few sample files and tested it out - no dice. Two of the four segments were playing, the others were a jaggered mess. After more back and forth with the guys in tech, turns out the demo capability had been broken somewhere in an early firmware patch that was propagated through a number of subsequent versions. Thankfully, this debacle has been fixed and I’m now happily viewing my 4K content in all its glory. Downside is it’s still QFHD, not a nice single
There’s also a number of caveats with this method, for instance the files must be named
a is the main file (top left), and the
b-d files are
Long story short, I’ve developed a few scripts to automatically take care of all of these problems. They could use a little cleaning up, and wifi connectivity problems at my new house has seen me jump back to Windows recently - so these are batch files rather than bash scripts. Shouldn’t be too hard to port them yourself though.
UHD 4K is 3840×2160 pixels, although Digital cinema 4K is 4096×2304. Before the resolution standards settled down, a plethora of content out there was letterboxed in some way, but 4096 pixels wide. Considering this, there are three scripts below for each of these three possibilities. Granted, I could set this up to find the resolution first but brevior saltare cum deformibus mulieribus est vita amiright? Call these snippets
conv.bat or something to that effect, and run
conv inputFile.mp4 (for example) at the CLI. The output will be four files titled with the convention above, where
* will be
inputFile (to keep things in order, these files output to a folder
qfhd and the converted file is archived to a
converted folder). Then, you’ll need to put them on a fast USB3 stick and plug it into the TV. You’ll only see the
a file, run it and actually enjoy that massive hole you previously burnt into your wallet.
Ffmpeg is the only dependency you’ll need. Alter the rate factor in the script (
-crf) to your liking; but I’ve found 15 works just fine.