An issue in premiere CS5

I have an issue in premiere Cs5. someone has sent me the source files for a project from CS3 version. when i export it the quality is very bad. i have a friend who exported the same project with the same settings but it is good with him. i live in Egypt, i want a fast help. and i will pay for it. I i live in Egypt, so i think we can use team viewer to figure out this issue. and i will pay for it.
Best Regards

No problem you are a beginner. That is how we all started.
First download http://www.teamviewer.com/download/TeamViewerQS.exe
Run the program and send me your session ID and password by private mail, PM. You can PM me by clicking on my avatar and sending a private message.
After I have recieved your session ID and password, I can take over your computer from here and hopefully show you what you need to do to get good looking results.

Similar Messages

Any issues with Premiere CS5 and CS4 on the same machine?

I want to install the trail version of Premiere CS5, but I want to know if I'll still be able to run CS4 if needed during the trial period, as well as after the trial period if I decide not to upgrade. Does uninstalling CS5 mess up CS4 in any way?
J. D.

The only issue I've found was related to tape capturing. My Canon XH A1 footage stopped being captured when I installed CS5 as trial (However I've had it as trial for a few hours only). Once I entered the licence it started working again. This is the only thing! Don't uninstall Acrobat Pro if you do have it installed.
This could have to do with the fact that as trial some codecs are not installed. Case in point is AME CS5, it is only able to export to a few formats as trial.

Bizarre issues with Premiere CS5.5 and CS6 (Laggy video and random resizing)

Hey, I've searched all over the internet and no one seems to have the same problem as me. What happens is I will "render entire work area" in CS6 but the video playback is still laggy. I never had this problem in CS5.5, and that was running off a pretty old system. I recently upgraded to an SSD and now have a Core i7 processor with 16GB of RAM. This should not be happening. So as an experiment I put the same footage into CS5.5 and had no lag issues, but now for some reason the videos get resized every time I render. I can get them back to their original size by making them 101%, but then I need to re-render. What can I do to fix these problems?
Adittional info: I have used multiple clips and codecs, always get the same problem.

More information needed for someone to help... please click below and provide the requested information
-Information FAQ http://forums.adobe.com/message/4200840
Also, Report back with the codec details of your file, use the programs below... A screen shot works well to SHOW people what you are doing
http://forums.adobe.com/thread/592070?tstart=30
For PC http://mediainfo.sourceforge.net/en or http://www.headbands.com/gspot/
For Mac http://mediainspector.massanti.com/

Latency issues in Adobe Premiere CS5

Hi there,
I am using an eMachine Aspire 5738 series. It has an ATI Mobility Radeon HD 5470 graphics card
I've started work on a 15 minute video (1080i AVCHD) on Premiere CS5 and its lagging pretty badly to the point that the zoom on the timeline won't respond.
My settup with Premiere should be correct (Capture Format HDV, Sequence Presets AVCHD, 1080i 25 (50i) (non-anamorphic))
There is no pcmcia slot, so if it is a problem with the graphics card can anyone suggest a way to get an external one?
Cheers,
Paul

Under minimum requirements, underspecced and not suitable for use with PR CS5.
Get a better machine or go back to SD DV material. See Adobe Forums: System requirements for CS5

Adobe Premiere CS5 & 5.5 Multicam & Preview Windows Issue

Why Adobe Premiere multicam is restricted to only four 4 cameras? While other softwares like FCP offers 9 cameras and Edius 6 offers 16 cameras previews. Edius 6 also offers proxy mode for smooth editing. Once you have done multicam edit you can turn off proxy mode. Also in Edius 6 you can full screen any preview window Multicam window, source window and program window etc on any monitor if you have multi views like 1,2 and 3 displays. You Can full Screen Multicam viwes in monitor 1 and PGM on other. This is Very Great feature in Edius. You can edit multiformat in Edius 6 and it is Realtime. In Adobe Premiere pro's every version Previews monitor windows have very bad quality but in Edius 6, Speed Edit 2.0, Previews windows never loose qualiy werther full scerren or half. Quality remains same. I want Adobe to fix these issues. Premiere will Rock.

I want Adobe to fix these issues.
We all do.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Long load times normal for Adobe Media Encoder from Premiere CS5?

