DSLR footage no longer recognized? Adobe Premiere Pro 8.2.0, OSX 10.10.2

A few months ago I upgraded my mac to Yosemite, and around the same time updated Premiere.
Premiere CC 2014 Now has major issues with DSLR footage.
First, I was able to get some DSLR footage in, but whenever I scrubbed through it in the timeline or source monitor the image would freeze, then the software would lock up.
The footage worked fine on a PC running the latest version of Premiere, and there was nothing unusual about this footage - .MOV, .h263, same type of material I usually work with,
I tried opening several other projects (mainly non-DSLR footage, but .MOVs exported from other sources) and CC 2014 works fine with that, so I think it's just something specific to that footage.
TODAY I try bringing some different DSLR footage in to Premiere CS 2014 and it won't even turn up in Media Browser. I try to drag the .MOV file in, and I get an error that the file isn't recognized. I tried dragging one of the files to my internal drive, same problem.
I still have 7.2.2 installed (last full release of Adobe CC before it was relabeled 2014). That takes the footage fine in Media Browser, and scrubs through it like I'd expect.
What's going on? Is it Yosemite? Is it Premiere 8.2.0? Did Adobe suddenly drop native support for DSLR files and now expect us to transcode everything??
Please help.
-Brian

Yes, I am not sure why Vinay's response was a PM. Agreed it would have been helpful to post publicly. All I did was uninstall Premiere Pro CC 2014, clicked yes for the option to remove preferences also, then immediately re-install.
Here is Vinay's message:
Hi Brian,
We have noticed this issue recently on 10.10.2 and we are trying to find the possible cause and as per my information this issue might arise due to licensing issues. So, might be in the OS upgrade process the licensing files are corrupted but right now I cannot comment on it. Please follow the step of Clean un-installation of Adobe products and the re-install them again.
Please uninstall all the Adobe applications manually from Applications folder one by one. Once done go to below locations and delete the specific files.
~ Files / Folders ~ Click on Go menu in finder and select Go to Folders option to type these location and click go to Navigate
/tmp
/Applications/Adobe*
/Applications/.AdobePatchFiles (hidden, use Go > Go to Folder command)
/Applications/Utilities/Adobe*
/[startup disk]/Library/Application Support/Adobe*
/[startup disk]/Library/Preferences/com.adobe*
/Users/[user]/Library/Application Support/Adobe*
/Users/[user]/Library/Caches/Adobe*
/Users/[user]/Library/Caches/com.adobe*
/Users/[user]/Library/Preferences/Adobe*
/Users/[user]/Library/Preferences/com.adobe*
Once the locations are cleaned. Please re-install Premier Pro CC 2014 only to check if it works fine. Once checked you can install all the applications again.
Please PM me once it is resolved.
//Vinay

Similar Messages

Adobe Premiere Pro CC will no longer play program after weeks of editing it

Adobe Premiere Pro CC will not longer play my program when hitting the play arrow. The first time I hit it will play. But if I stop and then hit play again it just basically hangs up. I've been editing this program for several weeks in Windows 8.1 with over 1TB of free disk space. It would occasionally not play but if I restarted the program it would go again and I continued on. However, now it has the problem on this program all the time.      Basically I'm not able to put the finishing touches on my program and have not been able to use Adobe Premier Pro for several weeks now.   I'm basically paying a 1 year subscription for a program that is not working correctly. WHAT IS ADOBE DOING TO FIX THIS PROBLEM?   I see that there are countless people having this issue on the web, so I figure ADOBE is aware of this problem.    IS THERE A NEW RELEASE TO COVER IT? IF NOT WHEN WILL THERE BE A RELEASE TO ADDRESS THIS ISSUE?
If I start a new program it seems to work ok... but I probably have over 100 hours into the current program... starting over from scratch would not be good.. and what guarantee would there be that the problem would not occur again after another 100 hours was invested into it?

