#198 Problem with VISTA X64 & 4GB+ ram

v2.5x
closed-fixed
Ian Brabham
Internals (76)
5
2008-08-05
2008-07-26
Anonymous
No

Hi

For some unknown reason the following script does not work on some movice while on others is working.

DirectShowSource("1920x816source.mkv",audio=false)

bicubicresize(1280,720,0,0.5,240,3,-240,-3)
fft3dGPU(mode=1,precision=2,bt=0,plane=4,sigma=1.5,sharpen=0.4)

The MEGUI x264 starts encoding then after couple hundreds of frames FFDSHOW stops sending frames to X264 resulting in black frames in encoded video.

I have tried different settings of FFT3dGPU without lack.

It seems to be some kind of memory problemm because if I remove the bicubicresize command and set my FFDSHOW to resize and crop it works perfectly in all cases.

BTW I have Windows VISTA X64 and all latest megui MATROSKA SPLITTERS etc. from www.x264.nl
I am also using 258RC2.

Discussion

  • Logged In: NO

    Update

    When I changed a little bit my avisynth it worked

    crop(240,0,-240,0)
    bicubicresize(1280,720,0,0.5,0,3,0,-3)
    fft3dGPU(mode=1,precision=2,bt=0,plane=4,sigma=1.5,sharpen=0.4)

    Conclusion:
    1. Some cropping problemms with resize function or
    2. Problemms with Multi Core capabilty of my CORE 2 QUAD 6600 processor

     
  • Logged In: NO

    Second update
    Unfortunatelly that only helped a bit so the black frames started not at the begining but at the middle of the video. :(
    Now I am checking AVISYNTH 2.57

     
  • Logged In: NO

    Avisynth 2.57 is working correctly with both of scripts.
    It seems that only 2.58 produces black frames during x264 encoding when using resize function. I have checked also other resize variants (bilinear, lanchos) with the same results.

     
  • Ian Brabham
    Ian Brabham
    2008-07-29

    Logged In: YES
    user_id=673887
    Originator: NO

    How much memory do you have? SetMemoryMax in 2.5.7 will default to 25% of free ram, in 2.5.8 it will default to 50% of the amount in excess of 256MB.

    How big does the encoding process get? If it is 1.5Gb to 2GB then add SetMemoryMax(1024) (or less) to the top of your script. Remember 32bit processes can only malloc into the bottom 2GB of address pace (3GB with a hack).

     
  • Ian Brabham
    Ian Brabham
    2008-07-29

    • labels: --> Internals
    • milestone: --> v2.5x
    • assigned_to: nobody --> ianb1957
     
  • Logged In: NO

    Hi

    I have full 4GB RAM, so plenty of it.
    I have six films with resolution 1920x816
    One of them is working with 2.58, rest is not.
    They all working fine with 2.57
    As for the produced file it has between 600-900MB.
    I am checking system resources and there is a lot of free Ram left.

    When I open FFDSHOW TRAY window, I see it transmites the frames and then after for ex.500 frames it stops sending them, while the encoding process continue producing the black frames.

    I will test Setmemorymax with this script but so far is not solved any of my problemms before.
    Some time ago I wanted to join 100 small video files, and no matter how much I used Setmemorymax limit, AVISYNTH always after 30file gave error, no memory left.

     
  • Ian Brabham
    Ian Brabham
    2008-08-05

    Logged In: YES
    user_id=673887
    Originator: NO

    Known problem, work around in 2.5.8-RC3

    32bit processes only have 2GB of address space. As I said 2.5.7 SetMemoryMax defaults to 25% of free ram, in 2.5.8 it defaults to 50%. 50% of 4GB is 2GB so the cache pool will attempt to allocate the entire address space and fail, on 8GB machines 2.5.7 fails the same way.

    SetMemoryMax only controls the size of the cache buffer pool. It has no effect on any other memory allocation in the process.

     
  • Ian Brabham
    Ian Brabham
    2008-08-05

    • summary: Problem with resize function --> Problem with VISTA X64 & 4GB+ ram
    • status: open --> closed-fixed