Premiere CS3 Problem

So I've made a video on my Polaroid i739 that I want to edit...But everytime I try, the video seems to be going way faster than the audio, and I can't slow it down because it repeats and stutters. It doesn't happen with any other device I use. How can I fix this problem?!

AVI could have anything inside
Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037?tstart=0
What is a CODEC... a Primer http://forums.adobe.com/thread/546811?tstart=0
What CODEC is INSIDE that AVI? http://forums.adobe.com/thread/440037?tstart=0

Similar Messages

Premiere CS3, problema con codecs

Hola, al iniciar Premiere Pro CS3 me dice que es necesario instalar codecs que no vienen con la versión trial. Le doy a aceptar y la instalación de codecs falla recordándome dicha necesidad de instalar codecs cada vez que abro premiere. Como puedo instalar dichos codecs o solucionar el problema???
gracias

Hola, al iniciar Premiere Pro CS3 me dice que es necesario instalar codecs que no vienen con la versión trial. Le doy a aceptar y la instalación de codecs falla recordándome dicha necesidad de instalar codecs cada vez que abro premiere. Como puedo instalar dichos codecs o solucionar el problema???
gracias

Hilights Clipping Problem with Premiere CS3 Media Encoder

I've just discovered a pretty serious problem with the way Premiere CS3 processes video to the Media Encoder.
Many of you are familiar with the term "super whites", the ability of modern cameras to capture and record levels above 100 IRE. With HDV and newer technology, recording to 109 IRE is quite common.
I was aware for some time that importing this footage into Premiere results in a hard truncation of whites above 100 IRE. However, I discovered last month that the Fast Color Corrector has a Output Levels adjustment that can rescale all the levels to fit down in the 0-100 IRE range. I verified this using the scopes in Premiere and by observing recovered details in my footage. I was even able to export frames to TIFF files and show the recovered highlights in the exported TIFFs. The difference is substantial and not subtle--it's the difference between a sky completely blown to white and one where you can see the sky is blue with clouds in it.
Last night, I discovered that the Unsharp Mask filter doesn't handle footage above 100 IRE, either. Even if I use Levels to set 0-235 RGB range, somehow, Unsharp Mask is processing the un-level-adjusted signal, regardless of stacking order of the filters.
I rendered two Blu-ray discs, one with Unsharp and the other without. To my astonishment, BOTH discs lacked any detail in the highlights--the whites were clipped at 100 IRE!
Now I turned attention to the Media Encoder. Pausing on a frame where I can see the difference between 100 IRE and 109 IRE and shades in between, I fire up the Media Encoder and note that even in ME's previews screens, the whites are already clipped. There is more highlight detail in the program monitor, whereas it's all gone in the Media Encoder's display.
It is obvious that highlight information, even scaled back to 0-235, is being treated as if it were 0-255 and clipped at 235 before passing to the encoder. This is a real disappointment, because there is another half f-stop of detail up there that I was trying to pull into the useable range of 100 IRE for the Blu-ray disc. Since it is very difficult to shoot footage and limit the peak whites in-camera to no more than 100 IRE, nearly all of us are losing valuable picture information.
Even if you can recover the highlights on the timeline through a Levels filter, it gets thrown away again on the way to the Media Encoder. Short of exporting a few hundred thousand frames as .TGA files and then loading those back in and rendering out to whatever motion CODEC, I am at a loss as to how to get Premiere to leave the whites intact.
I haven't seen this issue discussed in any detail here. Has anyone found a way around it, besides reshooting all your footage of one-time events to sub 100 IRE levels?

I'd rather the camera added that extra lattitide within the appropriate 0 to 100 IRE range.
That's a lot like saying you want 10 gallons of water in an 9-gallon jug.
As it is, it looks like such adjustments will need to be done on a clip by clip basis.
Or, you can do it the "Dan" way in AviSynth. I wrote a script function called SoftLimiter: It applies photoshop-style curves on the Y + U + V channels to bring the maximums within legal range… using a sort-of "soft-knee" approach to reducing extreme highlights and/or oversaturated areas.
It causes a tiny bit of posterization in the highlights, just like all 8-bit per channel color adjustments do… but it is hardly noticeable on a computer screen and even less on TVs.
SoftLimiter for AviSynth 2.5
Create a folder C:\SoftLimiterCurves\ and place the .amp curves files in that folder.
Place the other files in your AviSynth 2.5 / plugins folder.
The example below assumes DV avi files and requires a DV codec (such as Cecocida DV, MainConcept, Canopus) that can read / write in YUV formats.
Create a script like this:
AviSource("dv.avi", pixel_type="YUY2")
SoftLimiter()
Open the script in VirtualDub, use Video / Fast Recompress, Select Cedocida DV codec. File / Save as .avi
Before:
After:
And, Jim… you can place your dv2film() command at the end of this script if that's what you're trying to accomplish.

