Meh, I use the UI for like ten minutes and let it transcode multiple collection of seasons over the course of a weekend.
It’s a little nicer and a tad faster but it really doesn’t make a big difference unless they improve transcoding speeds/quality. Otherwise I don’t really touch it unless I buy a new box set or go to a garage sale.
If anyone’s curious I rip full quality media with make mkv and point handbrake at the folder to compress it with hevc.
You don’t have to be combative, all I was saying is the gui doesn’t make much difference to me. It worked perfectly fine before and I’m sure it’ll keep working just as well as before.
What would make a bigger difference is improvements to the backend seeing that it effects over 90% of the experience and usability of the app. I spend less time in the gui than I do renaming files in my file manager or even the make mkv app.
I’ve already said that but I guess you didn’t read past the first line. I didn’t say give up on development I said who cares about a change in graphics toolkit.
I agree with you that the gui toolkit is pretty uninteresting from the users pov, or at least mine. I do wonder if the multi-threaded transcoding pipeline changes in ffmpeg 7 will improve performance in handbrake at all. I’m not sure if Handbrake calls the ffmpeg cli or not.
It’s annoying but you can do multiple transcodes at a time on everything but Linux. It’s only annoying because the complexity of h265 means it’s highly serialized compared to older codecs.
I could easily handle multiple transcodes at a time on my 12 core processor with dvds but something like 4k blueray and sometimes hd blueray (depending on the complexity) saturates my processor. It doesn’t run transcodes in a separate process
Meh, I use the UI for like ten minutes and let it transcode multiple collection of seasons over the course of a weekend.
It’s a little nicer and a tad faster but it really doesn’t make a big difference unless they improve transcoding speeds/quality. Otherwise I don’t really touch it unless I buy a new box set or go to a garage sale.
If anyone’s curious I rip full quality media with make mkv and point handbrake at the folder to compress it with hevc.
I’m not sure what your comment is supposed to contribute. Should the developers stop developing the software? What changes do you expect?
You don’t have to be combative, all I was saying is the gui doesn’t make much difference to me. It worked perfectly fine before and I’m sure it’ll keep working just as well as before.
What would make a bigger difference is improvements to the backend seeing that it effects over 90% of the experience and usability of the app. I spend less time in the gui than I do renaming files in my file manager or even the make mkv app.
I’ve already said that but I guess you didn’t read past the first line. I didn’t say give up on development I said who cares about a change in graphics toolkit.
I agree with you that the gui toolkit is pretty uninteresting from the users pov, or at least mine. I do wonder if the multi-threaded transcoding pipeline changes in ffmpeg 7 will improve performance in handbrake at all. I’m not sure if Handbrake calls the ffmpeg cli or not.
https://www.phoronix.com/news/FFmpeg-CLI-MT-Merged
It’s annoying but you can do multiple transcodes at a time on everything but Linux. It’s only annoying because the complexity of h265 means it’s highly serialized compared to older codecs.
I could easily handle multiple transcodes at a time on my 12 core processor with dvds but something like 4k blueray and sometimes hd blueray (depending on the complexity) saturates my processor. It doesn’t run transcodes in a separate process
Did they add support in this version?