Every module advertises its input, output and working colour spaces to the pixelpipe and conversion are done on-the-fly when needed. Don't bother about it.
Yet, you still need to ensure you do the right pixel operation at the right time. Details : https://github.com/darktable-org/darktable/pull/3075#issuecomment-538410131 and https://github.com/darktable-org/darktable/pull/2905#issue-313652085. Upcoming video in preparation about that. Good luck, Aurélien. Le 11/11/2019 à 22:14, Coding Dave a écrit : > What would help I think is if each module tells the color space it > expects and the one it returns. In my limited knowledge and > understanding I think there must be a module that gets color space A > as input and returns color spacd B as output. But I might be wrong. > > Cheers > > jys <junkyardspar...@yepmail.net <mailto:junkyardspar...@yepmail.net>> > schrieb am Mo., 11. Nov. 2019, 22:08: > > > > On Mon, Nov 11, 2019, at 12:43, Keresztes Barna wrote: > > Hi, > > Can somebody summarize me the stages of the pixel pipe in > darktable, and > > the color space in each stage (if the stages have specific color > spaces). > > There's an early basic overview of the theory behind it here: > https://github.com/darktable-org/darktable/pull/2905 > > -- > jys > > ___________________________________________________________________________ > darktable developer mailing list > to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > <mailto:darktable-dev%2bunsubscr...@lists.darktable.org> > > > ___________________________________________________________________________ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