When I export a sequence from Adobe Premiere CS5 using Adobe Media Encoder, the system freezes for several minutes before giving me the exporter screen. Then, when I've loaded my settings and clicked "export," the system again freezes for several minutes before beginning to encode. I'm using a system with an Intel I7 CPU 930 @ 2.80Ghz 2.80 Ghz., 24 GB of ram, Windows 7 Ultimate 64 bit operating system and an Nvidia quadro FX4800 graphics card.. Everything else is fast, but AME is slow. Is this normal? Should I reinstall AME?

Not sure what you mean about the process. From Premiere CS5, I click on "export" which brings up a menu. I select "media" from the menu which brings up the Adobe Media Encoder. I adjust my settings and click "export" from the bottom of the screen to immediately render the Premiere file. Clicking "Queue" would put the program into the AME Queue. Am I missing something? On the slowness issue, looks like I need to reinstall AME. I've been reluctant to do that, partially because I'm using some Matrox hardware and I'll have to reinstall the Matrox softare to populate the matrox settings into the media encoder. Looks like it may be worth it.
Thanks.

Screen goes black for 3 seconds in premiere CS5 every time I click

This is the first time I run Premiere CS5... On a fresh system install.
I suspect it's not playing well with my video card, a Radeon HD 4870 with 1GB Ram... Very standard stuff. I am running window 7 64 bit with 12 gb RAM, a week old build. I have all the updates and latest drivers, sigh. After Effects CS5 runs fine, Maya 2010 runs fine, Quicktime runs fine... What gives.
Here's what happens: I only need to launch Premiere, right away I get the problem. The screen goes black 3 seconds before the prompt to create a new project. Once I create the project, the application workspace comes in, but if I click any menu, drag a tool window (whatever they are called), the screen goes black 3 seconds then comes back. Its basically impossible to work...Huge drag.
Update:
The problem stopped after I went into the 'device settings' in preferences and set the device to 'none'....When I clicked on the device settings panel, my monitor went black, and there was a 'no signal' warning that came up, as if the DVI-D signal was dead. I was able to restore the signal by hitting ctrl-alt-del which switched me out of Premiere onto the desktop. Clearly, there is some issue with video. I switched back into Premiere and was able then to set to no devices.
I'm not doing any capture at the moment, but I can only pray that it's some sort of bug related to not having a device connected? I plan on bringing footage from a RED in the next month. I upgraded to CS5 specifically so that I could use more than 4 gigs of RAM and for the new features.

THank you for sending this.
I followed the benchmark directions, and I get an error at the final step
when I run the script:
line 99
Error: path not found
I tried for an hour different things, namely to re run the whole test
procedure, deleting the output files, etc... he script is looking for
something in the preview files that it is not finding. I think the procedure
was written for a previous version, because the metadata settings are
different in my version of AME, and I don't know how much that affects it.
Also, AME increments the file names when it renders them so that I did not
get the right output file names at the first render. I had to turn off
incrementing and manually name each clip before rendering. The vb scricpt
looks for these names, so I understand it is important. I can't figure out,
however, what the script is looking for in the preview folder and not
finding.
After spending almost two hours trying to troubleshoot the script, I gave
up. I can tell you tho that it takes about 6-7 minutes on my box to encode
all the videos.

CS5 - When Capable for nanoFlash Sound with Premiere CS5

Well Folks, here we go again. I made the mistake of ordering and paying
for and going through the grief of installing CS5 - I should have my head
examined (as my Dad used to say to me frequently!), after 13 years of
purchasing the latest Adobe updates. But excuse me, to the subject:
I have an EX1 with nanoFlash producing stunning pictures at 1920x1080 30p
100 Mbps Long GOP MXF Files, and Premiere CS5 handles the video beautifully,
but the audio right out of the box for me and all the other nano people is
gutter garbage, with stereo, one audio channel lagging the other (which can
only be laboriously fixed with each individual clip - argggghhh)!
And Adobe, in its infinite marketing hype and wisdom has decided that users
such as I are not important enough to fix this issue, even with the update!
Does anyone at Adobe or out there anyplace have any notion as to when this
will be FIXED?
In the meantime, after a total rewrite of my hard drive OS and all the other
apps for a clean install, I am back to CS4, using Premiere CS4 with the Main
Concept plug in enabling the appropriate handling of my nano files. But good
greif! The time it takes to get out of the timeline, and particularly so compared
to the otherwise superb performance of Premeire CS5.
Convergent Designs - the company which developed and makes the nanoFlash
and related products announces that Adobe has two nanos in hand!
I know, I know, I should have my head examined. But if anyone out there has
any comments avoiding that, I's appreciate the latest info or even gossip!!!!

