headers
davidvincentjones | 1 Aug 2009 01:37
Picon

Print Image -- Options


Each time that I print an image I need to select the printer, select print
direction, select inch units, select margins ..... It would appear that the
Options should be saved to avoid those repetitions with individual printing.

It works fine otherwise.
--

-- 
View this message in context: http://www.nabble.com/Print-Image----Options-tp24764503p24764503.html
Sent from the digikam-users mailing list archive at Nabble.com.
Permalink | Reply | 0 comments |
headers
Hubert Furey | 2 Aug 2009 01:06
Favicon

Re: Create MPEG slideshow not available?

Ok, Thank you...

Hubert

> 
> MPEGSlideshow kipi-plugin is not ported to KDE4.
Permalink | Reply | 0 comments |
headers
davidvincentjones | 2 Aug 2009 02:22
Picon

Image Problem not just in Beta


I am using 0.10.0 with Ubuntu 9.04 ... I have kept well clear of the Beta.

Inadvertently deleted some images that required that I refresh part of my
data from a backup drive.

None of the refreshed material now is showing even though it can be seen in
ShowPhoto etc.

Even more alarming when I process the images that I can see they also
disappear into the black hole.

Tried removing DK totally and doing a full reinstall .. that is not helping,
problem remains.

This is really a disaster unless we find a quick fix.

--

-- 
View this message in context: http://www.nabble.com/Image-Problem-not-just-in-Beta-tp24773896p24773896.html
Sent from the digikam-users mailing list archive at Nabble.com.
Permalink | Reply | 2 comments |
headers
Sven Burmeister | 2 Aug 2009 11:11
Picon
Gravatar

Re: Image Problem not just in Beta

Am Sonntag, 2. August 2009 02:22:10 schrieb davidvincentjones:
> I am using 0.10.0 with Ubuntu 9.04 ... I have kept well clear of the Beta.
>
> Inadvertently deleted some images that required that I refresh part of my
> data from a backup drive.
>
> None of the refreshed material now is showing even though it can be seen in
> ShowPhoto etc.
>
> Even more alarming when I process the images that I can see they also
> disappear into the black hole.
>
> Tried removing DK totally and doing a full reinstall .. that is not
> helping, problem remains.
>
> This is really a disaster unless we find a quick fix.

Create a new user and start digikam with that one. If the pictures show up, 
your settings and/or db are messed-up.

Sven
Permalink | Reply | 0 comments |
headers
Gurvan Huiban | 2 Aug 2009 11:25
Picon
Favicon

Re: Image Problem not just in Beta

Hello,

> I am using 0.10.0 with Ubuntu 9.04 ... I have kept well clear of the Beta.
>
> Inadvertently deleted some images that required that I refresh part of my
> data from a backup drive.
>
> None of the refreshed material now is showing even though it can be seen in
> ShowPhoto etc.

Same kind of symptoms here (Debian testing - Digikam 0.10). Same problem?

I renamed some files outside digikam. And now, digikam shows me all the albums 
structure, but empty. As if the image database was completely empty.

> Even more alarming when I process the images that I can see they also
> disappear into the black hole.

In my case all the images disappeared.

> Tried removing DK totally and doing a full reinstall .. that is not
> helping, problem remains.

I tried the 1.0.0~beta3-1, but it did not change anything.

> This is really a disaster unless we find a quick fix.

And hopefully, the information (tags, caption) are not lost.

Regards,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stefan Aschenbach | 3 Aug 2009 14:50
Picon
Favicon

Re: building it for Mac OS / Windows

Hi there,

I've also managed to build on OS X.

I had to jump just some more hoops to get it going. Some dependencies  
of kde need a ggc 4.2 to compile,
while on Mac OS 10.4 (Tiger) the newest one to be delivered with  
xcode is 4.0.

So you have to get the apple-gcc42 package of macports and then start  
the compilation by typing

sudo port install digikam configure.compiler = apple-gcc-4.2

After that (and of course patching lqr as mentioned) digikam builds.
Before starting it you have to register some processes and start some  
daemons as told
be the notes to all the kde packages you installed with macports.

One file to load was a .plist which actually won't load right away.  
There was a active=no line in it which I had to change to make it work.

Digikam starts then if you manage to locate the executable in
/opt/local/var/macports/software/digikam/1.0.0-beta3_0+darwin_8/ 
Applications/MacPorts/KDE4

But it's unstable as hell. I usually get about 5 clicks until  
something makes it go down. Last time it took quite an amount of OS X  
with it, leaving me at a new login window.
Therefor my unsaved notes in a text editor were lost and the command
(Continue reading)

