Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Video Encoding > High Efficiency Video Coding (HEVC)

Reply
 
Thread Tools Search this Thread Display Modes
Old 22nd July 2015, 12:01   #121  |  Link
Jamaika
Registered User
 
Join Date: Jul 2015
Posts: 697
Hi
Recently in other forums for questions about images of BPG and WebP I was banned. Questions about something unreal should not have happened and incitement to the use of fiction is unacceptable. I see that here is quite sizable topic.
I have therefore a loose Vacation question.
Do BPG files are used in cameras?
Can I take screenshot BPG with videos X265? If so, how?

Thank you for your response.

Last edited by Jamaika; 22nd July 2015 at 16:36.
Jamaika is offline   Reply With Quote
Old 22nd July 2015, 12:39   #122  |  Link
jethro
Registered User
 
Join Date: Mar 2006
Posts: 102
no, and IMO you would not be able for the forseeable future, probably never. WEBP may be possible, though especially in android phones.
jethro is offline   Reply With Quote
Old 25th July 2015, 10:41   #123  |  Link
Jamaika
Registered User
 
Join Date: Jul 2015
Posts: 697
I became curious lossless compression HEVC / VP9 (All-I) from RAW. I don't know whether I'm doing it correctly. I have many doubts.
I can't do RAW (RGBA) doesn't using during the conversion to YUV444p10le. I don't think it is possible. Nor do I know what RAW files (eg. YUV420p10le) can be imported directly into BPGenc.

I started with the demuxing of the RAW file PNG (RGBA-32bit)
Code:
ffmpeg.exe -y -s 3840x2160 -r 120.000 -pix_fmt yuv420p10le -loglevel warning -i "input.yuv" -frames 20 -s 1920x1080 -an -sn -f image2 -pix_fmt rgba %%03d_1_image.png
and create animations HEVC (RGBA-32bit) All-I.
Code:
bpgenc.exe -v -a -q 0 -alphaq 0 -lossless -f 444 -m 9 -b 8 -c rgb -fps 120 -keepmetadata "%%03d_1_image.png" -o "rgba_32bit_lossless.bpg"
Here I have many doubts. Why BGPenc converter creates the file first yuv444p 8bit and then it HEVC (BPG) rgba (32bit) ??? Why is there no alpha channel ???
File yuv444p08le
Code:
Input          File               : C:\Users\KOMPUT~1\AppData\Local\Temp\out5624-1.yuv {How is it RAW and can be imported directly into BPGenc?}
Bitstream      File               : C:\Users\KOMPUT~1\AppData\Local\Temp\out5624-1.bin
Reconstruction File               : (null)
Real     Format                   : 1920x1080 25Hz {Why does not the function framerate -fps ???}
Internal Format                   : 1920x1080 25Hz
Sequence PSNR output              : Linear average only
Sequence MSE output               : Disabled
Frame MSE output                  : Disabled
Cabac-zero-word-padding           : Disabled
Frame/Field                       : Frame based coding
Frame index                       : 0 - 19 (20 frames)
Profile                           : main-RExt (main_444_16 [NON STANDARD]) ???
CU size / depth                   : 64 / 4
RQT trans. size (min / max)       : 4 / 32
Max RQT depth inter               : 4
Max RQT depth intra               : 4
Min PCM size                      : 8
Motion search range               : 96
Intra period                      : 250
Decoding refresh type             : 0
QP                                :  0.00
Max dQP signaling depth           : 0
Cb QP Offset                      : 0
Cr QP Offset                      : 0
Max CU chroma QP adjustment depth : -1
QP adaptation                     : 0 (range=0)
GOP size                          : 1
Input bit depth                   : (Y:8, C:8)
MSB-extended bit depth            : (Y:8, C:8)
Internal bit depth                : (Y:8, C:8)
PCM sample bit depth              : (Y:8, C:8)
Extended precision processing     : Disabled
Intra reference smoothing         : Enabled
Implicit residual DPCM            : Enabled
Explicit residual DPCM            : Disabled
Residual rotation                 : Disabled
Single significance map context   : Disabled
Cross-component prediction        : Enabled (encoder-side-residual-based estimate)
High-precision prediction weight  : Disabled
Golomb-Rice parameter adaptation  : Enabled
CABAC bypass bit alignment        : Disabled
Cost function:                    : Lossless coding with fixed QP of 0
RateControl                       : 0
Max Num Merge Candidates          : 5

