[darktable-user] Wish: darktable with viewing screen and control screen
Le 07/12/2018 à 17.08, Anton Aylward a écrit : IF AND ONLY IF you want more screen real estate I' do recommend a one-screen-at-a-time approach. A 27-inch screen for viewing and side 17-inch screen for controls is very nice to work with. I can do that with GIMP. I'm just sad that DT doesn't have the ability to 'tear off' the controls and move them to a side screen. Thanks Anton for sharing that idea! *Hardware setup* I have a 27-inch screen optimized for color rendition and an ordinary 15-inch laptop barely calibrated. *Observation* Part of the color-optimized screen is covered with controls. Sure I can click small (too small) triangles to collapse panels or use Tab. And sometimes I do. *Wish* The idea naturally came to dedicate the big screen to the picture, and the smaller screen to the controls. I sometimes use Gimp and to that. *Implementation* There are many ways to imagine such a separation in darktable. Toolbox windows with special properties etc may represent a significant refactoring effort, in code, in creating a new consistent and complete user experience, etc. Perhaps one approach may be much simpler: just extract the center image view of darktable to place it onto its own window, keep the rest as is (existing window without the extracted center view). What do you think? (I hope to clear time to contribute to darktable, perhaps in the coming year.) Cheers! -- Stéphane Gourichon darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Darktable crashes
It’s been a while since I started this thread. Now that winter has arrived I’ll have time to work on this. I’ve just installed 2.4.4 in Mac OS X 10.14.1 Here’s the crash report in Terminal. peter-whites-mac-pro-2:~ peterwhite$ /Applications/darktable.app/Contents/MacOS/darktable (process:74069): GLib-GObject-CRITICAL **: 08:40:02.876: g_object_set: assertion 'G_IS_OBJECT (object)' failed (darktable-bin:74069): GLib-GObject-WARNING **: 08:40:04.287: invalid cast from 'GtkMenuBar' to 'GtkWindow' (darktable-bin:74069): Gtk-CRITICAL **: 08:40:04.287: gtk_window_add_accel_group: assertion 'GTK_IS_WINDOW (window)' failed darktable-bin(74069,0x7c641000) malloc: Incorrect checksum for freed object 0x7fdcd200: probably modified after being freed. Corrupt value: 0x darktable-bin(74069,0x7c641000) malloc: *** set a breakpoint in malloc_error_break to debug Abort trap: 6 peter-whites-mac-pro-2:~ peterwhite$ Thanks for any assistance. > On Apr 10, 2018, at 1:56 PM, August Schwerdfeger > wrote: > > Try opening up a terminal and entering the command > > /Applications/darktable.app/Contents/MacOS/darktable > > Then if Darktable crashes it will output the crash report to the terminal. > > -- > August Schwerdfeger > aug...@schwerdfeger.name > > On Tue, Apr 10, 2018 at 12:43 PM, peter white > wrote: > No report pops up. Darktable just vanishes. > > Peter White > > >> On Apr 10, 2018, at 1:24 PM, Tobias Ellinghaus wrote: >> >> Am Dienstag, 10. April 2018, 16:49:17 CEST schrieb peter white: >>> I’m running OS X 10.13.4 >>> >>> Darktable crashes within a minute or so of starting the program. What can be >>> done? >> >> Showing the crash report would be a good start. >> >>> Thanks, >>> >>> Peter White >> >> Tobias > > > darktable user mailing list to unsubscribe send a mail to > darktable-user+unsubscr...@lists.darktable.org > > > > darktable user mailing list to unsubscribe send a mail to > darktable-user+unsubscr...@lists.darktable.org darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.or
Re: [darktable-user] "Inconsistent Output" Message
Thanks Ulrich for this explanation. This clarifies and I see now two clearer issues: * 1 this message is unclear and conveys a more alarming message than needed. * 2 the user does not know that changing anything triggers a re-render without any bad consequence * 3 changing anything feels like a workaround. The user should have an option to just re-render. I see two ways to fix these issues : * I guess the developers have considered fixing the issue (increasing the timeout ? Retrying the computation ?) and not done it for good reasons. * A simpler way:changing the wording. Perhaps something like: "Rendering timed out. You can continue adjusting parameters or [Retry]." with [Retry] being a clickable button that just requests another render without actually changing any parameter. This way, the user is not needlessly alarmed (fixing issue 1) and know they can just continue adjusting I might be stating the obvious, or not, since choosing good words (towards a user that is not a developer) is not that obvious and sometimes overlooked. In case it's useful I'm happy to add my two cents. Cheers ! -- Stéphane Le 09/12/2018 à 19.46, Ulrich Pegelow a écrit : Am 09.12.18 um 08:59 schrieb Stéphane Gourichon: My guess is a memory corruption error in some part of darktable. Of course it would be nice if somehow could trace this. (I'm willing to, but currently not using darktable much, and quite busy with other projects.) Well, no. The error message appears when darktable is not able to synchronize the two pixelpipes in darkroom mode: the preview one for the navigation window and the "full" one for the center view. Both pixelpipes normally run asynchronously as separate processes. Some of darktable's modules require a synchronization: the full pixelpipe needs to wait at certain points until the preview pixelpipe produces the needed data. Without that missing data the module in the full pixelpipe would produce wrong results, the output of the two pixelpipes would no longer be consistent. In some cases synchronization fails, e.g. when the full pixelpipes needs to wait too long and a pre-defined timeout value is exceeded (config variable pixelpipe_synchronization_timeout). If that happens the above warning message is displayed. However, this is of no big concern. Typically with the next processing step all is good again. Any zooming in or out, panning, (de-)activating of modules or any value change is sufficient. Ulrich -- Stéphane Gourichon darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] "Inconsistent Output" Message
Am 09.12.18 um 08:59 schrieb Stéphane Gourichon: My guess is a memory corruption error in some part of darktable. Of course it would be nice if somehow could trace this. (I'm willing to, but currently not using darktable much, and quite busy with other projects.) Well, no. The error message appears when darktable is not able to synchronize the two pixelpipes in darkroom mode: the preview one for the navigation window and the "full" one for the center view. Both pixelpipes normally run asynchronously as separate processes. Some of darktable's modules require a synchronization: the full pixelpipe needs to wait at certain points until the preview pixelpipe produces the needed data. Without that missing data the module in the full pixelpipe would produce wrong results, the output of the two pixelpipes would no longer be consistent. In some cases synchronization fails, e.g. when the full pixelpipes needs to wait too long and a pre-defined timeout value is exceeded (config variable pixelpipe_synchronization_timeout). If that happens the above warning message is displayed. However, this is of no big concern. Typically with the next processing step all is good again. Any zooming in or out, panning, (de-)activating of modules or any value change is sufficient. Ulrich darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Inconsistent Output Message
yes usually when using the mouse wheel. dt 2.4.4 , Ubuntu 18.04.1 LTS Στις Παρ, 7 Δεκ 2018 στις 11:57 μ.μ., ο/η I. Ivanov έγραψε: > > On 2018-12-07 09:00, David Vincent-Jones wrote: > > > > I occasionally get the message 'Inconsistent Output' on my screen ... > > most often when I am going through a screen zoom with the mouse wheel. > > Apparently there is no damage done. Anybody else seeing this? > > > I have seen it too. > > > > darktable 2.5.0+979~g22ab1bc66 > > > DT 2.4.4 on Ubuntu 16.04 > > > > David > > > Regards, > > B > > > > > > > > > darktable user mailing list to unsubscribe send a mail to > > darktable-user+unsubscr...@lists.darktable.org > > > darktable user mailing list > to unsubscribe send a mail to > darktable-user+unsubscr...@lists.darktable.org > > -- Nickolas M. Vassou darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Bulk export without crop settings
* Terry Duell [12-08-18 23:00]: > Hello Patrick, > > On Sun, 09 Dec 2018 13:18:43 +1100, Patrick Shanahan > wrote: > > Thanks for your advice. > > > > > backup your xmp files, > > run a script to remove the crop information from the xmp files > > import the images into a temporary library > > export the images > > remove the temp library > > replace the altered xmp files from backup > > > > This leads me to a couple of questions. > Is there a reference manual for the xmp files, detailing the syntax? > Looking at an xmp file I don't see any reference to 'crop', but I do see > 'clipping'. > Is 'clipping' what I'm looking for, and is it enough to simply set > 'enabled=0'? not tried, but take a throw-away image for testing and see what happens. I assume that "clipping" is the crop module, that is part of the module name, but shortened. but should be simple to test. I am *not* a developer, just an old user and see the possibility that the above approach might work. someone else mentioned making a "style" but I am not that familiar with using styles. note that you probably need to remove all the lines in the "clipping" group. but you should be able to determine that when you test. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Registered Linux User #207535@ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] 2.6.0rc1 windows and macos versions are available
Hi Hervé, > A naive question : now 2.6 is somehow 'announced for Christmas', for us > average 2.4 users is there a way to safely switch to 2.5? Why 2.5? The next version being prepared is 2.6. 2.5 is a dev release. 2.6.0rc1 is somehow a recent 2.5. > (I saw the hypnotic new features on 2.6, then woke up to the real world, > knowing my auto-updating would wait forever ;-) Going to 2.6 is possible depending on the platforms. But note that you cannot go back as the db has changed. So be sure to backup in case 2.6 is not ready for you (Windows versions has issues for example). For Linux the only solution is to build yourself for now or wait for the packager to propose a binary distribution for your platform. There is binary for Fedora if I'm not mistaken. Packagers will correct me if I'm wrong :) Best, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] 2.6.0rc1 windows and macos versions are available
A naive question : now 2.6 is somehow 'announced for Christmas', for us average 2.4 users is there a way to safely switch to 2.5? (I saw the hypnotic new features on 2.6, then woke up to the real world, knowing my auto-updating would wait forever ;-) H. Le 08/12/2018 à 13:56, Pascal Obry a écrit : > Just a quick note that the MacOS (thanks to parafin) and Windows > (thanks for Peter Budai) version are now available on our GitHub. > > Enjoy! And report bugs :) > darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Bulk export without crop settings
Hi, I would create a style consisting of the crop and rotate module being off, and apply that in the export style setting. Kindly, Anders søndag den 9. december 2018 02.58.03 CET skrev Terry Duell: > Hello All, > I have a few thousand family photographs, all shot in raw and processed in > darktable. > What I would like to do is pass these on to family members as jpg, with > all the darktable processing with the exception of crop settings. > I have experimented with calling darktable-cli from a bash script, and > that provides an easy way of doing the export to a nominated path, but it > does so utilising the current crop settings for each image. > If I exclude the .xmp files from the list passed to the bash script the > exports are uncropped but have none of the other darktable post processing. > Is there a relatively simple way of excluding any crop settings whilst > keeping all other PP for each individual image? > > Cheers, darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
