VideoHelp Forum




+ Reply to Thread
Page 41 of 75
FirstFirst ... 31 39 40 41 42 43 51 ... LastLast
Results 1,201 to 1,230 of 2222
  1. I tried both under windows 8 and 8.1 64 bit.
    I tried also several builds of x265.exe, all of them crashed.
    Here is a shot Click image for larger version

Name:	x265_shot.png
Views:	1778
Size:	11.3 KB
ID:	22325
    I tried with CBR or QP, same result.
    Quote Quote  
  2. have you tried using x265 without avs4x265?
    Quote Quote  
  3. Yes, and I had the same crashes at the same moment in the process.
    My UAC is off. I tried several video sources with different video codecs and/or containers, always the same problem.
    I have no problem encoding into Xvid, x264 or anything else, the problem is ONLY with x265.
    Quote Quote  
  4. btw. removing '--preset medium' and other default parameters might also help, x265 does not like to be called with parameters that are already the default,... (reported that a while ago to the dev-mailinglist but got no reply whatsoever)
    -> reporting bugs here only gets noticed by a dev if you are lucky, reporting bugs on the bug tracker really is a waste of time and reporting to the dev mailing list also only sometimes gives you a reply, so if this really is a general x265 issue you probably have to live with it until some developer stumbles over it by change,...
    Quote Quote  
  5. Member
    Join Date
    Aug 2013
    Location
    China
    Search PM
    Strongene PC OpenCL HEVC/H.265 Decoder ( test edition )
    I can not use


    Player crash
    Quote Quote  
  6. I was curious about avs4x265 so I gave it a try. I tested it out on a script where the clip is only 2-3 minutes long.

    The ETA came to about 8 hours.

    Is this normal? I can understand the "High Efficiency" encoding aspect and all.
    Quote Quote  
  7. depending on your settings and your machine: yes
    Quote Quote  
  8. Member
    Join Date
    Jul 2013
    Location
    Spain
    Search PM
    Hi all

    In case anyone is interested in x265 in linux, here leave a folder where I'll put the x265 compiled in this system.

    Ubuntu 12.04 LTS 64 Bit:

    Build x265 Linux Ubuntu

    Code:
    x265 [info]: build info [Linux][GCC 4.6.3][64 bit] 8bpp
    x265 [info]: using cpu capabilities: MMX2 SSE SSE2 SSE3 Cache64
    Or watch this video of how to compile x265

    To test encoded files, compile the latest ffmpeg and play the files with ffplay
    For me this way works perfectly...
    Preparation:

    Remove any existing packages:
    Code:
    sudo apt-get remove ffmpeg x264 libav-tools libvpx-dev libx264-dev yasm

    Note: The multiverse repository must be enabled in order to install the libfaac-dev package. See more details on adding repositories.

    Get the dependencies (Ubuntu Desktop users):
    Code:
    sudo apt-get update
    sudo apt-get -y install autoconf automake build-essential checkinstall git libass-dev libfaac-dev \
      libgpac-dev libjack-jackd2-dev libmp3lame-dev libopencore-amrnb-dev libopencore-amrwb-dev \
      librtmp-dev libsdl1.2-dev libspeex-dev libtheora-dev libtool libva-dev libvdpau-dev libvorbis-dev \
      libx11-dev libxext-dev libxfixes-dev pkg-config texi2html zlib1g-dev libmp3lame-dev

    Get the dependencies (Ubuntu Server or headless users):
    Code:
    sudo apt-get update
    sudo apt-get -y install autoconf automake build-essential checkinstall git libass-dev libfaac-dev \
      libgpac-dev libmp3lame-dev libopencore-amrnb-dev libopencore-amrwb-dev librtmp-dev libspeex-dev \
      libtheora-dev libtool libvorbis-dev pkg-config texi2html zlib1g-dev

    Installation Yasm
    Yasm is an assembler and is recommended for x264 and FFmpeg.
    Code:
    cd
    wget http://www.tortall.net/projects/yasm/releases/yasm-1.2.0.tar.gz
    tar xzvf yasm-1.2.0.tar.gz
    cd yasm-1.2.0
    ./configure
    make
    sudo checkinstall --pkgname=yasm --pkgversion="1.2.0" --backup=no \
      --deldoc=yes --fstrans=no --default

    x264
    H.264 video encoder. The following commands will get the current source files, compile, and install x264. See the x264 Encoding Guide for some usage examples.
    Code:
    cd
    git clone --depth 1 git://git.videolan.org/x264.git
    cd x264
    ./configure --enable-static --enable-shared
    make
    sudo checkinstall --pkgname=x264 --pkgversion="3:$(./version.sh | \
      awk -F'[" ]' '/POINT/{print $4"+git"$5}')" --backup=no --deldoc=yes \
      --fstrans=no --default
    cd
    sudo ldconfig

    fdk-aac
    AAC audio encoder.
    Code:
    cd
    git clone --depth 1 git://github.com/mstorsjo/fdk-aac.git
    cd fdk-aac
    autoreconf -fiv
    ./configure --disable-shared
    make
    sudo checkinstall --pkgname=fdk-aac --pkgversion="$(date +%Y%m%d%H%M)-git" --backup=no \
      --deldoc=yes --fstrans=no --default
    cd
    sudo ldconfig

    libvpx
    VP8 video encoder and decoder.
    Code:
    cd
    git clone --depth 1 http://git.chromium.org/webm/libvpx.git
    cd libvpx
    ./configure --disable-examples
    make
    sudo checkinstall --pkgname=libvpx --pkgversion="1:$(date +%Y%m%d%H%M)-git" --backup=no \
      --deldoc=yes --fstrans=no --default
    cd
    sudo ldconfig

    opus (optional)
    Opus audio encoder and decoder. Add --enable-libopus to your ffmpeg ./configure line if you want to use this.
    Code:
    cd
    wget http://downloads.xiph.org/releases/opus/opus-1.0.3.tar.gz
    tar xzvf opus-1.0.3.tar.gz
    cd opus-1.0.3
    ./configure --disable-shared
    make
    sudo checkinstall --pkgname=libopus --pkgversion="$(date +%Y%m%d%H%M)-git" --backup=no \
      --deldoc=yes --fstrans=no --default
    cd
    sudo ldconfig

    FFmpeg
    Note: Ubuntu Server users should remove --enable-x11grab from the following command:
    Code:
    cd
    git clone --depth 1 git://source.ffmpeg.org/ffmpeg
    cd ffmpeg
    ./configure --enable-gpl --enable-libass --enable-libfaac --enable-libfdk-aac --enable-libmp3lame \
      --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libspeex --enable-librtmp --enable-libtheora \
      --enable-libvorbis --enable-libvpx --enable-x11grab --enable-libx264 --enable-nonfree --enable-version3 --enable-libxvid
    make
    sudo checkinstall --pkgname=ffmpeg --pkgversion="7:$(date +%Y%m%d%H%M)-git" --backup=no \
      --deldoc=yes --fstrans=no --default
    hash -r
    cd
    sudo ldconfig

    Finish
    Installation is now complete and FFmpeg is now ready for use. You can keep the x264, libvpx, and ffmpeg directories in your home directory if you plan on updating later. See Updating FFmpeg below for more details. Some optional steps are next followed by instructions on updating FFmpeg and finally instructions on reverting all changes made by this guide.

    Optional Installation
    qt-faststart

    This is a useful tool if you're showing your H.264 in MP4 videos on the web. It relocates some data in the video to allow playback to begin before the file is completely downloaded. Usage: qt-faststart input.mp4 output.mp4. When converting files with ffmpeg you can add -movflags faststart to have the same effect.
    Code:
    cd ~/ffmpeg
    make tools/qt-faststart
    sudo checkinstall --pkgname=qt-faststart --pkgversion="$(date +%Y%m%d%H%M)-git" --backup=no \
      --deldoc=yes --fstrans=no --default install -Dm755 tools/qt-faststart \
      /usr/local/bin/qt-faststart

    Add lavf support to x264
    This allows x264 to accept just about any input that FFmpeg can handle and is useful if you want to use x264 directly. See a more detailed explanation of what this means.
    Code:
    cd ~/x264
    make distclean
    ./configure --enable-static
    make
    sudo checkinstall --pkgname=x264 --pkgversion="3:$(./version.sh | \
      awk -F'[" ]' '/POINT/{print $4"+git"$5}')" --backup=no --deldoc=yes \
      --fstrans=no --default

    Updating FFmpeg
    Development of FFmpeg and x264 is active and an occasional update can give you new features and bug fixes. First, remove some packages and then update the dependencies:
    Code:
    sudo apt-get -y remove ffmpeg x264 libx264-dev libvpx-dev
    sudo apt-get update
    sudo apt-get -y install autoconf automake build-essential checkinstall git libass-dev libfaac-dev \
      libgpac-dev libjack-jackd2-dev libmp3lame-dev libopencore-amrnb-dev libopencore-amrwb-dev \
      librtmp-dev libsdl1.2-dev libspeex-dev libtheora-dev libva-dev libvdpau-dev libvorbis-dev \
      libx11-dev libxext-dev libxfixes-dev texi2html zlib1g-dev

    x264
    Code:
    cd ~/x264
    make distclean
    git pull

    Now run ./configure, make, and checkinstall as shown in the Install x264 section.
    fdk-aac
    Code:
    cd ~/fdk-aac
    make distclean
    git pull
    Now run ./configure, make, and checkinstall as shown in the Install fdk-aac section.
    libvpx
    Code:
    cd ~/libvpx
    make clean
    git pull

    Now run ./configure, make, and checkinstall as shown in the Install libvpx section.
    opus
    Code:
    cd ~/opus
    make distclean
    git pull

    Now run ./configure, make, and checkinstall as shown in the Install opus section.
    FFmpeg
    Code:
    cd ~/ffmpeg
    make distclean
    git pull

    Now run ./configure, make, and checkinstall as shown in the Install FFmpeg section.
    Reverting Changes Made by This Guide

    To remove FFmpeg, x264, and other packages installed for this guide:
    Code:
    sudo apt-get autoremove autoconf automake build-essential checkinstall fdk-aac ffmpeg git libass-dev \
      libfaac-dev libgpac-dev libjack-jackd2-dev libmp3lame-dev librtmp-dev libsdl1.2-dev libspeex-dev \
      libtheora-dev libtool libva-dev libvdpau-dev libvorbis-dev libvpx libx11-dev libxfixes-dev \
      opus pkg-config qt-faststart texi2html x264 yasm zlib1g-dev

    Lastly, delete the x264, fdk-aac, libvpx, opus, and ffmpeg directories in your home folder.
    If you have some kind of error lack of libraries, open /etc/ld.so.conf and check, if the paths /usr/lib and /usr/local/lib exist in the file. If not, add them an run sudo ldconfig.

    I hope I do not disturb anyone putting it in this forum


    Last edited by Trepack; 14th Jan 2014 at 19:18. Reason: Update Info
    Quote Quote  
  9. you should at least post which version of Ubuntu you were using, since binaries build on newer versions can not always be used on older systems,...
    Quote Quote  
  10. Member
    Join Date
    Jul 2013
    Location
    Spain
    Search PM
    Originally Posted by Selur View Post
    you should at least post which version of Ubuntu you were using, since binaries build on newer versions can not always be used on older systems,...
    Ok Ubuntu 12.04 LTS 64 Bit

    Code:
    x265 [info]: build info [Linux][GCC 4.6.3][64 bit] 8bpp
    x265 [info]: using cpu capabilities: MMX2 SSE SSE2 SSE3 Cache64
    Quote Quote  
  11. Member
    Join Date
    Jan 2014
    Location
    Philippines
    Search Comp PM
    A good day to everyone here.I am technically a non-programmer but I do a lot of encoding in the current x264.
    Specifically, I encode in low-bitrate 500-1000kpbs.


    Anyways, may I impose a newbie tutorial on how to use this encoder?
    http://labs.divx.com/node/127929


    I already downloaded the binaries with the latest version - DivX HEVC Encoder v1.0.341
    however, I cannot understand a single bit of the instructions. I'm sorry.
    If someone doesn't mind, please teach me and show screenshots if possible.


    I managed to used strongene lentoid hevc encoder since I found a blogsite telling what's right and left and after that I want to try this one instead.


    Please bear with me sires and I hope I would't be much bother to teach to...



    Quote Quote  
  12. Member
    Join Date
    Jul 2013
    Location
    Spain
    Search PM
    Originally Posted by SuperNoob28 View Post
    A good day to everyone here.I am technically a non-programmer but I do a lot of encoding in the current x264.
    Specifically, I encode in low-bitrate 500-1000kpbs.

    Anyways, may I impose a newbie tutorial on how to use this encoder?
    http://labs.divx.com/node/127929
    What you do not understand?

    DivX H.265/HEVC Encoder

    Usage: DivX265 -i <infile> -o <outfile> -br <bitrate> -s <w>x<h> (for raw infile)

    or: DivX265 -i <infile> -o <outfile> -br <bitrate> (for .avs|.avi infile)

    or: DivX265 -h (for help)

    Example Usage

    from a raw file (yuv/raw, assumes IYUV/I420 colorspace):

    C:\DivX265.exe -i inputfile.yuv -o outputfile.hevc -br 3000 -s 1280x720

    Piping from stdin through another command line tool:

    C:\ffmpeg.exe -i inputfile.avi -s 1280x720 -f rawvideo -pix_fmt yuv420p - | DivX265.exe -s 1280x720 -br 4000 -i - -o outputfile.hevc

    open cmd navigate to the directory where the encoder and video files is.
    Code:
    cd C:\yourfolder
    Press enter
    Or place the pointer over the folder and press shift, right click "open command window here"
    Put the name of the encoder and the commands you want and then press enter
    I uploaded a video sample if it is not clear, excuse was a virtual machine in virtualbox on linux

    Excuse my poor English
    Image Attached Files
    Last edited by Trepack; 14th Jan 2014 at 19:30.
    Quote Quote  
  13. may be a mod can move the last to posts into a new thread.
    DivX265 related problems should not be in the x265 MinGW thread,...

    ---
    regarding DivX265: it is probably more comfortable to use DivXConverter since it offers more options than the DivX265 command line encoder. (+ unlike the DivX265 command line encoder, it will probably be updated more frequently)
    Quote Quote  
  14. Banned
    Join Date
    Nov 2005
    Location
    United States
    Search Comp PM
    @Trepack

    you start off talking about x265 on linux but right after the youtube video you switch to talking about getting x264 working on linux, is that one long ass typo? if it isn't an x264 tutorial doesn't belong in this thread, if it is a mistake you should update your post to reflect that you are talking about x265 all the way through.
    Quote Quote  
  15. Member
    Join Date
    Jul 2013
    Location
    Spain
    Search PM
    Originally Posted by deadrats View Post
    @Trepack

    you start off talking about x265 on linux but right after the youtube video you switch to talking about getting x264 working on linux, is that one long ass typo? if it isn't an x264 tutorial doesn't belong in this thread, if it is a mistake you should update your post to reflect that you are talking about x265 all the way through.
    What's after the video is to compile the new ffmpeg with support for decoding HEVC. I guess if you want to compile ffmpeg with libx264 support, besides having x264 available in the system? or not?

    Why explain how to compile the ffmpeg?

    Or are you encode a video and not want to play?

    For it is the message...
    To test encoded files, compile the latest ffmpeg and play the files with ffplay
    Last edited by Trepack; 15th Jan 2014 at 17:05.
    Quote Quote  
  16. Member
    Join Date
    Jan 2014
    Location
    Philippines
    Search Comp PM
    Thank you very much Mr. Trepack. I hope I can produce some hevc file laters XD

    EDIT: Just 3 minutes after this post...


    It says, Colorspace invalid for source: AVS Content type <avi. or .avs>


    I want to encoding this short avi clip into hevc then it says the ff. above
    Last edited by SuperNoob28; 16th Jan 2014 at 06:09.
    Quote Quote  
  17. x264 needs to be fed with raw video, so you need to run a decoder and feed it's raw output to x265, in example:
    Code:
    mencoder -lavdopts threads=8 -really-quiet -of rawvideo -o - -ovc raw -vf scale,format=i420 -sws 10 -forcedsubsonly -nosub -nosound -mc 0 "Path to AvisynthSkript.avs" | x265 ....
    alternative to mencoder you could also use avs2raw or similar decoders which support .avs

    ffmpeg is also a possibility:
    Code:
    ffmpeg.exe -i "path to file" -an -f yuv4mpegpipe - | x265 --y4m ...
    Quote Quote  
  18. Member
    Join Date
    Jan 2014
    Location
    Philippines
    Search Comp PM
    Sire, I'm sorry but I cannot really understand the code the tiniest bit.Here's what I am doing by now.


    I had this file in the name of 123. avi in the same folder as the DivX265_1.1.18.exe.
    I followed the instructions in the video of Mr. Trepack and the code I used was this.


    DivX265_1.1.18.exe -i 123.avi -o 123.hevc -br 299


    then the cmd says "Colorspace invalid for source..."


    I tried to use the ffmpeg.exe code in the above post but cmd states "[NULL @ 000000000...]Unable to find a suitable output format for 'pipe:' pipe:: Invalid argument


    Hmm, I apologize for asking too many newbie Q but I really want to learn how to encode using this DivX265...
    Quote Quote  
  19. Argh,.. best make a separate thread this thread is about x265 not DivX265,....
    Quote Quote  
  20. Member
    Join Date
    Jan 2014
    Location
    Philippines
    Search Comp PM
    Ok, sorry sire... Yoroshiku in the separate thread...
    Quote Quote  
  21. DECEASED
    Join Date
    Jun 2009
    Location
    Heaven
    Search Comp PM
    INFO

    From the x265 wiki ( https://bitbucket.org/multicoreware/x265/wiki/Home )

    Yasm performance patch

    By default yasm uses a hash table that is too small for our assembly files. By applying this patch you can speed up the compile of our assembly files by a great amount. We have a build of yasm.exe (1.2.0 Win32/VC9) available for free download from this wiki.
    HTH
    Quote Quote  
  22. don't care that much about compilation time, but good to know.
    Quote Quote  
  23. DECEASED
    Join Date
    Jun 2009
    Location
    Heaven
    Search Comp PM
    ^ Still, short compilation times should matter to x265.cc and Fllear, for example

    Anyway, me thinks this thread has already given (nearly?) everything it had to give

    In August of 2013, Vid01 observed that this topic has an unusually-LOW signal-to-noise ratio,
    and yes, he was right

    Originally Posted by Nikos Barkas
    (gui builds, encoder settings, decoder options and setups, you name it)
    Possibly it's time for a brand-new thread,
    dedicated only to test encodes and comparison of the available HEVC encoders
    (x265, DivX, and even the Strongene Lentoid thing)
    Last edited by El Heggunte; 22nd Jan 2014 at 05:12. Reason: formatting
    Quote Quote  
  24. Buildbot have been deceased, since the x265 team don't like this sort of support.
    Last edited by x265.cc; 1st Feb 2014 at 12:53.
    encoder.pw buildbot is NOT affiliated with, endorsed, or sponsored by the
    x265 development team, MultiCoreWare Inc, Xiph.Org Foundation nor VideoLAN organization.
    Quote Quote  
  25. DECEASED
    Join Date
    Jun 2009
    Location
    Heaven
    Search Comp PM
    Originally Posted by x265.cc
    Buildbot have been deceased, since the x265 team don't like this sort of support.
    That suckxsz, man : - /
    Quote Quote  
  26. Member vhelp's Avatar
    Join Date
    Mar 2001
    Location
    New York
    Search Comp PM
    i'm sorry to this news.......and i don't want to go through another session with the lack of stdin support in an alternative h265 encoder, or even vp9 / webm for that matter. it is too much work and time to have to put into the test(s) of these encoders.
    Quote Quote  
  27. with the lack of stdin support in an alternative h265 encoder, or even vp9 / webm for that matter.
    vpxenc does support stdin. DivX265s testing command line encoder does support stdin.
    kvazaar does support stdin.

    What alternative encoder are you thinking of?
    The only alternative H.265 encoder I can think of that doesn't support input via stdin is the direct show encoder from HEVC Encoder by Strongene Lentoid, which due to it's nature of being a DirectShow filter naturally doesn't support input via stdin.

    Cu Selur
    Quote Quote  
  28. kvazaar v0.2.1

    Highlights

    Intra period now as a commandline option
    stdin input support (thanks to JEEB)
    New unit test framework (greatest)
    x264asm abstraction layer taken into use

    BD-rate decrease of 15% expected in LP configuration in comparison to v0.2.0
    (approximation made using very limited testing set)

    More info:
    Quote Quote  
  29. Member x265's Avatar
    Join Date
    Aug 2013
    Location
    Sunnyvale, CA
    Search Comp PM
    We have no issue with anyone building executable software from x265, as long as they comply with the terms of the GPL, and the applicable laws of their country. But we can't sit by while anyone attempts to use the name "x265" (other than our licensees, who receive our permission to represent that their product/service utilizes the x265 encoder). Anyone who has ever created intellectual property understands this. How do you think Baldrick would feel if someone launched a site called videohelp.cc?

    Pro tip: If you want to create a new website/business/organization, pick a name that isn't already taken. The solution is simple... create bobsbuildbot.com, and you're all set to go.
    Quote Quote  
  30. Just to make sure: Is there a problem with me supporting x265 in Hybrid?
    Quote Quote  



Similar Threads

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