Thanks for the suggestion, I will give that a try.   It didn't work to go back a few weeks on the first try. As I get a chance I will try more saves that are further back.
Adobe Premiere Pro is working for me for the new music video project I'm working on today.
It's just this other program is large. 1/2 hour length.   If I push play it will work the first time. Then after I stop, and move the cursor to another spot, as long as I wait 2 or 3 minutes for it churn away and update the monitor, then it will play again.    As long as I wait 2 or 3 minutes each time it won't crash.   If I don't wait and start pushing multiple play and stop requests it will crash.   My machine has 12G of memory and 1Tb free disk space, and runs at burst speeds above 4GHz.
Several weeks ago I also had this problem.   I deleted all the render files and rebuilt them, and after that it worked for quite a while. This time I've tried that twice and it didn't help.
Maybe it has something to do with the order in which I render the sequences?    I might try that again, and experiment with the order of rendering.
There are 7 or

Audio-Problem with Adobe Premiere Pro CC 2014 by using long Clips in AVC-Intra Codec (4Gb Border)

Hello
We own a Panasonic camera (AJ-PX5000G) and we film in 1080p50 with the AVC-Intra100 Codec. When importing longer clips in Premiere Pro, the video is fully loaded, but the waveform of the sound ends at the Time Code 00:02:28:35.
Sometimes the sound could be played after this Timecode but otherwise there is no audio. Even if we use the same clip several times we see that it works sometimes and sometimes not. It looks random.
We also tried to import the Clips with Adobe Prelude directly from the P2-Card but there are the same problems.
The Clips in 1080p50 AVC-Intra100 have a bitrate of 227Mbps. After 2 Minutes and 28 Seconds 4Gb are written on the P2-Card and the Camera starts a new picture file and 4 sound files..
It looks like Adobe Premiere Pro has problems with the correct relation of the files that all get together to one clip.
Is there anybody who can confirm this problem? Can anybody help me with this Premiere Problem?
Dennis
(Workstation: Dell Precision T3600, Intel Xeon E5-1620 @ 3.60 GHz, 16 GB RAM, Windows 7 Professional 64-bit, Service Pack 1, Premiere Pro CC 2014.1 (Build 8.1.0)   )
Mediainfo of the P2-Cards:
General
Complete name                            : \CONTENTS\VIDEO\0068T7.MXF
Format                                   : MXF
Format profile                           : OP-Atom
Format settings                          : Closed / Complete
File size                                : 3.92 GiB
Duration                                 : 2mn 28s
Overall bit rate                         : 227 Mbps
Encoded date                             : 2014-10-15 13:33:41.000
Writing application                      : Panasonic P2 2.0
Writing library                          : Panasonic P2 2.0
Video
ID                                       : 2
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High 4:2:[email protected]
Format settings, CABAC                   : No
Format settings, GOP                     : N=1
Format settings, wrapping mode           : Clip
Codec ID                                 : 0D01030102106002-0401020201323104
Duration                                 : 2mn 28s
Bit rate                                 : 227 Mbps
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 50.000 fps
Standard                                 : Component
Color space                              : YUV
Chroma subsampling                       : 4:2:2
Bit depth                                : 10 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 2.193
Stream size                              : 3.92 GiB (100%)
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Mediainfo Audio-Datei P2-Card:
General
Complete name                            : \CONTENTS\AUDIO\0068T700.MXF
Format                                   : MXF
Format profile                           : OP-Atom
Format settings                          : Closed / Complete
File size                                : 13.6 MiB
Duration                                 : 2mn 28s
Overall bit rate mode                    : Constant
Overall bit rate                         : 770 Kbps
Encoded date                             : 2014-10-15 13:33:41.000
Writing application                      : Panasonic P2 2.0
Writing library                          : Panasonic P2 2.0
Audio
ID                                       : 3
Format                                   : PCM
Format settings, Endianness              : Little
Format settings, wrapping mode           : Clip (AES)
Codec ID                                 : 0D01030102060400
Duration                                 : 2mn 28s
Bit rate mode                            : Constant
Bit rate                                 : 768 Kbps
Channel(s)                               : 1 channel
Sampling rate                            : 48.0 KHz
Bit depth                                : 16 bits
Stream size                              : 13.6 MiB (100%)

Hi,
we have the same problem!
It is not possible to play audio with the AVC-Intra100 Codec fluently.
Can anybody help?
Thanks,
Anja

Adobe Premiere Pro CC no longer works

In (the) student (version) of Premiere Pro CC via the (Creative Cloud) app. on (It) installed, but every time (I try to launch) the program, to Adobe Premiere Pro CC no longer works. Other apps do work.
Message was edited by: Kevin Monahan Reason: translation to English

