vuescan, ls5000, it8 calibration -- all goes red

[Norbert Preining]

Hi!

I am new to the business and tried to make an icc profile with vuescan:
These are the steps:
* get an it8 target from Wolf Faust for Fuji Provia slide film (I am
using Provia)
* copy the file F020430S.txt from the CDROM to my homedir scanner.it8
(using linux)
* start vuescan
* load default options
* put in the target
* input|scan task = profile scanner
* preview
* rotate left and adjust the grid
* Menu->Profile->Profile Scanner

What happens is that the file scanner.icc is written, and the image
turns red (like negative).

If I scan any other image, it also looks red, like `night view'.

Does anybody have an idea how this could happen? What I did wrong.

Thanks for any suggestion and best wishes

Norbert

 

[Markus Plail]

I am new to the business and tried to make an icc profile with vuescan:
These are the steps:
* get an it8 target from Wolf Faust for Fuji Provia slide film (I am
using Provia)
* copy the file F020430S.txt from the CDROM to my homedir scanner.it8
(using linux)

This has been reported several times here. ICC profiling doesn't work
with the linux version. You could RAW scan and then use wine with the
windows version to get the ICC profile. After that you can use that
profile with the linux version.

Ed Hamrick didn't yet comment on that issue here, so perhaps you should
report that bug directly to him as describes on his homepage.

regards
Markus

 

[Ed Hamrick]

This has been reported several times here. ICC profiling doesn't work
with the linux version. You could RAW scan and then use wine with the
windows version to get the ICC profile. After that you can use that
profile with the linux version.

It's probably a CR/LF problem with the .IT8 file. Make sure
it's a normal Linux text file that can be read with fopen(file,"rt")
and fgets()

Regards,
Ed Hamrick

 

[Markus Plail]

It's probably a CR/LF problem with the .IT8 file. Make sure it's a
normal Linux text file that can be read with fopen(file,"rt") and
fgets()

plail@plailis:/daten/wolf$ file F020430S.*
F020430S.txt: ASCII text, with CRLF line terminators
F020430S.unix: ASCII text
plail@plailis:/daten/wolf$

It doesn't work with either of those versions. Would it be normal that
the same file works in Windows and doesn't in Linux?
That's the case here.

regards
Markus

 

[Ed Hamrick]

plail@plailis:/daten/wolf$ file F020430S.*
F020430S.txt: ASCII text, with CRLF line terminators
F020430S.unix: ASCII text
plail@plailis:/daten/wolf$

It doesn't work with either of those versions. Would it be normal that
the same file works in Windows and doesn't in Linux?
That's the case here.

These links don't work (they aren't URL's). Could you e-mail
me the text file you're using?

Yes, it would be normal that a file with CR/LF endings, if sent
to Linux without mapping to LF endings, would have problems.

Regards,
Ed Hamrick

 

[Markus Plail]

What happens is that the file scanner.icc is written, and the image
turns red (like negative).

It's a locale problem. Set LC_ALL to C before you start vuescan and it
should work. With locale set to C you can also type decimal values in
the different fields and they will actually work.
It doesn't when the locale is set to something that uses , as decimal
delimiter.

Servus
Markus

 

[Wolf Faust]

It's probably a CR/LF problem with the .IT8 file. Make sure
it's a normal Linux text file that can be read with fopen(file,"rt")
and fgets()

This would be rather strange and would be a bug in the profiling
software as the IT 8 and CGATS.5 standards cleary do allow CR/LF in
the reference file and most manufacturers do shipp their files with
CR/LF. The profiler should simply skip/ignore CR and LF.

 

[Markus Plail]

This would be rather strange and would be a bug in the profiling
software as the IT 8 and CGATS.5 standards cleary do allow CR/LF in
the reference file and most manufacturers do shipp their files with
CR/LF. The profiler should simply skip/ignore CR and LF.

The line endings were not the problem. It was the decimal
separator. Under certain locales vuescan expected ',', but the IT8 files
had '.' in them.

regards
Markus