I am all in for porting to whole Hugin program. Den fre 23 feb. 2024 11:29'kfj' via hugin and other free panoramic software <[email protected]> skrev:
> > > On Friday, February 23, 2024 at 10:54:38 AM UTC+1 [email protected] > wrote: > > This looks like something that could be #ifdef'd so it can be a Hugin > build option. > > > This is roughly what I am aiming at. My call signatures are more complex, > because the OIIO code does not interface with vigra data containers > directly but takes explicit separate stride arguments. But this could be > hidden with more go-between-code - as stated, I wanted a quick > proof-of-concept, mainly to see if I could get the entire toolchain set up > to work from a bunch of RAW files all the way to a stitched panorama. If > there is interest on the hugin side to take this further, I'm willing to > code some more and make it easy for hugin to try this out for the hugin > code base by supplying import functions with adapted signature. > > Though the UI would need some changes to allow heic files in the file > picker etc > > > I also had the UI issue when switching to use OIIO in lux. My old code > offered a file-select with common image file extensions, but this became > impractical with the large number of image file formats OIIO supports, so I > now simply offer all files for opening and silently ignore those files in > the selection which don't check out as OIIO-compatible. OIIO works like > vigraimpex: it looks into the files and opens them with the appropriate > plugin, no matter what the extension is. I wrote a replacement for vígra's > isImage as well which helps with figuring out whether a file can be used as > image input or not, and I could add that to the oiio_fileio repo. > > If we could get it to the point where all it would take is to replace the > type of the info structure and the name of the import routines, making it a > compile option should work out, and the new functionality would become > available throughout the hugin tool chain. hugin does try and open, e.g., > panoramas with .CR2 files, but fails miserably because libvigraimpex > doesn't understand them properly - I think libvigraimpex interprets them as > TIFFs and it all comes out wrong. > > -- > A list of frequently asked questions is available at: > http://wiki.panotools.org/Hugin_FAQ > --- > You received this message because you are subscribed to the Google Groups > "hugin and other free panoramic software" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/hugin-ptx/bed876ff-daaa-4ab6-bd6c-b2a2b2456894n%40googlegroups.com > <https://groups.google.com/d/msgid/hugin-ptx/bed876ff-daaa-4ab6-bd6c-b2a2b2456894n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CAHk3tqgqDWuQBWh0%2BAv9rSbJ6y2YFzR-qN2k1aJ3%2BnnTTbCfqA%40mail.gmail.com.
