[Adam Spencer]

Thanks for that, I was looking for more of a plugin solution… AE is a bit over the top.

[Adam Spencer]

Thanks for the replies. To answer some questions:

I’d prefer 2.5″ simply because it’s smaller. I went mini-ITX years ago, although kept my 3.5″. I’m trying to avoid bulky legacy components in a new build.

I only do editing for a hobby, so I won’t be going down the RAID route. The disk will be connected via SATA, definitely not working from USB.

I’ve been looking at two reviews from the same site:
WD Black 3.5″ 7200rpm
HGST TravelStar 2.5″ 7200rpm

The WD 3.5″ betters the 2.5″ in pretty much every test. Some results are marginal, but others look like they’d have an impact.

I guess I’m trying to gauge what non-RAID setups editors are using these days. Whenever I look into an SSD for editing, there’s always warnings about the drive wearing out fast due to all the writes needed for video editing. Meaning one would have to replace the drive a lot sooner than a regular hard disk. Others comment that they went to SSD and didn’t really notice a difference during editing.

[Adam Spencer]

“I tried looking in the project folder (which is where scratch drive is poiniting) but no luck. Only the version from an hour ago.”

Old thread, but this is my problem exactly. Premiere Pro CC 2014 just crashed, and I lost half an hour of work. I checked my autosaves, and there are 20 autosave files, yet the last one has not been saved for 90 minutes. The auto save is set to the default of every 15 minutes.

So why didn’t it save? This has happened to me a few times in the past actually. A sudden crash, and I remember even seeing PP auto-save my project just before the crash….yet when I load the autosave file, it’s from like an hour earlier!

[Adam Spencer]

I am STILL having this problem. It still happens in CS6. Really aggravates me because I have to manually fade every single clip that I want to dissolve. It doesn’t matter whether I use hardware or software rendering, I get the same result. In fact, 50% of the time hardware rendering crashes on me so I usually have to resort to software.
I use 25fps most of the time, I wonder if there’s a difference with 29.97.

[Adam Spencer]

I tried that, but all I got was one long clip containing my video. I could play it back on the timeline, but all the individual clips and edits were missing. It was just one long clip.

[Adam Spencer]

I can clearly see the image stop moving before it fades out. This means the keyframe did not snap to the absolute end of the clip like it was supposed to. This should not happen, and did not happen in CS5.5.

[Adam Spencer]

I don’t think it has anything to do with codecs. I would’ve thought the error message would say something about codecs.

Anyway, half of the projects I tried to open are slideshows – there’s no video in them.

[Adam Spencer]

I get this same problem using Both BCC 7 and 8 in Premiere Pro CS5.5.

I noticed that in the release notes for BCC 8.0 Vegas it says this:

“BCC Stars will occasionally exhibit horizontal bands of artifacts in the star field and galaxy controls.”
https://www.borisfx.com/borisfxwiki/index.php/Boris_Continuum_Complete_8.0.0_for_Sony_Vegas_Release_Notes

I didn’t see anything noted for Premiere Pro, but this is the exact problem. There is no suggestion for a workaround either.

With Premiere Pro I have had better luck turning off hardware acceleration and doing the render that way. Though it takes HOURS just to render an 8min video (when it would normally render in 5-10min). My render settings are nothing extreme – 1080p H264 MP4 at 10Mbps.

I came to this forum hoping someone had an answer for this problem, but it seems even with the release of BCC 8, this bug has still not been fixed.

In my own experiments, it seems this bug has to do with hardware acceleration. I am currently using a nVidia 560Ti 1GB.

[Adam Spencer]

I also have this problem. It’s been happening ever since either CS5.5 or using hardware acceleration (I upgraded both around the same time).

Cross Dissolve is not as smooth as it used to be, and Film Dissolve doesn’t make much of a difference. As a previous post mentioned, It’s like there’s a couple frames missing and the clip won’t fade to 0% opacity. The image disappears before it’s fully faded.

For some clips, I have manually had to fade the clip’s opacity in order to generate a smooth fade.

[Adam Spencer]

Yes, I’ve seen those free transitions and they’re great. A big thanks to the person that did those.

Yes Premiere Pro transitions are a real sore point. I can buy a $30 slideshow program and get a ton of nice slick transitions that I could only dream of in Premiere.