Haven't updated for a while,
kinda pissed at the lack of 32-bit support in later versions but would consider a bridge plugin if the following are fixed as yet:
* Tracktion recreates different thumbnails for wav file clips, for each edit, takes an eternity on a large project to get back up and going.
* Tracktion recreates slowed down/sped-up versions of clips (elastique), for each edit.
* Tracktion fails, in some cases, to begin creating thumbnails until track is played or until you view that part of the edit.
* Tracktion creates thumbnails concurrently across all tracks rather than sequentially, ie. the slowest possible way you can ever process a bunch of files. Even worse on non-ssd.
* Tracktion fails to carry over frozen tracks between edits.
* Tracktion stores track freezes and wav thumbnails somewhere other than the project folder.
Does tracktion/waveform still do these stupid things?
-
- KVRAF
- 4054 posts since 8 Jan, 2005 from Hamilton, New Zealand
I make music: progressive-acoustic | electronica/game-soundtrack work | progressive alt-metal
Win 10/11 Simplifier | Also, Specialized C++ containers
Win 10/11 Simplifier | Also, Specialized C++ containers
-
- KVRAF
- 1713 posts since 15 Aug, 2003 from Indianapolis
Not sure about the rest, but these two are still the same. It seems to me the waveforms get drawn a bit faster than before (W9), but it's still incredibly slow on very large projects. I like W11 for simple projects, but it's unusable for me with larger projects.metamorphosis wrote: Sun Jan 24, 2021 5:34 am * Tracktion recreates different thumbnails for wav file clips, for each edit, takes an eternity on a large project to get back up and going.
* Tracktion creates thumbnails concurrently across all tracks rather than sequentially, ie. the slowest possible way you can ever process a bunch of files. Even worse on non-ssd.
I'm talking about 32 track live recordings of 2.5 to 3 hours long. Sure, these are huge files, but Reaper manages to do it in mere moments, and doesn't decide to randomly redo them every time you turn around.
Again, I like W11 a lot. It seems considerably more stable for me than any version in recent memory. I just can't use it for large projects.
-
- KVRAF
- Topic Starter
- 4054 posts since 8 Jan, 2005 from Hamilton, New Zealand
Ah, that sucks. Yeah even on 15-minute 32-bit 96khz renders of tracks it takes ages. It's a shame because it used to do things the right way in terms of scanning (sequential). But it never saved peak files per-project, only per-edit, which makes no sense.bk wrote: Mon Jan 25, 2021 1:11 amNot sure about the rest, but these two are still the same. It seems to me the waveforms get drawn a bit faster than before (W9), but it's still incredibly slow on very large projects. I like W11 for simple projects, but it's unusable for me with larger projects.metamorphosis wrote: Sun Jan 24, 2021 5:34 am * Tracktion recreates different thumbnails for wav file clips, for each edit, takes an eternity on a large project to get back up and going.
* Tracktion creates thumbnails concurrently across all tracks rather than sequentially, ie. the slowest possible way you can ever process a bunch of files. Even worse on non-ssd.
I'm talking about 32 track live recordings of 2.5 to 3 hours long. Sure, these are huge files, but Reaper manages to do it in mere moments, and doesn't decide to randomly redo them every time you turn around.
Again, I like W11 a lot. It seems considerably more stable for me than any version in recent memory. I just can't use it for large projects.
I make music: progressive-acoustic | electronica/game-soundtrack work | progressive alt-metal
Win 10/11 Simplifier | Also, Specialized C++ containers
Win 10/11 Simplifier | Also, Specialized C++ containers
-
- KVRAF
- Topic Starter
- 4054 posts since 8 Jan, 2005 from Hamilton, New Zealand
Another bizarre behaviour (and again, I don't know if it's present in T11):
when the edit is in it's 'rendering peak files' phase, if you zoom in to a part of the edit, then zoom back out again, Traction forgets that it's already rendered some of the peak files outside of the zoomed-in level and re-renders them all over again.
when the edit is in it's 'rendering peak files' phase, if you zoom in to a part of the edit, then zoom back out again, Traction forgets that it's already rendered some of the peak files outside of the zoomed-in level and re-renders them all over again.
I make music: progressive-acoustic | electronica/game-soundtrack work | progressive alt-metal
Win 10/11 Simplifier | Also, Specialized C++ containers
Win 10/11 Simplifier | Also, Specialized C++ containers