Premiere CS3 AVI Problems!! (plz help)

I'm using Adobe Premiere CS3 on my Computer and I'm trying to import this AVI footage-- Now the footage imports smoothly BUT when I put it on the timeline it shows grey/pixelated image. I can hear audio, but the video doesnt play properly. I've tried Downloading numerous codecs to fix it, but I'm not sure that's the issue...
I can preview the AVI outside of Premiere using any media player and I can edit the same footage in After Effects..
ALSO I have Adobe Premiere CS3 on my iMac and I can preview the SAME AVI file without having that pixelated problem like I do on my computer..
I'm not sure what's up with my PC's version of Adobe Premiere CS3 or what.. **This particular AVI is a Panasonic DV Codec (i think) which I have.**
This/These video(s) with that type of AVI just doesnt work with the timeline's preview whereas all the other video types work fine... (For example, I can take the footage into After Effects and export it as an AVI and THEN it plays with Premiere with slightly altered quality..)
If anyone has some idea, let me know--
Thanks,
Ari

DV Type 2 AVI
Also-- I'm messing around with it trying to figure out the issue.. I think that it could be after effects. I think the intro to the video was made with AE or motion and Premiere isnt recognizing the colors or something..
I made a little animation in After Effects and exported it and Premiere wouldnt play it-- It imported it, but it wouldnt play on the preview window..
I just put that animation into GSpot and it showed me that it's a DV Type 2 AVI ( AVI v1.0 )
So there must be something going on with the AVI v1.0 and my Premiere doesnt want to play it.. I still cant figure out the solution though.

Premiere CS3- HDV problems¡¡ Help¡¡¡

Hi
I have been working in a movie since 2009, in Premiere Pro CS3. Project settings: HDV 1080i. I have been having a lot of problems with the render process, new timelines, and saving the project. Sometimes when i make renders, save the project, close and open again, It doesnt save the render, so I have to start from the begginning. But that´s not the big problem. 2 weeks ago, I capture 4 hours of hd video and aded to the project. Since then, all my other sequences have dissapear. I only have the main sequence with the movie, and the rest of the sequences are still ther, but only as video clips, not as sequences. So, I´m just working in one sequence, one timeline. The size of this only sequence is about 7 hours in full hd. Since then, Premiere have been crashing every 5 or 6 minutes. Sometimes when I´m working and I want to save, it pops up a message and say that it cant save the project becouse of an unknown problem, so I try to save it in a different location, but it doesnt work, so simply, I cant save my project.
This is the machine Im working on:
PC Microsoft xp Profesional, Version 2002, AMD ATHLON 64x2 Dual Core Processor 5200+, 2.61GHz, 3 gigs RAM..
Hard disk memory: I have like 130 gygabites available. The size of the project with all the captured videos, autosaves etc is about 200 gygabites.
I really cant understand the problem, I have uninstall and install two times Adobe Premiere cs3 and every time I have the same problems. Somebody tell me that Premiere only works fine with less than 4 hours of video in the timeline so, is this my problem? Is it the computer? I really cant undersatand.
I really need some help.
Thanx

First, read Harm on drive setup http://forums.adobe.com/thread/662972?tstart=0
Then, work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section, the questions at the end of the troubleshooting link

Premiere CS3 install problems

I cannot install Adobe Premiere CS3 Pro.
The error I get is
Product: Adobe Update Manager CS3 -- Error 1935.An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.163",type="win32",publicKeyToken="1fc8b3b9a1e18e3b ",processorArchitecture="x86"'. Please refer to Help and Support for more information. HRESULT: 0x80070422. assembly interface: IAssemblyCacheItem, function: Commit, component: {98CB24AD-52FB-DB5F-A01F-C8B3B9A1E18E}
I have tried making a new account
disabling UAC
using fsutil
granting full permissions to winsxs
updating the .net framework
renaming the files that might be trying to be replaced
fixing any JavaScript problems
using the adobe cleanup tool on level 5
trying everything in safe mode
I work in IT and know what I am doing, I tried using the process explorer to monitor exactly what setup.exe did, but could not find any reason why it was failing. This is insane.
My os is vista32, cpu is intel core2.

If you have an Acer computer, there are known problems with some of the "helper" software pre-loaded by Acer
I don't have an Acer so don't have details... if you do, use the search and read all messages which contain Acer

Premiere CS3: How can you encode xml cue point data in the chapter section of a marker for FlashVid?

Hi there,
I'm a total newb to this forum, so hello adobe premiere community! I'm perplexed by Adobes documentation on Premiere (and I'm sure I'm not the first ) anyway on the live documents page below:
http://livedocs.adobe.com/en_US/PremierePro/3.0/help.html?content=WS9390BED7-9466-46ea-A0E A-3240F1AFC36C.html
it states that:
“The cue point data in the Chapter field of a sequence marker in Adobe Premiere Pro will be encoded as Flash XML. For the XML protocol required, see Flash Help.”
Which is great…except this information doesn’t exist seemingly in either the Premiere documentation or Flash either for that matter, but as I’m interested in working with the chapter/marker area in Premiere – should I really be told to go off and search the documentation for another application, probably not! What would have been useful would have been a code snippet saying you do it like this, but of course, that would make things too easy!
Basically, I understand that in After FX you can add Flash marker information specifically for interpretation when exporting to Flash Video (i.e. name, type and parameters etc) and it suggests that you can do the same above in Premiere CS3 using some kind of concatenated string in the chapter area…it just doesn’t tell you how anywhere seemingly – WHY ADOBE!
Currently when I export markers as cue points based on the advice in the page above, anything I put in the chapter section to force Premiere to create a cue point is converted to a string, which becomes the cue point ‘name’.
This cue point name is then automatically appended to the ‘time’ the marker was inserted at and is always encoded as type ‘navigation’, with no obvious means of adding ‘parameters’ into the equation.
So (finally) does anyone know if you can insert this information into the chapter area for correct interpretation by flash (i.e. thus allowing you to choose between either 'navigation' or 'event' types, and pass as many 'parameters' as you wish etc) or are you just limited to supplying a name, and it being automatically set to the navigation type with no parameters?
I’m sorry for this long essay but at least the issue is well defined for you to answer, honestly any help you can provide what so ever would really be most appreciated!
Best regards,
Kat
PS – I have utterly no knowledge of XML either just in case you were wondering – and my only interest in XML is getting this basic information encoded into the FLV file from Premiere Pro CS3! Please help, pretty please with daisy’s!!!

Hi dradeke,
Thanks for your reply, which is indeed useful as clearly Adobe have made this task easier and less obscure in CS4 by adding simple interface functionality, however I'm stuck with using CS3 for the moment. Its not majorly a problem as the video material in question can be exported uncompressed then setup with cue points using the Flash encoder as an alternative (i.e. or even After FX CS3 also) which both provide the same features as Premiere CS4 seemingly. It is just that it would be much easier to be able to drop in simple markers whilst working with Premiere CS3, as this is what we are going to be using primarily, I just wondered if anyone knew how to invoke this in CS3 - its possible you can't, the documentation is vague at best!
However I really appreciate your response and help, thanks

Large project in Premiere CS3 causes Windows XP64 to reboot

