2013-06-14, 14:55
**Historical topic about RAW-files for reference**
While using RAW files in XBMC isn't a large feature but many photographers keep their RAW files in the same directory as the .JPEG equivalant. Why?
So RAW-files are listed as supported but they are surrounded with troubles. First, like you can see in the WIKI, it's not 100% clear which formats are supported.
Supported Vendor specific RAW extensions:
*.orf (Olympus), *.crw(Canon), *.ARW (Sony), *.NEF (Nikon), *.dcr (Kodak), *.raw, *.cr2(Canon), *.EEF (Epson), *.mrw (Minolta), *.pef (Pentax), *.raf (Fuji), *.srf (Sony), *.x3f (Sigma), *.rc2.
Then there also is *.DNG (Adobe prop. RAW format adopted as industry standard).
To better support all those vendor specific RAW extensions, XBMC (Wiso) already made the imagefactory to easily integrate other image libraries.
Since a lot of development happened around pictures like the imagefactory, the new jpeg-encoding and Ulion's rewrite (and in XBMC in generel like threading, caching, etc) is not strange that some regression pops up.
Some bugs related with raw-support:
http://trac.xbmc.org/ticket/14419
http://trac.xbmc.org/ticket/14184
http://trac.xbmc.org/ticket/13974
http://forum.xbmc.org/showthread.php?tid=157742
NEF problems: http://forum.xbmc.org/showthread.php?tid=140941
http://forum.xbmc.org/showthread.php?tid=13484&page=7
*.ARW has 2 bugs.
1> Caching .ARW over network: jpegparser is unable to load .arw files and then the threading crashes.
2> Displaying .ARW: Texture manager can not handle .ARW
*.dng fails creating thumbs
1> http://trac.xbmc.org/ticket/13947
(and wrongly created on .rc2 (http://trac.xbmc.org/ticket/14375))
http://forum.xbmc.org/showthread.php?tid...pid1499149
Making pictures threat-safe solved some problem with corrupted thumbs. To fix remaining bugs could be simply updating libdcr 8.91 (which ships with current CXimage 6.x) to the newest version (I've seen 8.93 in CxImage 7.x and 8.91 by the creator of libdcr). But the more final solution would be using the image factory to use libRAW and to use Ffmpeg's tag loader to do all CXimage's work.
Edit: This is confirmed with current nightlies.
While using RAW files in XBMC isn't a large feature but many photographers keep their RAW files in the same directory as the .JPEG equivalant. Why?
Quote:The advantage of the RAW format is that, like the old film negative, it contains the truest record of the data captured by the camera’s image sensor. That data can be processed to suit what the photographer wants as the final image. In traditional photography, this is equivalent to processing the negative into the final positive print
So RAW-files are listed as supported but they are surrounded with troubles. First, like you can see in the WIKI, it's not 100% clear which formats are supported.
Supported Vendor specific RAW extensions:
*.orf (Olympus), *.crw(Canon), *.ARW (Sony), *.NEF (Nikon), *.dcr (Kodak), *.raw, *.cr2(Canon), *.EEF (Epson), *.mrw (Minolta), *.pef (Pentax), *.raf (Fuji), *.srf (Sony), *.x3f (Sigma), *.rc2.
Then there also is *.DNG (Adobe prop. RAW format adopted as industry standard).
To better support all those vendor specific RAW extensions, XBMC (Wiso) already made the imagefactory to easily integrate other image libraries.
Since a lot of development happened around pictures like the imagefactory, the new jpeg-encoding and Ulion's rewrite (and in XBMC in generel like threading, caching, etc) is not strange that some regression pops up.
Some bugs related with raw-support:
http://trac.xbmc.org/ticket/14419
http://trac.xbmc.org/ticket/14184
http://trac.xbmc.org/ticket/13974
http://forum.xbmc.org/showthread.php?tid=157742
NEF problems: http://forum.xbmc.org/showthread.php?tid=140941
http://forum.xbmc.org/showthread.php?tid=13484&page=7
*.ARW has 2 bugs.
1> Caching .ARW over network: jpegparser is unable to load .arw files and then the threading crashes.
2> Displaying .ARW: Texture manager can not handle .ARW
*.dng fails creating thumbs
1> http://trac.xbmc.org/ticket/13947
(and wrongly created on .rc2 (http://trac.xbmc.org/ticket/14375))
http://forum.xbmc.org/showthread.php?tid...pid1499149
Making pictures threat-safe solved some problem with corrupted thumbs. To fix remaining bugs could be simply updating libdcr 8.91 (which ships with current CXimage 6.x) to the newest version (I've seen 8.93 in CxImage 7.x and 8.91 by the creator of libdcr). But the more final solution would be using the image factory to use libRAW and to use Ffmpeg's tag loader to do all CXimage's work.
Edit: This is confirmed with current nightlies.