View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000745 | ardour | features | public | 2004-10-27 14:25 | 2008-11-20 23:43 |
| Reporter | schrotie | Assigned To | paul | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Summary | 0000745: Caching tracks | ||||
| Description | It would be very usefull to be able to cache tracks. Currently what you can do with ardour is limited by your system (cpu, disk ...) speed. My PC at home can e.g. handle one or two dozen effects on a dozen tracks, my recording PC handles about twice that load. Now the most flexible way to implement my idea would be a "plugin" that you can drop anywhere in pre- or post fader plugins. You hit the cache button and it starts caching the track with all effects up to the point where the caching "plugin" is located. If you now play the track, the cached version will be used from the point of the caching "plugin", all efects before that point are bypassed. If the caching "plugin" is bypassed, the original track is used and the effects are processed again. It is obviously possible to achieve the same effect by exporting tracks and then using the exported versions for further mixing. But the caching "plugin" would much accelerate and simplify the process while yielding more flexibility. If this concept is cleverly combined with busses, it would yield unlimited power to ardour users. Want to mix 100 tracks using 300 effect plugins? Well you will have to exercise some patience while caching, but you will be able do whatever you like even with modest hardware. And most of the time you will only cache one track to proceed mixing others, so the wait will be short if you don't overdo it with 100 tracks and 300 effects :-) | ||||
| Tags | No tags attached. | ||||
|
|
please consider: context-click on track -> "Freeze" this follows 90%+ of the model used by other DAWs to do what you want. your caching plugin is an interesting idea, but it would be exorbitant in its use of disk space, which would be an invisible resource consumed by it without users realizing what they were doing. in addition, it would be a very complex plugin to write correctly. consider what happens when the caching plugin has never "heard" part of a track that the playhead finally gets to. |
|
|
The freeze functionality meets my needs perfectly. While the proposed plugin solution would be more flexible, the flexibility would likely not be needed by many users and would not justify the implied complexity and less intuitive user interface. It astonishes me though, that I have not discovered the freeze feature earlier, even though I needed it badly. Maybe the function should also be available through the plugin context menu of the mixer (and be called freeze track there or something ...). I found a bug related to the freeze function, see 0000747 |
|
|
an apparently satisfied customer, at least for this issue. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-10-27 14:25 | schrotie | New Issue | |
| 2004-10-28 01:05 | paul | Note Added: 0001544 | |
| 2004-10-28 01:05 | paul | Status | new => feedback |
| 2004-10-29 22:31 | schrotie | Note Added: 0001547 | |
| 2005-02-07 03:37 | paul | Status | feedback => resolved |
| 2005-02-07 03:37 | paul | Resolution | open => fixed |
| 2005-02-07 03:37 | paul | Assigned To | => paul |
| 2005-02-07 03:37 | paul | Note Added: 0001968 | |
| 2008-11-20 23:43 | seablade | Status | resolved => closed |
