Bitwig

stamp · Post by **stamp** » Sat Jan 03, 2015 5:00 pm

moss wrote: Try setting the input to Ableton Push instead of All Inputs. There is (still) a bug in Bitwig which erratically sends also the raw input to the output. Maybe that's the cause.

Hi moss,
done! but doesn't work.
I'm trying to understand how midiox works. I'll report back later.

stamp · Post by **stamp** » Mon Jan 05, 2015 9:50 pm

Hi guys,
sorry, but i give up. Now i can't access parameters of my vst. Perhaps there is a problem on my side. Don't know. For now I'll stick with Live. See you in the future!

All the best!!

pboy · Post by **pboy** » Thu Jan 08, 2015 2:00 pm

Cool! I just tried the script and have a few questions:

When touching the rotary encoder knobs on the Push now note ons are sent. This is typically used in Ableton Live to make "simply touching the encoder select the target for where you want to change a parameter value by twisting the knob".

Is there a way in Bitwig to filter out those low notes?
(In Logic I can mute them in the Environment before the Sequencer Input by cabling the specific Push output into a dummy object that isn't cabled anywhere further)

Or maybe the Push script can be tweaked to deal with that?

moss · Post by **moss** » Fri Jan 09, 2015 8:01 am

pboy wrote:Cool! I just tried the script and have a few questions:

When touching the rotary encoder knobs on the Push now note ons are sent. This is typically used in Ableton Live to make "simply touching the encoder select the target for where you want to change a parameter value by twisting the knob".

Is there a way in Bitwig to filter out those low notes?
(In Logic I can mute them in the Environment before the Sequencer Input by cabling the specific Push output into a dummy object that isn't cabled anywhere further)

Or maybe the Push script can be tweaked to deal with that?

This is a bug in Bitwig which is hard to reproduce, therefore not fixed yet. It occurs sometimes when you have set the Input to "All Inputs". If you set the Input to only Push it goes away.

hibidy · Post by **hibidy** » Fri Jan 09, 2015 8:29 am

I have to say that I don't fully appreciate the integration with push/bitwig like some smarter folk.......but what I do appreciate is that there is a relationship that is constantly being worked upon.

Thank you for that!

freakydj · Post by **freakydj** » Thu Jan 15, 2015 6:25 pm

Hi,

I was trying to reproduce some controls into the drum sequence mode like on this tutorial video but I was not available:

- Repeat fonction (at 1:55min)
- Move a note forward or backward (at 3:00 min)

can you let me know if it's available with this script, thank you

moss · Post by **moss** » Fri Jan 16, 2015 7:37 am

freakydj wrote:- Repeat fonction (at 1:55min)
- Move a note forward or backward (at 3:00 min)

can you let me know are available with this script, thank you

That's sadly some of the (less and less) deficiencies of the API. I would love to see that too.
But Bitwig is aware of my wishlist

https://github.com/teotigraphix/Framework4Bitwig/issues

taoyoyo · Post by **taoyoyo** » Fri Jan 16, 2015 2:33 pm

Hey Moss,

Do you know if improving the API to allow the features mentioned above (and more) is 'high on the list' (of those many things to implement in BWS) for the folk at Bitwig?

For instance I know you said that the current 'Parameter Pages' is not working because of issues at Bitwig's end and should be fixed in 1.2.

Would it help 'the scriptor's cause' if some of us dropped Bitwig FR's in this area to help push these API improvements or do you think they are already 'on the case' and don't need any 'prodding' that there are (potentially?) a lot of users to whom this is important (not just for the Push script but Mike's M4B and others)?

Cheers,

Alan

moss · Post by **moss** » Fri Jan 16, 2015 3:05 pm

taoyoyo wrote:Do you know if improving the API to allow the features mentioned above (and more) is 'high on the list' (of those many things to implement in BWS) for the folk at Bitwig?

I can't comment on their roadmap (because I do not know it). I can only tell you that all of it is noted and on their list but there is a lot of high-prio stuff on the list

taoyoyo wrote:Would it help 'the scriptor's cause' if some of us dropped Bitwig FR's in this area to help push these API improvements or do you think they are already 'on the case' and don't need any 'prodding' that there are (potentially?) a lot of users to whom this is important (not just for the Push script but Mike's M4B and others)?

I would suggest to wait after NAMM because you won't get much response before that.

taoyoyo · Post by **taoyoyo** » Fri Jan 16, 2015 3:37 pm

Thanks Moss... I figured they might have a lot of stuff on their overall 'to-do-list'.

Waiting until after NAMM seems like a plan!

Have a good one,

Alan

freakydj · Post by **freakydj** » Fri Jan 16, 2015 4:32 pm

Thank you Moss for your answers, I hope Bigwig will improve the API in 1.2

Raffi · Post by **Raffi** » Tue Jan 20, 2015 7:16 pm

Hey guys,

Don't know if this is a known thing, but at current it's almost impossible working in clip view.

When changing tracks it always force select the first scene clip, which makes it impossible to select two clips or copy a clip to another track. And also when I want to edit a clip I often have to double click to get focus back as it jumps to the first scene. When turning off Push everything works as normal.

Aside from that, I am still getting green pads when selecting a track in another bank. I have to select another track within the bank and then go back to be able to play. Also still hanging loops betweens selecting track, only now it won't get stuck, just have to wait / clicking other tracks to get it out of it's loop.

While this is a great script, these things get very frustrating after while...

I'm using the latest (stable version) script - Bitwig 1.15 RC1 on OSX.

Hope you can help!

Best,
Raffi

Cyoon · Post by **Cyoon** » Tue Jan 20, 2015 7:24 pm

maybe try the version on GitHub then?

Raffi · Post by **Raffi** » Thu Jan 22, 2015 9:45 am

Suloo wrote:maybe try the version on GitHub then?

There are no changes in the latest version regarding this issue.

What I did find out is that this selecting first scene behaviour only occurs when having more than 8 tracks, so when it has to switch track banks. The first bank with 8 tracks will always behave normal.

TeotiGraphix · Post by **TeotiGraphix** » Thu Jan 22, 2015 11:06 am

Raffi wrote:
Suloo wrote:maybe try the version on GitHub then?
There are no changes in the latest version regarding this issue.

What I did find out is that this selecting first scene behaviour only occurs when having more than 8 tracks, so when it has to switch track banks. The first bank with 8 tracks will always behave normal.

There has always been a bug in the bank switching past track 8.

I know this thread is long but it probably has been talked about by myself a couple of times. When I was working on it with Moss, I knew it existed because there is a "wrap" bank hack in the code because it's not properly implemented on Bitiwg's side.

I don't really work on the Push code atm but this timer code is in the framework and affects Maschine4Bitwig as well. We will need to find a proper solution on Bitwig's end.

Bitwig

KVR Audio

Ableton Push support is here