![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
![]()
For my workflow Freeze is a great approach to save resources.
But for a long time it was causing quite frequent crashes/hangs. As of 2023.3 that seems to be better. But now I notice that for a (relatively) complex session that I have been working on (on and off) for nearly a year or so, where I am using Freeze and Unfreeze tracks / folders to conserve resources, the Rendered Files folder is 20,341 files + 68.3GB! I notice that if I Freeze a track, pro Tools creates a new set of temporary files in the Rendered Files folder. But if I Unfreeze that track the track those temporary files are still there. So I end up with a series of temporary files for the track - of which only the latest is valid. With Elastic Audio temporary files Pro Tools takes responsibility for cleaning up unused files from the Rendered Files folder. [p1055 Reference Guide]. But Pro Tools does not do so with temporary Frozen files in the same folder. There appears to be no way to to tell what temporary Frozen files in the Rendered Files folder are used or not? If Pro Tools can do cleanup for Elastic Audio temporary files from the Rendered Files folder, it can also do that for temporary Frozen files in the same folder. That is clearly a bug in the implementation of Freeze / Unfreeze. I have raised an issue with Avid Support #04798296 - but their response if that Pro Tools is "working as designed". I understand that keeping duplicates / old files in the Rendered Files folder is "normal behavior". My issue is that it places the burden of "frozen" file maintenance on the user - when Pro Tools is well placed to do so (as it does for Elastic Audio temporary files). And it is not clear how a user can identify unused files in the Rendered Files folder for deletion. In my huge Rendered Files folder example there are files going back 12 months or more - some of which are valid (where I haven't worked on that track since) and some of which are not (there are more recent duplicates). ------------------------------- Windows 11 build 22621.1105, Pro Tools 2022.12 Operating System Windows 11 Home 64-bit CPU Intel Core i7 8700 @ 3.20GHz 42 °C Coffee Lake 14nm Technology RAM 64.0GB Dual-Channel DDR4 @ 1070MHz (15-15-15-36) Motherboard ASUSTeK COMPUTER INC. PRIME Z370-A II (LGA1151) 28 °C Graphics HP w2408 (1920x1200@59Hz) RAVEN MTi2 (1920x1080@59Hz) Intel UHD Graphics 630 (ASUStek Computer Inc) Storage 465GB Samsung SSD 860 EVO M.2 500GB (SATA (SSD)) 33 °C 1863GB Seagate ST2000DM006-2DM164 (SATA ) 29 °C 1863GB Seagate ST2000DM006-2DM164 (SATA ) 31 °C 1863GB Western Digital WD Blue SN570 2TB (Unknown (SSD)) 3725GB Western Digital WD Elements 25A3 USB Device (USB (SATA) (SSD)) 33 °C Optical Drives HL-DT-ST DVDRAM GH24NSC0 Audio Universal Audio Thunderbolt WDM
__________________
Pro Tools 2022.9 Windows 11 (up to date) UAD Apollo 16x + 8x Intel Core [email protected], 64.0GB |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Frozen files | Ride2 | Pro Tools 2019 | 24 | 06-24-2022 05:02 AM |
Missing frozen files | marcodeangelis | Pro Tools 12 | 3 | 05-18-2022 08:55 AM |
Rendered Frozen Files Missing | Jon_Atkinson | Pro Tools 12 | 8 | 08-24-2018 10:00 PM |
Where are my frozen files? | ripekeai | Pro Tools 12 | 6 | 12-29-2015 02:55 PM |
A Workaround to Edit Frozen Files | Wall2Wall | Pro Tools 12 | 1 | 12-27-2015 12:12 PM |