i like to use, but i use vegas11, and something doesn't work, handbrake just don't start encoding.

Anyway i like ripbot264 better, so i like to use that.

Thanks wwaag

In that case, here is the link for the files you need. Rather than V13, install in script folder for V11.

https://www.dropbox.com/sh/oy3cchtg2otwd8g/AAA7kdY4t439U8A50f-MSvDwa?dl=0

It should work. Let me know if there are problems.

wwaag

Great, it works perfecty!
Now i can set another render format and template too? :)

Now i can set another render format and template too?

Yes, you should be able to by changing the video renderer and template names in lines 12 and 13 and also the output filename and extension in line 41. If it works, change the name and add a new icon and you should be in business. I must admit that this script is actually pretty useful since I use frameserver a lot and one click is a lot easier than going through the dropdown menu process. One caveat that I forgot to mention. It will render only that portion of the timeline that has been selected as a loop region, so to render the entire timeline you need an in and out points at the beginning and end. In other words, it always defaults to "render loop region only" so you will need to define the region. Again, this is not my original script, but only a modified script that was part of the Send to Handbrake software written by Marco.

wwaag

Yes, thank you again!
Now finally ripbot264 mp4 rendering is also very good with interlaced hd material. At 15mbps the quality is fantastic vs. internal encoders. With avisynth script i can also correct the frameserver audio click bug at the end. So everything seems fine - at last.

Glad it's working for you. I'm sure that you're aware of the other audio problem. When frameserving, 48Khz audio is rendered out at 44Khz and then re-converted back to 48Khz in Handbrake or whatever encoder you are using. I'm not sure how much of a problem this really is, but I always render the audio separately and then remux. It's an extra step, but at least I know the two conversions were avoided. In any case, I'd be interested in seeing your avisynth script and how you deal with the click at the end.

wwaag

OT:

I don't think for average person this conversion 48->44->48 will be a problem. I cannot hear. I don't make music discs, or concerts and don't use high quality music tracks (sacd, 96khz, etc :)

My script is this:

AviSource("frameserved.avi")
Trim (0, FrameCount-1-Floor(FrameRate))
ConvertToYV12(interlaced=true,matrix="PC.709")

SeparateFields()
E = SelectEven().Sharpen(0.3)
O = SelectOdd().Sharpen(0.3)
Interleave(E, O)
Weave()

this will cut 1 seconds from the end (the audio bug)
also sharpen interlaced material correctly!

Thanks for the script info.

wwaag

I have not seen the audio problem at the end when frameserving but I use Avisynth+ instead of Avisynth. Avisynth+ also supports frameserving audio so no need to have audio samples placed in the AVI signpost file. Maybe this later part is why I don't see the audio thing. For reference I frameserve to ffmpeg.

What's your method exactly for frameserving audio?
I don't have to render audio to debugmode avi file? Sounds good, because on a 1+ hour timeline its a few minutes. Without audio its 3 seconds.

thanks

What's your method exactly for frameserving audio?

Simply uncheck the box "Write audio as PCM......" and audio will be served along with video frames, not as a separate file.

wwaag

Simply uncheck the box "Write audio as PCM......"

That.

When I first tried the frameserve thing I used Avisynth and it needed the PCM option checked for audio. I tried Avisynth+ and it worked with serving the audio and I have stayed with that.