Extendscript in Premiere CC 2019 try catch not working

October 19, 2018, 2:01 pm

≫ Next: Audio wont import after first import.

≪ Previous: Premiere Pro CC 2019 sync import problem

$

0

0

I am having a problem with using a try/catch statement in Extendscript for Premiere CC 2019. The call

app.getProjectViewIDs() 

used to return undefined if there were no open project IDs, but now in CC 2019 it throws an exception, which I can't catch.

 

With the below code, I still get an alert saying unhandled exception. How do I handle this exception? For a reference I have only opened a blank, default project, and haven't loaded anything at this point.

 

try {

     return app.getProjectViewIDs();

} catch (e) {

     return null;

}

 

---

Audio wont import after first import.

August 30, 2018, 2:19 pm

≫ Next: Adjustment layer bug with scaled content

≪ Previous: Extendscript in Premiere CC 2019 try catch not working

$

0

0

Hi everyone im having a strange problem on any clip imported after the first import. Ill try to explain, I import my first clip everything is fine, if I batch import clips as my first Import in a project everything is fine, but any clip imported after the first import on a new project wont have audio. I cant link the audio it just says "generic import problem" ive cleared and renamed the cache and common but this doesnt resolve the issue. Im very confused why any subsequent import after the first just doesnt have audio but the same clips imported first will have audio so i know its not the clips. If i remove all clips from the timeline and library then import again the first import works fine again, even if its a different file than the last first import. I know it sounds very confusing but thats the best way i can sum it up.

 

Im importing video (mp4) and audio (m4a) from an Elgato HD60 game capture device. Im pretty cetrain this has nothing to do with the device or files being used as any clip imported first will work fine. Premier is all up to date as is my elgato software and Mac OS.

 

Thanks for reading, if you have any questions ask away.

 

Ian

Adjustment layer bug with scaled content

October 18, 2018, 8:10 pm

≫ Next: Premiere is desaturating/washing out my footage BEFORE export

≪ Previous: Audio wont import after first import.

$

0

0

Hi all - I've found a bug with adjustment layers, resulting in pixelated output as below:

Easy steps to reproduce: Place an image into a layer, scale it to anything but 100%. Create an adjustment layer above, set to Luminosity blend mode, and you'll see the pixelation. To make it smooth again either set blend method to something else or remove scaling. Obviously Luminosity adjustment layers are kinda important in broadcast... so this is a pretty major problem. This is with CC 2018.

Premiere is desaturating/washing out my footage BEFORE export

October 19, 2018, 2:39 pm

≫ Next: Old MBP worked fine until latest update - MP4s broken

≪ Previous: Adjustment layer bug with scaled content

$

0

0

Hi Everyone,

 

I've been having this problem repetitively across multiple projects and hoping someone on here can help me.

 

When I first import my raw footage into a project it looks exactly as it should. It looks far more saturated than on Quicktime, but looks exactly as it would if I had opened it on VLC or another player without gamma issues.

 

After this I will close the project for the day, and when I re open it, it is suddenly washed out. Looking more like as if I had opened it on Quicktime.

 

The only way I have been able to fix this is by creating an entirely new project each time I need to reopen the project, and re importing footage and sequences.

 

This problem makes 0 sense to me and I've searched everywhere for an answer, please let me know if you know of a fix it's been a huge problem!

 

I'm running the newest version of premiere (13.0), but had this problem before I updated.

 

Thanks!

Old MBP worked fine until latest update - MP4s broken

October 19, 2018, 3:10 pm

≫ Next: Video blown out after Exporting

≪ Previous: Premiere is desaturating/washing out my footage BEFORE export

$

0

0

I know I am using an old MBP, but I have used Premiere on it for over a year with no problems. I updated to the lastest software and all things went to hell. Can't get any mp4s to work at all. It loads just audio and gives me the "low level exception" error. I followed everything I could online, clearing/cleaning/deleting/reloading software etc. Nothing worked.

 

I then tried to go back to an older version software.  I thought I remembered being able to go through all versions... but now it only gives you specific versions you can go to. I don't remember what my last working version was, but I tried all the versions that you had available to me thru CC and the same error with mp4 (in H 264) came up. 

 