Ok...I have a rather sizeable project going in Premiere CS3. It contains a rather large number of animations created in Autodesk Maya (most between 10 seconds and 3 minutes long) and a large number of stills, as well as scrolling background (a .mov file I created using Photoshop and Premiere) and a soundtrack created by myself (in Cakewalk/Sonar). The total project is about 18 1/2 minutes in length....around 8 video tracks and 3 audio tracks at the moment. The main problem is that when I start working on it...either importing files and especially moving files around in the project or even just hitting the playback button, the system just reboots. I have seen the infamous Windows "blue screen of death" flash briefly once or twice, but it doesn't hang...just goes right to the system BIOS screen. The ONLY thing that seems to help is basically saving the project like every 30 seconds. Import a file, save, conform file to widescreen, save, bring file into project, save, move file around a bit, save, add crossfade, save....you get the idea.
Now before I go too much futher here, I suspect the problem isn't actually with Adobe/Premiere as I had this happen a few times while I was creating the sound track in Sonar 4 as well. The sound track is basically a pseudo-orchastral piece and is equally around 18 1/2 minutes long....currently with around 42 tracks of audio and 5 midi tracks. The audio has been sampled down to a standard stereo wav file for the import into Premiere. And yes, as the audio portion of this project got bigger and bigger, it caused a few reboots as well (not to mention drop-outs, studders and all the other fun stuff associated with audio production). With that, I was able to "compact" the Sonar file (basically a Sonar project defrag) and the reboot problem seems to have went away on that end.
The system itself SHOULD be able to handle this project...not top of the line, but pretty beefy. 2nd generation Intel i5 quad core, 16 gigs of Kingston DR-1600 RAM, Tascam US-428 for the audio and a good 2+ terabytes across 5 harddrives (3 internal 3 gig-per-second SATA's, 2 USB). Also has a 4 gig HIS vid card with ATI chipset (still can't afford a FirePro yet). While Premiere is installed on the (comparatively dinky) 160 gig C drive, I'm using the 500 gig E drive internal and a 500 gig USB drive as my work drives. Most of the Maya animations are on the internal E drive but the rest...the stills and Premiere files and such...are on the USB drive. I.e., the system itself should have plenty of rendering power for this. Also I have replaced the C drive with a nearly identical twin. After a recent crash, I finally broke down and got a backup C drive...in other words, I'm sure the drive(s) are a-ok...even put a brand new 500 watt power supply in just in case.
I have already re-installed XP64...a couple of times in fact, as just before I started this project one of those god-foresaken MS "critical updates" crashed the crap out of my computer. Then on the first reinstall, something hosed in .NET framework during the "night of a thousand updates" so I had to scrap it and start the reinstall all over again. Likewise, I reinstalled Premiere CS3 (along with everything else including Maya) once I finally had the computer running again.
A quick note here: I did create my own custom 1080 Hi Def widescreen settings for Premiere since CS3 didn't appear to have any such thing. For short projects they seem to work just fine...although admitedly, the render time is a serious b*tch. Likewise, all the Maya animations have been rendered out at 1080 widescreen, production quality (yea...the render time there was a killer too).
Another quick note: While I'm trying to use Premiere exclusively while I'm working, on occasion I have had to open either Photoshop or Maya to deal with a couple of stills...and when I open something else, I get a "windows virtual memory to low" (16 gigs of RAM and the virtual memory is too low??). Otherwise, except for Avira (virus scanner) I don't really have anything else running in memory...no screen savers, no desktop pictures, no Instant Messanger crap, etc.. Never cared for bells and whistles and such, so the system is pretty clean in that regard (and I do keep up on my degrags as well).
Finally, while I -am- grateful for any helpful suggestions regarding this, please do NOT simply tell me to upgrade something (Premiere, Windows, etc) as point blank; it ain't gonna happen. Aside from the fact that Adobe seems to have made Premiere CS4 and up much more difficult to use (I have -many- niggles about the newer interfaces there...using CS5.5 at the college and it's REALLY annoying) and aside from my wife being a MS programmer/developer and having to listen to her complain about Windows 7 and 8, we're in the process of buying a new house, so any and all "disposable income" is nill...and will be for quite some time. No money...zero...nadda...i.e. no upgrades. Further, while granted this is certainly the biggest project I've done to date, I've ran this setup/configuration for at least the past 3 years now without a hitch...this all seems to have started with that last MS critical update (at the risk of sounding paranoid, I'm really starting to think they slid a nasty in that last one to FORCE people to upgrade since they're discontinuing XP64 support soon).
Alrighty...I know that's a lot but I wanted to provide as many details as I could here in hopes that someone can help me get a handle on this reboot issue. Getting to be REALLY annoying having to save every 30 seconds or so. I have searched the help files, but got tired of randomly sorting thru all the blather and not finding anything helpful.
I'm grateful for any help here...thanks!
Jim

