DrivenByMoss: Bitwig extension for many hardware controllers (version 26.6.1)

Post Reply New Topic
RELATED
PRODUCTS Bitwig Studio 6$399.00Buy Maschine

Post

I´ve found the Reason for the "Could not open Midi Out" Problem: It was one of the installes programs that blocked the Midi config (not bomes as i first thought, bomes was influenced by that prog as well). In my Case it was Desscapes from Stardock that blockes the Midi out. Deinstalled, cleaned the reg an now all runs as it should
Top

Post

Hey Jürgen,
first of all thanks for all the hard work you put into the push script! I use it since many years and its absolutely stunning!

Nevertheless i have one question regarding the push 1 in session mode triggering scenes. In the older version it was possible to trigger scenes in flipped mode from the second row below the display. This way it was easy to see which scene belongs to which clips.

With the new version i am just able to trigger it with the timing buttons on the right side. Is this possible to change ? i cant find anything in the preferences about it.

Nevertheless thx for all the good work. You are awesome Jürgen :)
Top

Post

Hey how to lock velocity in drum step sequencer un launchpad x? Thanks
Top

Post

Dipe wrote: Tue Aug 25, 2020 6:20 pm Nevertheless i have one question regarding the push 1 in session mode triggering scenes. In the older version it was possible to trigger scenes in flipped mode from the second row below the display. This way it was easy to see which scene belongs to which clips.

With the new version i am just able to trigger it with the timing buttons on the right side. Is this possible to change ? i cant find anything in the preferences about it.
Sorry, no. It changed since there were several issues because it conflicted with the use of the buttons for the display modes.
Top

Post

Luis887 wrote: Tue Aug 25, 2020 6:32 pm Hey how to lock velocity in drum step sequencer un launchpad x? Thanks
AFAIK you can't do this via the controller. That'd be a nice feature for the drum modes though!
Top

Post

Hallo Jürgen.

First let me thank you for this amazing piece of software. After the configuration of various controllers and daws this is fun for the first time!

Unfortunately i have still one problem, which is hard to ignore: Sometimes my faderfox (UC4) is going »offline«. It means that the hardware is still connected, running and sending data, but Bitwig does'nt react anymore. The Flexi controller in the prefs is still active, too. Usually quitting and reopening Bitwig works for me. I can't figure out when or why this happens? Is there any log file?

I'm using Bitwig 3.1.1, macos 10.11 and the faderfox is directly connected via usb.

Thanks a lot
Jan
Top

Post

Launchpad 95 script lock velocity in drum Mode add this please.thanks!!!!
Top

Post

Hi there

any chance on a future update the akai fire could display which bars the drum sequencer is displaying when pressing the right and left grid buttons?
Top

Post

stoltenberg wrote: Thu Aug 27, 2020 6:04 pm Hallo Jürgen.

First let me thank you for this amazing piece of software. After the configuration of various controllers and daws this is fun for the first time!

Unfortunately i have still one problem, which is hard to ignore: Sometimes my faderfox (UC4) is going »offline«. It means that the hardware is still connected, running and sending data, but Bitwig does'nt react anymore. The Flexi controller in the prefs is still active, too. Usually quitting and reopening Bitwig works for me. I can't figure out when or why this happens? Is there any log file?

I'm using Bitwig 3.1.1, macos 10.11 and the faderfox is directly connected via usb.

Thanks a lot
Jan
Check if there is an exception in the Javascript console (open from the document pane on the right). Also you can check the Bitwig log file.
Top

Post

