2017-01-19, 05:20 PM
Until now, I released my projects mainly on BD with menus. I like menus, and you? I bet so...
The only free software that allow authoring BDs with menus is MultiAVCHD. It works - I mean, it makes a BD structure, ready to burn on actual BD-R disc, but some users found the burned BD not compatible with their players. Moreso, the most known software media players (MPC and VLC) have often strange behaviour with BD menus (much worse than DVD). So, at the end, final users play directly the 00000.m2ts file, and all my work results useless... still, I love to have menus, and intro, and so no...
Lately I find that many, many users (me included) don't burn projects on discs anymore, but play the file directly on their PC; a plain single file is the best option - one could play it "as is", or remux it in a BD (or AVCHD) structure, and have a phisical media to play. Still, menus are lacking, and intro, if any, must be added at the beginning (and/or end) of the file, meaning much work, and "ethical" issues.
MKV "seems" ready to support menus, but when?
Then, I thought to a possible alternative. A simple HTML5 player!
Crazy idea? Maybe, that's why I'm posting it here, to have your opinions. HTML5 players are used by everyone, on YouTube, Vimeo, DailyMotion and so on. Yet, they are very limited in comparison to any software player. But this could work in our favour, somehow... frankly, when I want to watch a video clip on my PC, all I want to do (eventually) is to choose my language and/or subtitle tracks, and you?
We could release a project in a single folder, with one HTML file that will start the player, and one MVK (or other) video file containing the main feature. Well, almost useless, someone could point out, what is the difference instead of playing the file directly? Well, if there is more than one file - for example, bonus material, or an entire bonus project, having an HTML file with simple menu pointing to those files could be handy (and with a nice looking).
I've seen some free HTML5 video players that allow to add custom made buttons; why don't add one for the trailer? One for chapters, one for audio and subs selection? A bit like DVD/BD menus, but made in HTML/CSS; great appearance, and small footprint, can be read by any OS, also mobile - even if I don't think someone would normally watch an entire 1080p movies on a cellphone...
Another great option could be to add soft matte to an open matte release, avoiding two releases (and double work/time to upload/time to download/HDD space etc.)
Seamless branching "could" work, too... maybe it's possible to have HTML buttons in the menu for the theatrical and extended version, where for example TC calls file1+file2+file3, while EE calls file1+file4+file2+file5+file3... got the point? More investigation is needed, to understand if this is possible and the join are indeed seamless.
Now, codec support: video AVC for sure, also WebM and Theora; audio AAC, vorbis, opus, FLAC, mp3, WAV; containers WebM, Ogg, MP4; I'm pretty sure there is a way to support MKV container, and audio AC3 as well. What's about DTS? Of course, it's still possible to convert audio to a supported format.
What is the output quality of a video clip played in an HTML5 player (possibly without using Flash)? I mean, visually I have the same quality of a software player? And audio wise?
It will be great to have a standardized player, where each of us could put his logo, and other custom... "things", but still having a look'n'feel familiar with other releases...
Still another crazy, and useless, idea, or can have some potential?
The only free software that allow authoring BDs with menus is MultiAVCHD. It works - I mean, it makes a BD structure, ready to burn on actual BD-R disc, but some users found the burned BD not compatible with their players. Moreso, the most known software media players (MPC and VLC) have often strange behaviour with BD menus (much worse than DVD). So, at the end, final users play directly the 00000.m2ts file, and all my work results useless... still, I love to have menus, and intro, and so no...
Lately I find that many, many users (me included) don't burn projects on discs anymore, but play the file directly on their PC; a plain single file is the best option - one could play it "as is", or remux it in a BD (or AVCHD) structure, and have a phisical media to play. Still, menus are lacking, and intro, if any, must be added at the beginning (and/or end) of the file, meaning much work, and "ethical" issues.
MKV "seems" ready to support menus, but when?
Then, I thought to a possible alternative. A simple HTML5 player!
Crazy idea? Maybe, that's why I'm posting it here, to have your opinions. HTML5 players are used by everyone, on YouTube, Vimeo, DailyMotion and so on. Yet, they are very limited in comparison to any software player. But this could work in our favour, somehow... frankly, when I want to watch a video clip on my PC, all I want to do (eventually) is to choose my language and/or subtitle tracks, and you?
We could release a project in a single folder, with one HTML file that will start the player, and one MVK (or other) video file containing the main feature. Well, almost useless, someone could point out, what is the difference instead of playing the file directly? Well, if there is more than one file - for example, bonus material, or an entire bonus project, having an HTML file with simple menu pointing to those files could be handy (and with a nice looking).
I've seen some free HTML5 video players that allow to add custom made buttons; why don't add one for the trailer? One for chapters, one for audio and subs selection? A bit like DVD/BD menus, but made in HTML/CSS; great appearance, and small footprint, can be read by any OS, also mobile - even if I don't think someone would normally watch an entire 1080p movies on a cellphone...
Another great option could be to add soft matte to an open matte release, avoiding two releases (and double work/time to upload/time to download/HDD space etc.)
Seamless branching "could" work, too... maybe it's possible to have HTML buttons in the menu for the theatrical and extended version, where for example TC calls file1+file2+file3, while EE calls file1+file4+file2+file5+file3... got the point? More investigation is needed, to understand if this is possible and the join are indeed seamless.
Now, codec support: video AVC for sure, also WebM and Theora; audio AAC, vorbis, opus, FLAC, mp3, WAV; containers WebM, Ogg, MP4; I'm pretty sure there is a way to support MKV container, and audio AC3 as well. What's about DTS? Of course, it's still possible to convert audio to a supported format.
What is the output quality of a video clip played in an HTML5 player (possibly without using Flash)? I mean, visually I have the same quality of a software player? And audio wise?
It will be great to have a standardized player, where each of us could put his logo, and other custom... "things", but still having a look'n'feel familiar with other releases...
Still another crazy, and useless, idea, or can have some potential?