Bitwig

thetechnobear · Post by **thetechnobear** » Thu Jan 21, 2016 1:35 pm

blouaap wrote: Give me an example scenario of what you might want. I would like to try to see if I can do it. I have never had any problems with routing midi as of yet. I just want to see what I might be missing.

Ive a hardware sequencer, that outputs notes on midi channels 1 - 16, and Id like a 16 tracks on bitwig for each so that can access different instruments.
how do I do this in bitwig?

Hack: Create 17 controller devices (1-16 + one for omni)
but this doesnt scale, I have 3 other controllers .. some of which also I want to use filter by midi channels.
before you know it you have 30+ controllers is your drop down, most of which are just repetitions of the same controller just for different midi channels.

another scenario, say I want to a track to respond to ANY controller that transmits on midi channel (e.g) 2. this allows me from whichever controller to just change the midi channel, and then I can access that track.

and yes, Ive no other DAW which doesn't just allow me to select the controller for the track, and then select the midi channel i want to filter by... its a pretty basic feature, when you have multiple controllers.

pdxindy · Post by **pdxindy** » Thu Jan 21, 2016 8:38 pm

It's a big limitation...

The different Geist Engines send on different midi channels...

codec17 · Post by **codec17** » Thu Jan 21, 2016 10:06 pm

pdxindy wrote:It's a big limitation...

The different Geist Engines send on different midi channels...

+1

anp27 · Post by **anp27** » Fri Jan 22, 2016 1:16 am

I think we can just end this discussion now.. no new announcements were made and all my predictions were wrong..

toby · Post by **toby** » Fri Jan 22, 2016 1:33 am

anp27 wrote:I think we can just end this discussion now.. no new announcements were made and all my predictions were wrong..

NAMM hasn't even officially started yet? Or am I wrong?

anp27 · Post by **anp27** » Fri Jan 22, 2016 1:41 am

toby wrote:NAMM hasn't even officially started yet? Or am I wrong?

It started about 8 hours ago..

Also, are you Toby from Black Octopus Sound? I absolutely love your sample packs and Leviathan gets the most use out of everything I own. I don't have the time or patience to tune my kicks so I'm always grabbing your tuned Leviathan kicks that sound really good out of the box.

toby · Post by **toby** » Fri Jan 22, 2016 2:40 am

anp27 wrote:
toby wrote:NAMM hasn't even officially started yet? Or am I wrong?
It started about 8 hours ago..

Also, are you Toby from Black Octopus Sound? I absolutely love your sample packs and Leviathan gets the most use out of everything I own. I don't have the time or patience to tune my kicks so I'm always grabbing your tuned Leviathan kicks that sound really good out of the box.

I thought it officially started tomorrow, I'm still hopeful there will be a couple cool Bitwig announcements though!

Glad you dig the Leviathan pack! We have volume 2 in the works and I have learned a ton in sound design since then. Some huge snares and claps and a ton more tuned kicks on the way.

WXLF · Post by **WXLF** » Fri Jan 22, 2016 3:03 am

"Re: NAMM is here, Bitwig announcement predictions were all wrong!"

C'mon man... the subject title change is a little theatrical

takaii · Post by **takaii** » Fri Jan 22, 2016 5:14 am

WXLF wrote:"Re: NAMM is here, Bitwig announcement predictions were all wrong!"

C'mon man... the subject title change is a little theatrical

Haha yeah, and bitsig didnt makt any announcement or predictions meaning nothig right or wrong

pdxindy · Post by **pdxindy** » Fri Jan 22, 2016 5:17 am

WXLF wrote:"Re: NAMM is here, Bitwig announcement predictions were all wrong!"

C'mon man... the subject title change is a little theatrical

The new subject should have 'my' in there...

My prediction was correct

anp27 · Post by **anp27** » Fri Jan 22, 2016 6:24 am

toby wrote:I thought it officially started tomorrow, I'm still hopeful there will be a couple cool Bitwig announcements though!

It started on Wednesday actually... that's when all the vendors got together and had a meeting I think. It officially started today. About the announcements, somebody from the Bitwig Discord chat actually met the Bitwig team at NAMM and he reported that there will be no announcements

toby wrote:Glad you dig the Leviathan pack! We have volume 2 in the works and I have learned a ton in sound design since then. Some huge snares and claps and a ton more tuned kicks on the way.

That's such awesome news, please please please more tuned kicks that sound HUGE like the Production Master 212 Kick Drmus (which I also own!) Will definitely be picking Leviathan 2 up upon release

WXLF wrote:C'mon man... the subject title change is a little theatrical

Well, I'm a musician and aren't all musicians a little dramatic???

