[Alt-photo] Curves and text files in QTR

Clay Harmon clay at clayharmon.com
Thu May 25 21:15:05 UTC 2017


About 99% sure that it compiles the .acv file when it converts the ink descriptor file to a .quad file, which is the translation layer the driver uses to convert image %gray to specific amounts of ink delivered by the nozzles.

Clay
> On May 25, 2017, at 5:05 PM, Felix Martin via Alt-photo-process-list <alt-photo-process-list at lists.altphotolist.org> wrote:
> 
> Yes I keep several documented versions of each iteration (for certain papers, landscape, skin tones, and effects I like).
> .
> 
> I just thought it would be very cool to be able to just change the curve and do the last fine running for those moments when I just printed my final neg and
> I say, this is perfect, but for this image but I would love to drop a bit the mid point just a tad or raise mid-shadows without having to recompile.
> 
> This will allow me to keep all my text files intact and just mess visually with the .acv and copy into the right folder.
> 
> Would love to know with certainty if the compiled file refers to the .acv file externally or if it gets embedded in the compile.
> 
> Thanks all.
> 
> -Felix
> 
> 
>> On May 25, 2017, at 1:47 PM, Don Bryant via Alt-photo-process-list <alt-photo-process-list at lists.altphotolist.org> wrote:
>> 
>> I agree with Keith regarding the .acv file.
>> 
>> However this does raise the issue of learning and using version control
>> software.
>> 
>> Now that everyone's eyes are glazing over I'll leave it at that. But RCS is
>> easy to use and available across most platforms. Also available is VCS and
>> git.
>> 
>> 
>> 
>> 
>> 
>> On May 25, 2017 4:23 PM, "Keith Schreiber via Alt-photo-process-list" <
>> alt-photo-process-list at lists.altphotolist.org> wrote:
>> 
>>> I'm not sure about this, but I think that if he makes a change to the .acv
>>> curve file but does not rename it or move it then it is not necessary to
>>> reinstall the QTR curve text file. The QTR curve refers to the .acv
>>> on-the-fly, so as long as the .acv referred to is available in the location
>>> used in the installed curve (I am assuming that this is in the GrayCurve
>>> field or something similar) it will use whatever in in the .acv file at the
>>> time it is used.
>>> 
>>> But if you care about keeping track of your progress and changes, I don't
>>> think using the same name for a different .acv is good practice. Each
>>> variation should get a new variation on the name too, in which case the
>>> text file would be modified also to refer to the new .acv name, and the
>>> curve should then get a new name too. In this case you do need to run the
>>> installer each time you make a new iteration.
>>> 
>>> Cheers,
>>> Keith
>>> 
>>> 
>>>> On May 25, 2017, at 1:54 PM, Kees Brandenburg via Alt-photo-process-list
>>> <alt-photo-process-list at lists.altphotolist.org> wrote:
>>>> 
>>>> Hi Felix,
>>>> 
>>>> Yes you have to run the installer again when you change anything in the
>>> txt file or curve.
>>>> 
>>>> Kees
>>>> 
>>>> 
>>>> 
>>>>> My question is If I decide to make a change in the curve file, is it
>>> enough to just replace the curve file in the directory or do I have to run
>>> the
>>>>> Install program to “embed” the curve data into the driver?
>>>> _______________________________________________
>>>> Alt-photo-process-list | altphotolist.org
>>> 
>>> _______________________________________________
>>> Alt-photo-process-list | altphotolist.org
>>> 
>> _______________________________________________
>> Alt-photo-process-list | altphotolist.org
> 
> _______________________________________________
> Alt-photo-process-list | altphotolist.org



More information about the Alt-photo-process-list mailing list