Good day,
Preamble
The following text may appear to be rather long-winded, and even maybe to some, pointless. But, there is a meaning-to-my-madness! So, I ask that you please be patient with me. All will soon be revealed!
The HelpFiles
In the SAC\SAW HelpFile, the following information is provided:
* Disclaimer! I have modified the SAW text - in order to coincide with SAC the text. Please understand, that modifying the SAW text, in no way, alters the outcome of the existing, or, this present text!
"Starting SAC
Startup Command Line Options
SAC accepts an .mxs filename on the command line when starting up. This will run the program and automatically load the Mix Session file.
Example: C:\SAC\SAC.exe D:\Mix-Sessions\Test\Test.mxs"
"Starting SAWStudio
Startup Command Line Options
SAWStudio accepts an .edl filename on the command line when starting up. This will run the program and open into the MultiTrack View.
Example: C:\SAWStudio\SAWStudio.exe D:\Audio\Test\Test.edl"
About File Associations
File associations have been with us for some time, however, at least to me anyhow, file associations really came to prominence with the introduction of Windows 95. The employment of file associations altered the way in which we could employ computers - from what I refer to as "application-centric" to "document-centric" - or more simply, "app-centric versus docu-centric"...with the latter being the preferred methodology. Regardless however, of what these latter two terms are referring to, the sole purpose of this text is to simply introduce these two terms - not to focus on them! We move on...
Startup Command Line Options
To honour Bob's methodology of the employment of "Startup Command Line Options", I have devised a means of being able to launch SAC or SAW by simply providing the means of selecting a Session data file. This means is identical in principle to selecting "File, Open Mix Session" in SAC, or "File, Open Session" in SAW - all without the need to have to launch the applications first!
The Script
The primary difference in the deployment of this script, is that neither SAC nor SAW require being launched first - as just noted. The script appears only to be selecting a Session file, when in reality - the very same Startup Command Line Options are being deployed. Following, is a sampling of the "LaunchEdl()" function portion of the script:
; -----------------------------------------------
Func _LaunchEdl($sFileOpenDialog)
Local $_sSrcPath1 = "C:\SAWStudio64\SAWStudio64.exe "
Local $_sSrcPath2 = $_sSrcPath1 & $sFileOpenDialog
; -----------------
Run($_sSrcPath2)
; -----------------
MouseMove(340, 226, 0)
Sleep(2000)
EndFunc ;==>_LaunchEdl
; -----------------------------------------------
The variable "$_sSrcPath2" is simply combining the results of the "$_sSrcPath1" and the "$sFileOpenDialog" variables, in order to maintain the "C:\SAWStudio\SAWStudio.exe D:\Audio\Test\Test.edl" example from the HelpFiles.
* $_sSrcPath1 = C:\SAWStudio\SAWStudio.exe and $sFileOpenDialog = D:\Audio\Test\Test.edl.
An Important Note
The only "potential" downside to this script - indeed, if this point may be considered as a downside at all, is that the path to application is "fixed" - even though that so-called fixed path IS being assigned to a variable! However, Bob's Startup Command Line Options employ such fixed paths as well!
* For example, in my particular situation, the paths to SAC|SAW are "C:\RML\SAC\SAC64.exe" and "C:\RML\SAW\SAWStudio64.exe", whilst the "default" paths for SAC|SAW are "C:\SAC64\SAC64.exe" and "C:\SAWStudio64\SAWStudio64.exe" accordingly.
About Launch TTA [toggleTaskbarAutohide.exe]
All of my scripts employ " toggleTaskbarAutohide.exe" ***8211; TTA for short, which simply "hides the Task bar" if not yet hidden, or "restores the Task bar" if the Task bar was previously hidden.
* Note: TTA is only 22KB's in size, and only requires being copied to the [C:\Windows] folder. I will provide the TTA executable ***8211; along with the exit scripts for SAC and SAW as well for those that are interested.
In closing...
If anyone is at all interested in these scripts - one for SAC and one for SAW, then please, let me know. All that I require is the path to SAC or SAW that you are currently employing. I can also assign a default path to the location of where you store your Session files - if this would be of any interest to you?
I hope that some will find this information to be of some practicable use?
Thank you for your time....appreciated!
PS: Please see the following posting...
Startup Command Line Options
Moderator: Bob L
Re: Startup Command Line Options
Good day,
If anyone is interested in these scripts, please let me know the following in an email [Please do not PM me...]:
Notes
1) If you ARE NOT going to employ TTA, then you do not require the "exit scripts".
* However, if you ARE going to employ TTA, then you will require the "exit scripts".
2) Please include the full path to the data...for example:
a) For SAC
* Application: C:\SAC\SAC.exe
* Data: D:\Mix-Sessions
b) For SAW
* Application: C:\SAWStudio\SAWStudio.exe
* Data: D:\Mix-Sessions
Mouse Positioning
I prefer to have the mouse positioned in a specific location upon launch of the given application. For SAC, the mouse is positioned over the [LIVE] button. For SAW, the mouse is positioned near the beginning of the MultiTrack in I-01. I can also simply position the mouse in the centre of the display for bot applications. All that I would require is the following:
1) The screen resolution, for example 1929 x 1080
2) Text size: Small - 100% (default), Medium - 125%, or Larger - 150%
Q and A
Q1: Are you going to employ TTA [toggleTaskbarAutohide.exe]?
R1: [Yes | No]
Q2: Do you want both the SAC and the SAW scripts?
R2: [Yes | No]
Q3: What is the full path to SAC?
R3:
Q4: What is the full path to SAW?
R4:
Q5: What is the full path to your audio files?
R5:
Q6a: Do you want to employ "mouse positioning"?
R6a: [Yes | No]
Q6b: If so, where would you like the mouse positioned?
R6b:
The Zip file
Depending on what is selected above - for this example, we will "assume" that all of the above are being requested, the contents of the Zip file would be as follows:
toggleTaskbarAutohide.exe
LaunchSAC.exe
ExitSAC.exe
LaunchSAW.exe
ExitSAW.exe
Deployment
My suggestions for deploying these scripts are:
1) Create a folder in the root of Drive C, entitled, "RML_Scripts"
2) Copy the Zip to the "RML_Scripts" folder and extract the contents of the Zip file.
3) Move the toggleTaskbarAutohide.exe to the C:\Windows folder
4) Create "administrative" shortcuts for each of the "Launch" and "Exit" scripts.
5) Place these links in an accessible location.
6) Done
Again, I thank you for your time....appreciated!
If anyone is interested in these scripts, please let me know the following in an email [Please do not PM me...]:
Notes
1) If you ARE NOT going to employ TTA, then you do not require the "exit scripts".
* However, if you ARE going to employ TTA, then you will require the "exit scripts".
2) Please include the full path to the data...for example:
a) For SAC
* Application: C:\SAC\SAC.exe
* Data: D:\Mix-Sessions
b) For SAW
* Application: C:\SAWStudio\SAWStudio.exe
* Data: D:\Mix-Sessions
Mouse Positioning
I prefer to have the mouse positioned in a specific location upon launch of the given application. For SAC, the mouse is positioned over the [LIVE] button. For SAW, the mouse is positioned near the beginning of the MultiTrack in I-01. I can also simply position the mouse in the centre of the display for bot applications. All that I would require is the following:
1) The screen resolution, for example 1929 x 1080
2) Text size: Small - 100% (default), Medium - 125%, or Larger - 150%
Q and A
Q1: Are you going to employ TTA [toggleTaskbarAutohide.exe]?
R1: [Yes | No]
Q2: Do you want both the SAC and the SAW scripts?
R2: [Yes | No]
Q3: What is the full path to SAC?
R3:
Q4: What is the full path to SAW?
R4:
Q5: What is the full path to your audio files?
R5:
Q6a: Do you want to employ "mouse positioning"?
R6a: [Yes | No]
Q6b: If so, where would you like the mouse positioned?
R6b:
The Zip file
Depending on what is selected above - for this example, we will "assume" that all of the above are being requested, the contents of the Zip file would be as follows:
toggleTaskbarAutohide.exe
LaunchSAC.exe
ExitSAC.exe
LaunchSAW.exe
ExitSAW.exe
Deployment
My suggestions for deploying these scripts are:
1) Create a folder in the root of Drive C, entitled, "RML_Scripts"
2) Copy the Zip to the "RML_Scripts" folder and extract the contents of the Zip file.
3) Move the toggleTaskbarAutohide.exe to the C:\Windows folder
4) Create "administrative" shortcuts for each of the "Launch" and "Exit" scripts.
5) Place these links in an accessible location.
6) Done
Again, I thank you for your time....appreciated!