Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Momentary Clip Launching #20

Closed
weskoop opened this issue Feb 20, 2022 · 6 comments
Closed

Momentary Clip Launching #20

weskoop opened this issue Feb 20, 2022 · 6 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@weskoop
Copy link
Owner

weskoop commented Feb 20, 2022

New control surface API to launch clips with specific options. In the APC40mkII and Launchpad Pro scripts, you can:

  • Hold shift to immediately launch a clip or a scene
  • Release the clip or scene button while holding shift, to return immediately to last playing clip(s)

Momentary clips would be awesome, but updating the API version will exclude old versions of Bitwig. At a minimum we'll push one more release without this, but then we make make future versions require 4.2, or we maintain 2 versions, less into that.

We also use Shift + Grid for Selecting a slot, so this may need to be an optional thing, or Select only works on empty slots.

We'll look into all of this later when 4.2 is out of beta.

@weskoop weskoop added the enhancement New feature or request label Feb 20, 2022
@weskoop weskoop changed the title Momentary Clip Launching. Momentary Clip Launching Feb 20, 2022
@weskoop weskoop closed this as completed Feb 20, 2022
@weskoop weskoop reopened this Feb 20, 2022
@mwozniczak
Copy link

but then we make make future versions require 4.2

I'm relatively new to Bitwig's API, but wouldn't either try-catching, or something like

const some_bitwig_functionality = some_bitwig_functionality|a_stub_that_does_nothing

not work in this situation?

@weskoop
Copy link
Owner Author

weskoop commented Jun 24, 2022

I'm pretty sure the momentary clip launching is only available in the 4.2+ version of the Controller API. In any controller script, you need to declare the minimum API version at the beginning of the script. Is not the worst situation, since users on the old version can always use 1.0

@mwozniczak
Copy link

@weskoop what would happen if you declared a lower version, and then tried to use something from the higher version? i mean, on bitwig that supports the higher version? would it reject it, or let it through? because if the latter, then try-catching or stubbing might be a way of supporting both the lower versions, and the new functionality

@weskoop
Copy link
Owner Author

weskoop commented Jun 25, 2022

I'm open to reviewing a PR if you'd like to try, but don't have a ton of time right now to expand this. The other issue is that the typescript lib I'm using is still at API 12, so we may need to augment that as well.

@mwozniczak
Copy link

understandable, once I'm back from my vacation i'd be glad to give it a go!

@weskoop weskoop added the wontfix This will not be worked on label Mar 22, 2024
@weskoop
Copy link
Owner Author

weskoop commented Mar 22, 2024

Thanks for your notes, I really appreciate you putting in the time to debug; Bitwig 5.0+ include native support for the LaunchPad Pro Mk3. This project is no longer supported.

@weskoop weskoop closed this as completed Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants