Bitwig

Bobby L'Avenir · Post by **Bobby L'Avenir** » Fri Oct 30, 2015 1:05 pm

[quote="moss"][quote="Bobby L'Avenir"]
Thanks for the update Moss, i can use the arrow keys on audio tracks now but still not send tracks?

Works fine here. Can you please exactly describe what you are doing? What view is selected?

Basically i can't scroll to a send fx track or if i select one with the mouse, push says to select a track even though it's selected and i can control it with my frontier control surface. Slecting all other track types works but not send fx tracks. This is the same for all views, clip, send, pan, volume and track?

[quote="Bobby L'Avenir"]
I'm getting jumpy behaviour with the arrow keys now mate, see the gif below. It happens every time i try scrolling through my tracks one by one, what you see in the gif is me scrolling one by one then all of a sudden it jumps through 3/4 tracks really quickly or gets stuck between the current and the next track?

I noticed that too and made some adjustments till I could not reproduce it any longer on my PC. But that is a general problem because Javascript does not provide any synchronization, therefore I can not fix this.

It works very well in version 5.01 which is what i'm using though? Is the version you tweaked until it went away the same version i tried 5.02 or is there a new update?

[quote="Bobby L'Avenir"]
Also the octaves still don't match up to the drum machine in drum mode, C2 triggers pad C1 on the drum machine, E£ on push trigger pad E2, so on and so forth?

I still cannot reproduce that. Please give a detailed description of what you are doing (starting with an empty project). Have you tried selecting Push as the only input?

Sorry maybe i should've been a bit more clear, it all works but i was just pointing out that the display on push when selecting octaves in the drum mode doesn't match the drum machine module or the bitwig piano roll. Load a blank project with just one drum machine. Go into drum mode and tap the first pad, you see it triggers C1 of the drum machine and C1 of the piano roll. Now octave down and back up to where you were and you see push says you're on octave C2 to Eb3.

Also I just noticed a similar push read read out error on the piano mode, C-1 is triggering the C1 note in the bitwig piano roll, C0 is triggering C2 in the bitwig piano roll. Shouldn't octaves C1 to C3 trigger notes C1 to C3 in bitwigs piano roll? Did you mean it to be like this in both modes Moss?

[quote="Bobby L'Avenir"]
what line can i go to so i can change the colour of a selected audio track that has no input assigned? At the moment it's a very similar colour to the mute colour below as it doesn't turn red if there's no input assigned. I don't assing inputs to my audio tracks so i can see the meters if i select that track as they don't show activity if the track is record enabled. Hope that makes sense Moss?

Not quite. There is currently no flag for no-input, therefore there is also no specific color?!

Ok, is that something bitwig need to add so i can send a feature request in? For now though is it possible to change the colour of my mute buttons, they appear bright yellow, maybe if i go dark orange or something it will be clearer to see what's selected from the button lights. What line is the colour for the mutes mate?

Cheers

moss · Post by **moss** » Sat Oct 31, 2015 5:16 pm

Bobby L'Avenir wrote: Ok, is that something bitwig need to add so i can send a feature request in?

No, the information is already in the API. But how would you visualise that on Push? There is already a lot of color coding going on...

Bobby L'Avenir wrote:For now though is it possible to change the colour of my mute buttons, they appear bright yellow, maybe if i go dark orange or something it will be clearer to see what's selected from the button lights. What line is the colour for the mutes mate?

It is in the file AbstractTrackMode.js in the function "getTrackButtonColor". There you see how much is already going on

camenzr · Post by **camenzr** » Sun Nov 01, 2015 5:08 pm

Hi Moss, hi all you programming gurus,

is it possible to add the following footswitch2 behaviour:
-first push starts recording into the next Clip available on the track selected
-another push stops the recording into the clip.

if this is not possible, would it be possible to add the same behaviour that is standard in push for ableton:
-i manually select which clip i want to record in on the push device.
-the footswitch stops the recording into the selected clip.

i prefer bitwig so much over ableton but since i do a lots of live recordings and looping in my performances and need both my hands to do so, this is a very fundamental feature for me.

