View Issue Details

IDProjectCategoryView StatusLast Update
0002209ardourbugspublic2020-04-19 20:13
Reportergiso Assigned Tocth103  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Target Version3.0-beta1 
Summary0002209: freeze/unfreeze and editing multiple snapshots conflicts
DescriptionIf in one snapshot a track is freezed, then a new snapshot created, selected and edited, all regions are replaced by new regions (new files), in the track context menu only the option "unfreeze" but not the option "freeze" appears. Unfreezing will restore the original regions of the first original snapshot, without the possibility of undo, i.e., all edits in the later snapshot are lost.

Version is ardour 2.4 compiled on Fedora core 6.
Tagsfreeze, snapshot

  Users sponsoring this issue
Sponsors List Total Sponsorship = US$ 25

2010-05-01 00:00: djdualcore (US$ 25)
  Users sponsoring this issue (Total Sponsorship = US$ 25)

Activities

giso

2009-01-07 22:39

reporter   ~0005575

The behaviour is somewhat different in 2.7.1: It is now possible to correctly unfreeze a snapshot of a session with frozen tracks, but this snapshot can not be saved (error message: "programming error: illegal AutoState type: 24", with the only option to press "exit").

cth103

2009-10-29 00:20

administrator   ~0006929

Last edited: 2009-10-29 00:20

Giso's report is confirmed:

new session
create snapshot "1" and switch to it
add track & record something onto it
freeze track
save
create snapshot "2" and switch to it
unfreeze track
save
-> "programming error: illegal AutoState type: -1267201456"

cth103

2010-05-11 23:31

administrator   ~0007872

Can no longer reproduce this in A3 SVN. Can anybody else?

djdualcore

2010-05-22 01:13

reporter   ~0007972

Bounty paid.

cth103

2010-05-22 01:26

administrator   ~0007974

Thanks!

system

2020-04-19 20:13

developer   ~0021705

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2008-04-21 20:13 giso New Issue
2009-01-07 22:39 giso Note Added: 0005575
2009-03-08 17:23 giso Tag Attached: freeze
2009-03-08 17:23 giso Tag Attached: snapshot
2009-10-29 00:20 cth103 Note Added: 0006929
2009-10-29 00:20 cth103 Status new => confirmed
2009-10-29 00:20 cth103 Note Edited: 0006929
2010-05-01 00:00 djdualcore Sponsorship Added djdualcore: US$ 25
2010-05-01 00:00 djdualcore Sponsorship Total 0 => 25
2010-05-01 02:22 cth103 cost => 0.00
2010-05-01 02:22 cth103 Target Version => 3.0-beta1
2010-05-11 23:31 cth103 Note Added: 0007872
2010-05-11 23:31 cth103 Status confirmed => feedback
2010-05-22 01:13 djdualcore Note Added: 0007972
2010-05-22 01:26 cth103 Note Added: 0007974
2010-05-22 01:26 cth103 Status feedback => resolved
2010-05-22 01:26 cth103 Resolution open => fixed
2010-05-22 01:26 cth103 Assigned To => cth103
2020-04-19 20:13 system Note Added: 0021705
2020-04-19 20:13 system Status resolved => closed