"Run the Command"

[mrmisi]

Dear All,

I've written a script (actually 2, one for camera) to record the audio through the microphone using the windows tool (sound recorder).

The script is working, in fact, if I double click on it or run it on the command promt the record start; but, if I insert the file path (in 8.3 format) on the line "Run the command"(on your software) and click "test" the record doesn't start (it appear a cmd windows for a second but doesn't show any error message).

I attach one of the two script (the difference is the name of the directory which to save the record):

for /f "delims=" %%a in ('wmic OS Get localdatetime ^| find "."') do set dt=%%a

set datestamp=%dt:~0,8%
set timestamp=%dt:~8,6%
set YYYY=%dt:~0,4%
set MM=%dt:~4,2%
set DD=%dt:~6,2%
set HH=%dt:~8,2%
set Min=%dt:~10,2%
set Sec=%dt:~12,2%

set stamp=%DD%-%MM%-%YYYY% %HH%.%Min%.%Sec%
echo stamp: "%stamp%"
echo datestamp: "%datestamp%"
echo timestamp: "%timestamp%"

Start %SystemRoot%\system32\SoundRecorder.exe /File H:\Archivio\Sorveglianza\Audio\Soggiorno\%stamp%.wma /duration 0000:02:00

Thank you and best regards,
Matteo.

[ryan]

Hi mrmisi,

I don't have a windows machine to test this on at the moment, but you may try removing the "echo" statements. In the current implementation, to prevent broken or never ending commands from holding open file descriptors, stdin/stdout/stderr are closed so programs which require these may fail. I'm not sure if echo on windows errors or is silent if stdout is closed.

[mrmisi]

Hy Ryan,

I removed all the command line with "echo" (which really is not needed on), but the problem still exists.

If I open it normally works, if it is opened through your software does not work (I get a window for a moment but nothing happens).

In the line "Run the command" I just put the path in 8.3 format or even something like "Run" or "Start"?

Now the script is as follows:

for /f "delims=" %%a in ('wmic OS Get localdatetime ^| find "."') do set dt=%%a

set datestamp=%dt:~0,8%
set timestamp=%dt:~8,6%
set YYYY=%dt:~0,4%
set MM=%dt:~4,2%
set DD=%dt:~6,2%
set HH=%dt:~8,2%
set Min=%dt:~10,2%
set Sec=%dt:~12,2%

set stamp=%DD%-%MM%-%YYYY% %HH%.%Min%.%Sec%


Start %SystemRoot%\system32\SoundRecorder.exe /File H:\Archivio\Sorveglianza\Audio\Soggiorno\%stamp%.wma /duration 0000:02:00

[ryan]

Hi mrmsi,

I spent some time examining this and there appear to be a few issues, the primary being that Sound Recorder requires a 64 bit console to be created to execute. I was able to make this happen by wrapping your script in the following python script

import os
os.system(r'start C:\path\to\response.bat')

And configuring the response as

python.exe C:\\path\\to\\script.py

But this approach still has the problems that the command window remains after the batch file is executed, your wmic call is not available, and I had to make a copy of the sound recorder application to a different location as windows can obfuscate access to the system directories.

We'll look into adding more configuration options around the "run command" response in the future, but I don't have an access method for your particular script at this time.

[mrmisi]

Ok, thank you Ryan.

We hope in the future; however, just for knowledge,I've try to write another script with the only command to open the other script, like:

Start C:\...path...\script.cmd

and the problem is the same.
So, it look like that the problem isn't inside the script.

Now, I try to solve the problem creating an automatism to run the script with the e-mail notification and another software.

I've problem also on app remotation, but i will open a new topic different from this.
I hope that this new version that you've spoken about will be released soon.

Thx again.

[mrmisi]

Ok, I want only to inform, if this could help in the future, that I've solved the problem converting the batch file with a .bat to .exe converter.

Now it work.

Thanks for the helps.