On Sun, Dec 1, 2013 at 6:44 AM, Tobias Ellinghaus <[email protected]> wrote:
> Am Samstag, 30. November 2013, 17:47:24 schrieb Teodor Petrov:
> > On 11/30/2013 09:59 AM, johannes hanika wrote:
> > > no. you can always run --library another.db if you need to.
> >
> > Do you have some page where you have a description for what is stored in
> > the library.db file?
>
> No, there is nothing like that. If you are familiar with SQL you can use
>
> sqlite3 ~/.config/darktable/library.db
> .schema
>
> > > 2. I don't seem to like the idea of placing the xmp files next to
> the
> > > original image.
> > >
> > > you can switch off writing of those files completely. i highly
> > > discourage you do so.
> > >
> > > RawStudio here does it better, by placing them in a .rawstudio
> > >
> > > folder. Do you
> > >
> > > plan to implement this feature, too?
> > >
> > > no, why?
> >
> > I don't want to switch them off, just I don't want to see them when I
> > browse files on the file-system.
>
> There is nothing we can do for you, sorry.
>
> > > 3. A bug report: I've deleted several images on disk after I've
> loaded
> > > them in DT
> > >
> > > and now I'm getting the skull icon.
> > >
> > > not a bug.
> > >
> > > How can I get rid of it?
> > >
> > > select them and remove them from the database (right panel `selected
> > > image[s]') or delete your db. all information is in the db, xmp are
> > > backup. so as long as you don't delete both you should still have your
> > > edits.
> >
> > Would you like to add a command that does something like "delete all
> > skulled images"?
>
> I could imagine using Lua for that. Maybe it would need an additional flag
> in
> the image struct, so it might be a feature for the future.
>
https://github.com/darktable-org/darktable/blob/master/tools/purge_non_existing_images.sh
> > > true, that's an old feature request, but ctrl+mousewheel to zoom out
> > > and then scrolling works well enough so it never got implemented so
> far.
> >
> > Do you have a ticket/issue number, where I can vote for it?
>
> No idea, search through redmine [0]. However, keep in mind that adding a
> "me2"
> to a ticket will add bad karma to it so the chances are lower that we will
> work on it. No one likes people telling others what to do.
>
> > > 5. The new focus detection feature is good, but I suppose
> > > focus-peaking like
> > >
> > > preview would be better. I don't think the stylized rectangles
> are
> > >
> > > too useful.
> > >
> > > care to elaborate on this? i didn't parse it. `focus-peaking like'?
> >
> > Some newer mirror-less cameras have this focusing mode
> > Here is an example http://www.youtube.com/watch?v=yWHDEOLREGk
>
> Magiclantern has something like that, too. It would be nice indeed. And
> some
> day we might even enable it for tethering then.
>
> [...]
>
> > > the wiki that you have a plan to fixing my complaints about it.
> > >
> > > 3. Do you plan to add "free panning"
> > >
> > > ? you mean zoom out more than zoom-to-fit? try ctrl-mousewheel or the
> > > dropdown in the navigation view.
> > >
> > > or "panning passed the border" feature?
> > >
> > > It is pretty annoying to edit mask curves without it.
> >
> > Gimp has this feature, so I'll try to use it as an example:
> > 1. Load an image in gimp
> > 2. Zoom to 400%
> > 3. Use the middle mouse button an pan the image so you can see the
> borders
> >
> > In gimp you can see empty space next to the borders/edges of the image.
> > In DT you can't - the panning stops when the border of the image reaches
> the
> > border of the view-port/control. This is very limiting when I'm editing a
> > mask's
> > that has control points outside of the image.
> >
> > BTW: I've found the ctrl-mouse-wheel zoom-out, but this is just a
> > workaround, not a fix for
> > the problem.
>
> Ack, this would be nice. Please file a feature request under [0]. It might
> be
> quite easy to enable that.
>
> > > 4. Do you plan to add the possibility to enter numerical values
> > > with the
> > >
> > > keyboard. I know you like to use fancy UI, but this
> > >
> > > right click, type. we have a blinking cursor for this now.
> >
> > Oh, another of those hidden features. Probably displaying the original
> > number next to the cursor
> > will make it less hidden.
>
> I don't like this idea. I tried it when adding the cursor, but it was
> distracting and had a bad user experience since you either had to delete
> the
> old value before typing in the new one, or you would see a value, started
> typing and the old one suddenly disappears. That could be "fixed" by adding
> selectable text, so you could preselect the old one and make it
> replaceable by
> default, but that would be even more distracting.
> So at the end of the day it boils down to our usual approach "a little less
> discoverability is fine if it suits the workflow of the regular users". In
> other
> words: RTFM. :D
>
> > > 5. The range for exposure is quite useless - from -18 to 18, I
> think
> > > that a range
> > >
> > > from -3 to 3 will be a lot more useful.
> > >
> > > you're no big fan of hdr images? i need the range as it is.
> >
> > Hm, probably I don't see a use case for this, but most of the times when
> > I need to change the
> > exposure I want to do it with 1/3, 1/5 or 1 stop and when the slider's
> > range is 36 stops this is
> > impossible with the slider, I have to get in two advanced editing mode.
> >
> > Care to post a work-flow tutorial for your case where you need to change
> > the exposure of an
> > image with 18 stops?
>
> As Jo said: HDR images [1]. They typically span a much wider exposure
> range,
> so ±18 EV isn't that uncommon.
>
> > > 6. There is no scroll in the filmstrip at the bottom and so
> navigating
> > > hundreds
> > >
> > > of images is not easy.
> > >
> > > 7. Changing an image from the filmstrip requires a double click,
> > > but I'm
> > > trying
> > >
> > > to change them by single click and I'm always surprised that a
> > >
> > > double
> > > click
> > >
> > > is required.
> > >
> > > well, we get that a lot (people being surprised by random things in
> > > one or the other contradicting way).
> >
> > Do you plan to minimize this or this will state the way it is.
>
> It will stay as it is. Single click won't work for film strip for two
> reasons:
> - lighttable uses double click, so it would break user experience
> - you could no longer select images in the filmstrip.
>
> > I guess I can easily fix this double-click problem and provide a patch
> > which allows the user to
> > change the default if he/she doesn't like it. Would this be acceptable?
>
> No, see above. And a double click doesn't take that much longer.
>
> > Best regards,
> > Teodor
>
> Tobias
>
>
> [0] http://darktable.org/redmine/issues/
> [1] http://en.wikipedia.org/wiki/High-dynamic-range_imaging
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
> _______________________________________________
> Darktable-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/darktable-users
>
>
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
