Bitwig

moss · Post by **moss** » Mon Mar 06, 2017 8:46 am

askewd wrote: Bug - In 64 drum mode, pressing octave button up/down moves the lights around but then things go whack. Pads don't play etc. I think the lights are in the wrong places.

Can you send me an example project/drum kit, where I can test that?

odz · Post by **odz** » Mon Mar 06, 2017 8:49 am

Request: I would like the 64 pad drum mode to go in rows of 4 upwards, like Ableton Lives 64 pad drum mode, to match the layout of the Drum Machine pads. Is it possible to perhaps add this as a layout?

moss · Post by **moss** » Mon Mar 06, 2017 8:51 am

askewd wrote: bug/suggestion - in the browser, if filters are hidden, it's impossible to get 'out of ' the device presets when looking for a new sound, ie to select presets from a different device. For example i only use collections filter and i have some nicely organised collections such as "Drum Kits" "Pianos" etc. So my browsing is very simple - 1) select a collection 2) select a preset. Easy. The problem is that it only works nicely the first time. Next time i press browse i only see presets related to that device. I need a way of changing device back to 'everything' WITHOUT having to enable that filter.

You can use the cursor keys left/right to switch the tabs of the browser. Pressing cursor left brings you to the devices view.

askewd · Post by **askewd** » Mon Mar 06, 2017 1:20 pm

You can use the cursor keys left/right to switch the tabs of the browser. Pressing cursor left brings you to the devices view.

Thanks Moss, although that's not exactly what i meant. Changing the device to another device still only shows the presets for that specific device. I need a very fast way of reseting the browse to 'everything' so I have access to ALL my presets easily.

Let me try to clarify further.

I have a presets smart-collection called "Bells" In this collection there are number of Bell presets, from many different synths. Around 60 presets in total.

When i first insert the device i can see all 60 bells. Perfect!

But then after loading a bell sound , if i decide that i don't like it ten minutes later... so i want to change it to another bell sound. So I press Browse again. This time i only see say 4 bell sounds - because it's only showing me bells specific to the device.

You see?

So what i would love for it to do, is automatically reset the 'devices' filter to 'everything' when i press browse, so that i can see all my presets all the time. Ideally without needing to keep resetting filters each time.

I understand bitwig is trying to be clever and only show presets relevant to the synth i'm in...and that sometimes is useful, but in terms of the fast live workflow i'm building around the Push2 , it's not helpful.

Hope this makes sense.

I think the solution will be to tie it in with your options to hide filters. If a category is set to hide, that category should default to 'see everything'.

Cheers
DALE

askewd · Post by **askewd** » Mon Mar 06, 2017 1:23 pm

Had another hour on the Push2 today. Some extra findings:

1 - in drum mode, lots of issues where it seems to loses its link between the pad being played, the one being lit up in sequencer , and the one sounding.

I had times when it wouldn't allow me to press select+pad to edit the sound either. One time led to a Push2 crash message:

Push2Crashed
Can not get Property "Index" of null

2 - in sequencer mode, the pads are white and the 'bar length' at top is also white . can they be shaded differently to differentiate?

Thanks
Dale

moss · Post by **moss** » Mon Mar 06, 2017 1:37 pm

askewd wrote: I think the solution will be to tie it in with your options to hide filters. If a category is set to hide, that category should default to 'see everything'.

No, this will not work. When I reset the hidden columns everytime this might trigger some chaos.

I cannot test right now but try: Delete+Touch Knob of Collections, this should reset the filter of this column

moss · Post by **moss** » Mon Mar 06, 2017 1:39 pm

askewd wrote: I had times when it wouldn't allow me to press select+pad to edit the sound either. One time led to a Push2 crash message:

Push2Crashed
Can not get Property "Index" of null

Sounds like a bug. Can you reproduce that? Is there also an error in the JavaScript console?

askewd · Post by **askewd** » Mon Mar 06, 2017 2:58 pm

No, this will not work. When I reset the hidden columns everytime this might trigger some chaos.

I can't see why it should lead to chaos

It's simply the equivalent of clicking on "all devices" with the mouse in the bw browser preset device column.

The thing is, if people choose to hide filters, it's probably because they don't want to have to see - or think about them. So it could actually lead to chaos if a filter is being applied that they don't even realise. People would be like "where's my M1 piano gone!!??" So when filters are hidden, it makes sense to show all, not just some.

I cannot test right now but try: Delete+Touch Knob of Collections, this should reset the filter of this column

Even if it's reset, the numbers in brackets next to each collection are a lot smaller - again, because it's only counting the ones in the current device filter!

It's the device filter that's the main problem

When you select a synth, it then automatically applies a filter. But that's not always helpful or desired. So if you can create simple method to un-filter it, that would be amazing and appreciated.

