even though the threads are most likely held idle in the background
and not created new for every openmp loop, there will be an overhead
starting a parallel section.
plus, if your loop doesn't scale well, all threads have to wait for
the slowest one, so you'll get synchronization overhead (likely
On Sat, Nov 24, 2012 at 9:41 PM, johannes hanika wrote:
> On Sun, Nov 25, 2012 at 12:22 AM, Pascal de Bruijn
> wrote:
>> On Sat, Nov 24, 2012 at 9:34 AM, johannes hanika wrote:
>>> hey all,
>>>
>>> i just put together a tarball for 1.1, along with a pdf for the usermanual:
>>>
>>> https://sourc
But isn't is a normal behaviour that a camera registers as a USB storage
device? And is there a difference between a camera register as a storage
device and putting a sdcard in a card reader?
//Snaggen
--
Monitor your phys
Hi all,
I have a question about OpenMP statement.
While playing with that module, I find that borders doesn't use OpenMP
in his process routine. I have tried to add some OpenMP statements,
especially for the image blitting loop, at the end of the process, but
perfs are worth...
I understand it'
On Sun, Nov 25, 2012 at 12:22 AM, Pascal de Bruijn wrote:
> On Sat, Nov 24, 2012 at 9:34 AM, johannes hanika wrote:
>> hey all,
>>
>> i just put together a tarball for 1.1, along with a pdf for the usermanual:
>>
>> https://sourceforge.net/projects/darktable/files/darktable/1.1/darktable-usermanu
Hi Mattias,
Ah i see, the import from sdcard is not "supported" if you use sdcard in camera
and connect camera using usb then you should see the thumbs..
I have never tried the camera import code on mounted sdcards and cant help
you there, even if i wrote that code, its all designed for connected
Am 24.11.2012 15:53, schrieb Jesper Pedersen:
> On 11/20/2012 04:33 PM, Ulrich Pegelow wrote:
>> In most cases only a few additions/changes are needed. I could do all
>> screenshots on the modules (that's easy)
>
> Quick read-through:
>
> * "Gritty detail": Old UI for highpass
True.
The rest not
On 11/20/2012 04:33 PM, Ulrich Pegelow wrote:
> In most cases only a few additions/changes are needed. I could do all
> screenshots on the modules (that's easy)
Quick read-through:
* "Gritty detail": Old UI for highpass
- and "Highpass" section
* "Overexposed": Likewise
* "Exposure": Likewise
Hello Ulrich,
I would describe in detail what I did, if I didn't only switch the
pictures. Maybe I toggled the over/under exposure indicator.
BTW I am max_ on irc...
hal
On Sat 24 Nov 2012 12:44:21 PM CET, Ulrich Pegelow wrote:
> Hi,
>
> for some reason dt_dev_pixelpipe_synch() is called with h
Hi,
for some reason dt_dev_pixelpipe_synch() is called with history=0
from dt_dev_pixelpipe_synch_all(). So we need to find out why this happens.
Can you please open a ticket in www.darktable.org/redmine ? The better
you can describe how to provoke the crash the higher the chances it gets
fixed :
On Sat, Nov 24, 2012 at 9:34 AM, johannes hanika wrote:
> hey all,
>
> i just put together a tarball for 1.1, along with a pdf for the usermanual:
>
> https://sourceforge.net/projects/darktable/files/darktable/1.1/darktable-usermanual.pdf/download
>
> https://sourceforge.net/projects/darktable/fil
Hello,
while switching pictures in dr mode with SAPCE, I sometimes receive a
segfault:
(OpenCL is off because my system crashes reliable with it)
[New Thread 0x7fff53165700 (LWP 5770)]
[New Thread 0x7fff52964700 (LWP 5771)]
[New Thread 0x7fff52163700 (LWP 5772)]
Program received signal SIGSEGV,
hey all,
i just put together a tarball for 1.1, along with a pdf for the usermanual:
https://sourceforge.net/projects/darktable/files/darktable/1.1/darktable-usermanual.pdf/download
https://sourceforge.net/projects/darktable/files/darktable/1.1/darktable-1.1.tar.gz/download
changelog is about
13 matches
Mail list logo
