Thanks very much! [quote user="Kevin Klimek"] I'm looking into this and will report back when I find out something. [/quote]

I don't have a solution but have experienced this same behaviour. With Marquee I've just learnt to 1. save before opening Marquee and 2. check that the title in the timeline has actually updated. You're probably right that it is to do with working on different suites. cheers Campbell

Mentioned this in another thread but have just recreated the issue with help from Howard Kramer so thought I'd start a new thread. Moving a sequence with Titler+ effects from a Mac to a Windows suite results in the Windows suite crashing. If I remove the titler+ effects from the sequence it opens fine. If we create Titler+ effects on the Windows

Thanks for the new Titler+, will make a huge difference to our workflow. Two things I've come across so far. 1. Underline doesn't get an edge when you add an edge to text. 2. Issues going from Mac to PC. I just tried moving a sequence with Titler+ effects from Mac 10.13 suite to Win7 suiet. First time the sequence opened but the titles were

I also use Subcap regularly but our work systems are still on 8.7.5. I just tested at home on my PC with 9.2 and didn't have any problems importing the file. I use Belle Nuit to create an Avid DS .txt subtitle file and it's working fine. That's probably not too much help but thought I'd report anyway. I can try it on a Mac tomorrow to

Sorry I just realised you're using MC First, so I don't actually know if this is the same as regular MC.

How are you doing the resize? You should be using FrameFlex which is available in the Source Settings (right-click on the clip in the bin) or once you've edited a clip into the timeline the FrameFlex effect will be available in the Effects Editor for clips that are larger than the project raster.

I've also found with shared storage that the number of bins in a project affects performance. In ongoing projects I was finding it took up to a minute or more to open a project or auto-save, even if only one bin was open. A new project with only a few bins fixed it. And as mentioned already, simplifying what is in your bins as well.

It just seems to be SAS exports. I've tried H264 and PhotoJpeg codecs as well as Custom settings to DNxHD and they all work. But SAS to DV or DNxHD give me that error message.

I posted last week on AE of FB but didn't get any answers so I'll post again here. When I try to export a SAS qt to a network drive (either Editshare or Synology NAS) I get the error: UPDATE_MOVIE_RESOURCE_FAILED I can export to a local drive with no problem, only network drives are a problem. The network drives are mounted with SMB (Native