Field Recorder Assertion Errors

[feakerboo]

I'm having the EXACT same behavior. Updated to 10.3.5 and no change. Deleted prefs/databases and tried deleting unused and no dice. I'm seeing the same thing: it was working fine for weeks and all the sudden it stopped.

System:
Mac Pro 3,1 8 Core 6Gig RAM
PTHD 10.3.5
Running native right now w/o My HD3 cards in

[digiton]

i have the same thing

i open a session out of the session files backup from 2 days before and the function is still working pefectly

so the problem is not in the protool itself but in the sessionfile, in betwenn we have importet files for the sounddesign, i guess that is the reason,
regards george

one day someone my find the problem

[digiton]

ok i found the problem

one file from a old archive with letters that are no longer accepted had to be renamed. the files are in the renamed folder an had sort of nummer endings.
horse 7867
the fact that i simply erased the new numbers generated by protool in
horse
and remove the file renamed by protool horse 7867 did the job

it works again

this thing was taking me 2 hours
help it helps all of you
george

[Danny Caccavo]

We have found some crash situations on AAF tracks when we try to expand to new tracks - in our case it had to do with one or more clips on that track that did not have any matches. So if you tried to expand the whole track it would crash, or if you selected a bunch of clips and right-clicked - it would instantly crash. So in one case I expanded the track in small pieces, learning to avoid the trouble clips. Time consuming, but it worked.

Another time we had a crash that I traced to the presence of those MC database files. I removed them and the crashing stopped.

Hope that helps.

I reported them to Avid.

[thierryd]

We had the same problem as Danny recently. Crashing when expanding the entire track or when expanding too many clips at the same time on that track. But this problem was not due to non matching expand clips. For some reason PT put very long fade outs on certain expanded clips, extending those clips beyond others down the timeline. I think those overlaps crashed PT and we had to select groups of clips to avoid this. This happened in both PT 10 and 11, with the advantage of 11 having much quicker restarts to be back up and running (no crashes would be even better of course). The AAFs come from a MC and at the start of the project rushes were wrongly synced (losing metadata), which was correctd later in the MC. I think that some of the above issues started ther as I have never seen this fade problem before.
The assertion errors of the OP we have seen as well. Sometimes a restart helps, sometimes it's related to identical clips in the session (the AAF and the expanded ones that somehow create a mismatch). Sometimes it helps to temp rename the Audio Files folder before the session starts to put all those files offline and have PT look only for the original expanded soundrushes.

Greetings

Thierry

[gwhatley]

This may possibly address the problem of the OP:

http://protools.ideascale.com/a/dtd/...79?submitted=1

Things were working flawlessly for me at first, and then suddenly assertion errors popped up. Soon I discovered I had done a search for a clip name, and once I selected "Clear Find", the assertion errors stopped.