Hallöchen!
Pascal de Bruijn writes:
> On Sun, Oct 28, 2012 at 10:43 PM, Torsten Bronger
> wrote:
>
>> [...]
>>
>> Comparing timestamps would be enough for all practical purposes.
>
> Timestamps aren't reliable per-se...
Granted, you can manipulate them, but if you don't do that
deliberately --
Chances are, that there are some leftovers in /opt/darktable that you
should get rid of. So rm -r /opt/darktable and then go back into your
darktable sources and sudo make install again.
Am 28.10.2012 23:42, schrieb Roumano:
> Hi,
>
> Yes exact, The problem disapar with delete all data (rm -r bui
On Sat, Oct 27, 2012 at 4:16 PM, Eric Leblond wrote:
> Hello,
>
> Le samedi 27 octobre 2012 à 13:52 +0200, Pascal de Bruijn a écrit :
>> Hi,
>>
>> I just noticed we don't have white balance presets for the Nikon V1 yet...
>>
>> Would you mind taking a single RAW shot for each white balance preset
On Sun, Oct 28, 2012 at 10:43 PM, Torsten Bronger
wrote:
> Hallöchen!
>
> Pascal de Bruijn writes:
>
>> On Sun, Oct 28, 2012 at 9:29 PM, Torsten Bronger
>> wrote:
>>
>>> Pascal de Bruijn writes:
>>>
[...]
I think this is by design. Darktable's primary source of
information is
On 29/10/12 07:43 AM, Torsten Bronger wrote:
>> On Sun, Oct 28, 2012 at 9:29 PM, Torsten Bronger
>> wrote:
>>> Pascal de Bruijn writes:
I think this is by design. Darktable's primary source of
information is it's database. We write the .xmp files for
redundancy and easy interchange
On 28.10.2012 02:32, johannes hanika wrote:
> On Wed, Oct 24, 2012 at 12:16 PM, Richard Levitte wrote:
>> For degrees, why not use ° ?
>
> cool, how do you even type that :) i copied it out of your email and pushed
> it.
I get it by pressing AltGr+Shift+0. YMMV.
--
Mikko
Hallöchen!
Pascal de Bruijn writes:
> On Sun, Oct 28, 2012 at 9:29 PM, Torsten Bronger
> wrote:
>
>> Pascal de Bruijn writes:
>>
>>> [...]
>>>
>>> I think this is by design. Darktable's primary source of
>>> information is it's database. We write the .xmp files for
>>> redundancy and easy interc
Hi,
Yes exact, The problem disapar with delete all data (rm -r build was not
solve)
rm -rf *
git reset --hard HEAD
git pull
./build.sh
cd "./build"
sudo make install
Now i have got some invalid pointer, it's something known ?
(when i want from lightroom to darkroom for exemple ) :
If not, ho
On Sun, Oct 28, 2012 at 9:29 PM, Torsten Bronger
wrote:
> Hallöchen!
>
> Pascal de Bruijn writes:
>
>> [...]
>>
>> I think this is by design. Darktable's primary source of
>> information is it's database. We write the .xmp files for
>> redundancy and easy interchangeability between Darktable users
thanks for that. the obvious workaround is to delete
~/.cache/darktable/mipmaps.* (or only the one that belongs to your
current db, if you know which).
jo.
On Mon, Oct 29, 2012 at 9:34 AM, Andreas Schrell wrote:
> done. #9027
>
> Andreas
>
> Am 28.10.2012 20:18, schrieb Ulrich Pegelow:
>> Am 28.
Hallöchen!
Pascal de Bruijn writes:
> [...]
>
> I think this is by design. Darktable's primary source of
> information is it's database. We write the .xmp files for
> redundancy and easy interchangeability between Darktable users.
What's the rationale of this precedence? I can imagine only
use
done. #9027
Andreas
Am 28.10.2012 20:18, schrieb Ulrich Pegelow:
> Am 28.10.2012 19:18, schrieb Andreas Schrell:
>> Hm,
>>
>> I did that. And also I did delete the database for testing.
>>
>> When I enter darkroom the white balance looks ok. In lighttable mode all
>> images look wrong until I ent
Most likely you did not delete ./build
Please do so. From within darktable's source directory:
rm -r ./build
If even this does not help, there might be an issue with your local git
checkout. You may need to start anew with a completely fresh git pull
after having deleted all your local darktable
Hi Ulrich,
Making this step create a error :
./build.sh --prefix /opt/darktable/
[ 34%] Building C object
src/CMakeFiles/lib_darktable.dir/dtgtk/tristatebutton.c.o
[ 34%] /home/roumano/bin/darktable/src/develop/develop.c: In function
‘auto_apply_presets’:
/home/roumano/bin/darktable/src/develop
Am 28.10.2012 19:18, schrieb Andreas Schrell:
> Hm,
>
> I did that. And also I did delete the database for testing.
>
> When I enter darkroom the white balance looks ok. In lighttable mode all
> images look wrong until I enter darkroom mode with them. I have enabled
> raw thumbnails in the prefer
On Sun, Oct 28, 2012 at 7:58 PM, Pascal de Bruijn wrote:
> On Sun, Oct 28, 2012 at 12:37 PM, Andreas Schrell wrote:
>> PS: loading from the xmp file manually after import works.
>
> I think this is by design. Darktable's primary source of information
> is it's database. We write the .xmp files fo
On Sun, Oct 28, 2012 at 12:37 PM, Andreas Schrell wrote:
> PS: loading from the xmp file manually after import works.
I think this is by design. Darktable's primary source of information
is it's database. We write the .xmp files for redundancy and easy
interchangeability between Darktable users.
Hm,
I did that. And also I did delete the database for testing.
When I enter darkroom the white balance looks ok. In lighttable mode all
images look wrong until I enter darkroom mode with them. I have enabled
raw thumbnails in the preferences.
Andreas
Am 28.10.2012 16:25, schrieb Ulrich Pegelow
Am 28.10.2012 12:05, schrieb Andreas Schrell:
> Hi,
>
> my situation: Changed a bunch of images on my desktop. Rsynced them to
> my notebook. All have xmps, some changed xmps with crops. Imported them
> in DT on the notebook. All look unchanged. Not WB nor crop in the images
> on the notebook.
>
Please try the following steps:
git pull
rm -r ./build
./build.sh --prefix /path/to/install
cd build
make install (or sudo make install)
Ulrich
Am 28.10.2012 13:37, schrieb Roumano:
> Hi,
>
> I'm running on a Gentoo machine.
>
> My previous git version running well ( darktable 1.0+1875~g777ce
Hi,
I'm running on a Gentoo machine.
My previous git version running well ( darktable 1.0+1875~g777ce68) (and
also the stable version package in gentoo 1.0.5)
I'm updating darktable via : "git pull;cd build/ ; make ; make install
I missing something ? (i don't launch a configuration commande
PS: loading from the xmp file manually after import works.
Andreas
Am 28.10.2012 12:09, schrieb Andreas Schrell:
> forgot to include a xmp file
>
> Am 28.10.2012 12:05, schrieb Andreas Schrell:
>> Hi,
>>
>> my situation: Changed a bunch of images on my desktop. Rsynced them to
>> my notebook. All
forgot to include a xmp file
Am 28.10.2012 12:05, schrieb Andreas Schrell:
> Hi,
>
> my situation: Changed a bunch of images on my desktop. Rsynced them to
> my notebook. All have xmps, some changed xmps with crops. Imported them
> in DT on the notebook. All look unchanged. Not WB nor crop in the
Hi,
my situation: Changed a bunch of images on my desktop. Rsynced them to
my notebook. All have xmps, some changed xmps with crops. Imported them
in DT on the notebook. All look unchanged. Not WB nor crop in the images
on the notebook.
User error or DTs fault?
Andreas
-
Thanks,
I am using Ubuntu 12.04 with nvidia-current-updates. The working
solution is:
sudo ln -s /usr/share/nvidia-current-updates/nvidia.icd
/etc/OpenCL/vendors/nvidia.icd
Also not the libcuda has to go in the icd file (like in my starce) but
the nvidia-opencl.so
Andreas
Am 28.10.2012 10:23,
That's an issue of the OpenCL package maintainer of your distribution.
We don't touch /etc/OpenCL/ and the files there at all.
Ulrich
Am 28.10.2012 10:08, schrieb Andreas Schrell:
> Hi,
>
> looks like the cuda lib is not found because the trailing newline is
> included in the file name. strace i
Hi,
looks like the cuda lib is not found because the trailing newline is
included in the file name. strace included.
I don't know if its dt or libs fault.
Andreas
openat(AT_FDCWD, "/etc/OpenCL/vendors/",
O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 8
getdents(8, /* 4 entries */, 32768) = 11
27 matches
Mail list logo
