Posts: 10
Threads: 5
Joined: May 2025
I would like to request the ability to import encoding and filter settings from a job. Often I encode a video multiple times with different parameter settings, and only after viewing the videos can I determine which was the best. Once determined, I would like to load that particular job into Hybrid and use those parameter settings for encoding future videos of the same type. For example, the videos may be part of a episodic series where each as the same encoding requirements. If I can determine the best parameter settings for episode 1, then I can re-apply those parameter settings to episodes 2, 3, 4, ... N. this feature would also be useful for cases where I want to exhume work from the past, but the encoding settings are not available because upgrading Hybrid causes the presets to be deleted. I could load a .vs file to the job queue, then import the settings from the job using the right-click menu.
Posts: 11.363
Threads: 63
Joined: May 2017
That would require jobs to include all data models (basically a complete global preset ~1.2MB atm.).
=> Not happening.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 10
Threads: 5
Joined: May 2025
the job only contains the parameters that have been set. All other parameters are asssumed to be the default value. Why can't you just load the job and override the parameters that have been set and leave all else as default?
Posts: 11.363
Threads: 63
Joined: May 2017
Since things depend on each other.
The job only contains generated calls, they do not contain the parameters that need to be configured in the gui.
It's not possible to extract the information on how to configure the gui based on these calls.
The same command line could be created by different settings in the gui.
Calls contain way less actual data.
The only quick way to do what you want would be to save basically a global profile in each job.
This would increase the size of each job by ~1MB.
So this would:
1. increase the ram usage. (since all jobs in the queue are loaded into ram)
2. increase the size of the saved jobs on the hdd.
3. increase startup and shutdown time of Hybrid, since the jobs get parsed.
=> Not going to happen.
If you want to know what calls were used to create output file XY, tell Hybrid to create a report file during the job processing.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.