Guide to converting 30fps to 60fps for newbie?

[iamtrout]

I've got a DVD at 30fps and I'd like to convert it to 60fps. I read that I have to bob and interpolate to get it to convert to 60fps.

What are some good smart bobbers?

I have avisynth but I can't figure it out for the life of me. I actually downloaded some instructions to convert 30fps to 60fps using avisynth but the instructions were horrible from a newbie point of view. How do I run the script? What codecs do I need and where do I get them? I installed mvbob and avisynth but it doesn't even have an exe...

Anyone have an easy step by step tutorial?

[GodofaGap]

Avisynth comes with very good documentation. I suggest to read the "Getting started" section.

[iamtrout]

Avisynth comes with very good documentation. I suggest to read the "Getting started" section.

IMO saying that is like saying Linux has very good documentation. It's great documentation but not for newbies. I read through the getting started section, which is piss poor BTW, and I still don't understand how the thing works. What I need is a step wise explanation of what I'm doing. Like why the heck am I renaming a .avi into a .avs and why am I playing it in a media player that AFAIK has no capability of writing an output file to the HDD and why am I opening a huge 700MB file in a text editor that gets crashed? Not to mention it doesn't cover any errors like YV12 errors that I'm getting with VirtualDub. Also, what codecs do I need to encode? I remember back in the day that there was a DiVX codec for decoding, but you had to actually buy the codec that encodes. I have the CCCP codec pack and have no idea if my codecs can encode because they're definitely not showing up in VirtualDub when I save as AVI.

[Dark Shikari]

Like why the heck am I renaming a .avi into a .avsAt this point I stopped reading because I realized that you're complaining about documentation that you never actually read, since it never tells you to do such a thing anywhere in the documentation.

In fact, it gives a very clear newbie's guide right at the start, as follows:

Basically, AviSynth works like this: First, you create a simple text document with special commands, called a script. These commands make references to one or more videos and the filters you wish to run on them. Then, you run a video application, such as VirtualDub, and open the script file. This is when AviSynth takes action. It opens the videos you referenced in the script, runs the specified filters, and feeds the output to video application. The application, however, is not aware that AviSynth is working in the background. Instead, the application thinks that it is directly opening a filtered AVI file that resides on your hard drive.

Linear Editing:

The simplest thing you can do with AviSynth is the sort of editing you can do in VirtualDub. The scripts for this are easy to write because you don't have to worry about variables and complicated expressions if you don't want.

For testing create a file called test.avs and put the following single line of text in it:

Version

Now open this file with e.g. Windows Media Player and you should see a ten-second video clip showing AviSynth's version number and a copyright notice.

Version is what's called a "source filter", meaning that it generates a clip instead of modifying one. The first command in an AviSynth script will always be a source filter.

If you can't understand that, I don't think you'll be able to do much better on these forums.

[iamtrout]

At this point I stopped reading because I realized that you're complaining about documentation that you never actually read, since it never tells you to do such a thing anywhere in the documentation.

In fact, it gives a very clear newbie's guide right at the start, as follows:



If you can't understand that, I don't think you'll be able to do much better on these forums.

I'm reading the official instruction manual:

http://avisynth.org/mediawiki/First_script

Open up any text editor, type the above on the first line (using any AVI file on your machine as "myclip.avi"), and save it as "myclip.avs". You now have a script that can be opened by most AVI players in your machine: Windows Media Player 6.4 (aka "mplayer2") will play the script; so will VirtualDubMod or plain VirtualDub. So far as they care, your text document is an AVI file.

The thing you quoted is great. Too bad it wasn't even off of the official avisynth documentation:

http://puschpull.net/avisynth/english/

This is a hell of a lot more understandable than the official documentation. In fact, you answered my OP by giving me exactly what I wanted; better documentation than the official one.

[Dark Shikari]

The thing you quoted is great. Too bad it wasn't even off of the official avisynth documentation:

http://puschpull.net/avisynth/english/

This is a hell of a lot more understandable than the official documentation. In fact, you answered my OP by giving me exactly what I wanted; better documentation than the official one.I quoted you directly out of the /doc/ folder in the Avisynth directory on my hard disk, silly. That is the official Avisynth documentation.

[iamtrout]

I quoted you directly out of the /doc/ folder in the Avisynth directory on my hard disk, silly. That is the official Avisynth documentation.

Oh, I see. So avisynth.org is totally unofficial. It's so obvious!

[Dark Shikari]

Oh, I see. So avisynth.org is totally unofficial. It's so obvious!It isn't unofficial, in fact, the link you posted above seems to be a perfectly good explanation also. Of course, as it seems you are only here to complain and post sarcastic remarks rather than to ask for help, it is pointless to attempt to give you any further information.