TOOL CFG: IBD:0 HAD:0 RDQ:1 RDQTS:1 RDpenalty:0 SQP:0 ASR:0 FEN:0 ECU:0 FDM:1 CFM:0 ESD:0 RQT:1 TransformSkip:1 TransformSkipFast:1 TransformSkipLog2MaxSize:2 Slice: M=0 SliceSegment: M=0 CIP:0 SAO:0 PCM:0 TransQuantBypassEnabled
: =1WPP:0 WPB:0 PME:2  WaveFrontSynchro:0 WaveFrontSubstreams:1 ScalingList:0 TMVPMode:1 AQpS:0 SignBitHidingFlag:1 RecalQP:0

                   Input ChromaFormatIDC =   4:4:4
       Output (internal) ChromaFormatIDC =   4:4:4

RVM: 0.594
Bytes written to file: 47132828 (471328.280 kbps)
File HEVC/BPG (RGBA/32bit)
Code:
Input          File               : C:\Users\KOMPUT~1\AppData\Local\Temp\out5624-2.yuv
Bitstream      File               : C:\Users\KOMPUT~1\AppData\Local\Temp\out5624-2.bin
Reconstruction File               : (null)
Real     Format                   : 1920x1080 25Hz
Internal Format                   : 1920x1080 25Hz
Sequence PSNR output              : Linear average only
Sequence MSE output               : Disabled
Frame MSE output                  : Disabled
Cabac-zero-word-padding           : Disabled
Frame/Field                       : Frame based coding
Frame index                       : 0 - 19 (20 frames)
Profile                           : main-RExt (main_444_16 [NON STANDARD])
CU size / depth                   : 64 / 4
RQT trans. size (min / max)       : 4 / 32
Max RQT depth inter               : 4
Max RQT depth intra               : 4
Min PCM size                      : 8
Motion search range               : 96
Intra period                      : 250
Decoding refresh type             : 0
QP                                :  0.00
Max dQP signaling depth           : 0
Cb QP Offset                      : 0
Cr QP Offset                      : 0
Max CU chroma QP adjustment depth : -1
QP adaptation                     : 0 (range=0)
GOP size                          : 1
Input bit depth                   : (Y:8, C:8)
MSB-extended bit depth            : (Y:8, C:8)
Internal bit depth                : (Y:8, C:8)
PCM sample bit depth              : (Y:8, C:8)
Extended precision processing     : Disabled
Intra reference smoothing         : Enabled
Implicit residual DPCM            : Enabled
Explicit residual DPCM            : Disabled
Residual rotation                 : Disabled
Single significance map context   : Disabled
Cross-component prediction        : Disabled
High-precision prediction weight  : Disabled
Golomb-Rice parameter adaptation  : Enabled
CABAC bypass bit alignment        : Disabled
Cost function:                    : Lossless coding with fixed QP of 0
RateControl                       : 0
Max Num Merge Candidates          : 5

TOOL CFG: IBD:0 HAD:0 RDQ:1 RDQTS:1 RDpenalty:0 SQP:0 ASR:0 FEN:0 ECU:0 FDM:1 CFM:0 ESD:0 RQT:1 TransformSkip:1 TransformSkipFast:1 TransformSkipLog2MaxSize:2 Slice: M=0 SliceSegment: M=0 CIP:0 SAO:0 PCM:0 TransQuantBypassEnabled
: =1WPP:0 WPB:0 PME:2  WaveFrontSynchro:0 WaveFrontSubstreams:1 ScalingList:0 TMVPMode:1 AQpS:0 SignBitHidingFlag:1 RecalQP:0

                   Input ChromaFormatIDC =   4:0:0  ???
       Output (internal) ChromaFormatIDC =   4:0:0  ???
