VideoHelp Forum




+ Reply to Thread
Results 1 to 8 of 8
  1. Member
    Join Date
    Jun 2005
    Location
    N Ireland
    Search Comp PM
    Hi dudes

    I use FIT2DISC to create a nice avisynth scrip for use with CCE.
    Was using this method for months without a problem now all of a sudden every file generates a "frame size xxx * 56 not supported" error
    I have read that this can be a problem with a badly installed avisynth but i have tried uninstalling and reinstalling different versions all to no avail
    EXAMPLE AVS SCRIPT

    # -= AviSynth script by Fit2Disc v1.1.2 =-
    #LoadPlugin("D:\PathOf\AnyPlugin.dll")
    AviSource("C:\Documents and Settings\Dee\Desktop\Movie\the.devil's.ba.avi")
    BicubicResize(688,576,0,0.6,17,0,558,320)
    AddBorders(16,0,16,0)
    #Trim(0,154646).FadeOut(150)


    This results in the error frame size 772*56 not supported but the movies dimensions are 688*576 where as this Script

    # -= AviSynth script by Fit2Disc v1.1.2 =-
    #LoadPlugin("D:\PathOf\AnyPlugin.dll")
    AviSource("C:\Documents and Settings\Dee\Desktop\Movie\the tibetan book of the dead .avi")
    BicubicResize(672,448,0,0.6,0,4,720,395)
    AddBorders(24,16,24,16)
    #Trim(0,81055).FadeOut(150)

    gives the error frame size 924*56 not supported etc..
    any suggestions would be greatly appreciated
    Vote for me and all your wildest dreams will come true
    Quote Quote  
  2. Hi-

    Before sending your scripts to CCE, which doesn't give helpful error messages, first open them in VDub(Mod) which usually gives a message that will help pinpoint the problem.

    I suspect the problem has to do with the odd numbers being used in the crops. You didn't change anything from the way that FitCD gave them to you?
    Quote Quote  
  3. Always Watching guns1inger's Avatar
    Join Date
    Apr 2004
    Location
    Miskatonic U
    Search Comp PM
    Under Mode in the CCE settings, do you have "For DVD" ticked ?

    Try unticking it.

    I also second opening the script in Vdub first. If it does open clean, check File -> Information to make sure resolution from the script is what you think it should be.
    Read my blog here.
    Quote Quote  
  4. Member Soopafresh's Avatar
    Join Date
    Jan 2004
    Location
    United States
    Search Comp PM
    Are you using any external plugin at all in your script? If so, disable it until you find the culprit.

    Actually, disable one line at a time from your script, until you find the offender. If you get all the way to AVIsource("yourfile.avi"), then the problem is in the Avisynth dll or a bad Codec.

    BTW, for CCE specifically, add

    ConvertToYUY2() at the end of your script. It'll keep CCE from having to do the conversion internally.
    Quote Quote  
  5. XXXx56 are dimentions of an error from avisynth. So it outputs to CCE actualy not the image, but an error message. To check what error message is saying, do as manono suggested.
    Quote Quote  
  6. Good advice above. The only thing I might add is this:

    Have you "forced" any settings in FitCD, for instance PAL <-> NTSC resizing for the DGPulldown method?
    The next time you choose an input, (if you don't reset FitCD beforehand), you can get obscurely irregular resizing/cropping values. Those have been the only times I've seen that error.

    Good luck.
    Pull! Bang! Darn!
    Quote Quote  
  7. Member
    Join Date
    Jun 2005
    Location
    N Ireland
    Search Comp PM
    Ty for the advice Guys
    I think the problem was an audio codec and a div3 low motion file
    I usually have the audio demuxed and then saved without audio
    was trying it this way to save time

    VirtualDubMod was unable to open them because of this
    so ive found the culprit
    once again thanks
    Vote for me and all your wildest dreams will come true
    Quote Quote  
  8. The audio wasn't WMA, by any chance? Now that you mention it, I recall having to strip out WMA audio a few times. (Thereafter, I've done it that way regardless. ) Of course, VBR MP3 is often a cause of problems, but I hadn't suspected WMA could be a problem, and was leaving it be.

    Glad you sorted it out.
    Pull! Bang! Darn!
    Quote Quote  



Similar Threads

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