Bitwig

Clearscreen · Post by **Clearscreen** » Mon Mar 20, 2017 3:03 am

Not sure how I feel about this licensing yet.

I've just realised that bitwig 2 has the same v1 behaviour with regard to midi channels - all midi in a track is channel 1, no matter what the input is.

I just got a beatstep and would like to change channels on the fly.

So, if I pay the 12 month license fee and request proper internal midi channel handling in a support ticket, what are the odds of it getting changed (or to my mind, fixed...) within that 12 months? Is it unreasonable to expect to receive that change given you only have 12 months of available updating?

Not sure how to feel about it...

lunardigs · Post by **lunardigs** » Mon Mar 20, 2017 3:42 am

I upgraded and I'm feeling pretty good about it so far. I'll be very interested to see the next changelog.

Right now I'm cleaning up some of my controller scripts from 1.0. It's a rewarding exercise--in madness

. For real though, the API aspect is incredible. I almost can't believe it's there. Pro-audio companies are scarcely "open" in my experience. I think Bitwig represents something much more than a new DAW.

Btw, I'd really like to switch over to API 2, but it's definitely more advanced and I have to learn it. If I have any complaints right now, it's that resources on API 2 are somewhat hard to find. Also, nearly all of the included scripts with BWS2 are API 1.

TeotiGraphix · Post by **TeotiGraphix** » Mon Mar 20, 2017 12:29 pm

lunardigs wrote:Btw, I'd really like to switch over to API 2, but it's definitely more advanced and I have to learn it. If I have any complaints right now, it's that resources on API 2 are somewhat hard to find. Also, nearly all of the included scripts with BWS2 are API 1.

See this, it's API 2.

BTW, Framework4Bitwig is being deprecated as Moss is writing a new framework, he mentioned this in the Push4Bitwig thread.

The framework as it exists in that repo works with Push and V2, so you should be able to understand all the API by studying it.

https://github.com/teotigraphix/Framework4Bitwig

Cyoon · Post by **Cyoon** » Mon Mar 20, 2017 12:37 pm

Clearscreen wrote:Not sure how I feel about this licensing yet.

I've just realised that bitwig 2 has the same v1 behaviour with regard to midi channels - all midi in a track is channel 1, no matter what the input is.

.

there is a new device wich let you choose the midi channel now. Also this looks like an issue with script i guess. At least here it works fine to receive other midi channels.

lunardigs · Post by **lunardigs** » Tue Mar 21, 2017 12:33 am

TeotiGraphix wrote:
lunardigs wrote:Btw, I'd really like to switch over to API 2, but it's definitely more advanced and I have to learn it. If I have any complaints right now, it's that resources on API 2 are somewhat hard to find. Also, nearly all of the included scripts with BWS2 are API 1.
See this, it's API 2.

BTW, Framework4Bitwig is being deprecated as Moss is writing a new framework, he mentioned this in the Push4Bitwig thread.

The framework as it exists in that repo works with Push and V2, so you should be able to understand all the API by studying it.

https://github.com/teotigraphix/Framework4Bitwig

Thank you for the link, TeotiGraphix. You know, I've looked at the Push4Bitwig script quite a bit--I have Push 1 in fact and use it everyday--although, his stuff is above my head for the most part. Moss is a badass, no doubt ... Really, I'm looking for a primer on the API 2; yet something that goes into TrackBank and RemoteControl, etc.

Clearscreen · Post by **Clearscreen** » Tue Mar 21, 2017 1:07 am

.maki wrote:
there is a new device wich let you choose the midi channel now. Also this looks like an issue with script i guess. At least here it works fine to receive other midi channels.

Thanks for the reply .maki - which new device is that? I haven't subscribed yet so I'm still using Beta6 until I get paid. In b6 the midi CC and program change devices can select a channel to receive from.

The scripts I'm using are the generic ones Thomas Helzle has shared and all midi within a track is getting assigned to channel 1 by Bitwig. I've found a script that breaks each channel from an external device out to a track, but I'd like to send multi channel control to one plugin and re-routing via extra tracks each time is pretty tedious...

Cyoon · Post by **Cyoon** » Tue Mar 21, 2017 1:29 am

there might come a solution to this.

So long did you try this script?

https://www.bitwig.com/en/community/con ... _bi_1.html

Also especially for the Beatstep you might want to test this one: http://www.kvraudio.com/forum/viewtopic ... 8&t=427919

Clearscreen · Post by **Clearscreen** » Tue Mar 21, 2017 11:14 pm

Thanks .maki, I haven't seen that midi channel device in the beta! I'll subscribe at the end of this month and see I guess...

I haven't tried that T. Helzle script either, but I've used a similar one I think, that breaks each channel out to a separate midi input. which leads back to the tedious track/channel routing - I'll try this one out though when I have my beatstep at hand later today.

Moss' beatstep script is interesting and I haven't fully got my head around it yet - it seemed like overkill for me, but I'll dig into it deeper yet and see if I can do what I want.

Ideally I want to change the midi channel on the hardware and not have bitwig re-map all incoming channels to channel 1 internally... if that makes sense...

Appreciate the replies .maki, cheers!!

ere2learn · Post by **ere2learn** » Tue Mar 21, 2017 11:27 pm

.maki wrote:there is this device wich should help imo

I cant see this in 2.0 either,I only see MIDI CC,Program Change & Song Select

Cyoon · Post by **Cyoon** » Tue Mar 21, 2017 11:58 pm

i didn't see it as well, who knows might be an illusion.

Clearscreen · Post by **Clearscreen** » Thu Mar 23, 2017 12:36 am

.maki wrote:edited because of a leak blead, sry.

Was that a leak of a new feature?!?

Fleer · Post by **Fleer** » Thu Mar 23, 2017 1:04 am

Apparently, there are people trying to sell their copy of Bitwig 2.0 for as low as €200 already. Goes to show that the license model is scaring people off instead of luring them in.

Vortifex · Post by **Vortifex** » Thu Mar 23, 2017 12:03 pm

I will never buy any music software that requires a subscription. I was interested in Bitwig but when I heard about this they lost me as a potential customer.

pdxindy · Post by **pdxindy** » Thu Mar 23, 2017 3:55 pm

Vortifex wrote:I will never buy any music software that requires a subscription. I was interested in Bitwig but when I heard about this they lost me as a potential customer.

I would not describe Bitwig as a subscription.

I define subscription such that as soon as you stop paying the software stops working.

When you buy Bitwig, it has an annual cost to keep getting updates, but if you stop paying it, you can keep using the software without time restriction... for years if you want to.

tor.helge.skei · Post by **tor.helge.skei** » Thu Mar 23, 2017 4:41 pm

if you subscribe to a magazine or newspaper, but then end the subscription, the old issues you have already received doesn't stop "working" either..

Bitwig

KVR Audio

License model no way !!!