bug with object grabber

[PTLance]

1. Created new session
2. Imported some tracks from another session which were known to play OK
3. Clips played OK at their imported timecode
4. Performed 'object grabber' selection of a bunch of clips
5. Cut & pasted these to new location against movie
6. Hit play
7. As cursor gets to clips, Pro-tools hangs up badly (type 2 error, freeze and unable to force quit etc)
8. Repeated above with clips from copied session (i.e. different audio), same result
9. Disk warrior unable to fix problem and also having problems seeing mounted scusi drives
10.Repeated above again and checked automation of clips after moving using object grabber-found big corruption of automation graph.
11.Deleted corrupt automation and hit play, pro-tools still hung up

Could not get it to work using object grabber tool at all.

Finally, I created a new session, imported the tracks and moved the clips

individually using the conventional grabber tool and it played fine.


This suggests corruption may be occurring that is related to object grabber mode and that extends beyond automation only, perhaps to accessing the file info itself.

I've had it happen on three different systems.
PT 5.1.1
OS 9.0.4
Mix rigs

Anybody else see this?

[DigiTechSupt]

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:<HR>Originally posted by [email protected]:
9. Disk warrior unable to fix problem and also having problems seeing mounted scusi drives<HR></BLOCKQUOTE>

I think this particular issue is creating problems for your entire system. If Disk Warrior cannot fix problems it encountered, then I would urge you to back up and format the SCSI drive(s) with ATTO EPT v2.3.2.

Restore the data and try again.

Brent

[PTLance]

The problem with the drive only occured after it crashed the first time. Restarting and running DW then worked. Went back to the session and repeated above with same results.
I will re initialize and try again. Can you use Atto 2.7? Or is 2.3.2 better? Thanks.

[DigiTechSupt]

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:<HR>Originally posted by [email protected]:
Can you use Atto 2.7? Or is 2.3.2 better?<HR></BLOCKQUOTE>

-ATTO EPT v2.7 should only be used if running Mac OS 9.2 or later. Therefore, you should with v2.3.2 for best compatibility with your system.

Brent

[clutch]

I also have this problem and can re-create it on each of our 14 TDM systems.
The problem definitely involes the object grabber tool and seems to only occur in sessions which contain LCR bussing (although haven't tried 5.0 or 5.1 yet).

DIGI, could you try this for me:
create a new session with an LCR ouput and buss some stereo or mono tracks to the LCR.
Create some pan and volume automation on the tracks within the audio regions.
Use the object grabber tool to move one or two of the audio regions over others with automation on them. If the issue doesn't happen at first, keep moving around regions to different tracks until it does.
"Rogue nodes" are created which will crash the session in the way described when you try to play through them. I can send you some pictures of the unreal graphs we have been getting if you like.

We use FWB drivers throughout and have not had a problem with them. It also happens with sessions that exist exclusively on Firewire drives. I fail to see how the hard drive drivers could create the dodgy automation graph. We don't have any mounting issues with any of them.
Are you telling me I really have to reformat more than a terabyte of removable shuttles to fix this? Please Brent....nooooooo...!!!!!!
It would not be worth the time or effort. We just need to get this to work...
Please get in touch if you need more information than this.

chris

[Ray JB]

I'll second the dodgy pan graph stuff! Sorted out a number of crashes (type 2 error crash burn die...) with a session with a number of LCR tracks and where the object grabber tool had been used to moves regions around. Try it yourself.... you'll eventually find that the pan graphs look very wierd! Once those "rogue nodes" are deleted then your session will not crash again!

IMHO not a disk issue.

Feedback?

[PTLance]

Well I tried everything Digi said and it still happens. Digi any ideas? This BUG really needs to be fixed.

[clutch]

BUMP
this is costing us hours and hours...
come on Digi... [img]images/icons/mad.gif[/img]

[PTLance]

I've had three different editors on three different systems have this same problem. Causing a lot of grief...WASSS UPPP?!?!

[clutch]

BUMP
not letting this one get away...