Closed git-moss closed 2 years ago
Just found out that the problem seems to be a different one! Bitwig seems to cache all Cursor Tracks with an ID until Bitwig is restarted and even shares them among all scripts and extensions!
Needs further analysis and a test script.
With the used ID in this demo script no names are output if the dumpNames() function is called. Changing the ID to e.g. "xyz" makes it work.
Cannot be reproduced anymore in 4.3 Beta 4.
just wrote a simple test script to answer a question of someone. I noticed that if you have a number at the end of the cursor track ID it is not pinnable (or does not work at all, havent tested):
E.g.:
cursorTrack = host.createCursorTrack("TM0", "TrackMonitor", 0, 0, true);
That works:
cursorTrack = host.createCursorTrack("T0M", "TrackMonitor", 0, 0, true); cursorTrack = host.createCursorTrack("0TM", "TrackMonitor", 0, 0, true);