VideoHelp Forum




+ Reply to Thread
Results 1 to 16 of 16
  1. Member
    Join Date
    Feb 2001
    Location
    Berlin, Germany
    Search Comp PM
    Did anyone get this combination working?
    Or could anyone ever open a .avs file in v.2.62 at all?

    <font size=-1>[ This Message was edited by: Truman on 2001-07-05 15:59:31 ]</font>
    Quote Quote  
  2. no i have tried to get it to go but no way only way i get 2.62 to work is smartripper>dvd2avi?tmpgenc(for resizing)>vfapi>cce2.62

    i use this combo for video and audio and it is working awesome on my box duron 900. 112 minute movie takes 4 hours for video and audio doing 2450 bit and 256 audio
    then mux and chunk with bbmpeg then vcdimager to make leagal svcd nero would make the svcd unplayabe in my apex but vcdimager makes em right
    Quote Quote  
  3. Member
    Join Date
    Feb 2001
    Location
    Berlin, Germany
    Search Comp PM
    thanks buzzard, but rather I go back to CCE 2.50.
    Anyone else?
    Quote Quote  
  4. It's easy enough to get 2.62 to "open" an avs - use TMPGEnc to open the AVs, then use VFAPI to convert the TMPGENc project - the same way that _buzzard_ is using for dvd2avi - as long as you don't have TMPGEnc do any resizing or filters or whatnot, it doesn't appreciably increase the time.
    Quote Quote  
  5. Member
    Join Date
    Feb 2001
    Location
    Berlin, Germany
    Search Comp PM
    Until now I used the way, that buzzard mentioned.It works good, but always I try to make it better.

    First there is the resize question.Is resizing with Vdub (precise bicubic) better than Avisynth (bicubic) better than TMPG (???) ?

    The 2nd is the option to increase the encoding speed.
    The method dvd2avi>Avisynth(MPEG2DEC)>CCE2.50 is a lot faster than the method above (here 0.590, there 0.410)

    Unfortunatly I can it only use, when the video structure is progressiv.

    Quote Quote  
  6. AVISynth is slightly more accurate than VirtualDub because of a bug in VirtualDub, although AVISynth says you would never notice the difference. Don't know how it compare with TMPGEnc, but they're definitely no worse. One thing you will find - if you have enough hard disk space and you want to do a 2 or 3-pass encode, you're probably better off using Huffyuv and having VirtualDub write a segmented AVI file, then use AVISYnth's SegmentedAVISource() to read it - instead of .3-.5, I get 1.2 speeds when I do this (because all of the calculations have already been done, and it's just reading and encoding with no extra munging).
    Quote Quote  
  7. Member
    Join Date
    Feb 2001
    Location
    Berlin, Germany
    Search Comp PM
    Thanks man, I'll check it out.
    Quote Quote  
  8. Member
    Join Date
    Feb 2001
    Location
    Berlin, Germany
    Search Comp PM
    ..hmm one more question VidGuy, I did that. 1 hour movie need about 30-35 gigs. Conversion to segmented avi(huffyuv) takes about 3:15 hours. I have got movie00.avi, movie01.avi and so on (17 avis)
    To feed it in CCE I wrote following script:
    SegmentedAVISource("F:\full path\movie.avi"
    because I read anywhere, Avisynth will load every segment automaticly. But I must have done anything wrong, CCE freezes just when I try to feed the .avs into CCE.

    There may be one more thing wrong. I can encode the .avi (every segment seperatly). But I stay with a 0.350 speed!

    I calculated a bit. Even when I get a speed of 1.200, the whole process is exactly as fast as the MPEG2DEC method, when I do a 3pass encode. For 4 passes your method is the faster one (and indeed it looks good).

    Since I dont have so much HDD space all days, I will stay with MPEG2DEC, but VIdGuy, if you have an idea, what I did wrong, please tell me. I need it for VHS capture.

    Maybe I should use another Avisynth version for that, currently I have the latest MMX optimized version installed.


    <font size=-1>[ This Message was edited by: Truman on 2001-07-09 13:02:19 ]</font>
    Quote Quote  
  9. I haven't tried the Mpeg2Dec method yet - I'm going to give it a spin tonight, I hope. However, it should still be faster to output with VirtualDub, I would think, rather than doing the resizing and cropping 4 times (for 3-pass VBR).

    The SegmentedAVISource() does work. However - I have had problems with CCE and avs files. TYpically what I do is to create an ecl file using the original d2v_vfapi.avi file, then edit the ecl file to change the width from 720 to 480 and the d2v_vfapi.avi filename to the avs filename.

    The problem is CCE gets messed up trying to "find" the last frame for some reason - by editing the ecl project file - the last frame number is stored in it already. The other way is to just use TMPGEnc's source range tab to find the last frame and edit that into the ecl file if you haven't got the original d2v file handy.

    Someone might want to try this method on CCE 2.62 and see if this "backdoor" way of getting the avs file into CCE work (I'll probably try it later, but right now, I haven't bothered upgrading to 2.62)
    Quote Quote  
  10. Kind of odd that you stay at .315 - I'm not sure what the story is there. Obviously, if you get .315 on one segment, it won't get any faster with multiple segments. Not sure why I see such an improvement. Although it may be the YUV->RGB conversion - hadn't given that issue any though. I always thought that it was CCE that required RGB - didn't realize it was the VFAPI step. Looking forward to trying MPeg2Dec and see what numbers I get - I'll let you know.
    Quote Quote  
  11. Member
    Join Date
    Feb 2001
    Location
    Berlin, Germany
    Search Comp PM
    Yes, SegmentedAVISource(..)works after creating and editing the .ecl file. What a great idea, thank you. Unfortunatly I stick with 0.350. Anyway, I don't have the HD space to use this method everytime. And by the way, I tried that with v2.62 too. Everything seemed to work fine until I hit "encode".
    THIS IS NOT AN AVI FILE.
    Don't worry about, 2.62 isn't better or faster or anything else.
    The only real difference I've noticed is, that MPEG-1 VBR isn't possible anymore.

    And I guess the CCE guys work hard to make it uncompatible with open source progs like Vdub or Avisynth. That's probably the back side of open source.

    Back to SegmentedAVI: I capture from VHS using Vdub. Then I type that line, save it as avs, and feed the avs into TMPG. Then I save the tpr project and convert it with VFAPI. Now I feed the *vfapi.avi into CCE, save the project and edit the ecl file and encode.
    This sounds quite uncomfortable!

    For dvd rips I'm very happy with the MPEG2DEC method. Today I encoded a movie,(that I didn't need to resize) to 720x576 XSVCD with 0.735 speed (T-bird 1,2G).
    Quote Quote  
  12. Yeah - I was annoyed when I couldn't do MPeg1 VBR with it - that was the final straw that got it canned from my disk....
    Fortunately, I see no reason to stop useing 2.5 - it works great.

    Yeah the whole VFAPI thing is ugly just to get an avs into CCE. Fortunately, don't need to with 2.5.
    Quote Quote  
  13. Ommigod - Truman - I'm definitely a believer in MPeg2Dec now -

    A ReduceBy2/Crop for VCD - speed of 1.2
    A BicubicResize(480,480) - Speed of .98

    My speed the old way with CCE was about .4-.5. This is way better than dumping the whole sucker to disk. ...
    I luv it!
    Quote Quote  
  14. Member
    Join Date
    Feb 2001
    Location
    Berlin, Germany
    Search Comp PM
    I'm very glad to see you happy.
    Quote Quote  
  15. Member
    Join Date
    May 2001
    Location
    Somerset, CA
    Search Comp PM
    VidGuy - Glad to see you got around to trying MPEG2DEC. It really is a cool little .dll (tool). I use it all the time now. Now all we need is for someone to come up with something the do a good job with de-interlacing those "extras" on DVD's.
    Quote Quote  
  16. Member
    Join Date
    Feb 2001
    Location
    Berlin, Germany
    Search Comp PM
    Sully, is there a difference with de-interlacing extras or main movie??
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!