search for: avif

WebP (imagepart of VP9) is better then JPG AVIF (imagepart of VPX/AV1) is better then HEIF please support in OPUS file for album arts more then JPG and PNG... WebP and AVIF are free imageformats can store multiple images thats good for the problem with METADATA_BLOCK_PICTURE only can store one file. i try to push some devs of player and conve...

...e images.Sorry for the error. Correction and update on my demo page: http://nhwcodec.blogspot.com/ Else very quickly I find that this last version has now a good balance between neatness and precision, and I find this visually pleasant, and more and more interesting, I am currently comparing with AVIF.I'll try to improve this again, but for example I have a processing that improves again precision but now it starts to decrease neatness, and so I find results less interesting... Neatness is still the main advantage of NHW I want to preserve. Also I am (visually) comparing with avifenc with -...

...each can only store a single picture I'm very unclear about what the problem is? Opus isn't related to its containers, though, those are separate lists. On Fri, Jun 21, 2019 at 12:56 AM Oliver Petry <oliverpetry at gmx.de> wrote: > WebP (imagepart of VP9) is better then JPG > AVIF (imagepart of VPX/AV1) is better then HEIF > > please support in OPUS file for album arts > more then JPG and PNG... > > WebP and AVIF are free imageformats can store multiple images > thats good for the problem with METADATA_BLOCK_PICTURE > only can store one file. > > i...

...gle picture I'm very unclear about what the problem is? Opus isn't > related to its containers, though, those are separate lists. > > On Fri, Jun 21, 2019 at 12:56 AM Oliver Petry <oliverpetry at gmx.de> wrote: > >> WebP (imagepart of VP9) is better then JPG >> AVIF (imagepart of VPX/AV1) is better then HEIF >> >> please support in OPUS file for album arts >> more then JPG and PNG... >> >> WebP and AVIF are free imageformats can store multiple images >> thats good for the problem with METADATA_BLOCK_PICTURE >> only can...

...d me in the past that I must adapt NHW to any image size else nobody will consider and use it.That's certainly right, but again I am working on NHW on my spare time and this task is too exhausting for me.Also, I feel now that it is useless, as I have read that in the very next months, the great AVIF and JPEG XL will be definitely adopted everywhere on the Internet. Some people also told me to forget about image compression and turn my codec into a video codec, but that's also too much work for my free time.So I have come to the conclusion that very soon when AVIF and JPEG XL will be adopt...

...monitor > > would get confused by a VIC not yet defined when the monitor was > > produced. > > > Are you sure this is a good idea? As I said earlier 4K modes are present > in HDMI 1.4 and 2.0 but they are handled differently, so this is not > only matter of unknown VIC in AVIF. > > > Regards > > Andrzej -- Ville Syrjälä Intel

...IC not yet defined when the monitor was > >>> produced. > >>> > >> Are you sure this is a good idea? As I said earlier 4K modes are present > >> in HDMI 1.4 and 2.0 but they are handled differently, so this is not > >> only matter of unknown VIC in AVIF. > >> > >> > >> Regards > >> > >> Andrzej > -- Ville Syrjälä Intel

...ality setting whereas files size is smaller.I notably find this new -l16 quality setting better than x265 (HEVC). More at: http://nhwcodec.blogspot.com/ We can still save 2.5KB per .nhw compressed file. I however know that this work is hopeless because the industry will soon standardize AOM AV1 (AVIF) as the new image compression codec.I have also read on twitter that the new JPEG XL standard will be based on AOM AV1.I could not test AOM AV1 but I guess that if the Alliance for Open Media never answered me it's because AOM AV1 is better than the NHW Project. Anyway I wanted to remind the a...

Hello, For those interested, I have made a new version of NHW.This one has more precision and a little more neatness. I still find that NHW has a very good neatness -which I find visually more pleasant than AVIF and x265 for example-, and NHW is still extremely fast to encode/decode, faster than JPEG! There are still many improvements that can be done, first one is to adapt to any arbitrary image size this proof-of-concept, and for that I wanted to let you know (again...) that I am searching for a sponsor...

...seen any bugs where an older monitor > would get confused by a VIC not yet defined when the monitor was > produced. > Are you sure this is a good idea? As I said earlier 4K modes are present in HDMI 1.4 and 2.0 but they are handled differently, so this is not only matter of unknown VIC in AVIF. Regards Andrzej

...would get confused by a VIC not yet defined when the monitor was >>> produced. >>> >> Are you sure this is a good idea? As I said earlier 4K modes are present >> in HDMI 1.4 and 2.0 but they are handled differently, so this is not >> only matter of unknown VIC in AVIF. >> >> >> Regards >> >> Andrzej

On Wed, Nov 21, 2018 at 01:40:43PM +0200, Jani Nikula wrote: > On Tue, 20 Nov 2018, Ville Syrjala <ville.syrjala at linux.intel.com> wrote: > > From: Ville Syrjälä <ville.syrjala at linux.intel.com> > > > > Make life easier for drivers by simply passing the connector > > to drm_hdmi_avi_infoframe_from_display_mode() and > >

...ned when the monitor was >>>>> produced. >>>>> >>>> Are you sure this is a good idea? As I said earlier 4K modes are present >>>> in HDMI 1.4 and 2.0 but they are handled differently, so this is not >>>> only matter of unknown VIC in AVIF. >>>> >>>> >>>> Regards >>>> >>>> Andrzej

...> >>>>> produced. > >>>>> > >>>> Are you sure this is a good idea? As I said earlier 4K modes are present > >>>> in HDMI 1.4 and 2.0 but they are handled differently, so this is not > >>>> only matter of unknown VIC in AVIF. > >>>> > >>>> > >>>> Regards > >>>> > >>>> Andrzej > -- Ville Syrjälä Intel