Bitwig

stamp · Post by **stamp** » Wed Sep 10, 2014 2:16 pm

wow!! great job man...

contrast · Post by **contrast** » Wed Sep 10, 2014 7:08 pm

If I remember right, someone did make a Lemur template that emulates a Push. Have you tried just using that template with the Push script?

carlosjcuevasm · Post by **carlosjcuevasm** » Wed Sep 17, 2014 11:43 pm

Dont know where, but I think I saw one of the wise guys here talking about a possible TouchOSC Layout simulating Push. Am I right?

Orga · Post by **Orga** » Tue Sep 30, 2014 1:36 am

Edit 2: I accidentally deleted all channels in a Bitwig project (complete empty project) and then exited bitwig and push was 'hanging' graphically on the last thing i was doing inside of bitwig (is this normal?)

Edit: Figured it out

Love what you've done with LEDs - speaking of LEDS, what do you recon the chances are of figuring out a way to tell the LEDs to becomes a sort VU Meter - i've seen it done with this push script called PXT.

Hello!

Wow the functionally that this script offers is brilliant (in some respects more effective and better than default script for live)

that said, I haven't actually tried it yet cause I don't know how to install it

- I can't find any installation documentation? Is it just a question of dropping it inside of Bitwig (show package contents) within a folder?

Ta.

ThomasHelzle · Post by **ThomasHelzle** » Tue Sep 30, 2014 9:34 am

You install it in your user directory under documents/Bitwig Studio/Controller Scripts - should be a similar path for all OS'

Installing inside the package only applies if you replace factory scripts, which should be avoided where possible since you would need to install it after each update.

Cheers,

Tom

moss · Post by **moss** » Tue Sep 30, 2014 10:08 am

Detailed Installation instructions are in the Github Wiki linked from the first entry oft this thread, the download on my Homepage and Github.

thetechnobear · Post by **thetechnobear** » Sat Oct 04, 2014 10:05 pm

hi,
great work on this...

one question, I'm using 1.0.15 and 3.33 (mac os) , and I cannot get the device button to work, I can see the menu to select common etc, but none of the encoders do anything. how is this suppose to work?
thanks
Mark

TeotiGraphix · Post by **TeotiGraphix** » Sat Oct 04, 2014 10:17 pm

thetechnobear wrote:hi,
great work on this...

one question, I'm using 1.0.15 and 3.33 (mac os) , and I cannot get the device button to work, I can see the menu to select common etc, but none of the encoders do anything. how is this suppose to work?
thanks
Mark

Hi,

You press the Device button for the Common device bank of 8 and page it. if you press the Device button again, you select Common, Macro, User etc.

If you do not have macros or user nothing will show.

You need to make sure and select a device in the UI(this is something that is getting fixed). Not all the time the instrument or effect device is selected and you can't see anything.

Make sure you download from moss's web site right now as the GitHub is using 1.1 API and is probably broken in 1.0.14.

Basically, make sure you have a device selected in the UI where it shows a white dashed outline.

Mike

thetechnobear · Post by **thetechnobear** » Sat Oct 04, 2014 11:07 pm

thanks... it was the dotted border that was the problem
it seems that when you add a new instrument to a track, the first device is not automatic selected,
and it appears there is no way on the push to select it.
oddly... once you have selected it, it appears you then get an option go to the next device in the chain.

so looks like its just adding the instrument thats the issue, perhaps this is a newer issue?
(would be nice to be able to use the push,without having to grab the mouse to select things)

TeotiGraphix · Post by **TeotiGraphix** » Sat Oct 04, 2014 11:21 pm

thetechnobear wrote:thanks... it was the dotted border that was the problem
it seems that when you add a new instrument to a track, the first device is not automatic selected,
and it appears there is no way on the push to select it.
oddly... once you have selected it, it appears you then get an option go to the next device in the chain.

so looks like its just adding the instrument that's the issue, perhaps this is a newer issue?
(would be nice to be able to use the push,without having to grab the mouse to select things)

It's not our limitation in programming, its how Bitwig handles selection and they are working on it for 1.1.

I feel your pain but, its not yet fixed in your version. The whole controller/device selection has been changed in 1.1 (nested device will work eventually as we get the bugs worked out in beta 1.1).

Mike

ThomasHelzle · Post by **ThomasHelzle** » Sun Oct 05, 2014 10:46 am

Any specific reason you don't use the primary device based on the cursor track? That is always available without the user first having to select something and is more reliable and logical most of the time IMO.

Cheers,

Tom

TeotiGraphix · Post by **TeotiGraphix** » Sun Oct 05, 2014 11:49 am

ThomasHelzle wrote:Any specific reason you don't use the primary device based on the cursor track? That is always available without the user first having to select something and is more reliable and logical most of the time IMO.

Cheers,

Tom

Tom, we are.

I wrote the post when i was getting off the computer, so I may have guessed at something that was wrong.

i just tested in 1.1, added a Track, track selected. Switched to device mode on controller, right clicked and added a Polysynth. The synth was selected in the DAW and the device display updated correctly on the Push.

So, I don't actually know what the OP is referring to.

Sometimes though when you are navigating the device losses foucs. Maybe the problem is at the moment i don't know of a way to force a device selection at certain states. Need to research this further, maybe moss can chime in and say what I am not seeing.

Mike

ThomasHelzle · Post by **ThomasHelzle** » Sun Oct 05, 2014 12:03 pm

So far I was under the impression that a cursor track based primary device is always valid (if there is a device at all) which is why I generally recommend it. If you can provide steps to produce such a situation where it's not, we could look into it. I never encountered this I think.

Cheers,

Tom

TeotiGraphix · Post by **TeotiGraphix** » Sun Oct 05, 2014 12:09 pm

ThomasHelzle wrote:So far I was under the impression that a cursor track based primary device is always valid (if there is a device at all) which is why I generally recommend it. If you can provide steps to produce such a situation where it's not, we could look into it. I never encountered this I think.

Cheers,

Tom

Ok,

Luckily I just found a way it doesn't work.(I am not going crazy)

If you drag say a Sampler from the Browser into the track list, drop. the sampler is added but NOT selected, does not have a white dotted outline, thus on the Push there is no device selection and says Please select a Device...

You have to manually click on the device in Bitwig to get a current device pointer.

Mike

TeotiGraphix · Post by **TeotiGraphix** » Sun Oct 05, 2014 12:10 pm

repost...

Bitwig

KVR Audio

Ableton Push support is here