Encode time is dependent on your horsepower. More horseys, less time - everybody knows that, but what they donât know is when you throw a VC-1 video track into the mix âHulk Hoganâ breaks down in tears with snot dribbling on his Girl Scout Uniform. VC-1 is one of those annoyances that requires a fantastic âsingle thread ratingâ because it can only use one of your 98 cores. Whatâs even more annoying is that almost nothing can deal with a VC-1 track so Plex has to transcode it for almost everything. Bummer, right? Right.
When I meet up with a VC-1 video track I clear my schedule, bite the bullet and turn it into something my devices can use. I donât need somebody transcoding a VC-1 stream while Iâm being killed by hoards of Doom 2016 Baddies. I need to see my head fly off in full technicolor, all frames intact. Otherwise, why play, right? Right.
It takes as long as it takes. I have a pretty decent single thread rating so it doesnât take that long. I add 35% or so to the standard encode time.
Anyway, once you get your chops down and find the magic formula for video streams that you can live with you can play around with audio tracks and containers with ease using this puppy:
http://www.xmedia-recode.de/en/download.html - XMedia Recode
Basically you encode, or pass through, the best audio track in Handbrake and donât forget those commentary tracks. Then you can run that file through Xmedia Recode to back that audio track up in any slot while creating a compatible audio track that will direct play on your Roku, for instance. Roku likes to have itâs Direct Playable track in Slot One. If you put your big guns up front and want to stick a Direct Playable track further down Roku transcodes that track because itâs not in Slot One. I have heard other people say this doesnât happen to them, but it happens to me and I canât seem to make it not happen. Maybe Iâm not holding my foot off the floor while swinging my arms wildly enough during playback. Itâs hard to say. Maybe youâll have better luck than I have. I hope so.
The bottom line is that once you get a good video track you can play around with the audio tracks, creating, moving, backing up and most importantly for me - normalizing.
Donât you just hate it when you crank the volume up to 90 to hear Mumblinâ Matthew speak his lines in Interstellar (2014) only to be blown through the picture window in your living room when the effects kick in? I know I do. I also hate scheduling those expensive ear drum replacement surgeries. Man, thatâs a real buzz-kill right there.
Xmedia Recode will bring those audio levels up to 89db (usually from 73db) so you can actually hear them. It doesnât âcompressâ, just brings up the gain. Itâll fix just about anything except Interstellar (2014). The ONLY thing Iâve found to fix that mess is the active DRC in my Windows Audio section and for that reason I still maintain the HDMI hookup to the TV from the Computer so I can bypass Plex and everything else when nothing else will do the job. There are a few audio nightmares out there, not many, but when one is identified itâs dealt with accordingly.
AC3 5.1 tracks have been around a long time and are fairly commonplace. AAC 2.0 tracks have been around even longer and are more likely to Direct Play than anything else, but theyâre just stereo. One speaker per earhole. I havenât yet evolved to multiple aural canals (and donât need special glasses that hang from multiple ears), but if you have youâll probably want to stick with at least one of your tracks in an AC3 5.1 format. You can throw that DTS track in the back somewhere for safe keeping in the hopes that someday Plex will be able to pass it through to something, which seems to be a hot topic of conversation on just about every Plex Subforum we have.
Well, enough of my ramblings for now. I have a couple of encodes to pass through Xmedia Recode for the final audio work before they hit the library.