https://forums.adobe.com/people/Ann+Bens  wrote FYI I do not (or seldom) mark my own answers as correct. Besides this was 6 months ago. Wasn't implying that, Ann (and agree that it's not necessarily a self-identifying mark).  Just trying to steer folks to the best outcome. ... View more

https://forums.adobe.com/people/Ann+Bens  wrote Officially mkv is not supported but there are users who can import mkv without an issue (like me). Easiest way is to convert with HandBrake to mp4. BTW 12.1.2 is not the latest build: 13.0.2 is. This has been incorrectly marked as the "Correct Answer." There is absolutely zero justification to degrade the quality of the .mkv file using Handbrake -- and it takes longer to render, anyway. As Basil notes, you want to demux the .mkv file into the .mp4 format that Premiere can read -- without any degradation or rendering time. However, if you prefer a graphic interface, just use the free program MP4Box with a full GUI: https://www.videohelp.com/software/My-MP4Box-GUI ... View more

  wrote I also have the same problem, caused me to quite often lose work.  Very annoying.  All it's doing is browsing the file system!! It's incredible that Adobe has totally ignored this issue for many years. ... View more

EdisonCreative  wrote Adobe, will there be an update coming for BRAW support in Premiere and AE? Please, please, please! We are an Adobe shop through-and-through but BRAW is such a game changer for us that we've been editing in DaVinci on recent projects. We don't want to leave   To keep holding us over (though Adobe needs to step up), Autokroma's BRAW Studio really does work; and I've created an hour-long video tutorial that goes in-depth showing how: http://www.focuspulling.com/braw One of my conclusions is that whenever Adobe finally comes around, it probably won't function much differently than this third-party plug-in (because RAW files still require a step of configuration at the clip level anyway). ... View more

fritzunruh  wrote Unfortunately I cannot, since I'm on a mac. Plus I'd really like to avoid a plugin just to import my footage. Of course, mainly Adobe needs to get over its paranoia and simply provide support to BRAW (like it does to other camera manufacturers like Sony who throw money at them, like the Venice getting V3 codec support pretty much instantly last week). But don't forget that RAW import is sort of always like a plug-in anyway.  Think of Adobe Bridge/Lightroom/Photoshop and how modules have always performed the import.  BRAW Studio (currently for Windows only, which is the best OS platform for serious editing anyway) actually works impressively well in their newest version, and feels essentially transparent as a user experience.  Give it a try, until Adobe gets over itself. ... View more

Frankly  wrote My fx are muted in Multicam, toggling the FX global mute doesn't solve the problem.  Cut first is not a solution because there are some clips with 180 Rotation effect.  What's the latest on this issue? This is a bug that Adobe has known about for years, but refuses to address.  Still broken. ... View more

https://forums.adobe.com/people/Viktor+sloth  wrote hello my dear adobe friends, for years i totally have given up on 4k renders, as it simple just always fails the rendering. 1080p is no problem at all, but bump it up to 4K and it's totally impossible to get out of the system. prior it has not been such a big problem as clients didn't really request it... but now they do! i work with RED files ranging from 4-8K footage in a 4K timeline. Export to a h.264 file in high profile. in full hd: no problems. the computer chews it up and renders super fast. in 4K: the computer slows dramatically down until it's inevitably failing. the error from AME is always about the GPU: Error compiling movie. GPU Render Error Unable to process frame. Writing with exporter: H.264 Writing to file: \\?\D:\Dropbox\film work\loopers\numero russia - march editorial film_2.mp4 Writing file type: H264 Around timecode: 00:00:21:22 - 00:00:22:06 Rendering effect: AE.ADBE FC PRO 2.1 Rendering at offset: 21,880 seconds Component: EffectFilter of type GPUVideoFilter Selector: 9 Error code: -1609629695 So, it's a GPU problem.. but why? i have the GTX 1080 Ti with 12gigs of ram. is this really not enough to render 4k files out? and how do you guys get your 4K files out? I get this all the time, similarly on a very powerful system, and FilmConvert is always, always, always the primary culprit.  Although Lumetri causes random crashes too, my Error Log proves that FilmConvert has got a serious bug in this area, when hardware acceleration is enabled. Meantime, Adobe loves passing the blame, when in reality this is a systemic problem of one side never talking to the other.  I have been nagging the New Zealand-based FilmConvert (small) team about this for years, and they haven't budged an inch improving the plug-in (indeed, the version history shows that they haven't made a single change for over two years, which is an eternity in the Adobe Creative Cloud culture).  It might be in the end that some kind of GPU memory leak, or whatever, is something that both sides need to work together on - not one or the other. And it's a totally unacceptable solution for us to bring our renders to a crawl by permanently throttling down to Software Rendering, making our GPUs essentially worthless. ... View more

