[Brent Marginet]

You would think other software would crash but this is a computer and not all software allocates RAM or RAM Cache the same way so who knows.

Can’t hurt to try, especially reseating it or putting the old RAM back into the system.

[Brent Marginet]

One last thing that really drove me crazy was that when exporting merged clips through Media Encoder for the Daily viewers was the lack of audio control. The Daily Viewers need to have a Mono Mix Down of all the Audio but when I used the Merged Clips only Audio Track One would show up in these exports.

I posted this both on the Adobe Forum and here and no one had any answers so I found a work around.
I find the way Premiere handles Audio rather cumbersome.
You should not be stuck to one particular audio setup and you should be able to change it on the fly any time you want to.
Loading in a new Sequence Preset then Copying and Pasting from one Timeline to another is ridiculous.

I made a Sync Sequence that I would duplicate for each new Audio and Video Clip I was going to sync.
It’s Audio output was set to a mono mix down.
I would then drop the Audio and Video for each clip into this sequence, sync it, trim the excess Audio or Video off, remove the empty timeline in front of the synced media and finally Merge it. Now the plus is that I was able to export the 1280×720 H.264’s with a mono mix down of the Audio by exporting these Sequences but the minus is that I had to keep both the Merged Clips and there associated Timelines. This also meant extra time naming both of them even if I did copy and paste the names and keeping them in separate Bins.

Yeah I know I’m being a big baby.
I do however want to point many of these things out because in many ways I really like Premiere and I want to see it improve.
I’m also hoping to make more use of it because some of the latest Avid issues really make me want to find an alternative.

[Brent Marginet]

[greg janza] “So you decided to learn “trial by fire” style and therefore a mountain of frustrations come with the territory.”
We didn’t decide to learn Premiere “trial by fire” the production found an editor 6 days before the start of production who would only use Premiere. They also had to fly in an assistant editor in from another Province and he arrived 3 days before the start of Production so what choice did we have.

I’m only making comparisons because Premiere has been around since 1991 and Pro since 2003 and if they still haven’t fixed the link problems then theres something seriously wrong here. Like what 10,000 years ago when FCP 7 came out it’s links to media were far more stable than the current version of Premiere is.

Now putting that aside lets go on to syncing. Very easy and nice to do in Premiere except for the fact that they still haven’t allowed for subframe alignment that sticks when clips are merged. Hell even DaVinci Resolve doesn’t seem to do this and as far as I and the Audio Engineers are concerned this is a must in todays world of editing.

[greg janza] “Avid has such a richly developed media management engine and the software itself is finely tuned to film and television production.”

And so what then Premiere is only aimed at making home videos for your family. I think Pro says it all and that means fix or add these long overdue features.

[Brent Marginet]

Ok so calling it a TOY is rather cruel which I shouldn’t have done.
It is however not going to be fully movie ready until at least Sub Frame Audio Slipping stays with the Merged and MultiCam Clips like Perf Slipping does in Avid.

I handled all the transcoding, syncing, H.264 Viewers (dailies), archiving and I’m also technical support for our small facility. It’s a bit of a drag at times trying to resolve these ridiculous issues and keep on top of the dailies. Luckily the assistant editor is extremely thorough, organized and experienced even if he was also new to Premiere. The editor unfortunately moved from FCP-7 to Premiere but is also an extremely good editor so that helped a lot.

Having said that, my next goal is to make a list of all the things that I can post on Avids Forum. Premiere has many really nice features that Avid really needs to implement. It’s time for them to turn there noses down and look at what everyone else is doing. As much as I despise FCP X there’s features in it that Avid could really take a look at as well.

[Brent Marginet]

First thing to try is to re-seat this RAM or put back the old Sticks.
If doesn’t fix the problem it’s probably not RAM related.
You could also try building the bootable MEM Test Disk or USB boot from here
https://www.memtest.org to see if you have any bad RAM.

Last but not least, we pay a stupid amount of cash each month for our subscriptions so call Adobe like I do when I’m really stuck.

[Brent Marginet]

The problem I do believe is the AAF’s that Premiere imports or exports.
I have never had Premiere ever import or export a proper AAF.
I’m not even sure why Adobe includes the feature when it never works.

As an example if I export an AAF from Premiere and bring it into Resolve every video clip is off.
One will be 11 frames another 13 frames and so on, almost every clip is off by a different amount of frames. Exporting a FCP XML works but not AAF’s.

