Hi,
what started out as me being curious about how to handle midi return messages on my traktor f1 controller got a little out of hand
Anyway there is one issue I can't seem to figure out:
Clips have a dedicated delete method so implementation is straightforward,
Scenes and tracks don't have this.
It seems that the way to go here is to do a select/selectInEditor and then an application.remove().
This doesn't work reliably thoguh ... I have to first manually select a scene/track via ui in the editor/mixer window. Only then it is working (until I select the other thing, e.g. scene=>track)
If anyone can shed some light into this on how to handle this properly I'd be more than happy.
Ah and 2.4.3/api 7, javascript fwiw.
w.
Latest News: Bitwig updates Bitwig Studio to v5.1
application.remove() question
-
- KVRer
- Topic Starter
- 29 posts since 26 Jan, 2012
- KVRAF
- 4140 posts since 13 May, 2004
Yes, already on my wishlist: https://github.com/teotigraphix/Framewo ... issues/180
Feel free to bug the Bitwig guys for improvements, too
Feel free to bug the Bitwig guys for improvements, too
-
- KVRer
- Topic Starter
- 29 posts since 26 Jan, 2012
Ok thanks for clarifying, much appreciated.
Found this remarked in the jam script, scary that this has api 1, bitwig guys for sure have been busy on getting modular for quite some time
// TODO : Delete once API has reliable path to doing it
//applicationControl.focusClipLaunch();
//applicationControl.getApplication().remove();
Will bug.
w.
Found this remarked in the jam script, scary that this has api 1, bitwig guys for sure have been busy on getting modular for quite some time
// TODO : Delete once API has reliable path to doing it
//applicationControl.focusClipLaunch();
//applicationControl.getApplication().remove();
Will bug.
w.