Bitwig Studio 1.1 life

[Echoes in the Attic]

RECORD AUTOMATION I CAN ACHIEVE IN ABLETON but I CAN'T IN BITWIG

Hey, I saw your signature, this is fixed in 1.1, I am recording automation with the Push in session finally! No more free run bugs.

Mike

Hey cool. Does this mean automation can be recorded either by turning knobs in real-time or by selecting a step and tweaking the parameter to the value you want at that step? As in Ableton?

[ThomasHelzle]

Yeah, that one is huge:

Controller Scripts can have global settings in Preferences and per-Document-Settings in the I/O panel
So you can for instance have your pads in the right octave when you open a song with the correct scale... Depends on the script and will not be available for all scripts right away, but there is huge potential here.

Oh, and you can now rename controllers by doubleclick their name in preferences

Cheers,

Tom

[TeotiGraphix]

RECORD AUTOMATION I CAN ACHIEVE IN ABLETON but I CAN'T IN BITWIG

Hey, I saw your signature, this is fixed in 1.1, I am recording automation with the Push in session finally! No more free run bugs.

Mike

Hey cool. Does this mean automation can be recorded either by turning knobs in real-time or by selecting a step and tweaking the parameter to the value you want at that step? As in Ableton?

Yes and No.

Yes that you can record automation real time in a clip now.

No that you can't edit each step value yet.

The API in 1.1 is still lacking finite clip adjustments like length, automation value etc. Once we get nested devices implemented and the rest that 1.1 offers in API advancements, this is on the #1 priority feature list for me from Bitwig.

For example, I want to implement longpress on a step and adjust that steps, gate, velocity (As in Ableton).

Really, the only limitations for a complete polarity with Ableton is some minor API things. I can understand why Bitiwg doesn't have them yet as they are pretty small use-cases in the grand scheme of what they are trying to do at the moment.

Mike

[TeotiGraphix]

BTW

For any Push users or future users. In this coming winter I am planning on doing a pretty detailed "manual" and video series on all the features with Push4Bitiwg.

Honestly, i am starting to loose track of all the features. I know a new user would miss half of them. I have been using it a lot lately to create some tracks for fun and I am getting some use case patterns that might not be obvious to users coming from Ableton or new to the controller. Some of the work flow is a little different.

I am still working on the Maschine, some things got in the way (a pad light bug on my Studio in Windows). So I get held up, but it works on Mac so when i get my dev stuff on my Mac, I will continue that development.

Mike

[ISP]

Are there self contained files for audio clips as promised? This is my most awaited feature.

Presets can contain the audio now, yes. Sampler, Clips etc.

Does it also means all multisamples can be saved as one large monolith file?

[pdxindy]

How about record count-in for launcher clips? In 1.1?

[The Mantra]

Really, the only limitations for a complete polarity with Ableton is some minor API things. I can understand why Bitiwg doesn't have them yet as they are pretty small use-cases in the grand scheme of what they are trying to do at the moment.

Mike

Have the devs said any thing about adding a note repeat function?
That seems like a good general use thing that is standard across push,mpc,machine or any device with drum pads.

[nori.lam]

Just curious if anyone has tested 1.1 with toontrack plugins? wondering if the sync to host issue is fixed

But either way, this update is gonna rock

[nexttrack30]

RECORD AUTOMATION I CAN ACHIEVE IN ABLETON but I CAN'T IN BITWIG

Hey, I saw your signature, this is fixed in 1.1, I am recording automation with the Push in session finally! No more free run bugs.

Mike

omg! that's great news.

so "write mode" record automation does not overwrite preexisting value? (until parameter is dragged)

it's gon be so much fun!
thx bitwig team for improving this so fast.
i didn't expect this this fast.

[Hez]

RECORD AUTOMATION I CAN ACHIEVE IN ABLETON but I CAN'T IN BITWIG

Hey, I saw your signature, this is fixed in 1.1, I am recording automation with the Push in session finally! No more free run bugs.

