[Joseph Freeman iii]

[Joseph Freeman iii]

Looks like posting XML code is not permitted….the example was removed…

[Joseph Freeman iii]

Hi Mike,

Premiere Pro cc2018 ver.12.1.1 was program version “35”. I change it to “1” and when opened by cc2017, the standard conversion dialogue box appeared. By changing the version number to “1”, I presume one could possibly use much earlier versions of Premiere Pro.

Here is the XML line to change:
FROM:
TO:

Maybe starting with creative cloud, Adobe gzipped and renamed the project files to hide the XML code from prying eyes.

I agree with Rene that a “Save As” function would be desirable. It would alleviate much anxiety and misery with the user base.

In looking at the XML, I was surprised to see so many Lumetri references, especially since I had used “Remove Attributes” to delete all Lumteri references because of persistent “Low Level Exception” errors with Lumetri.

[Joseph Freeman iii]

Hi Jacob,

In my experience with dynamic linked AE material, I do no color correction in AE, except when compositing to match elements. I leave all color correction/balancing to the Premiere Pro side of the link. Typically, this minimizes or eliminates any color tweaking with the previous clip and following clip and the AE linked clip.

Often, I copy the AE linked clip to a disabled track, for backup, and just render and replace the AE linked clip with a high quality MNX file and color correct that file. This eliminates playback & render slow downs for AE linked clips.

Maybe this approach may offer similar results for your project.

Joseph

[Joseph Freeman iii]

Hi Dave and thanks for your on going responses.

I seem to have resolved most of my Premiere Pro cc2018 issues.

This current “Crash Prone” cc2018 project was exported via Project Manager from another computer, which required me to upgrade from cc2017. From the beginning of my involvement, this project had issues, which I attributed to cc2018 and inherent new rollout bugs. Yesterday, I scrubbed my system, reinstalled Windows 10 Pro, and reinstalled only the minimal necessary cc2018 programs, as well as needed third party plugins. This did not solve the issue. In my panic, I exported a XML copy of the project, then downloaded Vegas Pro15 and imported the cc2018 project, which didn’t work, then the XML project which did not work. I then co-installed cc2017 and imported the XML which only made the issues worst.

In a brief moment of inspiration (even a broken clock is right twice a day), I opened the cc2018 project and also created a new project and copy/pasted objects from one timeline to another. In the new project I had no issues at all.

Bottom line, when receiving a project first thing is to create a new project and copy-paste one timeline to another…

Your suggestion on Resolve was considered, but I always have too much work to take time to learn a new NLE. Additionally, the “Node Based” learning curve would be very steep.

Have a great day and I’m sure I’ll continue to see your “If it ain’t broke don’t fix it” sage advice in the Creative Cow forums.

Joseph

[Joseph Freeman iii]

If you find an alternative to Premiere Pro, that is STABLE, reasonably priced, and has 50% of Premiere Pro’s functionality, PLEASE put me on your alert list.

I have spent the day (9:30 am-7:00pm minus lunch and restroom breaks) reformatting, reinstalling Windows 10 Pro, Premiere Pro, After Effects and Media Encoder, Red Giant’s Magic Bullet 13.1 and Sound Toys 5.2 and that is it and Still I got a crash after a Lumetri low level exception…

As a last resort, I am installing cc2017 and will do a XML import to see if there is any improvement…

That doesn’t work, I’ll dump all lumteri effects and apply colorista…

Burn a candle for me…

[Joseph Freeman iii]

Greg,

Thank you for your reply. I agree ” The level of crashes you’re experiencing is definitely not normal.”

Short of a complete re-installation of Windows Pro, I had uninstalled CC2018 and all third party software, ran the Adobe software scrubber, cleaned my registry, ran windows SFC, ran SiSoftware’s Sandra system checker, a complete Virus scan, and re-installed only Premiere Pro, Media Encoder, and After Effects.

After disabling the allow index for each drive (13 in total) did I experience “Minimal” crashes, only three in a four-five hour period. Most Adobe errors, after the described re-installation process, were Low Level exception: Lumetri or MXF related issues. (I use DNx as my preferred Preview format and as the Render and Replace format for AE Linked files)

My post was meant to share my observation in good faith for those experiencing issues in a Windows work environment.

Joseph

Windows 10 Pro
i7-5820k CPU
32 GB DDR4 RAM
ASUS X99-A MoBo
13x internal fans
1000 WPS
Nvidia GeForce GTX 1080 Ti
ASUS PB287Q Monitor (4k 10bit)
Adobe CC 2018
OS/Program: Samsung SSD 950 Pro x2 in Raid 0
Project: Samsung 500 SSD
Media: Seagate 2 TB Sata III
Cache: Samsung SSD 960 PRO PCIe NVMe M.2 2280
Renders: Samsung 500 SSD
Misc: Western Digital Black 300 GB Sata III
Backups: 6x USB drives (30 TB in total)

[Joseph Freeman iii]

Dave,

In your experience, does Adobe FIX the problems of the current version (update) before releasing an upgrade to the next version?

Thanks?

[Joseph Freeman iii]

“there is a (cheap or free) solution to get ProRes out of your PC PP, based on a trick that it hooks into the frameserver PP seems to have.”

Please share.

[Joseph Freeman iii]

I had to compromise (an extra generation) and replace the clip (ProRes) with an after effects composition, apply denoiser, and in Premiere Pro do a render and replace (DNxHD)…This process was repeated for every cut needing denoiser.

In After Effects, I created an Animation Pre-set to minimize key strokes and reduce possibility of user error.