premiere pro 1.5 giving me a hard time
- Kariudo
- Twilight prince
- Joined: Fri Jul 15, 2005 11:08 pm
- Status: 1924 bots banned and counting!
- Location: Los taquitos unidos
- Contact:
premiere pro 1.5 giving me a hard time
whenever I try to get some editing done (recently) premiere seems to always go unresponsive.
It seems to only happen when I try to render a preview and scrub the timeline.
There is no set point on the timeline where this starts to happen
I threw together a 5 second segment in after effects 6.5 pro (which despite using more ram and cpu resources, runs prefectly fine) encoded with lagarith and threw it onto my timeline in premiere. All the other clips are now encoded with picvideo mjpeg V3 (they were encoded with lagarith first, then huffy when lagarith was making premiere pro hang)
Project settings
editing mode: video for windows
codec: huffyuv2.1.1 (optimize stills is unchecked.)
timebase: 24fps progressive (no fields)
frame size: 720x480 (PAR is .9 NTSC)
preferences
audio i/o: SB audigy2 ASIO [feco]
ASIO latency medium (50ms)
huffyuv settings
yuy2: predict median
rgb: predict gradient
always suggest rgb for output is checked
enable rgba compression, swap fields on decompress, enable console window logging are unchecked
Video properties: 24fps progressive, 720x480, picvideo mjpeg, .avi
Computer specs: Athlon 64 3200+, 1GB ddr333 (2x512 sodimm), Creative soundblaster Audigy2 ZS pcmcia
I've tried deleting all the preview files and re-rendering and switching codecs that my footage is compressed with. I have a few cross-disolves on the timeline, but most of the time I only have 1 cross-disovle occuring (lasting 4 frames each).
The part that appears to be giving me the most trouble has 2 cross-disolves happening at the same time, as well as a change of the opacity of the top video layer (it's set at 50%, no changes...it's either 50% or 100%)
A while ago (maybe about a year or so ago) I got the update for pro 1.5 from the adobe site
I also ran memtest86 for 2 hours (1000% coverage) with no errors
Are there any red flags in these settings/properties?
is there anything I can do to make premiere pro run smoother?
Am I just out of luck and should think again about running a video editing program on my laptop?
It seems to only happen when I try to render a preview and scrub the timeline.
There is no set point on the timeline where this starts to happen
I threw together a 5 second segment in after effects 6.5 pro (which despite using more ram and cpu resources, runs prefectly fine) encoded with lagarith and threw it onto my timeline in premiere. All the other clips are now encoded with picvideo mjpeg V3 (they were encoded with lagarith first, then huffy when lagarith was making premiere pro hang)
Project settings
editing mode: video for windows
codec: huffyuv2.1.1 (optimize stills is unchecked.)
timebase: 24fps progressive (no fields)
frame size: 720x480 (PAR is .9 NTSC)
preferences
audio i/o: SB audigy2 ASIO [feco]
ASIO latency medium (50ms)
huffyuv settings
yuy2: predict median
rgb: predict gradient
always suggest rgb for output is checked
enable rgba compression, swap fields on decompress, enable console window logging are unchecked
Video properties: 24fps progressive, 720x480, picvideo mjpeg, .avi
Computer specs: Athlon 64 3200+, 1GB ddr333 (2x512 sodimm), Creative soundblaster Audigy2 ZS pcmcia
I've tried deleting all the preview files and re-rendering and switching codecs that my footage is compressed with. I have a few cross-disolves on the timeline, but most of the time I only have 1 cross-disovle occuring (lasting 4 frames each).
The part that appears to be giving me the most trouble has 2 cross-disolves happening at the same time, as well as a change of the opacity of the top video layer (it's set at 50%, no changes...it's either 50% or 100%)
A while ago (maybe about a year or so ago) I got the update for pro 1.5 from the adobe site
I also ran memtest86 for 2 hours (1000% coverage) with no errors
Are there any red flags in these settings/properties?
is there anything I can do to make premiere pro run smoother?
Am I just out of luck and should think again about running a video editing program on my laptop?
- Krisqo
- Cooking Oil
- Joined: Mon Jul 07, 2003 1:22 pm
- Status: W.O.A (Waiting on Aion)
- Location: Moderating the Adobe Forums
I had something similar happen when I was simply trying to make a traveling matte. The clips only lasted 5 seconds and one was a simple PSD file. No matter what I did, it would always die on me. Granted this is Pro 1.0 but 1.5 shouldn't be TOO much different. Maybe try using Uncompressed clips since mine were also Huffy.
- Zarxrax
- Joined: Sun Apr 01, 2001 6:37 pm
- Contact:
- Kariudo
- Twilight prince
- Joined: Fri Jul 15, 2005 11:08 pm
- Status: 1924 bots banned and counting!
- Location: Los taquitos unidos
- Contact:
at least I'm not the only one who's had this happen :/
seemingly against [my] logical thought...Krisqo's suggestion seems to work.
Granted playback is kinda jumpy...but it isn't hanging on me (yet)
I'm really glad that I have about 200GB open between my 2 externals
It would still be nice to hear other input though
seemingly against [my] logical thought...Krisqo's suggestion seems to work.
Granted playback is kinda jumpy...but it isn't hanging on me (yet)
I'm really glad that I have about 200GB open between my 2 externals
It would still be nice to hear other input though
- Scintilla
- (for EXTREME)
- Joined: Mon Mar 31, 2003 8:47 pm
- Status: Quo
- Location: New Jersey
- Contact:
- Purge
- Joined: Mon Oct 10, 2005 9:18 am
- Location: Under Aus
- AMV_4000
- Joined: Wed Apr 10, 2002 6:29 am
- Location: USA
- Contact:
- Kariudo
- Twilight prince
- Joined: Fri Jul 15, 2005 11:08 pm
- Status: 1924 bots banned and counting!
- Location: Los taquitos unidos
- Contact:
alright, before I forget about this I got lucky on the adobe forums.
the styles file (ingeniously located in the styles folder ) and the layout file (again, located in the layout folder) may have become corrupt.
deleting those files has seemed to solve this problem (those files are remade as needed)
the styles file (ingeniously located in the styles folder ) and the layout file (again, located in the layout folder) may have become corrupt.
deleting those files has seemed to solve this problem (those files are remade as needed)