Automation Capture funny

[Pete Gates]

My understanding - though I can't find it in the 8.0 manual for D-Control - was:

Capture captures controls that are writing.

Option+Capture captures the whole desk state (for enabled parameter types).

Shift+Option+Capture capture the entire state of selected channels for selected parameter types.

What my D-Control (8.01cs1) is Actually doing on the third one, which I assume isn't a feature change but a bug, is Shift+Option+Capture adds the entire state of the selected channel to whatever is already in the capture buffer!

Pete

[uno1234]

Yes I've noticed this too. Seems like a bug. Does anyone actually care that the wonderful Capture feature that has lost its usefulness? I feel like this has been going on for quite a while.

[Drew Mazurek]

Bump.

I was messing with this today (to try and help someone else since I don't do a lot of Capturing) and noticed it seemed to be broken as well.

Paging Gil?????

[uno1234]

It's been broken for over a year. I guess no one cares and no one uses this feature. It is a great great feature but no one reads manuals so go figure.

Gil wassup?

[macaholic]

Ouch!!

Hopefully that will be addressed before too long since the post house where I am will be upgrading from 7.3.1 to 8 within the next few months.

Capture is a biggie for me (especially the 3rd option listed)... If you Option+Capture the console, does Shift+Option+Punch work??

I guess that would be a workaround, although a bit messy when storing your capture buffer to your snapshots.

JC

[digimidi]

I just saw this. I am out of the office until next Monday. I will check this as soon as I get back and let you know what I find.

Gil

[Drew Mazurek]

Thanks Gil. Look fwd to what you find.

[digimidi]

OK, I am looking into this today and will report back. At first glance, it does seem that a shift+option capture is adding to what is already in the buffer. Shift+option punch will only punch the selected channels, but does not address storing in snapshots. I will investigate more and let you know.

Gil

[digimidi]

OK, can someone give me an exact step by step workflow on how you are wanting to use this feature? I have tried a couple of things and want to make sure we are all on the same page. Thanks!

Gil

[SBP]

Originally Posted by digimidi

OK, can someone give me an exact step by step workflow on how you are wanting to use this feature?l

Gil,

I may be the only one but I like it the way it is. The documentation is unclear though -specifically the fact that you need to option shift both capture and punch capture -to copy and paste settings on selected channels only. -Its never been clear to me what the option shift capture bit does.

The way I use it now -to copy settings from one location on the timeline to a new location on the same tracks.

1-Select tracks and location in time line where I want to copy settings
2-option shift capture
3-select range and tracks I want those settings to be pasted
4-hit option shift punch capture
5- play (and bump and wiggle as I go) or 'wrt to all' to write settings to range.

Hope that helps -Now can we talk about 'write to all' wiping out your entire mix if no selection is made -I would love to see this changed.

1- WRITE TO ALL WITH NO RANGE RUNINS/WIPES DATA ACROSS ENTIRE MIX.
Because we are programming our mix. The integrity of this mix data is of
utmost importance. Our biggest concern mixing on ProTools is that it is
way too easy for mix data to be wiped and days of hard work to
disappear. Requiring us to stop work and rebuild from session back ups
or re-mix sections.

The behavior for button 'ALL' must be changed so that when there is no
selection made it does not write/wipe data over the entire mix. -It is too easy to loose data when for whatever reason a selection
has not been made prior to hitting the 'ALL' button.
-You really need to address this issue. Also working with a dual
operator mode compounds this issue as your 'partner' may stop or select
a range or start just before you select the range -all of which can mean
when you hit the 'all' button you wipe very valuable data.

Working in a Dual setup means if you select a range while the other system is in play then hit all you have wiped you mix.

Gil this is a very frustrating issue for dub stages working under time pressure and it would be great to get your thoughts on possible work arounds and/or solutions.

All the best

Bruno