This evening’s update is that the ophthalmologist reckons her optic nerve is ok – just irritated – so her eyesight should go back to normal. How long that will take we just don’t know. The anti-migraine meds are starting to work, and they’ve also put her on some anti-convulsive drug too.
She’s not home, though. At least another night in Club Wes. Hmmph.
The ENT neurosurgeon swung past, ran some tests and reckons that
She’s got massive Nystagmus going on
The pain she had at the back of her head around Easter was in fact a massive migraine, and
What she’s going through now is still part of that migraine (either a continuation thereof, or a side effect).
He’s going to confer with another neurosurgeon about course(s) of action, and in the meantime has written up some migraine meds for her.
The ophthalmologist appt is tomorrow at 11:30, not sure how that’s going to go. We might be lucky – she might be able to come home tomorrow arvo.
All our fingers/toes are crossed.
Due to her dizziness/nausea/vomiting over the last 5 days, J’s being admitted to the Wesley at 12pm today.
More news when there is some.
From last night’s conversation in #darktable:
Apr 17 03:38:27 <pmjdebruijn> it’s good to be able to support a platform out of the box, no patches required Apr 17 03:40:09 <dumbbell> I agree
Apr 17 03:48:04 <pmjdebruijn> it’s funny Apr 17 03:48:20 <pmjdebruijn> it seems Solaris is our second best supported platform at the moment due to McBofh’s great work
Apr 17 03:48:37 <pmjdebruijn> i’m glad freebsd is up to there too now Apr 17 03:52:41 <dumbbell> I’m glad too
And it’s great to find Open-Source advanced softwares like darktabke; I don’t want to reboot under Windows for any non-game-related activities
I’d go a bit further than <dumbbell> – I don’t want to boot into Windows for anything if I can avoid it.
Update: The underlying reason why it’s so easy for me to get Darktableto run on Solaris is because the codebase is very portable. I don’t like the style that it’s written in (understandable when you consider that I breathe the Solaris ON C style guide), but that’s irrelevant. I’ve needed to make very few changes – a total of 24 lines – to get it to build on Solaris, and most of those were to provide subtly different #pragma invocations for OpenMP.
Also, once you’ve got a build and packaging system figured out, it’s pretty easy to crank the handle and turn out a new build.
Seen at the footer of some spam I received earlier today:
You are receiving this email as you were added to our comprehensive database on account of your contribution in the PM domain. This e-mail has been sent to you to exhort you to achieve success in project management certification exam. If you no longer wish to receive e-mails from our side, you may Unsubscribe from this list
No, I haven’t contributed in the “PM domain”. Additionally, not only do I no longer wish to receive emails from “Caroline@prince2trainingacademy.com”, I NEVER wanted to receive emails from you in the first place.
SPAMMER. FAIL.
It’s getting close to 1.0.1 release time, and if you’re running Darktable on Solaris then I’d appreciate it if you could give the tires a kick on this 1.0.1 package. Reports of both success and failure are valuable, so please do let me know your results.
I’ve been playing around with exporting to jpeg lately, because after our recent Easter holiday I had a few hundred pics to process – some of which might get shared with family. In parallel with this I’ve been building Darktable from git master and was racking my brains trying to work out why the export process (from what is effectively a nightly build) was giving me useless output files. By “useless” I mean “had no content except for EXIF info”. Very, very annoying.
After firing up badopen.d and while testing the various intent and
profile settings for exporting to file-based storage, I realised that
stacks such as this:
0 100408 openat:return open for '/opt/darktable/share/darktable/color/out/image' failed libc.so.1`syscall+0x5 libc.so.1`__open+0x29 libc.so.1`open+0xd4 libc.so.1`_endopen+0xa1 libc.so.1`fopen+0x29 liblcms2.so.2.0.3`cmsOpenIOhandlerFromFile+0x73 liblcms2.so.2.0.3`cmsOpenProfileFromFileTHR+0x4c liblcms2.so.2.0.3`cmsOpenProfileFromFile+0x2c libdarktable.so`dt_colorspaces_create_output_profile+0x3e4 libjpeg.so`write_image+0x173 libdarktable.so`dt_imageio_export_with_flags+0x55e libdarktable.so`dt_imageio_export+0xfb libdisk.so`store+0x38f libdarktable.so`dt_control_export_job_run._omp_fn.0+0x40b libdarktable.so`dt_control_export_job_run+0x345 libdarktable.so`dt_control_run_job+0x21c libdarktable.so`dt_control_work+0x41 libc.so.1`_thrp_setup+0x9d libc.so.1`_lwp_start
were probably indicative of something strange in LCMS-land. Sure enough, the ‘always use littlecms2 when exporting’ box was ticked in the core options dialog. Turning that off made a world of difference – no more empty images! I assume that if I can locate an LCMS2 output profile then I’d have more success using it
For giggles (and because I’m still annoyed by this ticket, I decided to go through all the export options and compare the output:
My latest darktable-git package is darktable-git_20120414T210529Z.p5p.gz, which is built from git master up to and including changeset 3d2c7d296ae8b43bc143724ec4cdb3d3ab70dc97.
That means it’s got all the Bauhaus branch goodness:
J’s latest (which we’ll be having with friends this evening):
One feature that Lightroom has which I think Darktable needs is the ability to perform a backup of your current catalog from within the application. Lightroom checks every week to see if you’ve made a backup recently, and then prompts you to make one. You can ignore it, of course, but you never know when you’re going to want that backup.
While I figure out a way to make this happen from within Darktable, I’ve got this little quick-n-dirty shell script which I run out of cron at midnight every night:
#!/bin/bash DTLIB=$HOME/.config/darktable/library.db DTNEWLIB=${DTLIB}-`/usr/bin/date +%Y%m%d_%H%M` ECHO=/bin/echo SQLITE3=/usr/bin/sqlite3 RESULT=`$ECHO .dump | $SQLITE3 $DTLIB | $SQLITE3 $DTNEWLIB` if [ $? -eq 0 ]; then $ECHO "Dumped $DTLIB to $DTNEWLIB" else $ECHO "FAILED to dump $DTLIB to $DTNEWLIB" exit RESULT fi