Mike

Hey cool. Does this mean automation can be recorded either by turning knobs in real-time or by selecting a step and tweaking the parameter to the value you want at that step? As in Ableton?

Yes and No.

Yes that you can record automation real time in a clip now.

No that you can't edit each step value yet.

The API in 1.1 is still lacking finite clip adjustments like length, automation value etc. Once we get nested devices implemented and the rest that 1.1 offers in API advancements, this is on the #1 priority feature list for me from Bitwig.

For example, I want to implement longpress on a step and adjust that steps, gate, velocity (As in Ableton).

Really, the only limitations for a complete polarity with Ableton is some minor API things. I can understand why Bitiwg doesn't have them yet as they are pretty small use-cases in the grand scheme of what they are trying to do at the moment.

Mike

Awesome, assuming this will allow for note long press -> nudge start/end position (is that what you're referring to with gate)? That's absolutely essential, sequencing without microtiming capability is pretty limited. And yea, if per-step automation comes along with that too, happy days...

[ThomasHelzle]

Have the devs said any thing about adding a note repeat function?
That seems like a good general use thing that is standard across push,mpc,machine or any device with drum pads.

We had a meeting with Moss a while ago and one of the points that came up was some brainstorming how such a function could be implemented with the API. It's not completely trivial since it needs very precise timing and the JavaScript API isn't made for that, so it would need to be a function that runs in the context of the main engine but is getting triggered by the API. It would also need to account for Pressure -> Velocity etc. to be fully usable.

I'm pretty sure we will see a solution at one point but I can't say what the timeframe will be.

Cheers,

Tom

[ThomasHelzle]

Just curious if anyone has tested 1.1 with toontrack plugins? wondering if the sync to host issue is fixed

But either way, this update is gonna rock

Somebody just reported on the RC thread that one of the EZ plugins works in 1.0.15 RC now, but he wasn's sure if it was the BWS update or an update to the plugin that did it. Since other plugins work fine, it may be a bug on the EZ-side maybe?

Check it out.

Cheers,

Tom

[codec17]

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.

Did you know that if you hold the button of a tool down it will automatically switch back to the tool you were using before when you let go? So you can simply hold down 5, click where you want to split, and then let go. That seems very similar to placing your cursor and hitting ctrl+e like in Live, maybe even easier.

Oh yes! Let it stay that way, im just getting used to that... Not everybody used ableton before ...
i for a shortcut to mute things..

[u-u-u]

i for a shortcut to mute things..

Yes, maybe as an CTRL-shortcut extension for the rubber tool (as 'soft rubber' ) ?

[TeotiGraphix]

RECORD AUTOMATION I CAN ACHIEVE IN ABLETON but I CAN'T IN BITWIG

Hey, I saw your signature, this is fixed in 1.1, I am recording automation with the Push in session finally! No more free run bugs.

Mike

Hey cool. Does this mean automation can be recorded either by turning knobs in real-time or by selecting a step and tweaking the parameter to the value you want at that step? As in Ableton?

Yes and No.

Yes that you can record automation real time in a clip now.

No that you can't edit each step value yet.

The API in 1.1 is still lacking finite clip adjustments like length, automation value etc. Once we get nested devices implemented and the rest that 1.1 offers in API advancements, this is on the #1 priority feature list for me from Bitwig.

For example, I want to implement longpress on a step and adjust that steps, gate, velocity (As in Ableton).

Really, the only limitations for a complete polarity with Ableton is some minor API things. I can understand why Bitiwg doesn't have them yet as they are pretty small use-cases in the grand scheme of what they are trying to do at the moment.

Mike

Awesome, assuming this will allow for note long press -> nudge start/end position (is that what you're referring to with gate)? That's absolutely essential, sequencing without microtiming capability is pretty limited. And yea, if per-step automation comes along with that too, happy days...

Gate == nudge start/end position; Yes, sorry I use sequencer terminology.

We just have step on/off right now but, per note microtiming will come for sure.

Mike