Bitwig

pdxindy · Post by **pdxindy** » Thu Sep 25, 2014 8:26 pm

ThomasHelzle wrote: - No luck with poly pressure. I seem to be the only one thinking it's important...

No you are not!

pdxindy · Post by **pdxindy** » Thu Sep 25, 2014 8:28 pm

ThomasHelzle wrote:
ISP wrote:interesting, in what way it was bad in the first place ?
Not bad, but the stretching could change the transients/onsets. Claes now implemented two modes where one of them preserves onsets/transients with higher priority while the other has more priority on smoothness.
There are also three different grain sizes.

Cheers,

Tom

Ahh... so that is only related to timestretching...

pdxindy · Post by **pdxindy** » Thu Sep 25, 2014 8:30 pm

Ogopogo wrote:
ThomasHelzle wrote:
ISP wrote:I don't like the icons in routing section, its overloaded for the eyes imho. It was much better and easy for the eyes with just a text.
IMO they are actually needed to make clear what the routings mean. There are so many options now that I personally am thankful for the icons, even when I know what you mean.

Cheers,

Tom
I agree it does look pretty busy though, so maybe if the icons were a bit smaller or simpler they'd fit in with the text better. They seem out of alignment as it is, but maybe that's stuff they were planning on getting to anyway.

icons optional?

pdxindy · Post by **pdxindy** » Thu Sep 25, 2014 8:33 pm

thetechnobear wrote:
ThomasHelzle wrote:
thetechnobear wrote:oh well, the wait continues….
Yeah, you know I'm with you on that
It's just not such a widespread usecase yet, so it has to take the second seat for now - it's not ignorance.
1.1 is massive as it is, there will always be something missing, and it will hurt the more the closer it is to your own heart and work

Sending Midi directly to VSTs from the SDK doesn't sound too practical?
You wouldn't be able to record it in that case?
Yeah, I know...
as you know I view it as an opportunity... because the likes of LPX and Live also don't support it, bitwig could get in there with leader advantage, really have something others cannot do yet. (ok, cubase can, but its a linear daw) - also whilst the poly pressure isn't there, its has got a nice model to have per key expression, something others lack... so bitwig is 'closer'.

midi -> vst, no its not ideal, as you could not record midi, but you could record the audio output.
(i do this alot, due to the lack of per key expression and also when working with OSC based instruments, so daw is acting as a host)

Yeah... at least being able to play your linnstrument and record the audio would make it doable.

pdxindy · Post by **pdxindy** » Thu Sep 25, 2014 8:40 pm

Does 1.1 have a count-in for recording launcher clips??

+1 on the requests for PDC improvements... I want to know too!

Time signature changes?

mosska · Post by **mosska** » Thu Sep 25, 2014 11:48 pm

i want ctrl e working on the audiogrid. idont want to switch different tools everytime i want to cut sample up! please!its soooo conviinient when u can cut it up on the audio grid with ctrl e just like in ableton.

summer2000 · Post by **summer2000** » Fri Sep 26, 2014 3:15 am

emef wrote:
reflex58 wrote:Has input quantize been implemented?
i would really like this too, maybe a nice little Q button on the transport so i can quickly decide before recording if i want the notes i'm playing in to be quantized.

So what's the verdict? Does 1.1 have input quantize or not?

powermat · Post by **powermat** » Fri Sep 26, 2014 3:59 am

summer2000 wrote:So what's the verdict? Does 1.1 have input quantize or not?

qtheerearranger · Post by **qtheerearranger** » Fri Sep 26, 2014 4:06 am

Interested to know what is meant by "improved audio quality" ?

TristanMendoza · Post by **TristanMendoza** » Fri Sep 26, 2014 4:57 am

qtheerearranger wrote:Interested to know what is meant by "improved audio quality" ?

So am I!

qtheerearranger · Post by **qtheerearranger** » Fri Sep 26, 2014 5:11 am

PS. I talked to a Nektar Employee in the past hour (don't want to say his name if he's not supposed to be saying this stuff to me)

I asked "Are you guys continuing to improve the support with bitwig to make your controllers as integrated as cubase?" and he replied, "Yup, its also about opening up deeper scripting possibilities in BW. The next version adds a lot!!"

c-wave · Post by **c-wave** » Fri Sep 26, 2014 6:40 am

qtheerearranger wrote:PS. I talked to a Nektar Employee in the past hour (don't want to say his name if he's not supposed to be saying this stuff to me)

I asked "Are you guys continuing to improve the support with bitwig to make your controllers as integrated as cubase?" and he replied, "Yup, its also about opening up deeper scripting possibilities in BW. The next version adds a lot!!"

Thanks.. good to know. Was a time frame mentioned (after 1.1 is released of course)?

irtimid · Post by **irtimid** » Fri Sep 26, 2014 8:41 am

Does bitwig 1.1 have this? : start position follows when changing loop?
Please add it as a selectable option.
I'm really missing this.

codec17 · Post by **codec17** » Fri Sep 26, 2014 12:53 pm

Drag and drop to third party samplers????

Eta Carinae · Post by **Eta Carinae** » Fri Sep 26, 2014 1:12 pm

codec17 wrote:Drag and drop to third party samplers????

Wasn't this a problem with Windows? As you can't drag to an elevated process, and Bitwig needs to run as administrator.

Bitwig

KVR Audio

Bitwig Studio 1.1 life