pdxindy wrote:The new subject should have 'my' in there...

I was gonna do that but realized that I wasn't the only one here that thought they would have made some announcement of sorts

pdxindy wrote:My prediction was correct

Yes, you're prediction was CORRECT!

Ogopogo · Post by **Ogopogo** » Fri Jan 22, 2016 6:50 am

At least Tristan got to meet Claes.
https://www.instagram.com/p/BA0pCrnLdU_/

viceverser · Post by **viceverser** » Sat Jan 23, 2016 11:29 am

stamp wrote:
thetechnobear wrote:
anp27 wrote: flexible midi routing, i think would be almost embarrassing to announce, given most peoples response would be... what you cant do that already?

What I would like to see though, is BW give Moss and TeotiGraphix, a bucket of cash and direct dev support, to make the Push (/ Push 2) and other similar controllers as integrated as they are in Ableton (e.g. so we can add tracks/devices, view audio levels) . the Push with a fully integrated workflow could really challenge Ableton. but it needs to be complete like Ableton, completely mouseless/keyboard operation.

Moss/TeotiGraphix have done a fantastic job, but a few things in the controller api hold them back, they deserve some of the developers time/support to just get those last few things.
so announce at NAMM, Bitwig official support for Push2 in collaboration with Moss/TeotiGraphix
+ 1000

+ 1000 x 1000

TeotiGraphix · Post by **TeotiGraphix** » Sat Jan 23, 2016 12:04 pm

viceverser wrote:
stamp wrote:
thetechnobear wrote:
anp27 wrote: flexible midi routing, i think would be almost embarrassing to announce, given most peoples response would be... what you cant do that already?

What I would like to see though, is BW give Moss and TeotiGraphix, a bucket of cash and direct dev support, to make the Push (/ Push 2) and other similar controllers as integrated as they are in Ableton (e.g. so we can add tracks/devices, view audio levels) . the Push with a fully integrated workflow could really challenge Ableton. but it needs to be complete like Ableton, completely mouseless/keyboard operation.

Moss/TeotiGraphix have done a fantastic job, but a few things in the controller api hold them back, they deserve some of the developers time/support to just get those last few things.
so announce at NAMM, Bitwig official support for Push2 in collaboration with Moss/TeotiGraphix
+ 1000
+ 1000 x 1000

Nice,

You know what is funny is I haven't worked on Push for a while, reason being I started Machine4Bitwig in the hopes to get Maschine (all 3 controllers) working just as Moss has had in the last year with Push.

The thing is, I use Windows and the Maschine Studio is screwed up with pad lights. This issue has been around for over a year, damn probably 1.5 years now. I had been inc with BW about this many times, I actually thought something was going to happen in the Fall since they were in contact with NI and "I thought talking to NI" I was finally going to get a driver update from NI that would fix this issue.

Now we are in almost Feb and I have heard NOTHING from BW, I spent 100's of hours on not only the Push and Framework4Bitwig scripts with Moss but if you look at the impl of Maschine4Bitwig it's insane with code.

I feel like shit now because I put so much time into Maschine4Bitwig only to have it sit and rot because of some stupid reason that I have idea why. I'm a bit jaded only for the fact Maschine users could have the same integration that Push has right now expect without the 64 pads.

I digress, to say I am irritated isn't the right word, I just feel kind of let down because I put so much into Bitwig a year ago. I, from the core of my heart gave them Java code that created the changes docs for there API, told Volker he needed to add @see tags for devs, think about the future, donated code to create their javascript stubs that people use in IDEs for code completion.

Blah, just had to get this out. I'm the ype that can handle people telling me, sorry it ain't going to happen. With Maschine4Bitwig, it should have went down like that or better communication.

I also understand I am just a community member and BW has massive stuff they are keeping track of.

I love BW and will use it for years to come, if they offered me consultancy for controllers some day I would take it in a heart beat.

PS I don't need people telling me, just email them either because I have and it seems the emails just get lost.

Mike

thetechnobear · Post by **thetechnobear** » Sat Jan 23, 2016 1:15 pm

actually someone is misquoting anp27, for good or bad, I wrote the above.

TeotiGraphix, I completely understand how you feel, and I would too!

Bitwig have 'outsourced' an important element, controller integration, to the community... they need to nurture, foster and encourage that relationship, if they wish to see it prosper, not just 'take it for granted'.

In the case of Push/Maschine it was obviously a huge amount of work, not just a couple of scripts - and by far the biggest use of the Controller API, if it worked for those scripts, the chance are it would work for many...

anyway, be assured, I (and I'm sure many others) certainly appreciate the work you and Moss have done, its a fantastic achievement, and I hope Bitwig 'see the light'