I know your going from Avid to Premiere but I don’t think it’s ever been fixed and is therefore useless. Maybe try to flatten the timeline in Avid as much as possible and export an EDL for each individual Video track. Import the EDL’s into Premiere one at a time an then combine each into one timeline.

[Brent Marginet]

Heres a link to a Video that explains what’t happening with the markers.
Now I assumed that since your exchanging the Projects via Dropbox that you may be working with pretty much the same media but copying it to each system before it’s been XMP Tagged by one or the other projects. This check box essentially attaches the Markers to the Media when checked and Embeds them into the Project if unchecked.

https://www.creativeimpatience.com/premiere-pro-clip-markers-solved/

Hope that this helps.
It’s working perfectly for us on our project.
Mine is checked and they do not get passed on to the Assistant Editor at another location as we want.
His is unchecked and they do get passed to the Editor from the Assistant Editor as we need at yet another location.

I’m rendering the Red Media to DNxHD 36 QT Movies and and then syncing the Audio to the Video. The media is then sent off to the two editors and copied to they’re respective drives before any tagging of the media can be done. When the Assistant editor exports his daily project the Editor is seeing all of his markers.

[Brent Marginet]

Lets try that again.

[Brent Marginet]

I just read something about this and the latest version of Premiere.

Uncheck the box under Preferences/Media/Write clip markers to XMP and then they should show up on both systems when passing the project back and forth. I leave mine checked because the markers I create are irrelevant and are not needed by the assistant editor.

I’ve attached a screen grab, hope it shows up for you.

[Brent Marginet]

I have been using a PC version of the GTX-980 and then upgraded to the GTX-980Ti for awhile in my two 5,1’s and do have some info and advice to share. First there’s no increase in performance from the 980 to the 980Ti and so I doubt that the 1080 will do any better. I speculate that the bottleneck is the Gen 2.0 PCIe slots, bus architecture and bus speed of these older machines. I’ve also tested both EVGA and ASUS Cards with the same results. Probably cheaper to buy a used 980Ti from eBay than a new 1080.

Next, things get a bit tricky getting the OS to recognize the PC Versions of these cards. When installing a new OS. You must have a card with MAC Firmware on hand. In my case I must pull the 10gb CX-4 Card in Slot 2 and install a Mac Card like a GT-120 there which does and must not require external power. Next install the NVidia Web Drivers found at MacVidCards.com, to get the correct Drivers open “About this Mac” and click where it states your OS X version and the Build number should show up, then grab the proper version from there site. At least they won’t install if you download the wrong ones. Now install the CUDA Drivers from the NVidia Site. In my case I return the CX-4 card in slot two since all my slots are populated and connect my monitors to the 980Ti.

Now here’s the tricky part, for some reason Apple requires an update of the Nvidia Drivers after every Seurity Update is done and after installed and the system reboots my monitors do not come up. The NVidia Control Panel resets to the built in OS X Drivers and they don’t recognize the 980Ti. Instead of reinstalling the MAC Card every time I always leave remote login and management turned on under Sharing in System Preferences. I remote in from another machine, log in and go to System Prefernces. Then in the NVidia Control Panel click on the Check for Updates if it doesn’t automatically pop up and after installed a reboot is required. Your monitors will now come up but you will not see the typical MAC Grey boot screen, you will go directly to the desktop or login window depending how you have set up you system. Be patient it can take a minute or two for your monitors to come back to life.

Last bit of advice, turn off automatic updates and before you do any security update note the version of Drivers currently installed. Now go to MacVidaCards and make sure there has been a newer release of the NVidia Drivers otherwise you will be doing a complete OS Reinstall like I had to do once, learnt my lesson from that one. The update took a month to show up.

Last bit of info in this long winded reply. There has been a bug with either the NVidia or CUDA Drivers since Yosemite that is a PITA. It hasn’t occurred in every version but it’s a real pain if your using a single card like me. This bug effects both Media Encoder and DaVinci Resolve. If you setup a large batch of encodes in either the system will crash hard randomly and sometimes fairly often so here’s the workaround. I’ve even had cases where Safari causes the crash while the encodes are happening. Don’t reboot but shut down your machine and after restart setup your encode(s) and go to town. Try to minimize useage of GPU intensive software during your encodes and if you start another one after a period of doing whatever else do the Shut Down again.

I think that’s it, hope this helps and please as questions if I’ve confused you in any way.

Thanks