New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Snapshot Visibility Bug #757

Closed
Poofox opened this Issue Aug 11, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@Poofox

Poofox commented Aug 11, 2015

Win7 x64
SWS 2.8.0 build 0

Problem: In certain situations visibility snapshots are saving/recalling custom filter options instead of track visibility.

Steps to reproduce:

  1. Open Snapshots and select any custom filter options
  2. Use action _SWSSNAPSHOT_VISMODE to switch to visibility mode
  3. Save new snapshot

Expected: I've saved a new visibility snapshot

Actual Result: I have actually saved a new custom snapshot with most recent custom settings

Why it's an issue: I've been using cycle actions to switch between different sets of visible tracks. Recently I noticed recalling these snapshots were sometimes undoing extensive mixing work instead of changing track visibility. Finally noticed that it was because my "visibility" snapshots were actually custom snapshots, recalling various mix parameters, even between loading project sessions.

@Poofox

This comment has been minimized.

Show comment
Hide comment
@Poofox

Poofox Aug 16, 2015

Afaict, both the actions _SWSSNAPSHOT_MIXMODE and _SWSSNAPSHOT_VISMODE are broken. They appear to change the mode in the Snapshot window, but new snapshots do not use the correct settings, instead using whichever options are checked (and greyed out) in the Filter under "Custom."

Poofox commented Aug 16, 2015

Afaict, both the actions _SWSSNAPSHOT_MIXMODE and _SWSSNAPSHOT_VISMODE are broken. They appear to change the mode in the Snapshot window, but new snapshots do not use the correct settings, instead using whichever options are checked (and greyed out) in the Filter under "Custom."

Jeff0S added a commit that referenced this issue Aug 26, 2015

@Jeff0S

This comment has been minimized.

Show comment
Hide comment
@Jeff0S

Jeff0S Aug 26, 2015

Member

Thanks for the detailed report Poofox (that helped!) , should be fixed in the next pre-release

Member

Jeff0S commented Aug 26, 2015

Thanks for the detailed report Poofox (that helped!) , should be fixed in the next pre-release

@Jeff0S Jeff0S closed this Aug 26, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment