VideoHelp Forum

Our website is made possible by displaying online advertisements to our visitors.
Please consider supporting us by disabling your ad blocker or buy PlayOn and record Netflix! :)
+ Reply to Thread
Page 71 of 71
FirstFirst ... 21 61 69 70 71
Results 2,101 to 2,109 of 2109
Thread
  1. Originally Posted by LigH.de View Post
    (MSYS/MinGW, GCC 7.1.0) ... does XhmikosR still update?
    Good question But while he doesn't, you might give a try to the archive below.
    Nothing special, I just downloaded his latest MSYS1 package and replaced the contents of the mingw directory with nevcairiel's GCC 7.2
    Image Attached Files
    Quote Quote  
  2. Member
    Join Date
    Aug 2013
    Location
    Central Germany
    Search PM
    Huuuge THX
    Quote Quote  
  3. Member
    Join Date
    Aug 2013
    Location
    Central Germany
    Search PM
    Trying to switch from MSYS (XhmikosR) to MSYS2 (MABS); it's not so simple, using separate runs in MinGW32 and MinGW64 as workaround for now to avoid patching the cross compilation toolchain file.

    x265 2.5+27-0e168bdeb48b (GCC 7.2.0)
    Image Attached Files
    Last edited by LigH.de; 26th Oct 2017 at 10:53.
    Quote Quote  
  4. Member
    Join Date
    Aug 2013
    Location
    Central Germany
    Search PM
    x265 2.5+31-df2de6ea407d

    Support for more monochrome video source formats; plus a few fixed nits.
    Image Attached Files
    Quote Quote  
  5. x265.exe 2.5+37-aa9649a2aa8c

    Áchangelog:

    api: 'x265_get_slicetype_poc_and_scenecut' to fetch slicetype, poc and scenecut information

    api: 'x265_get_ref_frame_list' to get forward and backward refrence list

    Implementation of low-pass subband dct approximation.

    doc/test: Add lowpass test, remove/add experimental labels to some features.

    Add vbv-end to denote VBV emptiness after inserting all the frames into it.
    Image Attached Files
    Quote Quote  
  6. Member
    Join Date
    Aug 2013
    Location
    Central Germany
    Search PM
    x265 2.5+47-6a882a9300c2

    Speed-ups, API changes, more internal analysis features, new CLI parameters:

    Code:
       --vbv-end <float>             Final VBV buffer emptiness (fraction of bufsize or in kbits). Default 0 (disabled)
       --vbv-end-fr-adj <float>      Frame from which qp has to be adjusted to achieve final decode buffer emptiness. Default 0
       --lowpass-dct                 Use low-pass subband dct approximation. Default disabled
       --refine-mv-type <string>     Reuse MV information received through API call. Supported option is avc. Default disabled - 0
    Docs: refine-mv-type, vbv-end
    Image Attached Files
    Last edited by LigH.de; 8th Nov 2017 at 06:46.
    Quote Quote  
  7. x265.exe 2.5+54-6ac1b12bcde9

    Code:
    Encoder: avoid blocking in getEncodedPicture() for zero latency when multiple slices are enabled
    Improved performance by 10 - 15 fps depending upon preset and number of slices.
    Image Attached Files
    Quote Quote  
  8. Member
    Join Date
    Aug 2013
    Location
    Central Germany
    Search PM
    ^ please note that this is a real-time encode scenario, not a high-quality one.
    Quote Quote  
  9. Member
    Join Date
    Aug 2013
    Location
    Central Germany
    Search PM
    x265 2.5+55-dd9772385d15

    Add CLI option to enable or disable picture copy to internal frame buffer

    Code:
       --[no-]copy-pic               Copy buffers of input picture in frame. Default enabled
    Allow encoder to copy input x265 pictures to internal frame buffers. When disabled, x265 will not make an internal copy of the input picture and will work with the application's buffers. While this allows for deeper integration, it is the responsbility of the application to (a) ensure that the allocated picture has extra space for padding that will be done by the library, and (b) the buffers aren't recycled until the library has completed encoding this frame (which can be figured out by tracking NALs output by x265)
    I can imagine that when x265 is linked inside an application or as DLL; but how is that supposed to work for x265 as a separate CLI application? I doubt it would have access to memory pointers of a calling application.
    __

    P.S.:

    As far as I hope to understand, it may not be helpful to the pure x265 CLI encoder, but possibly to other applications derived from this structure, configuring itself internally with a CLI parameter string as well.
    Image Attached Files
    Last edited by LigH.de; 15th Nov 2017 at 14:07.
    Quote Quote  



Similar Threads