Re: [darktable-dev] Redmine issues ?

Hello Nicholas, Thanks for the timely observation. As I have said in my earlier reply to Patrick Shanahan ... If that is the case then a re-direct from the Redmine index page to github would seem to be prudent, and perhaps a statement to that effect on the 'News' pages of the darktable website.

Re: [darktable-dev] Redmine issues ?

On 03/09/2019 16:12, Patrick Shanahan wrote: * Richard Hobday [09-03-19 10:57]: Hmm Good to know that I am not the only one. Anyone know how to resolve this? On 03/09/2019 14:46, Dimitri Gathy wrote: I have the same problem & i can't login nor change my password... No email sent Le

Re: [darktable-dev] Redmine issues ?

* Richard Hobday [09-03-19 10:57]: > Hmm > > Good to know that I am not the only one. > > Anyone know how to resolve this? > > On 03/09/2019 14:46, Dimitri Gathy wrote: > > I have the same problem & i can't login nor change my password... No > > email sent > > > > Le mer. 28 août 2019 à 1

Re: [darktable-dev] Redmine issues ?

Hmm Good to know that I am not the only one. Anyone know how to resolve this? On 03/09/2019 14:46, Dimitri Gathy wrote: I have the same problem & i can't login nor change my password... No email sent Le mer. 28 août 2019 à 10:50, Richard Hobday mailto:rlhob...@gmx.co.uk>> a écrit :

[darktable-dev] Redmine issues ?

Redmine seems to have an 'issue' when I try to access it. https://redmine.darktable.org/projects/darktable gives this : Internal error An error occurred on the page you were trying to access. If you continue to experience problems please contact your Redmine administrator for assistance.

[darktable-dev] Redmine

I was looking to see if a specific feature has been requested, and noticed a few tickets which stated they should be closed in the comments. I have a little bit of free time, and I no longer do C coding. So can I help manage redmine? If yes, is there any documentation on how it is managed?

Re: [darktable-dev] Redmine Certificate expired ....

Richard Hobday schrieb am 19.08.2018 um 10:04: For info ... redmine.darktable.org uses an invalid security certificate. The certificate expired on August 19, 2018, 7:58 AM. The current time is August 19, 2018, 9:02 AM. Error code: SEC_ERROR_EXPIRED_CERTIFICATE __

[darktable-dev] Redmine Certificate expired ....

For info ... redmine.darktable.org uses an invalid security certificate. The certificate expired on August 19, 2018, 7:58 AM. The current time is August 19, 2018, 9:02 AM. Error code: SEC_ERROR_EXPIRED_CERTIFICATE ___ dark

Re: [darktable-dev] Redmine

Am Freitag, 17. November 2017, 08:08:34 CET schrieb Timothy Spear: > Is it useful for me to verify fixed bugs and comment on the bug? Absolutely! > Tim Tobias [...] signature.asc Description: This is a digitally signed message part.

Re: [darktable-dev] Redmine

Is it useful for me to verify fixed bugs and comment on the bug? Tim On Fri, Nov 17, 2017 at 3:23 AM, Tobias Ellinghaus wrote: > Am Freitag, 17. November 2017, 00:14:42 CET schrieb n61...@gmail.com: > > I reported a bug on redmine for the Windows release. However the version > > number is not c

Re: [darktable-dev] Redmine

Am Freitag, 17. November 2017, 00:14:42 CET schrieb n61...@gmail.com: > I reported a bug on redmine for the Windows release. However the version > number is not correct. Should Windows release be against the git master/ > git stable, or what version number? The Windows snapshots are git master. >

[darktable-dev] Redmine

I reported a bug on redmine for the Windows release. However the version number is not correct. Should Windows release be against the git master/ git stable, or what version number? Tim ___ darktable developer mailing l

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

Hi Jo, sorry for the late reply - time’s always an issue, here too. ;-) Full 20MP export is around 16 secs on my very weak machine, pretty much equivalent to the time needed for the equalizer module. As to the fftw3 dependency, I made it fully optional now in my latest commit. cmake files are ad

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

hi ingo! wow, that's great news :) unfortunately i only found time to have a very quick look, i hope things cool down a little here near end of year. so now wer'e talking what time frame for a full 20MP export? 10-20sec? we'll need to discuss what to do with the additional fftw dependency. i gues

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

