lcms-user Mailing List for Little cms color engine (Page 7)
An ICC-based CMM for color management
Brought to you by:
mm2
Menu
▾
▴
lcms-user — For users of the little cms library
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(15) |
Jun
(24) |
Jul
(9) |
Aug
(14) |
Sep
|
Oct
(12) |
Nov
(17) |
Dec
(31) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(34) |
Feb
(7) |
Mar
(7) |
Apr
(16) |
May
(4) |
Jun
(14) |
Jul
(34) |
Aug
(54) |
Sep
(11) |
Oct
(25) |
Nov
(1) |
Dec
(6) |
| 2003 |
Jan
(27) |
Feb
(54) |
Mar
(23) |
Apr
(68) |
May
(82) |
Jun
(36) |
Jul
(45) |
Aug
(45) |
Sep
(49) |
Oct
(30) |
Nov
(65) |
Dec
(23) |
| 2004 |
Jan
(52) |
Feb
(52) |
Mar
(35) |
Apr
(38) |
May
(93) |
Jun
(22) |
Jul
(51) |
Aug
(50) |
Sep
(73) |
Oct
(28) |
Nov
(30) |
Dec
(51) |
| 2005 |
Jan
(22) |
Feb
(79) |
Mar
(38) |
Apr
(51) |
May
(95) |
Jun
(60) |
Jul
(56) |
Aug
(49) |
Sep
(22) |
Oct
(43) |
Nov
(15) |
Dec
(40) |
| 2006 |
Jan
(51) |
Feb
(31) |
Mar
(37) |
Apr
(25) |
May
(9) |
Jun
(13) |
Jul
(17) |
Aug
(66) |
Sep
(7) |
Oct
(12) |
Nov
(14) |
Dec
(31) |
| 2007 |
Jan
(18) |
Feb
(9) |
Mar
(22) |
Apr
(18) |
May
(5) |
Jun
(25) |
Jul
(2) |
Aug
(15) |
Sep
(12) |
Oct
(40) |
Nov
(10) |
Dec
(23) |
| 2008 |
Jan
(21) |
Feb
(56) |
Mar
(12) |
Apr
(23) |
May
(47) |
Jun
(75) |
Jul
(24) |
Aug
(2) |
Sep
(7) |
Oct
(26) |
Nov
(20) |
Dec
(16) |
| 2009 |
Jan
(14) |
Feb
(1) |
Mar
(29) |
Apr
(54) |
May
(18) |
Jun
(16) |
Jul
(5) |
Aug
(3) |
Sep
(38) |
Oct
(6) |
Nov
(25) |
Dec
(28) |
| 2010 |
Jan
(11) |
Feb
(26) |
Mar
(2) |
Apr
(10) |
May
(45) |
Jun
(94) |
Jul
(11) |
Aug
(32) |
Sep
(18) |
Oct
(37) |
Nov
(19) |
Dec
(34) |
| 2011 |
Jan
(21) |
Feb
(16) |
Mar
(16) |
Apr
(29) |
May
(17) |
Jun
(18) |
Jul
(7) |
Aug
(21) |
Sep
(10) |
Oct
(7) |
Nov
(15) |
Dec
(6) |
| 2012 |
Jan
(13) |
Feb
(16) |
Mar
(15) |
Apr
(12) |
May
(15) |
Jun
(31) |
Jul
(22) |
Aug
(15) |
Sep
(46) |
Oct
(21) |
Nov
(15) |
Dec
(33) |
| 2013 |
Jan
(19) |
Feb
(17) |
Mar
(31) |
Apr
(17) |
May
(27) |
Jun
(24) |
Jul
(26) |
Aug
(11) |
Sep
(9) |
Oct
(22) |
Nov
(14) |
Dec
(16) |
| 2014 |
Jan
(20) |
Feb
(66) |
Mar
(29) |
Apr
(13) |
May
(9) |
Jun
|
Jul
(11) |
Aug
(21) |
Sep
(15) |
Oct
(5) |
Nov
(5) |
Dec
(10) |
| 2015 |
Jan
(6) |
Feb
(26) |
Mar
(26) |
Apr
|
May
(9) |
Jun
(5) |
Jul
(5) |
Aug
(11) |
Sep
(8) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
(3) |
Feb
|
Mar
(9) |
Apr
(3) |
May
(16) |
Jun
(26) |
Jul
(32) |
Aug
(27) |
Sep
(9) |
Oct
|
Nov
(4) |
Dec
(10) |
| 2017 |
Jan
(11) |
Feb
(44) |
Mar
(6) |
Apr
(8) |
May
(1) |
Jun
(2) |
Jul
(34) |
Aug
(28) |
Sep
(3) |
Oct
(9) |
Nov
(3) |
Dec
|
| 2018 |
Jan
(1) |
Feb
(5) |
Mar
(6) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(6) |
Oct
|
Nov
(6) |
Dec
|
| 2019 |
Jan
(18) |
Feb
(16) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
(3) |
Oct
(10) |
Nov
(1) |
Dec
(3) |
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(17) |
Jun
(23) |
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
(10) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
(1) |
Dec
|
| 2022 |
Jan
(8) |
Feb
|
Mar
(9) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(13) |
Nov
(12) |
Dec
|
| 2023 |
Jan
|
Feb
(1) |
Mar
(9) |
Apr
|
May
(3) |
Jun
(5) |
Jul
(3) |
Aug
(8) |
Sep
|
Oct
|
Nov
(1) |
Dec
(9) |
| 2024 |
Jan
(8) |
Feb
|
Mar
(14) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
(2) |
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Carles L. <car...@in...> - 2020-06-02 10:44:03
|
Thanks a lot Martí Carles Llopis | Developer & neoStampa Specialist T. +34 937 912 821 - +34 646 373 569 A. C/Rocà, 6 08394 - Sant Vicenç de Montalt, Barcelona. View Map <https://goo.gl/maps/eN3Yo2Hty3K77sVPA> Visit our website> <https://www.inedit.com/> <https://www.youtube.com/channel/UCoZRohS-Vx7DrieESs6M92g> <https://www.linkedin.com/company/ineditsoftware> <https://www.instagram.com/inedit_software/> <https://www.facebook.com/ineditsoftware/> <https://twitter.com/IneditSoftware> > On 2 Jun 2020, at 11:47, mar...@li... wrote: > > > > well, the specs say that Lut16 type contains a 3x3 matrix (only used for XYZ), input and output curves and the grid itself. > So we keep thinking that the n calculated as inputChannels * outputChannels makes no sense. > > You are absolutely right, weird enough, the spec forces 3x3 no matter channel count. If color space is not XYZ, whole matrix is ignored. The CMM does that, but somehow the write routine was not doing same behaviour. Thanks for pointing out. It is now fixed on GIT. > > Marti -- La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada desde INEDIT SOFTWARE SL, es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida y puede ser ilegal cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias. POLÍTICA DE PRIVACIDAD <https://www.inedit.com/es/aviso-legal/> The information contained in this message and/or attached file(s), sent from INEDIT SOFTWARE SL, is confidential/privileged and is intended to be read only by the person(s) to whom it is adressed. If you read this message and you are not the designated recipient, employee or agent responsible for delivering the message to the recipient, or have received this communication by mistake, we inform you that it is totally prohibited and may be illega, any disclosure, distribution or reproduction of this communication, and we ask you to notify us immediately and return the original message to the address mentioned above. Thank you. PRIVACY & TERMS <https://www.inedit.com/en/aviso-legal/> |
|
From: <mar...@li...> - 2020-06-02 09:48:10
|
<div dir='auto'><div><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>well, the specs say that Lut16 type contains a 3x3 matrix (only used for XYZ), input and output curves and the grid itself.</div><div>So we keep thinking that the n calculated as inputChannels * outputChannels makes no sense. </div><div></div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">You are absolutely right, weird enough, the spec forces 3x3 no matter channel count. If color space is not XYZ, whole matrix is ignored. The CMM does that, but somehow the write routine was not doing same behaviour. Thanks for pointing out. It is now fixed on GIT.</div><div dir="auto"><br></div><div dir="auto">Marti</div></div> |
|
From: Vincent T. <vin...@gm...> - 2020-06-02 08:44:09
|
hello use LaTeX :-) regards Vincent Torri On Tue, Jun 2, 2020 at 9:12 AM <mar...@li...> wrote: > > Hello Bob, > > This is because the PDFs. I use ms word and print to PDF and the result is huge files. > > I could make a tarball without the doc folders and this will squeeze the size in about 10 Mb less. > > Someting like lcms2-2.10_no_doc.tar.gz would work? > > I guess most people just want the sources for automated builds. > > Best regards > Marti > > El 2 jun. 2020 1:57, Bob Friesenhahn <bfr...@si...> escribió: > > It seems that the lcms distribution packages have grown to > astonishingly large sizes given what the software is. It used to be > pretty small. Lcms2 has grown from 3.3M up to its current size of > 15M. > > The growth in the package size impacts GraphicsMagick since > GraphicsMagick ships lcms sources almost as is for the Windows builds. > I put this into the GraphicsMagick source repository and so the source > repository becomes even larger. Then the full GraphicsMagick sources > for Windows becomes astonishingly large. > > Is there a way to make the distribution package smaller? For example, > split source files, sample files, formatted documentation? > > This is the growth that I see in lcms2 distribution file sizes: > > % ls -lthgr lcms2* > -r--r--r-- 1 ftp 3.3M May 15 2010 lcms2-2.0a.tar.gz > -r--r--r-- 1 ftp 3.6M Dec 1 2010 lcms2-2.1.tar.gz > -r--r--r-- 1 ftp 4.1M Jun 10 2011 lcms2-2.2.zip > -r--r--r-- 1 ftp 4.0M Jun 10 2011 lcms2-2.2.tar.gz > -r--r--r-- 1 ftp 4.3M Dec 23 2011 lcms2-2.3.tar.gz > -r--r--r-- 1 ftp 4.3M Dec 23 2011 lcms2-2.3.zip > -r--r--r-- 1 ftp 4.1M Sep 10 2012 lcms2-2.4.tar.gz > -r--r--r-- 1 ftp 4.2M Sep 10 2012 lcms2-2.4.zip > -r--r--r-- 1 ftp 6.7M Jul 1 2013 lcms2-2.5.tar.gz > -r--r--r-- 1 ftp 6.8M Jul 1 2013 lcms2-2.5.zip > -r--r--r-- 1 ftp 4.4M Mar 17 2014 lcms2-2.6.tar.gz > -r--r--r-- 1 ftp 4.5M Mar 17 2014 lcms2-2.6.zip > -r--r--r-- 1 ftp 6.2M Mar 21 2015 lcms2-2.7.tar.gz > -r--r--r-- 1 ftp 6.4M Mar 21 2015 lcms2-2.7.zip > -r--r--r-- 1 ftp 6.4M Jul 20 2016 lcms2-2.8.tar.gz > -r--r--r-- 1 ftp 6.5M Jul 20 2016 lcms2-2.8.zip > -r--r--r-- 1 ftp 11M Dec 7 09:48 lcms2-2.9.zip > -r--r--r-- 1 ftp 10M Dec 7 09:48 lcms2-2.9.tar.gz > -r--r--r-- 1 ftp 15M May 31 11:38 lcms2-2.10.tar.gz > -r--r--r-- 1 ftp 15M May 31 11:39 lcms2-2.10.zip > > Bob > -- > Bob Friesenhahn > bfr...@si..., http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ > Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt > > > _______________________________________________ > Lcms-user mailing list > Lcm...@li... > https://lists.sourceforge.net/lists/listinfo/lcms-user > > > _______________________________________________ > Lcms-user mailing list > Lcm...@li... > https://lists.sourceforge.net/lists/listinfo/lcms-user |
|
From: Carles L. <car...@in...> - 2020-06-02 08:17:27
|
Hi Marti, well, the specs say that Lut16 type contains a 3x3 matrix (only used for XYZ), input and output curves and the grid itself. So we keep thinking that the n calculated as inputChannels * outputChannels makes no sense. Best regards Carles Llopis | Developer & neoStampa Specialist T. +34 937 912 821 - +34 646 373 569 A. C/Rocà, 6 08394 - Sant Vicenç de Montalt, Barcelona. View Map <https://goo.gl/maps/eN3Yo2Hty3K77sVPA> Visit our website> <https://www.inedit.com/> <https://www.youtube.com/channel/UCoZRohS-Vx7DrieESs6M92g> <https://www.linkedin.com/company/ineditsoftware> <https://www.instagram.com/inedit_software/> <https://www.facebook.com/ineditsoftware/> <https://twitter.com/IneditSoftware> > On 1 Jun 2020, at 16:11, mar...@li... wrote: > > > Quoting Carles Llopis <car...@in...>: > >> we found with the latest releases that we can't save DeviceLink profiles to >> memory buffers or files. >> We create DeviceLink profiles "on the fly". The input is normally RGB and >> the output can be anything from 1CLR to FCLR > > This is by design. Has been there for many time. If you create a rather usual 3x3 lut and you dont't specify any matrix, lcms puts in the profile a identity for you. If the pipeline is not 3x3, then you have to add the matrix. This is because for multichannel it is not clear what a "identity" means. Note that the spec *requires* a matrix for Lut16, so you have to put something. > > Then you have several options: > > - Use a V4 ICC profile with a modern LutAtoB/LutBtoA > - Add a matrix to the pipeline. > > Best regards > Marti > > > > > -- La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada desde INEDIT SOFTWARE SL, es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida y puede ser ilegal cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias. POLÍTICA DE PRIVACIDAD <https://www.inedit.com/es/aviso-legal/> The information contained in this message and/or attached file(s), sent from INEDIT SOFTWARE SL, is confidential/privileged and is intended to be read only by the person(s) to whom it is adressed. If you read this message and you are not the designated recipient, employee or agent responsible for delivering the message to the recipient, or have received this communication by mistake, we inform you that it is totally prohibited and may be illega, any disclosure, distribution or reproduction of this communication, and we ask you to notify us immediately and return the original message to the address mentioned above. Thank you. PRIVACY & TERMS <https://www.inedit.com/en/aviso-legal/> |
|
From: <mar...@li...> - 2020-06-02 07:11:06
|
<div dir='auto'>Hello Bob, <div dir="auto"><br></div><div dir="auto">This is because the PDFs. I use ms word and print to PDF and the result is huge files.</div><div dir="auto"><br></div><div dir="auto">I could make a tarball without the doc folders and this will squeeze the size in about 10 Mb less. </div><div dir="auto"><br></div><div dir="auto">Someting like lcms2-2.10_no_doc.tar.gz would work?</div><div dir="auto"><br></div><div dir="auto">I guess most people just want the sources for automated builds.</div><div dir="auto"><br></div><div dir="auto">Best regards</div><div dir="auto">Marti</div></div><div class="gmail_extra"><br><div class="gmail_quote">El 2 jun. 2020 1:57, Bob Friesenhahn <bfr...@si...> escribió:<br type="attribution" /><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">It seems that the lcms distribution packages have grown to <br> astonishingly large sizes given what the software is. It used to be <br> pretty small. Lcms2 has grown from 3.3M up to its current size of <br> 15M. <br> <br> The growth in the package size impacts GraphicsMagick since <br> GraphicsMagick ships lcms sources almost as is for the Windows builds. <br> I put this into the GraphicsMagick source repository and so the source <br> repository becomes even larger. Then the full GraphicsMagick sources <br> for Windows becomes astonishingly large. <br> <br> Is there a way to make the distribution package smaller? For example, <br> split source files, sample files, formatted documentation? <br> <br> This is the growth that I see in lcms2 distribution file sizes: <br> <br> % ls -lthgr lcms2* <br> -r--r--r-- 1 ftp 3.3M May 15 2010 lcms2-2.0a.tar.gz <br> -r--r--r-- 1 ftp 3.6M Dec 1 2010 lcms2-2.1.tar.gz <br> -r--r--r-- 1 ftp 4.1M Jun 10 2011 lcms2-2.2.zip <br> -r--r--r-- 1 ftp 4.0M Jun 10 2011 lcms2-2.2.tar.gz <br> -r--r--r-- 1 ftp 4.3M Dec 23 2011 lcms2-2.3.tar.gz <br> -r--r--r-- 1 ftp 4.3M Dec 23 2011 lcms2-2.3.zip <br> -r--r--r-- 1 ftp 4.1M Sep 10 2012 lcms2-2.4.tar.gz <br> -r--r--r-- 1 ftp 4.2M Sep 10 2012 lcms2-2.4.zip <br> -r--r--r-- 1 ftp 6.7M Jul 1 2013 lcms2-2.5.tar.gz <br> -r--r--r-- 1 ftp 6.8M Jul 1 2013 lcms2-2.5.zip <br> -r--r--r-- 1 ftp 4.4M Mar 17 2014 lcms2-2.6.tar.gz <br> -r--r--r-- 1 ftp 4.5M Mar 17 2014 lcms2-2.6.zip <br> -r--r--r-- 1 ftp 6.2M Mar 21 2015 lcms2-2.7.tar.gz <br> -r--r--r-- 1 ftp 6.4M Mar 21 2015 lcms2-2.7.zip <br> -r--r--r-- 1 ftp 6.4M Jul 20 2016 lcms2-2.8.tar.gz <br> -r--r--r-- 1 ftp 6.5M Jul 20 2016 lcms2-2.8.zip <br> -r--r--r-- 1 ftp 11M Dec 7 09:48 lcms2-2.9.zip <br> -r--r--r-- 1 ftp 10M Dec 7 09:48 lcms2-2.9.tar.gz <br> -r--r--r-- 1 ftp 15M May 31 11:38 lcms2-2.10.tar.gz <br> -r--r--r-- 1 ftp 15M May 31 11:39 lcms2-2.10.zip <br> <br> Bob <br> -- <br> Bob Friesenhahn <br> bfr...@si..., http://www.simplesystems.org/users/bfriesen/ <br> GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ <br> Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt <br> <br> <br> _______________________________________________ <br> Lcms-user mailing list <br> Lcm...@li... <br> https://lists.sourceforge.net/lists/listinfo/lcms-user <br> </p> </blockquote></div><br></div> |
|
From: Bob F. <bfr...@si...> - 2020-06-01 23:57:23
|
It seems that the lcms distribution packages have grown to astonishingly large sizes given what the software is. It used to be pretty small. Lcms2 has grown from 3.3M up to its current size of 15M. The growth in the package size impacts GraphicsMagick since GraphicsMagick ships lcms sources almost as is for the Windows builds. I put this into the GraphicsMagick source repository and so the source repository becomes even larger. Then the full GraphicsMagick sources for Windows becomes astonishingly large. Is there a way to make the distribution package smaller? For example, split source files, sample files, formatted documentation? This is the growth that I see in lcms2 distribution file sizes: % ls -lthgr lcms2* -r--r--r-- 1 ftp 3.3M May 15 2010 lcms2-2.0a.tar.gz -r--r--r-- 1 ftp 3.6M Dec 1 2010 lcms2-2.1.tar.gz -r--r--r-- 1 ftp 4.1M Jun 10 2011 lcms2-2.2.zip -r--r--r-- 1 ftp 4.0M Jun 10 2011 lcms2-2.2.tar.gz -r--r--r-- 1 ftp 4.3M Dec 23 2011 lcms2-2.3.tar.gz -r--r--r-- 1 ftp 4.3M Dec 23 2011 lcms2-2.3.zip -r--r--r-- 1 ftp 4.1M Sep 10 2012 lcms2-2.4.tar.gz -r--r--r-- 1 ftp 4.2M Sep 10 2012 lcms2-2.4.zip -r--r--r-- 1 ftp 6.7M Jul 1 2013 lcms2-2.5.tar.gz -r--r--r-- 1 ftp 6.8M Jul 1 2013 lcms2-2.5.zip -r--r--r-- 1 ftp 4.4M Mar 17 2014 lcms2-2.6.tar.gz -r--r--r-- 1 ftp 4.5M Mar 17 2014 lcms2-2.6.zip -r--r--r-- 1 ftp 6.2M Mar 21 2015 lcms2-2.7.tar.gz -r--r--r-- 1 ftp 6.4M Mar 21 2015 lcms2-2.7.zip -r--r--r-- 1 ftp 6.4M Jul 20 2016 lcms2-2.8.tar.gz -r--r--r-- 1 ftp 6.5M Jul 20 2016 lcms2-2.8.zip -r--r--r-- 1 ftp 11M Dec 7 09:48 lcms2-2.9.zip -r--r--r-- 1 ftp 10M Dec 7 09:48 lcms2-2.9.tar.gz -r--r--r-- 1 ftp 15M May 31 11:38 lcms2-2.10.tar.gz -r--r--r-- 1 ftp 15M May 31 11:39 lcms2-2.10.zip Bob -- Bob Friesenhahn bfr...@si..., http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt |
|
From: Carles L. <car...@in...> - 2020-06-01 14:11:41
|
Ah, ok, then we'll add the indentity matrix by ourselves. thank you! Carles > On 1 Jun 2020, at 16:11, mar...@li... wrote: > > > Quoting Carles Llopis <car...@in...>: > >> we found with the latest releases that we can't save DeviceLink profiles to >> memory buffers or files. >> We create DeviceLink profiles "on the fly". The input is normally RGB and >> the output can be anything from 1CLR to FCLR > > This is by design. Has been there for many time. If you create a rather usual 3x3 lut and you dont't specify any matrix, lcms puts in the profile a identity for you. If the pipeline is not 3x3, then you have to add the matrix. This is because for multichannel it is not clear what a "identity" means. Note that the spec *requires* a matrix for Lut16, so you have to put something. > > Then you have several options: > > - Use a V4 ICC profile with a modern LutAtoB/LutBtoA > - Add a matrix to the pipeline. > > Best regards > Marti > > > > > -- La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada desde INEDIT SOFTWARE SL, es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida y puede ser ilegal cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias. POLÍTICA DE PRIVACIDAD <https://www.inedit.com/es/aviso-legal/> The information contained in this message and/or attached file(s), sent from INEDIT SOFTWARE SL, is confidential/privileged and is intended to be read only by the person(s) to whom it is adressed. If you read this message and you are not the designated recipient, employee or agent responsible for delivering the message to the recipient, or have received this communication by mistake, we inform you that it is totally prohibited and may be illega, any disclosure, distribution or reproduction of this communication, and we ask you to notify us immediately and return the original message to the address mentioned above. Thank you. PRIVACY & TERMS <https://www.inedit.com/en/aviso-legal/> |
|
From: <mar...@li...> - 2020-06-01 14:09:34
|
Quoting Carles Llopis <car...@in...>: > we found with the latest releases that we can't save DeviceLink profiles to > memory buffers or files. > We create DeviceLink profiles "on the fly". The input is normally RGB and > the output can be anything from 1CLR to FCLR This is by design. Has been there for many time. If you create a rather usual 3x3 lut and you dont't specify any matrix, lcms puts in the profile a identity for you. If the pipeline is not 3x3, then you have to add the matrix. This is because for multichannel it is not clear what a "identity" means. Note that the spec *requires* a matrix for Lut16, so you have to put something. Then you have several options: - Use a V4 ICC profile with a modern LutAtoB/LutBtoA - Add a matrix to the pipeline. Best regards Marti |
|
From: <mar...@li...> - 2020-06-01 13:51:14
|
Hi,
I am glad to the announce the release 2.10 of the LittleCMS open
source color engine.
It includes bug fixes and some new features. Please see the ChangeLog
file for more details.
The biggest difference of 2.10 with other releases lies in the bundle
with the "fast float" plug-in. Previouly released as a commercial
package, the "fast float" plug-in increases floating point performance
significantly. That means, you call a function when initializing your
code and you get a throughput gain when doing floating point
transforms. 8 bit matrix-shaper transforms are also faster, handled by
using SSE2 instructions where possible.
The plug-in has also other features like dithered output or fast 8 bit
RGB transforms. There is a test bed in the plug-in directory that
shows and measures the throughput gain in your target computer.
I have decided to releases this plug-in AS OPEN SOURCE UNDER GPL3 LICENCE.
Please check the license carefully before including the code in your
applications. This is only on the plug-in, the LittleCMS core is still
under MIT license. In case of doubt you can contact me on this mailing
list or by using the mail info { at } littlecms { dot } com.
Little CMS intends to be a small-footprint color management engine,
with special focus on accuracy and performance. It uses the
International Color Consortium standard (ICC), which is the modern
standard when regarding to color management.
The ICC specification is widely used and is referred to in many
International and other de-facto standards.
For more information, please take a look on
Main site:
http://www.littlecms.com
Downloads:
http://www.littlecms.com/download.html
Best regards,
Marti Maria
The Little CMS project
http://www.littlecms.com
|
|
From: Carles L. <car...@in...> - 2020-05-29 12:42:21
|
Hello all,
we found with the latest releases that we can't save DeviceLink profiles to
memory buffers or files.
We create DeviceLink profiles "on the fly". The input is normally RGB and
the output can be anything from 1CLR to FCLR
The function Type_Lut16_Write returns with an error if the inputCha *
outputCha is not 9, in the case that the LUT has no matrix.
...
if (!_cmsWriteUInt8Number(io, (cmsUInt8Number) InputChannels)) return FALSE;
if (!_cmsWriteUInt8Number(io, (cmsUInt8Number) OutputChannels)) return FALSE
;
if (!_cmsWriteUInt8Number(io, (cmsUInt8Number) clutPoints)) return FALSE;
if (!_cmsWriteUInt8Number(io, 0)) return FALSE; // Padding
n = NewLUT->InputChannels * NewLUT->OutputChannels;
if (MatMPE != NULL) {
for (i = 0; i < n; i++)
{
if (!_cmsWrite15Fixed16Number(io, MatMPE->Double[i])) return FALSE;
}
}
else {
if (n != 9) return FALSE;
if (!_cmsWrite15Fixed16Number(io, 1)) return FALSE;
if (!_cmsWrite15Fixed16Number(io, 0)) return FALSE;
if (!_cmsWrite15Fixed16Number(io, 0)) return FALSE;
if (!_cmsWrite15Fixed16Number(io, 0)) return FALSE;
if (!_cmsWrite15Fixed16Number(io, 1)) return FALSE;
if (!_cmsWrite15Fixed16Number(io, 0)) return FALSE;
if (!_cmsWrite15Fixed16Number(io, 0)) return FALSE;
if (!_cmsWrite15Fixed16Number(io, 0)) return FALSE;
if (!_cmsWrite15Fixed16Number(io, 1)) return FALSE;
}
...
We think that the verification about the number of elements of the matrix
(n != 9) should be in the other case, not in
the place where the identity matrix is written.
Do you think you can fix it?
Are we wrong?
Thanks a lot
Carles Llopis
On Sat, May 23, 2020 at 5:38 PM <mar...@li...> wrote:
>
> Hello,
>
> Many thanks to everybody for testing & reporting.
>
> Here is release candidate 2, with all glitches you have found hopefully
> fixed.
>
> http://www.littlecms.com/lcms2-2.10rc2.tar.gz
>
> Best regards
> Marti Maria
> The LittleCMS Project
> http:\www.littlecms.com
>
>
>
>
> _______________________________________________
> Lcms-user mailing list
> Lcm...@li...
> https://lists.sourceforge.net/lists/listinfo/lcms-user
>
--
La información contenida en este mensaje y/o archivo(s) adjunto(s),
enviada desde INEDIT SOFTWARE SL, es confidencial/privilegiada y está
destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida.
Si
usted lee este mensaje y no es el destinatario señalado, el empleado o el
agente responsable de entregar el mensaje al destinatario, o ha recibido
esta comunicación por error, le informamos que está totalmente prohibida y
puede ser ilegal cualquier divulgación, distribución o reproducción de esta
comunicación, y le rogamos que nos lo notifique inmediatamente y nos
devuelva el mensaje original a la dirección arriba mencionada. Gracias.
POLÍTICA DE PRIVACIDAD <https://www.inedit.com/es/aviso-legal/>
The
information contained in this message and/or attached file(s), sent from
INEDIT SOFTWARE SL, is confidential/privileged and is intended to be read
only by the person(s) to whom it is adressed.
If you read this message and
you are not the designated recipient, employee or agent responsible for
delivering the message to the recipient, or have received this
communication by mistake, we inform you that it is totally prohibited and
may be illega, any disclosure, distribution or reproduction of this
communication, and we ask you to notify us immediately and return the
original message to the address mentioned above. Thank you.
PRIVACY &
TERMS <https://www.inedit.com/en/aviso-legal/>
|
|
From: Carles L. <car...@in...> - 2020-05-25 18:51:57
|
Hello Marti, yes we are aware of the limitations. In any case, we are going to create 4 points per dimension for that number of channels, so we keep te final size “under control” I have managed to chang this value plus implementing the N Dimensional interpolation methods. Should I send you the changes directly for your verification? Thank you! Carles Llopis Project Manager Inèdit Software, S.L | Carrer del Rocà, 6| 08394 Sant Vicenç de Montalt | Barcelona - Spain T. (+34) 937 912 821 | M. (+34) 646 373 569| www.inedit.com > On 25 May 2020, at 20:10, Mar...@li... wrote: > > > Hi Carles, > > Well, you could try, but... Are you sure you want this? > > In the case you use 9 inputs on tables of 12 points per dimension, which is clearle insufficient, you got a nice icc profile of 14.4 gigabytes. This is if you keep 8 bit profile and one intent. 33 points, 16 bits and 3 intents makes it 760 terabytes and not possible at all because 32 bit offsets. > > Regards > Marti > > > > On 25 May 2020 16:04, Carles Llopis <car...@in...> wrote: > Dear users, > > we are trying to use LCMS to help us building synthetic DeviceLink profiles both for separation to multichannel and for simulation (NCLR to LAB). > Everything runs fine except there is a limitation on the input channels count for the NCLR->LAB > I've found that MAX_INPUT_DIMENSIONS is set to 8. > Do you think it's possible to change this constant value to 15, as 15 is the maximum allowed number of DCS channels ? > > Thank you! > > Carles Llopis | Developer & neoStampa Specialist > > > > > La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada desde INEDIT SOFTWARE SL, es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. > Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida y puede ser ilegal cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias. > > POLÍTICA DE PRIVACIDAD > > The information contained in this message and/or attached file(s), sent from INEDIT SOFTWARE SL, is confidential/privileged and is intended to be read only by the person(s) to whom it is adressed. > If you read this message and you are not the designated recipient, employee or agent responsible for delivering the message to the recipient, or have received this communication by mistake, we inform you that it is totally prohibited and may be illega, any disclosure, distribution or reproduction of this communication, and we ask you to notify us immediately and return the original message to the address mentioned above. Thank you. > > PRIVACY & TERMS > > > > On 25 May 2020 16:04, Carles Llopis <car...@in...> wrote: > Dear users, > > we are trying to use LCMS to help us building synthetic DeviceLink profiles both for separation to multichannel and for simulation (NCLR to LAB). > Everything runs fine except there is a limitation on the input channels count for the NCLR->LAB > I've found that MAX_INPUT_DIMENSIONS is set to 8. > Do you think it's possible to change this constant value to 15, as 15 is the maximum allowed number of DCS channels ? > > Thank you! > > Carles Llopis | Developer & neoStampa Specialist > > > > > La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada desde INEDIT SOFTWARE SL, es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. > Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida y puede ser ilegal cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias. > > POLÍTICA DE PRIVACIDAD > > The information contained in this message and/or attached file(s), sent from INEDIT SOFTWARE SL, is confidential/privileged and is intended to be read only by the person(s) to whom it is adressed. > If you read this message and you are not the designated recipient, employee or agent responsible for delivering the message to the recipient, or have received this communication by mistake, we inform you that it is totally prohibited and may be illega, any disclosure, distribution or reproduction of this communication, and we ask you to notify us immediately and return the original message to the address mentioned above. Thank you. > > PRIVACY & TERMS > > > > On 25 May 2020 16:04, Carles Llopis <car...@in...> wrote: > Dear users, > > we are trying to use LCMS to help us building synthetic DeviceLink profiles both for separation to multichannel and for simulation (NCLR to LAB). > Everything runs fine except there is a limitation on the input channels count for the NCLR->LAB > I've found that MAX_INPUT_DIMENSIONS is set to 8. > Do you think it's possible to change this constant value to 15, as 15 is the maximum allowed number of DCS channels ? > > Thank you! > > Carles Llopis | Developer & neoStampa Specialist > > > > > La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada desde INEDIT SOFTWARE SL, es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. > Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida y puede ser ilegal cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias. > > POLÍTICA DE PRIVACIDAD > > The information contained in this message and/or attached file(s), sent from INEDIT SOFTWARE SL, is confidential/privileged and is intended to be read only by the person(s) to whom it is adressed. > If you read this message and you are not the designated recipient, employee or agent responsible for delivering the message to the recipient, or have received this communication by mistake, we inform you that it is totally prohibited and may be illega, any disclosure, distribution or reproduction of this communication, and we ask you to notify us immediately and return the original message to the address mentioned above. Thank you. > > PRIVACY & TERMS > > -- La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada desde INEDIT SOFTWARE SL, es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida y puede ser ilegal cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias. POLÍTICA DE PRIVACIDAD <https://www.inedit.com/es/aviso-legal/> The information contained in this message and/or attached file(s), sent from INEDIT SOFTWARE SL, is confidential/privileged and is intended to be read only by the person(s) to whom it is adressed. If you read this message and you are not the designated recipient, employee or agent responsible for delivering the message to the recipient, or have received this communication by mistake, we inform you that it is totally prohibited and may be illega, any disclosure, distribution or reproduction of this communication, and we ask you to notify us immediately and return the original message to the address mentioned above. Thank you. PRIVACY & TERMS <https://www.inedit.com/en/aviso-legal/> |
|
From: <mar...@li...> - 2020-05-25 18:10:30
|
<div dir='auto'><div dir="auto"><div dir="auto">Hi Carles,<div dir="auto"><br></div><div dir="auto">Well, you could try, but... Are you sure you want this?</div><div dir="auto"><br></div><div dir="auto">In the case you use 9 inputs on tables of 12 points per dimension, which is clearle insufficient, you got a nice icc profile of 14.4 gigabytes. This is if you keep 8 bit profile and one intent. 33 points, 16 bits and 3 intents makes it 760 terabytes and not possible at all because 32 bit offsets.</div><div dir="auto"><br></div><div dir="auto">Regards</div><div dir="auto">Marti</div><div dir="auto"><br></div><div dir="auto"><br></div></div><div><br><div class="elided-text">On 25 May 2020 16:04, Carles Llopis <car...@in...> wrote:<br type="attribution"><blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Dear users,<div><br></div><div>we are trying to use LCMS to help us building synthetic DeviceLink profiles both for separation to multichannel and for simulation (NCLR to LAB).</div><div>Everything runs fine except there is a limitation on the input channels count for the NCLR->LAB</div><div>I've found that MAX_INPUT_DIMENSIONS is set to 8.</div><div>Do you think it's possible to change this constant value to 15, as 15 is the maximum allowed number of DCS channels ?</div><div><br></div><div>Thank you!</div><div><div> <div dir="auto" style="color:rgb( 0 , 0 , 0 );font-family:'soho gothic pro';font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word"><div dir="auto" style="color:rgb( 0 , 0 , 0 );letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word"><div dir="auto" style="color:rgb( 0 , 0 , 0 );letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word"><div dir="auto" style="color:rgb( 0 , 0 , 0 );letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word"><div><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="font-family:'soho gothic pro';word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="ltr"><div dir="ltr"><div dir="auto" style="word-wrap:break-word"><div dir="ltr"><div dir="ltr"><div dir="auto" style="word-wrap:break-word"><div dir="ltr"><div dir="ltr"><font face="SohoGothicPro-Regular" style="font-family:'sohogothicpro-regular'"><b><font color="#ea521c"><br>Carles Llopis</font></b> <font color="#222222">| Developer & neoStampa Specialist</font></font><div style="font-family:'sohogothicpro-regular'"><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div> <br> <div style="font-size:1.3em"></div><div style="font-size:1.3em"></div><div><div style="color:rgb( 255 , 255 , 255 );font-family:'helvetica';margin:0cm 0cm 0.0001pt;background-color:white"><img src="https://www.inedit.com/wp-content/uploads/2020/03/Untitled-1-4.png"></div></div><div><div style="color:rgb( 255 , 255 , 255 );font-family:'helvetica';margin:0cm 0cm 0.0001pt;background-color:white"><br></div></div><div><span style="color:rgb( 191 , 191 , 191 );text-align:justify"><font size="1">La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada desde INEDIT SOFTWARE SL, es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida.</font></span></div><font size="1"><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida y puede ser ilegal c</span><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">ualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias.</span><br><br></font><div><div><a href="https://www.inedit.com/es/aviso-legal/" style="text-align:justify"><font size="1">POLÍTICA DE PRIVACIDAD</font></a></div><font size="1"><br><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">The information contained in this message and/or attached file(s), sent from INEDIT SOFTWARE SL, is confidential/privileged and is intended to be read only by the person(s) to whom it is adressed.</span><br><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">If you read this message and you are not the designated recipient, employee or agent responsible for delivering the message to the recipient, or have received this communication by mistake, we inform you that it is totally prohibited and may be </span><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">illega, any disclosure, distribution or reproduction of this communication, and we ask you to notify us immediately and return the original message to the address mentioned above. Thank you.</span><br><br></font><div><a href="https://www.inedit.com/en/aviso-legal/"><font size="1">PRIVACY & TERMS</font></a></div></div><div style="font-size:1.3em"><br></div></blockquote></div><br></div></div><div><br><div class="elided-text">On 25 May 2020 16:04, Carles Llopis <car...@in...> wrote:<br type="attribution"><blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Dear users,<div><br></div><div>we are trying to use LCMS to help us building synthetic DeviceLink profiles both for separation to multichannel and for simulation (NCLR to LAB).</div><div>Everything runs fine except there is a limitation on the input channels count for the NCLR->LAB</div><div>I've found that MAX_INPUT_DIMENSIONS is set to 8.</div><div>Do you think it's possible to change this constant value to 15, as 15 is the maximum allowed number of DCS channels ?</div><div><br></div><div>Thank you!</div><div><div> <div dir="auto" style="color:rgb( 0 , 0 , 0 );font-family:'soho gothic pro';font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word"><div dir="auto" style="color:rgb( 0 , 0 , 0 );letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word"><div dir="auto" style="color:rgb( 0 , 0 , 0 );letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word"><div dir="auto" style="color:rgb( 0 , 0 , 0 );letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word"><div><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="font-family:'soho gothic pro';word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="ltr"><div dir="ltr"><div dir="auto" style="word-wrap:break-word"><div dir="ltr"><div dir="ltr"><div dir="auto" style="word-wrap:break-word"><div dir="ltr"><div dir="ltr"><font face="SohoGothicPro-Regular" style="font-family:'sohogothicpro-regular'"><b><font color="#ea521c"><br>Carles Llopis</font></b> <font color="#222222">| Developer & neoStampa Specialist</font></font><div style="font-family:'sohogothicpro-regular'"><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div> <br> <div style="font-size:1.3em"></div><div style="font-size:1.3em"></div><div><div style="color:rgb( 255 , 255 , 255 );font-family:'helvetica';margin:0cm 0cm 0.0001pt;background-color:white"><img src="https://www.inedit.com/wp-content/uploads/2020/03/Untitled-1-4.png"></div></div><div><div style="color:rgb( 255 , 255 , 255 );font-family:'helvetica';margin:0cm 0cm 0.0001pt;background-color:white"><br></div></div><div><span style="color:rgb( 191 , 191 , 191 );text-align:justify"><font size="1">La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada desde INEDIT SOFTWARE SL, es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida.</font></span></div><font size="1"><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida y puede ser ilegal c</span><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">ualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias.</span><br><br></font><div><div><a href="https://www.inedit.com/es/aviso-legal/" style="text-align:justify"><font size="1">POLÍTICA DE PRIVACIDAD</font></a></div><font size="1"><br><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">The information contained in this message and/or attached file(s), sent from INEDIT SOFTWARE SL, is confidential/privileged and is intended to be read only by the person(s) to whom it is adressed.</span><br><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">If you read this message and you are not the designated recipient, employee or agent responsible for delivering the message to the recipient, or have received this communication by mistake, we inform you that it is totally prohibited and may be </span><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">illega, any disclosure, distribution or reproduction of this communication, and we ask you to notify us immediately and return the original message to the address mentioned above. Thank you.</span><br><br></font><div><a href="https://www.inedit.com/en/aviso-legal/"><font size="1">PRIVACY & TERMS</font></a></div></div><div style="font-size:1.3em"><br></div></blockquote></div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 25 May 2020 16:04, Carles Llopis <car...@in...> wrote:<br type="attribution" /><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Dear users,<div><br /></div><div>we are trying to use LCMS to help us building synthetic DeviceLink profiles both for separation to multichannel and for simulation (NCLR to LAB).</div><div>Everything runs fine except there is a limitation on the input channels count for the NCLR->LAB</div><div>I've found that MAX_INPUT_DIMENSIONS is set to 8.</div><div>Do you think it's possible to change this constant value to 15, as 15 is the maximum allowed number of DCS channels ?</div><div><br /></div><div>Thank you!</div><div><div> <div dir="auto" style="color:rgb( 0 , 0 , 0 );font-family:'soho gothic pro';font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word"><div dir="auto" style="color:rgb( 0 , 0 , 0 );letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word"><div dir="auto" style="color:rgb( 0 , 0 , 0 );letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word"><div dir="auto" style="color:rgb( 0 , 0 , 0 );letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word"><div><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="font-family:'soho gothic pro';word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div dir="ltr"><div dir="ltr"><div dir="auto" style="word-wrap:break-word"><div dir="ltr"><div dir="ltr"><div dir="auto" style="word-wrap:break-word"><div dir="ltr"><div dir="ltr"><font face="SohoGothicPro-Regular" style="font-family:'sohogothicpro-regular'"><b><font color="#ea521c"><br />Carles Llopis</font></b> <font color="#222222">| Developer & neoStampa Specialist</font></font><div style="font-family:'sohogothicpro-regular'"><br /></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div> <br /> <div style="font-size:1.3em"></div><div style="font-size:1.3em"></div><div><div style="color:rgb( 255 , 255 , 255 );font-family:'helvetica';margin:0cm 0cm 0.0001pt;background-color:white"><img src="https://www.inedit.com/wp-content/uploads/2020/03/Untitled-1-4.png" /></div></div><div><div style="color:rgb( 255 , 255 , 255 );font-family:'helvetica';margin:0cm 0cm 0.0001pt;background-color:white"><br /></div></div><div><span style="color:rgb( 191 , 191 , 191 );text-align:justify"><font size="1">La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada desde INEDIT SOFTWARE SL, es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida.</font></span></div><font size="1"><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida y puede ser ilegal c</span><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">ualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias.</span><br /><br /></font><div><div><a href="https://www.inedit.com/es/aviso-legal/" style="text-align:justify"><font size="1">POLÍTICA DE PRIVACIDAD</font></a></div><font size="1"><br /><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">The information contained in this message and/or attached file(s), sent from INEDIT SOFTWARE SL, is confidential/privileged and is intended to be read only by the person(s) to whom it is adressed.</span><br /><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">If you read this message and you are not the designated recipient, employee or agent responsible for delivering the message to the recipient, or have received this communication by mistake, we inform you that it is totally prohibited and may be </span><span style="text-align:justify;color:rgb( 191 , 191 , 191 )">illega, any disclosure, distribution or reproduction of this communication, and we ask you to notify us immediately and return the original message to the address mentioned above. Thank you.</span><br /><br /></font><div><a href="https://www.inedit.com/en/aviso-legal/"><font size="1">PRIVACY & TERMS</font></a></div></div><div style="font-size:1.3em"><br /></div></blockquote></div><br></div> |
|
From: Carles L. <car...@in...> - 2020-05-25 14:31:34
|
Dear users, we are trying to use LCMS to help us building synthetic DeviceLink profiles both for separation to multichannel and for simulation (NCLR to LAB). Everything runs fine except there is a limitation on the input channels count for the NCLR->LAB I've found that MAX_INPUT_DIMENSIONS is set to 8. Do you think it's possible to change this constant value to 15, as 15 is the maximum allowed number of DCS channels ? Thank you! Carles Llopis | Developer & neoStampa Specialist -- La información contenida en este mensaje y/o archivo(s) adjunto(s), enviada desde INEDIT SOFTWARE SL, es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida y puede ser ilegal cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias. POLÍTICA DE PRIVACIDAD <https://www.inedit.com/es/aviso-legal/> The information contained in this message and/or attached file(s), sent from INEDIT SOFTWARE SL, is confidential/privileged and is intended to be read only by the person(s) to whom it is adressed. If you read this message and you are not the designated recipient, employee or agent responsible for delivering the message to the recipient, or have received this communication by mistake, we inform you that it is totally prohibited and may be illega, any disclosure, distribution or reproduction of this communication, and we ask you to notify us immediately and return the original message to the address mentioned above. Thank you. PRIVACY & TERMS <https://www.inedit.com/en/aviso-legal/> |
|
From: <mar...@li...> - 2020-05-23 15:36:39
|
Hello, Many thanks to everybody for testing & reporting. Here is release candidate 2, with all glitches you have found hopefully fixed. http://www.littlecms.com/lcms2-2.10rc2.tar.gz Best regards Marti Maria The LittleCMS Project http:\www.littlecms.com |
|
From: Kevin G. <s7...@ya...> - 2020-05-23 13:52:24
|
Hi Marti Thanks for responding, your answer is very helpful. Regards Kevin > On 22 May 2020, at 13:03, mar...@li... wrote: > > Hi Kevin, > > Opening profiles at the begin and then reusing them in different transforms is a good idea. The code is designed to work in that way. There should be no issues on concurrency, as the library does the necessary locks. Just avoid cmsChangeBuffersFormat to modify a yet created transform, this is a throughput killer > > Memory fragmentation is not an issue, the code uses sub-allocators. Keep you focus on code clarity, there is no need of dummy transforms. > > Regards > Marti > > On 22 May 2020 13:32, Kev via Lcms-user <lcm...@li...> wrote: > Hi. > > Our lcms2 usage is quite basic: > open source & target profiles held in memory > create transform > do transform > delete transform > close both profiles > > (our code originally used lcms1 so when we switched to lcms2 we kept the changes to a minimum). > > Quite often, the target profile will be the same sRGB profile and sometimes the source profile will be a generic CMYK profile. > > I guess there is an overhead of always opening and closing these common profiles so i'm wondering if it would be better to create them at startup and leave them open until our application closes. If we did change our code is there any issues we need to look out for. For example, > • Would there be any multi-threading related issues caused by different transforms using the same profiles at the same time? > > • I'm sure I read that opening a profile only reads a subset of the data and the rest isn't read until it is required. I guess this could cause memory fragmentation issues so to help avoid this would it be a good idea to perform a dummy transform after opening the profile so that the rest of the profile data was read into memory as early as possible. > > > Any help or advice would be greatly appreciated. > > > Regards, > Kevin > |
|
From: <mar...@li...> - 2020-05-22 12:03:41
|
<div dir='auto'><div>Hi Kevin, </div><div dir="auto"><br></div><div dir="auto">Opening profiles at the begin and then reusing them in different transforms is a good idea. The code is designed to work in that way. There should be no issues on concurrency, as the library does the necessary locks. Just avoid cmsChangeBuffersFormat to modify a yet created transform, this is a throughput killer</div><div dir="auto"><br></div><div dir="auto">Memory fragmentation is not an issue, the code uses sub-allocators. Keep you focus on code clarity, there is no need of dummy transforms.</div><div dir="auto"><br></div><div dir="auto">Regards</div><div dir="auto">Marti</div><div dir="auto"><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">On 22 May 2020 13:32, Kev via Lcms-user <lcm...@li...> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:'helvetica neue' , 'helvetica' , 'arial' , sans-serif;font-size:13px"><div dir="ltr">Hi.</div><div dir="ltr"><br></div><div dir="ltr">Our lcms2 usage is quite basic: <br></div><div dir="ltr">open source & target profiles held in memory > create transform > do transform > delete transform > close both profiles</div><div dir="ltr"><br></div><div dir="ltr">(our code originally used lcms1 so when we switched to lcms2 we kept the changes to a minimum).</div><div dir="ltr"><br></div><div dir="ltr">Quite often, the target profile will be the same sRGB profile and sometimes the source profile will be a generic CMYK profile.</div><div dir="ltr"><br></div><div dir="ltr">I guess there is an overhead of always opening and closing these common profiles so i'm wondering if it would be better to create them at startup and leave them open until our application closes. If we did change our code is there any issues we need to look out for. For example,<br></div><div dir="ltr">• Would there be any multi-threading related issues caused by different transforms using the same profiles at the same time?</div><div dir="ltr"><br></div><div dir="ltr">• I'm sure I read that opening a profile only reads a subset of the data and the rest isn't read until it is required. I guess this could cause memory fragmentation issues so to help avoid this would it be a good idea to perform a dummy transform after opening the profile so that the rest of the profile data was read into memory as early as possible.<br></div><div dir="ltr"><br></div><div><br></div><div dir="ltr">Any help or advice would be greatly appreciated.<br></div><div><br></div><div><br></div><div dir="ltr">Regards,<br>Kevin<br></div></div></div></blockquote></div><br></div></div></div> |
|
From: Kev <s7...@ya...> - 2020-05-22 11:32:20
|
Hi. Our lcms2 usage is quite basic: open source & target profiles held in memory > create transform > do transform > delete transform > close both profiles (our code originally used lcms1 so when we switched to lcms2 we kept the changes to a minimum). Quite often, the target profile will be the same sRGB profile and sometimes the source profile will be a generic CMYK profile. I guess there is an overhead of always opening and closing these common profiles so i'm wondering if it would be better to create them at startup and leave them open until our application closes. If we did change our code is there any issues we need to look out for. For example, • Would there be any multi-threading related issues caused by different transforms using the same profiles at the same time? • I'm sure I read that opening a profile only reads a subset of the data and the rest isn't read until it is required. I guess this could cause memory fragmentation issues so to help avoid this would it be a good idea to perform a dummy transform after opening the profile so that the rest of the profile data was read into memory as early as possible. Any help or advice would be greatly appreciated. Regards, Kevin |
|
From: Boudewijn R. <bo...@va...> - 2020-05-21 08:00:59
|
On donderdag 21 mei 2020 09:35:59 CEST mar...@li... wrote: > I must confess Krita has been one of the reasons to release the > plug-in as open source. Let me say you have evolved into an awesome > program. The one I reccomend it to whosever that wants a photoshop > alternative. Thanks! > The plug-in should add enough speed to allow floating-point > transformations in HDR and other special workflows. 8 bit throughput > should also be increased. > > But please be careful on testing, because the optimizations the > plug-in uses are rather agressive and it is possible to get some small > differences in numbers. I have been using the plug-in for years and it > works, but it is certainly desireable to have a way to deactivate. The > yet-existing flag cmsFLAGS_NOOPTIMIZE disables the plug-in as well. > > Please let me know if you need assistence on Krita. And keep on that > good work! Sure, will do! -- https://www.krita.org |
|
From: <mar...@li...> - 2020-05-21 07:50:30
|
Quoting Richard Hughes <hug...@gm...>: > Work great here, thanks. All the colord self tests pass with this installed. Thanks! >> MD5 is now accesible in API. > Do you mean something like cmsSetHeaderProfileID? You have cmsMD5alloc, cmsMD5add, cmsMD5finish in the plug-in API. This exposes the internal implementation of the MD5 algorithm. Good for embedded systems and situations whith scarce resources where code reuse is a big requirement. Otherwise, carefull about MD5, which has been proven to be insecure. I use it because the ICC spec, but there are way better message digest algorithms. > > Less awesome. :( Whilst I really appreciate the "gift" of the fast > math plugin, if it was "LGPL v2+" I could unconditionally enable it in > colord. Obviously the L in the LGPLv2+ means it can be used in > non-free software (which is probably why you chose the * variant) but > it means it can be used by the animation studios and places like that. > I really don't want to come across ungrateful, as it's your gift to > give, not the receiver to set conditions. Well, this is a way to give support to free software. The plug-in basically adds thoughput. With the core lcms2 you can do the same. If you do free free software you can use it for free. If you need this on commercial software, please contact me privately. There is a commercial license available at a reasonable fee. Best regards Marti |
|
From: <mar...@li...> - 2020-05-21 07:34:24
|
Hello, Quoting Boudewijn Rempt via Lcms-user <lcm...@li...>: > > Same here -- works fine, all related unittests in krita pass. Excellent, thank you. > For Krita it's perfect, and subjectively speaking, it makes > everything feel smoother :-) I must confess Krita has been one of the reasons to release the plug-in as open source. Let me say you have evolved into an awesome program. The one I reccomend it to whosever that wants a photoshop alternative. The plug-in should add enough speed to allow floating-point transformations in HDR and other special workflows. 8 bit throughput should also be increased. But please be careful on testing, because the optimizations the plug-in uses are rather agressive and it is possible to get some small differences in numbers. I have been using the plug-in for years and it works, but it is certainly desireable to have a way to deactivate. The yet-existing flag cmsFLAGS_NOOPTIMIZE disables the plug-in as well. Please let me know if you need assistence on Krita. And keep on that good work! Best regards Marti |
|
From: Noel C. <NCa...@Pr...> - 2020-05-20 13:28:44
|
With only a few minutes effort we merged your updated Little CMS sources into our code and it builds into our plug-in products and runs perfectly. We only have 3 .c files where we (minimally) modify your code e.g., to hand-optimize for better performance or eliminate warnings as our compiler is set to build as C++ and emit maximum warnings and code analyzer output. If only other libraries were this clean and functional. Thank you, Marti and all who have contributed. -Noel Carboni ProDigital Software -----Original Message----- From: mar...@li... <mar...@li...> Sent: Tue, May 19, 2020 3:50 PM To: Lcms List <lcm...@li...> Subject: [Lcms-user] Release candidate of lcms2-2.10 available Hi there, After a long period of inactivity, I am happy to announce the imminent release of lcms2-2.10. The release candidate is available here: http://www.littlecms.com/lcms2-2.10rc1.tar.gz It includes bug fixes and some compilation aids, like the possibility of removing the "register" modifier. MD5 is now accesible in API. PostScript CSA generation is also much better, thanks to Philipp Knechtges. This solves historical performance issues on PostScript which affect many intepreters, Camelot, Ghostscript... Maybe the biggest difference of 2.10 with other releases lies in the bundle with the "fast float" plug-in. Previouly released as a commercial package, the "fast float" plug-in increases floating point performance significantly. Thet means, you call a function when initializing your code and you get a throughput gain when doing floating point transforms. The plug-in has also other features like dithered output or fast 8 bit RGB transforms. There is a test bed in the plug-in directory that shows and measures the throughput gain in your target computer. I have decided to releases this plug-in AS OPEN SOURCE UNDER GPL3 LICENCE. Please check the license carefully before including the code in your applications. This is only on the plug-in, the lcms2 core is still under MIT license. In case of doubt you can contact me on this mailing list or by using the mail info { at } littlecms { dot } com If the release candidate is ok for all you, I will proceed with the official in a very few. Best regards Marti Maria The LittleCMS Project http:\www.littlecms.com _______________________________________________ Lcms-user mailing list Lcm...@li... https://lists.sourceforge.net/lists/listinfo/lcms-user |
|
From: Boudewijn R. <bo...@va...> - 2020-05-20 12:01:10
|
On woensdag 20 mei 2020 13:34:02 CEST Richard Hughes wrote: > On Tue, 19 May 2020 at 20:50, <mar...@li...> wrote: > > http://www.littlecms.com/lcms2-2.10rc1.tar.gz > > Work great here, thanks. All the colord self tests pass with this installed. Same here -- works fine, all related unittests in krita pass. > > I have decided to releases this plug-in AS OPEN SOURCE UNDER GPL3 > > LICENCE. Please check the license carefully before including the code > > in your applications. > > Less awesome. :( Whilst I really appreciate the "gift" of the fast > math plugin, if it was "LGPL v2+" I could unconditionally enable it in > colord. Obviously the L in the LGPLv2+ means it can be used in > non-free software (which is probably why you chose the * variant) but > it means it can be used by the animation studios and places like that. For Krita it's perfect, and subjectively speaking, it makes everything feel smoother :-) -- https://www.krita.org |
|
From: Richard H. <hug...@gm...> - 2020-05-20 11:34:21
|
On Tue, 19 May 2020 at 20:50, <mar...@li...> wrote: > http://www.littlecms.com/lcms2-2.10rc1.tar.gz Work great here, thanks. All the colord self tests pass with this installed. > MD5 is now accesible in API. Do you mean something like cmsSetHeaderProfileID? > Maybe the biggest difference of 2.10 with other releases lies in the > bundle with the "fast float" plug-in. Yes! > I have decided to releases this plug-in AS OPEN SOURCE UNDER GPL3 > LICENCE. Please check the license carefully before including the code > in your applications. Less awesome. :( Whilst I really appreciate the "gift" of the fast math plugin, if it was "LGPL v2+" I could unconditionally enable it in colord. Obviously the L in the LGPLv2+ means it can be used in non-free software (which is probably why you chose the * variant) but it means it can be used by the animation studios and places like that. I really don't want to come across ungrateful, as it's your gift to give, not the receiver to set conditions. Richard. |
|
From: <mar...@li...> - 2020-05-19 19:48:45
|
Hi there, After a long period of inactivity, I am happy to announce the imminent release of lcms2-2.10. The release candidate is available here: http://www.littlecms.com/lcms2-2.10rc1.tar.gz It includes bug fixes and some compilation aids, like the possibility of removing the "register" modifier. MD5 is now accesible in API. PostScript CSA generation is also much better, thanks to Philipp Knechtges. This solves historical performance issues on PostScript which affect many intepreters, Camelot, Ghostscript... Maybe the biggest difference of 2.10 with other releases lies in the bundle with the "fast float" plug-in. Previouly released as a commercial package, the "fast float" plug-in increases floating point performance significantly. Thet means, you call a function when initializing your code and you get a throughput gain when doing floating point transforms. The plug-in has also other features like dithered output or fast 8 bit RGB transforms. There is a test bed in the plug-in directory that shows and measures the throughput gain in your target computer. I have decided to releases this plug-in AS OPEN SOURCE UNDER GPL3 LICENCE. Please check the license carefully before including the code in your applications. This is only on the plug-in, the lcms2 core is still under MIT license. In case of doubt you can contact me on this mailing list or by using the mail info { at } littlecms { dot } com If the release candidate is ok for all you, I will proceed with the official in a very few. Best regards Marti Maria The LittleCMS Project http:\www.littlecms.com |
|
From: <mar...@li...> - 2020-05-18 12:52:15
|
Hi, It seems to me that this code is reading the lab pixelss from the file format, doing some math on floating point with those values and then filling a cmsCIELab structure, which is also floating point. Then it performs a color transform to convert to RGB 8. You can do that in this way but is extremly inefficient. Rather, I would investigate how the file format stores Lab in 8 and 16 bits and convert it to Lab16 V4 ICC format, which is documented in ICC spec and Lcms manual. You don´t need floats at all to do this. Then doing the color transform from Lab16 The throughput gain can be times x4 or more. Hope that helps Marti Quoting Aaron Boxer <bo...@gm...>: > Hello! > This isn't strictly an lcms question, but I was wondering if anyone here > can give me some insight into a few lines of code I've inherited in my > project that use > lcms to convert Lab to RGB: > > https://github.com/GrokImageCompression/grok/blob/master/src/bin/common/color.cpp#L742 > > This code works for 8 bit Lab but not for 16 bit and I am trying to fix > this. I am particularly wondering about the three constants 100, 170 and > 200. > > Any insight would be greatly appreciated. > Thanks! > Aaron |
19 messages has been excluded from this view by a project administrator.
![https://www.inedit.com/wp-content/uploads/2020/03/Untitled-1-4.png"></div></div><div><div](https://www.inedit.com/wp-content/uploads/2020/03/Untitled-1-4.png"></div></div><div><div){kind=link}
![https://www.inedit.com/wp-content/uploads/2020/03/Untitled-1-4.png"](https://www.inedit.com/wp-content/uploads/2020/03/Untitled-1-4.png"){kind=link}