home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Software
Tools and other software
Media-Buddy - the MKV Buddy successor.
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Lehmden" data-source="post: 1290717" data-attributes="member: 109222"><p>Hi.</p><p>I also use h265 for all my videos. No real alternative at the moment, imho...</p><p></p><p>In early days, Media-Buddy uses HandbrakeCLI as recoding engine. Sadly Handbrake often removes 1 or 2 pixel from the sides of the video, leading to weird video dimensions like 1916 x 1078 instead of 1920 x 1080 or similar. And the folks on Handbrake needed much more time to implement H265_QSV support... </p><p></p><p>Aside this the under laying engine (FFMpeg) in Handbrake is exactly the same as in today's Media-Buddy. But Media-Buddy always should keep the exact file dimensions and I always use QuickSync for transcoding video streams. That some of of the reasons why I replaced Handbrake in Media-Buddy with "original" FFMpeg long time ago. FFMpeg has much more complex settings and command line options but it's much more flexible as you can transcode pure audio files too, and you even can generate video stills as used in the custom cover and fanart, Media-Buddy generates. Without the change from HandbrakeCLI to FFMpeg many of the features of Media-Buddy were not possible (e.g. the automatic creation of an episodes thumbnail if it is missing online).</p><p></p><p>Aside this I never copy the audio tracks as I really hate the massive volume differences between way too many video files. All my videos are normalized (another thing FFMpeg can achieve) so all my "finished" videos have the same volume when playing, wonderful. No more quiet videos where you need to raise the volume to the ceiling, just to be able to understand the dialogues. Then the next video is so loud, it blows the glass out of your windows and make your ears bleed... </p><p></p><p>Most often I try to keep the original audio codec as long as it is not too "exotic" but normalize is not possible with stream copy so I need to recode the audio track(s) always, even if I can copy the video stream as it already is h265. But transcoding audio only takes some seconds, so this is no big deal...</p><p></p><p>Even if you use the same settings it is not 100% guaranteed that the resulting videos are "compatible enough" to be joined with MKVMerge. Mostly they are, but "sh...t happens". Especially if you stream-copy the audio streams. Aside this, if you need to recode and after that join the video anyway with different software, why not doing this in one step with e.G. OpenShot. There you also can eliminate the audio gap and even opening and closing titles if the videos are two parts of a splitted episode?</p></blockquote><p></p>
[QUOTE="Lehmden, post: 1290717, member: 109222"] Hi. I also use h265 for all my videos. No real alternative at the moment, imho... In early days, Media-Buddy uses HandbrakeCLI as recoding engine. Sadly Handbrake often removes 1 or 2 pixel from the sides of the video, leading to weird video dimensions like 1916 x 1078 instead of 1920 x 1080 or similar. And the folks on Handbrake needed much more time to implement H265_QSV support... Aside this the under laying engine (FFMpeg) in Handbrake is exactly the same as in today's Media-Buddy. But Media-Buddy always should keep the exact file dimensions and I always use QuickSync for transcoding video streams. That some of of the reasons why I replaced Handbrake in Media-Buddy with "original" FFMpeg long time ago. FFMpeg has much more complex settings and command line options but it's much more flexible as you can transcode pure audio files too, and you even can generate video stills as used in the custom cover and fanart, Media-Buddy generates. Without the change from HandbrakeCLI to FFMpeg many of the features of Media-Buddy were not possible (e.g. the automatic creation of an episodes thumbnail if it is missing online). Aside this I never copy the audio tracks as I really hate the massive volume differences between way too many video files. All my videos are normalized (another thing FFMpeg can achieve) so all my "finished" videos have the same volume when playing, wonderful. No more quiet videos where you need to raise the volume to the ceiling, just to be able to understand the dialogues. Then the next video is so loud, it blows the glass out of your windows and make your ears bleed... Most often I try to keep the original audio codec as long as it is not too "exotic" but normalize is not possible with stream copy so I need to recode the audio track(s) always, even if I can copy the video stream as it already is h265. But transcoding audio only takes some seconds, so this is no big deal... Even if you use the same settings it is not 100% guaranteed that the resulting videos are "compatible enough" to be joined with MKVMerge. Mostly they are, but "sh...t happens". Especially if you stream-copy the audio streams. Aside this, if you need to recode and after that join the video anyway with different software, why not doing this in one step with e.G. OpenShot. There you also can eliminate the audio gap and even opening and closing titles if the videos are two parts of a splitted episode? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Software
Tools and other software
Media-Buddy - the MKV Buddy successor.
Contact us
RSS
Top
Bottom