Or maybe somebody could help me out with the script lines needed to do this. i'm not into java programming unfortunately.

best regards,
roman

svervs · Post by **svervs** » Sun Nov 01, 2015 9:40 pm

Seems like Push 2 was announced ...

p2.jpg

maschinelf · Post by **maschinelf** » Mon Nov 02, 2015 1:33 pm

Apparently Push 1 functionality was updated too. Which makes me wonder, are the newest firmware versions needed for the latest versions of the bitwig script to work, or it doesn't matter? I currently have the firmware that came with 9.2 but sold my Live Suite license, so I don't have a way of updating in future.

EDIT: apparently Push 1 firmware has not been updated with Live 9.5. I am still curious though, is it necessary to stay on the latest firmware for it to work properly as the Bitwig script gets updates in the future, or it doesn't matter?

TristanMendoza · Post by **TristanMendoza** » Mon Nov 02, 2015 3:48 pm

Push 2 looks pretty sick. I would like it, but how would the screen work with Bitwig?

thetechnobear · Post by **thetechnobear** » Mon Nov 02, 2015 6:34 pm

TristanMendoza wrote:Push 2 looks pretty sick. I would like it, but how would the screen work with Bitwig?

we have been discussing this here

looks like Push2 display will not be backwards compatible with Push1, so Push4Bitwig in its current form would not work... but its early days to say what interaction with the Push2 display will be possible.
(looks currently like you have to render the graphics and send directly to the push via USB.. but no details on protocol yet, except I have a quote from ableton dev saying protocol is pretty simple)

moss · Post by **moss** » Mon Nov 02, 2015 6:36 pm

camenzr wrote:Hi Moss, hi all you programming gurus,

is it possible to add the following footswitch2 behaviour:
-first push starts recording into the next Clip available on the track selected
-another push stops the recording into the clip.

if this is not possible, would it be possible to add the same behaviour that is standard in push for ableton:
-i manually select which clip i want to record in on the push device.
-the footswitch stops the recording into the selected clip.

i prefer bitwig so much over ableton but since i do a lots of live recordings and looping in my performances and need both my hands to do so, this is a very fundamental feature for me.

Or maybe somebody could help me out with the script lines needed to do this. i'm not into java programming unfortunately.

best regards,
roman

Look at the settings of the script in the preferences dialog. There you can set the behaviour of Footswitch 2. I guess "Clip based looper" is the option you are looking for.

moss · Post by **moss** » Mon Nov 02, 2015 6:40 pm

maschinelf wrote:Apparently Push 1 functionality was updated too. Which makes me wonder, are the newest firmware versions needed for the latest versions of the bitwig script to work, or it doesn't matter? I currently have the firmware that came with 9.2 but sold my Live Suite license, so I don't have a way of updating in future.

EDIT: apparently Push 1 firmware has not been updated with Live 9.5. I am still curious though, is it necessary to stay on the latest firmware for it to work properly as the Bitwig script gets updates in the future, or it doesn't matter?

I doubt that there will be much upates coming for Push 1 in the future. However, you can always use the demo or lite version to do the update.

TeotiGraphix · Post by **TeotiGraphix** » Mon Nov 02, 2015 6:46 pm

moss wrote:
maschinelf wrote:Apparently Push 1 functionality was updated too. Which makes me wonder, are the newest firmware versions needed for the latest versions of the bitwig script to work, or it doesn't matter? I currently have the firmware that came with 9.2 but sold my Live Suite license, so I don't have a way of updating in future.

EDIT: apparently Push 1 firmware has not been updated with Live 9.5. I am still curious though, is it necessary to stay on the latest firmware for it to work properly as the Bitwig script gets updates in the future, or it doesn't matter?
I doubt that there will be much upates coming for Push 1 in the future. However, you can always use the demo or lite version to do the update.

When I installed 9.5, it asked if I wanted to update the firmware, I can't remember which version right now.

Mike

thetechnobear · Post by **thetechnobear** » Mon Nov 02, 2015 7:16 pm

