Bitwig

nexttrack30 · Post by **nexttrack30** » Wed May 21, 2014 8:04 am

not sure this is bug or intended.
(i'm praying this is bug. please..

)

made a gif videos here. hope you guys get my point. (if you can't see gif, click it. you can see it bigger.)

http://blog.naver.com/knkm003/220009503138

edit: gif videos on my blog are much more understandable.
so i deleted kvr post. please go to blog and watch.

33tetragammon · Post by **33tetragammon** » Wed May 21, 2014 8:39 am

"write" automation is ALWAYS destructive, meaning it will always overwrite ANY previous automation that was already present. This is the same in most other DAW's (Cubase, Logic, Reaper etc).

Change it to "latch", see if that works for you.

nexttrack30 · Post by **nexttrack30** » Wed May 21, 2014 8:43 am

33tetragammon wrote:"write" automation is ALWAYS destructive, meaning it will always overwrite ANY previous automation that was already present. This is the same in most other DAW's (Cubase, Logic, Reaper etc).

Change it to "latch", see if that works for you.

well.. in ableton, each and every time i hit record automation, it doesn't drestruct UNTIL i touch parameter.
(see videos in blog)
and "latch " can't achieve steady volume with looped clips.

1. i want to achieve steady automation line in looped clips.
2. i want to destruct only certain track. not every tracks.
ableton can, bitwig can't.
for me ableton's behavior makes much more sense.

and i'm VERY shocked most other daws are always destructive.

(thx for letting me know.)
what's the advantage with that?
i can't imagine everytime i hit "record automation", i have to be cautious about it erasing my previous value in EVERY TRACKS.

33tetragammon · Post by **33tetragammon** » Wed May 21, 2014 9:36 am

nexttrack30 wrote:
and i'm VERY shocked most other daws are always destructive.
(thx for letting me know.)
what's the advantage with that?
i can't imagine everytime i hit "record automation", i have to be cautious about it erasing my previous value in EVERY TRACKS.

To clarify, most DAW's have different automation modes : Read, Latch, Touch, Trim, Write. It's up to the user's preference to select what they want.

This is something i like about Ableton in general. I just hit session record, and when i touch and turn a knob on Push this gets recorded as long as i touch and turn it.....
No headscrathing when i'm in creative mode.....

LOVE IT!!!!!

nexttrack30 · Post by **nexttrack30** » Wed May 21, 2014 9:57 am

33tetragammon wrote: This is something i like about Ableton in general. I just hit session record, and when i touch and turn a knob on Push this gets recorded as long as i touch and turn it.....
No headscrathing when i'm in creative mode.....

LOVE IT!!!!!

that's what i'm sayin!
hit record, play with balance, different part different balance.
no need to fear overwriting other untouched previous values.
if bitwig's record automation behavior is not wrong and intended, i hope they give us new automation option (ableton's behavior).

ThomasHelzle · Post by **ThomasHelzle** » Wed May 21, 2014 10:18 am

Please report this with a link to this thread to tech support:
http://www.bitwig.com/en/support/tech-support.html

Cheers,

Tom

nexttrack30 · Post by **nexttrack30** » Wed May 21, 2014 10:36 am

ThomasHelzle wrote:Please report this with a link to this thread to tech support:
http://www.bitwig.com/en/support/tech-support.html

Cheers,

Tom

already did it.

eagerly waiting for them to answer if they have any will to change this.

this behavior just takes away lots of fun of mine with record automation.

ThomasHelzle · Post by **ThomasHelzle** » Wed May 21, 2014 10:38 am

Bitwig

KVR Audio

there is something i can achieve in ableton's record automation but i can't in bitwig.