blueoris
2016-09-28 06:09:08 UTC
I am not an Audacity developer so please bear with me...
I am trying to get the pipe-test.pl script to work in Windows. This is what
I have done:
1. Built Audacity, with mod-script-pipe project;
2. mod-script-pipe.dll copied to <audacity-src>\win\Release\Modules\;
3. Start Audacity.exe from <audacity-src>\win\Release\;
4. Go to Edit -> Preferences -> Modules and select "Enabled" from the
drop-down next to mod-script-pipe;
5. Close Audacity;
6. Re-open Audacity (all good, no errors / exceptions, I assume
mod-script-pipe.dll was loaded)
7. Install ActiveState perl
7. Open command line, execute "perl pipe-text.pl >> output.txt".
pipe-text.pl script is located on <audacity-src>\scripts\
8. The script prints [Mode: Select=All] to the command line session and
stays there forever.
9. Close Audacity and the script continues and finishes, printing a lot of
information.
Findings:
1. The execution of pipe-test.pl gets into a endless loop at line 105 (while
($resp = <FROM_SRV>) {)
2. The only way for the script to continue is by closing Audacity;
3. If I don't close Audacity and kill and re-start script, I get an error in
line 46
4. The pipe-test.pl output (stored in the output.txt file) includes a lot of
information re. executed commands. The recorded times for each command are
suspiciously short.
Does this mean that the perl script is creating the pipes but, Audacity is
not listening to them?
How can get more debugging information?
Thanks in advance.
--
View this message in context: http://audacity.238276.n2.nabble.com/Audacity-scripting-issues-running-pipe-test-pl-tp7576201.html
Sent from the audacity-devel mailing list archive at Nabble.com.
------------------------------------------------------------------------------
I am trying to get the pipe-test.pl script to work in Windows. This is what
I have done:
1. Built Audacity, with mod-script-pipe project;
2. mod-script-pipe.dll copied to <audacity-src>\win\Release\Modules\;
3. Start Audacity.exe from <audacity-src>\win\Release\;
4. Go to Edit -> Preferences -> Modules and select "Enabled" from the
drop-down next to mod-script-pipe;
5. Close Audacity;
6. Re-open Audacity (all good, no errors / exceptions, I assume
mod-script-pipe.dll was loaded)
7. Install ActiveState perl
7. Open command line, execute "perl pipe-text.pl >> output.txt".
pipe-text.pl script is located on <audacity-src>\scripts\
8. The script prints [Mode: Select=All] to the command line session and
stays there forever.
9. Close Audacity and the script continues and finishes, printing a lot of
information.
Findings:
1. The execution of pipe-test.pl gets into a endless loop at line 105 (while
($resp = <FROM_SRV>) {)
2. The only way for the script to continue is by closing Audacity;
3. If I don't close Audacity and kill and re-start script, I get an error in
line 46
4. The pipe-test.pl output (stored in the output.txt file) includes a lot of
information re. executed commands. The recorded times for each command are
suspiciously short.
Does this mean that the perl script is creating the pipes but, Audacity is
not listening to them?
How can get more debugging information?
Thanks in advance.
--
View this message in context: http://audacity.238276.n2.nabble.com/Audacity-scripting-issues-running-pipe-test-pl-tp7576201.html
Sent from the audacity-devel mailing list archive at Nabble.com.
------------------------------------------------------------------------------