[Robert Wentz]

I would suggest taking a look at Archiware P5 Archive They have techs who respond within 24 hours if you are having any sort of difficulty or issues with archives, backups or restores. Their support is ALMOST as good as Atempo’s when they had Barbara Pierscieniak on staff ☺

There’s a free trial you can give it a shot, and one of Archiware’s partners put together an excellent masterclass video series on youtube:
https://www.youtube.com/playlist?list=PLLRoWZsYKz0gztFsr77s-Zem6kbPKXkh0

Rob

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Robert Wentz]

Sure, just as I said – in our situation based on my experience working with the listed footage types – on a MAC proRes 422(HQ) was the better option between the two. I would never suggest following the logic that because something is a default (all things for all people) it is a better option.

I would venture to guess that part of the reason proRes is not the default option is that proRes is not also available on windows (neither easily or by default).

Based on my experience – if you’re on a mac have the disk space and throughput set your preview preset to proRes 422(HQ) .. not LT, not 422 – set it to 422(HQ).

[Robert Wentz]

Among quite a number of obstacles – Unless Blackmagic decides to allow third party Video I/O devices (ie AJA KONA) with Resolve they don’t have a chance of causing the revolution that is being hinted at here.

They also should probably get up on finally qualifying (or not) AMD GPUs . . . As of January 2015, this is what Blackmagic support had to say about qualifying AMD GPUs in resolve:
“That’s not to say they don’t work, just that we haven’t tested and verified any at this point”

[Robert Wentz]

@Joseph Owens “at least it doesn’t keep disappearing like the AJA does if the Mac ‘sleeps’. Then its a system cold boot or forget it.”

One of the many reasons why most people disable sleep mode on any machine dedicated to production or post.

[Robert Wentz]

No, I see the alpha just fine in premier.. your image is 1609×905 which is an odd format… are you certain the png is not scaled outside of the viewing region of your sequence?

What is the format of the sequence you’re attempting to bring this png into?

[Robert Wentz]

Hi again,

First – render work area only appears if you have the work area bar enabled, it sounds like you (smartly) have it disabled. Render in to out would suffice for what I was suggesting but like you mentioned it sounds moot as the jump is in your renders and exports as well.

I would certainly give it a shot – conform the 30.4 FPS footage to 30 FPS exactly. 30.4 is … well.. suspect to say the least in the first place so it would be a good idea to just conform that OR re-shoot it at exactly 30 FPS.

Id be curious – what would happen if you replace your 30.4 FPS footage with some other footage that IS conformed to 30FPS? If you just option+drag a clip already imported into your project window onto the 30.4 media in the sequence it will replace the clip with what you are dragging. .

[Robert Wentz]

Also note you wont be able to set the Preview file format to Quicktime in many cases unless you first change the “Editing Mode” to “Custom”.

I have found that in 99% of my situations (we mostly edit 5D and Red Dragon) setting the editing mode to custom, preview format to Quicktime, codec to ProRes422(HQ) is the way to go. I-FRAME ONLY MPEG on a mac is for the birds in my experience.

[Robert Wentz]

Thanks for the prompt suggestion, Trent.

I went about it slightly differently so I didn’t have to do any additional transcoding.
I simply ran the consolidate/transcode/Project Manage within premier to trim off the many GBs of unused footage, then dropped the resulting QT movies onto a simple applescript I wrote that rotates right then saves QT movies in QT 7. The save operation in QT 7 on proRes 422HQ is ridiculously fast so the appleScript ripped through the batch rather quickly.

[Robert Wentz]

First, a couple of things.. just out of curiosity…

Are you just seeing this in realtime playback of your sequence or is this also occurring in exports of this sequence? Does the issue seem to persist after Sequence>Render Entire Work Area

What is the framerate of your sequence? What is the framerate of your source footage?

I’d suggest just hitting the stopwatch to delete ALL keyframes on the position (and any other attribute that seems to be jumping) of the problematic clip, then re-doing your three keyframes.

Also – would be easier to identify and troubleshoot the issue if you would step through the frames where the problem occurs with the right arrow key as opposed to “3… 2… 1… spacebar”

[Robert Wentz]

Hi Carlos/David:

First off you say “no matter what kind of project I’m on, using whatever kind of footage. ”
It would actually be helpful to troubleshoot the cause of this issue if you can give examples of the type of footage you’re editing — what camera was the footage shot from? Is it raw footage? What codec is the footage you’re editing? Are these mixed codec sequences? What is your GPU(s)? Do you have any AV I/O card installed in your system (AJA/BlackMagic) and is Mercury Transmit enabled, outputting the video to a reference monitor/plasma/second monitor/etc?

Premier is a pro editing solution that does all things for all people so it helps to keep that in mind when asking for help.

You didn’t mention anything about your sequence settings – here’s what I’d recommend here, based on my experience, and by all means this is open to debate:
Select your sequence’s timeline. Go to Sequence>Sequence Settings Override the “Editing Mode” by selecting “Custom”. Under “Video Previews” Set the “preview file format” to “QuickTime”. For most purposes then set your Codec to ProRes 422(HQ). Hit OK, then hit OK again…

After that, I’d move on to give the system some apparently much needed TLC.
typical TLC steps which normally tend to resolve the types of issues you describe:

Trash premier preferences. The need to do this is not an “Adobe Issue” it is a maintenance step, not unlike changing oil in your car. you can do this manually, or download digital rebellion’s preference manager: https://www.digitalrebellion.com/prefman/

(NOTE: Any preference setting you’ve made or kb shortcut that has NOT been sync’d to your cloud acct will be gone. As of 2014 you must sync to the cloud in order to keep your shortcuts, etc)

Trash your media cache. Same explanation as above. Go to Preferences>Media to find where the location of the media cache, and instead of “cleaning” the database through the preference pane in premier, just manually trash the contents of the folder.

Take out the trash.

(NOTE: After tossing media cache you’ll simply need to wait for premier to rebuild the cache for that project next time you open it)

After doing the steps above, reboot the computer, gracefully. If you’re the type who tends to press and hold the power button of your computer to force shut it down I’d recommend shutting it down then restarting while pressing cmd+alt+P+R to clear the NV/PRAM.

If the problem persists go to Disk utility and repair disk permissions on your system drive, then reboot gracefully (as in don’t press/hold the power button)

Should problems STILL persist you may have a permissions issue with your media/project folder – open perms by going to terminal and sudo chmod -R 777 the folder containing your project/media.