Premier Crashing when opening multiple avs scripts

[Pirate King]

I am having a problem with Adobe Premier Pro 2.0 crashing when opening more than 6 avs script files of typical episode length. There is no problem with any of the scripts themselves as they all open fine on their own. I have never tried editing directly with avs files and have just used lagarith in the past but im working with a large number of episodes and lagarith takes up like 7 times the space that raw DVD files do and space was going to be an issue.

I thought about using the swap method but assume I would just run into the same problem when I went to switch the low quality encodes for the avs files.

Is it a memory issue? my comp has 2 gigs of ram and I have tried lowering the set memory max option in the Premier AVS configuration to the lowest recommended setting of 16 MB with no luck. I cant see why it would be a problem as I have no problem with loading multiple video files that are much larger.

If all else fails I can resort to using Lagarith encodes but would prefer not to.

Has anyone had this same problem and found a work around, any input would be appreciated as I am out of ideas.

thanks in advance.

[fiathriel!]

I'm also having this trouble, I can see in the systray that a ridiculous amount of icons are appearing as Premiere tries to load the file.

I have a quad processor and 8gig of ram, it's driving me nuts. I had no problem with my previous PC which has 1gb of ram and a 6 year old processor.

[fiathriel!]

I'm also having this trouble, I can see in the systray that a ridiculous amount of icons are appearing as Premiere tries to load the file.

I have a quad processor and 8gig of ram, it's driving me nuts. I had no problem with my previous PC which has 1gb of ram and a 6 year old processor.

I'm using ffmegsource now instead of directshow in the avs scripts and the icons don't appear anymore!!

[Krisqo]

I've never had success using AVS files in Premiere 6.5 or Pro.

First try shutting off most of your filters aside from deinterlacing, resizing and framerate conversions when you edit because it can still sap a lot of memory. If you do not know, you disable filters by placing a "#" before the filter name.

For Example

Code: Select all

Mpeg2Source("E:\Sakura1\sakura1.d2v", cpu=4)
TCOmb()
deint=TDeint(mode=2, mtnmode=3, blim=100)
TFM(cthresh=4, slow=2, clip2=deint)
TDecimate(mode=1)
#deen("w2d",7,5,9)
#FluxSmoothST(7,7)
#WarpSharp()
#FastLineDarken()
#SDDerainbow()
#tweak(sat=1.4, cont=1.0, bright=-10)
#ColorYUV(gain_u=1)
ConvertToRGB32()
Crop(8,60,-8,-60)
BiCubicResize(720,360)
AddBorders(0,60,0,60)
AssumeFPS(24)

Then edit. When you are done. Go back to your AVS files and delete the #. All your scripts should then update when you reload the software for render.

Also try using the "SetMemoryMax()" function at the start of your script to dictate how much RAM you want allocated to that script.

If you have the AMVApp 3.0 beta, you should have a program called VFAPIConv. All you do is load your scripts into the program, hit convert and presto. You now have a small fake AVI file to edit with. I also suggest shutting off the filters as mentioned. When you are done editing, run the scripts back through VFAPIConv and convert and you are done.

I have had little to no problems using VFAPI on a Intel Pentium 4 2.8GHz Dual Core processor with 2 GB of RAM.

[fiathriel!]

I've never had success using AVS files in Premiere 6.5 or Pro.

First try shutting off most of your filters aside from deinterlacing, resizing and framerate conversions when you edit because it can still sap a lot of memory. If you do not know, you disable filters by placing a "#" before the filter name.

Then edit. When you are done. Go back to your AVS files and delete the #. All your scripts should then update when you reload the software for render.

Also try using the "SetMemoryMax()" function at the start of your script to dictate how much RAM you want allocated to that script.

If you have the AMVApp 3.0 beta, you should have a program called VFAPIConv. All you do is load your scripts into the program, hit convert and presto. You now have a small fake AVI file to edit with. I also suggest shutting off the filters as mentioned. When you are done editing, run the scripts back through VFAPIConv and convert and you are done.

I have had little to no problems using VFAPI on a Intel Pentium 4 2.8GHz Dual Core processor with 2 GB of RAM.

All filters are off except 'Trim', didn't help.

Also, tried to use VFAPIConv but it wont install with the security permissions in Vista, even after setting full access to the system32 and system.ini.

Now I'm at a loss what to do, I can't edit in lossless because I have 50+ episodes I'm working on. The VFAPI sounded like the perfect solution

[Autraya]

Now I'm at a loss what to do, I can't edit in lossless because I have 50+ episodes I'm working on. The VFAPI sounded like the perfect solution

I did. I converted all of gundam seed and gundam seed destiny to lossless to edit with that 100 episodes There are things you can do to save space, like picking a smaller resolution, killing the audio, not increasing saturation, using lagarith instead of huffyuv etc
But if HDD space is a problem for you them just scan through the footage and make clips of scenes that you think you'll need instead of the entire episode.

[fiathriel!]

Now I'm at a loss what to do, I can't edit in lossless because I have 50+ episodes I'm working on. The VFAPI sounded like the perfect solution

I did. I converted all of gundam seed and gundam seed destiny to lossless to edit with that 100 episodes There are things you can do to save space, like picking a smaller resolution, killing the audio, not increasing saturation, using lagarith instead of huffyuv etc
But if HDD space is a problem for you them just scan through the footage and make clips of scenes that you think you'll need instead of the entire episode.

I did consider it, I have lots of HDD space, about 500gb . . . . how big did each of your episodes turn out to be?

I've got the VFAPI thing installed finally, works very well but Premiere Pro doesn't like it. Everytime I drag from the bin to the timeline it gets an error and also when I drag from one video track to another, if I drag left and right on the same video track, it's fine.

Mmmm . . . . still considering options.

[Zarxrax]

50 episodes, that's your problem.
Try loading multiple episodes through each avisynth script, and cut out any episodes you don't need. Reduce the total number of avisynth scripts by as much as possible.

[fiathriel!]

50 episodes, that's your problem.
Try loading multiple episodes through each avisynth script, and cut out any episodes you don't need. Reduce the total number of avisynth scripts by as much as possible.

Ahh, OK, so overloading Premiere with scripts isn't the greatest idea? . . . . so far after changing to VFAPI it's being far more compliant, it's mainly crashing on drag and drop features, it's more workable.

I was going to compress the footage and using avi's but most people advise against this as well. Thanks for the all the input, I'll keep plodding along.

[Krisqo]

With VFAPI I typically encode just one DVD per script. And also I'm using older versions of Premiere which seem to be more stable than the newer from what I hear.

But making clips is the best choice. Find the scenes you know you are going to use and created a Lag or Huff file. Might be about 10-20mb + for a few seconds, but they should load with no problem. Then as you edit, you can cut more clips as you find necessary.

I don't do it because I never know what I'm going to use for my clips until I'm actually working.