News for hackers. Stuff that matters.
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by scoot on Monday March 02, 2020 @05:31PM (#22469766)
I bought Aperture only shortly before they killed it off. Still seething about that. Since Photos can't seem to cope with my ~30K picture photo library (that I'm still trying to recover it after numerous attempts), can anyone suggest a viable alternative?
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by timdesrochers on Tuesday March 03, 2020 @01:04AM (#22472215)
I use and love DigiKam[0] for organizing my ≈230k RAW & JPG media library, and both RawTherapee[1] and Darktable[2] are great for more specific editing (though I haven't settled on an ideal workflow yet). One cool thing about DigiKam is that you can have it use a remote MySQL server for its db, theoretically allowing you to work with your library from the road (I think... it's been several months since I've spent a weekend working on my photo libraries).

Adobe's Lightroom truly is a great and powerful tool like so many of their other apps, but I just can't stomach having years' worth of work locked up in a proprietary subscription-model app. And I just consider Apple Photos untrustworthy, though I do like to use it + iCloud shared photo albums to publish my edited "selects" instead of my full library.

Now if only there was a real F/LOSS contender to replace FCPX...

[0] https://www.digikam.org/

[1] https://rawtherapee.com/

[2] https://www.darktable.org/

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by mceachen on Monday March 02, 2020 @05:58PM (#22470009)
I got sick of fighting apps that don't scale, force me to use a specific OS or expensive hardware, feed the adtech panopticon, or don't clean up the messes left behind from all the other photo apps I've used, so I started my own company to do just that.

https://photostructure.com/about/introducing-photostructure/

It's currently in closed beta. I'm letting people in first-come-first-served roughly monthly, as I release new versions. It's free while in beta, in exchange for your feedback. Here's what's coming soon:

https://photostructure.com/about/release-notes/

Note that PhotoStructure doesn't have any editing tools other than fixing rotation. It does let you easily open the current image in other apps, though.

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by jwr on Tuesday March 03, 2020 @03:48AM (#22472908)
After I got royally screwed by Apple discontinuing Aperture (I mean, come on, it's not like they're google or something), I decided to a) package Aperture in a VMware virtual machine so that I don't lose access to my libraries and b) start working on my own software for long-term photo archives.

The project you are describing sounds close to my goals, with the possible exception of long-term storage: I've been planning to develop everything so that data is easily retrievable even if the software doesn't work. Metadata in text files, for example, image storage in well-known formats, folder structure that is understandable to humans, etc. This is for family archives: I'm scanning photos that are a hundred years old and I feel like an idiot when cataloging them using software that some company will obsolete in a couple of years.

Incidentally, there is another niche which is largely unaddressed: easy organizing of photos into sets with various access tags and sharing these with friends and family in a secure and easy way. It's kind-of doable today if you don't care about privacy, security, and longevity, but it's still annoyingly difficult to use, especially for less computer-literate family members. It seems that all designers of photo software only keep photos from their latest vacation, wipe their entire collection with each device upgrade, and want sharing links to be valid for at most a month or so.

One thing which could prevent me from using your software is lack of control: I got burned several times already and I'm considering my options carefully. It might be better to roll my own rather than start depending on something again.

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by mceachen on Tuesday March 03, 2020 @12:49PM (#22476851)
I've made a bunch of design decisions to address long-term storage concerns (after being personally burned by more than a handful of abandoned photo apps):

File storage (if you opt for PhotoStructure doing automatic organization) is configurable (with a default of $library/yyyy/yyyy-mm-dd/$original-filename).

All metadata extracted or changed is saved in standard-format sidecars next to the original, or in the image itself. The sidecar format and whether to use sidecars for edits are both configurable.

The database is a SQLite DB with a straightforward schema (although as I add features, each version has had db migrations).

If you try PhotoStructure out, and you find or think of anything else I can do to set things up to be more friendly to long-term storage, I'd love to hear your ideas.

(Sharing is coming in a future release, both via any hierarchical tag, or by manually-selected images).

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by jwr on Wednesday March 04, 2020 @05:16AM (#22482561)
Everything you wrote is very intriguing and largely aligned with my goals. I'd like to take a closer look at what you are building.

There is still the issue of control: I am worried about the lack of a "Pricing" page, not because I do not want to pay (quite the opposite), but because I am worried about the sustainability of your business. And about what will happen when you sell it to Google, or otherwise abandon it.

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by mceachen on Tuesday March 03, 2020 @03:17PM (#22478339)
> scanning photos that are a hundred years old

FWIW I've got a bunch of both scanned images and older JPGs that I inadvertently stripped all metadata from (if you use jpegtran to losslessly rotate, make sure you use `-copy`!), so PhotoStructure infers captured-at time from filenames or enclosing folder names if it's missing from the EXIF headers, and it can extract at least a reasonable year, month, and day from the path.

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by Nextgrid on Monday March 02, 2020 @06:57PM (#22470436)
Just wondering, is the desktop client based on Electron?
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by mceachen on Monday March 02, 2020 @07:29PM (#22470633)
yes, that's how I've currently packaged up PhotoStructure for Desktops.

There's also PhotoStructure for Servers which can run under Docker, or as a standard node app (ala `git clone $url; photostructure/photostructure`).

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by aikinai on Monday March 02, 2020 @09:59PM (#22471420)
Thanks for the heads up; saved me from being intrigued by this project.
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by jwr on Tuesday March 03, 2020 @02:20AM (#22472498)
This kind of comment is typical for someone who does not have to contend with business reality and has no idea how much it costs to develop and maintain native desktop applications.

My guess is that the same people, when given a native app, complain about the subscription pricing or the price tag.

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by aikinai on Tuesday March 03, 2020 @03:07AM (#22472744)
Oh I understand the business reality very well and I don't blame anyone for making that call when it's the right move for them, but I'm still not going to use the software.

And I happily pay for all of the quality native software I can find. One of the most exciting things is finding a well-crafted native application with a clear business model.

I'm really hoping Serif, for example, moves into the Photo organization space. I've already purchased all of their current apps even though I don't really need them all that much; probably 70% of the reason I bought them was just to support what they're doing.

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by diffeomorphism on Tuesday March 03, 2020 @03:20AM (#22472795)
That sounds to me like you agree entirely, "Yes, it is horrible, but we have to use it anyways because..."
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by petepete on Monday March 02, 2020 @05:46PM (#22469906)
I thoroughly recommend Capture One Pro. It deals with my huge catalogue without breaking a sweat and its editing capabilities are class-leading.
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by atombender on Monday March 02, 2020 @07:08PM (#22470526)
How are the photo organizing capabilities? I like to organize everything into nested folders.

One thing I like about Lightroom is that I can right-click on a folder and get a shareable, private link that people can go to to view the album. Great for sharing photos from a trip or an event without having to go to some other services.

The link opens a minimalist, unintrusive, functional album app where people can optionally download originals and even rate and comment on the photos, which is nice when you want to work together to whittle a larger set of candidates down to a smaller set.

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by dvcrn on Monday March 02, 2020 @09:08PM (#22471217)
Another Capture One user here. Capture One has 2 ways of organizing your stuff: Inside a Catalog (embedded into the library) or as a Session. In a Session, Capture One gives you a rough folder recommendation that you can use but just uses the folders from your file system. Catalogs embed the pictures and handle all the managing for you, but can also be set to not do that.

None of that sharing and cloud stuff of lightroom though. It's just a RAW/photo processor.

https://www.azuloxworkshops.com/educational/capture-one/capt...

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by firecall on Monday March 02, 2020 @07:53PM (#22470788)
I've never had issues with Lightroom.

With regards to Apple Photos, I have ~130k photos synched without issues (that I can tell). No problems with iCloud sync either these days.

I also double sync the photos as JPG to Google Photos.

Having everything in Apple Photos is great for mobile browsing... the other night I pulled up images from 2006 on my iPhone!

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by aikinai on Monday March 02, 2020 @10:04PM (#22471444)
I’m around the same with 140,000 photos and it works fine day-to-day. I think they fixed the performance issues a few years ago. However, there are two gotchas:

I can’t open the photo library from other apps on iOS; it hangs forever. So I have to pick the photo from Photos and share into the app. Sometimes this isn’t possible like picking a profile photo, so it’s just not possible.

It takes about a month to resync my library after a fresh install of MacOS. I just installed Catalina and am waiting on this process right now. It looks like it’ll be done around April.

Edit: Clarified below, but I mean just to confirm the sync state, not redownload. I have the entire local library intact, but if you change anything locally (library location, OS, etc), Photos says "Uploading 140,000 items" and takes a month to confirm the library is in sync with the server.

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by bobbylarrybobby on Monday March 02, 2020 @11:21PM (#22471750)
1. Surely this is the apps' faults for not paginating queries on your Photos library correctly? (Unless it's a real Photos app bug, which I suppose is possible although unlikely)

2. Yikes, I guess with 140k photos putting your library on an external drive before wiping and then copying the library back to your Mac would also take a long time, but it shouldn't take a full month.

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by aikinai on Monday March 02, 2020 @11:42PM (#22471835)
1. I'm not an iOS dev so I can't say for sure, but my impression is that the apps don't have that much control when they open the photo library.

2. Sorry I wasn't clear; this is what I do. The problem is that if you move the photo library at all (or even if you don't but it's a new OS installation), it doesn't trust the old sync state so it manually checks each photo. It does seem to be hashing or something since it's using very little network, but it's only processing one photo every 10 to 20 seconds. I have no idea what makes it so slow, but I've found similar reports on forums so it seems to just be the way it is.

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by ngokevin on Monday March 02, 2020 @08:17PM (#22470936)
You can sync your photos to Lightroom cloud and pull up the photos and edit them from anywhere like the app.
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by foxandmouse on Monday March 02, 2020 @05:39PM (#22469826)
DarkTable is an open source alternative to lightroom that I used to use.
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by nkristoffersen on Tuesday March 03, 2020 @05:09AM (#22473211)
What kind of issues are you having with Photos? I have over 50,000 photos and over 4,000 videos and it’s been nothing but a dream.
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by scoot on Tuesday March 03, 2020 @08:16AM (#22474172)
It crashes repeatedly on launch, and the built-in repair function fails to repair it. I’m currently trying to import the photos and videos into a new Photos library, but you lose metadata (such as video dates, faces etc.) and projects, so I might as well move to something more reliable.
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by zerkten on Monday March 02, 2020 @05:36PM (#22469808)
From your tone, I'm assuming you've tried and discounted Lightroom already?
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by wiredfool on Tuesday March 03, 2020 @03:36AM (#22472855)
I'm in the same boat with Lightroom -- I've bought it 3 times and I've got a historic library in it with tens of thousands of images, but if I upgrade to Catalina my non-subscription Lightroom won't work anymore. I don't open it often, like maybe a couple of times a year, but I don't want to lose the work that's in there.
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by zerkten on Tuesday March 03, 2020 @10:29AM (#22475201)
Could you run the old Lightroom in a VM? Ultimately, you might have to unless you migrate or pay up.

Lightroom is inexpensive relative to other tools and everyday expenses I have. The same goes for other closed-source photography software mentioned on threads like this, to the point that I've bought some of it to experiment moving off Lightroom.

Given the propensity of photographers to splurge huge amounts on gear, and their positions on intellectual property, I don't think I'm that unusual. Perhaps within the HN crowd the philosophy is different.

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by wiredfool on Tuesday March 03, 2020 @01:21PM (#22477226)
I didn’t object to paying for upgrades when I was actively using the software, but at this point, I’d be paying tens per invocation of the program.

I’ve moved on, I don’t do photography much anymore and if I’m going to be plowing money into something, I’d rather it be in a current hobby.

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by bradknowles on Monday March 02, 2020 @06:32PM (#22470264)
No Adobe products, please.
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by wilg on Monday March 02, 2020 @08:45PM (#22471097)
I have 40K photos in Photos and it works okay. Definitely a few issues here and there but there really doesn't seem to be a better alternative.
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by lowdose on Wednesday March 04, 2020 @09:24AM (#22483977)
Google photos, unlimited storage plus automatic ml tagging. I even upload 4k video up from my Netflix Plus channels.
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by craftinator on Monday March 02, 2020 @09:53PM (#22471397)
Have you tried Linux?