adm 040916 and before (15 days ~)
1 Save a job with a cutting.
2 Run the job.
The cuttings dont appear correctly.
Although A: and B: have the good cutting values when you clic on,
cursors and blue rectangle are not at the good place any more.
This seems to be partially fixed by [cli] update markerA & B after running script (https://github.com/mean00/avidemux2/commit/ade3d417e535d33849a60dff3b7f68a4379c0c62): the GUI reflects now the correct values for markers A and B if the script is loaded via Recent --> Recent Projects, but not if the same script file is loaded via File --> Project Script --> Run Project...
In any case the markers get saved and later loaded correctly and can be navigated with PgUp and PgDown.
Nothing better in avidemux_r060916_win64Qt5 (last try).
> Make cuttings + a crop (to have a blue rectangle in scrolling bar) in a video (TS ie), then save the job.
Run the job : no blue rectangle in the scrolling bar, first thing to notice.
Clic on A: or B: the saved cropping points are there (see time).
But its a mess in blue rectangle and cursors positions in the scrolling bar.
And even most of time : no cursor (!) in the scrolling bar.
Quote from: twinsun on September 09, 2016, 02:19:15 PM
Run the job
From where? The "Recent" --> "Recent Projects" path is fixed. The issue still exists via "File" --> "Project Script" --> "Run Project..." as stated above (http://avidemux.org/smif/index.php/topic,17110.msg76774.html#msg76774).
'Recent Projects' is not usable for me, it has too few files in the list.
I need to use Project Script / Run Project.
> See why :
Jobs list I create (Queue) has several tens of jobs when I run avidemux_jobs.exe.
Sometime (rarely) a job fail, so I need to retrieve the according job.py project to see why.
If I can't run it I would have to redo a new edition missing the reason of the fail.
I 'Save As Project' each edit, before I 'Queue job to joblist' this edit.
So every job in Job List as its own job.py ready to be reused just in case the job fail.
Anyway, for now I use adm030516, OK for that, and long since.
Fixed by [UI] Resync markers after each call to script engine (https://github.com/mean00/avidemux2/commit/e678f57f95878c73240d2c7081cf81a667b86026), merci mille fois!
It turns out to be there is one scenario still not covered by the last commit: if there was a crash and Avidemux loads the crash file, the GUI doesn't show (correctly loaded) markers.
Should be covered by [UI] Check marker after loading crash file also (https://github.com/mean00/avidemux2/commit/2b2dafc224718c508ccfb67c9f11856cf178e82e) (my favourite crasher has gone, but I really assume this is fixed), thanks!