Permalink | Reply | 8 comments |
headers
Marcel Wiesweg | 3 Aug 2009 18:52
Picon
Picon

Re: building it for Mac OS / Windows


> But it's unstable as hell. I usually get about 5 clicks until
> something makes it go down. Last time it took quite an amount of OS X
> with it, leaving me at a new login window.
> Therefor my unsaved notes in a text editor were lost and the command
> line given above is made up from memory.
> If I just be very carefully with my clicks it just stops loading
> preview thumbnails after about 5 pictures
>
> As the whole build with all the dependencies took about two days, I
> gave it a try on a windows machine while waiting.
> Of course there is no prebuild binary either. The website says so,
> but just redirects to the kde-on-windows site offering in 'kde
> installer', which just as macports compiles things from source.
> Albeit said on the website, there is no beta3 package availiable
> within the 'kde installer', so I took the beta1.
>
> It actually builds and starts! But it kept spitting error messages
> about not being able to connect to the dbus server with every other
> dialog box. That's probably the kde installers fault, which just
> didn't succeeded in preparing the whole kde environment.

I can't comment on KDE-on-Windows status. There was some trouble with writing 
a native DBus implementation.

>
> If this is the state of being for the final release of digikam 1.0.0,
> you better scratch that 'multi platform' off the website. Digikam is
> strictly mono-platform, and this platform is KDE.
> Whatever the KDE guys are saying, just because QT4 would enable it to
(Continue reading)

Permalink | Reply | 2 comments |
headers
Andi Clemens | 3 Aug 2009 20:05
Picon
Gravatar

Re: building it for Mac OS / Windows


On Monday 03 August 2009 18:52:28 Marcel Wiesweg wrote:
machines and therefor interested in bug reports?
> Noone of us has Mac OS X available, Gilles has been testing on Windows. (I
> could too, but have been lacking interest).
> If you have a nice crash log just report it. If noone reports we think all
> is well. If someone reports, we may do something about it (especially if
> it's a crash with a good backtrace) - but keep in mind the problem that we
> can't test.

I have Mac OS X here, but since developing under Windows was already a pain, I 
never compiled digiKam under Mac. Maybe I should try to do so...

Andi
Permalink | Reply | 1 comment |
headers
Michael G. Hansen | 3 Aug 2009 20:12
Picon

image editing: comparing right parts / bottom parts?

Hi,

I'm using the Digikam's image editor to adjust color curves. The buttons
for comparing the original and the target allow me to compare the left
side of original and target, or the top of original and target. Is there
a way to compare the right sides or the bottom part? Turns out I have
quite a few images where the important parts are in these areas...

Thanks,

Michael
Permalink | Reply | 0 comments |
headers
Milan Knížek | 3 Aug 2009 21:14
Picon

Re: Colour Management... Help!

Mark Greenwood píše v Pá 31. 07. 2009 v 00:23 +0100:
However, this is the bit that has got me confused.... now I go to Colour->Colour Management. Under 'Input Profile', 'Use default profile' is selected. If I now change that to 'Use selected profile' and browse to the exact same profile that I selected in the Settings dialog (the Nikon D40 one) all of a sudden my image has saturation and contrast. If I now change 'Workspace Profile' from 'Use default workspace profile' to 'Use selected profile' and browse to an sRGB profile I have downloaded I get even more saturation and contrast. If I now adjust the white balance to D50 instead of D65 I get something pretty close to how the embedded preview looks. But shouldn't all that be happening automatically if I have colour management enabled? So what's going on? It looks to me as though Digikam is not applying my default profiles when it imports the RAW files, and that I would have to go through the Colour Management step for every file. What have I missed? Finally, if I go back to using JPEG files, do I have to change the colour management settings so the input profile is sRGB?
Many of these things are known and  already reported as bugs
https://bugs.kde.org/buglist.cgi?quicksearch=digikam+color+management

For the time being, I would recommend to follow the status of these bugs and avoid using CM in digiKam. According to other posts here, Gilles plans to have a look at this topic before 1.0.0 final release. (You can use UFRaw to convert NEF files to sRGB in the meantime.)

regards,

Milan Knizek
knizek (dot) confy (at) volny (dot) cz
http://www.milan-knizek.net - About linux and photography (Czech language only) 
_______________________________________________
Digikam-users mailing list
Digikam-users@...
https://mail.kde.org/mailman/listinfo/digikam-users
Permalink | Reply | 0 comments |

Gmane