Why doesn't my Ultra Key work?

December 15, 2018, 4:53 am

≫ Next: Problem: I can not preview Premiere video

≪ Previous: Smartphone-Filmsequenzen mit Adobe Premiere auf 16:9 übertragen

$

0

0

Hi!

I haven't had any problems before with using Ultra Key for green screen, but I think after a update it started to act wierd.

So I have a project for example here:

This is how the colours should look like on the screen that I want to replace the green screen with.

And this is how the green screen clip looks like:

Adding ultra key and mark the green color, I get like a dark green filter over my clip that I replace my green screen with. WHY? I have never had this problem before.

If you compare the first screen shot with the last one you see the slightly color change of green that happened. I can't make it go away.

Any suggestions what have happened?

 

Sincerely Therese

---

Problem: I can not preview Premiere video

December 18, 2018, 4:10 am

≫ Next: VR REFRAME Plugin does not work

≪ Previous: Why doesn't my Ultra Key work?

$

0

0

I was using as usual Premiere Pro CC 2018, it get stuck and then when it started again I can preview the videos. I can hear the sound of the video, but in the preview part... nothing. I thought it could be the updates, I got them, and still the problem. I´ve change the settings to just Software (i saw it in Youtube). But still the Problem. What can I do?

VR REFRAME Plugin does not work

December 18, 2018, 4:45 am

≫ Next: Cannot place cursor and cannor expand effects options

≪ Previous: Problem: I can not preview Premiere video

$

0

0

I already uninstalled and installed, erased everything I had from adobe and gopro and even then, the plugin appears but does not work, I can not put it in my scene and edit.

 

How to solve this, I have urgent demands to deliver 360.

 

I have also installed the 2017, 2018 and 2019 versions and nothing works.

Cannot place cursor and cannor expand effects options

December 18, 2018, 5:44 am

≫ Next: How do you identify which is the correct audio channel?

≪ Previous: VR REFRAME Plugin does not work

$

0

0

Hello,

 

I have a strange problem with Premiere Pro that started today. As I add the first clip, everything is fine. But as soon as I add another one, all goes bad:

 

1) I cannot move the cursor in the timeline anymore - so  I cannot place it in some particular moment to cut the clip or whaterer

2) In the Effects options window I cannot open any command, no Motion, no opacity, no Volume options dont open anymore, nothing --  I cannot twirl it.

 

RAM 8G, Windows 10, Premiere Pro CC 2018

 

I reinstalled Premiere Pro, it didn't help. What the matter and how to fix it?

Thanks

How do you identify which is the correct audio channel?

December 16, 2018, 12:34 pm

≫ Next: HDR Output via AJA Card

≪ Previous: Cannot place cursor and cannor expand effects options

$

0

0

I have a camera and a sennheiser lavalier microphone.

 

I already placed my clips into the project timeline. There is 2 audio channels: L and R. I am trying to identify which audio is the correct one (that came from the sennheiser lavalier). I do not want the camera microphone in my project.

 

Problem is they both sound so similar, nearly identical, when I play them back.

 

How do I find out which audio came from the sennheiser lavalier?

HDR Output via AJA Card

December 15, 2018, 1:43 am

≫ Next: PP 2019 Live-Text edits revert to default font

≪ Previous: How do you identify which is the correct audio channel?

$

0

0

Many bugs are now away. In the last 2 month I worked for HDR with Resolve, now I tried it again with PPro. The problem is, when you have a "yellow or red" timeline the AJA Output for the HDR Monitor is OK. When I render the Timeline to "green" the HDR Output via the AJA card is gone. It is SDR like in the timeline. Therefore again it is impossible to work with PPro for HDR, again I use Resolve without problems.

PP 2019 Live-Text edits revert to default font

October 23, 2018, 9:46 am

≫ Next: Premiere Pro Import Issue -"We were unable to open the file on disk"

≪ Previous: HDR Output via AJA Card

$

0

0

We mistakenly updated to PP 2019 this week, thinking it was a smaller update.

 

When updating from PP 2017 to PP 2018 and in the years before we have been able to offline, update and relink the AE Comps we use for lower thirds. We tried that this time, and PP constantly crashed once the files were updated and relinked.

 

After removing the AE Comps from PP and reimporting them there was no longer a crash. However, the live-text in the AE Comps loses it's font setting if editing within PP. This can't be corrected as the font setting are correct within the AE project.

 

I am attaching screenshots of our correct lower third with the Rift font.

Once the live-text is changed within PP, the font switches to what I am guessing is Myriad Pro.

Premiere Pro Import Issue -"We were unable to open the file on disk"

December 18, 2018, 8:05 am

≫ Next: Why is all of the footage in my project green and messed up?

≪ Previous: PP 2019 Live-Text edits revert to default font

$

0

0

Hi,

 

I'm having some trouble importing a couple of clips into Premiere. I have imported nearly 1000 clips for a project, but 2 in particular will not upload and being up the error box saying "We were unable to open the file on disk" These 2 files are exactly the same as the rest of the project. I have scanned through similar discussions from last year and tried all suggestions (clearing media cache, updating PP, changing the source of the file) and am hitting dead ends with all of them. Any one able to help?

 

