"Use Preview Files" works in CS5.5 but is "Useless" in CS6

Report · Jul 23, 2012

I'm a heavy user of the "Use Previews Files" option when exporting files. This has worked great with Premiere CS5.5 but using the same method in CS6 no longer works and reverts back to rerendering the original files in the timeline and rerendering all the effects on them which is very time consuming since the original files are HD and are being downscaled in a DV widescreen timeline.

Anyone figure out how to get Premiere CS6 to correctly find the preview files when exporting using the "Use Preview Files" option?

In the meantime, I had to load all the preview files I had rendered back into a new timeline and reassemble them in the correct order. Once I did that, I exported this 1 hour 38 minute timeline to an MPEG-2 file which only took 19 minutes instead of the 7 hours it would have taken even with the "Use Preview Files" on and with a fully rendered timeline.

Again, it works great in CS5.5 so something changed in CS6 to make the "Use Preview Files" useless now.

Randy

Report · Jul 03, 2013

Nope, not gonna work since I prefer to render and check all my video at full res and playback quality as I edit from the timeline on video monitors (SD and HD) before exporting. I do a lot of short renders and really don't notice the time it takes (I multitask with other work during the quick 3-5 minute renders throughout a project) while in the editing process but it ends up being a huge time saver on the export. Other advantage is that if I make one change in the timeline I don't have to wait 4+ hours (for this last 2+ hour project I did) for it to export the timeline since it would have to process all the effects again from AVCHD files. There is a huge advantage to using preview files, I would go out of business with your method.

Report · Jul 03, 2013

Well, one thing I can recommend is instead of rendering, just export and check that on the calibrated monitor. (It's what I do.)

Report · Jul 03, 2013

If you are on a PC I would use DNxHD for a quicktime file. I know DV is

quick to render, but its extremely low quality and I wouldn't trust it

for using previews in my final renders. DNxHD has smart render

capability and comes with CC (if you move the project to CC). It would

at very least be worth the test.

I'm with you, i like to use previews and render when i'm waiting on

feedback or have downtime, also so that if there is a change the

reexport will be much much faster.

Report · Jul 03, 2013

I want to see on the video monitor what the end product will look like while editing which is not HD, DV is great for doing that since I will be going to DVD. If you think 720x480 DV is low quality then you'll think 720x480 MPEG2 is too. I'm making standard definition DVD's as my end product not Blu-ray so encoding an MPEG2 file from DV is plenty good enough for that, been doing it for years.

Premiere CC leaves out a critical file that was generated with CS6 when exporting MPEG2, now causing the chapter points to no longer be 0-frame accurate when making a DVD in Encore so no go for CC at this point unless I'm not using chapter points in a specific project.

Report · Jun 19, 2014

Just did a test on a 47 timeline with Premiere CC 2014 in GPU mode and it found all the preview files on export which only took 6 minutes. Looks like they sped up the way effects are rendered also since it took about 1/4 of the time to do the initial timeline render.

Report · Apr 14, 2015

1080/60p still not work when using Warp Stabilizer with syntheses edges.

Report · Oct 17, 2012

I can confirm that this same issue occurs on Premiere 6.0.2 on the Mac. Using your method seems to have fixed it. So thanks for that! I'm reporting the issue to Adobe. But it seems that others have already done the same. Hope they can fix it. I can see myself accidentally hitting "delete preview files" when doing this. And that would sssssuuuuck.

Report · Oct 18, 2012

Garbershop wrote:
I can confirm that this same issue occurs on Premiere 6.0.2 on the Mac. Using your method seems to have fixed it. So thanks for that! I'm reporting the issue to Adobe. But it seems that others have already done the same. Hope they can fix it. I can see myself accidentally hitting "delete preview files" when doing this. And that would sssssuuuuck.

Great. Glad it helped. And yes, I have accidentally deleted my previews a few times this way. And yes, it sucked really, really badly.

Still awaiting some help and/or a mature admittance to how moderators keep writing off real bugs as user error when so many users are corroborating and reproducing the same issue and all ending up here from searching the internet for a solution to their very real issue. I guess it could just be magic. Magic is always a possibility...

Report · Oct 19, 2012

I also confirm the workaround only in workstations with a cuda card, in the case of ati cards the problem still persists. I also noticed that the "export with previews" seems to work if you export previews generated from premiere built in effetcs. If you use colorista or any other non adobe effect the bug appears. It would be great if adobe take note of every discover that users made about bugs to help fix them soon

Report · Oct 19, 2012

Dan2207 wrote:
I also confirm the workaround only in workstations with a cuda card, in the case of ati cards the problem still persists. I also noticed that the "export with previews" seems to work if you export previews generated from premiere built in effetcs. If you use colorista or any other non adobe effect the bug appears. It would be great if adobe take note of every discover that users made about bugs to help fix them soon

That must be why it's never worked for me - we use colorista a lot.

Report · Oct 24, 2012

Sorry for my english. I continued with the test and I was wrong!!!, premiere pro built in effects doesn't work either, I put 4 effects and export faster but does recompress again, Please adobe fix it!!! If this were an old bug, I would understand the delay, but just cs6 have this bug, before all was ok. I like premiere pro but seeing how fast Final cut X have significant updates (10.0.6) gets me upset.

Report · Apr 17, 2015

Randy, I tried it your way and my computer still shuts down! I'm exporting a H.264 which I just didnthe other day! Only this one is 6.5 minutes long. Wtf? I have a gtx 660 graphics card, 8 megs of ram and an I 5 processor. This is nonsense!

Report · Apr 17, 2015

The native file is an mts file. Is this a issue?

Report · Jul 27, 2012

So you're say that there are no bugs in Adobe CS6 and if anything doesn't work correctly it is due to something wrong with the installation?

Not at all. I'm saying that it works just fine for me, and always has, so it's not likely a bug.

Report · Oct 11, 2012

Jim Simon wrote:
Again, excepting the QuickTime issue, there is nothing you have ever needed to do to "make it work" other than check the box. If it ever hasn't worked for you, then something is probably wrong with your installation.

This is 100% false. Several people in this one thread alone have confirmed along with me about the "Switch to CPU render mode, keep previews" workaround.

Additonally, every single poster in this thread should be posting their Sequence Settings, Project Settings and Output Settings.

But of course it takes a random user to request such a logical step forward toward constructively isolating the issue and not a Moderator who just instantly denies the existence of a bug based on zero evidence.

Report · Oct 10, 2012

This is so dissapointing. The whole "switching to CPU only rendering but Keeping Preview files" thing worked for me in 6.0.0 but now it doesn't. And what if there are QT files in there? I didn't see anyone actually explain what happens if there are QT files. Also, why the heck doesn't "Use Previews" just work? It doesn't work at all for me and this is totally unacceptable. Back to FCP 7. Good grief...