Ticket #562 (new planned)

Opened 2 years ago

Last modified 23 months ago

semantics of deleting a track

Reported by: ichthyo Owned by: ichthyo
Priority: grave Milestone: 1alpha
Component: lumieraProc Keywords: design
Cc: Blocked By:
Blocking: #306, #550

Description

See in TiddlyWiki renderengine.html#TrackHandling
The considerations there are partially outdated now, but basically correct.

We have to distinguish some cases

  • deleting a track asset. Is this even possible, given the fact that track assets are created on referral?
  • deleting a track MObject. Do we want to allow that? Usually, MObjects are handled automatically. Thus we'd need a dedicated purge function
  • removing a Placement<Track> from the session. The PlacementIndex doesn't allow this, unless the scope defined by this track is already empty. Do we want/need a "kill complete scope"-operation?

The mentioned wiki page also considers a functionality similar to Ardour's "Playlist". But meanwhile it looks that we won't get this as a sideeffect from track handling. But, on the other hand we have sequences now? Is that reasoning valid?

Change History

comment:1 Changed 2 years ago by ichthyo

  • Blocking 550 added

comment:2 Changed 23 months ago by ichthyo

  • Type changed from todo to planned
  • Milestone changed from 0integration to 1alpha

important, but not relevant right now

Note: See TracTickets for help on using tickets.