Help - Audio regions greyed out

[sidereal-studios]

I tried a search on this, but couldn't find anything...

A very important audio region now appears as a grey box (no waveform) in my current session. I had renamed the FireWire drive where the session is located since last time I saved, which caused the "disk allocation" window to pop up. That may or may not be a factor.

The file is "bass_07-26-MXBM-01". I tried backtracking to dragging in "bass_07-26" to reapply the Audiosuite plug-in, but that didn't help.

Using the import audio dialog doesn't work, and Sherlock is no help either. Ideas?

[the dude]

there are couple of reasons this happens
1.the track has no output assigned
2.the track has no voice assigned
3.the track has been made inactive

[sidereal-studios]

Thanks for the reply. I should have been more clear... It's just one particular audio region. The rest of the regions on the audio track are fine, so it couldn't be any of the items you mentioned.

I suspect a missing or corrupt file. If it's the former, I'm wondering where it went.

[the dude]

what if you try bringing into a new session all by its self?

[img]images/icons/confused.gif[/img] [img]images/icons/confused.gif[/img] [img]images/icons/confused.gif[/img]

[FajitaTone]

Try recalculating invalid waveforms, if the audio does not play back then maybe you need to run diskwarrior or something on the drive. You did all the normal tap dancing with preferencaes and stuff already, right?

good luck!
[img]images/icons/smile.gif[/img]

[Rail Jon Rogut]

Select the region and it should be highlighted in the region bin - use the region menu and select Show Full Pathnames... check if the path is valid.

Rail

[cakehead]

it seems this file "bass_07-26-MXBM-01".
no longer exists...did you write over it, ( applying another audiosuite plug in for example) and close the session without saving it??????

the last "saved session' would be therefore looking for the file "bass_07-26-MXBM-01".

just a thought

[sidereal-studios]

Thanks all. I think I've figured out the reason but not the solution. Pilot error combined with PT's stupid file management system.

I was originally working off a Digi Drive for this session. Then I moved the entire session over to my FireWire drive and continued working from that drive. I did this in order to wipe the Digi Drive clean to record a new session.

I had printed an AudioSuite plug-in to that region after the move, but prior to wiping the drive clean. Of course, PT didn't understand that I had moved the session, and made the bounce to the Digi Drive rathar than the FW drive. Then I wiped the Digi Drive clean.

Why doesn't PT understand that when you move a session, any bouncing or printing activity should now shift to that new drive? Annoying.

(btw, this was revealed when I saw the full path names.)

[Rail Jon Rogut]

When moving a session between drives, I'd recommend using the "Save Session Copy..." command rather than dragging your session in the Finder - it may help.

Otherwise after copying the session to the new drive - unmount (or remove) the original drive with the session and open the session and PT will know that the old path is invalid and give you the disk allocation dialog.... Check the new disk allocation, say OK and save the session.

Rail