docker-handbrake
docker-handbrake copied to clipboard
Simultaneous encodes
Feature Request!
CPU with lots of cores are becoming much more common.
I am only using 30% of my Ryzen processor when encoding to H265
Looking for the option of choosing simultaneous encodes rather than installing multiple docker instances each pointing to different watch folder.
This is similar to #158
I too am looking for simultaneous encodes. I know the Handbrake application supports this, so I am not sure where the limitation lies. On a 6-core Ryzen CPU, the first pass for x264 1080p is always under 50% utilization and the second pass usually sits around 90%. I was previously doing encode work on a Windows machine running 2-3 encodes simultaneously (though not with Handbrake) to achieve 98-100% usage at all times. I'd love to see that capability with this Docker container.
Having the same need as OP. Both the windows version of Handbrake and Vidcoder ( another GUI version of handbrake ) have this option to run multiple encodes simultaneously. Having many handbrake docker instances is not difficult to set up only once but annoying when changing to a different workflow with a different profile.
For those wanting this feature, you are asking in the wrong place. It has not been implemented in the linux version of handbrake yet. Check this out: https://github.com/HandBrake/HandBrake/issues/1445. Once the Handbrake team gets it implemented, I'm sure it will show up in the docker image
for the meantime, why not just start two docker containers of handbrake?? given upstream has not implemented it for more than 4years+ Isn't this what docker is for, orchestrating multiple instances of containers?
What would be a valid issue is if two instances of handbrake can't run at the same time..
for the meantime, why not just start two docker containers of handbrake??
I have a 16-core processor now and do run multiple instances, up to 4 in fact. I don't like having to update and maintain 4 different instances. It is tedious to do things such as making changes to each instance one at a time or copying custom profiles and preferences from one instance to the other 3. It's all a minor inconvenience really.
I have other small complaints, but none of them are related to this particular issue.