RVM: 0.000
Bytes written to file: 1169 (11.690 kbps)
'it-depth' is not recognized as an internal or external command,
operable program or batch file.
For comparison, recording commands codec VP9.(frames aren't All-I)
Code:
ffmpeg.exe -y -loglevel warning -i "%%03d_1_image.png" -s 1920x1080 -an -sn -f rawvideo -pix_fmt yuv444p10le - | /
vpxenc.exe -v --bit-depth=10 --input-bit-depth=10 --i444 -w 1920 -h 1080 --profile=3 --threads=4 --passes=1 --pass=1 --best --codec=vp9 --cpu-used=3 --fps=120000/1000 /
--test-16bit-internal --lag-in-frames=1 --color-space=sRGB / {functions for me, I don't know of unknown use}
--lossless=1 - -o "vp90_444p10le.webm"
Code:
Codec: WebM Project VP9 Encoder v1.4.0-745-gdb50037
Source file: - File Type: RAW Format: I44416  ???
Destination file: vp90_444p10le.webm
Encoder parameters:
    g_usage                      = 0
    g_threads                    = 4
    g_profile                    = 3
    g_w                          = 1920
    g_h                          = 1080
    g_bit_depth                  = 10
    g_input_bit_depth            = 10
    g_timebase.num               = 1
    g_timebase.den               = 1000
    g_error_resilient            = 0
    g_pass                       = 0
    g_lag_in_frames              = 1
    rc_dropframe_thresh          = 0
    rc_resize_allowed            = 0
    rc_scaled_width              = 0
    rc_scaled_height             = 0
    rc_resize_up_thresh          = 60
    rc_resize_down_thresh        = 30
    rc_end_usage                 = 0
    rc_target_bitrate            = 256
    rc_min_quantizer             = 0
    rc_max_quantizer             = 63
    rc_undershoot_pct            = 25
    rc_overshoot_pct             = 25
    rc_buf_sz                    = 6000
    rc_buf_initial_sz            = 4000
    rc_buf_optimal_sz            = 5000
    rc_2pass_vbr_bias_pct        = 50
    rc_2pass_vbr_minsection_pct  = 0
    rc_2pass_vbr_maxsection_pct  = 2000
    kf_mode                      = 1
    kf_min_dist                  = 0
    kf_max_dist                  = 600
Pass 1/1 frame   20/20   53249681B 21299872b/f 2555984688b/s  608028 ms (0.03 fps)[K
Oddly enough, I can't create a file WebM (RGBA) ie. in WebP. {Edit: Already known. WebP (lossy) doesn't RGBA.}

Last edited by Jamaika; 27th July 2015 at 07:18.
Jamaika is offline   Reply With Quote
Old 25th July 2015, 11:20   #124  |  Link
foxyshadis
ангел смерти
 
foxyshadis's Avatar
 
Join Date: Nov 2004
Location: Lost
Posts: 9,558
I'm confused what you're comparing here, since multi-frame BPG already has a format: HEVC. Compressing 20 frames to BPG doesn't make sense, and still images have no fps.

BPG stores RGB32 streams as one 444 stream and one 400 alpha stream, maybe that'll explain what you're seeing. It looks like you're pulling the analysis from HM, which is incorrect, since BPG isn't HEVC. You need a BPG parser to get BPG information.
foxyshadis is offline   Reply With Quote
Old 25th July 2015, 13:58   #125  |  Link
Jamaika
Registered User
 
Join Date: Jul 2015
Posts: 697
Quote:
Originally Posted by foxyshadis View Post
Compressing 20 frames to BPG doesn't make sense,...
Why I chose only 20 frames of the movie? Video compression lasted 1 hour.
Quote:
Originally Posted by foxyshadis View Post
...and still images have no fps.
I don't understand. Videos MJPG has fps and similarly MBPG.
Quote:
Originally Posted by foxyshadis View Post
BPG stores RGB32 streams as one 444 stream and one 400 alpha stream, maybe that'll explain what you're seeing.
I didn't know. Strange record and double the waiting time.
Quote:
Originally Posted by foxyshadis View Post
It looks like you're pulling the analysis from HM, which is incorrect, since BPG isn't HEVC.
I see a transition file *.bin. FFplayer reads it as HEVC. Then BPGenc converter puts it into a container of BPG.
https://www.sendspace.com/file/zemyom
Code:
Input #0, hevc, from 'out5624-1.bin':
  Duration: N/A, bitrate: N/A
    Stream #0:0: Video: hevc (Rext), yuv444p(tv) <-- rgb24(pc), 1920x1080, 25 fps, 25 tbr, 1200k tbn, 25 tbc
    nan M-V:    nan fd=   0 aq=    0KB vq=    0KB sq=    0B f=0/0
I understand that HEVC not read RGBA and content must be in BPG. Otherwise we will not open.

Last edited by Jamaika; 25th July 2015 at 15:04.
Jamaika is offline   Reply With Quote
Old 26th July 2015, 03:00   #126  |  Link
foxyshadis
ангел смерти
 
foxyshadis's Avatar
 
Join Date: Nov 2004
Location: Lost
Posts: 9,558
Quote:
Originally Posted by Jamaika View Post
Why I chose only 20 frames of the movie? Video compression lasted 1 hour.
Use -e x265

Quote:
I don't understand. Videos MJPG has fps and similarly MBPG.
Unless you're specifically trying to make an embeddable animation (like an animated GIF), I think what you really want is real HEVC. Built-in alpha channel support is handy, but that doesn't make sense for a normal movie, and compression will suffer without B frames and only a single reference frame.

The 25fps framerate you wondered about is because bpgenc throws away the encoder's framerate and writes its own instead, so it doesn't bother to pass one to the encoder.

Quote:
I didn't know. Strange record and double the waiting time.
Not double, it's the same time whether it's compressed all at once (which means modifying the encoder) or separately. Each plane is just mostly-unrelated monochrome information to the encoder.

Quote:
I see a transition file *.bin. FFplayer reads it as HEVC. Then BPGenc converter puts it into a container of BPG.
https://www.sendspace.com/file/zemyom
Code:
Input #0, hevc, from 'out5624-1.bin':
  Duration: N/A, bitrate: N/A
    Stream #0:0: Video: hevc (Rext), yuv444p(tv) <-- rgb24(pc), 1920x1080, 25 fps, 25 tbr, 1200k tbn, 25 tbc
    nan M-V:    nan fd=   0 aq=    0KB vq=    0KB sq=    0B f=0/0
I understand that HEVC not read RGBA and content must be in BPG. Otherwise we will not open.
Same thing, BPG just uses the usual YUV planes for whatever purpose necessary. You have to use bpgdec to get the real information from the bpg header.
foxyshadis is offline   Reply With Quote
Old 26th July 2015, 05:14   #127  |  Link
Jamaika
Registered User
 
Join Date: Jul 2015
Posts: 697
Quote:
Originally Posted by foxyshadis View Post
I think what you really want is real HEVC. Built-in alpha channel support is handy, but that doesn't make sense for a normal movie, and compression will suffer without B frames and only a single reference frame.
Okay, we can throw out the channel alpha and B-frames encoder X265. Only in this case, what is the point of using the old codec BPGenc (X265 1.4+96). Not better to take X265.exe --amp --rect --ref 1 --bframes 0 --lossless ?
Problematic is also the elimination of the alpha channel. There is no function -noalpha. You have to replace PNG files by changing RGBA to RGB24.
Quote:
Originally Posted by foxyshadis View Post
The 25fps framerate you wondered about is because bpgenc throws away the encoder's framerate and writes its own instead, so it doesn't bother to pass one to the encoder.
I don't know what is the function of -fps? For me it is a dead function.
Code:
Info with BPGdec
size=1920x1080 color_space=RGB format=4:4:4 limited_range=0 bit_depth=8 animation=1
Extension data:
  tag=5 (Animation control) length=3
PS. When will update v0.9.5 (2015-01-11)? Because it can actually wasting time on things that have fallen into disuse.

Last edited by Jamaika; 26th July 2015 at 07:53.
Jamaika is offline   Reply With Quote
Old 26th July 2015, 08:09   #128  |  Link
foxyshadis
ангел смерти
 
foxyshadis's Avatar
 
Join Date: Nov 2004
Location: Lost
Posts: 9,558
Quote:
Originally Posted by Jamaika View Post
Okay, we can throw out the channel alpha and B-frames encoder X265. Only in this case, what is the point of using the old codec BPGenc (X265 1.4+96). Not better to take X265.exe --amp --rect --ref 1 --bframes 0 --lossless ?
You can build it with a newer x265, some builds might be available. I had it dynamically linking to the x265 dll when it first appeared, but I didn't keep the changes up through later versions.

The format has a very specific purpose: Coding single pictures, with exif information and other photography-specific stuff. Recently it added the ability to do animated GIF-like sequences. It was never intended to be a competing video format, because HEVC itself already serves that role. This is a picture format first and an animation format second (and a movie format not at all).

You can use x265 directly and then bpgmux (from https://github.com/xooyoozoo/libbpg) to convert encodes to BPG. You could create a simple batch file to emulate bpgenc that way.

Quote:
Problematic is also the elimination of the alpha channel. There is no function -noalpha. You have to replace PNG files by changing RGBA to RGB24.
That can easily be done with the C library, but yeah, it's a missing function from the command line. The command-line also can't encode from a pipe, which would be another way to work around it.

Quote:
I don't know what is the function of -fps? For me it is a dead function.
Code:
Info with BPGdec
size=1920x1080 color_space=RGB format=4:4:4 limited_range=0 bit_depth=8 animation=1
Extension data:
  tag=5 (Animation control) length=3
Looks like bpgdec just doesn't show the contents of the animation tag, only its existence; it only reports the size and colorspace. I have looked with a hex editor and I can guarantee that it's whatever you set for fps, not just 25; -fps 120 shows up as 01 78, or 1/120 second per frame. bpgview and the js decoder both respect that framerate.

I'll see if it's possible to get more complete support in MediaInfo so you don't have to rely on bpgdec.

Last edited by foxyshadis; 26th July 2015 at 08:17.
foxyshadis is offline   Reply With Quote
Old 26th July 2015, 11:47   #129  |  Link
Jamaika
Registered User
 
Join Date: Jul 2015
Posts: 697
Quote:
Originally Posted by foxyshadis View Post
You can build it with a newer x265, some builds might be available. I had it dynamically linking to the x265 dll when it first appeared, but I didn't keep the changes up through later versions.
Okay, but we can scratch off such advertising as color spaces RGB, RGBA, CMYK for BPG.
Quote:
Originally Posted by foxyshadis View Post
You can use x265 directly and then bpgmux (from https://github.com/xooyoozoo/libbpg) to convert encodes to BPG. You could create a simple batch file to emulate bpgenc that way.
Supposedly there is a small advantage with respect to compress the file size for the function. On the forum Videohelp told that it is best to compress with minimal loss of data or quality of 95%.
The problem is, I don't know how to set it up for the X265 codec or BPG.
Quote:
Originally Posted by foxyshadis View Post
Looks like bpgdec just doesn't show the contents of the animation tag, only its existence; it only reports the size and colorspace. I have looked with a hex editor and I can guarantee that it's whatever you set for fps, not just 25; -fps 120 shows up as 01 78, or 1/120 second per frame. bpgview and the js decoder both respect that framerate.
I confess that I did not check the EXIF.
On the other hand, I discovered later versions BPGdec/enc where you can convert to BMP, RGB and YUV. I can also conwertować BMP to BPG.
https://www.reaconverter.com/convert/bmp_to_bpg.html
https://convert.zone/BMP-to-BPG
http://pragmaticjoe.blogspot.com/201...n-android.html
PS. Converting other formats is payable.
Quote:
Originally Posted by foxyshadis View Post
The format has a very specific purpose: Coding single pictures, with exif information and other photography-specific stuff. Recently it added the ability to do animated GIF-like sequences. It was never intended to be a competing video format, because HEVC itself already serves that role. This is a picture format first and an animation format second (and a movie format not at all).
Hmmm, just what does it do?
Size file lossless RGB24: | Size file quality 95% RGB24
BMP 6.220.854 | none
PNG 2.996.039 | none
JPG 3.133.548 (RGB24) | 1.224.531 (RGB24)
BPG 2.986.506 | 1.713.554 (-q 12)
WEBP (VP8) 2.671.754 (RGB24) | 0.591.536 (-q 96) (YUV)

Last edited by Jamaika; 26th July 2015 at 21:52.
Jamaika is offline   Reply With Quote
Old 26th July 2015, 17:34   #130  |  Link
foxyshadis
ангел смерти
 
foxyshadis's Avatar
 
Join Date: Nov 2004
Location: Lost
Posts: 9,558
Quote:
Originally Posted by Jamaika View Post
Hmmm, just what purpose is being done?
Size file lossless RGB24: | Size file quality 95% RGB24
BMP 6.220.854 | none
PNG 2.996.039 | none
JPG 3.133.548 | 1.224.531
BPG 2.986.506 | ~1.500.000 (???)
WEBP 2.671.754 | 0.551.310
You can make any of the lossy formats any size you want and call it a percentage or anything you want. Only comparisons of how it looks at similar sizes are meaningful. If you have a rough target of what you want to hit, say 1mb, adjust the quality setting to roughly hit it. I can tell you that the rough equivalent of "95%" in JPEG is -q 12 in BPG, -q 96 in WebP, and -q 70 in JPEG-XR, for 8-bit YV12, but if you change the colorspace then all bets are off.

Since WebP can't store lossless RGB, only YV12, it's not really lossless and will always be much smaller than BPG's true RGB. JPEG can never be lossless at all, even without quantization, due to rounding errors and conversion to YUV. (JPEG-LS exists but isn't compatible.) If you're comparing to formats that can't store RGB, then why bother storing RGB at all?

WebP is just a better-looking JPEG; it doesn't support more than 8-bit or wide gamut or full color, plus it's much slower than x265. VP8 is a terrible format to base a new image format on, it ended up not even being patent-free. BPG is more comparable to JPEG-XR, the VC-1-based image format.

Edit: OK, I take part of this back; WebP lossless is actually 3 or 4 monochrome planes compressed like PNG, so it actually can store RGB(A). However, that's only in lossless mode, not regular.

Last edited by foxyshadis; 26th July 2015 at 18:16.
foxyshadis is offline   Reply With Quote
Old 26th July 2015, 18:18   #131  |  Link
Jamaika
Registered User
 
Join Date: Jul 2015
Posts: 697
I'm a beginner so you can suggest me a lot.
Quote:
Originally Posted by foxyshadis View Post
I can tell you that the rough equivalent of "95%" in JPEG is -q 12 in BPG, -q 96 in WebP, and -q 70 in JPEG-XR, for 8-bit YV12, but if you change the colorspace then all bets are off.
Are the network to any tables?
Quote:
Originally Posted by foxyshadis View Post
JPEG can never be lossless at all, even without quantization, due to rounding errors and conversion to YUV.
I see no loss of data in HEX BMP.

I don't know, is it a JPEG-LS?
Quote:
Originally Posted by foxyshadis View Post
(JPEG-LS exists but isn't compatible.) If you're comparing to formats that can't store RGB, then why bother storing RGB at all?
Understandings that isn't compatible web browsers. Many converters are already JPEG (RGB24). It says that compatible with Adobe.
Quote:
Originally Posted by foxyshadis View Post
However, that's only in lossless mode, not regular.
Why? Is this record lossy not WebP RGB24, the quality factor of 95%? (-q 0:small..100:big)
cwebp.exe -v -q 96 -noalpha -m 6 -progress -metadata all "001_1_image.png" -o "001_1_image_95%.webp"

Last edited by Jamaika; 26th July 2015 at 21:41.
Jamaika is offline   Reply With Quote
Old 26th July 2015, 19:23   #132  |  Link
foxyshadis
ангел смерти
 
foxyshadis's Avatar
 
Join Date: Nov 2004
Location: Lost
Posts: 9,558
I just downloaded Image Converter Plus, created a true lossless JPEG just like your screenshot, and couldn't open it in Photoshop ("Could not complete your request because reading spatial/lossless JPEG files is not implemented.") or anything else for that matter. The format does exist, but it's not used at all outside of specialized medical software. Same with JPEG-LS.

Quote:
Originally Posted by Jamaika View Post
Why? Is this record lossy not WebP RGB24, the quality factor of 95%? (-q 0:small..100:big)
cwebp.exe -q 95 -noalpha -m 6 "001_1_image.png" -o "x265_444p10le.webp"
That'll convert to YUV 4:2:0, because that's the only format lossy WebP can be. I'm not sure why HoneyView would call it RGB, maybe a limitation of the program.
foxyshadis is offline   Reply With Quote
Old 26th July 2015, 19:41   #133  |  Link
Jamaika
Registered User
 
Join Date: Jul 2015
Posts: 697
You're right. There is something wrong. I thought that colorspace YUV be accompanied by a function -jpeg_like. I was wrong.
Code:
Input #0, webp_pipe, from '001_1_image_95%.webp': sq=    0B f=0/0
  Duration: N/A, bitrate: N/A
    Stream #0:0: Video: webp, yuv420p(tv, bt470bg/unknown/unknown), 1920x1080, 25 tbr, 25 tbn, 25 tbc
   4.08 M-V:  0.000 fd=   0 aq=    0KB vq=    0KB sq=    0B f=0/0
Oddly enough, the codec WebP v0.4.3 has no function -color-space sRGB ie. for VP9 WebM.

Last edited by Jamaika; 27th July 2015 at 17:47.
Jamaika is offline   Reply With Quote
Old 2nd October 2015, 07:19   #134  |  Link
Jamaika
Registered User
 
Join Date: Jul 2015
Posts: 697
New version codec BPG 0.9.6. Much faster work.
http://bellard.org/bpg/bpg-0.9.6-win64.zip

Edit: Cancelled function encoder bpgenc.exe -e jctvc. My previous inquiry passed into history. (:
Because the container BPG is based on X265 so I think that soon should be included eg. for ffmpeg and other converters. :idea:

Edit: Problems with conversion:
Code:
bpgenc.exe image1_yuv444p(12bit).jpg -q 0 -f 444 -c ycbcr -b 12 -m 9 -v -keepmetadata -o image1_yuv444p(12bit).bpg
cwebp.exe image1_yuv444p(12bit).jpg -q 100 -noalpha -progress -m 6 -v -metadata all -o image1_yuv420p(8bit).webp {VP8X}
bpgenc.exe image1_rgb(12bit).jpg/png/tiff -q 0 -f 444 -c rgb -b 12 -m 9 -v -keepmetadata -o image1_rgb(12bit).bpg
cwebp.exe image1_rgb(12bit).jpg/png/tiff -q 100 -noalpha -progress -m 6 -v -metadata all -o image1_yuv420p(8bit).webp {VP8X}
ffmpeg -i image1_yuv444p(12bit).jpg -f webp -quality 100 -pix_fmt yuv444p12le image1_yuv420p(8bit).webp {VP8X}
ffmpeg -i image1_rgb(12bit).jpg -f webp -quality 100 -pix_fmt rgb48be image1_yuv420p(8bit).webp {VP8X}
https://www.sendspace.com/filegroup/...3lV7vXx%2FGFcl

Last edited by Jamaika; 3rd October 2015 at 08:13.
Jamaika is offline   Reply With Quote
Old 2nd October 2015, 13:21   #135  |  Link
Skarstorm
Registered User
 
Join Date: Feb 2014
Posts: 8
The new version can also handle files with a resolution higher then the max resolution HEVC supports
Quote:
Originally Posted by vivan View Post
The maximum resolution HEVC supports is 8192x4320.
Very nice
Skarstorm is offline   Reply With Quote
Old 19th May 2016, 17:50   #136  |  Link
Jamaika
Registered User
 
Join Date: Jul 2015
Posts: 697
New version BPG v0.9.7
http://bellard.org/bpg/libbpg-0.9.7.tar.gz

PS Unfortunately, I don't know what contains new. No information. There isn't also compiled. ):

Last edited by Jamaika; 19th May 2016 at 17:59.
Jamaika is offline   Reply With Quote
Old 19th May 2016, 18:43   #137  |  Link
smok3
brontosaurusrex
 
smok3's Avatar
 
Join Date: Oct 2001
Posts: 2,392
Acording to changelog in tarball only js part is updated.
smok3 is offline   Reply With Quote
Old 29th October 2016, 22:18   #138  |  Link
Jamaika
Registered User
 
Join Date: Jul 2015
Posts: 697
Who knows how is it with images BPG (X265)? Are they only to a program XnView?
There are plugins with BPG X265 with 2.1 but not on the official site. Strange
http://encode.ru/threads/2095-BPG-ye...ll=1#post50549

Last edited by Jamaika; 30th October 2016 at 06:49.
Jamaika is offline   Reply With Quote
Old 30th October 2016, 16:36   #139  |  Link
CruNcher
Registered User
 
CruNcher's Avatar
 
Join Date: Apr 2002
Location: Germany
Posts: 4,926
Hi there is a nice compare platform

http://wyohknott.github.io/image-formats-comparison/

it shows exactly

Quote:
Originally Posted by Tommy Carrot View Post
WebP has the same problem these new image formats have: it's superior at high compression rates, where jpeg starts to fall apart to blocks. But image sizes are no big deal anymore, so nobody uses that high compression on images. At sane compression levels, these new and advanced image formats are not better at all, in fact they look smoother and blurrier than jpeg (partly because jpeg's ringing makes the image look sharper and more detailed, but hey, it looks better). This BPG format is probably the first one that doesn't really have this issue, while being undoubtedly much better at high compression rates.



Daala is nowhere near ready for action. It's improving quite rapidly, that's what makes it interesting, but in its current form it's not competitive yet. It has rather noticeable ringing artifacts, and at higher compression rates, chroma artifacts. But i think it has the potential to improve quite a lot in the future, maybe even beyond HEVC.
But it also shows some other interesting results and it shows indeed the visual superiority of BPG currently in most test cases.

http://wyohknott.github.io/image-for...:1&bpg=m&jp2=m
http://wyohknott.github.io/image-for...:1&bpg=l&jp2=l
http://wyohknott.github.io/image-for...:1&bpg=l&jpg=l

http://wyohknott.github.io/image-for...:1&bpg=l&jpg=l
http://wyohknott.github.io/image-for...:1&bpg=m&jpg=m
http://wyohknott.github.io/image-for...&bpg=ll&jpg=ll

At low bitrates you can obviously see it's superior ringing avoidance in a snap,especially on already noisy input it works at those like always since the inloop filter as a pre processor though at higher bitrates it tries to maintain the input as much as possible, exactly what you would want from good content adaptive result imho.

Low Bitrates

Superior Ringing Avoidance without becoming visually unpleasing no matter the input quality

High Bitrates

Exact replication

So it scales pretty nicely overall from 0 to Hero

you can also nicely see how some things of Daala where rethought and more stabilized in AV1 though some unique daala things gone lost obviously in that process as well so far

http://wyohknott.github.io/image-for...:1&ogv=m&jpg=m
http://wyohknott.github.io/image-for...:1&ogv=m&jp2=m


http://wyohknott.github.io/image-for...1&ogv=m&webm=m
http://wyohknott.github.io/image-for...1&ogv=m&webm=m
http://wyohknott.github.io/image-for...1&bpg=m&webm=m
__________________
all my compares are riddles so please try to decipher them yourselves :)

It is about Time

Join the Revolution NOW before it is to Late !

http://forum.doom9.org/showthread.php?t=168004

Last edited by CruNcher; 30th October 2016 at 17:58.
CruNcher is offline   Reply With Quote
Old 30th October 2016, 18:24   #140  |  Link
Jamaika
Registered User
 
Join Date: Jul 2015
Posts: 697
Quote:
Originally Posted by CruNcher View Post
Hi there is a nice compare platform
It's probably everyone knows that such a test was. I wonder what has that got to do with the current theme of BPG. BPG is a new codec X265 v2.1. (I understand that the fee required)
http://forum.doom9.org/showthread.ph...85#post1784385

Last edited by Jamaika; 31st October 2016 at 08:58.
Jamaika is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 14:35.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.