(Of course, i can show the device filter and manually select "all devices" each time, but with workflow in mind, that's extra steps and an annoyance. )

I'll have a think about an elegant solution too.

Sounds like a bug. Can you reproduce that? Is there also an error in the JavaScript console?

This is a bug related to the drum mode issues i reported yesterday. It seems to happen a lot. I'll try to help find the exact procedure that creates the problem and report.

best
DALE

moss · Post by **moss** » Mon Mar 06, 2017 10:14 pm

Just found out that there is a conceptual problem with 64 pad drum mode: The drum pads navigated on in the display uses the 16 pad version from the normal drum mode. So, if you try to select a pad outside of this range it will not work. That's not easy to fix and might take some time.

goatgirl · Post by **goatgirl** » Tue Mar 07, 2017 3:14 am

I'm not sure if this is a bug related to the Push4Bitwig or not, however I am getting incorrect values displayed on the Push 1 when using the rotary encoders, when they are mapped to a paramter on a VST.

For instance, I create a preset page in the remote control editor and map one of the controls to a parameter on the VST, say the attack on a mod envelope. When I turn on the encoder on the Push, the displayed values do not match the value shown in Bitwig.

This problem is more obvious when setting min/max values. When I turn the encoder to the minimum, in this example 0, Push may display a 0 or more likely a random value above zero. Turning the encoder to a greater value, then back to the minimum will then display a different minimum value. Similarly turning the encoder to the max value will display random values close to the value expected and shown in BItwig.

I have tried with Lennar Digital Sylenth1 and also U-He Ace, both are 32-bit versions and both exhibit the same problem.

This appears to only affect VST's and not bitwigs own devices, though I only briefly tried the polysynth.

Tested in Beta 6 and the released version 2. Push4Bitwig 8.00
Windows 10, Push 1

moss · Post by **moss** » Tue Mar 07, 2017 7:47 am

goatgirl wrote:I'm not sure if this is a bug related to the Push4Bitwig or not, however I am getting incorrect values displayed on the Push 1 when using the rotary encoders, when they are mapped to a paramter on a VST.

For instance, I create a preset page in the remote control editor and map one of the controls to a parameter on the VST, say the attack on a mod envelope. When I turn on the encoder on the Push, the displayed values do not match the value shown in Bitwig.

This problem is more obvious when setting min/max values. When I turn the encoder to the minimum, in this example 0, Push may display a 0 or more likely a random value above zero. Turning the encoder to a greater value, then back to the minimum will then display a different minimum value. Similarly turning the encoder to the max value will display random values close to the value expected and shown in BItwig.

I have tried with Lennar Digital Sylenth1 and also U-He Ace, both are 32-bit versions and both exhibit the same problem.

This appears to only affect VST's and not bitwigs own devices, though I only briefly tried the polysynth.

Tested in Beta 6 and the released version 2. Push4Bitwig 8.00
Windows 10, Push 1

Please report to Bitwig.

sonson5 · Post by **sonson5** » Tue Mar 07, 2017 11:14 am

Hello Moss,

I downloaded the latest script for push to have it work with bitwig 2.0 and when attempting to open the run.command file I get this error:

"The file “run.command” could not be executed because you do not have appropriate access privileges."

Funny thing is when I open the old run.command file with older script it works and runs Push 2 display normally but for some reason I feel that there is something funny as sometimes things don't seem to be working right, as in pads/display vs whats really happening in bitwig's session.

Thanks!

Hassan

moss · Post by **moss** » Tue Mar 07, 2017 1:56 pm

sonson5 wrote:Hello Moss,

I downloaded the latest script for push to have it work with bitwig 2.0 and when attempting to open the run.command file I get this error:

"The file “run.command” could not be executed because you do not have appropriate access privileges."

Funny thing is when I open the old run.command file with older script it works and runs Push 2 display normally but for some reason I feel that there is something funny as sometimes things don't seem to be working right, as in pads/display vs whats really happening in bitwig's session.

Thanks!

Hassan

https://github.com/git-moss/Push4Bitwig ... ion-on-mac

goatgirl · Post by **goatgirl** » Tue Mar 07, 2017 3:24 pm

moss wrote:Please report to Bitwig.

Done, thank you.

sonson5 · Post by **sonson5** » Wed Mar 08, 2017 1:03 pm

moss wrote:
sonson5 wrote:Hello Moss,

I downloaded the latest script for push to have it work with bitwig 2.0 and when attempting to open the run.command file I get this error:

"The file “run.command” could not be executed because you do not have appropriate access privileges."

Funny thing is when I open the old run.command file with older script it works and runs Push 2 display normally but for some reason I feel that there is something funny as sometimes things don't seem to be working right, as in pads/display vs whats really happening in bitwig's session.

Thanks!

Hassan
https://github.com/git-moss/Push4Bitwig ... ion-on-mac

Thank you so much for your reply!
I had some bumps here and there and reinstalled the script and now working just fine! Just 2 more questions if I may,

-in seq drum mode is there a way to edit velocities and shift position for each pad same as in ableton? in ableton you just keep holding the pad then you can change velocity and move the note. is there a workaround to have this feature?

-Is there a way to control shuffle/swing amount from Push 2?

Thank you!

Hassan

Bitwig

KVR Audio

Ableton Push support is here