KVR Audio

egbert · Post by **egbert** » Wed Nov 13, 2013 11:45 am

If you are feeling the shortage of felines on this page - here is an emergency top up.

rodan · Post by **rodan** » Wed Nov 13, 2013 5:45 pm

I'm really interested in this project.

The one thing that will be the deciding factor for me is definitely the piano roll.
Please give it a lot of focus and user testing.

I'd hate for it to end up like Ableton's piano roll. I need something fast and intuitive!

SWallace · Post by **SWallace** » Wed Nov 13, 2013 6:16 pm

rodan wrote: The one thing that will be the deciding factor for me is definitely the piano roll.
Please give it a lot of focus and user testing.

I'd hate for it to end up like Ableton's piano roll. I need something fast and intuitive!

That is the number one reason I can't use Live. It's piano roll's lack of ghost notes is a bummer. Bitwig's implementation of this looks closer to Studio One, which has an awesome piano roll.

aharu · Post by **aharu** » Wed Nov 13, 2013 7:14 pm

Regarding the earlier discussion about sending midi from one track to another, are you guys talking about the possibility to let thesys, cthulhu, tonespace etc send notes and chords to other vsti's? If this is not implemented it's unfortunately a no go for me, sending midi to external software and then back in sucks, it'll be Renoise all over again. It has been highly requested throughout all version updates but still many years later it has not been added. Isn't this basic functionality in a daw, year 2013 (or 2014 maybe)?

dsan@mail.com · Post by **dsan@mail.com** » Wed Nov 13, 2013 8:03 pm

aharu wrote:Regarding the earlier discussion about sending midi from one track to another, are you guys talking about the possibility to let thesys, cthulhu, tonespace etc send notes and chords to other vsti's? If this is not implemented it's unfortunately a no go for me, sending midi to external software and then back in sucks, it'll be Renoise all over again. It has been highly requested throughout all version updates but still many years later it has not been added. Isn't this basic functionality in a daw, year 2013 (or 2014 maybe)?

2nd this!

Happy Musiking!
dsan

UncleAge · Post by **UncleAge** » Thu Nov 14, 2013 1:41 am

aharu wrote:Regarding the earlier discussion about sending midi from one track to another, are you guys talking about the possibility to let thesys, cthulhu, tonespace etc send notes and chords to other vsti's?

Yes, and/but, there is a hitch. See Thesys sends stuff on one channel and so does Tonespace, I like both and use both. And that scenario is usually handled pretty well in most hosts. However, if the plugin was capable of sending on more than one channel like the ones I mention in my post then the receiving track would need to separate that info and allow you to choose that info. Some hosts do and some don't.

Ogopogo · Post by **Ogopogo** » Thu Nov 14, 2013 5:50 am

aharu wrote:Isn't this basic functionality in a daw, year 2013 (or 2014 maybe)?

Eh, imo it's not basic. As people have been saying earlier, it's a v1. Some stuff just can't make the list. But it's already on the list for the future it seems, as I'm sure the modular functions will allow this when they arrive.

pdxindy · Post by **pdxindy** » Thu Nov 14, 2013 5:56 am

Ogopogo wrote:
aharu wrote:Isn't this basic functionality in a daw, year 2013 (or 2014 maybe)?
Eh, imo it's not basic. As people have been saying earlier, it's a v1. Some stuff just can't make the list. But it's already on the list for the future it seems, as I'm sure the modular functions will allow this when they arrive.

It is understandable that some stuff is missing... but the fact that there are various plug-ins that simply cannot be used in Bitwig is (at least for me) a showstopper.

Ogopogo · Post by **Ogopogo** » Thu Nov 14, 2013 6:13 am

^Sure, I think we are on the same page. I'm not saying it shouldn't be a showstopper for some. It's just that it's a tad beyond basic I think.

arkmabat · Post by **arkmabat** » Thu Nov 14, 2013 6:47 am

UncleAge wrote:
aharu wrote:Regarding the earlier discussion about sending midi from one track to another, are you guys talking about the possibility to let thesys, cthulhu, tonespace etc send notes and chords to other vsti's?
Yes, and/but, there is a hitch. See Thesys sends stuff on one channel and so does Tonespace, I like both and use both. And that scenario is usually handled pretty well in most hosts. However, if the plugin was capable of sending on more than one channel like the ones I mention in my post then the receiving track would need to separate that info and allow you to choose that info. Some hosts do and some don't.

Midi Yoke helps me route plugs like that...

Cyoon · Post by **Cyoon** » Thu Nov 14, 2013 7:37 am

hm, Stutter Edit would also need additional Midi Input, would be nice to have for sure. Or even essential for me to use in a live orientated application like BWS.

ThomasHelzle · Post by **ThomasHelzle** » Thu Nov 14, 2013 11:18 am

Well, as much as I agree about the substandard midi-routing between tracks, there is one thing were the current implementation inside of chains shines: All plugins in the chain get the full original midi, which in my experience is not always the case in other hosts. So you are able to reach every plugin however deep in the chain with control information.

That is also the reason why I personally think I wouldn't want to change it completely.

I still think the idea of a "Midi Chain" Instrument/NoteTool that holds any number of midi-generating or -mangling VSTIs could be a good solution, since you would be able to very specifically define if you want to work on midi or not in a node-friendly way.

Well, I guess we will see what they come up with in the end

Cheers,

Tom

crazyfiltertweaker · Post by **crazyfiltertweaker** » Thu Nov 14, 2013 12:13 pm

Can I drag&drop marked clips to the mixer or/and arranger view? And if yes, is all the automation with it?

UncleAge · Post by **UncleAge** » Thu Nov 14, 2013 1:24 pm

ThomasHelzle wrote:I still think the idea of a "Midi Chain" Instrument/NoteTool that holds any number of midi-generating or -mangling VSTIs could be a good solution, since you would be able to very specifically define if you want to work on midi or not in a node-friendly way.

I like this idea. I'm sure something will address the issue somewhere down the line.

pdxindy · Post by **pdxindy** » Thu Nov 14, 2013 6:18 pm

Ogopogo wrote:^Sure, I think we are on the same page. I'm not saying it shouldn't be a showstopper for some. It's just that it's a tad beyond basic I think.

Name another host that cannot use an arpeggiator or other midi plug-in?

In Bitwig I could not use Geist as I commonly do either. Nor any step sequencing. These are very common uses. I understand the lack of AU support, but there are lots of VST plug-ins that are also not supported in Bitwig. I guess that if this is not addressed before 1.0 is released that Bitwig will get skewered for it.

The All In One Source Bitwig Information & Speculation Thread