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

[moss]

Regarding Push 3, is it somehow possible to keep the session view focus always on the top level view of the clip launcher, irregardless if with mouse I am currently selecting a group or a track within a group?

You could pin one of the top tracks.

[moss]

HI are you planning the APB64 in the future? I like the fire controller. I wonder if this is better

No idea.

[xtreme sounds]

HI are you planning the APC64 in the future? I like the fire controller. I wonder if this is better

No idea.

Sorry I meant Akai APC64. its probably better to get a used push 2

[kulacki]

hello Moss, sadly Electra 3.5 bug is still here in 21.5, different Bitwig 5.11 project altogether on Ventura 13.6.2, only Electra connected, no other DAW running, cleanest possible scenario in my workflow. I think it is sometimes happening with remapped Volume control to Macro if that makes any sense, so maybe that could help. Thank you.

Index 8 out of bounds for length 7
java.lang.ArrayIndexOutOfBoundsException: Index 8 out of bounds for length 7
at de.mossgrabers.controller.electra.one.controller.ElectraOneControlSurface.handleSysexCommandsController(ElectraOneControlSurface.java:531)
at de.mossgrabers.controller.electra.one.controller.ElectraOneControlSurface.processSysEx(ElectraOneControlSurface.java:485)
at de.mossgrabers.controller.electra.one.controller.ElectraOneControlSurface.handleSysEx(ElectraOneControlSurface.java:442)
at pCs.Ked(SourceFile:240)
at tIp.Ked(SourceFile:880)
at ohE.Ked(SourceFile:726)
at uY.Ked(SourceFile:57)
at Eg1.Ked(SourceFile:40)
at PrT.Ked(SourceFile:37)
at raN.Ked(SourceFile:1067)
at uY.BDt(SourceFile:28)
at raN.Nnb(SourceFile:1187)
at kF.Ked(SourceFile:287)
at DE.run(SourceFile:91)
at kF.run(SourceFile:191)

[salter10]

Hello folks. I have a question about Push 2/3. If for some reason this is not the appropriate place to ask this question, please let me know if there's a better forum for this.

I'm just about to pull the trigger on the Push 3 - at least for the 30 days trial-return period Ableton allows. I am wondering if anyone here is using either Push 2 or 3 with Bitwig - especially in "performance" mode, less so for fine grained composition workflow that I'll continue to do directly through Bitwig. And generally whether they find it useful for the purpose. Obviously - but I'll state it clearly - using Moss brilliant scripts.

Thanks in advance. Salter.

[El_Qarrier]

Hello,

FIrst of all thanks you for your amazing work§

Then, i have, to be a honest a problem that are is on every daw.

Pads are not as responsive as they are when running maschine software.

It's like you can't use three of four pads at once and if i use my little finger or do a little of pression on a pad it doesnt detect it it's not pleasant at all when you want to play something.

Any solutions ? Maybe if have to upload a video of comparaison to be more clear or its something known ?

I tried some key words before in search engine but i havent found my answer (or maybe i'm not using the right keywords)

[moss]

Hello,

FIrst of all thanks you for your amazing work§

Then, i have, to be a honest a problem that are is on every daw.

Pads are not as responsive as they are when running maschine software.

It's like you can't use three of four pads at once and if i use my little finger or do a little of pression on a pad it doesnt detect it it's not pleasant at all when you want to play something.

Any solutions ? Maybe if have to upload a video of comparaison to be more clear or its something known ?

I tried some key words before in search engine but i havent found my answer (or maybe i'm not using the right keywords)

You can change the "Pad Velocity Curve" with the NI Controller Editor for the DrivenByMoss template.

[El_Qarrier]

Hello,

FIrst of all thanks you for your amazing work§

Then, i have, to be a honest a problem that are is on every daw.

Pads are not as responsive as they are when running maschine software.

It's like you can't use three of four pads at once and if i use my little finger or do a little of pression on a pad it doesnt detect it it's not pleasant at all when you want to play something.

Any solutions ? Maybe if have to upload a video of comparaison to be more clear or its something known ?

I tried some key words before in search engine but i havent found my answer (or maybe i'm not using the right keywords)

You can change the "Pad Velocity Curve" with the NI Controller Editor for the DrivenByMoss template.

Yep i omitted to say i tried every setting in here, perhaps the cable i use is faulty i tried two different but still.

edit: if it works well in maschine software no reason to change cable

Thanks for you answer anyway

[moss]

Hello,

FIrst of all thanks you for your amazing work§

Then, i have, to be a honest a problem that are is on every daw.

Pads are not as responsive as they are when running maschine software.

It's like you can't use three of four pads at once and if i use my little finger or do a little of pression on a pad it doesnt detect it it's not pleasant at all when you want to play something.

Any solutions ? Maybe if have to upload a video of comparaison to be more clear or its something known ?

I tried some key words before in search engine but i havent found my answer (or maybe i'm not using the right keywords)

You can change the "Pad Velocity Curve" with the NI Controller Editor for the DrivenByMoss template.

Yep i omitted to say i tried every setting in here, perhaps the cable i use is faulty i tried two different but still.

Thanks for you answer anyway

Then you can try to contact NI. I cannot change anything from my side.

[Kaz62]

Hi Moss,

It seems that there is a small issue introduced after 21.2 on Generic Flexi. I was able to revert from 21.5 after noticing it.
"Track n: Select" functions only changes the focus in the Launcher and do not actually select the instrument.
I see that there was breaking changes on the Generic Flexi in the release notes, but I don't think this affects this function since it is assigned to a button.
Is this by design?
Thanks again for all the good work that you are doing.

[carlca]

Can anyone confirm my suspicion that Bitwig is now (as of Bitwig v5.1 beta 6) using the Java 21.01 engine. I got this by navigating to

Code: Select all

/Applications/Bitwig Studio 5.1b6/Contents/PlugIns/JavaVM-arm64.bundle/Contents/Home/bin

and typing

Code: Select all

java -version

which gave me...

Code: Select all

java version "21.0.1" 2023-10-17 LTS
Java(TM) SE Runtime Environment (build 21.0.1+12-LTS-29)
Java HotSpot(TM) 64-Bit Server VM (build 21.0.1+12-LTS-29, mixed mode)

Also, does that now mean I have to alter my Maven POM file to have...

Code: Select all

        <dependency>
            <groupId>com.bitwig</groupId>
            <artifactId>extension-api</artifactId>
            <version>21</version>
        </dependency>

[wimvandenborre]

Anyone having the issue with the launchpad, when note repeat is selected octaves are playing in stead of one note?

[moss]

Hi Moss,

It seems that there is a small issue introduced after 21.2 on Generic Flexi. I was able to revert from 21.5 after noticing it.
"Track n: Select" functions only changes the focus in the Launcher and do not actually select the instrument.
I see that there was breaking changes on the Generic Flexi in the release notes, but I don't think this affects this function since it is assigned to a button.
Is this by design?
Thanks again for all the good work that you are doing.

Thanks for reporting! Will be fixed in the next update!

[moss]

Anyone having the issue with the launchpad, when note repeat is selected octaves are playing in stead of one note?

It is not a simple note repeat but an arpeggiator. So this depends on the octave setting.

[wimvandenborre]

ah ok, makes sense then why i play 2 samples in the drummachine they alternate Any plans for adding the note repeat device functionality to it?