Bitwig

reflex58 · Post by **reflex58** » Thu Nov 12, 2015 9:00 pm

Just wanted to chime in, I have Push 1 and just got Push 2.
With the existing Push4Bitwig script there is some fictionality
There is of course at this point no visual feedback on the new display
A good deal of the features are working
thus far I tested record, play, metronome, volume, pan note view (some views are working drum etc.. and the clip launcher appears to be working.
I will update as i test more, sure hope we can get the visual end of this working

TeotiGraphix · Post by **TeotiGraphix** » Thu Nov 12, 2015 10:35 pm

reflex58 wrote: I will update as i test more, sure hope we can get the visual end of this working

Read this thread again. Even if we could get the screen working, that is no small task and it would be very primitive. It all boils down to a bunch of details that are not known right now.

Mike

reflex58 · Post by **reflex58** » Fri Nov 13, 2015 12:15 am

Mike I am aware of that I was just pointing out that there is some functionality with the existing script just know visual feedback

Litex · Post by **Litex** » Fri Nov 13, 2015 6:44 pm

Has anybody seen this yet? Seems quite promising!

https://vimeo.com/145661291

http://sigabort.co/p2d

Cyoon · Post by **Cyoon** » Fri Nov 13, 2015 6:53 pm

maybe unrelated but maybe of interest
there is a way to display a waveform in lemur with canvas by using a max msp patch.

https://liine.net/en/products/lemur/pre ... ning-pack/

maybe there would need to be smth like this max thing in Bitwig to make it work also in push?

donstar · Post by **donstar** » Fri Nov 13, 2015 6:59 pm

Litex wrote:Has anybody seen this yet? Seems quite promising!

https://vimeo.com/145661291

http://sigabort.co/p2d

Indeed. This looks very promising.

moss · Post by **moss** » Fri Nov 13, 2015 11:03 pm

Yesss!

TeotiGraphix · Post by **TeotiGraphix** » Sat Nov 14, 2015 12:13 am

Litex wrote:Has anybody seen this yet? Seems quite promising!

https://vimeo.com/145661291

http://sigabort.co/p2d

Nice, if I recall earlier in this conversation an Ableton dev said it's not that hard to hook into the display. I guess this proves his point.

Mike

thetechnobear · Post by **thetechnobear** » Sat Nov 14, 2015 12:35 am

It will be a very simple max external, written to use the usb protocol

Ive pretty much worked out the details myself too, its simple enough, just do a USB trace.

as far as I can tell, you send the raw graphics data to the Interface 0 ( Push Display) use output endpoint 1.
each display packet is made up of
- a 16 byte message over the bulk interface , containing : ef cd ab 89 00 00 00 00
- then graphics data as 20 x 16384 byte messages.

I think this 'protocol' should be open source, hopefully this guy will make it open... otherwise I'll see if I can get a chance to detail the remaining bits of the puzzle. Ive not had a chance to check the graphics format yet, but it looks like its just raw pixel data... so really just a matter of sending some data to determine row/column resolution to get placement, and then check colour depth... id guess 8 or 16 bit?
(only thing I've noticed , when casually looking, is there appears to be repeating patterns every 0x200 bytes, which Id have thought mean thats the line size but 512 pixels seems a bit small for the Push2 display)

(actually this guy will be doing this any way, as his jitter examples will tell you this)

ceasless · Post by **ceasless** » Sat Nov 14, 2015 5:42 pm

Could it be a "segment" marker? The original Push was segmented in 4, but I don't recall there being any formal recognition / affordance to that in the sysex commands. It would have actually been a whole lot handier if it had. Took a while for me to get the display math right when I was working on Push support in Usine Hollyhock. I did finally get it working, but that was around the time I started to really dig into Bitwig so I never finished the full patch I had envisioned.

Concerning what we know: so the QML app provides Live some API that they (presumably) chat to via Python, which then creates the raw graphics messages and dispatches them to the Push 2? This would mean the Max external would be more or less 'replacing' the QML app in the chain?

Crackbaby · Post by **Crackbaby** » Mon Nov 16, 2015 3:02 pm

Do you think Akai's new MPC Touch could be Bitwigized? Not sure it would make any sense though

donstar · Post by **donstar** » Tue Nov 24, 2015 2:43 pm

https://www.facebook.com/sigabort/video ... 810680243/

lem8r · Post by **lem8r** » Wed Nov 25, 2015 12:25 pm

I think Bitwig goes it's own way with Touch interface omitting any hardware controller between Bitwig and user.
Touch display + midi keyboard or pads is way better than tiny display and mapped knobs on Push 2, imo

thetechnobear · Post by **thetechnobear** » Wed Nov 25, 2015 6:51 pm

Sigabort has got some nice stuff coming along ... also check out net147, https://github.com/net147/Push2Qml

@lem8r, touch interface - nah i disagree, they lack tactile feedback... this is why many turn to hardware controllers...
its the same reason, I find iPad interfaces 'limiting' in satisfaction.
Of course the Push (& Maschine) have limits, which I think makes them more suitable for Live/Jamming, to hold you 'in the zone', if you want much more in-depth editing, then the touch interface might starting coming into its own. (though frankly, at that stage I'm happy to return to my Mac, with a bigger screen/power etc, though others may feel differently)

FastTriggerFish · Post by **FastTriggerFish** » Wed Nov 25, 2015 7:01 pm

I agree that touch interfaces are not very satisfying to use.
I've got a large acer touchscreen which is setup in my keyboard rack so I can edit vsts while playing. It works very well for large GUIs, but I still much prefer using my nektar panorama controller in Cubase, some synths have got truly excellent mappings in there.

Bitwig

KVR Audio

Can't wait to see the new Push being integrated into Bitwig