delete rendered files elastic audio BUG!!!

[carlos santana]

ok

first i open the sesion im going to work with:

open a new audio (stereo) trak.
set the imputs and outputs
reccord enable the trak.
reccord the trumpet in this case

once i finish recording i consolidate the regions into just one soundbite by pressing (shift+alt/option+3)

then i enable the elastic plugin to monophonic.
wait till it analyses the soundbite
once the soundbite is online
i select the analsys tab
erase all the analysis markers.
then i create all the markers one by one on my own (better then the auto analysis) i do this by right clicking (add analysis marker)
then i select the warp tab
move the markers around to edit elastic
after im done warping i select the elastic plugin and disable it
when it promps me if i want to commit ( i do)

after that i select the stereo soundbite and i consolidate it wich generates a new audio file

after that i select unused files (shift+command+U) and delete then (shift+command+B) to delete them.

when im done i close the session and inside the rendered files folder i still have both .wav files and .aan files

please digi advice

[DigiTechSupt]

Ok - I see what you're seeing, to a degree. I'm going to have to look further into this to see what's causing it.

One question - you say:

when it promps me if i want to commit ( i do)

after that i select the stereo soundbite and i consolidate it wich generates a new audio file

Is there a reason you're doing that last consolidate? Are there multiple regions you're consolidating?

The reason I ask - when you commit, Pro Tools is already creating a new audio file, so doing the consolidate again seems redundant.

[carlos santana]

i re-consolidate to make shure it creates a audio file into the audio files folder

(yes it is redundant).

even if i skip this step the issue will still appear

[carlos santana]

please digitechsupport

help

should i just delete the files from the workspace browser as a workaround till you guys fix this...

please advice

[DigiTechSupt]

should i just delete the files from the workspace browser as a workaround till you guys fix this...

Yes, I would do that for now.

[carlos santana]

thanks

[carlos santana]

bump

[holden]

Carlos-

Just so you know, you are not alone. I also work at 96k/24b and have the same space problems due to what should be obsolete rendered elastic audio files taking up huge amounts of disk space. I have no solution, only a workaround: Use "Save Copy In ..." to make a copy of the session and associated files on another disk, choosing to copy all audio files, any plug-in settings you want to keep, etc.. I also choose "Don't copy rendered elastic files". Upon opening the new copied session I choose to re-render rendered EA files. Make sure you also copy any documentation files and old session files you want to keep. Then once I've checked that I can work with the new copy, I trash the old session and its associated files, and put the new copy in its place. It's a PITA but it frees up all that space that had been taken up by obsolete rendered files. I reclaim double digits GBs of disk space per song this way.

DigiTechSupt-

My process is to
1. Comp from recorded playlists.
2. Activate real-time elastic audio on the comp'd track.
3. Edit each section of the comp using EA warp markers.
4. Cross-fade to connect sections of the comp.
5. Switch to rendered processing.
6. Copy the edited comp playlist to a new playlist.
7. Consolidate the new playlist and lock it.

Note that the transition of step 5 can be problematic. I often find that rendered processing produces unacceptable artifacts that don't appear in real-time EA for the same algorithm, visibly and audibly shifting the signal with respect to the real-time version, so lately I've been recording the edited real-time EA comp to a new track to work-around such problems.

[DigiTechSupt]

We are aware of the problem and are working on a fix. No need to bump the thread - when we fix it, we'll make an announcement about the CS update or version that fixes it.

It seems in the preliminary investigation that these files are being left due to the consolidate process. Consolidating seems to break the link that let's Pro Tools keep track of which rendered files are actually being used and which can be deleted.

[carlos santana]

thanks
no more bumping