Git Product home page Git Product logo

Comments (5)

hassount avatar hassount commented on May 26, 2024

@GuCaixuan
Thank you for your feedback.

From the command line there seems to be a mismatch between the input height of the original yuv input and the height inputted to the encoder. Is that intended ?

from svt-hevc.

GuCaixuan avatar GuCaixuan commented on May 26, 2024

@hassount
Yes, it is.

Thanks!

from svt-hevc.

hassount avatar hassount commented on May 26, 2024

@GuCaixuan
are you expecting the encoder to resize the input on its own ? or are you testing that it will be able to encode garbage video ?

from svt-hevc.

GuCaixuan avatar GuCaixuan commented on May 26, 2024

@hassount
With the following command line, the encode is executed correctly, and the bitstream obtained is resized successfully.
The only difference between the failed command line and the following is that the value of "-h" is 1104 .

SvtHevcEncApp -i Netflix_FoodMarket2_4096x2160_10bit_60Hz_P420.yuv -b width_height_test_M9_Netflix_FoodMarket2_4096x2160_10bit_60Hz_P420_Q16_TUNE1_4060_1104.265 -errlog width_height_test_M9_Netflix_FoodMarket2_4096x2160_10bit_60Hz_P420_Q16_TUNE1_4060_1104.errlog -w 4060 -h 1104 -bit-depth 10 -fps 60 -intra-period 55 -n 100 -compressed-ten-bit-format 0 -q 16 -encMode 9 -rc 0 -tune 1

from svt-hevc.

hassount avatar hassount commented on May 26, 2024

@GuCaixuan
Thank you for the additional information.
the library will not be able to know the original size of the video from a yuv file and it will depend on the input width and height passed in by the user. That said, if the output of the encode with -h 1104 looks good, it means that most likely the actual height of the input file "Netflix_FoodMarket2_4096x2160_10bit_60Hz_P420.yuv" is 4096x1104.

Bottom line what you see above is an expected behavior:

If the encoder gets a width and height that are mismatching with the original dimensions of the input video then it will start encoding garbage video (it will be all green likely). In which case, the prediction will be too bad and the encoder needs to output too many bits to compensate for the bad prediction. @ qp 16, the residual is barely quantized and the output bitrate will probably be in the few hundred Mbps range. in which case the encoder would usually throw an error:
"Error: CopyRbspBitstreamToPayload: output buffer too small"
That is because the output buffers are too small to handle this kind of output. The encoder is usually designed to operate in bitrate ranges that are <100Mbps.

from svt-hevc.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.