I get this CONSTANTLY.  On a very high-spec'ed system, with no problems in any other application.  It's a bug that Adobe has not even bothered investigating for quite a while by now. ... View more

sampo  wrote Had the exact same problem and for me the fix was thrashing all cache and preview files. (I deleted Media cache, Media cache files, peak files and all audio and video preview files.) Now when Premiere has re-generated the files, everything works fine. I think the problem started after Premiere update. Adobe recommends deleting Media Cache files before update. I did not know that before, so I think the problem was caused by not deleting those media cache files before update. I'm quite certain that this isn't the thing which can fix the problem.  It remains an unaddressed Adobe bug. ... View more

https://forums.adobe.com/people/Dave+Merchant  wrote Game changer. https://www.blackmagicdesign.com/products/blackmagicursaminipro/blackmagicraw Up to 12:1 visually lossless compression at 32-bpc. Playback rates over 300fps at 4.6k on an iMac Pro without any fancy eGPU boxen. Unlike Adobe's dismal support for cinemaDNG, let's hope with a totally license-free open codec and cross-platform SDK this gets into Creative Cloud quickly. They're either so scared that Davinci Resolve will steal more of their customers, that they'll refuse to support this codec; or will ignore all of it (together with Apple's ProRes RAW lobbying that's utterly financial) and just do the right thing. With Blackmagic Design offering an SDK immediately, Adobe has no excuse... ... View more

www.focuspulling.com/cc2018 (check BIOS) ... View more

https://forums.adobe.com/people/Adam+Ullstr%C3%B6m  wrote - Encoding Time: 00:19:42 08/19/2018 09:27:19 AM : Encoding Failed ------------------------------------------------------------ Export Error Error compiling movie. GPU Render Error Unable to process frame. Writing with exporter: H.264 Writing to file: \\?\E:\Export\Test exports\V1 (19_30)_1 nyeste.mp4 Writing file type: H264 Around timecode: 00:02:33:25 - 00:02:34:04 Rendering effect: AE.ADBE Lumetri Rendering at offset: 153.987 seconds Component: EffectFilter of type GPUVideoFilter Selector: 9 Error code: -1609629695 ------------------------------------------------------------ Just want to let Adobe and people know that this is still a problem in 2018!!. This is a render for a 6K timeline for 360 VR mono output. With CPU and GPU hardly going over 35% in usage. In this particular case, the render stops at a particular point where there is a cut between 2 clips and both of them have the Lumetri Color correction on. I got the render out by just removing the Lumetri grade. Render it out and grade it in Resolve and re-render it out from Resolve. Not ideal and certainly not a solution. Adobe you are losing customers!  - and customers are losing their mind over stuff like this. This is the reason I ALREADY HAVE SWITCHED away from Adobe to Davinci Resolve. The project mentioned above was actually a friend and collegue's project that I helped troubleshoot with. After this, she will also switch to Davinci Resolve. Get your act together Adobe! It's really sad that Adobe -- for years -- just hasn't gotten this message, for fixing basic widespread bugs while bloating the program with barely used new features, and the only way they'll learn is by taking a beating from Down Under.  I love the shot of competition coming from Blackmagic (they've done this with their cameras magnificently), and Adobe ought to finally pay attention with humility. But it seems likely that folks like Jason Levine ("Adobe Jesus") are not the type to let Adobe course-correct, because it would hurt their ambitions to talk/teach about new things... ... View more

