Bitwig

TeotiGraphix · Post by **TeotiGraphix** » Thu Aug 14, 2014 5:07 pm

ThomasHelzle wrote:Hm - not sure if there is a kind of limit to the number of timers maybe?
Would it make sense to only have one timer going, write the value-while-wiggling into the same variable where it is retrieved when the time is up, so it doesn't accumulate?
Didn't analyse the script, just a quick hunch

Basically: one timer, flags for dirty or not, if dirty -> retrieve value when timer is up, rinse and repeat. ?

Cheers,

Tom

We only have one timer and we use a dirty flag when the timer is flushed (blocks any other interval calls).

I think we are trying to be in two places at once, in the future I think we need to get out of the flush() call of global Bitwig and just manage our own complete invalidation/paint system.

Mike

ThomasHelzle · Post by **ThomasHelzle** » Thu Aug 14, 2014 5:42 pm

Ah - I see.
Well, if you can create a clear case where the JS Engine goes bonkers I'd be happy to file a bug, but this sounds more like a possible collision between different things then?

If I understood Claes correctly, flush needs not be used.
The observers already do data reduction and combining.
So if you have your own timer going, flush may add little to your system or even be in the way with it firing on each observer call...
I could imagine that you could even work with two or three queues, slow, medium, fast for different events.
flush feels more like a general purpose solution that may not be the best for complex scripts like push4bitwig.

Cheers,

Tom

moss · Post by **moss** » Fri Aug 15, 2014 7:15 am

ThomasHelzle wrote:Well, if you can create a clear case where the JS Engine goes bonkers I'd be happy to file a bug, but this sounds more like a possible collision between different things then?

As said above: Set the refresh rate in framework\core\AbstractControlSurface.js in line 101 from 70 back to 5 with the Novation Remote script. Then turn the volume knob quickly.
I guess you can provoke do the same if you set the rate to 1 and use the Push script.

ThomasHelzle · Post by **ThomasHelzle** » Fri Aug 15, 2014 8:27 am

I got that, I just wasn't sure from your other post if that is indeed JS related or maybe some kind of endless loop inside your script or an Midi overload of the MK2 itself. I created something like that myself a while ago

I may have a chance to test the script today in the office.

Cheers,

Tom

moss · Post by **moss** » Fri Aug 15, 2014 12:19 pm

It is time for a new release! TeotiGraphix & Moss present you 3.2!

Get the latest stable release from: http://www.mossgrabers.de/Software/Push/Push.html
The version in GitHub might always be in an alpha or beta state, you have been warned!

https://github.com/git-moss/Push4Bitwig

* Hold Session while in Note mode to switch temporarily to Session mode
* Knobs change values now by how fast you turn them.
* If no track is selected a text is now displayed.
* Decreased refresh rate of display. Improves responsiveness.
* Bugfix: Frame and Device mode had incorrect button colors due to last color refactor.
* Bugfix: Master Knob temporary mode behavior not returning to all previous modes.
* Bugfix: Full maximum value range of knobs might not have been reached.

Enjoy!

Cyoon · Post by **Cyoon** » Mon Aug 25, 2014 12:08 pm

Im writing for a friend here, since he has no internet connection currently but might be interested in Bitwig. He tried the script with his push and the Bitwig demo and claimed that the Drum Modus isn`t working, and also he cannot select the vst instruments in clip view with the controller.

Is this covered in this thread or a known issue or should it work and he has overseen something?

cheers

moss · Post by **moss** » Mon Aug 25, 2014 12:43 pm

Suloo wrote:Drum Modus isn`t working,

Since we can not detect if the track is intended to be a "drum track" you have to activate the drum mode by pressing the Shift+Note buttons.

Suloo wrote:and also he cannot select the vst instruments in clip view with the controller.

What do you mean? Clip view is not related to VST instruments. You need to enter the device mode. To see the VST parameters on the Push you first have to map them in the VST device. Search the forum for an explanation of the the correct way to do it because there are some flaws there.

Cyoon · Post by **Cyoon** » Mon Aug 25, 2014 7:07 pm

cool thx!

sardaukar · Post by **sardaukar** » Sun Aug 31, 2014 3:45 pm

moss wrote:It is time for a new release! TeotiGraphix & Moss present you 3.2!

Get the latest stable release from: http://www.mossgrabers.de/Software/Push/Push.html
The version in GitHub might always be in an alpha or beta state, you have been warned!
https://github.com/git-moss/Push4Bitwig

* Hold Session while in Note mode to switch temporarily to Session mode
* Knobs change values now by how fast you turn them.
* If no track is selected a text is now displayed.
* Decreased refresh rate of display. Improves responsiveness.
* Bugfix: Frame and Device mode had incorrect button colors due to last color refactor.
* Bugfix: Master Knob temporary mode behavior not returning to all previous modes.
* Bugfix: Full maximum value range of knobs might not have been reached.

Enjoy!

awesome

moss · Post by **moss** » Mon Sep 01, 2014 5:54 pm

It is time for a new release! 3.3 is out!

Get the latest stable release from: http://www.mossgrabers.de/Software/Push/Push.html
The version in GitHub might always be in an alpha or beta state, you have been warned!

https://github.com/git-moss/Push4Bitwig

Lot's of goodies here:

* Press Track button twice to toggle between editing of normal tracks and effect tracks. To toggle VUs press now Shift+Track.
* Playing sequencer notes are now reflected on the Play and Drum grid.
* The names of the Send tracks are now displayed.
* Non existing track columns are now fully blank.
* Pan & Send button only steps through existing sends tracks.
* Hold Select + Drum Rack pad to select its notes without triggering the pad (Drum View)
* Hold Delete + Drum Rack pad to delete the midi notes of the current clip on that 'pad'.
* 8 track window now scrolls to the newly selected track (selected in Bitwig).
* Memory savings due to change from inline functions to class functions.
* Bugfix: Hold the delete key and touch a knob to reset its value in Device Mode was broken.

Enjoy!

Raffi · Post by **Raffi** » Tue Sep 02, 2014 9:06 am

sardaukar wrote:* 8 track window now scrolls to the newly selected track (selected in Bitwig).

Been waiting for this one! So glad to see this working now. Great job, thanks!!

xbitz · Post by **xbitz** » Thu Sep 04, 2014 6:26 pm

I'd also like to say a BIG THX for this, btw the udemy course is free now ... https://www.udemy.com/music-theory-with ... eton-push/ it's a music theory based one not about how to use it (hope it's not a repost

)

billcarroll · Post by **billcarroll** » Thu Sep 04, 2014 6:46 pm

xbitz wrote:I'd also like to say a BIG THX for this, btw the udemy course is free now ... https://www.udemy.com/music-theory-with ... eton-push/ it's a music theory based one not about how to use it (hope it's not a repost )

A big thanks to @moss for all of the work on Bitwig and Push.

Also, thanks for posting the free "music-theory-with-the-ableton-push" course.

moss · Post by **moss** » Sun Sep 07, 2014 4:34 pm

Half a best is on the run: Version 3.33!

Get it from: http://www.mossgrabers.de/Software/Bitwig/Bitwig.html

- Shift+Small Knob 1: Fine adjust tempo
- Bugfix: Added missing implementation of light states of cursors in Play mode.
- Bugfix: Corrected colors of rec armed tracks and clip states in Session mode.
- Bugfix: Corrected colors of Solo buttons.

Enjoy!

Cyoon · Post by **Cyoon** » Sun Sep 07, 2014 5:12 pm

Hey Moss, would you mind porting this to a Lemur script?

That would be sooo aaweesoome!

Bitwig

KVR Audio

Ableton Push support is here