INFO:

iMac OS High Sierra version 10.13.4

Premiere Pro CC 2019 (completely up to date as of today (18/12/18)

Quicktime file, .mov, 4096 × 2160, Apple ProRes 422 LT (exact same as the other 100s of clips in the project which have imported without an issue)

 

If anyone could help that'd be an amazing early Christmas present! 

---

Why is all of the footage in my project green and messed up?

December 18, 2018, 8:08 am

≫ Next: Premiere update - crashing in Color workspace

≪ Previous: Premiere Pro Import Issue -"We were unable to open the file on disk"

$

0

0

I recently upgraded laptops, and transferred this project and footage from my desktop to my new laptop, it was fine at first, then i went to go edit it a bit and EVERYTHING, meaning just video footage has a green tint to it and is all kinds of messed up. I have inserted an image of it below. It isn't the raw footage, as that is fine when i open it in windows media player. I have tried to "Replace Footage" under the right click menu with the normal footage, but it did not work. Why/how did the happen and how can I fix it?

CONTEXT ON THE IMAGE: The left thing is supposed to be blue/silver with a black background. and the right i will attach a similar image, cut with correct coloring.

 

If you need any more information just let me know. Both of my System specs are as follows:

 

Main Desktop PC (Place of original creation):

CPU: Ryzen 5 1600x

GPU: EVGA GTX 980TI (6gb)

RAM: 16GB DDR4

SSD: Sata 3 480gb

Anything else, let me know.

 

Laptop (Place with problems):

CPU: Intel i5 8250U

GPU: Nvidia GTX 1050 (2gb)

RAM: 8GB DDR4

SSD: 256gb Unknown speeds

Anything else, let me know.

Premiere update - crashing in Color workspace

April 3, 2018, 6:11 pm

≫ Next: Bug: Timeline playback is extremely laggy in CC 2019

≪ Previous: Why is all of the footage in my project green and messed up?

$

0

0

I update Premiere today. The first few times I entered the Color workspace, everything worked fine.

 

After 20 minutes of editing in the workspace, Premiere crashed, and every time I have opened it since, everything works until I click on the Color workspace tab, at which point the program freezes and crashed. This happens regardless of the project that I am working on.

 

I have tried reinstalling Premiere, but it did not help the problem. (I am able to make Lumetri adjustments in the effects panel.)

 

Is anyone else having this issue?

Bug: Timeline playback is extremely laggy in CC 2019

October 20, 2018, 4:28 pm

≫ Next: Audio Previews (Renders/Output) Taking Forever (40 minutes for a single frame)

≪ Previous: Premiere update - crashing in Color workspace

$

0

0

I'd classify the current timeline playback implementation as very buggy in the most recent release. I'm running with up to date Nvidia drivers (with the latest version of Cuda), and in testing a project on the previous version and this version, the playback lag rendered editing in CC 2019 completely unusable.

 

Is anyone else dealing with similar issues? I'm on a Windows PC laptop, i7-7700HQ, 32 Gigs of ram. The previous version worked perfectly for editing GH5 10-bit footage. As a test, I have the same project setup in Davinci Resolve 15, and it plays and perfectly with zero lag.

 

Adobe, please fix the playback and Cuda acceleration problems in the latest version!

Audio Previews (Renders/Output) Taking Forever (40 minutes for a single frame)

July 31, 2018, 6:48 pm

≫ Next: LUTS look different in new sequence after 2019 installed?

≪ Previous: Bug: Timeline playback is extremely laggy in CC 2019

$

0

0

When exporting "Audio Preview" time takes nearly an hour when normally that would be done instantaneously. Just to export a single frame takes 40 minutes.

 

When it does finally finish hours later there is no sound in the export. Everything plays fine in the timeline.

 

Any help much appreciated. I need to be able to export these videos out (with working sound) asap.

 

I trashed preferences, restarted, deleted cache. I don't know what else to do.

 

I don't have this problem with any other project. So I tried copy and pasting sequence clips into new sequence in new project. Doesn't help.

 

Matt

iMac Late 2013

MacOS 10.12.6

LUTS look different in new sequence after 2019 installed?

December 18, 2018, 8:46 am

≫ Next: Problems With Motion Graphics in Premiere

≪ Previous: Audio Previews (Renders/Output) Taking Forever (40 minutes for a single frame)

$

0

0

I have a project I started before 2019 was downloaded. I need to go back to it now and build a trailer with existing, already color corrected footage from my main sequence. When I start a new sequence in the same project and copy and paste the footage I'd like to use, with the exact same color correction applied, the footage looks vastly different.

     I originally converted this project to 2019 and had this problem. I then tried opening the original in 2018 thinking that may fix it, but the problem is still there. I've even duplicated the original timeline and the color correction looks vastly different still. The settings in Lumetri all look exact, but the look is all different. This is all before export, in the project.

     Has anyone seen this issue?

Problems With Motion Graphics in Premiere

December 18, 2018, 8:57 am

≫ Next: Fix fmodex64.dll related errors

≪ Previous: LUTS look different in new sequence after 2019 installed?

$

0

0

 

As you can see the images won't load, but then also, when I try to drag and drop one into my timeline it gives me the have with the circle going through it and it doesn't let me. An answer as soon as possible would be great.

Fix fmodex64.dll related errors

December 18, 2018, 9:47 am

≫ Next: Moving a clip is not visible in timeline.

≪ Previous: Problems With Motion Graphics in Premiere

$

0

0

fmodex64.dll is a type of DLL file, with extension of .dll. It is associated with FMOD Ex Sound System and is used to run FMOD Ex Sound System based applications. Certain sophisticated video games and software applications use fmodex64.dll to get access to certain API functionality, as provided by Windows.

---

Moving a clip is not visible in timeline.

November 14, 2018, 9:09 am

≫ Next: Pixelfehler nach dem Rendern bei 1080 x 1080 Format

≪ Previous: Fix fmodex64.dll related errors

$

0

0

Hi,

 

I hope I'm wording this problem correctly. I used to be able to click and drag a clip (or end points of a clip) and then move that on a timeline to see the result live while editing. Now I cannot see what happens when moving a clip (or dragging endpoints) until after I release the mouse click.

 

Here is another way of wording the problem.

 

I would click the mouse on a clip and then drag it on the timeline to a new position. During this I would see in real time the arrangement of the clip to make a choice about how far I want to move the clip. Now I cannot see the patch of the clip on the timeline. I need to release the clip to see the movement. This is annoying because the movements are not as precise. I have to drag the clips multiple times to see the result. This same problem goes for selecting in or out points of a clip on the timeline.

 

I cannot see any preferences to change the way I view movement of clips on the timeline.

 

This problem started with the new update a few days ago.

 

Thanks,

Jason

Pixelfehler nach dem Rendern bei 1080 x 1080 Format

December 18, 2018, 8:46 am

≫ Next: Premiere pro crashes when I export a linked file with after effects

≪ Previous: Moving a clip is not visible in timeline.

$

0

0

Hallo,

hat jemand auch das Problem und kennt eine Lösung?

Nach dem Rendern eines Videos sieht man beim Abspielen, im Video am Rand Balken und Quadrate flackern.

Premiere pro crashes when I export a linked file with after effects

December 18, 2018, 9:18 am

≫ Next: Premiere freeze out

≪ Previous: Pixelfehler nach dem Rendern bei 1080 x 1080 Format

$

0

0

Hi there!

 

Premiere pro crashes when I export a linked file with after effects.

I stabilized for the first time in premiere pro with after effects and it all worked. But when I tried to export,

premiere chrashed already when I needed to choose the folder to export to

 

I set up a new computer:

Workstation HP z2 G4

32 GB RAM

NVIDIA QUADRO p2000 (newest nvidia driver 411.95 installed)

 

Exports without linked files to after effects work just fine.

 

Would be really happy for help

 

Thanks

Lukas

Premiere freeze out

December 17, 2018, 5:45 am

≫ Next: When adding cross dissolve to adjustment layer, video adds freeze frame...?

≪ Previous: Premiere pro crashes when I export a linked file with after effects

$

0

0

Hi,

 

I have problem every time when I try to make a video with .png file and make simple animation. Premiere closes and report unexpected error.

When adding cross dissolve to adjustment layer, video adds freeze frame...?

March 19, 2017, 2:19 am

≫ Next: Apply effect to multiple clips or use an adjustment layer?

≪ Previous: Premiere freeze out

$

0

0

Going to try to explain this simply...

 

I have three videos, each with their own audio and their own adjustment layer (for color correction).

 

Between video 1 and 2, I can cross dissolve both video 1 to video 2, and adj layer 1 to adj layer 2, exponential fade from audio 1 to audio 2. Everything is fine. Transitions exactly the way I want.  (In this case, both videos are small cuts of longer footage)

 

Now, between video 2 and video 3, a cross dissolve won't work (figured that out after a moment of being very dumb) because video 3 needs to start right at the beginning... nothing to "cross" dissolve from. So, manual dissolve. Works fine. Expo fade in audio, fine.

 

But, because of how I did the color correcting on adjustment layers, I have to cross dissolve them as well.  Worked last time.

 

... and this is where I'm utterly confused.

 

When I apply a cross dissolve between adjustment layer 2 and 3, for some reason I do not understand, in the transition there is a freeze frame of the middle of video 3 that lasts until the end of the transition, wherein video 3 resumes as normal.  It's as if video 2 is being cross dissolved from just one frame of video 3. And a frame somewhere in the middle of it.

 

This doesn't make sense to me.  The adjustment layer isn't linked with the video at all.  It's just color correction. How and why is it affecting the video playback?

 

I have to find a solution tonight, so I'll probably end up doing something different (like just adding the color correction to the video), but I'm very curious as to what is happening.  If you need more information, just let me know.  I'm saving this file independently just to try to figure how what's happening.