LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview libtiff implementation

You need to use the DLL with the correct bitness (32 or 64) for your LabVIEW version. A 32-bt application only can load DLLs compiled for 32-bit, and the 64-bit application only can load DLLs compiled for 64-bit.

Rolf Kalbermatter
Averna BV
0 Kudos
Message 101 of 106
(322 Views)

Hi Suhail,

 

please have a look at this thread here

 

https://forums.ni.com/t5/LabVIEW/Multipage-TIF-VIs/m-p/4046309/highlight/true?profile.language=en#M1...

 

I wrote a collection of VIs for saving multipage TIFF which don't rely on an external DLL, just Labview.

 

Cheers,

 

Nico

0 Kudos
Message 102 of 106
(319 Views)

Hello Nico,

 

I've just read the whole thread, and not yet tried anything, but it looks a huge work, thanks !

At the beginning you were talking about adding the ability to write/read custom tags (which I'm interested in) and you said that it was tricky to implement (and I trust you), did you abandon the idea?

 

Should I stop asking you questions on this thread but more on your "ALL-LabView-no-external-library VIs"?

 

cheers

guigui

0 Kudos
Message 103 of 106
(224 Views)

Hi guigui,

 

thanks for your message: I looked into writing custom tags but didn't find an easy solution with libtiff. Moreover, I am now using a labview only solution which does not rely on any external library, and I think this will make reading/writing custom tags even harder!

However, you could give a look at my code and see whether you find a way of adding the info you need into the file. Good luck and let me know!

 

Best,

 

Nico

0 Kudos
Message 104 of 106
(221 Views)

thank you for your answer Nico,

I'll try to have a look, but honestly I don't feel expert enough to succeed...

I'll let you know.

guigui

0 Kudos
Message 105 of 106
(207 Views)

Why would be reading custom tags harder? Of course you can’t provide ready made VIs that provide the user with the fully parsed data type for tags you don’t know but you certainly must have a low level function that actually locates tags in the binary stream to pass the offset and length to the actual parse function that returns then the converted data. Create a “conversion” VI that looks for the tag in the stream and returns the content as binary stream (personally I think a byte array is the most logical choice here but that requires the user to convert to string if he wants to use Unflatten or Typecast. So wish NI had made the Unflatten and Typecast accept byte arrays as an alternative to string inputs many versions ago! It would be a no brainer to do and cost zero time in terms of development time. Bonus points for allowing the Flatten to have a popup selection to choose between generating either of the two and default to byte arrays!)

The user then has to parse this custom tag data himself but that’s the nature of custom tags. 😀

 

Rolf Kalbermatter
Averna BV
0 Kudos
Message 106 of 106
(201 Views)