Capture One with Samsung NX10 raw files
Hello Capture One,
I see that Capture One 6.3 release bring some enhancement in Samsung NX10 support. That's nice because i have just bought NX10 and i can see Capture One really work fine with srw files.
But there still a bug: when i use NX10 with lens mount adater (PK-NX for exemple) and Pentax lens (or other) Capture One refuse to load files (raw and even jpeg). I thing that become from missing informations in Exif file and it is little annoying.
Thanks for all.
Exemple of message when i try to load NX10 files:
Error: Input string was not in a correct format. at System.Number.ParseSingle(String value, NumberStyles options, NumberFormatInfo numfmt)
at System.Single.Parse(String s, IFormatProvider provider)
at P1.C1.Core.ImagePersistency.GetVariantDefaults(Image image, CustomDefaults customDefaults, FilmCurveLoader filmCurveLoader, ColorProfileLoader colorProfileLoader)
at P1.C1.Core.ImagePersistency.CreateImageSettings(Image image, CustomDefaults customDefaults, FilmCurveLoader filmCurveLoader, ColorProfileLoader colorProfileLoader)
at P1.C1.Core.ImagePersistency.LoadImageSettings(Image image, CustomDefaults customDefaults, Boolean deleteOldSettings, FilmCurveLoader filmCurveLoader, ColorProfileLoader colorProfileLoader, List`1 errorList, Boolean readOnly)
at P1.C1.Program.DefaultLoadImageSettingsCallback(Image img)
at P1.C1.Core.Image.GetSettingsOverride()
at P1.C1.Core.ProxyPropertySet.LoadSettings()
at P1.C1.Components.CollectionFiller.insertFileInternal(FolderCollection& collection, String& path, IFileInfo& file, IDirectoryInfo& settingsDirCache, IDirectoryInfo& packageSettingsDirCache, IDirectoryInfo& proxyDirectoryNodeCopy, ImageSettingsLoaderCallback& loadSettingsCallback, Boolean CaptureMode, CaptureSettingsCopier settingsCopier)
I see that Capture One 6.3 release bring some enhancement in Samsung NX10 support. That's nice because i have just bought NX10 and i can see Capture One really work fine with srw files.
But there still a bug: when i use NX10 with lens mount adater (PK-NX for exemple) and Pentax lens (or other) Capture One refuse to load files (raw and even jpeg). I thing that become from missing informations in Exif file and it is little annoying.
Thanks for all.
Exemple of message when i try to load NX10 files:
Error: Input string was not in a correct format. at System.Number.ParseSingle(String value, NumberStyles options, NumberFormatInfo numfmt)
at System.Single.Parse(String s, IFormatProvider provider)
at P1.C1.Core.ImagePersistency.GetVariantDefaults(Image image, CustomDefaults customDefaults, FilmCurveLoader filmCurveLoader, ColorProfileLoader colorProfileLoader)
at P1.C1.Core.ImagePersistency.CreateImageSettings(Image image, CustomDefaults customDefaults, FilmCurveLoader filmCurveLoader, ColorProfileLoader colorProfileLoader)
at P1.C1.Core.ImagePersistency.LoadImageSettings(Image image, CustomDefaults customDefaults, Boolean deleteOldSettings, FilmCurveLoader filmCurveLoader, ColorProfileLoader colorProfileLoader, List`1 errorList, Boolean readOnly)
at P1.C1.Program.DefaultLoadImageSettingsCallback(Image img)
at P1.C1.Core.Image.GetSettingsOverride()
at P1.C1.Core.ProxyPropertySet.LoadSettings()
at P1.C1.Components.CollectionFiller.insertFileInternal(FolderCollection& collection, String& path, IFileInfo& file, IDirectoryInfo& settingsDirCache, IDirectoryInfo& packageSettingsDirCache, IDirectoryInfo& proxyDirectoryNodeCopy, ImageSettingsLoaderCallback& loadSettingsCallback, Boolean CaptureMode, CaptureSettingsCopier settingsCopier)
0
-
I suggest you open a support case with Phase One and provide such a NX10 srw file so they can investigate.
http://www.phaseone.com/supportmain.aspx0 -
I do have exactly the same issue when using the NX10 with OM adapted lenses, so I assume that to be a code issue of P1.
Rgds, Oliver0 -
Just though I would mention that I was experiencing the same issue with the NX100 and raised a call with support. The problem has been acknowledged and expected to be resolved in an update.
Neil0 -
Many thanks for all.
So wait and see...
Hope the next release will resolved this problem.0
Post is closed for comments.
Comments
4 comments