So I transcoded a folder full of my mp4s to Apple Prorez...and that at least imported to my timeline properly, but when I tried to render the timeline I got another low level error message.

 

So what gives???  I don't mind running an earlier version if you tell me my Mac is the problem...but I can't get back to making an earlier version work.  As it stands now your software is broken and unusable to me.

 

Thanks,

 

D

 

OSX El CApitan

10.11.6

 

MBP 3,1

Intel Core 2 Duo

2.4 GHZ

6GB RAM

Video blown out after Exporting

October 19, 2018, 3:36 pm

≫ Next: A low-level exception occurred in: lvcod64.dll (GetAVICodecs)

≪ Previous: Old MBP worked fine until latest update - MP4s broken

$

0

0

Just upgraded to 2019 -  V13.0. Video looks great in the monitor but after exporting the brightness gets cranked up to 10. See screenshots.

 

Before:

 

 

After:

 

 

I removed all effects, luts color grade, etc. and get the same result.

A low-level exception occurred in: lvcod64.dll (GetAVICodecs)

October 19, 2018, 3:52 pm

≫ Next: 2019 - No Video Displayed in Program or Source

≪ Previous: Video blown out after Exporting

$

0

0

After upgrading to the 2019 version of Premiere Pro CC I'm getting this error when opening any project. I can edit the project but I don't know if any work that I'll be doing will be compromised by this error. I need a position about this problem to continue working in any project in the 2019 version.

2019 - No Video Displayed in Program or Source

October 19, 2018, 4:14 pm

≫ Next: h.264 exporting as green with sound

≪ Previous: A low-level exception occurred in: lvcod64.dll (GetAVICodecs)

$

0

0

Seriously, was this beta tested? I understand Adobe owns a monopoly, but please....beta test this stuff. A focal point of video editing, the core function to even begin is to ohh....SEE the content!

 

Thankfully Adobes installer was highly inept and somehow left 2018 on....which works fine. Why rush out 2019 if it clearly is not ready???? Again, you are a monopoly, no competition to need to rush out.

 

Loaded 2018 file, took a long time to load, then after it cached, nada, double clicked previews, nothing, just a blank area. Space bar does not play my session.

 

Dell Precision 7720 (Core i7)

16GB RAM

Nvidia Quadro P4000

---

h.264 exporting as green with sound

October 19, 2018, 5:08 pm

≫ Next: Premiere Pro CC Crashes when changing to certain workspace layouts

≪ Previous: 2019 - No Video Displayed in Program or Source

$

0

0

The new PP 2018 update and 2019 have killed off any hope of exporting an mp4 video.

Everything was working fine until the update, since then I’ve had multiple error exceptions, red screen of death, media pending, blank project screens, constant crashes and now finally a green screen on exporting.

 

I’m about done with this software after what I’ve experienced this week.

 

Right now, I can export in every form perfectly except h.264. All it gives me is a green screen with the audio files.

I’ve tried:

 

Turning off accelerated h.264 decoding

Fully rendering before export

Changing the render settings to software only

Making my current CS19 file backwards compatible and using it on CS18

Updatimg drivers and manually setting graphics card to Nvidia

 

Computer:

 

Windows 10

16 RAM

Intel i7 CPU

Intel UHD Graphics 630

Nvidia GeForce gtx 1060

 

Any advice for how to fix this is most welcomed

Premiere Pro CC Crashes when changing to certain workspace layouts

March 28, 2018, 3:09 pm

≫ Next: Problem with Premiere

≪ Previous: h.264 exporting as green with sound

$

0

0

When I try to switch to "Assembly" workspace, the entire interface stops responding and I can't do anything until I force quit.

 

I'm using a MacBook Pro (15-inch, 2016), 2.9 GHz Intel Core i7, 16 GB 2133 MHz LPDDR3, Radeon Pro 460 4096 MB Intel HD Graphics 530 1536 MB

Problem with Premiere

October 19, 2018, 5:01 pm

≫ Next: Premiere Rendering Error: "Error compiling movie. Render Error. Render returned error..."

≪ Previous: Premiere Pro CC Crashes when changing to certain workspace layouts

$

0

0