thanks the problem is solved,
greetings wolfturtle
2014-01-21 Kevin Monahan <[email protected]>
Re: Adobe Premiere Pro CC no longer works created by Kevin Monahan<http://forums.adobe.com/people/Kevin-Monahan>in *Premiere
Pro* - View the full discussion<http://forums.adobe.com/message/6034160#6034160

Why does Adobe Premiere Pro modify original footage/asset files (e.g. mov)? (CS6)

Background:
A colleague had given me a large 33Gb .mov for use in a project, I put this file on a backup drive.
I made an identical copy of this 33Gb .mov file and placed it in a folder that I'd use to work on a Premiere Pro Project.
I ran Adobe Premiere Pro CS6 and dragged in the 33Gb .mov file into the Sequence (imported it)
Premiere Pro CS6 started conforming the file.
After it had finished, I noticed that it's Modified Date was just now i.e different to the Modified Date on the original copy of the file on the backup drive (see step 1)
I ran a BeyondCompare check between the .mov file on the backup drive (see step 1) and the one that the Premiere Pro project was using (step 2, 3) and Beyond Compare reported they were different.
I had initially thought it was unrelated file corruption of some kind, but I have checked this several times and got the same outcome, so it's definitely Premiere Pro deliberately modifying the file.
So I am puzzled: these are supposed to be the same file.
Why would there be a need for Adobe Premiere Pro to modify the footage?
What does it do to the file?
Would it not be better to create a separate file if necessary?
I can accept this if that's how it works and it's good to know that it was Premiere Pro deliberately modifying the files and not corruption (so my hardware ought to be healthy). But it makes more sense to me if Premiere Pro made separate modified copies for its own use. Modifying the file as it does hinders my process for checking the integrity of backups; if the original asset footage files were the same as earlier copies then it would be easy to know that the backups are OK.
Thoughts?

Definitive Answer (I believe): It's all about this setting, "Write XMP ID To Files On Import" - which confirms that Adobe Premiere Pro is deliberately modifying the .mov file: http://helpx.adobe.com/premiere-pro/using/preferences.html#WSE3BD4A43-7022-4fe6-97F5-95313 935347B
These posts give some background as to why having this setting enabled would be beneficial: one benefit being to be able to skip conforming files by matching the conformed file with the original using the embedded XMP tag :-
http://helpx.adobe.com/premiere-pro/using/preferences.html#WSE3BD4A43-7022-4fe6-97F5-95313 935347B
http://www.dvinfo.net/forum/adobe-creative-suite/498627-why-premiere-modifying-video-files .html
https://forums.creativecow.net/thread/205/876064
(Found using Google search term "adobe premiere pro date modified")

Why are Adobe Premiere Pro CS6 source and program monitors playing each others footage?

Why are Adobe Premiere Pro CS6 source and program monitors playing each others footage? I import my footage into the project like normal. I drag it to the source monitor on the left hand side to set in and out points then I drag it to the time line. The footage drops into the time line with no problem but when I go to play the footage in the time line it plays back on the source monitor and not on the program monitor like it is suppose to. Other times ill drag the clip to the time line and trim it there and it will be fine and show up on the program monitor. Then ill go try to set a clip to have in and out points (which is suppose to show up in the source monitor) but it shows up in the program monitor. The clip is not even in the time line it should not be on that monitor! I have updated the program to the late update. I have re installed the program numerous times and I have even ran the Adobe Clean up program. Couldn't find much on this problem. Please help thank you! I have a PC. My computer is also way over the recommended minimum specifications to have the program installed on.

Definitive Answer (I believe): It's all about this setting, "Write XMP ID To Files On Import" - which confirms that Adobe Premiere Pro is deliberately modifying the .mov file: http://helpx.adobe.com/premiere-pro/using/preferences.html#WSE3BD4A43-7022-4fe6-97F5-95313 935347B
These posts give some background as to why having this setting enabled would be beneficial: one benefit being to be able to skip conforming files by matching the conformed file with the original using the embedded XMP tag :-
http://helpx.adobe.com/premiere-pro/using/preferences.html#WSE3BD4A43-7022-4fe6-97F5-95313 935347B
http://www.dvinfo.net/forum/adobe-creative-suite/498627-why-premiere-modifying-video-files .html
https://forums.creativecow.net/thread/205/876064
(Found using Google search term "adobe premiere pro date modified")

