UI is very sluggish with MXF clips and dropped frames

December 8, 2014, 10:08 am

≫ Next: I'm a novice on Premier so forgive me. Choppy Video..unable to edit

≪ Previous: PPro 8.1 Update causes EXTREME UI sluggishness. Don't do it.

$

0

0

The PR UI will intermittently get very sluggish on a documentary we've been working on for about 5 months and we've been plagued by the MXF dropped frames issue. The slow UI started back in the middle of October and we upgraded from 8.0.1 to 8.1, that converted the project, to try and resolve the issue, but only made it worse.

The CTI will paint very slowly, playback start is delayed by 3-8 seconds and the windows header will display "not responding".

 

The sequence contains a mix of old DV, XF305 and 5d Mark III footage. The DV footage and sequence are 720 x 480 (0.9091) and 29.97. The MXF and 5d footage is 23.976.

I've worked a couple of support calls for these issues and ended up removing all Adobe products and reinstalling. I've been following similar posts for C300 dropped frame issues and may have found a possible work around and information that might be relevant.

 

I was trying to get some work done on the project this weekend and it became unusable again because of the sluggish UI. I decided to copy the sequence onto a USB disk, using File -> Project Manager, so I could try it on our Macbook Pro to see if it behaved any differently. I opened the project on the Mac and link media -> locate showed that some of the MXF footage, that was all originally imported as MXF through the Media Browser, couldn't be located. I went back to my Windows 7 system and had the same issue. It was asking for specific clips, as if the media had been imported as individual clips, so I couldn't relink the media pointing to the CONTENTS folder. I remembered a suggestion from one of Kevin's posts saying that you could use the Canon XF Utility and export Virtual Media to one clip. I abandoned trying to get it to run on the Mac and created one file for each MXF container on the PC, renamed the original media folders and was then able to relink all the MXF media.

 

I was able to work about 8 hours yesterday without any problems and haven't seen the UI slow down or any dropped frames. I'm going to edit all day today, try an export and will update this post with my findings tonight.

 

Adobe Premiere CC 2014 8.1.0 (81) Build

Windows 7 Pro SP1, latest updates

Intel Core i7-920 CPU

48GB RAM

Nvidia GeForce GTX 480 - 9.18.13.4052 Driver

LSI 9286CV-8e with a RAID 6 and RAID 0 for media and cache

---

I'm a novice on Premier so forgive me. Choppy Video..unable to edit

December 8, 2014, 9:57 am

≫ Next: Red Frames and Freezed Frames with XDCam and C300 Files on export an edit

≪ Previous: UI is very sluggish with MXF clips and dropped frames

$

0

0

