11.05.2025, 09:04
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
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.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.