[Daniel Corcoran]

Thank you so much Jeff for commenting.

Yes I generally export to h.264 and have never tried an intermediate codec. I used to use wmv or h264 when using CS5.

I think, though, I seem to have found a solution to the problem. It doesn’t solve the root of why ME opens but doesn’t receive the files from PP when using FILE>EXPORT, but at least I can export now! What works is if I make a subsequence of what I want to export and then drag it to AME2019’s queue window, it receives it without any problems – just as long as I save the PP project just before dragging the sequence. If I don’t save it first I get an error saying that it’s missing some file (which it isn’t!). Maybe this is how many people do it – I’d always just done FILE>EXPORT.

But this method only works now that I have AME2018 also installed (but not open)!

PP is still crashing regularly though.

In terms of plugins, I only have a few transitions from FilmImpact.net

Thanks for your tip about it not necessarily being a solution to switch platforms.

Very grateful to you.
Have a good day!
Dan

[Daniel Corcoran]

Many thanks Robert for your comment and good wishes.
Yes I wonder whether CS5 or CS6 would have been fine for me, but it seems ok at the moment.

The encoding problem seems to have been solved by using ME2019 but having ME2018 installed as well, and also by dragging the sequence across to ME rather than using File>Export.

Many thanks,
Dan

[Daniel Corcoran]

Thanks Vince,
Many thanks for your comment.
Yes you’re right it was a big from CS5 and I tested the import out on the trial version of PP before buying it. The only major problems I found were:
– it didn’t carry across any transitions (of which there are many) in my timeline as it is the backdrop of a theatre production
– it broke some of the audio tracks up

On CS5 I used to encode to wmv or h264 (both took ages especially the double pass for wmv)
Now, I only really use h264 for projection onto a big screen.

In terms of encoding without ME, I’m sorry I’m going to show some ignorance here: I didn’t know there was an alternative as on export, it’s ME that normally automatically just did it.

Very grateful for your help.
Dan

[Daniel Corcoran]

Hi Jon,

I’ve had the same issue for a few weeks. Hope this helps you!

I’m using…

PP CC 2019: Version 13.0.1 (Build 13)
AME CC 2019: Version 13.0.1 (Build 12)

Windows 10 Home 64bit (10.0, Build 17134)
Dell XPS8900 BIOS 2.4.0
Processor Intel Core i7-6700 CPU 3.40GHz (8CPUs) 3.4GHz
RAM 32768MB
GPU GeForce GTX745 (Driver 416.81) (11.08.2018)

Adobe recommended a few things:

– upgrading GPU driver,
– trashing preferences,
– renaming ME’s folder to “old##.#
These worked, but only momentarily.

Last night, I thought I’d solved this by copying my entire 3 hour timeline into a fresh new project. And lots of sequences encoded (CUDA) no problem over night (apart from one sequence where I had the Error 1609629695 which I’ve never had before but seems to have been a mystery error in Adobe’s community for a number of years.)

But this has only worked once. Having rebooted to try and solve this 1609629695 error, I’m back to square one and it won’t encode again!

I’ve copied/pasted into a fresh project yet again, trashed the preferences, renamed ME’s “13.0” folder to “old130” etc and it still doesn’t work.

It’s as if once PP knows you’ve got a remedy to it’s illness, it gets resistent to the treatment!

Also, what is even more frustrating, PP is suddenly saying that my hardware doesn’t support CUDA anymore for “H.264 Highbitrate” and my only option is software encoding.

Since I invested in “upgrading” from CS5 (which never let me down) only in the Summer, I’ve had nothing but problems!

I hope this idea of copying and pasting into a new project works at least once for you but you’ve probably already tried it.

All the best,
Dan

[Daniel Corcoran]

James,
Thank you so much for your reply. I’ve been away all this time and have just checked back and have seen your post.
I will try your solution.
Very grateful to you!
Dan