Remi,


I am using Windows 7 x64, so that is another variable from your test.  I think as you mention there must be some interaction with new command line parser and maybe windows 7.

Since I got it to work I haven't played around with it too much more to see if I can isolate it further.

Stephan,

The issue is not with a long path name in the -d %i1.   (And by the way, this issue still occurs when I replace the batch parameter "%1" with a hardcoded path). And the path itself is very short anyway.

Plus, I think that  that Siren 'receives' the right directory, because it loads that directory as it executes the command line, and shows the preview of the rename operation. But it just sits idle and doesn't rename or quit. So I think this means that all commands (other than /r /q) were received/processed by siren.

Remi,

Thanks for your fast response, and for making the changes to History. I think this will be helpful to others who are porting to 3.0.

Under windows, the standard option prefix is "/" (not "\"). It is the only one authorized by Siren 2.
As Siren3 is multiplatform you can use "-" or "/".
I did not specify this in the Help but you can see it in the command line usage : siren /h

Sorry, I had a typo on the "\". Initially I thought that the slash was the problem in my statements, but in reality it was the capital versus lower case. So this is cleared up for me.  However, on a command line "siren /h" does not list "-" as an option delimiter. For example,  for rename, it lists  "/r", and "--rename", but does not list "-r".

As for the option order issue:

I've just made some tests and did not see any problem.
Can you post an example ?

Actually, I did some more tests from straight command line and they seemed to work. However, I am calling from inside a batch file and see the issue.

I have two batch  files.  Batch File 1 (Batch1) runs and does a CALL to Batch File 2 (Batch2), and passes a directory in the first batch parameter.  Batch2 contains a siren rename command line.  The CALL command from the first batch file works in a similar fashion to Start /Wait. Batch 1 will wait for Batch 2 to complete for continuing.

Batch2 has a command line like this:

"C:\Program Files (x86)\Siren\Siren.exe" -e %%Xddd-%%Xfs-00MAS-%%N1.%%e -s img_*.jpg -d %1 -f *.* -r -q

This worked in Siren 2.0 (with capitals for options).  With Siren 3, Siren window loaded and stayed open. The "new filename" showed the future name for the files, but the rename action didn't take place, and Siren didn't quit.  After some testing, I c moved the -r and -q to the beginning of the option string, like this:

"C:\Program Files (x86)\Siren\Siren.exe" -r -q -e %%Xddd-%%Xfs-00MAS-%%N1.%%e -s img_*.jpg -d %1 -f *.*

And after making this change, Siren renamed the files and quit. Maybe there is something more complicated going on because of the batch file calls.  I think I also tried using "Start /wait" method, with the same results.

I will have to do some more testing, but the batch files are at least running again.

I'm a long time Siren user on Windows.  I was happy to see the new version 3.0 with support for additional file types, like .3gp and .mp4.

However, it took some time to port my scripts and batch files from Siren 2.01 to Siren 3.0.  Some change items didn't seem to be listed in the history, especially for command line. So it may be helpful to add these to the history of changes for others looking to port from Siren 2.0(1).

Some of the items that I found:

Command line argument deliminator changes from "\" to "-" or "--" for long form.

Command line options are case sensitive, and many changes case from UPPER to LOWER in 3.0. For example,  "\E" worked in 2.01, but is not recognized in 3.0, replaced with "-e", also true for /R, /Q, etc.

/I option (specifying INI file) is gone.  Seemingly, so is INI file support. Where do settings go now, registry?

Command line arguments seem to be order sensitive in a way that they were not in 2.0.    Specifically, the "-r" "-q" options did not seem to work when placed at end of options, but they do work when placed at the beginning of options list. When at the end, the rename and quit functions did not work, i.e  "Siren.exe -e blah -f blah -d blah -r -q" did not work, but "Siren.exe -r -q -e blah -f blah -d blah"