Well, I'm about 98% sure it isn't a hardware problem. I had already pulled the RAM and tried some backup RAM I have sitting in the box (8 gigs of Corsair), went thru the harddrives weeks ago with Chkdsk and everything was a-ok there (a couple of bad clusters on the old C drive, but that has since been replaced and is on the shelf as a backup), motherboard seems to be fine, re-seated all cards and cables, etc.. Again I even slapped a new 500 watt PS in just in case (the old one was a 400 watt and with all the crap I have on this system, thought it might have been a voltage drop off issue...nadda). I did have a bit of a heat problem a while back...one of the case cooling fans was going bad and the CPU was getting just hot enough to trip the system (about 5 degrees over). That said, that also shows up in the BIOS monitor as well and was easy enough to track down. Either way, the bad cooling fan has been replaced and I even added a "squirrel cage" style fan as well...system is running nice and cool now.
BTW...I used to be A+ certified on both PC's and Macs when I was a hardware tech (not to mention HP, IBM and Lexmark certified, Cat 5 installer, etc), so I like to think I know my hardware fairly well. Not just a weekend warrior on that front...used to do it for a living.
I had also already tried manually resizing the paging file as well...tried different sizes, tried spreading it out across the drives, etc.. Didn't really make a difference either way and again the only time the virtual memory low comes up is if I try to open Photoshop or Maya while this big project is open in Premiere. That said, Photoshop and Maya both tend to be pigs when it comes to memory/RAM (Photoshop especially). Doesn't seem to happen with Illustrator or any other program....just PS and Maya if this project is open in Premiere.
One other oddity I have noticed recently is actually with Maya. Before all of this started...in other words, before that last MS critical update and 3 days of reinstalling software...I used to be able to do a background render with Maya and still be able to keep working on stuff. I'd fire off batch render and then I could move on to other things...editing images in Photoshop (CS 5 there if it matters), surfing the web and even doing some light stuff in Premiere. Since this problem has been occuring however, I have noticed that the Maya batch renders are REALLY slowing down the system big time. Difficult to even check my email while a batch is running. Likewise, I have noticed that since I upgraded the Maya from 2011 to 2013, Maya has a nasty tendency to freeze during a batch render. If I have a long batch render, I'll set it up to run over night...when I get up the next moring, the render itself will still be running (you can see Mayabatch.exe still going in processes under Task Manager) but Maya is totally frozen up. Now I did that update at the same time as the rest of this mess happened so I don't know if these problems are due to the Maya upgrade or the (apparent) Windows problem...I'm inclined to believe the latter.
BTW...after having a project file get corrupted yesterday during one of these shut downs, I've been double saving the files (so as to have a backup) and that too seems to have made things a bit better. Hasn't actually shut down on me when I've been doing this. That said, it's also a serious pain in the butt having to save that way too.
With that, looking thru the rest of Hunt's article there, I did kill indexing services...at least on the work drives. it's about the only thing there that I haven't tried, so we'll see what happens this afternoon. I seriously doubt that would be the problem though as usually that would give an error or a lockup and not an instant shut down, but we'll see.

Error compiling movie: out of memory !!! Premiere CS3

Hey every1 --- desperate need of some guidance here. I've been all over the internet and these boards --- have seen this come up with a lot of people but no real solid answers that I'd seen or that have helped.
First off, my comp is an imac 3.06 Ghz Core 2 Duo, 4GB memory. (just bought the computer last year)
I'm shooting with a canon 7d in HD (1920 x 1080p) and I'm editing using Premiere CS3. I've noticed that editing has become very difficult since I started using HD; playback is very choppy and the 'quality settings' in the preview monitor are a joke and do absolutely nothing whether it's on draft or automatic.
Anyway, despite the choppiness and slow editing, I was able to get a 3 min clip completed. These are my export settings:
Export > Movie
H.264
960 x 540
23.976 fps
Square pixels,
100% quality,
recompress: unchecked.
Once exported (I was able to export smaller timelines previously--- say, 50 secs of footage or so) the files look AMAZING and from there I use them for online video via vimeo -- stuff looks really awesome.
Anyway, recently I'm getting: 'Error compiling movie. Out of Memory. Change optimization preferences to memory', etc. etc. Well, I did as it asked and that did absolutely nothing.
So, I decided to open up my activity monitor and watch what's going on with my memory while premiere is exporting. I also closed ALL unused applications. System runs at about 2.16gb free memory before I start exporting. Memory seems stable during export UNTIL around the 50% exporting mark, and then its starts climbing like crazy and my memory just gets eaten up --- finally resulting in a crash at about 70% render.
I really don't know what else to do. Does my computer not have the power to export 3 min of HD footage??? This seems surprising to me ... I don't know what else to try.
Thanks for any help !!!
-Mark