TeotiGraphix wrote:
moss wrote:
maschinelf wrote:Apparently Push 1 functionality was updated too. Which makes me wonder, are the newest firmware versions needed for the latest versions of the bitwig script to work, or it doesn't matter? I currently have the firmware that came with 9.2 but sold my Live Suite license, so I don't have a way of updating in future.

EDIT: apparently Push 1 firmware has not been updated with Live 9.5. I am still curious though, is it necessary to stay on the latest firmware for it to work properly as the Bitwig script gets updates in the future, or it doesn't matter?
I doubt that there will be much upates coming for Push 1 in the future. However, you can always use the demo or lite version to do the update.
When I installed 9.5, it asked if I wanted to update the firmware, I can't remember which version right now.

Mike

odd, didnt ask me... I've still got 1.16 installed... (from live 9.2)
what firmware version do you now have?

EDIT: tried to force ableton to update firmware, and was still offering 1.16...
did you have 9.2 installed before? perhaps you had the older firmware from 9.1?

maschinelf · Post by **maschinelf** » Mon Nov 02, 2015 7:35 pm

So the current version of Push4Bitwig requires firmware 1.16? I think that's what I got, cause if I remember correctly, I had Live 9.2 installed prior to selling my license. Is there a way to check the firmware currently installed? I searched on google but couldn't find an answer, and it seems the only way to know is when Live indicates that an update is required.

TeotiGraphix · Post by **TeotiGraphix** » Mon Nov 02, 2015 7:40 pm

thetechnobear wrote:
TeotiGraphix wrote:
moss wrote:
maschinelf wrote:Apparently Push 1 functionality was updated too. Which makes me wonder, are the newest firmware versions needed for the latest versions of the bitwig script to work, or it doesn't matter? I currently have the firmware that came with 9.2 but sold my Live Suite license, so I don't have a way of updating in future.

EDIT: apparently Push 1 firmware has not been updated with Live 9.5. I am still curious though, is it necessary to stay on the latest firmware for it to work properly as the Bitwig script gets updates in the future, or it doesn't matter?
I doubt that there will be much upates coming for Push 1 in the future. However, you can always use the demo or lite version to do the update.
When I installed 9.5, it asked if I wanted to update the firmware, I can't remember which version right now.

Mike
odd, didnt ask me... I've still got 1.16 installed... (from live 9.2)
what firmware version do you now have?

EDIT: tried to force ableton to update firmware, and was still offering 1.16...
did you have 9.2 installed before? perhaps you had the older firmware from 9.1?

I had 9.2 installed but I don't remember updating the firmware. I updated firmware on this 9.5, like I said I can't remember what version, I thought it said 1.7.

But when I try to force it, I get this ridiculous popup. Makes no sense, I am just leaving it right now and not pressing OK.

Push.JPG

Mike

svervs · Post by **svervs** » Wed Nov 04, 2015 10:54 am

While the Push2 seems quite nice, I don't think it's for me so far.
What I was thinking about is, getting a second Push(1) from eBay.

So my question is, how would 2 of them behave together? Would they be working independly?

e.g.

Push#1: Clip launching
Push#2: Playing notes
I think this should work?

Not sure about this:
Push#1: Working on Track X Clip X
Push#2: Working On Track Y Clip Y
Would one Push always mirror the clip selection I do with the other?

Thanks for any insights, assumptions, ...!

TeotiGraphix · Post by **TeotiGraphix** » Wed Nov 04, 2015 10:59 am

svervs wrote:While the Push2 seems quite nice, I don't think it's for me so far.
What I was thinking about is, getting a second Push(1) from eBay.

So my question is, how would 2 of them behave together? Would they be working independly?

e.g.

Push#1: Clip launching
Push#2: Playing notes
I think this should work?

Not sure about this:
Push#1: Working on Track X Clip X
Push#2: Working On Track Y Clip Y
Would one Push always mirror the clip selection I do with the other?

Thanks for any insights, assumptions, ...!

It shouldn't since if you have them hooked up using different port in/out I would think Bitwig tracks each track/device/clip banks as individual.

I haven't actually tested this but it's a theory.

Mike

Bitwig

KVR Audio

Ableton Push support is here