Non-simultaneous execution of command script?

[Valery_Kondakoff]

Hi!

Let's imagine I have 100 mp3-files, and I want to decode them back to wavs. This can be done with the following command line

Code: Select all

lame.exe --decode in_filename out_filename

I'm creating the Command Script:

Code: Select all

lame.exe --decode "$N" "$I\$B.wav"

and execute it. The result: 100 simultaneous console windows and really overloaded PC.

I was sure the commands are executed not simultaneous, but one after one. Yes, I know, I can modify the Command Script like this:

Code: Select all

start /w d:\tools\lame\lame.exe --decode "$N" "$I\$B.wav"

but this causes the following problem: it is impossible to launch such a script as a shell and there is an open command prompt window after the script execution.

Let me suggest to add an additiona checkbox to the Script Wizard dialog window: 'Simultaneous'. When this box is checked, the commands are executed simultaneously, when unchecked (default) the commands are executed one after one.

What do you think about this?

[nikos]

why don't you use x2's console?

[MegaZapFan]

Hi!

Let's imagine I have 100 mp3-files, and I want to decode them back to wavs....

This is audio blasphemy!  :twisted:

As MP3 is a lossy compression algorithm, each time you convert an .MP3 file back to .WAV you are losing information.  Convert it back to .MP3 again, and now your second .MP3 is lossier than the first.

Audiophiles will attest, MP3 files are evil  Stick with lossless formats such as SHN (Shorten), APE (Monkey's Audio), FLAC (Free Lossless Audio Codec), etc.

You can learn about lossless audio here:  http://www.etree.org

.MP3 files are fine for your personal use, especially when fidelity is of lesser importance, like when mowing the lawn, etc., but for general listening on your computer, once you start using lossless formats, you'll never go back to .MP3.  Further, .MP3 files degrade and dillute the community when trading music (legal implications aside, there are plenty of places to go for legally traded music).  Lossless formats do not dillute the community.

/rant  

[Valery_Kondakoff]

why don't you use x2's console?

Ah! This is important point. I wanted to use it and I tryed to, but there are some negative issues: currently I'm not using x2's console just because it has no visual indicator that the lengthy process is finished. In the 'original' console a 'blinking' input promt is acting as such an indicator. I can't find a way to determine if the process is finished or not in x2's console. This is very annoying.

An additional inconvenience: x2's console just does not print the current working dir in window title or on the command prompt when you are using the 'cd' command. For example, I'm opening the console in d:\tools\wget folder and applying the 'cd ..' command. The window title still prints 'd:\tools\wget'. And nothing useful is printed in the working artea. This really confuses me: I'm forced to apply additional 'cd' just to print the current working dir...

[Valery_Kondakoff]

This is audio blasphemy!

Yes, you are right! Let's redefine the example: 'I have 100 wav-files and I want to convert them to mp3s...'

[MegaZapFan]

Excellent!

[nikos]

For example, I'm opening the console in d:\tools\wget folder and applying the 'cd ..' command. The window title still prints 'd:\tools\wget'

the console's title shows the folder of the main x2 window
whenever you change folders in the main, the console follows

there's no way to tell when a console is busy or not other than executing another command (e.g. dir)