I’ll have to open a thread on this for additional functionality.
In “Handbrake speak” most people are used to hearing; if we could set the h.264 profile (eg high); level (eg 4.0) and crf setting (eg 20) that would be awesome. I doubt this would be hard to implement as it’s just allowing a user to set the configs and then use those config settings when setting up the transcode parameters. More or less the same thing I do with ffmpeg.
The profile level really isn’t that important as long as Plex chooses a good one to start with. Really it’s just the profile type and crf that would be ideal to be able to configure.
This would then allow us to create version of the files that are far better then what could be achieved in real-time and also a lot smaller. Everyone could then adjust the Optimize to their needs and trade speed for quality/lower storage as needed.
Don’t know how many people have checked but I notice many of the converted files are a lot bigger then the original file.
Yeah, having settable parameters would be awesome. Maybe they will come in an update. I don’t think the profile level does anything to quality, but the crf and x264 preset would have dramatic impacts on quality.
Don’t know how many people have checked but I notice many of the converted files are a lot bigger then the original file.
Do your original files possibly have high ref frames? I’ve seen Plex use very low values which would make the files larger. Also the x264 preset will have an impact on filesize as well. Plex using Very Fast is not the best option if you have the CPU power to go faster.
Concerning the profile level, ref frames and things of this nature. I do not think these should be configurable at all. These don’t affect the end result of quality much (if at all) but are there for compatibility to the many devices. It’s really just the x264 preset and “crf” setting I believe. I’m going to to a quick look through my code/scripts to see if there is anything else.
Ideally for Optimize if the Job Setup/edit allowed you to pick the profile (ultrafast, superfast, veryfast, faster, fast, medium, slow, slower, veryslow) from a drop down and ALSO allow you to set the CRF or Constant Rate Factor from a drop down with sane values such as 18 to 28 as choices then this is all that should be needed.
The above would easily allow the command line options such as “-preset slow -crf 20” to be handed off to the transcoder to get the results needed.
We would then have some real freedom in setting up our jobs to meet our individual needs.
Carlo when or how long till you release betas of your distributed transcoder software i have multiple servers and 54tb of files and im limited to naming them server 1-5 and asking friends to jump to another server if it lags which is lame
There’s a forum thread somewhere in the 3rd party section with some individuals working on something that sounds awfully close to the idea you had. Might be worth taking a look at their github project. Let me see if I can find the link.a
Hey, recently the converter stopped working for me. No idea why that would be.
Any idea?
It just opens this window and does nothing. Tested with multiple files.
I would suggest renaming your files first before processing them so that subtitles get the correct name generated. I’ve seen it get hung up previously if you don’t have good plex names for the origin files.
However, with that said, I doubt it’s the reason. Can you fire off and convert these files directly with ffmpeg or does it die also?
Has anything changed on your side? Have you recently updated to Windows 10? Did it ever run on windows 10?
Are you processing “in place” or having the results written to a common “done” or “completed” directory?
Have you checked to make sure you aren’t low or disk space?
If you want we could setup TeamViewer and I could give you a hand figuring out what’s not working. Just send me a PM if you like.
what do i need to change in order to get it to pick up FRA and FRE as French