Re: Scripting newbie
Posted: 18 Oct 2013 03:10
Hi Guys
Have only kinda followed this thread as I dont use Cubase or PC but have been working on AlphaTrack and TranzPort emulations . see Alphatrack thread
Have got the Tranzport timecode stuff running fairly reasonably but need to do some more optimising of the whole thing really . .
Getting values of controls from applications to show the same in Lemur can be difficult - they can vary massively from app to app for one thing.
For instance there is no set point for 'unity' on faders across apps so iff you line in up in Cubase it could be different in Cubendo, or Live or Logic etc
For matching up parameters just for one app can also be complex - they could be simple linear or logarithmic scalings, or more complex functions
If you are pretty good at maths it is probably a bit easier to work out, but it is also possible that a table-based approach has been used that maths won't solve.
Ie 0-127 could be used in a log function to show frees or it may just look up values that have no maths involved.
For Faders - One way is just to place text markers by hand to show the important approximate positions as Phil said
If using numerical monitors try to get the top end as accurate as possible and ignore the lower end inaccuracies
Hope that helps
MM
Have only kinda followed this thread as I dont use Cubase or PC but have been working on AlphaTrack and TranzPort emulations . see Alphatrack thread
Have got the Tranzport timecode stuff running fairly reasonably but need to do some more optimising of the whole thing really . .
Getting values of controls from applications to show the same in Lemur can be difficult - they can vary massively from app to app for one thing.
For instance there is no set point for 'unity' on faders across apps so iff you line in up in Cubase it could be different in Cubendo, or Live or Logic etc
For matching up parameters just for one app can also be complex - they could be simple linear or logarithmic scalings, or more complex functions
If you are pretty good at maths it is probably a bit easier to work out, but it is also possible that a table-based approach has been used that maths won't solve.
Ie 0-127 could be used in a log function to show frees or it may just look up values that have no maths involved.
For Faders - One way is just to place text markers by hand to show the important approximate positions as Phil said
If using numerical monitors try to get the top end as accurate as possible and ignore the lower end inaccuracies
Hope that helps
MM