Bug on load command?

Software Siril
1

Hello!

It seems that there’s a bug in load command in script.
When I use it from in the GUI’s command line, in right panel, no worries.
But when I ran it from a script as:

requires 1.2.0
load any.ser
close
load any.ser
close

The second load makes the program crash:

[…]
log: Timestamps in the SER file are correctly ordered.
log: ========================================
log: Sequence loaded: any (0->138392)
log: Opening any.ser failed.
log: Error in line 2 (‘load’): generic error.
[…]

Do you have any idea?

2

the load command is designed for images, not sequences. Sequences are loaded by commands that work on sequences, their first argument is the sequence name.
It’s still not supposed to crash… Thanks

3

the load command is designed for images, not sequences.

Oh, i loaded a .SER file, indeed. Not directly the sequence. But the first load on SER did work, and read the related sequence (eg. selected & unselected frames were OK).

So it seems that load can be applied to SER and uses sequence information (?)

Sequences are loaded by commands that work on sequences, their first argument is the sequence name.

I noticed that; but I use the “.” shortcut to apply sequence commands on loaded sequence.

You’d advice to not use this feature and avoid to load sequence to work on, and instead specifying it on each single command?

Do you think the load on SER can be fixed?

4

As far as I can remember, and as Vincent said, the load command was mainly designed for single images.
SER films are not intended to be processed by command lines. This is why the debayer is not in the load command. SER files are in fact just sequences.

5

I understand. But what seems weird to me is that the first load of SER is working, but not the next ones.

6

I’ll try with the said commands, by specifying the sequence each time, without loading it.

7

FYI using seq dedicated commands works fine. Thanks again!