I made this a couple months ago but, I thought I would share it for those that might not know it exists that are using Maschine as a controller for Bitwig Studio and my script. I have been working on some Caustic applications and haven't had a lot of time to work on this script in the last month or so but, I will get back to it when I have some more time. It is quite functional as it is. The main thing that needs work is the step sequencing expanded. Mike
It has been a long road of bugs and other various setbacks for these scripts.
I have spent the day refactoring and getting the basic transport and pad work in for all 3 controllers.
Some notes right now, the pad section is under construction as we speak and you can play on the pads but, things are in flux.
I am announcing this right now since all the features listed in the wiki are tested and stable and the list will only be added to. As is stands you can control most of Bitwig's transport and such, take a look at the wiki.
I have a lot more implemented under the covers in code, but since i actually have the controllers to test with, I am not releasing this as alpha for those that want to use their Maschine to control whats listed.
The displays on the Studio and MK2 work, along with the encoder knobs.
Native Instruments made it really hard for me to transition a lot of the code from the Push4Bitwig script, so I have been inventing new ways to set modes and views etc.
Notes as of now and I will update this as I go;
- Beta 1.1 required on 1.0.15
- Windows it seems has a bug in the driver for pad lighting, this has been a pain in the ass, NI is looking at it.
- Mikro pad lights don't really work right now but play notes.
I have scales and other things working but I am creating a way to toggle modes without using NI's knob pages, pain in the ass.
I will update this post as I add features, thanks!
Well reading the last post of mine a couple months ago and seeing where I am today, just proves never loose optimism in life, you just don't know where it's going to take you.
So, a month or so ago I invested in some hardware controllers namely the Maschine Studio and Ableton Push. I also decided I loved working with "new" things so I purchased the 1.0 version of Bitwig Studio (https://www.bitwig.com).
Life is a very fickle and insane joy ride through unknowns and surprises. For the last year I have been working on Caustic related projects and if you read the last blog post, I was showing of this little DAW/IDE project I had made with LibGDX and the Caustic Core.
Well my life has gotten in the way of that large project and sent me off course. Honestly, I have no idea what I am doing right now other than tinkering with possible smaller ideas and goals.
Unity is definitely something I want to explore more and tune my 3D modeling skills more with blender. Other than this, 2014 seems to have gone into oblivion again with trying to plan any type of real projects.
So, Caustic Live is on permanent hold until I know what the heck I am going to do this year.
Just thought I would post an update to what I got done in the last 4 days;
- Base IDE framework working with views and panes, full command framework, undo/redo If yuo look at the right where it says history, that is like a Photoshop history to rewind and fast forward all application commands. You can see I have delete and move commands in there right now
- The Patterns view is populated when you click on a track, it shows all patterns of the machine, you can click on the list item to preview the pattern, if you like it, then drag it into the sequencer. (previews in pattern mode)
- Transport controls in tool bar. This is really important, have the tool bar implemented now means I am just creating commands finally, this thing is starting to grow.
- Move, Delete, Add, Trim song sequencer clips.
- More little stuff but I just got that major foundation finished this weekend.
It's been along time since I have blogged, about 3 years now of change that Flash has finally been laid to rest, Adobe is finally out of my companies picture and I have successfully helped build a community over at www.singlecellsowftware.com.
Its that time in your life that you focus back in on yourself and see what you have learned. I have been developing some audio frameworks, using LibGDX for Java graphics on top but, now after some very deep searching, I have decided to take a whack at Unity again for fun, well we will see if its just for fun.
For most that don't know my past, I started developing Flash components back in 2001, tiny Flash 5 and smart clips. I found out that I loved developing UI components, so I made a some to sell and did quite well. Then came Flex, the first "RIA" like framework that was mainly built around Flash's component framework. I took that and created some very large commercial components, did well there also. The main key and you can probably still google my name was in help and support. I had 1000's of flashcoders and Adobe forum posts helping people learn the user interface programming, I loved it.
During this time I ran into Unity. Unity reminded me of the spark I had dragging and dropping behaviors in Flash 10 years ago. I am such a visual programmer so now I am diving in with a couple projects to have a bit of fun.
This site is going to focus on my Caustic projects and Unity projects, with some LibGDX thrown in. So I will have Java and C# code probably.
Anyway, this is my first blog post in a long time, feels good. And see you in the future.
The Caustic Core is an audio engine developed by Rej at singlecellsoftware.com.
This audio system powers one of the most respected Android audio apps; Caustic.
The Caustic Core will always refer to the libcaustic.so that is included in
the framework I have written, git/CausticSDK. The Caustic Core is the
central OSC messaging hub that takes in osc messages and gives out values for command queries.
Caustic Core SDK
The OSC messages are wrapped by a Java layer that is know as the CausticSDK project on GITHub located at;