Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18
  1. Collapse Details
    #11
    Senior Member
    Join Date
    May 2015
    Location
    Central NY
    Posts
    2,054
    Default
    Wasn't VP9 available to anyone without patent issues? Or is my memory failing on this.

    I wish we would see additional codecs that are truly open, especially really good acquisition and DI codecs (could be one in the same).Also good open consumer codecs (maybe AV1 will take this place from h.264/h.265 which are an mpeg license). Would love to see Avid truly open the DNx system, only some parts are truly open (the LE codecs).


    Reply With Quote
     

  2. Collapse Details
    #12
    Senior Member
    Join Date
    May 2015
    Location
    Central NY
    Posts
    2,054
    Default
    I got about half way through the wiki, but I did pull out some things of note:

    #1 they left room for lossless compression

    #2 they built in a profile that can handle 444 at up to 12 bits

    This is also troubling:
    Patent claims
    In March 2019, Luxembourg-based Sisvel announced the formation of patent pools for AV1 and VP9. Members of the pools included JVCKENWOOD, NTT, Orange S.A., Philips, and Toshiba, all of whom were also licensing patents to the MPEG-LA for either the AVC, DASH, or the HEVC patent pools.[149][150] Sisvel announced it would demand €0.32 for display devices and €0.11 for non-display devices using AV1, but would not seek royalties for encoded content. At the time of the announcement, a list of patents owned by Sisvel was not publicly available. However, Sisvel's CEO stated in an interview that such a list would be posted on Sisvel's website before any licensing demands were sent out.[151][149]

    As of 8th April 2019, the Alliance for Open Media has made a press release, which reiterated the commitment to their royalty-free patent license[152], and made mention of their "AOMedia patent defense program to help protect AV1 ecosystem participants in the event of patent claims", but did not mention the Sisvel claim by name.[153]
    I hate people that take free stuff and pretend to own it!


    Reply With Quote
     

  3. Collapse Details
    #13
    Senior Member
    Join Date
    Mar 2012
    Location
    Beverly Hills, CA
    Posts
    1,915
    Default
    VP9 was free, however only Google was behind the patent defense.

    AV1 incorporates part of VP10. The VP series is concluded.

    Cineform is a great DI codec.

    With Google, Facebook, Apple, Samsung and more supporting the patent defense, AV1 is likely to remain free.


    Reply With Quote
     

  4. Collapse Details
    #14
    Senior Member Cary Knoop's Avatar
    Join Date
    Jan 2017
    Location
    Newark CA, USA
    Posts
    1,384
    Default
    Quote Originally Posted by jcs View Post
    With Google, Facebook, Apple, Samsung and more supporting the patent defense, AV1 is likely to remain free.
    I strongly doubt that Apple is a proponent of any free codecs, it would be a first.

    AV1 is going strong, Android Q will have it built-in.


    Reply With Quote
     

  5. Collapse Details
    #15
    Senior Member
    Join Date
    Mar 2012
    Location
    Beverly Hills, CA
    Posts
    1,915
    Default


    Reply With Quote
     

  6. Collapse Details
    #16
    Senior Member
    Join Date
    Dec 2005
    Location
    Northern California
    Posts
    789
    Default
    How does this fit in?

    =====
    https://support.apple.com/en-us/HT209000

    About incompatible media in Final Cut Pro X
    To prepare for future versions of macOS, detect and convert incompatible media in your Final Cut Pro X and Motion projects.

    [snip]
    In macOS versions up to and including macOS Mojave, third-party software has extended the QuickTime 7 framework to support many incompatible media formats. In versions of macOS after macOS Mojave, the QuickTime 7 framework will no longer be available, so incompatible formats won't be supported in Final Cut Pro, Motion and Compressor.

    Third-party developers may continue to offer compatibility with some formats by building support directly into their apps. Contact developers of third-party apps for more information about media formats supported in their apps.

    Here are examples of media formats affected by this transition:
    AV1 / VP9
    =====

    There are a bunch of other formats listed. And the article was posted at the end of April, 2019.

    Has the AV1 group addressed this issue or announced plans to?

    Jim "not a FCPX users, but I work with some" Feeley
    ----------
    Jim Feeley
    POV Media


    Reply With Quote
     

  7. Collapse Details
    #17
    Senior Member
    Join Date
    Mar 2012
    Location
    Beverly Hills, CA
    Posts
    1,915
    Default
    Jim- AV1 is really still a work in progress. On YouTube it's available for SD video to play with (if you opt in): HD and 4K (where it's really needed) is a way off, though development progress is rapid.

    Apple devices support H.265 in hardware. It's not clear if this is built into a fixed function VLSI hardware component, or if it's more programable (e.g. DCT and vector processors can be combined into new algorithms). If it's the latter, then it might be possible to add AV1 support as a firmware update. If not, then perhaps the GPU, AI/ML (math engines), and CPU can be used to decode AV1 at the cost of more battery usage. Otherwise AV1 won't be available until Apple adds hardware support.

    As for MacOS support: previously VP9 (and early VP1?) was supported through QuickTime 7. Moving forward Apple is dropping QuickTime, though since they joined AV1 I'd expect them to add AV1 to AVFoundation (Apple's newer media support system) which would bring support to all Apple apps. Note the AV1 spec appears to have been finalized around Jan 2019 (perhaps sooner; still being updated in Jan): https://aomediacodec.github.io/av1-spec/av1-spec.pdf . Since literally everyone is on board with AV1, expect to see full Apple support in the future, on both desktop and mobile.

    Again, the tech in AV1 could be used to produce high quality DI variants, e.g. ALL-I (intraframe- no interpolation between frames), similar to ProRes except much smaller file sizes with equivalent quality. The same can be said for photos and stills: HEIF is basically H.265 for stills (latest iOS devices can store images in this format). Think of the JPG frames in MJPEG being H.265 stills (ProRes is basically a variant of MJPEG). The same can be done with the more efficient AV1 for DI video and stills.


    Reply With Quote
     

  8. Collapse Details
    #18
    Senior Member
    Join Date
    Jul 2007
    Location
    Toronto
    Posts
    6,557
    Cool
    Quote Originally Posted by Jim Feeley View Post
    How does this fit in?

    =====
    https://support.apple.com/en-us/HT209000

    About incompatible media in Final Cut Pro X
    To prepare for future versions of macOS, detect and convert incompatible media in your Final Cut Pro X and Motion projects.
    With the current version of Mac OS and Final Cut Pro X you get a "missing plug-in" message when you try to access Cineform files, with no explanation or link to where you can solve this problem.


    Reply With Quote
     

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •