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

[moss]

Hi moss, Not sure if you want comments on much older devices, but this functionality on the Komplete Kontrol S61 Mk1 does not work for me here:

Sure! All devices supported in DrivenByMoss are supported

• SHIFT+PLAY - Create new clip, start playback and activate overdub

I just went over every function and all the rest seem to work fine except for this one thing!

Thanks, will be fixed in the next update!

[moss]

Not sure if this one has been solved/reported yet, but using Push 1 on Bitwig 4 exhibits some strange behavior. Transport controls and pads are extremely laggy and unreliable, most of the buttons seem to be non-functional, and the rotary encoders don't appear to change anything on the display or the DAW. I tried the "New Template" trick that others had suggested and it didn't appear to fix it.

I'm fairly sure it's not a hardware issue (opened the Push up and cleaned it inside-and-out, same behavior) and I'm using Arch Linux if that means anything.

Thanks in advance to the community for being so helpful, and to Moss for making such an incredible piece of software!

There were some reports in the last time with issues on Linux with different controllers. Sadly, none of them wanted or had the know-how to dig deaper into this. I only have a test machine with Ubuntu Studio (Ubuntu is the only officially supported distro for Bitwig!) and did not notice any issues so far.

[smoldesu]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Not sure if this one has been solved/reported yet, but using Push 1 on Bitwig 4 exhibits some strange behavior. Transport controls and pads are extremely laggy and unreliable, most of the buttons seem to be non-functional, and the rotary encoders don't appear to change anything on the display or the DAW. I tried the "New Template" trick that others had suggested and it didn't appear to fix it.

I'm fairly sure it's not a hardware issue (opened the Push up and cleaned it inside-and-out, same behavior) and I'm using Arch Linux if that means anything.

Thanks in advance to the community for being so helpful, and to Moss for making such an incredible piece of software!

There were some reports in the last time with issues on Linux with different controllers. Sadly, none of them wanted or had the know-how to dig deaper into this. I only have a test machine with Ubuntu Studio (Ubuntu is the only officially supported distro for Bitwig!) and did not notice any issues so far.

That's okay, thanks for the heads up. I've got a bit of a grasp on debugging this sort of thing on Linux, so I'll report back if I can figure anything out. A few things I can confirm:

- Doesn't seem to be cable-related. Tried ~5 type-A cables, all exhibited the same behavior. Also tried two different devices (both Arch :p), same story.
- Again, doesn't seem to be hardware failure. Display/buttons are responsive outside of Bitwig.
- Script console reports

Code: Select all (#)

Unhandled MIDI status: 0

repeated 5 times on startup. Not sure if that's expected or documented.
- Downgrading the Bitwig extension doesn't seem to fix the issue.

My current guess is that it has something to do with the Java version used on Arch, which is probably more eager to jump to new versions than on more stable distros. I'll play around with downgrading packages to see if I can fix it this weekend. Ciao!

[moss]

My current guess is that it has something to do with the Java version used on Arch, which is probably more eager to jump to new versions than on more stable distros. I'll play around with downgrading packages to see if I can fix it this weekend. Ciao!

Bitwig brings its' own Java runtime. So, it doesn't matter what is installed.
Since Push 1 is pure MIDI, it must be something on the MIDI side. MIDI implementation in Bitwig is also native code, so not Java related.

[xtreme sounds]

Good morning sir. Could you take another look at the velocity settings for the akai fire pads in Bitwig. I believe it supports 4 velocity layers but I can only hear 2 in Bitwig - soft and loud (using the Legend plugin on the filter)

[moss]

Good morning sir. Could you take another look at the velocity settings for the akai fire pads in Bitwig. I believe it supports 4 velocity layers but I can only hear 2 in Bitwig - soft and loud (using the Legend plugin on the filter)

I am afraid it is how it is. These pads are just really really bad.

[wvshpr]

I've experimented a bit with the footswitch input of the Push 2 to start the recording of a new clip in the launcher. Unfortunately when recording a new audio clip it creates a new clip, but does not record anything and mutes the input. With MIDI tracks it seems to work. Is this expected behavior?

[moss]

I've experimented a bit with the footswitch input of the Push 2 to start the recording of a new clip in the launcher. Unfortunately when recording a new audio clip it creates a new clip, but does not record anything and mutes the input. With MIDI tracks it seems to work. Is this expected behavior?

Which function are you using? If you use "New clip", this works only with MIDI.

[wvshpr]

I've experimented a bit with the footswitch input of the Push 2 to start the recording of a new clip in the launcher. Unfortunately when recording a new audio clip it creates a new clip, but does not record anything and mutes the input. With MIDI tracks it seems to work. Is this expected behavior?

Which function are you using? If you use "New clip", this works only with MIDI.

I'll have to double check later, but I think uses “New Button”.

[xtreme sounds]

HI sir

I have a feature request for the Akai fire. When we move it to chromatic mode, it would be nice if under settings we could specify a default Layout (I like 8th up) . Also can we get a drum layout mode for use even without the drum machine loaded? Maybe like the 8th up layout but in a 4 by 4 grid. that would be really useful as well when working with other drum vsts.

[moss]

DrivenByMoss 15.6.0 is online!

Get it from http://mossgrabers.de

• Requires Bitwig 4.1
• Generic Flexi
  • New: Added functions for controlling EQ+ equalizer, which is automatically inserted if one of the functions is triggered.
  • Fixed: Updated/corrected the names of CC and MMC commands.
  • Fixed: Resolution was set to 14-bit on first slot when CC was less than 32 on file load.
• Komplete Kontrol Mk1
  • Fixed: Shift+Play to create a new clip did not work
• MCU
  • New: Option+Toggle Device: Toggle the devices' expanded state
• MidiMonitor
  • Fixed: Updated/corrected the names of CC and MMC commands.
• OSC
  • Fixed: Removed unnecessary invertion of Q-factor parameter. Inverted Q-factor knob in Open Stage Control example template instead.
• Push 1/2
  • New: Added new Bitwig 4.2 devices to track template list.
  • Fixed: Layer detail view (pressing Select button in Drum and Drum 64 modes) did not work for pads > 8.

Enjoy!

[pdxindy]

[moss]

HI sir

I have a feature request for the Akai fire. When we move it to chromatic mode, it would be nice if under settings we could specify a default Layout (I like 8th up) . Also can we get a drum layout mode for use even without the drum machine loaded? Maybe like the 8th up layout but in a 4 by 4 grid. that would be really useful as well when working with other drum vsts.

You can configure this in the document settings. Simply store it in your project template.

[gExpectations]

In the manual to the newest version of "driven by moss" you write "The S-series has additional device/parameters and send modes. Toggle these modes with the CLEAR button." I think this is not correct anymore. As far as I could understand from your videos on A-Series keyboards, they have the mode switches and functionality as well, just not the buttons and the screens.

[moss]

In the manual to the newest version of "driven by moss" you write "The S-series has additional device/parameters and send modes. Toggle these modes with the CLEAR button." I think this is not correct anymore. As far as I could understand from your videos on A-Series keyboards, they have the mode switches and functionality as well, just not the buttons and the screens.

No. On the A-series (and M32) you can only control Volume and Panorama. No Sends and no devices.