Having this problem too. Clearly yet another bug among billions, added by the recent "upgrade."  In my case, a nested sequence defined from the beginning with 5.1 audio will play back inside of a matching 5.1 timeline with only the stereo track that is stacked inside the nested sequence among the 5.1-defined tracks.  This has nothing to do with multicam (no "audio follows video") so of course the order of audio tracks should mean nothing.  When I mute the stereo track, total silence, even though all the 5.1 tracks are enabled.  But the nested sequence, when opened into the timeline, plays with all tracks firing. To make things even more ridiculous, this bug doesn't appear with the first (and only first) placement of the nested sequence in the timeline.  Just all subsequent placements, from that same nested sequence, using of course different in and out points from that original nested sequence asset.  But then, the problem goes away when you further nest the problematic/silent nested sequence.  There is no way Premiere is meant to work like this, and the stopgap (no matter what a mod says about "do whatever works") adds unacceptable clutter. ... View more

These are the kinds of ganged-on responses we've come to expect from Adobe on every bug report about Premiere, followed by haughty passive-aggressive "trying to be helpful" comments from forum admins who are literally compensated by Adobe. But the screenshot proves prima facie that the bug exists, not to mention at least another forum thread alluding to the behavior in nested sequences (same thing).  And that in turn presumes anyone/everyone would bother posting here, upon finding a bank vault of defense every time, anyway. I do think that the one Adobe-compensated person who tried to replicate this, didn't try hard enough. You need to have a sequence that has been converted to multicam, nested into another sequence with properly matching specs, and with all those nested UHD tracks (say, four) having Lumetri color applied.  Make the thing last normally, like a multicam sequence would -- not just a minute, but many minutes.  This is clearly something that happens when playback is moderately stressful (i.e., normal these days).  Basically, you didn't perform a stress test at all. It is obviously no solution whatsoever that we compromise our productivity dramatically by adjusting our workflows completely to accommodate this bug.  I won't be removing all color work from existing sequences, nor will I follow a dictated workflow in order to accommodate neglect by Adobe who are receiving record profits but not staffing up in equal respects:  • Adobe Systems net profit by quarter 2009-2018 | Statistic Jim Simon's typical admonition, proclaiming that a good editor adjusts everything to suit Adobe's bugs, amounts to unproductive noise.  That's what he's paid to say. This is not coming from an implicitly unreasonable or temperamental place; it's coming from pent-up disappointment over years of neglect in Adobe's ambitions to bloat Premiere without addressing its extraordinary, anti-consumer bugs -- combined with the way the corporation has bulked up its front lines with compensated forum apologists. They can keep banning people who express this, ignore them, and stay on course, or finally come to terms with the ubiquitous disgust in the real world that should soon lead to everyone jumping ship whenever a viable competitor finally teaches Adobe a lesson.  Blackmagic is the tortoise in this hare scenario.  Very exciting. ... View more

Here we are 1-1/2 years later, and Adobe is purposefully ignoring this bug.  Typical. ... View more

gavinb9475083  wrote Solution is available! Even though this thread was from forever ago, I thought I would try to help save anyone else time and frustration! For anyone searching on the internet like I was in the version of Premiere CC 17 for how to turn off all effects for preivew purposes. Our prayers have been answered! I can't tell you Adobe how grateful I am for this little feature finally. To gain this feature click the plus symbol in your program window to add the icon for the "global effects Mute" that looks like an "fx" icon. Ta-Da! The feature has been broken for years, in the context where it actually would have been the most useful (and Adobe totally ignores bug reports on this). You will find that the fx mute function automatically toggles back to inactive upon starting multicam playback, randomly but most of the time.  There is no fix, and no interest from Adobe in fixing the widely reported bug. ... View more

pavelt90913290  wrote Hello ! Just interesting thing, why only Intel QS can provide hardware accelerated decoding ? What about NVIDIA or AMD cards, which is 10x or more powerfull than Intel HD graphics ? Why AMD cards can accelerate decoding on MAC and not on Windows ? How it's come's up that simple VLC player use NVDIA power to accelerate playback and Premiere Pro CC 2018 Program or Source monitor can use only Intel QS with a lot of problems ( red screens on Reverce speed or jumping video on SloMo footages ) Why Adobe do not use all power of NVIDIA cards on decoding process or encoding ??? Why NVIDIA cards only accelerate effects, scale etc but not used to encode video or decode it during playback ??? Can someone give an intelligible answer ? Well, it seems you basically misunderstand the fundamental role of a discrete GPU in the Premiere environment.  Decoding has always been a task of the CPU anyway, this this (under-reported) QuickSync feature is just a further extension.  Meantime, a discrete GPU absorbs and accelerates tasks like color correction on-the-fly, transitions, etc. ... View more

