Turtle speed AVS

Krisqo · Post by **Krisqo** » Fri Aug 18, 2006 2:45 pm

I did steps 1 and 2 and after the restart, I have these listed in the codecs menu. Are these supposed to be gone too, since I deleted them orginally, or is it okay to keep them.

BTW, I was using ffdShow from the AMVApp because the one with the CCCP didn't have makeAVIS as far as I could see.

Gepetto · Post by **Gepetto** » Fri Aug 18, 2006 6:26 pm

Those are render codecs, leave them there.

CCCP's ffdshow doesn't have MakeAVIS but since MakeAVIS is making your Premiere crash, you're better off not having it.

Krisqo · Post by **Krisqo** » Fri Aug 18, 2006 9:19 pm

Okay, premiere finally opens fine. Is it safe to install PICVideo?

Now back to what was orginaly asked before my PC went to hell. Am I stuck making huge huffy files to use for editing or is there another way to make fake avis without makeAVIS? I really don't have the space to make over 50 - 70 1GB+ avi files. For example, my AVI rips of Princess 69 are all 4GB each for 30 mins. I really cannot spare that much space and still have my pc run effectivley.

BasharOfTheAges · Post by **BasharOfTheAges** » Fri Aug 18, 2006 9:32 pm

Only make clips. Space problem isn't "solved" perse, but it's going to take up far less space.

Krisqo · Post by **Krisqo** » Fri Aug 18, 2006 9:54 pm

There lies the problem. That would be the obvious answer, but it goes against my editing style. I usually never know what exactly I'm gonna make, so I've been using whole episode avs files and cutting them up in premiere. I did try using just clips in my video "The Place We Promised" and ended up having a good 75% of the movie on my HD anyway. I'm working on replacing my 160 GB drive and getting a 400 Hitachi (It has the right connectors) and a 500 Western Digital (has the other connector) That'll give me about 1225gb of space inside by tower. But right now, I don't have the cash for it.

I'm still wondering why some of my AVS files work fine while others don't. I have gotten them to run fine in premiere per se. I just need to lower the opacity, but why should I need to do that to have them run at normal speed in the timeline?

This is just so confusing

Gepetto · Post by **Gepetto** » Sat Aug 19, 2006 6:36 am

you need to what?

you mean they don't import with normal 100% opacity? Exorcise your computer.

Krisqo · Post by **Krisqo** » Sat Aug 19, 2006 2:50 pm

Hold yer horses. I said I NEED TO LOWER the opacity. Not the opacity is below 100% when I import.

Krisqo · Post by **Krisqo** » Sat Aug 19, 2006 8:07 pm

Double post, sorry.

I'm now posting from a fresh system. Yep, something went to hell and my HD crashed

. Apparently something was inhabiting my PC and it just nuked. Got all slow, started freezing whenever I clicked something and then, bam! System meltdown.

I'll get things up and running again by late tomorrow (8/20) and I'll let you all know if the problem still persists. Thank god I backed up all my files.

Scintilla · Post by **Scintilla** » Tue Aug 22, 2006 7:46 pm

Krisqo wrote:I'm still wondering why some of my AVS files work fine while others don't. I have gotten them to run fine in premiere per se. I just need to lower the opacity, but why should I need to do that to have them run at normal speed in the timeline?

Okay, here's what's going on.

When you drop a clip into Premiere Pro's timeline and don't put any effects on it or change the motion/opacity settings or something else funny, Premiere Pro will think it can play the clip back at realtime, even if it can't. And Premiere Pro will not render preview files (which have a much better chance of playing back smoothly than clips straight from .AVS scripts) for any clip it thinks it can play back at realtime.

But once you change the opacity (or as I do, put a white matte in a higher track at opacity level 0), it allows you to render preview files (that bar will turn red for the affected section, green once you render).

Yes, it is annoying and I don't know of any way to change it. However, it's one of the only disadvantages Pro has to the earlier versions.

And by the way, you probably want to get rid of that "cpu=4" in the call to MPEG2Source in your script. It's useful for when you get to your final export, but while you're still editing it'll just slow you down.

Krisqo · Post by **Krisqo** » Wed Aug 23, 2006 4:54 pm

I did everything and only have one thing to say...

IT WORKS!

This took over a week, but putting the useless clip at the top of the project and setting the opacity to 0 fixed the problem.

Thanks to everyone who helped me with this problem (as well as the ffdShow and Premiere squabble).