So if something is to be disabled, the associated widget should be visible and near the widget that is causing it to be disabled so the user can see the my intention isn't to add an option or checkbox for everything under the sun (well, at least everything ffmpeg supports, which is just about literally everything under the sun! 😆 ) - I'm only asking about adding a passthrough video option. It's best if there is no hidden disabling of features.
It's very difficult to show in a clear way why features are being disabled when some other feature has been enabled.
You can't assume that a user will know that video passthru means they can't deinterlace.ĭisabling features is especially problematic for the GUI. There are a surprising number of people out there that do not understand the difference between transcoding and remuxing. it needs to be very clear to the user that they may have A/V sync issues they wouldn't see when re-encoding and that no video filtering is possible. Also the GUI would have to be reworked to make it clear what all is getting disabled. Primarily I'm talking about the A/V sync correction and other filters here. If we enabled video passthru, we would have to disable several things that HandBrake currently does during encoding. It is a matter of project scope and focus.
Handbrake audio passthrough crack#
Totally cool if nobody on the team is interested in implementing this, but are you opposed to someone else taking a crack at it? I'm not sure I'll have the time soon but I'm definitely interested in helping however I can. I usually just end up using ffmpeg for that, but have to sometimes scour the internet to find the right incantation of command line flags to get what I need done. There are plenty of cases where I know the input video is already in a compatible format for the hardware I want to play it on, but still need to transcode the audio and/or subtitles. But does that mean it won't be considered at all? Offering a passthrough video option would make HandBrake an even more powerful video conversion tool. Apologies for not using the issue template here but it didn't seem appropriate given the style of request.īefore you immediately close this issue as duplicate, please hear me out 😅īased on the previously mentioned issues, it sounds like there are architecture issues in the way of supporting something like this.
0 kommentar(er)