I hope next time you realize that complaining (regardless of whether such a complaint is valid!) is not a valid way of convincing others to help you, especially when the person helping you has nothing to do with the thing you're complaining about. Its like walking up to the guy at Starbucks to complain about the food at McDonald's; its only going to get him annoyed at you.

Of course, if you do actually want help and are willing to return to the topic at hand rather than continuing the off-topic complaints, I'd be happy to continue to offer assistance...

[iamtrout]

It isn't unofficial, in fact, the link you posted above seems to be a perfectly good explanation also. Of course, as it seems you are only here to complain and post sarcastic remarks rather than to ask for help, it is pointless to attempt to give you any further information.

I hope next time you realize that complaining (regardless of whether such a complaint is valid!) is not a valid way of convincing others to help you, especially when the person helping you has nothing to do with the thing you're complaining about. Its like walking up to the guy at Starbucks to complain about the food at McDonald's; its only going to get him annoyed at you.

Of course, if you do actually want help and are willing to return to the topic at hand rather than continuing the off-topic complaints, I'd be happy to continue to offer assistance...

I ask for help because I don't understand the documentation that I found. The reply I get is to read the documentation. I reiterate that the documentation is over my head. You link to a documentation that is a lot easier to understand and tell me that I'm just complaining about documentation. Thanks. If this is going to be how you guys treat newbies, by basically pointing them to the equivalent of google every time they have a problem that is legitimately a bit on the technical side... sorry, not all of us are so technically inclined or experienced in the field of video. I come to you guys with more experience hoping to get an explanation in layman's terms or to get a recommendation for a better resource that is hopefully more understandable and you instead throw my noviceness into my face.

[dat720]

iamtrout, the reason you were pointed to the documentation is because avs can be difficult to explain, often the only way to get the result you want is trail and error, and many different test run's.

AVS can be pretty advanced, but it can also be pretty simple.

Simple AVS script:

video = AVISource("video.avi")
audio = WAVSource("audio.wav")
AudioDub(video, audio)

You then open the avs script with a program that is capable of reading them, which will be most media player's/media convertors, and process it with the chosen program.

Your best bet is going to attempt to get something working with avs then post a "why is'nt this working?" post.

Here is a more advanced script that might be something along the lines of what you are after, again fiddle and adjust to suit your needs:
AVISource("PAL_clip.avi") # Get clip
Bob(height=480) # Separate fields and interpolate them to full height.
BicubicResize(640,480) # Resize to NTSC square-pixel frame size.
ChangeFPS(60000, 1001) # Convert field rate to NTSC, by duplicating fields.
SeparateFields.SelectEvery(4,0,3) # Undo Bob, even field first. Use SelectEvery(4,1,2) for odd field first.
Weave # Finish undoing Bob.


Why do you need to convert to 60fps?

[iamtrout]

Gotcha. Thanks.

[Gavino]

I quoted you directly out of the /doc/ folder in the Avisynth directory on my hard disk, silly. That is the official Avisynth documentation.
I've recently installed Avisynth v2.58, and for some reason the passage you quoted ("Basically, AviSynth works like this:...") has been removed from the installed documentation, which jumps straight into details of syntax, etc. A backward step IMHO.

[dat720]

I don't think so, the creators of Avisynth can't be expected to cater for "everyone's" needs, it just is not possible, i guess they assume if you are downloading Avisynth then you have an idea of what it does. And if you can't figure out the manual it is probably too advanced for you anyway, there is also tons of info available by doing a google search.

Not trying to toot my own horn here, but none of the task's i have ever set out to acheive have i resorted to asking question's on a forum, i have either read the manual, searched for my answer and if i couldn't find it i moved on to trial and error.

[Gavino]

Agreed, it is difficult to write documentation that caters for a broad range of users. But I was surprised to see that an existing (and pretty good) introductory section had been removed (I assume deliberately).

Users like you (and me, if I may say so) don't need it but we can easily skip over it, whereas a real newbie would benefit from a more gentle introduction.

I get the impression that many people do download and use Avisynth without really understanding it, simply by following a recipe, so they should be encouraged to learn more, not put off.

[dat720]

I wouldn't say that, Avisynth is not easy the first time you try to use it, i did heaps of reading before i could acheive what i wanted, i guess he got treated the way he did because his question is not really something that is easily answered for a newb to avisynth, as it requires understanding of how it works and what can and can't be done, a better approach may have been trying with a gui style program without any scripts rather than diving into the deep end....

Lots of the advanced stuff still confuses me, but i work in IT support for a large agency in Australia and get pretty large amounts of satisfaction if i can work something out myself, i like taking on challenges, and making the higher level staff worry that a "Help Desk" employee can acheive things they have troubles with.... gotta shake things up :)