Hola, tengo dos problemas con mi premier cc, no se donde publicar esto, disculpa si lo ago aqui.

1: Los efectos que instale preestablesidos que me funcionaban ayer , hoy ya no me funcionan algunos.

2: los titulos que creo en mi proyecto sobre un video los ubico en el centro, pero al exportarlos y ver el video final los titulos cambiaron de lugar no se porque me sale asi si no tienen ningun efecto ni nada solo estaticos,  y asi estan en el proyecto pero al finalizar aparecen en otra parte de la pantalla. Me explico?  gracias si pueden ayudarme.

 

Hello, I have two problems with my premier cc, I do not know where to post this, sorry if I'm here.

1: The effects that I installed preestablished that worked for me yesterday, today I do not work anymore.

2: the titles that I create in my project about a video I place them in the center, but when exporting them and watching the final video the titles changed place I do not know why I get it like that if they do not have any effect or anything just static, and so they are in the project but at the end appear in another part of the screen. I explain? thank you if you can help me.

 

[Here is the list of all Adobe forums... https://forums.adobe.com/welcome]

[Comments is to ask about the operation of the Forum, not a specific program]

[Moved from the Comments forum to the specific Program forum... Mod]

Premiere Rendering Error: "Error compiling movie. Render Error. Render returned error..."

February 22, 2017, 12:18 am

≫ Next: Cross Dissolve effect between a video clip and a still image

≪ Previous: Problem with Premiere

$

0

0

Premiere keeps giving me this "render error" when attempting to export a 00;01;45;00 long project as an H264. I've read some discussions where people had similar problems but none that I found helpful. (I uploaded a screen shot of the error message at bottom of post). I've ran into this problem before a couple months ago with another project in premiere, but I managed to fix it and successfully render the project after some tweaking and re-importing of certain content (the error message specified an 8 second window that could contain the content causing the error and I just made trial and error adjustments until it worked but took a long time to do so). I'm curious as to why I keep encountering this error and how I might go about fixing it and preventing it from happening again in future projects because it is a super frustrating error since one has to guess what content is causing the problem and have to delete the content and/or adjust effects on the content that may be causing the error.

 

 

I suspect the error may be caused by certain effects being used, or perhaps I have too many nests in the project (this never happened to me before I started using the nesting function for some reason). It could also be because my computer is not able to process the project because it could be more than it can handle (my hardware and software specifications are listed at end of post). I also have already tried updating Premiere to see if that would fix it and it did not. Could it possibly be being caused by using too may effects in Premiere? Should I try to stick with After Effects when when working with effects like color correcting and other more technical effects that require more work from my computer when applied to content in the project?

 

Any tips, advice, or experience from anyone else encountering the same or similar errors when rendering in Premiere would be much appreciated!

 

My hardware and software specifications:

 

MacBook Air: (13-in, Early 2014) running macOS Sierra Version 10.12.1 (16B2657)

Processor: 1.4 GHz Intel Core i5

Memory: 4 GB 1600 MHz DDR3

Startup Disk: Macintosh HD

Graphics: Intel HD Graphics 5000 1536 MB

Storage: 120.11 GB

 

Adobe Premiere Pro CC

2017.0.2 v11.0

(last Premiere Pro update was installed one day before I made this post)

Cross Dissolve effect between a video clip and a still image

October 19, 2018, 7:57 pm

≫ Next: Adobe 2019 products stuck on splash screen

≪ Previous: Premiere Rendering Error: "Error compiling movie. Render Error. Render returned error..."

$

0

0

I'm using the Cross Dissolve effect between a video clip and a still image.  I've also applied video effects (position and scale or panning and zooming) to the still image. The end of the video clip dissolves smoothly into the still but the still image is stationary until the very end of the video clip then jumps rather abruptly into the effects I've applied. It is not visually smooth. This is difficult to explain. It's not a problem dissolving between two video clips because there are a few frames or handles (and movement) at the end of one clip and the beginning of the one it's dissolving into. But it's a problem going from a video clip to a still frame. If anyone can figure out what I'm talking about - is there a fix or a workaround to make the transition smooth? I guess I'm asking if there's a way to make the still image start moving earlier so it is in motion as the transparency decreases in the transition?

Adobe 2019 products stuck on splash screen

October 19, 2018, 8:58 pm

≫ Next: Steps to Create a DVD, Pro vs Elements

≪ Previous: Cross Dissolve effect between a video clip and a still image

$

0

0

As title suggests, my 2019 products are all stuck on splash screens and do not open.

Steps to Create a DVD, Pro vs Elements

October 19, 2018, 9:05 pm

≫ Next: Low level exception occurrence in Adobe scopes

≪ Previous: Adobe 2019 products stuck on splash screen

$

0

0

I am thinking of upgrading to Premiere Pro from Elements, have downloaded the free trial,  and have questions about the entire process to burn a DVD from Pro.   In Elements you are able to add titles, apply transitions between media, add chapter titles, create a DVD menu, and burn the disc.  I expected to find all these functions in Premiere Pro, but now I am finding out that to do this utilizing Pro requires a combination of Pro, Photoshop, Encore and ImgBurn.   What software is required to burn a DVD with chapters and a menu?   And, when I installed the trial version of Pro, it erased Premiere Elements.

---

Low level exception occurrence in Adobe scopes

October 18, 2018, 11:46 pm

≫ Next: Premiere Pro crashes regardless of version, I can't fix it.

≪ Previous: Steps to Create a DVD, Pro vs Elements

$

0

0

Just updated to version 13 now cant open anything I've done keep getting the above error. 2015 mac os

Premiere Pro crashes regardless of version, I can't fix it.

October 10, 2018, 12:55 am

≫ Next: Project manager "unknown error"

≪ Previous: Low level exception occurrence in Adobe scopes

$

0

0

So, I've seen a lot of talk about Premier Crashing for other people, my problem is similar but is definitely caused by something else. This problem has persisted, whether I use CS6, CC 2014, CC 2018 or any other version, I can load it up drop a few files in, to test making a video, but as soon as I try to do anything it crashes. I can put it on the timeline but if I go into the effects it crashes, if I attempt to add a transition then crash, if I try to cut it together with no effects just splitting clips it crashes. I have reinstalled A LOT, my drives are up to date, It's got a good amount of ram since 12GB is not the best, but it's good enough for the 1080p I'm using. I'm fully up to date with Windows 10, and Creative Cloud is fully updated also, and yet it crashes. The other Creative Cloud Apps work perfectly fine, I can even do the intense stuff with those programs, yet the simplest of tasks crashes Premier Pro. I am effectively barred from using any version of Premiere Pro, and I don't have the faintest clue why.

Thanks for the advice you can give me.

Project manager "unknown error"

August 21, 2017, 8:34 am

≫ Next: Youtube export is not working

≪ Previous: Premiere Pro crashes regardless of version, I can't fix it.

$

0

0

   Hi,

 

After 2 years of using project manager to consolidate and back up my projects, it is now giving me constant grief.

 

On almost every project (mainly promos) it is unable to calculate project size og unable to back up my projects.

 

Every time giving me "unknown error", asking me to try again.  Not even once, has this improved anything.  I keep getting "unknown error"

 

It does not work and I've tried many combination of settings.

 

I will have to stop using Premiere as my editor if this keeps up.  I cannot keep backing up by copying 100s of GB of assets for a each 30 sec. spot.

 

What is going on?

 

Has a bug been introduced in the last few versions?

 

Does anybody else have these issues?

 

What could be the possible cause? 

 

Thank you

//Stig A.

Youtube export is not working

October 19, 2018, 11:00 pm

≫ Next: How to get premiere without Photography Pack?

≪ Previous: Project manager "unknown error"

$

0

0

Just updated premiere pro to the Oct 2018 update and now the youtube export is not working.

anyone having the same problem and can't upload directly from premiere to youtube?

How to get premiere without Photography Pack?

October 19, 2018, 11:19 pm

≫ Next: Facebook Exports

≪ Previous: Youtube export is not working

$

0

0

Hello, everytime my expired free trial prompts me to buy premiere it says that my current plan allows me not to. How can I only get / add premiere? I work with lightroom, photoshop, and premiere so for creative cloud to only sell in packs is a little bit of a problem..