Hi Jo, In the meanwhile I applied FFTW, and I found some other ways to save processing time. All in all, processing time is now roughly half, and it’s usable even on my weak machine. The description in the dropbox location is adapted accordingly. Again, I’d like to thank François Guerraz for gi

Re: [darktable-dev] Redmine #11526 - Color profile for Fuji X-M1

On Tue, May 16, 2017 at 2:25 PM, Rolf Wuerdemann wrote: > Hi, Hi. > at first thanks a lot for your work. > > I don't know if this is the right mailing list, but I like to > ask anyway. > > Roughly 2 1/2 months ago I've submitted the color profile for the > Fuji X-M1 to your redmine installation.

[darktable-dev] Redmine #11526 - Color profile for Fuji X-M1

Hi, at first thanks a lot for your work. I don't know if this is the right mailing list, but I like to ask anyway. Roughly 2 1/2 months ago I've submitted the color profile for the Fuji X-M1 to your redmine installation. I've also asked Pascal de Bruijn if he can take a look at this. Pascal tol

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

nice thanks! will give it a read! -jo On Mon, May 15, 2017 at 6:55 AM, Ingo Liebhardt wrote: > Hi Jo, > > I made a high level description of the algorithm. > You can download it at > https://www.dropbox.com/s/wshrkfhylnikpei/FDC%20high%20level%20desc.pdf?dl=0 > > Together with the code, it shows

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

Hi Jo, I made a high level description of the algorithm. You can download it at https://www.dropbox.com/s/wshrkfhylnikpei/FDC%20high%20level%20desc.pdf?dl=0 Together with the code, it shows quite well how the algorit

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

Hi Jo, If I find some time next weekend, I’ll try to make a high level description of the algorithm. The blog only represents a very-high level description. It basically just sketches out the ideas and cites some references that I used as starting points. But that alone won’t be enough I think,

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

heya, doesn't sound too bad for something that hasn't been optimised at all yet. did you describe what you do on a high level somewhere on your blog? or is the best documentation reading the code? maybe it would be good to do one pass over the high level algorithm to find out whether there may be

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

Hi Jo, OK, here we go, some measurements. And I must admit that they are not too encouraging. see below... > Am 07.05.2017 um 21:57 schrieb Ingo Liebhardt : > > The 30 sec are export time on a full res image. > For darkroom mode, it's slow but usable. It's not that abysmal. :-D > I'll give you t

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

The 30 sec are export time on a full res image. For darkroom mode, it's slow but usable. It's not that abysmal. :-D I'll give you the remaining measurements tomorrow. I do think that there's hope... actually, up to now I was really focusing on the algorithm itself and on demosaicking quality. Code

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

hi, On Mon, May 8, 2017 at 6:33 AM, Ingo Liebhardt wrote: > Hi & thx :-) > > Well my machine I use for this is super-weak: intel core m3, 4.5W TDP. Very > energy efficient :-( Takes around 30 sec with this machine. > It uses openmp. okay :) that's export time on a full res image or for darkroom

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

