130 karma · joined November 3, 2018
Colour is a bit more hands on and with negadoctor you really can get a nice starting base but it's much more manual. You need to make sure colour profiles and white balance match your scaner/dslr scan. The you need to set up the shadow casts and highlight colours. Much more manual just to then get a rather flat image with correct colours to your liking. Then it's more regular raw workflow so altering contrast and saturation but it's nothing too hard still. But it's 100% more hands on the using NLP (this is what I'm assuming you are using. Check YouTube see what you think.
Time wise, the speed of snapping a photo is also mostly outweighted by the time needed to post process the image (neg invert, white balance, colour correct) versus the slow scanning speed of a flatbed negative scanner. Never used the cheaper 35mm scanners you can buy, but from what I’ve seen they're just the dslr approach without the quality.
I think it comes down to two questions. 1: Do you own a dslr with a macro lens? 2: Do you know how to use raw editors like lightroom or darktable?
If yes to both, then dslr scanning is easily the cheaper of the two and is most likely the best route to go to test the process.
For anyone wanting to do this, you will need to invert your b&w or colour negatives with software capable of processing RAW files (lightroom, darktable, rawtherapee) white balance the negative, invert and then colour/exposure correct the final image. I use darktable for this and the latest version has a real nice plugin called negadoctor that can give you a great starting point. For lightroom, NegativeLabPro is the goto tool and works in a similar way to negadoctor but is better at producing the initial image.
This here is my most hated thing about KDE. I run it on Debian so my version is pretty old compared, has it been fixed in newer versions? I have been thinking about switching to Neon, but I don't care for the Ubuntu base verses vanilla Debian.
Our use case is dynamic dashboards generation where a document contains multiple components for our frontend to render. Having a simple unstructured database really helps us build the dashboard efficiently. Using a relational database would increase the development time of each dashboard tremendously and having relational integrity would make it even worse.
Having a simple document with everything needed is a much nicer experience. Granted, our use case is very limited and it is read only.
I've switched to the tram train route that's just opened in Sheffield and that is seeing the same problems. Northern trains running late causing a backlog.
I really miss Japan's rail system.