I'm getting multiple reports from people indicating that while Luminar Neo supports their camera model, the program does not recognize raw files shot in IR. I had a similar problem when making a video on Luminar 4 a few years ago. ruclips.net/video/rxc0vwAplJE/видео.html At the time, it was unclear if this was an issue where the camera raw files from my Fujifilm X-T20 were not supported or were specific to IR. It appeared resolved in later versions since those files from the Fujifilm X-T20 are now recognized as raw. However, multiple people are now having the same issue. Be sure to test the trial version of Luminar with your raw files before purchasing. When editing your raw file, look for the blue "Raw" tag next to the Develop module name. If you don't see it, your camera model is unsupported or Luminar cannot recognize IR images shot in raw. You can get a list of Luminar-supported cameras here: userguide.skylum.com/hc/en-us/articles/11545807976210-Supported-File-Types-and-Cameras
As an additional note to this issue- in catalog the image is correctly identified as a raw image. However a RAW image from my Nikon Z5 (not converted to IR) is correctly identified in develop. I’ve submitted an image to Skylum support
Thank you so much, Rob. As a Luminar Neo user I find your reeview and tips extremely useful. Though this editor is not great for infrared photography, I think it is great to get started. Your luts seem like a good option. Once again, thank you.
Thanks for that Rob. I would not have thought of using Luminar Neo, but from your table it looks like one of the "better" alternatives. I have dedicated On1 to IR processing instead. May try Luminar as well, as I own it (and have an older version too).
@@philmtx3fr Hello, I do have an A74 for regular shooting. I had an older Canon 7D I was going to convert, but I wanted to go mirrorless for all of its advantages. 👍🏼
Thanks, very helpful. Have you ever tried working with Radiant Photo and IR? I use it with my non-IR photos for creating a good basis for further edits. But I've been unsuccessful using it for IR photos. Normally I have to do the channel swap in On1 first. I love Neo for certain tasks, but it it lack too many basic functions and often make changes that is our of our control.
In the Develop module, do you see the blue RAW indicator next to the module name? It could also depend on your camera model. Ensure that your camera mode is supported. userguide.skylum.com/hc/en-us/articles/11545807976210-Supported-File-Types-and-Cameras
Thanks Rob interesting Video, I have a R72 Hoya and have not been successful and converting my images from a Canon Rebel T 6 with the Infa Red Filter . Think you video might help assuming the camera is compatible with the filter. Look forward to seeing some of your other videos. Once again thanks
I really appreciate the effort you put into this. I like Neo, but I use ON1 or PS for IR. I tried to add your method in Neo but my version of 1.20.1 does not give me the option of adding a camera profile in either Develop or Develop within Edits. The first option I see is Light. What am I missing? I can go ahead and add LUTs, because the ones I built already have the profile built in. Yours, too, I believe.
Ensure that you are seeing the "Raw" next to the Develop module name. This confirms that you are viewing a raw file and the raw files from that camera are supported by Luminar.
@@robshea Thank you for getting back to me. I played with it. It turns out for some reason, I only see the Develop-RAW option when I open a DNG file. If I open an Olympus ORF RAW file. I do not see it. I even tried opening one where there was no associated XMP file. Is this something I need to refer to Skylum support? I have no problem with the same camera profile in PS-ACR.
@@FastidiousOne That is very interesting. I wonder if the difference between raw and DNG is the key. I would certainly share your findings with Skylum support.
This is what I got back from Skylum support: "Kindly note that Luminar Neo supports Olympus E-M1 II only partially. It is compatible with lossless compression files. So, I can assume that you have high resolution, due to this, the software behaves unpredictably."
With regard to the question about Nero not recognising RAW IR files. I have a Nikon D90 with a 590nm internal filter. Catalog recognises it as a RAW image whilst Develop module doesn’t. I contacted Skylum who advised the following I have received a reply from our engineering team. Please note that the issue lies within the shots made in IR format due to the temperature limitations for the RAW format. For now, our app has a limitation from 2000 kelvins to 50000 kelvins. In this specter, the RAW files will be recognized. I have also forwarded your request as a suggestion for future expand of the supported temperature. I’m certain I used neo before with my camera without issue. I don’t know about other photo editors but I know Affinity doesn’t have this limitation. Is there a way to change the temperature in camera to get around this? Bit disappointing
Most cameras have a limited color temperature range, which does not support infrared color temperatures. Here are the ways that you can correct temperature with different raw editors. - Some raw editors allow you to use a custom profile to lower the color temperature range. This includes raw editors such as Lightroom, Photoshop Camera Raw, DxO PhotoLab, Exposure X, and Luminar Neo. See www.robsheaphotography.com/infrared-profile-pack/#editors - Some raw editors allow for a wide range of color temperatures below 2,000K. Editors such as darktable, RawTherapee, and Affinity. - Some raw editors allow for a blue/yellow adjustment instead of color temperature, such as ON1. - You can also use a Tone Curve to correct white balance. ruclips.net/video/GwcsFH-s61Y/видео.html
@ Thanks Rob. The link you supplied is helpful, but I’m not sure how to take the next step. Do I load a profile into Adobe’s DNG profile editor then bring in the RAW file to output a .dng file? My understanding with Neo is that you import the profile via Develop Raw which I don’t have access to because of the temperature issue?
@@tomgardner9963 This is the major downside of this Luminar issue. If Luminar recognized the image as raw and then just set the Temperature at the bottom of the scale, as other editors do, you'd be able to load a profile to correct the temperature. Since it blocks this, the only other workaround in Luminar is manually defining a channel-by-channel tone curve for each image.
here is the answer, not sure why you can use it and I cannot. I'm using Kohlari filters on a full spectrum conversion: I have received a reply from our engineering team. Please note that the issue lies within the shots made in IR format due to the temperature limitations for the RAW format
hello i would like to know if i buy your infrared book as an ebook, can i translate it into french? by translator system i am already advanced in infrared but i am really interested and passionate
![[#2024MAMA] G-DRAGON - 무제(Untitled, 2014)+POWER+HOME SWEET HOME+뱅뱅뱅+FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/Ox29z5Nf1Uk/mqdefault.jpg)
I'm getting multiple reports from people indicating that while Luminar Neo supports their camera model, the program does not recognize raw files shot in IR. I had a similar problem when making a video on Luminar 4 a few years ago. ruclips.net/video/rxc0vwAplJE/видео.html At the time, it was unclear if this was an issue where the camera raw files from my Fujifilm X-T20 were not supported or were specific to IR. It appeared resolved in later versions since those files from the Fujifilm X-T20 are now recognized as raw. However, multiple people are now having the same issue.
Be sure to test the trial version of Luminar with your raw files before purchasing. When editing your raw file, look for the blue "Raw" tag next to the Develop module name. If you don't see it, your camera model is unsupported or Luminar cannot recognize IR images shot in raw.
You can get a list of Luminar-supported cameras here: userguide.skylum.com/hc/en-us/articles/11545807976210-Supported-File-Types-and-Cameras
I have the same issue. I have a Nikon .NEF
As an additional note to this issue- in catalog the image is correctly identified as a raw image. However a RAW image from my Nikon Z5 (not converted to IR) is correctly identified in develop. I’ve submitted an image to Skylum support
Thank you so much, Rob.
As a Luminar Neo user I find your reeview and tips extremely useful. Though this editor is not great for infrared photography, I think it is great to get started. Your luts seem like a good option. Once again, thank you.
Very interesting Rob ! And a big thx to not limiting you to expensive Adobe SW :). Luminar seems to be good too for infrared. I will try this !
You can see all of the raw editor options here: 590.red/raw
@@robshea thx
thats cool, works great with my new "old" @5000 IR. thank you
Thanks for that Rob. I would not have thought of using Luminar Neo, but from your table it looks like one of the "better" alternatives. I have dedicated On1 to IR processing instead. May try Luminar as well, as I own it (and have an older version too).
You inspired me to get my a7 III converted! Thank you Rob for so much solid information.
Hum I think it s better to convert a more low end camera or an old dslr… except if you also have in your bag an A74 and an A7r5 :)))
@@philmtx3fr Hello, I do have an A74 for regular shooting. I had an older Canon 7D I was going to convert, but I wanted to go mirrorless for all of its advantages. 👍🏼
@@dallasroberts3206 in this case I may understand :). But converting a camera is a potential risky task so I prefer to do it on camera under 400$.
You have an impressive voice 👍
Thanks, very helpful. Have you ever tried working with Radiant Photo and IR? I use it with my non-IR photos for creating a good basis for further edits. But I've been unsuccessful using it for IR photos. Normally I have to do the channel swap in On1 first. I love Neo for certain tasks, but it it lack too many basic functions and often make changes that is our of our control.
Not yet! I will take a look at it.
Yes to both
In the Develop module, do you see the blue RAW indicator next to the module name? It could also depend on your camera model. Ensure that your camera mode is supported. userguide.skylum.com/hc/en-us/articles/11545807976210-Supported-File-Types-and-Cameras
Thanks fo rhtis!
Thanks Rob interesting Video, I have a R72 Hoya and have not been successful and converting my images from a Canon Rebel T 6 with the Infa Red Filter . Think you video might help assuming the camera is compatible with the filter. Look forward to seeing some of your other videos. Once again thanks
That camera should be fine with an R72 filter.
I really appreciate the effort you put into this. I like Neo, but I use ON1 or PS for IR. I tried to add your method in Neo but my version of 1.20.1 does not give me the option of adding a camera profile in either Develop or Develop within Edits. The first option I see is Light. What am I missing? I can go ahead and add LUTs, because the ones I built already have the profile built in. Yours, too, I believe.
Ensure that you are seeing the "Raw" next to the Develop module name. This confirms that you are viewing a raw file and the raw files from that camera are supported by Luminar.
@@robshea Thank you for getting back to me. I played with it. It turns out for some reason, I only see the Develop-RAW option when I open a DNG file. If I open an Olympus ORF RAW file. I do not see it. I even tried opening one where there was no associated XMP file. Is this something I need to refer to Skylum support? I have no problem with the same camera profile in PS-ACR.
@@FastidiousOne That is very interesting. I wonder if the difference between raw and DNG is the key. I would certainly share your findings with Skylum support.
This is what I got back from Skylum support: "Kindly note that Luminar Neo supports Olympus E-M1 II only partially. It is compatible with lossless compression files. So, I can assume that you have high resolution, due to this, the software behaves unpredictably."
@@FastidiousOne ☹ Good to know, but frustrating.
Hi I do not see the camera profile option in the develop lumina Neo option
Ensure that you are using the latest version of Luminar Neo and that you are viewing a raw file.
With regard to the question about Nero not recognising RAW IR files. I have a Nikon D90 with a 590nm internal filter. Catalog recognises it as a RAW image whilst Develop module doesn’t. I contacted Skylum who advised the following
I have received a reply from our engineering team. Please note that the issue lies within the shots made in IR format due to the temperature limitations for the RAW format. For now, our app has a limitation from 2000 kelvins to 50000 kelvins. In this specter, the RAW files will be recognized.
I have also forwarded your request as a suggestion for future expand of the supported temperature.
I’m certain I used neo before with my camera without issue. I don’t know about other photo editors but I know Affinity doesn’t have this limitation. Is there a way to change the temperature in camera to get around this?
Bit disappointing
Most cameras have a limited color temperature range, which does not support infrared color temperatures. Here are the ways that you can correct temperature with different raw editors.
- Some raw editors allow you to use a custom profile to lower the color temperature range. This includes raw editors such as Lightroom, Photoshop Camera Raw, DxO PhotoLab, Exposure X, and Luminar Neo. See www.robsheaphotography.com/infrared-profile-pack/#editors
- Some raw editors allow for a wide range of color temperatures below 2,000K. Editors such as darktable, RawTherapee, and Affinity.
- Some raw editors allow for a blue/yellow adjustment instead of color temperature, such as ON1.
- You can also use a Tone Curve to correct white balance. ruclips.net/video/GwcsFH-s61Y/видео.html
@ Thanks Rob. The link you supplied is helpful, but I’m not sure how to take the next step. Do I load a profile into Adobe’s DNG profile editor then bring in the RAW file to output a .dng file? My understanding with Neo is that you import the profile via Develop Raw which I don’t have access to because of the temperature issue?
@@tomgardner9963 This is the major downside of this Luminar issue. If Luminar recognized the image as raw and then just set the Temperature at the bottom of the scale, as other editors do, you'd be able to load a profile to correct the temperature. Since it blocks this, the only other workaround in Luminar is manually defining a channel-by-channel tone curve for each image.
Thanks - that's a shame. Thanks for the advice
here is the answer, not sure why you can use it and I cannot. I'm using Kohlari filters on a full spectrum conversion:
I have received a reply from our engineering team. Please note that the issue lies within the shots made in IR format due to the temperature limitations for the RAW format
🤔
hello
i would like to know if i buy your infrared book as an ebook, can i translate it into french? by translator system
i am already advanced in infrared but i am really interested and passionate
You are welcome to translate for your personal use.
@@robshea yes but can it work or not? because unfortunately often the applications do not work .....
@@davidmereghetti9053 Unfortunately, I don't have a way to validate the quality of a translation without hiring a professional translation service.
v 1.20.1 18066
Next step would be the reach out to Luminar's support.