Capture Canon Legria HF R26 footage with Adobe Premiere pro cs5

Hello,
I need to capture some footage from Capture Canon Legria HF R26 using Adobe Premiere pro cs5.
I have a usb cable with the camera. I would like ot know if captirng via usb is a good option or if there are other better options .
Cheers m

Premiere can not 'capture' footage from any source using a USB connection.
Capture from tape into Premiere requires a firewire connection (DV & HDV).
For your camera, you should use the USB connection to copy the media files
from the camera to your hard drive and then 'import' the footage into Premiere.

Will Adobe Premiere Pro CC 2015 support direct import and editing of H.265 footage?

Hello, please let me know if Adobe Premiere Pro CC 2015 will support direct import and editing of H.265 footage. If not, when?

Kevin-Monahan: Your feature requests form is not working, I cannot fill in any data. It's like talking to a brick wall.
D. Chakalov

Adobe Premiere Pro no longer opening on my Mac

I have Adobe Premiere Pro CC 2014 on my Mac. My monthly subscription doesn't end until late November. I've been using Adobe Premiere Pro for over a month with no problems; lately, the playback has been slower, but I figured this was due to my slow hard drive/ larger media files/increased use of effects (and this may be the case, but I figured I'd mention this if there is a connection). The main problem is that Adobe Premiere Pro just WON'T open. The main screen opens up but every time it freezes at "Loading ExporterQuickTimeHost.bundle", as you can see in the screen shot. I then always need to force quit the application..... I urgently need a fix to this problem.

Not sure if these will help, but the only links I have
Quicktime errors http://forums.adobe.com/message/4545437
ExporterQuickTimeHost QT Version http://forums.adobe.com/thread/1109614

Adobe premiere pro cc 2014 - constantly crashing

Naturally, my project is under deadline..
My system is running OS X 10.9.4 (13E28)
late-2012 MacBook Pro Retina
2.6 GHz Intel Core i7
16GB 1600 MHz DDR3
Intel HD Graphics 4000
NVIDIA GeForce GT 650M
768Gb Flash Hard Drive
My project consists of DSLR footage (h.264 compressed files) and Zoom H4N Audio (.WAV files)
Even after spending most of Thursday and Friday on the phone with Adobe support; deleted all files from media cache, re-imported project, waited for premiere to re-conformed footage, etc..
...I still find my project loading sluggishly.. like it takes 15 minutes until video clips in the sequence will fully loads & appear in the project window... it becomes momentarily operable before quickly becoming inoperable as the video and audio no longer playback or respond to the cursor.
At that point (when playback no longer works) I can still save the project.
It seems as though the software loses the dynamic link between the footage as it completely goes black.
Then when I try to exit Premiere CC 2014.. the program locks up and crashes with no report.
The crash reports I have are from a few days ago when they first began and before they stooped generating reports.
Majority of the errors were:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
It also crashed a few times with the following errors:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00007fff5fbfdef0
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018
Any help would be greatly appreciated!

First I must say.. ADOBE PREMIERE PRO CC 2014 is glitchy as hell (and in my three weeks editing a documentary or rather two weeks bc I lost an entire week due to this issue) I have come to learn and identify some workaround solutions..
Here is what I originally wrote after speaking to five different Adobe engineers...
It is only an issue with PrCC2014 and the temporary solution before the upcoming update is to...
1) Go into Preferences... Audio... and UNCHECK the box next to "Maintain pitch while shuttling."
[this is a new feature in PrCC2014 that is processor intensive, causes audio dropouts, and is a major player in why the playback suffers]
2) Go into your sequences settings for each sequence you have for DSLR footage and change the Editing Mode preset to "CUSTOM"
3) Next scroll down to Video Previews and change the preview file format to "QuickTime" and the codec to "Animation."
4) Uncheck the box next to "Composite in Linear Color (requires GPU acceleration or max render quality).
[this is another new feature that is also processor intensive & is also a key suspect to the problem]
THE KEY TO FIXING (temporarily) THE BEHAVIOR
When your computer begins to show signs of the glitchy - sluggish playback behavior..
Stop.. go back into your SEQUENCE SETTINGS and change it to a different EDITING MODE (only temporarily) and click OK.
You could change yours from ProRes to CUSTOM (as indicated in step #3)
Next a prompt will pop up asking you...
Click okay then immediately go back to SEQUENCE SETTINGS and change it back to your original setting, in your case, ProRes.
Somehow, by DELETING those PREVIEW FILES it essentially resets the issue... until the dreaded glitchy behavior returns.
I have had luck with this trick and hopefully you will too..
Cheers!

XDCAM HD workflow with Adobe Premiere Pro CC and Macbook Pro

Hi folks,
I have an assignment for a TV production to secure and convert the data (mxf files XDCAM HD 422 1080i 50 / 50 Mbit/sec with 8 audio channels) from Sony XDCAM camcorders (PDW-700) for postproduction.
The producer wants me to convert the mxf files during production to Apple ProRes 422 (HQ) for faster and smooth editing during postproduction.
I'm not sure about the final output yet, but I guess it will be either 720p50 or 1080i 25, since the production will be broadcast and as far as I know this is the standard for HD on German television. It is also not clear which NLE will be used for editing (usually one of the producers edits their projects with FCP, but this time they've got their hands full and are still looking for someone to outsource postproduction.
Unfortunately, my Macbook is getting fixed as we speak, so I can't try things out.
Since this is the first time I'm doing this workflow, could someone please check if I got everything right?
1. Can someone please confirm that I can actually convert the mxf files using AME CC to Apple ProRes 422?
Or do I need to install any other tools/converters for this task? Does MPEG streamclip do the job? Any other freeware?
2. When converting to Apple ProRes422, the producer suggested to deinterlace the footage (1080i 50) to 25p, if 720p or 1080p I have to find out tomorrow since our conversation got interrupted this afternoon.
In my opinion this doesn't make sense, though. First, if output to 1080i 25 it has to stay interlaced anyway. Second, in case the output will be 720p 50 I would edit the footage either natively or in Apple ProRes 422, but leave deinterlacing until the very end when outputting to the final format. This way I could use an advanced deinterlacer, e.g. the one from Magic Bullet Suite, rather than just checking some deinterlace box in the export settings for Apple ProRes 422.
The reason the producer suggested to deinterlace right away when using an intermediate like ProRes was that she and the client got irritated by the jagged lines from the interlaced footage when editing the last project with the same requirements on a progressive display.
3. What would be the best solution to tackle this issue (jagged lines) during editing?
As I said my Mac is getting fixed, so I have no way of trying things out,and I usually edit DSLR footage which is progressive anyway.
But if I remember correctly I can switch my monitor between 1080p and 1080i. This should do the trick, shouldn't it?
4. Can I keep all of the 8 audio tracks when converting to ProRes using AME CC ?
5. Is ProRes422 (HQ) really necessary, or is the regular quality sufficient for this kind of job?
6. Let's assume the whole project would be edited within Adobe Premiere Pro CC and system specs as stated below:
Since Adobe Premiere Pro CC has native support for XDCAM HD is there any advantage of using an intermediate like ProRes at all?
How smooth is native editing with XDCAM HD in Premiere Pro CC? I don't think there will be more than 3-4 video tracks in use...
Thanks for your help!
working with
Adobe Premiere Pro CC and Adobe Media Encoder CC
Apple MacBook Pro
Intel Core i7 Quad Core Prozessor
2.3 GHz and 6MB L3 Cache
16 GB RAM 1600MHz DDR3,
256 GB SSD
Intel HD Graphics 4000 512MB + nVidia GeForce GT 650M with 1 GB GDDR5 RAM

Thanks Jim! I knew there must be a reason xdcam is widely uses for eng aquistion :) I think they used FCP 6 or 7 on their last project... So what about monitoring interlaced footage on a progressive screen? Any advice on that? Is there a converter built in to APP CC that deinterlaces in realtime when monitoring interlaced sources on a progressive screen? And would you agree that deinterlacing source material is best left right before outputting?

Adobe Premiere Pro CC 2014.2 (8.2) freezes up constantly on Mac OS X Yosemite

After the latest update (no idea which one but the latest update) Premiere Pro cc just keeps freezing up constantly. There's no indication what brings it up but after different periods of time I just get the apple wheel and the entire program freezes up. I force quit and get the "sorry, a serious problem has occured", blabla. Sometimes it's in the middle of cutting a clip, sometimes it's while trimming. There isn't a single indication what causes it. At first I thought it was only because of using a multicam clip, but that's not the case anymore. I tried reducing memory to other apps, deleting preview files, deleting autosaves, turning off autosave altogether, deleting Adobe Premiere 8.0 preference file, changing permissions, basically everything in this post: Re: Adobe Premiere Pro CC keeps crashing... (Which now also seems totally neglected by Adobe).
Believe me, there's hardly a thing I haven't tried.
It's getting REALLY frustrating now and it's time something is done about this. Yes I know, "don't just say it's frustrating, explain the problem", but that fase has passed now. I'm paying for this product and it needs to work like it should.
Also I know I'm not the only one who's having these problems.
My specs are:
OS X Yosemite 10.10.1
MacBook Pro (Retina, Mid 2012)
2,3 GHz Intel Core i7
16 GB 1600 MHz DDR3
NVIDIA GeForce GT 650M 1024 MB

