Why is the park buffer being saved with the show file in the 2.4 update?

Why is the park buffer being saved with the show file in the 2.4 update? Whenever I change something in park I am getting an asterisk next to the name of the show file saying I haven't saved. I have relays I park on at the start of the day and unpark at the end. During a show run, when you don't necessarily want to change anything, this feature effectively nullifies the asterisk for a user who needs to park things on a daily basis and was using it to track if they had accidentally made a change. Was this an intentional choice to remove that kind of functionality?

John728 over 8 years ago

Saving the park buffer would help someone who shoots on a sound stage where he needs channels parked and also packs up the same console to go out and shoot on location. When he comes back to the sound stage, he reloads the appropriate show file and the channels are parked again.

If I were you I would build a macro to park your relays with Shift+Update at the end of the macro. Then the asterisk goes away and you can use it as intended.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
RickR over 8 years ago in reply to John728

FYI
Many of my clients expect the park settings to save with the show file. Typically they are schools or churches and not the most technically advanced. With non-dims for power to LEDs and movers becoming common in smaller settings, managing them is an issue for these folks.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Gregg over 8 years ago

My workaround for this was to create a sub (in my case I use subs 298 through 300) for the channels I used to park and unpark regularly and then make macros to put the sub(s) and full and out. The subs are never mapped to physical faders.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
dsmurfin over 8 years ago in reply to Gregg

In actuality the Park buffer has always been saved with the show file, it's just that now there is an option to load it when you open a file.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Gregg over 8 years ago in reply to dsmurfin

Dan,

Prior to 4.2 Parking channels would not cause the * to appear, for those of us that power on automated fixtures and power them off at the end of the day Park used to be a convenient way to do that . Now it causes the * to appear when, for our purposes, the show file does not need to be updated.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Cameron Swenson over 8 years ago in reply to Gregg

Then don't update your show
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Gregg over 8 years ago in reply to Cameron Swenson

Which defeats the entire point of having the * in the first place.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
dsmurfin over 8 years ago in reply to Gregg

This is exactly how I work also but it hasn't really bothered me. Technically making a change in Park is changing the show file as the buffer is stored in it, hence the *. As I mentioned though this has always been the case. I expect 2.4 just changed to show the star as well because now you can recall park so it becomes relevant whether you've saved it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
luke.delwiche over 8 years ago in reply to Gregg

An unmapped shielded sub works in largely the same way - would that be a solution? You could use a macro to say [Sub][x][At][Full]. If that Sub had the channels in an IP/Preset called "Power", this has the potential added benefit of showing on the Live display.

As this is a playback action and not changing the Park buffer, you won't get the asterisk.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel