Premiere Pro CC (2018) Missing my custom presets

Explorer ,
Oct 19, 2017 Oct 19, 2017

Copy link to clipboard

Copied

Just updated all CC products to 2018 versions.

Opened Premiere Pro CC only to find that my custom export presets have disappeared. Why don’t Adobe warn people about this? Or is there a way to get my presets back?

Then I realised I still have a folder for Premiere Pro CC (2017) in Applications. So I tried opening the app only to get the message: ‘The application “Adobe Premiere Pro CC 2017.app” can’t be opened.’ Please tell me there IS a way to open this app so I can at least make a note of my previous settings? And if not, what is the point of the app being there at all?

Views

19.6K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Oct 19, 2017 Oct 19, 2017

Copy link to clipboard

Copied

Your Export presets should still be on your system unless you deleted them.

Quit Premiere. Go to Documents > Adobe > Adobe Media Encoder > 11.0 (or whatever version you created them in) > Presets. Copy your custom presets and paste into Documents > Adobe > Adobe Media Encoder > 12.0 > Presets folder. Launch Premiere and now the presets should be in 12.0. In the Export Settings dialog, you also have the option to add the presets (but, one at a time).

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 20, 2017 Oct 20, 2017

Copy link to clipboard

Copied

Hi Trent

Thanks for your suggestion. I tried it and it seemed fine at first.

But then every time I tried File - Export - Media, I immediately got the message: ‘Sorry a serious error has occured that requires Adobe Premiere Pro CC to shut down’.

I even tried creating a completely new file containing just one movie - but still got the same problem. So then I tried removing my custom presets from folder 12.0 and succeeded in getting to the export panel. Then I used the Install Preset button, installed the preset I needed from folder 11.0 and was able to successfully export.

So, thank you all the same because I would never have know where to look to find the old preset. But please be aware that copying multiple presets in the way you describe can have disastrous results.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Oct 20, 2017 Oct 20, 2017

Copy link to clipboard

Copied

Well, that is not good. I tried copy/paste of a few MXF and MPEG presets and so far I have not run into this serious error crash. Maybe there is something specific about your presets or I'm missing something.

Would it be possible for you to supply all of the presets that you copy/pasted along with the crash log? Or, if you prefer, you can submit a bug report at Wishform - Adobe Premiere Pro

Thank you.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 22, 2017 Oct 22, 2017

Copy link to clipboard

Copied

Hi Trent

I have more info for you as requested. Not sure if it will help.

First of all, I’ve tried replicating the problem several times but have got inconsistent results.

Test 1. I deleted all presets in folder 12 and copied the presets from folder 11. As expected PP crashed when I clicked Export.

Test 2. I deleted just one of the presets that I suspected was a New Sequence presets rather than an export preset. This time export worked.

Test 3. I deleted all presets in folder 12 leaving it blank. Surprisingly PP crashed when I clicked Export.

Test 4. Re-opened PP (nothing changed from Test 3) . This time export worked

Tests 5, 6 & 7. Re-opened PP (nothing changed from Test 3) . Each time PP crashed when I clicked Export

Test 8. Re-opened PP (nothing changed from Test 3) . This time export worked

So the only conclusion I can draw is that (for me at least) Premiere Pro CC 2018 is buggy and unreliable and liable to crash at export 2/3rds of the time. And I haven’t even mentioned that in the short time that I’ve been using Premiere Pro CC 2018 I’ve had at least 6 other random crashes which I can’t relate to any particular action.

Not sure how to supply you info about the presets I used. The one I deleted in Test 2 was called ‘2361x1728.epr’. Does .epr mean it’s an export setting? I noticed that it had the same name (without the .epr) as one of my custom New Sequence presets. Here are the details of that setting:

General

Editing mode: Custom

Timebase: 25.00 fps

Video Settings

Frame size: 2361h 1728v (1.0000)

Frame rate: 25.00  frames/second

Pixel Aspect Ratio: Square Pixels (1.0)

Fields: Lower Field First

Audio Settings

Sample rate: 32000 samples/second

Default Sequence

Total video tracks: 3

Master track type: Stereo

Audio Tracks:

Audio 1: Standard

Audio 2: Standard

Audio 3: Standard

Finally, here is the log for the Test 1 crash:

Process:               Adobe Premiere Pro CC 2018 [55269]

Path:                  /Applications/Adobe Premiere Pro CC 2018/Adobe Premiere Pro CC 2018.app/Contents/MacOS/Adobe Premiere Pro CC 2018

Identifier:            com.adobe.PremierePro.CC12

Version:               12.0.0 (12.0.0)

Code Type:             X86-64 (Native)

Parent Process:        ??? [1]

Responsible:           Adobe Premiere Pro CC 2018 [55269]

User ID:               501

Date/Time:             2017-10-22 16:07:48.931 +0100

OS Version:            Mac OS X 10.13 (17A405)

Report Version:        12

Anonymous UUID:        F99A8517-F98C-5EC8-9D88-0449635790E2

Time Awake Since Boot: 270000 seconds

System Integrity Protection: enabled

Crashed Thread:        53  Dispatch queue: opencl_runtime

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)

Exception Codes:       0x0000000000000001, 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Illegal instruction: 4

Termination Reason:    Namespace SIGNAL, Code 0x4

Terminating Process:   exc handler [0]

Application Specific Information:

*** CFRetain() called with NULL ***

Thread 53 Crashed:: Dispatch queue: opencl_runtime

0   com.apple.CoreFoundation       0x00007fff2adcd072 CFRetain + 114

1   com.apple.GeForceGLDriver     0x00007fff2579046d 0x7fff25493000 + 3134573

2   com.apple.GeForceGLDriver     0x00007fff2578f5b0 0x7fff25493000 + 3130800

3   libGPUSupportMercury.dylib     0x00007fff4354bf11 gldLoadTexture + 194

4   com.apple.GeForceGLDriver     0x00007fff257aad02 gldLoadTexture + 223

5   com.apple.opencl               0x00007fff33387783 0x7fff33352000 + 219011

6   com.apple.opencl               0x00007fff3338e449 0x7fff33352000 + 246857

7   com.apple.opencl               0x00007fff3337136d 0x7fff33352000 + 127853

8   com.apple.opencl               0x00007fff333749fc 0x7fff33352000 + 141820

9   libdispatch.dylib             0x00007fff5240ff64 _dispatch_client_callout + 8

10  libdispatch.dylib             0x00007fff5242442b _dispatch_queue_serial_drain + 635

11  libdispatch.dylib             0x00007fff5241730e _dispatch_queue_invoke + 373

12  libdispatch.dylib             0x00007fff52425117 _dispatch_root_queue_drain_deferred_wlh + 332

13  libdispatch.dylib             0x00007fff52428ef0 _dispatch_workloop_worker_thread + 880

14  libsystem_pthread.dylib       0x00007fff526d3033 _pthread_wqthread + 980

15  libsystem_pthread.dylib       0x00007fff526d2c4d start_wqthread + 13

Model: iMac13,2, BootROM IM131.010F.B00, 4 processors, Intel Core i7, 3.4 GHz, 16 GB, SMC 2.11f16

Graphics: NVIDIA GeForce GTX 680MX, NVIDIA GeForce GTX 680MX, PCIe, 2 GB

Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020

Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Oct 23, 2017 Oct 23, 2017

Copy link to clipboard

Copied

Thank you for the additional info. .epr is the extension used for export presets. Sequence presets have the extension .sqpreset and are located in the Documents > Adobe > Premiere Pro > (version) > Profile > Settings > Custom folder, so they should not be in the Adobe Media Encoder folder that contains your export presets.

As you are seeing other random crashes, possibly try deleting your Preferences and see if that helps. Quit Premiere, hold down Opt + Shift while launching Premiere. The other possibility is an issue with OpenCL on your system. Make sure your drivers are up-to-date and if so, try to switch your Renderer to Software Only. File menu > Project Settings > General > Video Rendering and Playback, switch Renderer to Mercury Playback Engine Software Only.

