View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000353 | ardour | bugs | public | 2004-03-24 11:45 | 2008-11-20 23:36 |
| Reporter | timbyr | Assigned To | paul | ||
| Priority | normal | Severity | trivial | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Summary | 0000353: What does the "space" as reported by ardour indicate? | ||||
| Description | I assume that space indicates how much recording space is available by looking at the sample rate and bit depth. I was thinking it may be more accurate to base the space available on the track count aswell. So that if a session has 16 tracks it accurately represents how much recording time is available, assuming it doesn't allready, although it doesn't appear to. | ||||
| Tags | No tags attached. | ||||
|
|
its a measure based on single-track time. so if its says HH:MM:SS, then the defined session RAID path (typically just the session directory) contains enough time to record a single track that is HH:MM:SS long. if you record 10 tracks, 1/10th that, and so forth. |
|
|
we don't use the number of tracks because there is no way to know how many tracks will be used for recording. some of them may already be "set up" with their data. i tried both ways - they are both confusing, this one is less so but as usual requires documentation. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-03-24 11:45 | timbyr | New Issue | |
| 2004-03-24 11:45 | timbyr | => timbyr@pacific.net.au | |
| 2004-03-24 11:45 | timbyr | Name | => Tim Mayberry |
| 2004-03-24 13:26 | paul | Note Added: 0000585 | |
| 2004-03-24 13:28 | paul | Note Added: 0000586 | |
| 2004-03-24 13:28 | paul | Status | new => resolved |
| 2004-03-24 13:28 | paul | Resolution | open => no change required |
| 2004-03-24 13:28 | paul | Assigned To | => paul |
| 2008-11-20 23:36 | seablade | Status | resolved => closed |
