|
Post by obsessive24 on Nov 20, 2011 18:30:46 GMT -5
Is there any particular reason why you want avisynth to load into Vegas? These days I just use avisynth for post-production after I export a lossless AVI from Vegas.
|
|
eunice
Pub Enthusiast
Posts: 116
|
Post by eunice on Nov 20, 2011 19:24:21 GMT -5
Am very tired, just got back from 7 year old niece's birthday party. Just wanted to let y'all know I will be back to answer questions when slightly better rested, and if I can grab a few hours tomorrow I'll do the second screencast with avisynth and DVD source then.
|
|
eunice
Pub Enthusiast
Posts: 116
|
Post by eunice on Nov 21, 2011 9:06:15 GMT -5
Sleep is gooooood. Am awake now amnisias - Not having to convert files is the biggest draw for me because it saves so much hard drive space to just pull it all into premiere as is and make 'virtual clips' (which also don't take up any hd space) on the fly. I've heard some people can just pull straight up .avis as is into Premiere, but I've never been able to. It throws tantrums at me if I try. The other big draw is having so much control over the source itself, being able to fix aspect ratio or kill the audio or change the framerate or whatever quickly and easily across all the files with a single command. Saves a ton of time. astarte - hee, yeah. the great thing about avisynth is how much flexibility there is built into it. I hate to code so I just memorize what I need to make the files work and leave it at that...but for people who love to mess with various ways of doing stuff and dig into it, there's like, a whole other world out there of avisynth filter possibilities As for Vegas...I don't know? I've never worked with anything but Premiere, except for the years when I had a Mac and Final Cut (but no avisynth).
|
|
|
Post by astarte on Nov 21, 2011 15:25:25 GMT -5
I still have to suppress the thought, 'OMG! I'm doing it WRONG!' whenever I see a script for the same thing/effect with different coding. For example I tend to use ' ++ ' between clips to add eps up into one season. I needed a moment to remember that I also use a different clip attribute for mkvs - FFmpegSource2. Your way is the way I add up my export clips before final filtering, so I know both ways and yet I had the treacherous, 'OMG - Wrong. I'm doing it wrong', for half a second ringing in my head.
And I also never worked with anything other than Premiere, so what I said to Nicky about Avisynth 64-bit was nothing more than a guess, because I was told it works with CS5.
|
|
|
Post by obsessive24 on Nov 21, 2011 16:07:53 GMT -5
Hmm, didn't know that you could just use FFmpegSource2() for mkvs. That's useful to know, thanks! 32-bit or 64-bit, I don't think you can just drag and drop .avs files into Vegas the way you could with Premiere (after installing the plugin, that is). There's something that you have to do with avi wrappers and frameserving. I know the name of the processes but never had any luck doing it myself since I only ever had 64-bit Vegas. Oh, okay, I found it in the A&E guide here, halfway down the page. Now it's coming back to me. That should work with 32-bit Vegas.
|
|
|
Post by astarte on Nov 21, 2011 18:41:30 GMT -5
Yeah, I did explain it a bit in my tut over at astartexx.livejournal.com/90448.html, just scroll down. But what it comes down to is going to code.google.com/p/ffmpegsource/ and downloading either 32 or 64bit version or both and then dumping the contents into your Avisynth plugin folder. If you load your script for the first time, you need an extra minute to load, while it gets an index.
|
|