If neither of those help, then I would suggest contacting Customer Care to help troubleshoot. Contact Customer Care

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 24, 2017 Oct 24, 2017

Copy link to clipboard

Copied

Hi Trent

Thanks for your advice.

Not sure what you mean by 'drivers'. I only know about printer drivers. I'll check them. Are there other sorts of drivers?

Apart from that I have latest OSx - all updates installed.

I'll try out your other suggestions.

Anyway thank you for taking time to look into my case - much appreciated.

Cheers

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 04, 2017 Nov 04, 2017

Copy link to clipboard

Copied

I appreciate your help, but honestly I think that problems like this should never arise.  People work with Adobe Premiere instead of FCPX because we prefer a solid company and a solid product.  How did the programmers and testers miss this problem when offering an update?  I'm literally speechless.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 29, 2018 Jan 29, 2018

Copy link to clipboard

Copied

Thank you Trent for this info.  Much appreciated.

B

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Oct 24, 2017 Oct 24, 2017

Copy link to clipboard

Copied

Your video settings are strange.

Odd numbers, lower field with 1.0 PAR and 32000 audio.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 24, 2017 Oct 24, 2017

Copy link to clipboard

Copied

Thanks Ann

My odd video setting (2361x1728) has turned out to be a red herring. I mentioned it just in case it was the cause of the problem - but I was wrong.

As Trent has pointed out, the settings I copied from the presets 11 folder were .epr - ie. Export Settings. Whereas the setting I gave details for (2361x1728) was a Sequence preset. I couldn’t tell because I’d given both settings the same name so I wondered if the presets 11 folder contained a mixture of Export and Sequence settings. Trent has explained that that folder only contains Export settings.

Also, I wasn’t using the 2361x1728 sequence preset for this job. The preset was a one off for a random job I had to do with those odd dimensions. It didn’t require sound so the audio setting is irrelevant. I didn’t know ‘lower field’ was considered odd though? I suppose I’ve been used to choosing ‘lower field’ as a default because that was always the specified setting when I used to import from a camcorder running DV tapes in the past. I’d be interested to know what you’d recommend?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 08, 2018 Jan 08, 2018

Copy link to clipboard

Copied

RalphDCW,

Are you clear of this issue yet? Let us know.

Thanks,

Kevin

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 28, 2018 Sep 28, 2018

Copy link to clipboard

Copied

Has Adobe put out a fix for this issue yet?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 01, 2018 Jan 01, 2018

Copy link to clipboard

Copied

You must access your old Premiere 2017 Folder named "4E49...3634" and copy the presets.
Then you copy it again in the same folder in the 2018 version.

Here's a video (it's in portuguese but it's easily understandable):
Missing Presets in Adobe Premiere CC 2018 - - YouTube goo.gl/x6S71w

Here's a link to download the 2017 presets:

goo.gl/x6S71w

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 21, 2018 Jun 21, 2018

Copy link to clipboard

Copied

There is definitely something wrong with the update process in Premiere as I lost my export presets as well with the most recent update. I searched my entire Mac for the old preset and it was gone. Fortunately I have autobackup on my mac into TimeMachine so I retrieved the export presets that had been backed up before the last update. Now with Timemachine, when you recover old data it automatically offers to put it back into the same subfolder it originated from,  and in reviewing the contents of that subfolder there is no doubt it had been deleted.

I haven't used Premiere or even accessed that hard drive since just before the last software update, so there is nothing other than the update that could have deleted these files.

So... Adobe...this is definitely your issue.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 09, 2020 Jan 09, 2020

Copy link to clipboard

Copied

LATEST

yeah,Screen Shot 2020-01-09 at 2.34.04 AM.pngScreen Shot 2020-01-09 at 2.34.14 AM.png my presets won't even work or show up. not even the default ones

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines