Redesign for editability in GUI

Enhancement from earlier backlog.
-Annotation lista custom (user leszúrhat kommenteket?)
-Annotation lista autómenedzsmentes(Midi bar, perc-másodperc n darab ami látható)
-Régiólista (elnevezhetőséggel)
-Feladatlista (undo,redo-zható) kivágás, némitás hogyan?

This sw is not a complete DAW. This is a record engineer tool, to export recorded material to WAVs.
Now the displaying based on Fostex D80 self bookkeeping of the blocks, which contains the raw sequence list of the block regions. The actual gui implementation shows samples exactly this way. At this moment, the tool let select one region for exported part of the disk.
In the future, we would like to edit the project by this tool. Where edit means, to select which part of the record would be interest, and need to be exported later.
At the first step, we would like to improve the work of export workflow, to add multiple regions, also user annotations, and midi clock based ruler. (also processing of a recorded SMTP channel can be a new feature)
-List of regions: use-case: to select songs or deselect silence parts of the record. Deselected parts still visible.
Regions should be editable from gui, also automatic regions from silence detection should be goal.
-regions from input. use-case: record engineer add markers, or collects punch in-out points in a .csv file.
-the image file should be intact, editing of the file means gui collects a list of edit points. GUI should display curves based on both fdms and edits. (but this will be implemented later)
-User may need to add textual annotations for edit points, to help the work with the record. It would be nice to have a dialog/list of markers.
-Edit points based or separate database of volume and mute/solo automation.
-Exported regions may contains channel selection (in case of different regions may use different channels too).

No files, tests, or GUI entry points are named. Start by locating the GUI and export workflow, then clarify which part of the proposed region, annotation, ruler, undo/redo, and channel-selection work is in scope. Done should be defined as a specific, testable editing workflow rather than the full backlog.

Written by the indexing model from the issue text.