Sigh... I know, but that's almost as big a pain as any of these bugs. Hopefully it won't come back to bite me later on, but if it does at least it'll be no one's fault but my own :) Thanks for the confirmation on the workspaces. If that's an intentional design, the error message could stand to be a little more helpful. If it's a bug new to 2.7.2, well

So just to answer my own question... the problem apparently lies in having a Workspace name that is the same as any Folder that Avid needs to access. So our SFX folder was conflicting with our SFX workspace, and my "Evan" user settings were conflicting with my "Evan" workspace. Changing the directory names fixes it, we're going to test changing a workspace

Hello- I'm on a production cutting in 1080p/23.976 on 8-core Intel Macs, and we just upgraded to 2.7.2 with the hopes of fixing the disappearing bin issue. As things tend to go, you always trade one problem for another, but it seems that Intel Macs still have filesystem problems when connecting to a Unity. The problem we are having is that the new release

Any news on whether sending linked AAFs to PT still corrupts the media?

Hello- A little while ago I ran into the issue of Pro Tools corrupting media that was linked to by an AAF exported from Avid (I was on XpressPro 5.6.3 at the time), and I've seen posts and knowledge base articles acknowledging the issue both here and on Digidesign's support site. Does anyone know if this issue has been addressed in the release of MCA

Just wanted to throw my "Me Too" in there. Opening the bin directly in the EDL Manager works fine and takes negligibly more time, but it'd still be nice to have a fix for the bug. For me, the Get Current Sequence function still works great in a 23.98 project I was working on before. Where I get this error is in the 30i project I'm working on now. I

Great, thanks! --Evan

Has anyone submitted a request to add the option of seeing the entire thread by default when you click on a search result? If not, I'd like to make that request. As you said, the way it is now is 'kind of a pain.' Thanks, --Evan

Well, this is the part where I knock my head against the wall. It seems that the post house took care of the 2 frame delay, but what was throwing my sync off was the Desktop Play Delay. It was set way high, and when I brought it back down to 0 everything played in sync. I stepped through a few more of the 0 frame delay clips and the slates are all good

Sounds like modifying the start timecode is the easier fix, so I'll give that a shot. I've seen the audio delay setting, but since our audio was already behind the video, delaying it more somehow seemed counter-intuitive. Thanks again, I'm going to give your suggestions a try now. --Evan