Page 1 of 1
Posted: 25 Mar 2015, 17:21
by drakh
hello in the manual there is written
On Activation
Sends a 1 value when the patch is activated or starts its calculation:
when the main engine of Usine is switched ON
when the parent rack is activated in the The Grid Panel
out
Sends 1 when the patch is just activated, 0 otherwise.
how does it work wit the main engine? it sends 1 only when the main engine is started for the first time, or any time when main engine changes its state from off to on?
Posted: 26 Mar 2015, 14:33
by sephult
Hi drakh,
It looks like On Activation is actually a more rack specific. If you use in a patch within the rack, it sends a 1,0 pulse when the rack is enabled.
Almost like a Rack-Activation
Used in conjunction with the Grid, when the Rack is activated by the Grid it will send out a pulse.
On Initialization seems like it only happens once when the first-time the main engine is started...like a first-time initialization.
Need to update Wiki with some clearer info for this and use.
-S
Posted: 26 Mar 2015, 21:50
by drakh
but in HH1 this works :/ as written in manual. i am using it in arGRID for syncing the tracks to main tempo. so everytime, i stop the main engine, and then start it again, the tracks start on the begining in the correct sync with main tempo.
and one another thing - the main tempo position indicators are somehow stucked. In HH1 when i restarted the main engine, main tempo showed normally position 1/1 , but in HH2 the beat indicator is somhow stucked, for example i stop main engine on 2/3, then i start, the indicator shows 1/3 when it should show 1/1 (so i assume all computations based on bar/beat positions will be wrong)
Is there some other module which sends something like "on start" event ?
Posted: 27 Mar 2015, 09:49
by drakh
oh, nevermind i bugreported it and it will behave like in HH1 in .63 release as senso replied thru bugtracker
Posted: 30 Mar 2015, 18:49
by drakh
huh. now in .63 where the main synchro is fixed, it sends 1 when any rack is activated
Posted: 30 Mar 2015, 18:51
by drakh
probably it wil be good to split this module into separate parts to catch events idependly
on activation of rack (
https://github.com/drakh/hollyhock-libr ... vation.pat )
on activation of patch
on activation of main engine