home.social

#openexr — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #openexr, aggregated by home.social.

  1. That's the point of @Blosc2 being a meta-compressor for numerical data, you can do what ever you want, if you are interested look at the #OpenEXR usages, and filters presented for @aras_p:
    aras-p.info/blog/2023/02/18/Fl
    aras-p.info/blog/2023/03/01/Fl
    8/11

  2. That's the point of @Blosc2 being a meta-compressor for numerical data, you can do what ever you want, if you are interested look at the #OpenEXR usages, and filters presented for @aras_p:
    aras-p.info/blog/2023/02/18/Fl
    aras-p.info/blog/2023/03/01/Fl
    8/11

  3. That's the point of @Blosc2 being a meta-compressor for numerical data, you can do what ever you want, if you are interested look at the #OpenEXR usages, and filters presented for @aras_p:
    aras-p.info/blog/2023/02/18/Fl
    aras-p.info/blog/2023/03/01/Fl
    8/11

  4. I just released a new Blender extension for blurring images and scene backgrounds: extensions.blender.org/add-ons

    Under the hood, it uses the image processing libraries @pillow and #OpenEXR.

    If you have ideas to build blender extensions yourself, join Brady Johnston and me at our talk “Extensions are Coming” at the Blender Conference next week, were we will be talking about how to develop Blender extensions. conference.blender.org/2025/pr
    (Recordings will be available as well.)

  5. I just released a new Blender extension for blurring images and scene backgrounds: extensions.blender.org/add-ons

    Under the hood, it uses the image processing libraries @pillow and .

    If you have ideas to build blender extensions yourself, join Brady Johnston and me at our talk “Extensions are Coming” at the Blender Conference next week, were we will be talking about how to develop Blender extensions. conference.blender.org/2025/pr
    (Recordings will be available as well.)

  6. I just released a new Blender extension for blurring images and scene backgrounds: extensions.blender.org/add-ons

    Under the hood, it uses the image processing libraries @pillow and #OpenEXR.

    If you have ideas to build blender extensions yourself, join Brady Johnston and me at our talk “Extensions are Coming” at the Blender Conference next week, were we will be talking about how to develop Blender extensions. conference.blender.org/2025/pr
    (Recordings will be available as well.)

  7. I just released a new Blender extension for blurring images and scene backgrounds: extensions.blender.org/add-ons

    Under the hood, it uses the image processing libraries @pillow and #OpenEXR.

    If you have ideas to build blender extensions yourself, join Brady Johnston and me at our talk “Extensions are Coming” at the Blender Conference next week, were we will be talking about how to develop Blender extensions. conference.blender.org/2025/pr
    (Recordings will be available as well.)

  8. #OpenEXR best practices
    - Real-Time Playback/Compositing: Use B44/B44A or DWA for faster I/O .
    - CGI/Rendered Content: ZIP (lossless) or PIZ (smaller files) .
    - Texture Maps: ZIP for fast access .
    - Layered EXRs: ZIPS for scanline efficiency .
    - Avoid Lossy Compression for non-color data (e.g., normals, depth). #exr #vfx #rendering #b3d #CGI

  9. #OpenEXR best practices
    - Real-Time Playback/Compositing: Use B44/B44A or DWA for faster I/O .
    - CGI/Rendered Content: ZIP (lossless) or PIZ (smaller files) .
    - Texture Maps: ZIP for fast access .
    - Layered EXRs: ZIPS for scanline efficiency .
    - Avoid Lossy Compression for non-color data (e.g., normals, depth). #exr #vfx #rendering #b3d #CGI

  10. #OpenEXR best practices
    - Real-Time Playback/Compositing: Use B44/B44A or DWA for faster I/O .
    - CGI/Rendered Content: ZIP (lossless) or PIZ (smaller files) .
    - Texture Maps: ZIP for fast access .
    - Layered EXRs: ZIPS for scanline efficiency .
    - Avoid Lossy Compression for non-color data (e.g., normals, depth). #exr #vfx #rendering #b3d #CGI

  11. #OpenEXR best practices
    - Real-Time Playback/Compositing: Use B44/B44A or DWA for faster I/O .
    - CGI/Rendered Content: ZIP (lossless) or PIZ (smaller files) .
    - Texture Maps: ZIP for fast access .
    - Layered EXRs: ZIPS for scanline efficiency .
    - Avoid Lossy Compression for non-color data (e.g., normals, depth). #exr #vfx #rendering #b3d #CGI

  12. #OpenEXR best practices
    - Real-Time Playback/Compositing: Use B44/B44A or DWA for faster I/O .
    - CGI/Rendered Content: ZIP (lossless) or PIZ (smaller files) .
    - Texture Maps: ZIP for fast access .
    - Layered EXRs: ZIPS for scanline efficiency .
    - Avoid Lossy Compression for non-color data (e.g., normals, depth). #exr #vfx #rendering #b3d #CGI

  13. Powiedziałbym, że dla #EasyCLA bardziej pasowałaby nazwa "skomplikowane i zepsute CLA".

    Po tym, jak w końcu udało mi się wysłać wniosek o CLA dla #OpenEXR, firma dalej go nie widziała. Spróbowałem jeszcze raz, i tym razem udało im się zaakceptować. Tyle że EasyCLA dalej twierdziło, że nie jest podpisane.

    Ale już po problemie, bo jakiś przypadkowy typ postanowił wziąć moją łatkę, wraz z oryginalnym opisem zmian, usunąć moje dane osobowe i wysłać ją, przy okazji zamykając moją — a autorzy od razu to przyjęli. Nie, żeby to robiło jakąś szczególną różnicę, bo łatka była trywialna (do tego stopnia, że ta cała bieganina wokół CLA nie miała żadnego sensu), ale i tak niefajnie, jak ktoś kradnie twoją pracę i usuwa autorstwo.

    #WolneOprogramowanie

  14. Powiedziałbym, że dla #EasyCLA bardziej pasowałaby nazwa "skomplikowane i zepsute CLA".

    Po tym, jak w końcu udało mi się wysłać wniosek o CLA dla #OpenEXR, firma dalej go nie widziała. Spróbowałem jeszcze raz, i tym razem udało im się zaakceptować. Tyle że EasyCLA dalej twierdziło, że nie jest podpisane.

    Ale już po problemie, bo jakiś przypadkowy typ postanowił wziąć moją łatkę, wraz z oryginalnym opisem zmian, usunąć moje dane osobowe i wysłać ją, przy okazji zamykając moją — a autorzy od razu to przyjęli. Nie, żeby to robiło jakąś szczególną różnicę, bo łatka była trywialna (do tego stopnia, że ta cała bieganina wokół CLA nie miała żadnego sensu), ale i tak niefajnie, jak ktoś kradnie twoją pracę i usuwa autorstwo.

    #WolneOprogramowanie

  15. Powiedziałbym, że dla #EasyCLA bardziej pasowałaby nazwa "skomplikowane i zepsute CLA".

    Po tym, jak w końcu udało mi się wysłać wniosek o CLA dla #OpenEXR, firma dalej go nie widziała. Spróbowałem jeszcze raz, i tym razem udało im się zaakceptować. Tyle że EasyCLA dalej twierdziło, że nie jest podpisane.

    Ale już po problemie, bo jakiś przypadkowy typ postanowił wziąć moją łatkę, wraz z oryginalnym opisem zmian, usunąć moje dane osobowe i wysłać ją, przy okazji zamykając moją — a autorzy od razu to przyjęli. Nie, żeby to robiło jakąś szczególną różnicę, bo łatka była trywialna (do tego stopnia, że ta cała bieganina wokół CLA nie miała żadnego sensu), ale i tak niefajnie, jak ktoś kradnie twoją pracę i usuwa autorstwo.

    #WolneOprogramowanie

  16. Powiedziałbym, że dla #EasyCLA bardziej pasowałaby nazwa "skomplikowane i zepsute CLA".

    Po tym, jak w końcu udało mi się wysłać wniosek o CLA dla #OpenEXR, firma dalej go nie widziała. Spróbowałem jeszcze raz, i tym razem udało im się zaakceptować. Tyle że EasyCLA dalej twierdziło, że nie jest podpisane.

    Ale już po problemie, bo jakiś przypadkowy typ postanowił wziąć moją łatkę, wraz z oryginalnym opisem zmian, usunąć moje dane osobowe i wysłać ją, przy okazji zamykając moją — a autorzy od razu to przyjęli. Nie, żeby to robiło jakąś szczególną różnicę, bo łatka była trywialna (do tego stopnia, że ta cała bieganina wokół CLA nie miała żadnego sensu), ale i tak niefajnie, jak ktoś kradnie twoją pracę i usuwa autorstwo.

    #WolneOprogramowanie

  17. I dare say a better name for #EasyCLA would be "convoluted and broken CLA".

    Even after I was finally able to submit the CLA for #OpenEXR, the company couldn't find it. After another attempt, they were finally able to approve it. Except that it still claimed I'm unapproved.

    However, that's not a problem anymore, because some random decided to take my patch, up to the commit message, wipe my authorship from it and submit it with a closing tag on my pull request — and upstream gladly merged that. I mean, it was a trivial patch (so trivial the whole CLA business was entirely pointless), so it's not like it matters, but it still feels wrong when people steal your work and remove authorship.

    #FreeSoftware

  18. I dare say a better name for #EasyCLA would be "convoluted and broken CLA".

    Even after I was finally able to submit the CLA for #OpenEXR, the company couldn't find it. After another attempt, they were finally able to approve it. Except that it still claimed I'm unapproved.

    However, that's not a problem anymore, because some random decided to take my patch, up to the commit message, wipe my authorship from it and submit it with a closing tag on my pull request — and upstream gladly merged that. I mean, it was a trivial patch (so trivial the whole CLA business was entirely pointless), so it's not like it matters, but it still feels wrong when people steal your work and remove authorship.

    #FreeSoftware

  19. I dare say a better name for #EasyCLA would be "convoluted and broken CLA".

    Even after I was finally able to submit the CLA for #OpenEXR, the company couldn't find it. After another attempt, they were finally able to approve it. Except that it still claimed I'm unapproved.

    However, that's not a problem anymore, because some random decided to take my patch, up to the commit message, wipe my authorship from it and submit it with a closing tag on my pull request — and upstream gladly merged that. I mean, it was a trivial patch (so trivial the whole CLA business was entirely pointless), so it's not like it matters, but it still feels wrong when people steal your work and remove authorship.

    #FreeSoftware

  20. I dare say a better name for #EasyCLA would be "convoluted and broken CLA".

    Even after I was finally able to submit the CLA for #OpenEXR, the company couldn't find it. After another attempt, they were finally able to approve it. Except that it still claimed I'm unapproved.

    However, that's not a problem anymore, because some random decided to take my patch, up to the commit message, wipe my authorship from it and submit it with a closing tag on my pull request — and upstream gladly merged that. I mean, it was a trivial patch (so trivial the whole CLA business was entirely pointless), so it's not like it matters, but it still feels wrong when people steal your work and remove authorship.

    #FreeSoftware

  21. I dare say a better name for #EasyCLA would be "convoluted and broken CLA".

    Even after I was finally able to submit the CLA for #OpenEXR, the company couldn't find it. After another attempt, they were finally able to approve it. Except that it still claimed I'm unapproved.

    However, that's not a problem anymore, because some random decided to take my patch, up to the commit message, wipe my authorship from it and submit it with a closing tag on my pull request — and upstream gladly merged that. I mean, it was a trivial patch (so trivial the whole CLA business was entirely pointless), so it's not like it matters, but it still feels wrong when people steal your work and remove authorship.

    #FreeSoftware

  22. I released v2.1.0 of my #research oriented #HighDynamicRange image viewer HDRView yesterday. Worked on lots of changes and improvements over the holiday break. Get the deets and binary downloads at the link below.

    #hdr, #graphics, #rendering, #openexr, #cgi, #webgl, #macos, #dearimgui,

    github.com/wkjarosz/hdrview/re

  23. I released v2.1.0 of my #research oriented #HighDynamicRange image viewer HDRView yesterday. Worked on lots of changes and improvements over the holiday break. Get the deets and binary downloads at the link below.

    #hdr, #graphics, #rendering, #openexr, #cgi, #webgl, #macos, #dearimgui,

    github.com/wkjarosz/hdrview/re

  24. I released v2.1.0 of my #research oriented #HighDynamicRange image viewer HDRView yesterday. Worked on lots of changes and improvements over the holiday break. Get the deets and binary downloads at the link below.

    #hdr, #graphics, #rendering, #openexr, #cgi, #webgl, #macos, #dearimgui,

    github.com/wkjarosz/hdrview/re

  25. I released v2.1.0 of my #research oriented #HighDynamicRange image viewer HDRView yesterday. Worked on lots of changes and improvements over the holiday break. Get the deets and binary downloads at the link below.

    #hdr, #graphics, #rendering, #openexr, #cgi, #webgl, #macos, #dearimgui,

    github.com/wkjarosz/hdrview/re

  26. I released v2.1.0 of my #research oriented #HighDynamicRange image viewer HDRView yesterday. Worked on lots of changes and improvements over the holiday break. Get the deets and binary downloads at the link below.

    #hdr, #graphics, #rendering, #openexr, #cgi, #webgl, #macos, #dearimgui,

    github.com/wkjarosz/hdrview/re

  27. HDRView v2.0 is out!

    Release notes and Mac and Windows binaries here: github.com/wkjarosz/hdrview/re

    Also runs on Linux (no binaries yet) and directly in your browser, even on iPhone/iPad! (just go to wkjarosz.github.io/hdrview/).

    #HDR #OpenEXR #VFX #rendering

  28. HDRView v2.0 is out!

    Release notes and Mac and Windows binaries here: github.com/wkjarosz/hdrview/re

    Also runs on Linux (no binaries yet) and directly in your browser, even on iPhone/iPad! (just go to wkjarosz.github.io/hdrview/).

    #HDR #OpenEXR #VFX #rendering

  29. HDRView v2.0 is out!

    Release notes and Mac and Windows binaries here: github.com/wkjarosz/hdrview/re

    Also runs on Linux (no binaries yet) and directly in your browser, even on iPhone/iPad! (just go to wkjarosz.github.io/hdrview/).

    #HDR #OpenEXR #VFX #rendering

  30. HDRView v2.0 is out!

    Release notes and Mac and Windows binaries here: github.com/wkjarosz/hdrview/re

    Also runs on Linux (no binaries yet) and directly in your browser, even on iPhone/iPad! (just go to wkjarosz.github.io/hdrview/).

    #HDR #OpenEXR #VFX #rendering

  31. HDRView v2.0 is out!

    Release notes and Mac and Windows binaries here: github.com/wkjarosz/hdrview/re

    Also runs on Linux (no binaries yet) and directly in your browser, even on iPhone/iPad! (just go to wkjarosz.github.io/hdrview/).

    #HDR #OpenEXR #VFX #rendering

  32. Need to inspect an (#HDR / #OpenEXR) image on an iPad, iPhone, or a computer without a proper image viewer? HDRView’s latest beta seemingly now works in those cases. Just go to:

    wkjarosz.github.io/hdrview/

    And creating a home screen bookmark on iOS makes it almost feel like a real app.

  33. Need to inspect an (#HDR / #OpenEXR) image on an iPad, iPhone, or a computer without a proper image viewer? HDRView’s latest beta seemingly now works in those cases. Just go to:

    wkjarosz.github.io/hdrview/

    And creating a home screen bookmark on iOS makes it almost feel like a real app.

  34. Need to inspect an (#HDR / #OpenEXR) image on an iPad, iPhone, or a computer without a proper image viewer? HDRView’s latest beta seemingly now works in those cases. Just go to:

    wkjarosz.github.io/hdrview/

    And creating a home screen bookmark on iOS makes it almost feel like a real app.

  35. Need to inspect an (#HDR / #OpenEXR) image on an iPad, iPhone, or a computer without a proper image viewer? HDRView’s latest beta seemingly now works in those cases. Just go to:

    wkjarosz.github.io/hdrview/

    And creating a home screen bookmark on iOS makes it almost feel like a real app.

  36. #BSI WID-SEC-2024-3336: [NEU] [hoch] #Red #Hat #Enterprise #Linux (#OpenEXR): Schwachstelle ermöglicht Manipulation von Dateien

    Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux ausnutzen, um Dateien zu manipulieren.

    wid.cert-bund.de/portal/wid/se

  37. #BSI WID-SEC-2024-3336: [NEU] [hoch] #Red #Hat #Enterprise #Linux (#OpenEXR): Schwachstelle ermöglicht Manipulation von Dateien

    Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux ausnutzen, um Dateien zu manipulieren.

    wid.cert-bund.de/portal/wid/se

  38. #BSI WID-SEC-2024-3336: [NEU] [hoch] #Red #Hat #Enterprise #Linux (#OpenEXR): Schwachstelle ermöglicht Manipulation von Dateien

    Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux ausnutzen, um Dateien zu manipulieren.

    wid.cert-bund.de/portal/wid/se