Hi JJ,
JJ Millen wrote:
It is not about the past times you may or may not have participated, but about the latest message from rob654 and my last messages in that thread (which are clearly not about Windows).
One great reason to get a Mac only version of the post. It is never a good idea to post on a Windows post with Mac problems. And when threads get so long and unruly, the team can't focus on the actual issue so it doesn't get the attention it needs.
Now that we have that sorted out...
JJ Millen wrote:
I checked that and it says 8.2.0. (65) build.
Thanks for the verification. You are running Premiere Pro CC 2014.2 (8.2). It helps to have that absolutely clear.
JJ Millen wrote:
Here are all the checkpoints mentioned in that thread, applicable to my project:
- Version 8.2.0;
- My Creative Cloud says Premiere Pro is up-to-date;
- Operating system is OS X Yosemite version 10.10.1 (14B25);
Very well, did things operate any differently on Mac OS X 10.9.x? Or did you have the same problem?
JJ Millen wrote:
Type: MPEG Movie
File Size: 4,0 GB
Image Size: 1920 x 1080
Frame Rate: 25,00
Source Audio Format: 48000 Hz - 16 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00:12:35:16
Pixel Aspect Ratio: 1,0;
So is this H.264? What is the camera that you are working with? DSLR?
JJ Millen wrote:
- I do not get any error messages, except for the "Sorry, a serious problem has occurred"-message after I have to force quit my Premiere because of the freeze;
What kind of drives are the media files stored on?
Are the permissions set correctly (as Read/Write) for the Mac HD and your media drives?
Are the permissions set correctly for all the Adobe folders as I outlined in my blog?
JJ Millen wrote:
- The problem mostly occurs when cutting a clip with the razor tool, regardless of the kind of clip;
When you import clips, are you using File > Import, or are you importing via the Media Browser?
JJ Millen wrote:
- Yes this has worked before, the problems started either after creating a submix (which I've deleted, without result) and/or after updating to a newer version of Premiere CC;
Definitely do not update Premiere Pro or OS X when in the middle of a project. Wait until it's complete. If you did either or both of these things, you can cause your project to become corrupt. After your current project is wrapped, test with a brand new project.
JJ Millen wrote:
- The only software I run actively besides Premiere is Apple's Mail program, Safari and/or Chrome, sometimes Wire, sometimes Spotify;
- I currently have no third-part effects or codecs installed in Premiere;
- I installed the latest CUDA Mac Driver, version 6.5.37 (release date 01/14/2015);
- The problem just happens while working in my sequence, not in any final output. I don't know what is meant by "previews", but I have the yellow bar indicator in my sequence, if that's info you need.
I have heard of others having issues with OS X 10.10 and NVIDIA GPUs. My advice is to consider downgrading your OS if you continue to have issues. I believe I have avoided a lot of trouble by sticking to OS X 10.8.5.
Previews AKA the Media Cache are your "render files." They can become corrupt, so it's a good idea to trash them when troubleshooting. You can locate them via your Preferences > Media. Click the Browse button.
JJ Millen wrote:
Okay I went through that menu (which I'm not eager to do, I prefer direct contact) and came across the CUDA setting inside the project settings. I've now enabled the "Mercury Playback Engine GPU Acceleration (CUDA)", which might help.
So were you set to "Mercury Playback Engine Software Only" or "Mercury Playback Engine GPU Acceleration (OpenCL)" prior to changing it to "Mercury Playback Engine GPU Acceleration (CUDA)?
JJ Millen wrote:
Testing with a brand new project is not an option. I have a deadline for my current project and it's impossible to start from scratch. What I did try is start a new project and importing the existing one, which didn't help so far.
I was just wondering if you experienced the same issues in a new project. Any project you update to a new version is suspect, in my opinion. In the future, try to avoid doing that. If your current project is corrupt, I could see why you are having certain issues.
For what it's worth, we had another user that exhibited similar issues until they started with a brand new Premiere Pro CC 2014.2 (8.2) file.
Since importing your 8.1 file to a new 8.2 project isn't working, make sure to triple check permissions on all the Adobe folders I laid out in my blog post: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
It's the #1 reason Mac users experience freezing and crashing. The other one I'd look at is that NVIDIA drivers are not working well with Yosemite. Finally, if you update a project across versions, it can become corrupt. Not much you can do about that except start a new project ASAP.
Thanks,
Kevin

Adobe Premiere Pro CS3 3.2.0 update

Thought I'd share a bit of information on the 3.2.0 update that will be coming out via AUM this morning. The update will come out first via AUM, then will be available on the updates page shortly after at http://www.adobe.com/downloads/updates/?ogn=EN_US-gntray_dl_updates.
The readme will also be hosted at http://www.adobe.com/support/documentation/en/premierepro/releasenotes.html.
Dave Helmly has posted about the update on his blog, as well: http://blogs.adobe.com/davtechtable/2008/04/xdcam_and_premiere_32.html#more
New in this release:
- This update adds compatibility with the Sony XDCAM range of cameras. This includes disc-based XDCAM and XDCAM HD cameras., and the newer SxS-based XDCAM EX cameras. Content from XDCAM cameras can be imported and edited natively without transcoding or conversion. This makes possible similar workflows to Panasonic P2, including the ability to edit content directly from XDCAM EX cameras.
- Note: Adobe Premiere Pro CS3 3.2.0 does not support IMX editing or XDCAM HD50 editing at this time. Export to XDCAM is also not possible.
- Adobe Premiere Pro now has presets for HDV 24p. Note: Adobe Premiere Pro does NOT support print to tape in 24p mode.
- Improved handling of MPEG streams (e.g.: HDV video), along with error detection. MPEG stream errors can occur during recording due to tape dropouts, record start/stop glitches, timecode breaks, etc. Bad frames caused by these MPEG stream errors are identified during import/indexing or playback. These frames will play back as full red frames to alert the user that there is a problem in the encoded video at that location. Adobe Premiere Pro will also log error messages to the Events panel, indicating where the error(s) were encountered in the stream. Users can open the Events panel, determine the location of the MPEG stream error, navigate to that location in the clip and take corrective action, such as trimming out the video glitch or covering up the red frames with duplicated good frames copied from before or after the glitch. Note: MPEG files will need to be re-indexed to take advantage of the improvements in Adobe
Premiere Pro CS3 3.2.0. For more information, please see Working with MPEG Files.
Notable fixes:
- Titles/Footage no longer show up as offline when reloading saved projects.
- Rendered preview files no longer missing when reloading saved projects.
- Certain filters and/or transitions are now applied correctly when reloading saved projects, until the timeline is forcibly refreshed.
- When exporting via the Adobe Media Encoder, there is no longer a long delay before the progress dialog shows and rendering resums (Mac OS 10.5.x only).
- 24p HDV clips shot on a Canon XH A1 no longer come in incorrectly as 30 fps clips.
- Creating an offline clip in the project window then attempting to link it to media on disk no longer results in the application crashing.
- QT PAL movies rendered out of Adobe After Effects® software are no longer incorrectly identified as requiring rendering in a Adobe Premiere Pro PAL project.
- DV Clips of certain specific durations are no longer incorrectly identified on the timeline as requiring rendering.
- For P2 DVCPro clips, the right-most pixel column no longer contains video garbage.
- Fixed a memory fragmentation problem that would occur with projects with many custom bin columns.
- Fixed a bug where exporting to a QuickTime movie (with QT 7.4) would crash the application.
- Selecting "display only exact name matches" when relinking clip no longer crashes on Leopard.
- Fixed an issue where 30p and 30f HDV clips would incorrectly be identified as requiring rendering in a 29.97 progressive project.

Harm,
I don't use HDV, so I'm not sure if this is the case or not, but in the top post, there is mention of having to re-index the MPEG files "to take advantage of the improvements in Adobe Premiere Pro CS3 3.2.0." While it seems this should be an automatic process, maybe wiping out the previously-created index files (I seem to remember them being in the Media Cache folder when importing MPG files from DVD rips and such) would let the project open. Or, maybe the old trick of importing an existing project into a new one? Just a couple thoughts...
To the other poster: surely, I don't jest. At least, not when it comes to anything in the video production industry and my operation in it. Long ago, I gave up expecting perfection from any particular piece of hardware or software, and just focused on being creative. That's why I got into this. I refuse to let any piece of equipment dictate what I can or can't do--I just find another way around. Funny how we managed to make it as a species and a civilization as long as we have, and now that computers are here to make our lives easier (*snort*), we're quick to raise our ire about everything that's wrong with them. That's why I will always marvel at things built long ago prior to the advent of all the technology we take for granted today.
Anyway, we're all entitled to our opinions, and I've taken this thread completely off-topic. My apologies, so...

Adobe Premiere Pro CS5.5 Crashing on Render/Encode

So, this is a pretty non-complicated problem. I think I have narrowed it down.
So basically it's this, I try and render footage that is about 10 minutes long. About 3/4's of the way through that Adobe Premiere Pro crashes. It just shuts down, no warning. Computer is still on, and the CPU Load reduces to about 10% from 80%-90%. I think I have narrowed it down to the problem of the CPU overheating. I got speedfan, lastest version and I look at it, pumped all the fans up to 100%. It still crashed along with the CPU heating up to about 52-55 degrees Celsius. Now you might be thinking that is extremeley low, but my CPU is usually at a resting temp. of 38 celsius.
Please help, everything is updated. I think the problem is that I only have 3 fans. GPU fan, CPU fan, and a fan to suck air in. The problem lies with my case. It is so POORLY designed that with my MotherBoard it LITERALLY CANNOT FIT ANY MORE FANS IN THE CASE. Now, words cannot describe how angry I would get at the person who designed the case, but hey, you get what you pay for. Do you guys think this is purely Overheating - I'm sure if I tried hard enough I could fit another fan in there. Or something else - because I don't think it should shut down at 50 celsius.
Specs..
AMD Radeon Sapphire HD 6850 Graphics Card
AMD FX(tm)-6100 Six-Core Processor
ASUSTeK Computer Inc. M5A97 R2.0 (motherboard)

Take the side off the computer case and put a small fan next to the computer to blow room air onto the CPU and motherboard
If that works, you know you need better cooling (maybe use the furniture brush with your vacuum cleaner... computer power off, of course... to remove any dust bunnies)
How are you with building a computer... so do you think you could move everything to a new case?
I built a computer for my wife a couple months ago http://www.pacifier.com/~jtsmith/ADOBE.HTM and with options, the case has 4 fans and her CPU runs fairly cool

Adobe Premiere Pro CS3 Confusion

Hi guys,
I have very basic problem in Adobe Premiere Pro CS3. When I import video it's size is scaled down and quality is rapidly droped down. When I export it quality is very bad and my video have a black frame. How would I keep the quality and get rid of black frame?
I really need this project to be done soon, thank you very much!
Maksimilijan.
Project details:
DV - PAL
Widescreen 48kHz
30Fps

The great little utility, G-SPOT will tell you what FRAPS is Exporting. What you are seeing is a disparity between that FRAPS footage, and your Project Preset. They must match 100%. You will most likely need to set up a Desktop Project and adjust the Frame Size to match your footage.
Also, going back about a year, there were several long threads on FRAPS footage into PrPro. I would Search this forum for "FRAPS," and read. There were some good tips in those. One was quite long, and used to have some neat flight-sim screen-caps, but last time that I looked, the images were no longer up on the OP's server, so they will be missing now - the discussions were all still there.
Good luck,
Hunt

DSLR footage no longer recognized? Adobe Premiere Pro 8.2.0, OSX 10.10.2

Similar Messages

Maybe you are looking for