Bitwig

pdxindy · Post by **pdxindy** » Sat Sep 26, 2015 11:19 pm

sl1914 wrote:
pdxindy wrote: Do you have the latest firmware from Ableton?
It should be the latest.
I never had these freeze problems before beta10.

You said you just downloaded the latest Push4bitwig script to something changed besides Beta 10

sl1914 · Post by **sl1914** » Sun Sep 27, 2015 6:52 am

pdxindy wrote:
sl1914 wrote:
pdxindy wrote: Do you have the latest firmware from Ableton?
It should be the latest.
I never had these freeze problems before beta10.
You said you just downloaded the latest Push4bitwig script to something changed besides Beta 10

Yes, but I tried beta10 and my older script first. When I saw the freezing problem I downloaded the latest script to make sure I have latest versions of everything. Didn't notice any improvement.

TristanMendoza · Post by **TristanMendoza** » Mon Sep 28, 2015 1:31 am

I can't get Push to work in beta 9 or 10. Is this a script problem? I downloaded the last one when I was experiencing this with beta 9, but obviously no luck.

moss · Post by **moss** » Mon Sep 28, 2015 7:27 am

TristanMendoza wrote:I can't get Push to work in beta 9 or 10. Is this a script problem? I downloaded the last one when I was experiencing this with beta 9, but obviously no luck.

The latest from GitHub works fine with Beta 10. Make sure that you really replaced the old version.
Do you get any errors in the script console?

twumpy · Post by **twumpy** » Mon Sep 28, 2015 6:51 pm

I'm getting an issue that devices don't react to knobs (or just zeros the values). It seems to happen when I go to device->direct and play with the device settings through there. I get it with all VSTs I have, and if it happens, Polysynth or FM devices won't work either. Happened with beta 10& 11 and few latest revisions of the script (downloaded latest one 10 min ago.

Edit: seems that I don't necessarily need to use VST for the issue to occur. The Direct page just doesn't seem to work for me.

moss · Post by **moss** » Mon Sep 28, 2015 8:05 pm

twumpy wrote:I'm getting an issue that devices don't react to knobs (or just zeros the values). It seems to happen when I go to device->direct and play with the device settings through there. I get it with all VSTs I have, and if it happens, Polysynth or FM devices won't work either. Happened with beta 10& 11 and few latest revisions of the script (downloaded latest one 10 min ago.

Edit: seems that I don't necessarily need to use VST for the issue to occur. The Direct page just doesn't seem to work for me.

Yes, I can reproduce that. Will report it to Bitwig.

twumpy · Post by **twumpy** » Tue Sep 29, 2015 2:39 pm

Danke schön!

SB-SIX · Post by **SB-SIX** » Wed Sep 30, 2015 10:04 pm

Is there any way to map a parameter of choice to a rotary encoder in 1.2? On bitwig 1.1.11 I could do this on the pan/send mode of push (right click the control and choose add controller mapping, then turn the encoder), but now that's not possible anymore.

pdxindy · Post by **pdxindy** » Wed Sep 30, 2015 10:36 pm

The Push encoders are all wonky right now... none of the device macros are currently working

moss · Post by **moss** » Thu Oct 01, 2015 7:41 am

pdxindy wrote:The Push encoders are all wonky right now... none of the device macros are currently working

I noticed that too.
Will need to check if this is Bitwig bug or not.

moss · Post by **moss** » Thu Oct 01, 2015 7:43 am

futuresproof wrote:
stamp wrote: How about the issue with the Virus?
I had a play around with this and found that they same thing happens using standard midi cables if the virus is set to use polypressure as one of the midi control "Page" options in edit mode. If you set "Page A" to controller data and "Page B" to sysex it works as normal. The trouble is you cant seem to change this setting when the plugin is used.

I tried converting ploy pressure to CC in the push script but it just set the CC and the poly pressure so a filter in the script might be the way to go. I might try using midiox and some virtual midi ports to filter this out to be sure.

Regarding the Poly-Aftertouch problem: I recently noticed that Poly-Aftertouch was always sent to Bitwig even if you translated it in the settings. I found a workaround to stop that (latest checkin), which means you can now safely use it with the Virus, e.g. transform it to CC 0 or turn it off.

futuresproof · Post by **futuresproof** » Thu Oct 01, 2015 3:33 pm

Cheers moss I will check this out tonight.

futuresproof · Post by **futuresproof** » Thu Oct 01, 2015 3:49 pm

moss wrote:
futuresproof wrote:Anyone tried using the mapping mode in 1.2 beta to map the push touchstrip to a macro?

When i try this instead of receiving the midi CC that you set in push4bitwig it maps the note c-1.

Plugins that that have midi learn work fine I just cant map in bitwig
Try if it works when you select Push as the only midi input and not All.

I tried this but it made no difference unfortunately.

Cheers

Chris.

moss · Post by **moss** » Fri Oct 02, 2015 6:57 pm

moss wrote:
pdxindy wrote:The Push encoders are all wonky right now... none of the device macros are currently working
I noticed that too.
Will need to check if this is Bitwig bug or not.

The whole control of the direct parameters (which contain now also the macros) is broken. I reported it to Bitwig.

moss · Post by **moss** » Fri Oct 02, 2015 6:59 pm

futuresproof wrote:Anyone tried using the mapping mode in 1.2 beta to map the push touchstrip to a macro?

When i try this instead of receiving the midi CC that you set in push4bitwig it maps the note c-1.

Plugins that that have midi learn work fine I just cant map in bitwig

The ribbon sends a midi note when you touch it. If you touch it first you can map it but then it does not control the value. I reported the later one to Bitwig.

Bitwig

KVR Audio

Ableton Push support is here