Hi Mark,
Hope you are having a wonderful day.
Sorry to hear that you are having such a hard time. Although I did not specifically get the out of memory error, I can only be convinced that that is the problem.
Although I am not a computer whiz, I have learned my share of things. I have been troubleshooting a video all this week (really, a couple of months), but I had to put it aside and come back to it.
I tend to be talkative; so I will get back on topic or at least try to stay on topic, so bare with me. Smile....
Here is what I have learned and maybe it will help you with yours if you have not found a solution already.
Based on your hard drive specs and ram, I was thinking the same thing e.g. hard to believe that you are not able to render 3 minutes of video in HD. I primarily work in HD/1080p.
The place where we are similar is that I eventually could get the video to render by reducing the workspace that is rendered piece by piece until I was able to render the entire file. When I tried to encode the video, I kept getting error compiling messages. I tried different codecs, deleting xmpses, not rendering xmpses, etc. I could not figure out the keyframe trick so I just put in a black video from after effects. By the way, all of my videos intro the same and no problems with the other videos fading from black to a still photo.
Here is the problem from what I could gather.
Simply, out of memory. I was rendering and trying to encode a 45 minute video with after effects compositions and the dynamic linking kept timing out once the file reached a certain size. There were no other true fancy effects. I do alot on the green screen and just use after effects to make a white background. Smaller videos, rendering has been slow, but doable. This massive video would never compile. I won't bore you with my system specs, but know that similar to your situation, the system in theory should have been adequate.
Work around...
I ended up exporting the video as 3 separate 15 minute video clips. I could not get them to encode as .wmv files so I encoded them as .mp4 files. By the way, I still encoded in HD.
Here is the kool stuff.
After what seems like forever, I found a converter that could convert .mp4 to .wmv and rejoin the files to play as one large file with the same quality as my source file and no audio synching issues. By the way, I do not work for this company. I just found this encoder at 4 o'clock this morning after trying all of these other converters that were straight garbage or were free to try and not really free if you wanted quality. By the way, the conversion tool is not only user friendly, but free which is awesome.
The name of the software is Media Cope. Just visit www.mediacope.com.... Be sure to send the owner an e-mail to thank him and let him know that Mark sent you. I just sent him an e-mail earlier to let him know that I was going to post on Adobe what a wonderful software he created. I just needed something free, quick, easy, and user-friendly.
Whoops... got off topic....
I'll do a summary at the end for my recommendation to you.
Here are some other tidbits that I learned as well that may save you some time.
When editing this is what I do now...
1) I use CCleaner from www.piriform.com to quickly clean my system especially temporary files before I start editing and if I am switching from project to project.
2) In all of my troubleshooting this week, I found a kool little software call Smart Close. (Just google to find this one.) It closes all of your non-critical background files in order to maximize system resources. (When I am done editing, I just reboot and all of my background programs start up again. You do not have to do it that way, that's just how I do it. The nice thing is that it is a wizard interface; so you do not have to try to figure out if a process in the background is critical or non-critical.)
3) Depending on my mood and if I did not forget, smile.... I change the priority to high for the adobe products in the task manager.
More things that I learned...
1) We are not able to change the temp file for how Adobe encodes. My logic was if I could change the encoding to a hard drive that was simply empty so Adobe can render there, then I would be good. Wrong.... Adobe does not allow you to change the temp location. (Note: This is what I discovered in the different forums; so encoding to an external hard drive is not the best move. Read more to se why.)
2) It is best to have your scratch disks as your internal disk. If you have multiple internal disks, then you shoud check some other forums for the best way to set up your scratch disks. When I was just starting out, I bought an external hard drive enclosure with the thought that I would work primarily off of those external drives with the option of doing some RAID work. Bad idea... Even the simplest of tasks took forever. It was best to work off of the internal drive. By the way, I still use the enclosure hard drives for backups in order to allow me to free up some space on the primary hard drive. When rendering, it is truely a use of the RAM and the hard drive space in the editing process.
I'll leave you with this...
I take back what I said earlier, you do need a new computer with more RAM. If you can get 16 GB, great. The primary reason is that if you are editing in Premiere and if you do anything with dynamic linking into your after effects, it will cause your ram to climb as the file gets larger. Of course, be sure to get the largest hard drive possible as an internal drive, the maximum on processor speed, 64 bit operating system, etc.
I know you are like by now, Mark, what is the point of all of your gibberish... Really, it was to share with you and others on some really kool work arounds.
My recommendation for you are as follows.
1) You have already proven that you can render and encode 50 second clips and you are very happy with those clips, so create separate smaller clips for this particular project.
2) Once you have the final clips outputted, then use Media Cope to rejoin the files as one large file and you are done.
(Note: The one thing that I did notice is that there is a small break right between where the files are merged. The nice thing is that as a video editor/film maker, you will be the only person likely to notice it because you know where the breaks are. The other nice thing is that the untrained eye will not notice it and if you had to submit your work to a television station especially on DVD, the video system should recognize the file as one large file and play all the way through. Note: For the last sentence, I said 'should play all the way through' as I have not had a chance to check this one yet as I just finished this project today and still have to turn in all of my videos. I still have some more videos to merge.)
By the way, the only specs that I will share are that I work on a PC and it has 8 GB of ram.
The summary of the summary is that sometimes an error compiling message could simply be that your system does not have resources to render and the encode that large of a file. At least that is what I learned this week or at least my specific situation. The confirmation is that I just finished shooting a documentary which was one hour and some change and was able to render and encode to .wmv with no problems. Of course, I was not using after effects for this particular project.
In either case, hope all the information helps you with your project.
Have a wonderful day and happy holidays everyone.
Mark

