Closed kdejaeger closed 4 years ago
Only if you tell me how you do that :-)
Ok :). Check out my template. The navigation section has an invisible text widget for /track/selected/hasParent. The widgets output (0 or 1) is then consumed in the dynamic css property of the 'group-up'-button:
css = @{tools_track_hasparent} == 0 ? "visibility:hidden" : "" }
The whole trick I use with invisible buttons will be replaced by this new feature I think: https://github.com/jean-emmanuel/open-stage-control/issues/191 that was just pushed. I don't have time to check it out but looking from the comments we could do something like this now as the value of a css field:
hasParent = OSC{"/track/selected/hasParent", 0}
css = hasParent == 0 ? "visibility:hidden" : ""
}
Thanks, will add hasParent in the next update.
Just tried to implement this but it turns out it is currently not possible. I also checked back with Bitwig to be sure and it is now on the (long) wishlist. Sorry.
The Track interface has a position, you should check but I believe that only the root track group has the position 0.
Good idea, I could check if the position is 0 and if it is a group. Will give it a try.
Maybe checking that the position is 0 is enough.
Actually, that is not going to work. Imagine you have 20 tracks on the top level, they all have different positions but no parent. Same is inside of a group, whicj jas a parent.
Alexandre Bique notifications@github.com schrieb am Mi., 22. Mai 2019, 17:23:
Maybe checking that the position is 0 is enough.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/git-moss/DrivenByMoss/issues/53?email_source=notifications&email_token=AAXSNVBMNKCYUI4TS7N4EXTPWVQO7A5CNFSM4EU4QKQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7NGSQ#issuecomment-494850890, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXSNVBB3VWWKO67XVQGOH3PWVQO7ANCNFSM4EU4QKQA .
Every tracks always have a parent, only the root track group does not have one.
Maybe you're interested in the depth of the track?
Yes, but that info does not help. I cannot check for the root track ...
Alexandre Bique notifications@github.com schrieb am Mi., 22. Mai 2019, 18:12:
Maybe you're interested in the depth of the track?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/git-moss/DrivenByMoss/issues/53?email_source=notifications&email_token=AAXSNVBKMSISUX5AVMEBMSTPWVWH5A5CNFSM4EU4QKQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7SBZQ#issuecomment-494870758, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXSNVHFYH5XX2LRR6CNFG3PWVWH5ANCNFSM4EU4QKQA .
Track Track.createParentTrack()
I think that would do the job. You can then call parentTrack.exists(), move the cursor to the parent track and so on...
Would it work for you?
I guess.
Alexandre Bique notifications@github.com schrieb am Mi., 22. Mai 2019, 18:23:
Track Track.createParentTrack()
I think that would do the job. You can then call parentTrack.exists(), move the cursor to the parent track and so on...
Would it work for you?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/git-moss/DrivenByMoss/issues/53?email_source=notifications&email_token=AAXSNVDTFQVICSB5R6PKZB3PWVXQHA5CNFSM4EU4QKQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7TCQY#issuecomment-494874947, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXSNVG52SLJ5FQWSWTJDS3PWVXQHANCNFSM4EU4QKQA .
There is also the wish to access the whole path from tje root to the cirrent track. Can we solve that somehow in one go?
Jürgen Moßgraber juergen.mossgraber@googlemail.com schrieb am Mi., 22. Mai 2019, 18:24:
I guess.
Alexandre Bique notifications@github.com schrieb am Mi., 22. Mai 2019, 18:23:
Track Track.createParentTrack()
I think that would do the job. You can then call parentTrack.exists(), move the cursor to the parent track and so on...
Would it work for you?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/git-moss/DrivenByMoss/issues/53?email_source=notifications&email_token=AAXSNVDTFQVICSB5R6PKZB3PWVXQHA5CNFSM4EU4QKQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7TCQY#issuecomment-494874947, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXSNVG52SLJ5FQWSWTJDS3PWVXQHANCNFSM4EU4QKQA .
What is the whole path supposed to look like?
e.g. Drums -> Toms -> Floor Tom
Alexandre Bique notifications@github.com schrieb am Mi., 22. Mai 2019, 18:46:
What is the whole path supposed to look like?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/git-moss/DrivenByMoss/issues/53?email_source=notifications&email_token=AAXSNVHKJM7LC6ESCLPZEBDPWV2FFA5CNFSM4EU4QKQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7U65A#issuecomment-494882676, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXSNVDE7SWJ2X574FQ7JVDPWV2FFANCNFSM4EU4QKQA .
So you can quicker mobe up a group tree.
Jürgen Moßgraber juergen.mossgraber@googlemail.com schrieb am Mi., 22. Mai 2019, 18:48:
e.g. Drums -> Toms -> Floor Tom
Alexandre Bique notifications@github.com schrieb am Mi., 22. Mai 2019, 18:46:
What is the whole path supposed to look like?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/git-moss/DrivenByMoss/issues/53?email_source=notifications&email_token=AAXSNVHKJM7LC6ESCLPZEBDPWV2FFA5CNFSM4EU4QKQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7U65A#issuecomment-494882676, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXSNVDE7SWJ2X574FQ7JVDPWV2FFANCNFSM4EU4QKQA .
Yes that is useful, I'll discuss with Nick how we want to do that.
Breadcrumbs. :)
Exactly 😁
Michael Schmalle notifications@github.com schrieb am Mi., 22. Mai 2019, 18:57:
Breadcrumbs. :)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/git-moss/DrivenByMoss/issues/53?email_source=notifications&email_token=AAXSNVDPKYZQGGKESSK7JODPWV3PJA5CNFSM4EU4QKQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7VV3Y#issuecomment-494885615, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXSNVFCARTITGGSOBQF2QTPWV3PJANCNFSM4EU4QKQA .
That might be useful if push 3 has a touch screen. Did any of you guys put your hands on the AKAI force?
@abique Yeas I have the Force, don't get me started on Akai, like Native Instruments and the Maschine Studio bug, hehe. I got it for my guitar recording and such.
I'll really like it when I Akai finally finishes it's implementation. Seems like they released it when it was still alpha. :)
Also, I don't think they are allowing USB MIDI, yes you heard it right, no USB MIDI, let's just say I and others were not happy on their site. Akai stonewalled, I left the forum and now I am talking to you about it. :)
I am doing Touch4Bitwig right now, so this is funny.
/track/hasParent {0,1} will be added to DrivenByMoss 8.50.
Hi, I tested this today and noticed that /track/selected/hasParent does not work yet. (bitwig 3.1). Can you verify/propagate hasParent also for the /selected url? Just like /track/selected/isGroup works as well?
That is not necessary since there is only one parent, so you can simply use /track/hasParent.
I would like to have a /track/selected/hasParent so I can conditionality show a /track/parent button.