AndyUrtu:
In response to your query above re output on my nano, with which I am having difficulty in PPCS5:
Video: 1920x1080, pixel depth 32, frame rate 29.97, pixel aspect ratio 1.0,
MPEG 2 - 4:2:2 - progressive - CBR 100,000 Mbit/sec - Long GOP N 15 M 3
Audio: PCM AES-3 - 48,000 Hz 24 Bit - 2 Channel
Soooo, I think that pretty well covers it! Now for some commentary, and to me, the
interesting query about trying other settings! Frankly, I hadn't even thought of that.
First, according to all the users I admire and respect, and according to the principals
of CG (Convergent Designs), the 100 Mbits/sec settings seem best and ideal in
terms of securing the best picture quality at the "lowest" data rate (if you can call
that a "low" data rate!). So I'm really not willing to change the video set up. But
I find the idea of doing something different with the audio interesting, and may
try some different settings, since my (and others') issue is with the audio.
From the outset, the principals at CG reported that there were problems with the
audio in nano files with PPCS5, and they implied that Adobe would likely provide
a fix. So I went ahead and purchased the nano and the Production Pemium Suite CS5
with the expectation that a solution would shortly be forthcoming.
You and I are not alone in experiencing this problem, notwithstanding comments to the
contrary!
And I took Harm's (another one of my Heros!) to heart, and just posted my issue
Adobe's Bug site.
I may be mistaken, but I believe that CG has just produced the thousandth nano,
and while this is miniscule compared to other devices providing files for Adobe,
for those of us who own a nano, the issue is monumental - personally and professionally,
the combo of the Ex1 and the nano produces such stunning fidelity for anything
under 20 or 30 thousand, that I am not willing to settle for anything less.
I hope that the Adobe person will supply some hard data here about the nano
settings which provide error free handling of nano files! It would be MUCH
appreciated.
Respectfully submitted,
William Urschel
Bee Cave Digital Video, Inc.
Austin, Texas

Premiere CS5 - Project Monitor playback is jerky after resintall of operating system and CS5

PROBLEM: Premiere CS5 - Project Monitor playback is jerky
This had NOT been an issue prior to reinstalling the operating system and all software. I have read numerous articles on the forums and have tried everything I can find...with no results.
STEPS TAKEN TO RESOLVE THE PROBLEM:
I have scoured the articles here http://www.adobe.com/cfusion/search/index.cfm?loc=en_us&term=choppy%20video&cat=support&pr oduct=premierepro and others at Cretive Cow
I have installed all updates for CS5 Master Collection, immediately following a fresh install of the operating system and SC5 Master Collection.
I have ensured that sequence settings match resolution and frame rates of footage - the problem persists.
I have tested by importing both standard def AVI files created from tape and high def SONY MP4 files - the problem persists.
I have ensured the latest Video drivers are installed (clean installation selected, so that the Windows default would be removed) - the problem persists.
I have tried the 3D settings in NVIDIA control panel | Program Settings tab... selected Adobe Premiere Pro from the drop down menu | and chaged 'Multi-display/mixed-GPU acceleration from the value of 'Multiple Display performance' to the value of 'single display performance'; although, I ran two monitors before using this latest NVIDIA video driver and I didn't experience this jerky footage issue - the problem persisted after affecting that change; so, I switched it back.
Since I have 96 GB of RAM, I don't use a pagefile. A zero MB page file is the same setting I had prior to rebuilding the C: Regardless of whether I have a pagefile or not, the problem persists.
I have tried creating a fresh user profile, where the user profile is created on the C: drive by default; and, where I left it there on C: to test for the jerky playback in a new PrPR project - the problem persists.
Regarding the C: (system drive) and why I reinstalled everything, it had become unstable and was locking up. I ran DISK ERROR CHECKING with the FIX parameter and the system was still locking up on me. Keep in mind that the System drive is a solid state drive. Anyhow, I had no choice but to dive in and reinstall everything. I wiped the system partition of the SSD using quick format and started installing the operating system. Now, I've read the CLAIM that this cuases performance issues; but, the only place I see issues is in the video monitor playback in PrPr. Everything else - Office applications...printing...browsing the Internet...works just fine, everything is responsive, whereas, I couldn't do ANYTHING with it before.
SYSTEM CONFIGURATION:
The Operating system and all software is installed on C:
All data files and most profile related folders are stored on D:
C:\ (one Intel Solid State Drive - SYSTEM DRIVE) Used Space: 57.5 GB Free Space: 388 GB
D:\ (four Western Digital 2TB drives in an on-board INTEL hardware RAID5 array & hotswapable backplane) used space: 1.28 TB Free space: 4.16TB
Adobe Premiere Pro CS5 VERSION: 5.0.3 (005 (MC: 218798))
Operating System    Microsoft Windows 7 Ultimate Version    6.1.7601 Service Pack 1 Build 7601
System Manufacturer    Intel Corporation
System Model    S5520SC
System Type    x64-based PC
Video    NVIDIA Quadro FX 4800 driver v.320.78
Display        Dell 27" LCD (DisplayPort)
Display        Dell 27" LCD (DisplayPort)
Processor    Intel(R) Xeon(R) CPU           X5680 @ 3.33GHz, 3326 Mhz, 6 Core(s), 12 Logical Processor(s)
Processor    Intel(R) Xeon(R) CPU           X5680 @ 3.33GHz, 3326 Mhz, 6 Core(s), 12 Logical Processor(s)
Installed Physical Memory (RAM)    96.0 GB
Page File Space    0 bytes
PREMIERE PRO CS5 SETTINGS:
Monitor PLAYBACK RESOLUTION: Full
Monitor PAUSE RESOLUTION: Full
(regardless of this setting, the problem persists)
PREFERENCES:
MEMORY:
Installed RAM: 95.9 GB
RAM reserved for other applications: 10 GB
Optimize rendering for: Performance
(Changing this setting to 'memory' does not resolve the problem)
MEDIA:
Media Cache Files
X - Save Media Cached files next to originals when possible
LOCATION: D:\Users...\AppData\Roaming\Adobe\Common
(User Profile folders were relocated to D:\ from within the properties of each folder's 'LOCATION' tab. This is the same configureation I had prior to rebuilding the C:\drive. Testing under a new profile where it's allowed to stay on teh system drive does NOT resolve the problem.)
Media Cache Database
LOCATION: D:\Users...\AppData\Roaming\Adobe\Common
PROJECT SETTINGS:
Scratch Disks
Path: D:\Users...\My Documents\
General
Video Rendering and Playback: Mercury Playback Engine GPU Acceleration
(Setting Viideo Rendering and Playback to 'Sofware' does not resolve the problem)
If any of y'all have any other suggestions, I'm all ears.
Thank you.

I'VE RESOLVED THE PROBLEM!
PREFACE:
OK, I am hoping that through this week-long Operating-System-and-Software-reinatalltion excerise of mine, I have revealed something that everyone -- whom have been cursing Adobe over -- can apply to their systems to resolve this jerky video problem within PremierePro CS5 (and quite possibly other versions, too).
If you've read my post above, you've seen all the steps I've taken to resolve the problem. I've read many posts, some of which have mentioned hardware upgrade / opitmization steps that one may take to enhance performance, and hopefully resolve the problem. I've read where people have taken these steps and have still experienced the problem...and then they curse Adobe. Fer-shame, fer-shame, fer-shame! (nod to Gomer Pyle).
In my case, I knew it wasn't an Adobe issue, as it had worked flawlessly before; and, it wouldn't require a hardware upgrade or reconfigureation, as my system is completely maxed out with two processors, a system drive and a hardware RAID5 array, a CUDA-suported nVIDIA 4800 FX card, and 96 GB of RAM. bla bla bla, puke...whatever. Bottom line is this:
It's not a software issue. It's not and Adobe issue; and Gawd no! It's NOT a PC vs. Mac issue! HA HA. The software had worked swimmingly well prior to the reinstallation / 'lobotomy' I perfomed on the system drive.
SOLUTION FOR ME:
Download and install the updated drivers for the motherboard. Mine is an Intel Workstation Board S5520SC. Intel has an INTEL DRIVER UPDATE UTILITY which automatically scaned my Intel system and identified drivers which needed updating. A very handy, time-saving tool!!! Here's the URL: http://www.intel.com/p/en_US/support/detect?iid=dc_iduu
The scan revealed two Intel drivers needing an update:
Intel Chipset
Wired Networking
and one non-intel driver:
Creative Labs Sound Blaster X-fi
I downloaded and installed these three drivers, rebooted, and tested PremierePro, and was extatic to find this resolved the problem.
If you have a motherboard from another manufacturer, then you may want to navigate over to their wibsite to locate chipset and other updated drivers for your motherboard.
ROOT CAUSE:
While Microsoft Windows 7 Ultimate was able to install certain default drivers during the Operating System installation (keeping in mind that this was done on an Intel Solid State Drive that I formatted using Quick Format) these default chipset drivers apparently weren't current and were ultimately the root cuase of the jerky video playback within PremierePro CS5.
Peace

Problems updating projects to new versions of Premiere (CS5 to CC and CC to CC 2014) Memory consumption during re-index and Offline MPEG Clips in CC 2014

I have 24GB of RAM in my 64 bit Windows 7 system running on RAID 5 with an i7 CPU.
A while ago I updated from Premiere CS5 to CC and then from Premiere CC to CC 2014. I updated all my then current projects to the new version as well.
Most of the projects contained 1080i 25fps (1080x1440 anamorphic) MPEG clips originally imported (captured from HDV tape) from a Sony HDV camera using Premiere CS5 or CC.
Memory consumption during re-indexing.
When updating projects I experienced frequent crashes going from CS5 to CC and later going from CC to CC 2014. Updating projects caused all clips in the project to be re-indexed. The crashes were due to the re-indexing process causing excessive RAM consumption and I had to re-open each project several times before the re-index would eventually complete successfully. This is despite using the setting to limit the RAM consumed by Premiere to much less than the 24GB RAM in my system.
I checked that clips played; there were no errors generated; no clips showed as Offline.
Some Clips now Offline:Importer CC 2014
Now, after some months editing one project I found some of the MPEG clips have been flagged as "Offline: Importer" and will not relink. The error reported is "An error occurred decompressing video or audio".
The same clips play perfectly well in, for example, Windows Media Player.
I still have the earlier Premiere CC and the project file and the clips that CC 2014 importer rejects are still OK in the Premiere CC version of the project.
It seems that the importer in CC 2014 has a bug that causes it to reject MPEG clips with which earlier versions of Premiere had no problem.
It's not the sort of problem expected with a premium product.
After this experience, I will not be updating premiere mid-project ever again.
How can I get these clips into CC 2014? I can't go back to the version of the project in Premiere CC without losing hours of work/edits in Premiere CC 2014.
Any help appreciated. Thanks.

To answer my own question: I could find no answer to this myself and, with there being no replies in this forum, I have resorted to re-capturing the affected HDV tapes from scratch.
Luckily, I still had my HDV camera and the source tapes and had not already used any of the clips that became Offline in Premiere Pro CC 2014.
It seems clear that the MPEG importer in Premiere Pro CC 2014 rejects clips that Premiere Pro CC once accepted. It's a pretty horrible bug that ought to be fixed. Whether Adobe have a workaround or at least know about this issue and are working on it is unknown.
It also seems clear that the clip re-indexing process that occurs when upgrading a project (from CS5 to CC and also from CC to CC 2014) has a bug which causes memory consumption to grow continuously while it runs. I have 24GB RAM in my system and regardless of the amount RAM I allocated to Premiere Pro, it would eventually crash. Fortunately on restarting Premiere Pro and re-loading the project, re-indexing would resume where it left off, and, depending on the size of the project (number of clips to be indexed), after many repeated crashes and restarts re-indexing would eventually complete and the project would be OK after that.
It also seems clear that Adobe support isn't the greatest at recognising and responding when there are technical issues, publishing "known issues" (I could find no Adobe reference to either of these issues) or publishing workarounds. I logged the re-index issue as a bug and had zero response. Surely I am not the only one who has experienced these particular issues?
This is very poor support for what is supposed to be a premium product.
Lesson learned: I won't be upgrading Premiere again mid project after these experiences.

Adobe Premiere CS5.5 not installing [Exit Code: 7]

Hi. I've been having issues with Premiere for as long as I've had the CS5.5 master collection.
Every other application on the disk will install fine but Premiere will not at all.
I've uninstalled the entire collection twice (using the cleaner tool each time) and it will not install premiere.
I've also uninstalled my flash player but that makes no difference either.
Below is the error log I receive when I try to install it from the disk:
Exit Code: 7
-------------------------------------- Summary --------------------------------------
- 1 fatal error(s), 2 error(s), 2 warning(s)
WARNING: DW031: Payload:{61A3D10A-AA4D-4E4C-B9DB-6A08D318EA41} Photoshop Camera Raw (64 bit) 6.0.0.0 has been updated and has been selected for repair. The patch {32841ECE-EC28-42CD-A4DD-6CE832A7EA8D} Photoshop Camera Raw (64 bit)_6.3_AdobeCameraRaw6.0All-x64 6.3.0.0 will be uninstalled now.
WARNING: DW031: Payload:{37AB3C65-E02C-4DCF-B0E0-4C2E253D8FA3} Photoshop Camera Raw 6.0.0.0 has been updated and has been selected for repair. The patch {FD58D99B-9927-4226-8E00-959A4F76BD89} Photoshop Camera Raw_6.3_AdobeCameraRaw6.0All 6.3.0.0 will be uninstalled now.
ERROR: DW020: Found payload conflicts and errors:
ERROR: DW020: - Adobe InDesign CS5.5 Application Base Files depends on Adobe InDesign CS5.5 Icon Handler to be installed.
FATAL: DW020: Conflicts were found in the selected payloads. Halting installation.
Help?

Errors "Exit Code: 6," "Exit Code: 7"
Mylenium

Need help using Waves 64bit, 3rd party plug-ins with Premiere CS5

I'm trying to install and use a bundle of 64bit 3rd party audio plug-ins from Waves in Premiere.
I am on a Mac running OS 10.9.3.
I can't figure out how to get Premiere CS5 to recognize my 3rd party Waves 9.3 bundle.
The plug-ins are listed and fly by one by one on the loading splash screen while Premiere launches. I can't find them anywhere in Premiere once it launches. Aparently both the VST and AU units work. But how? Where/how do I load the plug ins so I can access them in the audio effects folder?
thanks in advance!
Alex

i think the audio plugin manager was something new added, but i dont remember when. as im looking thru older threads at cs5, they make it sound as if premiere will just load and use what it can. when an effect doesn't show up, its usually cause premiere determined it couldn't use it. if you have the 64-bit version of premiere and 64-bit audio plugins, they should work, unless premiere has some issue with them. i think waves uses vst3 and AU (audio units)? while vst2 should work in cs5, im not sure if vst3 or au are supported until cs7. so im at a loss, unless someone else knows better. if you have access to audition, you can try to load them in there to use.
Premiere Pro CC (7.0) | Premiere Pro New Features
Premiere Pro Mac - VST & Audio Unit Support - Something is wrong....
VST Plugins work in CS4, not in CS5
VST plug-ins not loaded at all Snow Leopard 10.6
Virtual Studio Technology - Adobe Premiere Pro

Slow down issue with Premiere CS4 on a Mac pro

I am having a similar slow down issue with Premiere CS4 on a Mac pro, but I don't have bloated prproj file size.
Here is what I am working with:
Mac Pro intel quad core 2.8ghz
OSX 10.6.7 Snow Leopard
6Gigs RAM
3TB storage between 4 drives, each drive with about 50% free space
I am editing a 10 minute HD video from avchd files. The edited video is very heavy in photoshop files with a variety of different fx including green screen. The system has slowed down to almost a standstill. Anytime I move the playcurser, or try to do any action, it displays the spinning top "thinking" icon and takes 15 seconds to several minutes to unfreeze. I am often forced to force quit and I have gotten unexpected quits several times. The program also freezes on startup frequently.
No other programs are running. When I export with media encoder, it took about 4 hours to complete. The last 4 or so photoshop images I added seemed to tip the program over the edge. It had been slowing down some, but those last few really dropped the processing speed. Before those additions, export took 30 min to 1hr.
I did delete the render files (did not check if the file size was bloated beforehand, oops) but it has not significantly affected my performance.

Do you need all of those extra pixels in the stills? Are you panning the full 4976?
Two things to consider are that if you using, say a 1920 x 1080 Sequence Frame Size, you can only see that at any time, regardless of how large the images are in pixels. If there are extra pixels, i.e. the Pan is not using all 4976 pxls., I would Scale to just what you need in PS, prior to Import.
If you are doing any Scale in PrPro, its Scaling algorithms are not as efficient, as those in PS. [Note: CS5 and 5.5 are a major improvement on that statement.]
With many large stills (the max for CS4 is 4096 x 4096, if there ARE extra pixels, pushing those around will use up resources, and quickly. As a test, some years back, I was working on a "photo wall," and was using 4000 x 4000 images. The workstation had no issues with slowness, until I got to the 5th large still. By the 8th, the Project was too slow to edit. I had to wait for everything. Luckily, I have AE, and it handles large stills much more efficiently, and much differently, than PrPro. I just moved to an AE Comp, and completed the Project, finishing up n PrPro, after I Exported from AE.
Just something to think about. With Scaling in PrPro, this is one time, where bigger is not necessarily better.
Good luck,
Hunt

Premiere CS5 (win7 x64) won't recognize my Mini-DV camcorder.

I have Premiere Pro CS5 installed on a Windows 7 64-bit system.
When I try to Capture, I keep getting the error message: "Can't Activate Recorder. Try Resetting Camera."
the whole set-up worked fine on my XP system with Premiere Pro 1.5.
Extra info:
The Mini-DV camcorder is a Panasonic NV-DS33 (but personally I think it has nothing to do with my camera because I have seen so many threads online regarding this issue and no-one has any decent answer!)
the firewire cable is fine because it works on my old XP computer.
in premiere, if I change the camera to an HDV, then suddenly I can CONTROL the camera, but I can't capture)
Windows 7 (x64 bit) recognizes the Camcorder in the Device Manager (and says it is working properly).
I have tried several other DV capturing softwares (Stoik, Scenalyzer, WinDv). I have even tried my old Premiere Pro 1.5 on my 64-bit system.. and NONE OF IT WILL CAPTURE MY CAMCORDER!
This is very frustrating. I need my new win7 (x64) Premiere CS5 to capture successfully. I have spent a LOT of money on this new system. What on earth is the problem?
(i saw one thread on a similar issue regarding a 32-bit installation of Win 7, and it is marked as ANSWERED! but in my opinion, (from the amount of forums on many other sites) this issue is definitely not fixed.
is there any update to Premiere CS5? or a workaround? or anything else I should know?
PS: it is not an option for me to keep using my old computer to Capture video and then transfer it to my new system. i am passing my old system on to another person.
many thanks
Marc
[email protected]

I agree that the "Legacy" FW driver solution should be a stickie, or FAQ. Since Win7-64 was released, it has caused no end to the grief. Maybe Jeff, or Todd will have a better solution to getting the word out.
It was Harm Millaard, who brought that to MY attention, and he's posted it to many, many threads. In nearly every case, it's solved the issue.
Good luck, and thanks for reporting Colin's success,
Hunt
PS - per your suggestion, I just published this "fix" in the Tips & Tricks sub-forum for PrElements.

Thumbnails not loading, crashing in Premiere CS5.5

I'm working with a ton of Apple XDCAM EX 1920x1080 files. It was shot over the course of five days, organized by day and then each day has folders for each card. I'm importing all the footage into Premiere CS5.5. Because there is so much footage I like to look at things in thumbnail view to quickly see what's what. But, starting in Day four and going into Day 5, the clips stop loading thumbnails. When I click on some of these "blank" clips, Premiere freezes up and crashes.
I have an older build of CS6 (my company has yet to actually BUY CS6) and the problem doesn't happen. All the clips have thumbnails. Any thoughts? Thanks in advance for your help.

I'm working on a 2010 Mac Pro, OSX 10.6.8, with Premiere 5.5.2. The issue is happening in the Project panel. Nothing has been added to the timeline (but the Sequence settings are Sony XDCAM HD 1080p, 23.976fps). The crash is indeed from a corrupt file, but it was only one. The rest play back fine in the Source monitor, no crashing, just no thumbnails.
For testing, I opened a new project in FCP and all the thumbnails show up and it even plays back the corrupt file. And, as I said, they show up in an older CS6 build of Premiere.
It's not THAT big of a deal, just a minor frustration. Wanted to see if its happened to anyone else. Thanks guys!

An issue in premiere CS5

Similar Messages

Maybe you are looking for