Hi Ivan,
yes, this is certainly your "masks" test. That's why we always say to to
backup everything before testing.
In your case, I even think that's not masks but multi-instance. This
mean that this concern all tests you may have done on git master.
Best solution would be dropping your db and re
Hi Ammon,
great! We don't have a fixed timeline yet. There is no feature or string
freeze for 1.2 so far. And even after that we should have at least 2-3
weeks. So in total a month or so. You can give me your reply chapter by
chapter. Helps me to do the final changes.
Ulrich
Am 19.02.2013 07:
I can read. I even took a tech-writing class in university. :)
Time, is of course, my enemy. I'm currently sitting with a new-born,
so I can spare a few cycles here and there. What sort of deadline are
we talking?
A
On Mon, Feb 18, 2013 at 10:33 PM, Ulrich Pegelow
wrote:
> Hi,
>
> after some
Hi,
after some rounds of optimization our usermanual is getting close to
what we want to publish with darktable 1.2.
A number of errors have been fixed. However, all authors are non-native
speakers. So there are likely a lot of language related errors still
remaining.
Here we need your help.
I didn't intend them for any sort of machine-based analysis. I developed the
patch when I was having a slow-down of my own and the existsing "-d all" data
didn't have enough data to find the problem.
In the example cited, a time stamp would quickly show whether an SQL statement
was taking a lon
don't think i like these timestamped logs. you'll need a machine to
parse them. the way to profile stuff is to use `darktable -d perf', in
this case it's `darktable -d perf -d lighttable'.
-jo
On Tue, Feb 19, 2013 at 4:48 PM, Kevin wrote:
> The recent discussion in dt-user "lighttable sluggish w
The recent discussion in dt-user "lighttable sluggish with collection based on
multiple tags" made me think that a small patch I developed some time ago
could be of use.
It just places the time since startup at the beginning of each line produced
by dt_print.
A "git diff" is attached.
Cheers,
Manual fixed the known issues of the script.
The result below seems to be ok.
{ "Panasonic", "DMC-G5", Daylight, 0, { 2.343396, 1, 1.618868, 0
} },
{ "Panasonic", "DMC-G5", Cloudy, 0, { 2.45283, 1, 1.532075, 0
} },
{ "Panasonic", "DMC-G5", Shade, 0,{ 2.
Il 19/02/2013 00:06, Ivan Tarozzi ha scritto:
[...]
> So, how library could change this behavior?
> How can I debug if some problem occours? Are presets stored in database?
> Looking in presets windows in dt preference all seems ok.
ops, sorry, my mistake: I just see this output error executing da
Hi,
tryied ask to user ML, but no answer there. So I would try to
investigate my issue myself but I'd like some background info :)
The problem is: importing folder containing DNG files from my pentax k7,
no base correction is applied.
It stops working some day ago, but I can't remember why.
If I
cool, those graphs look fine. i'll push your profile as soon as i get
some time for it.
thanks for profiling!
-jo
On Mon, Feb 18, 2013 at 10:53 PM, Anton Katsarov wrote:
> Hi, all,
>
> Please find attached a noise profile I generated for Canon EOS 650D. I
> do not understand much of these stuff,
Hello DT's
playing around with geotagging i found that all exported files have
GPSLongitude: 0 deg 0' 0.00" E
here the fix for the returned length in dt_exif_read_blob:
(and some braces around the 'then'...)
src/common/exif.cc:
...
Exiv2::Blob blob;
Exiv2::ExifPars
Am 17.02.2013 22:26, schrieb johannes hanika:
> if you ask me, those guys just start 4 threads just in case.
> `MicroSleep' sounds like they're not up to anything useful at this
> time. maybe the call to ioctl indicates that they need to tell the
> device that nothing has happened? or maybe the dev
13 matches
Mail list logo
