[Cameron Warn]

I can’t say I’ve used Audition much, but just having a quick look on my 16 inch Catalina laptop it also doesn’t work for me.

It exported a sequence with its media, but didn’t open it in Audition when it did so. I also don’t seem to be able to send a clip to Audition at all, I only have the option of sending a sequence from the project panel.

I know that Adobe broke Dynamic Link engine with the 2020 bug update versions of Premiere and AE 2020, so perhaps it’s related to this, though I did have the base 13.0.0 app installed so maybe it’s something else.

I’m not very familiar with audition though, so I’m assuming it should load up the app when you export a sequence to it.

[Cameron Warn]

Sounds good.

I’ll have a play and see how I go. Thanks again for your help.

[Cameron Warn]

Lovely!

That seems to work quite well for keeping selected space and overall centering too.

If I need to keep the text lines and objects on the same horizontal level is it just a matter or changing the anchor point to the lower edge of bounding box, or is there a better way to do it?

Cheers

[Cameron Warn]

Did you recently upgrade to CC 2019? This version has an issue with the Legacy Title Tool (if that’s where your problem is) that has been reported.

Here’s a link to Adobe forums about it:
https://forums.adobe.com/thread/2550601

Believe a few suggestions are put forward with how to deal with it, but it’s a bit of a pain and even if you get it to show the tool tabs you want their sizing can be all over the place.

[Cameron Warn]

Not sure if this would work for you, but have you tried the ‘render and replace’ option for dynamic linked clips in Premiere Pro?

There’s a render time involved converting the AE comp to clips, but once done they’ll play nice in your sequence as are now actual media clips. If you need to adjust something, you then use the ‘restore unrendered’ option to change the clip back to the AE linked comp.

[Cameron Warn]

What version of Premiere are you using?

A bug has been introduced in CC2018 – especially the 12.0.1 version – where importing projects and sequences can fail. We reluctantly had to upgrade to CC2018, but not to the 12.0.1 version, as importing projects and sequences was part of our workflow.

If you’re on CC 12.0.1, I would suggest downgrading to the ash 12.0.0 version and see if that works for you, or go back to CC2017 where importing is fine. Another thing you could try is to tick the ‘Allow duplicate media during import’ option in the ‘Preferences’ ‘Media’ tab. This can help as sometimes if it is not selected it will not import sequences, though in previous versions I would not want it to do this.

The bugs a pain, and we wouldn’t have upgraded to CC2018 while unfixed, but one machine had used it on key projects which forced our hand. There is also a thread about this in the Adobe forums that you might like to read.

https://forums.adobe.com/thread/2397562

[Cameron Warn]

Don’t think the Mercury playback engine message relates to your issue. This is about the use of a Nvidia GFX card that the other editor had which your system does not.

I am trying to recreate your problem with the ‘OK’ option being greyed out, but have not run into this yet.

Have you tried exporting an XML from his projects and imported it into your own? Won’t fix the issue you are having but should get you working again.

[Cameron Warn]

Hi. Some questions for you.

How are you trying to import the other editors completed sequences? Are you importing directly through media browser or using an XML or similar? You say that you can’t retrieve the clips, does this mean you have been able to import his sequences but that the media does not appear online?

I regularly import other peoples sequences through media browser with no issues, but we are on the same platform and software version.

[Cameron Warn]

I believe this is also dependent on the wrapper as well as codec.

We use XDCAM HD422 in-house and export to .mov files. Premiere always re-renders for us even though we select ‘use previews’ which we have set to the same XDCAM codec.

If we exported to .MXF files we would get much faster exports as ‘use previews’ actually works.

Cheers

[Cameron Warn]

I don’t have AVID in front of me right now, but from memory you just need to force it to re-encode to XDCAM rather then using ‘same as source’.

We would get failures if ‘same as source’ was selected but it’s been a while since i’ve done it so can’t remember what options you get on the AAF export screen, or if I am just thinking about regular .mov export options.

I did not export to embedded files either, so don’t know if that makes a difference or not too.