Hi & thx :-) Well my machine I use for this is super-weak: intel core m3, 4.5W TDP. Very energy efficient :-( Takes around 30 sec with this machine. It uses openmp. It has basically 3 building blocks: 1. Markesteijn 1 pass for obtaining luma and directionality. 2. Some 11x11 correlation filterin

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

heya, nice results! especially the high iso one shows quite a bit more pleasant noise behaviour in the gray center patch. how bad is the performance? do you think it could be improved? does it use SIMD/openmp yet and how promising would an opencl code path be? cheers, jo On Mon, May 8, 2017 at

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

Hi all, Coming back to this old topic, I have the next iteration of my alternative approach to X-Trans demosaicking ready. For those of you who’d like to try, the GitHub fork is at https://github.com/ILiebhardt/darktable There’s a menu item in the dem

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

On Fri, Feb 24, 2017 at 10:52 AM, Ingo Liebhardt wrote: > Hi all, > > For those who want to give it a try, I made some further improvements to > the below-mentioned fork with the experimental approach to X-Trans > demosaicking. > In particular to the issue of colour bleeding found by J Liles, thi

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

Hi all, For those who want to give it a try, I made some further improvements to the below-mentioned fork with the experimental approach to X-Trans demosaicking. In particular to the issue of colour bleeding found by J Liles, this should be much less now. There was also still some hue shift, whi

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

Aha, interesting, thanks! Would you maybe have the raw file for me, I’d like to check something more in-depth? Is this from my very last commit, or the one from the beginning of January? Thx, Ingo > Am 07.02.2017 um 02:35 schrieb J. Liles : > > > > On Sun, Feb 5, 2017 at 2:35 AM, Ingo Liebhar

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

On Sun, Feb 5, 2017 at 2:35 AM, Ingo Liebhardt wrote: > Hi all, > > Thanks again for the feedback, especially to J Liles, which helped me a > lot to find out some issues concerning the filter design. > In the meanwhile, I managed to get rid of the hue shift and of the > textile artifacts. > > A n

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

Hi all, Thanks again for the feedback, especially to J Liles, which helped me a lot to find out some issues concerning the filter design. In the meanwhile, I managed to get rid of the hue shift and of the textile artifacts. A new commit from today is in the (still very experimental) fork at: h

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

On Wed, Dec 21, 2016 at 11:27 AM, J. Liles wrote: > > > On Wed, Dec 21, 2016 at 11:20 AM, J. Liles wrote: > >> >> >> On Wed, Dec 21, 2016 at 11:17 AM, Ingo Liebhardt > > wrote: >> >>> Ah, and by the way @J Liles: could you please explain me a bit more what >>> you mean by ‚textile like artifact‘

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

On Wed, Dec 21, 2016 at 11:20 AM, J. Liles wrote: > > > On Wed, Dec 21, 2016 at 11:17 AM, Ingo Liebhardt > wrote: > >> Ah, and by the way @J Liles: could you please explain me a bit more what >> you mean by ‚textile like artifact‘, I’d like to investigate that one a bit >> more in-depth. >> Thx

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

On Wed, Dec 21, 2016 at 11:17 AM, Ingo Liebhardt wrote: > Ah, and by the way @J Liles: could you please explain me a bit more what > you mean by ‚textile like artifact‘, I’d like to investigate that one a bit > more in-depth. > Thx > > > Am 21.12.2016 um 20:10 schrieb Ingo Liebhardt : > > Hi all,

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

Ah, and by the way @J Liles: could you please explain me a bit more what you mean by ‚textile like artifact‘, I’d like to investigate that one a bit more in-depth. Thx > Am 21.12.2016 um 20:10 schrieb Ingo Liebhardt : > > Hi all, > > Thanks a lot for the feedback, and no worries if it takes y

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

Hi all, Thanks a lot for the feedback, and no worries if it takes you a while testing it. As you see, I’m also progressing rather slowly on my side… It’s still a proof-of-concept and I have quite some items on my to do list, most notably: - the literature mentions training the filters based on

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

On Mon, Dec 19, 2016 at 7:40 PM, J. Liles wrote: > > > On Mon, Dec 12, 2016 at 10:40 AM, Ingo Liebhardt > wrote: > >> Hi all, >> >> Maybe you still remember that I tried an alternative approach to X-Trans >> demosaicking (using guided filtering) in March / April this year… >> In the end, I was n

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

On Mon, Dec 12, 2016 at 10:40 AM, Ingo Liebhardt wrote: > Hi all, > > Maybe you still remember that I tried an alternative approach to X-Trans > demosaicking (using guided filtering) in March / April this year… > In the end, I was not satisfied, and I gave up on that approach. The > problems were

Re: [darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

On 12/12/2016 19:40, Ingo Liebhardt wrote: > Hi all, > > Maybe you still remember that I tried an alternative approach to > X-Trans demosaicking (using guided filtering) in March / April this year… > In the end, I was not satisfied, and I gave up on that approach. The > problems were comparable to

[darktable-dev] Redmine bug #10333 and X-Trans demosaicking re-visited

Hi all, Maybe you still remember that I tried an alternative approach to X-Trans demosaicking (using guided filtering) in March / April this year… In the end, I was not satisfied, and I gave up on that approach. The problems were comparable to the Markesteijn algorithm, and the improvements marg