… it happened again in the minute, but there a no details in the two logs?
(I'm using the console app and /Library/Logs/Bitwig, right?)

Activating »Add detected controllers automatically« and disconnecting/reconnecting the usb-cable seems to help.
moss wrote: Fri Aug 28, 2020 8:02 am Check if there is an exception in the Javascript console (open from the document pane on the right). Also you can check the Bitwig log file.
Top

Post

Push 2 Controller - UX Problem with Clip Display

There is a UX thing (not really a bug) but for intuitive understanding a little ugly.

When you use clips with the push 2 and the clip is shown on the screen, it adapts its vertical appearance (resolution) and density upon the distance and numbers of notes (octaves), that is used.

If the whole clip fits on the display, everything is fine. But if you zoom in and den clip has to visually split up into e.g. two parts and on each part the range between the notes is different, the display shows a different "resolution". That is very confusing because the first time I thought i switched to another track and clip.

I made a video. Maybe it is more clear what I mean
https://mytube.madzel.de/videos/watch/4 ... 21018ce16f

If the Video doesn't playback, you can download it (6mb)
Last edited by OdoSendaidokai on Fri Aug 28, 2020 3:45 pm, edited 3 times in total.
Top

Post

stoltenberg wrote: Fri Aug 28, 2020 10:20 am … it happened again in the minute, but there a no details in the two logs?
(I'm using the console app and /Library/Logs/Bitwig, right?)

Activating »Add detected controllers automatically« and disconnecting/reconnecting the usb-cable seems to help.
moss wrote: Fri Aug 28, 2020 8:02 am Check if there is an exception in the Javascript console (open from the document pane on the right). Also you can check the Bitwig log file.
This sounds more like a hardware issue. Try the usual: switch USB cables and ports.
Could also be power management. Check you energy plan if devices get deactivated after some time.
Top

Post

Push 2 Controller - Can't change Drum Sequencer resolution anymore

Today I played around with the Raindrop Sequencer and while increasing the clip size to 32 bars, the controller script crashed twice with the following error message
Push 2 did something wrong
Parameter x (0513) must be in the range 0 to 511
Disable / Restart
I selected Restart.

Since then I can't change the resolution 1/4, 1/8 ,... in with the following Sequencer Types
- Drum
- Drum 4
- Drum 8

It's "frozen" on 1/32 resolution

In all other Sequencers (Sequencer, PolySeq and Raindrop) it is still working.
I already switched of everything (push 2 and computer) took both from the powerline for 5 Minutes. But still the same situation.

What can I do now?
Top

Post

OdoSendaidokai wrote: Fri Aug 28, 2020 3:53 pm Push 2 Controller - Can't change Drum Sequencer resolution anymore

Today I played around with the Raindrop Sequencer and while increasing the clip size to 32 bars, the controller script crashed twice with the following error message
Push 2 did something wrong
Parameter x (0513) must be in the range 0 to 511
Disable / Restart
I selected Restart.

Since then I can't change the resolution 1/4, 1/8 ,... in with the following Sequencer Types
- Drum
- Drum 4
- Drum 8

It's "frozen" on 1/32 resolution

In all other Sequencers (Sequencer, PolySeq and Raindrop) it is still working.
I already switched of everything (push 2 and computer) took both from the powerline for 5 Minutes. But still the same situation.

What can I do now?
Can you please post the full exception from the JavaScript console? Or give some steps to reproduce.
Top

Post

moss wrote: Fri Aug 28, 2020 4:17 pm
OdoSendaidokai wrote: Fri Aug 28, 2020 3:53 pm Push 2 Controller - Can't change Drum Sequencer resolution anymore

Today I played around with the Raindrop Sequencer and while increasing the clip size to 32 bars, the controller script crashed twice with the following error message
Push 2 did something wrong
Parameter x (0513) must be in the range 0 to 511
Disable / Restart
I selected Restart.

Since then I can't change the resolution 1/4, 1/8 ,... in with the following Sequencer Types
- Drum
- Drum 4
- Drum 8

It's "frozen" on 1/32 resolution

In all other Sequencers (Sequencer, PolySeq and Raindrop) it is still working.
I already switched of everything (push 2 and computer) took both from the powerline for 5 Minutes. But still the same situation.

What can I do now?
Can you please post the full exception from the JavaScript console? Or give some steps to reproduce.
1. Open Bitwig and choose a Drum Machine with a Preset
2. Create new clip with 32 bars
3. Change to Raindrop sequencer
4. Change resolution to 1/32
5. Run clip
6. Insert 32th (e.g. Kick)

Here is the output of the Push 2 Javascript console

Code: Select all

null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
null
Parameter x (=512) must be in the range 0 to 511
zVB: Parameter x (=512) must be in the range 0 to 511
    at LWY.inRange(SourceFile:185)
    at com.bitwig.flt.control_surface.proxy.ControlSurfaceObject.inRange(SourceFile:344)
    at com.bitwig.flt.control_surface.proxy.ClipProxy.validX(SourceFile:1557)
    at com.bitwig.flt.control_surface.proxy.ClipProxy.validPosition(SourceFile:1541)
    at com.bitwig.flt.control_surface.proxy.ClipProxy.validPosition(SourceFile:1536)
    at com.bitwig.flt.control_surface.proxy.ClipProxy.setStepCommon(SourceFile:477)
    at com.bitwig.flt.control_surface.proxy.ClipProxy.setStep(SourceFile:465)
    at com.bitwig.flt.control_surface.proxy.DelegatingClipProxy.setStep(SourceFile:365)
    at de.mossgrabers.bitwig.framework.daw.CursorClipImpl.setStep(CursorClipImpl.java:380)
    at de.mossgrabers.framework.view.AbstractRaindropsView.onGridNote(AbstractRaindropsView.java:102)
    at de.mossgrabers.framework.controller.AbstractControlSurface.handleGridNote(AbstractControlSurface.java:941)
    at de.mossgrabers.framework.controller.AbstractControlSurface.lambda$createPads$3(AbstractControlSurface.java:187)
    at de.mossgrabers.framework.controller.hardware.AbstractHwButton.handleButtonPressed(AbstractHwButton.java:69)
    at com.bitwig.flt.control_surface.proxy.CustomAction.lambda$invokedByHardwareAction$0(SourceFile:41)
    at fyC.zuE(SourceFile:94)
    at fyC.Agf(SourceFile:90)
    at u3g.mn(SourceFile:128)
    at xNa.xdW(SourceFile:76)
    at gVa.THb(SourceFile:248)
    at gKZ.zuE(SourceFile:335)
    at cVf.zuE(SourceFile:205)
    at olG.run(SourceFile:91)
    at cVf.run(SourceFile:106)

Called init()
Running.
Top
Post Reply

Return to “Controller Scripting”