No audio in Premiere CS3

Hi
I have just installed CS3 onto a brand new machine, and no audio of any type is playing from with Premiere CS3 - I have tried all the usual video formats, MP3, WMA etc which all worked on my last computer. (audio in other windows programs works fine). I do get a message when I start up CS 3 which says "The currently installed soundcard driver does not support DirectSound Input, Recording audio is not possible" This obviously doesn't mention anything about playing back audio.....
Anybody have any ideas?

John, Thanks for your reply. In fact, the audio is built in to the motherboard on my Dell. I'm a little confused by the error message though... It says that, with my present sound card, recording will not be possible. Hmmm... Does that mean that I can not record narration by plugging a mic into the sound card, but that audio from my source tape(s) will still be recorded? I'm just getting started with CS3 after I have experienced a 2 month nightmare of crashes and a multitude of problems with Premier Elements 4. (The Adobe techs finally admitted to me that Premier Elements 4 really isn't cut out for HD processing/editing). Anyway, back to the sound issue.. It appears as though the sound from my source tape is being recorded as is sound from a CD or a file. If it's just the mic input that won't work on my sound card, it's no big deal as I do no narration. If you know the answer to that, I'd appreciate hearing it. Thanks so much for your input! Kent

How to get HD presets in Premiere CS3?

Hi,
I use Adobe Premiere CS3 under W7 and I would like to import, process and export movie clips in HD resolution (1920 X 1080).
The files to import are video files having a format .wmv or .mp4 with the above mentioned resolution and located on the hard disk.
When opening a new project I have the presets folders for DV-24P, DV-PAL, DV-NTSC and folder HDV which is unfortunately empty.
Looking In the Adobe Premiere Pro CS3 Program File I found a folder called Settings which contains a folder HDV with all the HD presets such as HDV 1080i30.prpreset or HDV 1080p25.prpreset.
How can I "move" these presets into the empty presets folder HDV in the program in order to access them?
Many thanks in advance for any help you can provide.
N.B. So far I can import the 1929 x 1080 clips , but then they are processed and exported as 720 x 576 files hence loosing the original HD resolution.

Do you have a USB hard drive handy?
If yes, you need to make a full boot drive backup to that USB hard drive before changing anything
Hardware crashes or virus infections or simple software problems happen, so you should buy AND USE software to make a full backup of your hard drive to an external USB hard drive... plus, making step-by-step backups during a new install or major program addition makes it easy to go back a step if something doesn't work
This backup and then restore is, of course, only to the same computer with a new drive (or the same drive as long as you don't mind writing over everything) since doing a restore to a new computer won't work due to Windows and many programs having activation information that is keyed to your hardware (which is why Windows will force you to RE-Activate if you change very much hardware)
The product I use is at http://www.terabyteunlimited.com/image-for-linux.htm
Image runs off of a bootable CD via Linux (the Zip you download includes a program to make the bootable CD) and it reads EVERYTHING on the drive, even the hidden registration information, so everything is restored when needed... and you may restore the image to a brand new drive in case of a crash, and not have to re-install anything
Please note that I own no part of Image, and I don't get a referral fee (that is just a plain web link) but I use the program and it has saved me a LOT of trouble when I had a hard drive die... and I was able to restore everything and not have to re-install or re-activate a single program, from Windows on up

My Premiere CS3 crashes when I am exporting anything.

Premiere CS3 crashes on my HD project Most of the video i am working with is from the new 5D The files are as I recorded them on the camera there have been no conversion done to them. when ever I try to export anything out of premiere it crashes and windows Vista 64 crashes with it showing a blue screen and restarting the computer. I don't know whats the problem. I think it mite be my hard drives or something on the hardware end.
I am running
E8500 processor with 4 gb of ram DDR3 1600 Asus P5Q3 mob and Ati 4890 graphic card also I have 2 big hardrives and two 500gb drives on Raid.

BSOD can also point to heat, bad RAM, MoBo issue or power supply not adequate, along with Jeff's suggestions.
This ARTICLE might point you in the right direction.
I cannot recall if that article mentions Speedfan, but if it IS a heat issue, that will help you sort it out.
Good luck,
Hunt

CRAM Codec & Premiere CS3

I'm doing some simple editing in Premiere CS3. My pre-recorded videos play fine in Windows Media Player, but export jerky and vibrating after editing them.
After doing some research I found out that my pre-recorded videos us the CRAM (Microsoft Video 1) codec. The program G-spot tells me that I do not have this codec installed.
If I install this codec will my videos export properly?, or should I be converting them before editing (is this possible?). My worry is that if installing the codec solves the issue, after burning to dvd will others who play the dvd experience issues?
I'm pretty new to this so very basic instructions are best lol.
Thanks guys.

Welcome to the forum.
Have to admit that I have not heard of the CRAM CODEC.
Now, the installation of some CODEC's will allow PrPro to Import, edit and Export - though not all. The first two operations in that list are usually the "weak sisters." Installation might help you with Export.
Now, before you do that, is a DVD-Video your ultimate goal? If so, do NOT Export in any CODEC, but either DV-AVI Type II w/ 48KHz 16-bit PCM/WAV Audio (or DD AC3 for DD 5.1 SS), or fully DVD-compliant MPEG-2.
One can Export in either of these (I choose DV-AVI elemental stream, and AC3 DD 5.1 SS elemental stream), and then Import the Video into Encore as a Timeline and the Audio as an Asset. Drag the Audio to the appropriate Timeline and author to DVD-Video in Encore.
If you know what you're doing, you can use bit-budgeting to calculate your MPEG-2 compression, Export that, and then Import it into Encore. Make sure that all settings are 100% DVD-compliant.
Now, back to your quality problem:
The source files are using CRAM, but you do not have it. Installing it might improve the quality, or it might not. What are the settings that you have used on Export, where you got the bad results?
Good luck,
Hunt

Premiere CS3 and 24p exporting

Hello,
I've been working on this problem for a long time.
I have some clips shot with a Canon XL2 in 24p mode with 2:3:3:2 pulldown. I import in Premiere CS3 in a 24p project, go in "Interpreter footage" and set "Remove 24p pulldown", and in the timeline the clips are good, 24p without interlaced frames.
Then I go exporting: I want export in 24p (23,97) DV format.
1) If I choose "Microsoft DV AVI" with "DV (24p Advanced)", the clips I get are in 29,97 with still the flagged frame that should have been removed. So I have the same output format that I get setting DV NTSC with his 29,97 framerate.
2) If I choose "Microsoft AVI" and then I go with an alternative DV codec, such as the Panasonic's one (but I've tried many and I've got the same results, so I don't think it's their fault), I get a 23,97 clip, but the frame that has been removed is not the flagged and interlaced one, is one of the progressive. Watching the clip frame to frame I see that I have 24 fps: 3 progressive, 1 interlaced, 3 progressive, 1 interlaced, and so on.
Let me know. Sorry for my bad english but I'm italian.
Thank you

My own testing shows that Premiere doesn't create 24p friendly DV files. I've had much better success creating 24p MPEG2-DVD files.

Importar mp3 en Adobe Premiere CS3

Hola!.
Estoy probando el premiere CS3, pero cuando le doy a importarv, en los tipos de archivo no me deja escoger ficheros .mp3 (deja muchos otros, avi, jpg, etc...) y si pongo en tipo de archivo *.* y elijo un archivo de audio en mp3, me dice que el "formato de archivo no admitido". Esto no me ocurre con el premiere 1.5 por ejemplo.
Podria alguien decirme como puedo importar mp3 con premiere cs3 ???
estoy desesperado ya :( gracias.

hola
tengo un problema con premiere cs3, es que la linea de tiempo no esta activa, trato de arrastrar un clip o musica o lo que sea y no lo permmite, en la pestaña de la ventana de linea de tiempo solo dice: Linea de tiempo(sin secuencias)
alguien puede ayudarme?
gracias

Premiere CS3 Problem

Similar Messages

Maybe you are looking for