Good day,
I hope that the day finds you all very well!
I have just completed the following for your perusal: [Click_Me]
Any comments and|or suggestions would be greatly appreciated.
Thank you for your time...appreciated!
The Three Control Track Menu Options
Moderator: Bob L
Re: The Three Control Track Menu Options
That looks like it could be useful.
____
Here is another tidbit that may be handy for those of you who have a lot of control data; you can display it:
control2tempo -c input_edl_file
...or you might redirect it to a csv file:
control2tempo -c input_edl_file > output_file.csv
I forget if it prints any extraneous lines - which would have to be deleted.
(Search the forum for control2tempo to get the utility. Which reminds me I had a bug in the auto-name function which I have yet to fix.)
____
Here is another tidbit that may be handy for those of you who have a lot of control data; you can display it:
control2tempo -c input_edl_file
...or you might redirect it to a csv file:
control2tempo -c input_edl_file > output_file.csv
I forget if it prints any extraneous lines - which would have to be deleted.
(Search the forum for control2tempo to get the utility. Which reminds me I had a bug in the auto-name function which I have yet to fix.)
Re: The Three Control Track Menu Options
jmh,
Can you please tell me what "control2tempo" actually does?
Can you please tell me what "control2tempo" actually does?
Re: The Three Control Track Menu Options
For the purpose of this discussion, it dumps an edl's control entries as csv data which can be opened with a spreadsheet. This is just a trivial feature that I wrote into it for the purpose of probing an edl. Since there is no documentation, the fields may not be perfectly defined - but it does what I needed it to do.
_____
The real purpose is to generate a tempomap - particularly for songs that were recorded without a click but with natural variations by the performers. One that can be tweaked, refined and if 'home' is adjusted you can effortlessly regenerate the map. It is all described here:
http://www.sawstudiouser.com/forums/sho ... trol2tempo
There were a couple of problems I encountered, and that is that the Control2Tempo.exe is a 'compiled' auto-hot-key script does not work on all versions of windows. This was my first attempt to make an 'executable' from AHK. When I investigated I determined that I would not attempt that again, but simply say that installing auto-hot-key-2 is a prerequisite. Instead one would run the Control2Tempo.ahk script and do the slight adjustments to the script needed to run it on various versions of windows - or change the key-bindings to personal taste (which is what ahk is all about).
The file I was referring to was the lower case control2tempo.exe in the bin sub-directory that is 31k. There is a link to a zip file containing these files on that thread. If you want to add a button to launch a spreadsheet feel free to use it. At least someone would be using it for something.
BTW in the thread I mention that there was a bug (for a particular function). I found what it was but I was on vacation with a mac and like the dwarfs in the mines of Moria, I dug too deep and made a bunch of changes and added a couple of features without the benefit of incrementally making adjustments to the source code and now have to either revert to where I was, or do a tough debugging. Either way I need a few free days and the right frame of mind to do it.
_____
The real purpose is to generate a tempomap - particularly for songs that were recorded without a click but with natural variations by the performers. One that can be tweaked, refined and if 'home' is adjusted you can effortlessly regenerate the map. It is all described here:
http://www.sawstudiouser.com/forums/sho ... trol2tempo
There were a couple of problems I encountered, and that is that the Control2Tempo.exe is a 'compiled' auto-hot-key script does not work on all versions of windows. This was my first attempt to make an 'executable' from AHK. When I investigated I determined that I would not attempt that again, but simply say that installing auto-hot-key-2 is a prerequisite. Instead one would run the Control2Tempo.ahk script and do the slight adjustments to the script needed to run it on various versions of windows - or change the key-bindings to personal taste (which is what ahk is all about).
The file I was referring to was the lower case control2tempo.exe in the bin sub-directory that is 31k. There is a link to a zip file containing these files on that thread. If you want to add a button to launch a spreadsheet feel free to use it. At least someone would be using it for something.
BTW in the thread I mention that there was a bug (for a particular function). I found what it was but I was on vacation with a mac and like the dwarfs in the mines of Moria, I dug too deep and made a bunch of changes and added a couple of features without the benefit of incrementally making adjustments to the source code and now have to either revert to where I was, or do a tough debugging. Either way I need a few free days and the right frame of mind to do it.
Re: The Three Control Track Menu Options
jmh,
You noted, "There were a couple of problems I encountered, and that is that the Control2Tempo.exe is a 'compiled' auto-hot-key script does not work on all versions of windows." I employed AutoHotKey for a time, but found the language set rather limited. I will not get into ALL of the details of those limitations, but I DID find Autoit to be much less limited.
I did take a number of Brett Brandon's AHK scripts and port those over to Autoit. The same could be done with Control2Tempo.
You noted, "There were a couple of problems I encountered, and that is that the Control2Tempo.exe is a 'compiled' auto-hot-key script does not work on all versions of windows." I employed AutoHotKey for a time, but found the language set rather limited. I will not get into ALL of the details of those limitations, but I DID find Autoit to be much less limited.
I did take a number of Brett Brandon's AHK scripts and port those over to Autoit. The same could be done with Control2Tempo.
Re: The Three Control Track Menu Options
The .ahk script is in that zip. Several of the functions are oddball ones, so they may not all exist in autoit. Also the fix is just to install autohotkey2 and run the Control2Tempo.ahk script. If studio is run as admin, the ahk script also must be launched as admin. In that case an extra parameter may be needed in the 'run' command as described in posts 16 & 18:mr_es335 wrote:jI did take a number of Brett Brandon's AHK scripts and port those over to Autoit. The same could be done with Control2Tempo.
http://www.sawstudiouser.com/forums/sho ... post224375
It is coming back to me, when the AHK executable (Control2Tempo.exe - which is a bundle of the AHK interpreter and the script, and not a 'normal' compiled program) calls bin/control2tempo.exe it does not consistently pass on admin privileges to some of the functions.
-----
There is a SSSetup function in the script that primarily collects the unique IDs of studio's windows may come in handy for some of the things you are doing:
Global SSWINDOW := map("SAWSTUDIO_CTRLTRACK", 0, "SAWSTUDIO_MULTITRACK", 0, "SAWSTUDIO_MAIN", 0)
...it could be generalized to collect all of Studio's available window names to that hash ( - or map as it is known in ahk) and have it collect IDs for each window - to make it handy for other uses - but that would be a bit more involved than what I did, as the script would need to cycle through the menus to activate all of the views...