because i'm desperate to get into the midi routing and the multi outsISP wrote:Why do you need this?emef wrote:i bought a copy of bitwig, i'd like to have a go on this 1.1 beta
Bitwig Studio 1.1 life
-
- KVRian
- 899 posts since 5 Jun, 2001
-
- KVRian
- 899 posts since 5 Jun, 2001
excellentThomasHelzle wrote:- VST multiouts work basically like a containerdevice in that each output has it's own chain which also shows up in the mixer like the DrumMachine.
- Folders will be in 1.2 as was said before.
- Midi Routing between tracks with the Note Receiver Device or directly in the track header (recording only).
- Currently closed beta but will open up later to all license holders.
Cheers,
Tom
-
tor.helge.skei tor.helge.skei https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=152647
- KVRian
- 566 posts since 30 May, 2007
among (a lot of) other things:sardaukar wrote:ok...so whats new!?
devices: de-esser, multiband fx-3, note mod, note receiver, audio receiver..
vst plugins: output effect chains, side-chaining, routing for multi-timbral, multi-out plugins, and more..
other: improved sound quality and timing, grain size parameter, transient preservation mode, vastly improved track routing, tracks/chains/devices can be decativated (and for tracks, hidden), tap tempo, track crossfader, and more..
controller scripting: the list of improvements and additions are enormous..
-
- KVRist
- 317 posts since 30 Jun, 2012
really good news here! Can't wait to try it o_Otor.helge.skei wrote:among (a lot of) other things:sardaukar wrote:ok...so whats new!?
devices: de-esser, multiband fx-3, note mod, note receiver, audio receiver..
vst plugins: output effect chains, side-chaining, routing for multi-timbral, multi-out plugins, and more..
other: improved sound quality and timing, grain size parameter, transient preservation mode, vastly improved track routing, tracks/chains/devices can be decativated (and for tracks, hidden), tap tempo, track crossfader, and more..
controller scripting: the list of improvements and additions are enormous..
- KVRian
- 696 posts since 27 Mar, 2014
Dang I want to drive 1.1 ... 
What about external outs PDC?
What about external outs PDC?
-
TristanMendoza TristanMendoza https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=325569
- KVRian
- 807 posts since 27 Mar, 2014
Looks great
excited to check it out and hear more about it!
Damn the new devices and tap tempo and cross fader sound very exciting! Everything sounds exciting
Kinda curious about the improved sound quality though like how was it improved?
Damn the new devices and tap tempo and cross fader sound very exciting! Everything sounds exciting
Kinda curious about the improved sound quality though like how was it improved?
-Tristan
MacBook Pro|MacOS Sierra|Bitwig Studio 2.0
UA Apollo Twin| EVE SC207 Monitors|ATH M50x|Focal Spirt Pro|Komplete 10|Push
MacBook Pro|MacOS Sierra|Bitwig Studio 2.0
UA Apollo Twin| EVE SC207 Monitors|ATH M50x|Focal Spirt Pro|Komplete 10|Push
-
Echoes in the Attic Echoes in the Attic https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=180417
- KVRAF
- 12040 posts since 12 May, 2008
What was the granular size thing?
Any improvements to sampler?
Any improvements to sampler?
-
- KVRAF
- 1551 posts since 14 Feb, 2010
ThomasHelzle wrote:- VST multiouts work basically like a containerdevice in that each output has it's own chain which also shows up in the mixer like the DrumMachine.
Can you select how many outputs you want to use? So if i want just 4 outputs of say FXpansion GEIST, you can select the last 4 or the first 4? Or is it always the full 16 in case of geist?
- KVRian
- 868 posts since 2 Jan, 2013
is 1.1 seeing some improvements on midi input to tracks, in particular:
- multi midi channel passthrough* to VSTs? (so we can use u-he with voice per channel midi?)
- poly pressure support through to VSTs? (i.e. not always mapping to things like timbre)
- generic midi port/channel on track input?, so we don't have to create different controllers for each port/channel combo
* i guess this could also be thought of as multi channel input on tracks, rather than munching them all down to midi channel 1 (just like Ableton)
- multi midi channel passthrough* to VSTs? (so we can use u-he with voice per channel midi?)
- poly pressure support through to VSTs? (i.e. not always mapping to things like timbre)
- generic midi port/channel on track input?, so we don't have to create different controllers for each port/channel combo
* i guess this could also be thought of as multi channel input on tracks, rather than munching them all down to midi channel 1 (just like Ableton)
