KVR Audio

Cyoon · Post by **Cyoon** » Sat Nov 23, 2013 11:38 pm

Will this native modulation system be open for third party developers? like an available sourcecode or format they could port their plugins to, in order to make use of it?

i think about using a third party plugin as soundgenerator but making all the parameters of it available in the modular system in the backround, wich then could be rearranged or maybe even combined with other instruments.

codec_spurt · Post by **codec_spurt** » Sun Nov 24, 2013 12:06 am

That's a bit more like it!

hibidy · Post by **hibidy** » Sun Nov 24, 2013 12:11 am

Poor babies! Max is gonna get that pretty soon (though he's three times as big as those cats) I was going to do it last week but I thought wraslin' him should wait until my curfew for my arm has lifted (didn't do anygood anyways.)

Now back to bitwig. Lookin' interesting. The heat is on if they are going to get it out this year.

pdxindy · Post by **pdxindy** » Sun Nov 24, 2013 1:34 am

ThomasHelzle wrote:
pdxindy wrote:
What if I want to use an expression pedal and/or breath controller? How would that work?
Ah cool that it makes more sense now
Yeah, exactly. Or you could have one LFO in each "Arm"/Layer reaching down to all the effects in that Arm, but not backwards.

That whole nesting and un-nesting is supersimple IMO. Depending on where you come from it may take a moment to adjust, but well, that's the price to pay for the coolest modulation system on the planet

As for additional controllers: Any parameter of any device, internal or VST -> Rightclick -> Learn Control mapping. Then you get a green highlight and a small moving "I'm waiting" Icon until you move your controller. Done.

Cheers,

Tom

The modulation system sure looks to be one of the highlights of Bitwig!

Regarding the additional controllers... Does rightclick -> Learn Control Mapping behave the same for scaling? You drag the assigned control to set the range? How do you go back later and adjust that range?

Also, Suppose I have an LFO with a nested LFO and nested in the second LFO a synth chain with effects. I have a bunch of synth/fx parameters modulated by one LFO and a bunch modulated by the second LFO, is there any easy way to see what is modulating what? Like a viewable modulation list?

Likewise, if one parameter has 2 modulation sources assigned, is there any sort of visual clue?

justin3am · Post by **justin3am** » Sun Nov 24, 2013 2:07 am

pdxindy wrote:Also, Suppose I have an LFO with a nested LFO and nested in the second LFO a synth chain with effects. I have a bunch of synth/fx parameters modulated by one LFO and a bunch modulated by the second LFO, is there any easy way to see what is modulating what? Like a viewable modulation list?

Likewise, if one parameter has 2 modulation sources assigned, is there any sort of visual clue?

When you right click on the Modulation target button, it will show a list of parameters that are modulated by that source (with an option to clear mod targets individually). Likewise, if you right click on a control, you will see a list of active modulators mapped to that control which can be edited (mod depth) or cleared.

tooneba · Post by **tooneba** » Sun Nov 24, 2013 5:31 am

It's a curious thing that if beta testers are allowed to speak about it and even post a screenshots to public forum why won't update their official video to explain more features?

sl1914 · Post by **sl1914** » Sun Nov 24, 2013 6:22 am

Maybe their small team is busy trying to get the product to release condition?

hibidy · Post by **hibidy** » Sun Nov 24, 2013 6:25 am

Ooooooooooo, I see what you did there!

pdxindy · Post by **pdxindy** » Sun Nov 24, 2013 6:26 am

sl1914 wrote:Maybe their small team is busy trying to get the product to release condition?

That seems likely...

hibidy · Post by **hibidy** » Sun Nov 24, 2013 6:33 am

Omg, you set yourselves up for this one

Hey, looks like a good product is coming your way, but it's been a wee while

ChiTown24 · Post by **ChiTown24** » Sun Nov 24, 2013 6:34 am

tooneba wrote:It's a curious thing that if beta testers are allowed to speak about it and even post a screenshots to public forum why won't update their official video to explain more features?

they're busy ironing out bugs and implementing new features. beta testing. the software isn't for sale yet, so what benefit is there in posting more videos than they are already ? you gotta live in the present man.

tooneba · Post by **tooneba** » Sun Nov 24, 2013 6:39 am

sl1914 wrote:Maybe their small team is busy trying to get the product to release condition?

But it won't explain why they didn't do public beta. How could devs debug on hundreds of different environments themselves without having a big parent company like Yamaha for steinberg. Even with that, software came out with bugs... They must have sufficient resource to do...

Bronto Scorpio · Post by **Bronto Scorpio** » Sun Nov 24, 2013 6:53 am

Closed betas are much more controlled than public ones.
Just have a look at this thread and imagine half of the posts here would have been support mails.

Public betas are more useful to check if an already feature complete product runs on a variety of different systems, but are useless during the actual developement phase, at least in my experience.

Cheers
Dennis

pdxindy · Post by **pdxindy** » Sun Nov 24, 2013 7:12 am

tooneba wrote:
sl1914 wrote:Maybe their small team is busy trying to get the product to release condition?
But it won't explain why they didn't do public beta. How could devs debug on hundreds of different environments themselves without having a big parent company like Yamaha for steinberg. Even with that, software came out with bugs... They must have sufficient resource to do...

They are free to choose whatever development method they wish and do not owe you an explanation.

pdxindy · Post by **pdxindy** » Sun Nov 24, 2013 7:19 am

Bronto Scorpio wrote:Closed betas are much more controlled than public ones.
Just have a look at this thread and imagine half of the posts here would have been support mails.

Public betas are more useful to check if an already feature complete product runs on a variety of different systems, but are useless during the actual developement phase, at least in my experience.

Cheers
Dennis

I agree with Dennis...

Not many hosts do public betas and many of the people who have participated in Live's past public betas have complained about how little feedback they got from Ableton, how haphazard the beta process seemed. Now they are moving away from how they used to do it (and it works better)

In big public betas, most of the people just want to check the stuff out, make crappy or sloppy bug reports, don't know the software well so make mistakes, false reports, etc. There are endless feature requests, complaints, user errors and so on.

I suspect it would have been suicide for Bitwig to have a public beta.

The All In One Source Bitwig Information & Speculation Thread