https://forums.adobe.com/people/Stan+Jones  wrote I can't find this bug in the list. Premiere Pro: Hot (1767 ideas) – Adobe video & audio apps Can someone provide a link? This is a very old thread, and the workaround works for some and not others. I only found one other thread (with little followup by the poster), and I'm not sure what descriptions may be used. Premiere completely crashes when trying to change output name in export  The proposed "workaround" has certainly never been either a solution, or even remotely related to the bug. It's impossible that CUDA acceleration versus software-only via Mercury Playback Engine has anything to do with the dialog box/file system locking up after merely clicking the blue link to rename/relocate a destination file. Instead of resisting the issue or naming it "old," Adobe needs to finally fix it. The link you offered to "Hot ideas" or whatever, is not the official repository of bugs.  Staff are ignoring bugs anyway, identified from many sources.  That said, you overlooked this:  Crashing when renaming and selection destination of finishes project. – Adobe video & audio apps ... View more

JustinWoo  wrote Yeah, it's really terrible. The way I actually ended up fixing this crap was just buying another damn computer. Well, hold on - let's not mischaracterize the issue.  This is not solved by buying a new computer; it's a ​software​ bug that Adobe refuses to address. ... View more

RNKN  wrote Having this issue in version 12.1. It's very annoying because it happens about 9/10 times I try and export. I still can't figure out what is causing it to happen as it happens with CUDA and without. I'm shocked that after persistent and constant bug reports on this, Adobe has totally, totally ignored the issue for years.  It's a huge problem. ... View more

Jim_Simon  wrote I need the original H265 encoded file to load correctly into Premiere Pro, not a transcoded version of that file. Need?  Or want?  I'm at a lack trying to think of situations for the former. What I mean is, I believe you might be artificially limiting yourself here.  Do what works. Typical pro-Adobe, defensive, Jim Simon answer. Transcoding and thus degrading the file quality is unacceptable.  This is a widely reported problem elsewhere in these forums and the solution takes a little more than pointing to the usual "try this first" blow-off. ... View more

It's really annoying that this thread is marked as "answered" and after almost one full year, in fact Premiere still fails to support VR180.  Again, to be literal and specific, there was a claim that Premiere supports VR180, and nearly one full year later, that un-truth has not been addressed in a version update, at these forums, or anywhere else. ... View more

An unfortunate result of this thread is that it can fail to leave the impression that Adobe is 100% silent (not just here at these forums, but everywhere) on this major development in VR.  Supporting VR180 would require very little coding.  Adobe is cynical to not spend the resources on that, if they're waiting for some massive market penetration of the tech before moving an inch into this inevitable feature. ... View more

Crazy that Adobe is 100% silent (not just here at these forums, but everywhere) on this major development in VR.  Supporting VR180 would require very little coding.  Adobe is cynical to not spend the resources on that, if they're waiting for some massive market penetration of that tech before moving an inch on this inevitable feature. ... View more

mallabik@hotmail.com  wrote Ok so this explains the issue.  Apparently the Intel i9 Processor doesn't support Quick Sync.  Which is crazy because I have an email from Intel Support from when before I purchased the i9 that said it DID support Quick Sync.  They even provided a link to show case this was true.  I guess I will have to have a conversation with them. With all that said.  I have two followup questions.  Would Quick Sync really be any faster than using the 10/20 cores of the i9? And last question, is there hardware that I can add (PCI card?) that will give me very fast h.264/4k decode and encode?  I tried to use google to find some hardware and there is some stuff out there but it looks like a SOC (System On a Chip) products that needs to be turned into usable hardware. Any suggestions if I wanted to get something to do this faster? I think your instinct is right, that your high-end i9 would smoke a typical Quick Sync-compatible CPU anyway (certainly mine included, which is a Skylake i7-6700K).  That said, I think the feature is cumulative:  you experience all the benefits of whatever CPU speed you have running, and then as an additional acceleration layer specific to H.264 (and HEVC on Mac OS), Quick Sync further quickens exports. What's bothersome about this thread is that Adobe-compensated staff kulpreet singh (all lower case because too cool?) marked it as answered, even though he provided totally incorrect information about Xeon processors not making the list (they do) - and his/her answer is only partial and strategically vague, which is Adobe's modus operandi. ... View more