DrivenByMoss: Bitwig extension for many hardware controllers (version 26.6.1)
-
- KVRian
- 784 posts since 29 Mar, 2016
HI any way to look at the root note setting on the fire? holding shift and pressing grid buttons is kind of slow. Im wondering if there is a way to get it to work with the selector knob instead??
-
- KVRian
- 784 posts since 29 Mar, 2016
hi never mind on the root note idea for the fire - it would probably mess up using the selector know. thanks
-
- KVRian
- 784 posts since 29 Mar, 2016
Hi sir on the fire. I am trying to load custom samples into the drum machine using the small plus sign in the c1 for example and I lose the ability to mute using the drum sequencer. The four buttons to the left no longer show green lights or anything. Its strange because if I load a drum machine preset like California 1 the mutes work but as soon as I load up my own sample the buttons go dark and unresponsive.
This is occurring loading one shot samples. But i would also like to load loops in the drum machine parts and mute and unmute them for performance.
However if I load up a drum machine preset and then replace the sample in the sampler for each note, then the mutes still work on the fire.
This is occurring loading one shot samples. But i would also like to load loops in the drum machine parts and mute and unmute them for performance.
However if I load up a drum machine preset and then replace the sample in the sampler for each note, then the mutes still work on the fire.
-
OdoSendaidokai OdoSendaidokai https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=466569
- KVRist
- 216 posts since 24 May, 2020 from Berlin
I used used the DrivenByMoss 10.6.1 and now the DRUM/Drum4/Drum8 are working again.moss wrote: Fri Aug 28, 2020 4:17 pm Can you please post the full exception from the JavaScript console? Or give some steps to reproduce.
Then I switched back to 10.6.2 = same bug. Switching back to 10.6.1 everything is fine. So for now I'm working on 10.6.1. Maybe this info helps you finding the bug.
- KVRAF
- Topic Starter
- 4875 posts since 13 May, 2004
- KVRAF
- Topic Starter
- 4875 posts since 13 May, 2004
WIll be in the next update.melodyz wrote: Fri Aug 28, 2020 12:12 am 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?
- KVRAF
- Topic Starter
- 4875 posts since 13 May, 2004
I see what you mean. The problem is that I only know about the current page and not the whole clip.OdoSendaidokai wrote: Fri Aug 28, 2020 1:35 pm 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.
- KVRAF
- Topic Starter
- 4875 posts since 13 May, 2004
Just fixed a bug that the number of steps were too small. 32 measures at 1/32t are now working fine (gets a bit slow since inserting notes is not that fast). Measures greater than 32 are ignored.OdoSendaidokai wrote: Sat Aug 29, 2020 5:18 pmI used used the DrivenByMoss 10.6.1 and now the DRUM/Drum4/Drum8 are working again.moss wrote: Fri Aug 28, 2020 4:17 pm Can you please post the full exception from the JavaScript console? Or give some steps to reproduce.
Then I switched back to 10.6.2 = same bug. Switching back to 10.6.1 everything is fine. So for now I'm working on 10.6.1. Maybe this info helps you finding the bug.
Please test again with the next version. If you still have issues with Drum 4 or 8 please report since there is no difference between 10.6.1 and 10.6.2 in that regard.
- KVRAF
- Topic Starter
- 4875 posts since 13 May, 2004
I found the bug in Drum 4 / 8 too, which got introduced in 10.6.2OdoSendaidokai wrote: Sat Aug 29, 2020 5:18 pmI used used the DrivenByMoss 10.6.1 and now the DRUM/Drum4/Drum8 are working again.moss wrote: Fri Aug 28, 2020 4:17 pm Can you please post the full exception from the JavaScript console? Or give some steps to reproduce.
Then I switched back to 10.6.2 = same bug. Switching back to 10.6.1 everything is fine. So for now I'm working on 10.6.1. Maybe this info helps you finding the bug.
- KVRAF
- Topic Starter
- 4875 posts since 13 May, 2004
Mhm, yes. That is problematic since the layer is selected and not the track anymore. I have currently no idea how to fix this.melodyz wrote: Sat Aug 29, 2020 10:31 am Hi sir on the fire. I am trying to load custom samples into the drum machine using the small plus sign in the c1 for example and I lose the ability to mute using the drum sequencer. The four buttons to the left no longer show green lights or anything. Its strange because if I load a drum machine preset like California 1 the mutes work but as soon as I load up my own sample the buttons go dark and unresponsive.
This is occurring loading one shot samples. But i would also like to load loops in the drum machine parts and mute and unmute them for performance.
However if I load up a drum machine preset and then replace the sample in the sampler for each note, then the mutes still work on the fire.
- KVRAF
- Topic Starter
- 4875 posts since 13 May, 2004
DrivenByMoss 10.6.3 is online!
Get it from http://mossgrabers.de
Get it from http://mossgrabers.de
- Requires Bitwig 3.2.5+
- All devices
- Fixed: Raindrop sequencer did crash if more measures than 32 or 32 with 1/32t and 1/32 were used. The later issue is fixed and the first issue get blocked (only 32 measures get filled).
- Fixed: Drum 4 / Drum 8 - setting note length on the grid was broken
- Akai Fire
- New: Displays the number of the edit page when switching to the previous/next.
- Fixed: Crash in browser when select knob was released.
- Launchpad
- New: Updated documentation images
- New: Added fixed accent option to the settings
- New: Fixed accent can be toggled with the yellow pad in the right upper corner of the shift mode
- Push 2
- Fixed: Long press delay was about double the time as with Push 1
-
OdoSendaidokai OdoSendaidokai https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=466569
- KVRist
- 216 posts since 24 May, 2020 from Berlin
Moinmoin, in 10.6.3 I still have the Push 2 Bug with the Drum Sequencers. I can't switch between 1/4 - 1/32t ... so I switched back again to 10.6.1
- KVRAF
- Topic Starter
- 4875 posts since 13 May, 2004
ArghOdoSendaidokai wrote: Mon Aug 31, 2020 5:21 am Moinmoin, in 10.6.3 I still have the Push 2 Bug with the Drum Sequencers. I can't switch between 1/4 - 1/32t ... so I switched back again to 10.6.1
- Requires Bitwig 3.2.5+
- Push
- Fixed: Grid resolution could not be changed in drum modes
-
- KVRian
- 784 posts since 29 Mar, 2016
Thanks Moss
Were you able to look into the Fire issue regarding losing the function of the mute buttons in the drum sequencer when adding new samples to the individual pads in Bitwig?
Were you able to look into the Fire issue regarding losing the function of the mute buttons in the drum sequencer when adding new samples to the individual pads in Bitwig?
You do not have the required permissions to view the files attached to this post.
- KVRAF
- Topic Starter
- 4875 posts since 13 May, 2004
See my answer above.melodyz wrote: Mon Aug 31, 2020 12:46 pm Thanks Moss
Were you able to look into the Fire issue regarding losing the function of the mute buttons in the drum sequencer when adding new samples to the individual pads in Bitwig?
