KVR Audio

kennyda · Post by **kennyda** » Fri Feb 21, 2014 4:51 pm

Regnas wrote:The drum creation is my only concern atm, since Bitwig doesn't has a step sequencer a la FL Studio...

Will I need a idrum style vsti for drums?

What's wrong with using the piano roll?

kennyda · Post by **kennyda** » Fri Feb 21, 2014 4:53 pm

Regnas wrote:The drum creation is my only concern atm, since Bitwig doesn't has a step sequencer a la FL Studio...

Will I need a idrum style vsti for drums?

What's wrong with using the piano roll? Personally I just stick them all on separate tracks actually. But I do house music so the drums are pretty simple.

Echoes in the Attic · Post by **Echoes in the Attic** » Fri Feb 21, 2014 8:20 pm

virtualmark wrote:
Echoes in the Attic wrote:Unfortunately it looks like the faders and knobs above the faders stay locked in Bitwig, so you also have just the 8 knobs that change pages of parameters for VST. I don't know about the buttons but I guess those stay locked as well. It's nice that you can name pages and scroll to them, but man what a waste of all those extra controls. I can't imagine mapping some synths to pages of 8 parameters. Endless pages! Apparently in other supported DAWs, they map to the whole set of controls, wish it was the same with Bitwig. For some synths, the fixed controls will work work well, but for many that'll be tough to manage. And if buttons aren't on different pages, even more so.
Damn, that's a bit off putting. I thought that all of the controls on the Nektar would map to any synth. How did you find this out?

A combination of the videos and questions I sent to Justin3am who is involved with the Nektar controllers. Keep in mind I'm just talking about the out-of-the-box control script that Nektar has done for Bitwig, like they did for Reason and Cubase. But one of the cool things about Bitwig is the javascript API so you can create your own control scripts. And I'm sure many will. And obviously there would be a generic midi mode like any other keyboard so of course you could map whatever you want with regular midi. But who wants to use midi!

It is too bad i fpages are restricted to the 8 knobs but the Nektar still looks a great controller with very smart set up for all the DAWs it supports.

Echoes in the Attic · Post by **Echoes in the Attic** » Fri Feb 21, 2014 8:23 pm

StrZlee wrote:
Echoes in the Attic wrote: Unfortunately it looks like the faders and knobs above the faders stay locked in Bitwig, so you also have just the 8 knobs that change pages of parameters for VST. I don't know about the buttons but I guess those stay locked as well. It's nice that you can name pages and scroll to them, but man what a waste of all those extra controls. I can't imagine mapping some synths to pages of 8 parameters. Endless pages! Apparently in other supported DAWs, they map to the whole set of controls, wish it was the same with Bitwig. For some synths, the fixed controls will work work well, but for many that'll be tough to manage. And if buttons aren't on different pages, even more so.
bullshit, you can map every fader and knob to anything you want.

Sorry I can't tell if you know something that I don't or if you have no idea what we're actually talking about. Do you know how the Nektar Panorama custom script for Bitwig works with device control? Are you saying there are multiple assignment pages of the sliders, buttons and encoders on the left side as well? It is my understanding that they get mapped once per device, not multiple pages. Pages refer only to the right side 8 encoders.

Regnas · Post by **Regnas** » Sat Feb 22, 2014 12:38 am

kennyda wrote:
Regnas wrote:The drum creation is my only concern atm, since Bitwig doesn't has a step sequencer a la FL Studio...

Will I need a idrum style vsti for drums?
What's wrong with using the piano roll?

Mostly speed/accuracy...

Cyoon · Post by **Cyoon** » Sat Feb 22, 2014 12:45 am

basically one could also use any knob/poti and control them with a pad controller, just the way how you set up your midi mode then..

Ogopogo · Post by **Ogopogo** » Sat Feb 22, 2014 1:27 am

Cyoon · Post by **Cyoon** » Sat Feb 22, 2014 1:38 am

Nice one!

hibidy · Post by **hibidy** » Sat Feb 22, 2014 2:58 am

It's just not fair.

Cyoon · Post by **Cyoon** » Sat Feb 22, 2014 4:48 am

hibidy wrote:It's just not fair.

hibidy · Post by **hibidy** » Sat Feb 22, 2014 5:02 am

haha!

virtualmark · Post by **virtualmark** » Sat Feb 22, 2014 9:10 am

nimano45 wrote:which Nektar controller are you talking about. Leaning towards the Akai MPK 249/261, but if they're good, it could be a Nektar instead.

It's the Nektar Panorama range. It comes in different sizes - P1, P4 and P6. P1 is just a controller with no keyboard, P4 and P6 have different sized keyboards with P6 being the largest.

Look up some videos on Youtube, these things look awesome. Literally the closest you'll get to making your software synths into hardware synths. They have custom maps for a lot of the popular synths and support a few DAWs now.

I'd really like to see more now, as some people here are suggesting that the controller is a lot more limited than they suggest in the videos.

Echoes in the Attic · Post by **Echoes in the Attic** » Sat Feb 22, 2014 7:55 pm

virtualmark wrote:
nimano45 wrote:which Nektar controller are you talking about. Leaning towards the Akai MPK 249/261, but if they're good, it could be a Nektar instead.
It's the Nektar Panorama range. It comes in different sizes - P1, P4 and P6. P1 is just a controller with no keyboard, P4 and P6 have different sized keyboards with P6 being the largest.

Look up some videos on Youtube, these things look awesome. Literally the closest you'll get to making your software synths into hardware synths. They have custom maps for a lot of the popular synths and support a few DAWs now.

I'd really like to see more now, as some people here are suggesting that the controller is a lot more limited than they suggest in the videos.

No saying the Panoramas are limited. They look awesome (although could use more buttons). But the Bitwig script for Panorama might be limited in terms of how it maps third party VSTs. At least as compared to plug-in mappings in other supported DAWs like Cubase, which uses multiple pages of all controls (16 knobs, 8 sliders, 8 buttons). But I'm still trying to get a clearer picture on that. As far as I know so far, only the eight right side encoders get multiple pages for plug-ins with Bitwig, with the other 8 knobs, 8 sliders and buttons getting mapped but being static. If this is the case, I hope it changes.

pdxindy · Post by **pdxindy** » Sat Feb 22, 2014 8:33 pm

Is there any way to control the note expression in realtime? Or it only can be done in the editor after playing/recording?

The All In One Source Bitwig Information & Speculation Thread