I'm very experienced in Photoshop but am trying my hand at doing some videos.  I'm struggling with editing.  When I import my files into a project. (I'm using a MAC) When I try to edit in the source window the video is choppy and I can't seem to edit.  I'm not sure what I'm doing wrong.  Any help is so appreciated.

Red Frames and Freezed Frames with XDCam and C300 Files on export an edit

January 21, 2014, 4:07 pm

≫ Next: Premiere Pro CS6 Crashes When Dragging

≪ Previous: I'm a novice on Premier so forgive me. Choppy Video..unable to edit

$

0

0

Hi there

 

im getting random red frames on export and editing with adobe premiere pro cc the current version (7.2.1). my actual timeline is about 50 min. documantary most c300 .mxf some xdcam .mxf files an gopro stuff.

im on a windows 7 machine with enough power to handle that long timelines. seems fom me that premiere has some problem en/decoding xdcam op1a. Getting a lot of errors like this : MXF read error "\\?\V:\xxxxx-1080p-XDCAMHD50PAL.mxf" frame 383.

sometimes i have to export more than 5 times to get a file without red frames thats annoying. my current workaround is exporting dnxhd and reencode to xdcam op1a but its quite time consuming.

 

i have to export xdcam 50i for delivery to tv stations some of them dont acept other formats.

tryed some of the other hints on other threads like this (clear database, create new project, clear media cache) any other suggestions

 

please its quite urgent

i have to deliver a new episode in 2 days..

Kevin

Premiere Pro CS6 Crashes When Dragging

November 25, 2014, 7:25 am

≫ Next: Debug event f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe

≪ Previous: Red Frames and Freezed Frames with XDCam and C300 Files on export an edit

$

0

0

Trying to edit in PP CS6 and keep getting this error every time I drag files.

"Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project."

This happens every time I try to drag any footage. Regardless of files or locations.

 

I'm working (at least trying to) on a Mac Pro (Mid 2012) running OS X Yosemite 10.10.1.

 

Processor- 3.2GHz Quad-Core Intel Xeon

Memory- 16GB 1066 MHz DDR3 ECC

Graphics- ATI Radeon HD 5770 1024MB

 

 

The Adobe applications manager says everything is up-to-date and I've tried everything I can think of.

 

Restarting computer.

Testing different video files in the project (happens with all)

Moving files to a different drive

Creating a new project on a different drive

Opening old project with footage that worked before.

 

No luck with anything.  Any help is greatly appreciated! I've got deadlines to meet and no backup computer!

Debug event f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe

September 28, 2014, 12:23 pm

≫ Next: Just did an PP update and Warp Stabilizer does not work.

≪ Previous: Premiere Pro CS6 Crashes When Dragging

$

0

0

Hello everybody,

 

I just ran into this extremely annoying problem:

 

Premiere Pro CS6 cannot load my project anymore. It gives the following error message:

Premiere  Pro has encountered an error.

f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe

 

 

My autosave files all refuse to open giving another error
..\..\src\TickTime.cpp-364

 

When i press continue it says the project might be damaged or contain outdated elements.
I do not know what that means...

 

I do not know what i did last before the problem started, except for adding some layers (lightstreaks) rendering the file and then stopping that thinking "I'll do it later"

What a mistake. The projectfile didn't open anymore when i got home. All my autosaves now give similar errors.

 

I got warpstabilizer on some clips but would gladly give that up if there was a way to open these files. I cannot import them to a new project. Essentially the files refuse to open in any possible way.

 

You can find my latest projectfile here: jajageweetmaarnooit.prproj - Google Drive

 

I am desperate, this movie needs to be delivered tomorrow and i have to start all over.

Just did an PP update and Warp Stabilizer does not work.

October 6, 2014, 4:54 pm

≫ Next: Premiere Pro CS6 Playback window zoomed in or something..?

≪ Previous: Debug event f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe

$

0

0

Just updated PP and Warp Stabilizer doesn't not work. It processes, stabilizes but the finished product shows almost like a black matte over the video with only a small corner showing. Tried several times even in new projects and sequences. This literally happened right after the update. Any ideas or how to correct?

Premiere Pro CS6 Playback window zoomed in or something..?

December 8, 2014, 10:22 am

≫ Next: inactive Mercury Engine Playback GPU Acceleration

≪ Previous: Just did an PP update and Warp Stabilizer does not work.

$

0

0

The playback window for my project seems to be permanently zoomed in or locked or something.

I put playback view settings on Full and set it to Fit but it didn't change and its grainy and blurry.

Anyone have an idea as to what could be causing this or how to remedy it?

 

I've already restarted my computer, the program and whatnot so theres that.

 

Thanks in advanced!

 

-Gavin

inactive Mercury Engine Playback GPU Acceleration

December 8, 2014, 4:51 am

≫ Next: Problem rendering closed caption video with PremierePro CC 2014

≪ Previous: Premiere Pro CS6 Playback window zoomed in or something..?

$

0

0

Hello. I have problems with activating Mercury Engine Playback GPU Support in Premier Pro, Media Encoder, Prelude. It is dimmed and a can't choose it. Only Mercury Engine Playback Software Only.

Workstation configuration: iMac 21'5 (mid 2013), Windows 8.1, Adobe Creative Cloud 2014 with last updates, Nvidia drivers 344.75 for Geforce GT650M

I tried method with cuda_supported_cards.txt but it does not help.

How I can enable CUDA Support?

---

Problem rendering closed caption video with PremierePro CC 2014

December 5, 2014, 10:54 am

≫ Next: need help badly. project file wont open. saying damaged file or may contain outdated elements. please help

≪ Previous: inactive Mercury Engine Playback GPU Acceleration

$

0

0

I am on a Mac running Yosemite and using Premiere Pro CC 2014.  No matter how I try to render video with closed captioning (embedded or with a side car file in various formats) I cannot render a file that contains the closed captioning.  I have followed the tutorials, but cannot produce a file that has readable closed captioning either in the Quicktime player nor when I import the generated file back into Premiere Pro.

 

Any hidden tricks? Tips?  Help!

need help badly. project file wont open. saying damaged file or may contain outdated elements. please help

December 8, 2014, 10:52 am

≫ Next: I don’t know what I changed on the program…

≪ Previous: Problem rendering closed caption video with PremierePro CC 2014

$

0

0

project file wont open. damaged file or contains outdated elements message. i believe its an XML error but i dont know how to fix it. please help

I don’t know what I changed on the program…

December 8, 2014, 12:07 am

≫ Next: Premier estimates 331 hours to make my movie???

≪ Previous: need help badly. project file wont open. saying damaged file or may contain outdated elements. please help

$

0

0

Last time I used CS6 I was able to do the following:

In the timeline I would have a 5 minutes long video in Video 1, and in Video 2 a 30 seconds title, normally I would stretch the title's time on the timeline to the point where a line would appear noticing me that the times on Video 1 and Video 2 have matched, but now it doesn't’ appear at all.

 

Thank you for your time!

Premier estimates 331 hours to make my movie???

December 7, 2014, 6:03 pm

≫ Next: Premiere Pro CC 2014 Crashing/Not Responding on Windows 8.1

≪ Previous: I don’t know what I changed on the program…

$

0

0

I have a Dell Optiplex Core 2 Duo running at 3 Ghz. 16 gigs of memory, 2 TB 7200 RPM drive.

I have a series of 108 lectures, each ~20 minutes long, in .MP4 format, 15 - 20 megs each , that I want to turn into one movie.

 

I loaded them all into a sequence, and tried to export it as an MPEG2 movie. One of the DV formats, roughly 940 x 560 size, and I had to covert from 30 frames/sec to 29.7 frames/sec. Preview checked on.

 

331 hours is two weeks, if I don't crash.

 

Does one have to use a mainframe or a supercomputer to make a movie?

 

I recently bought a Mac Mini with an i7 quad core at 2.4 Ghz with a solid state drive and 16 gigs of memory. It is not yet set up. The Mac will be better but not that much better....

 

Thanks very much for any insight.

Jim

Premiere Pro CC 2014 Crashing/Not Responding on Windows 8.1

July 3, 2014, 6:07 am

≫ Next: Premiere CC 7.1 - Red frames in playback and export

≪ Previous: Premier estimates 331 hours to make my movie???

$

0

0

Unfortunately I "upgraded from CS6 to CC 2014 and can no longer do work.  The program stops functioning properly after a few minutes, whether or not I am doing anything or letting it sit.  It is not an outright crash, but what happens is that the video becomes non-responsive, though the audio plays.  I can cut things (though I cannot see) and, if I save the file, I can re-open and see the edits (until it goes non-responsive again).  In addition, once it goes non-responsive, though I can close the projects through File > Close Project and Exit, once I am out of PP CC 2014, I cannot open it again unless I go into Windows Task Manager and end the process.  I have tried to troubleshoot this, but am at a loss.  I have tried the following:

 

Updated my graphics driver (GF GTX 660, version 337.88)

Uninstalled all third-party plugins (Magic Bullet Color Suite)

Uninstalled/cleaned PP CC 2014 with Adobe's Creative Cloud Cleaner Tool

Re-installed PP CC 2014

 

Is anyone else having these issues?  Can anyone provide assistance?

 

Windows 8.1

Intel i7-3770

32 GB Ram

GeForce GTX 660

Premiere CC 7.1 - Red frames in playback and export

November 14, 2013, 8:56 am

≫ Next: Consolidate and Transcode in Cineform workflow: A great feature... if it worked properly .

≪ Previous: Premiere Pro CC 2014 Crashing/Not Responding on Windows 8.1

$

0

0

Having some problems after the 7.1 update.

 

In a variety of projects, on a variety of footage, we're experiencing random fully red frames (#ff000). Sometimes there are 1-2 frames in a clip, and occaisionally it's 80%-90% of the frames in a clip (this is less frequent). It has never been all of the frames of a clip.

 

This happens:

- On an undrendered timeline (you'll be watching an edit and you'll see a red frame - if you scrub back to it it'll still be there)

- On a rendered timeline

- In exports

 

Red frames that are visible on a timeline, are sometimes carried through to the export and sometimes not. Sometimes an exported file will display red frames that were not present on the timeline.

 

Red frames seem to be based on clips, not sequence frames. For example, in one of my exports, I had video footage with a lower third graphic over it. In one frame of the export, a red box appeared over the graphic, but the main shot was not affected.

 

This has happened to the following types of footage:

- .MTS (from C100)

- .MXF (from C300)

- ProRes 422 MOV

- ProRes 4444 MOV with alpha channel

 

Fixes that seem to work:

- If an export has red frames, re-export. Watch the new one like a hawk. Repeat until you get lucky.

- If a clip on a timeline has red frames, force a re-render via a Crop filter or similar

- Quit Premiere and reopen it

 

System/environment details:

- OSX 10.8.5

- Premiere Pro CC 7.1

- Mercury Playback Engine Software Only

- Often (always?) I-Frame Only MPEG sequence settings

- Much (all?) of the footage we've been working with has been on AFP shares via GigE with MTU of 9000

 

I haven't been able to confirm yet:

- Whether this ever happens with locally stored footage

- Whether this ever happens when Queueing to media encoder (rather than Exporting from Premiere)

- Whether changing to a QuickTime Desktop based sequence setting resolves the issue

 

Is anyone else experiencing this issue? It's frutstratingly un-testable, since it seems to happen at random. We'll continue to gather data points though and see if we notice any other trends.

 

Edit: Added additional system context

Consolidate and Transcode in Cineform workflow: A great feature... if it worked properly .

December 8, 2014, 5:39 am

≫ Next: Sony F55 Premiere Workflow

≪ Previous: Premiere CC 7.1 - Red frames in playback and export

$

0

0

Hello,

So my company recently acquired 17 licences of Creative Cloud teams, we were all very excited for the new 2014 features and capabilities of Premiere Pro CC and the new cineform codec workflow, plus all the connection between video apps on Cc..

Although it doesn't seem the most important feature, for us, the Project Manager on the presented cineform option of Consolidate and Transcode is a Big Deal for updating and preparing for archive older projects.

But the thing does not work, and its warnings and results are anything but clear or functional.

 

Example 1:

A full HD project 1920*1080 progressive 25pfs, mixed footage of apple ProRes and Quicktime Animation. Go to consolidade and transcode > sequence > quicktime > match source goPro Cineform :: FAILS..

Example 2:

Full HD project 1920*1080 progressive, mixed footage of Quicktime H264 (full hd) and RED 5120*2700, fails.. same error...

 

Example 3:

Full HD project, mixed footage 1920*1080, progressive jpeg sequence + MFX with fields.. fails.. same error..

 

IF INSTEAD of choosing "match sequence" i choose "match individual clips" sometimes it works partially but some MXF´s are not converted (premiere does not say why on the Events panel) and those are copied in all the original format. It does not makes much sense.

 

Now i can go on and on.. giving more examples.. Trent Happel, on a similar post here, explained that this error appears because the selected Format (my case Cineform) does not support the combination of frame size, frame rate and field combination.. Wish is ridiculous because its failing transcoding, standard full HD resolution, with or without fields, or experimented different fps and quicktime´s, MFX´s , Red´s or even sequences..

EVEN when i create a preset (based on cineform or any other) most of the time it fails.. and if a transcode a individual clip (that Premiere Manager was failing on examples described above) in its own solo sequence timeline (just that single individual clip), ironically it gives no error.. so what the heck is happening??

So now.. the company is really happy.. happy they are on the 30 day full refund period, for 17 licences bought based on a workflow adobe promotes, but fails consistently on real world application.

Help if possible is appreciated

---

Sony F55 Premiere Workflow

December 8, 2014, 12:37 pm

≫ Next: Problem with GPU power

≪ Previous: Consolidate and Transcode in Cineform workflow: A great feature... if it worked properly .

$

0

0

Howdy all,

 

So I'm having a bit of an issue trying to get a rhythm going for Sony F55 workflows in CC started. Firstly, I know that I can import the native files from the f55 camera and work with them directly. What I'd like to know is how I could set up a proxy for 4k footage, perhaps as a 1080p/ Pro res LT sequence, in order to add all the necessary effects and color correction without slowing my rig down. There are no plug-ins for the sony f55 for CC so should I just create a 1080p sequence and then relink to a 4k sequence? If so, when doing so should I set the clips to the frame size or should I scale to frame size? Or should I just do that in Encoder?

 

Also, I am working with footage shot at 50fps. The final sequence is set to 25FPS and so far there are only a few clips that I interpreted to 25 FPS in order to achieve the slow-mo effect. The others are supposed to be set in regular real time motion, as if they were shot in 25FPS,  but due to the fact they are shot in 50FPS, they all just play too fast. Again, If I interpret them to 25fps I can slow mo but I don't want that.

 

Can anyone help? I need to get this out by this weel and I am kind of at a stand still. Also, if anyone can link me a video for exporting this type 4k I'd appreciate it!!!

Problem with GPU power

December 2, 2014, 7:34 am

≫ Next: I hope next Premiere Pro CC update comes with LetterBox presets

≪ Previous: Sony F55 Premiere Workflow

$

0

0

Hello,

I would need your help.

I have Adobe Premiere Pro CS6.

I created the Boris Red 5.5 Composition but when you play at all really load the GPU, but only the

computer's processor. Video is played very slowly.

Overall, I have a problem with Boris FX, Graffiti, Red. Like operate only on the CPU, not the GPU.

Can someone help me?

Sorry for my English.

 

My computer:

i7-3930K

RAM: 32 gigabytes

Graphics Card: NVIDIA Quadro 6000

System HDD: SSD

Video HDD to SSD

 

Thank you.

 

 

 

 

I hope next Premiere Pro CC update comes with LetterBox presets

December 8, 2014, 6:47 am

≫ Next: .MTS files no sound

≪ Previous: Problem with GPU power

$

0

0

We missing in build letterbox presets i hope next version comes with letterbox presets

.MTS files no sound

February 14, 2013, 11:03 am

≫ Next: Best conversion to see a film on computer

≪ Previous: I hope next Premiere Pro CC update comes with LetterBox presets

$

0

0

We use Premiere Pro to edit .MTS files.  We have constantly experienced problems with Premiere Pro not importing sound.  Usually, updating everything (not just Premiere Pro) will solve this.  We currently have one machine were nothing is working, and right this second, we are deleting Premiere Pro to reinstall and try it again.

 

  This nonsense of constantly battling to get Premiere Pro to import sound has been going on for months.  Why is this such a horrible ongoing battle?  Is there something we can do?

Best conversion to see a film on computer

December 8, 2014, 10:54 am

≫ Next: Capturing Hi8 Tapes - My capture device is USB or S-Vid / Component Out. Will Premier Pro CS6 Recognize this device?

≪ Previous: .MTS files no sound

$

0

0

Hi,

 

I try Premiere Pro for the first time.

I made a film with Premiere Pro (56min) and I would like to convert it in the "best" format to read it on computer.

I tried a conversion but the result is not so great. The movements are "jerky" which is not so visible on the dvd conversion that i made. the size of the final Movie was almost 15 GB.

 

The movie has the following caracteristics :

1920x1080 (1,0)

30i/s

progressive

44100 Hz stereo

 

I tried the following conversion:

H.264

1920x1080 (1,0)

25 i/s (i'm in Europe)

PAL

VBR 1

Target Bit Rat = 32

Max Bit Rate 40

upper first

profile: principal

level 4.1

use maximum render quality

use previews

 

What am i doing wrong ?

Thanks a lot for your help.

Ludovic