Timeline for What is the most compatible compression/Codec to in Handbrake use for video that will be played in Chrome and Safari browsers?
Current License: CC BY-SA 3.0
5 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 20, 2015 at 19:23 | comment | added | Peter Cordes | Yeah I googled a bit after posting that comment. Unfortunately it seems there are a fair amount of HW decoders that support Main but not High, so a year or two of phones. I guess it makes sense that 8x8dct might require different logic blocks on a FPGA or ASIC, unlike the case for software where it's not hard. (CPU power to decode CABAC is the hard part for going from baseline to main, for software I think.) Anyway, blargh, are we never going to get rid of sub-optimally encoded videos, thanks to crappy devices? As soon as we do, devices with partial h.265 support will come out... square 1 | |
Jan 20, 2015 at 9:08 | comment | added | Duvrai | The Main profile recommendation comes from the mobile device world. For example most Apple A4 and A5 processors are H.264 Main profile limited. More specifically iPod Touch 4G & 5G, iPod 1 & 2, iPhone 4, AppleTV 2G & 3G (model A1427). Anything beyond is High profile. | |
Jan 20, 2015 at 6:11 | comment | added | Peter Cordes | Why would you ever use Main, not High, profile, for anything? I thought HW decoders were usually either baseline or high, so worse compression (no 8x8dct) for no or very small gain in combatibility. | |
Feb 17, 2014 at 14:47 | vote | accept | Clay Nichols | ||
Feb 16, 2014 at 13:26 | history | answered | Duvrai | CC BY-SA 3.0 |