5 ms·

I would just love it if a project using something like this came out that allowed you to use a VM run old versions of applications (EG: perpetually licensed ado

by hoherd 5y ago

I would just love it if a project using something like this came out that allowed you to use a VM run old versions of applications (EG: perpetually licensed adobe products) that are no longer supported. Bonus points if they let us adjust the date that is presented to the VM so that the subcomponents that Adobe did not get a perpetual license on (EG: face recognition) that were sold as part of a perpetually licensed product continue to function. I literally have an old Mac Mini running an old version of macOS and its only purpose is to run Lightroom 6. I'd love to not have to do that.

SmellTheGlove 5y ago
Would RAM be a limiting factor there? I suppose macOS is ok on 8gb so as long as you have 16 to give another 8 to the guest you can do it. It’d also depend on the resource needs of that legacy app you want to run.
- isfazri 5y ago
lisper 5y ago
I have a whole stable of machines running Mavericks just because I have a huge investment in iPhoto. I would like to switch to Photos but every time I try to convert an iPhoto library to Photos it fails (after a very very long time).
- orobinson 5y ago
  Once it’s up and running it’s fine but importing photo libraries into Photos is truely the worst software experience I have ever had. It took me weeks of on and off tinkering to get my partner’s photo library setup correctly and syncing with iCloud Photos. The worst part is that when it does fail there’s absolutely no indication to the user what went wrong. At best you’ll get some kind of generic error message, at worst it just hangs forever. Perfectly demonstrates how Apple’s “it just works” design philosophy falls apart when it doesn’t just work.
  - wkearney99 5y ago
    so. much. this.
- ralfd 5y ago
  Can you do it in batches?
  - JKCalhoun 5y ago
    Yeah, that would be my advice. Either export all images from iPhoto, original files (not compressed, down-scaled). Then pull them into Photos. Or literally open the iPhoto Library folder and go rescuing your photos. There are all sort of thumbnail versions in there for performance, so you'll have to discover the folder hierarchy to find your originals, but they're there.
    - lisper 5y ago
      The problem is not rescuing the original photos. That's easy. The problem is that we have put a lot of effort into editing the photos, curating them into albums, and adding captions.
      - Terretta 5y ago
        How many? I came from Aperture into modern Photos after holding out as long as possible. As versions updated, Photos understood more and more Aperture metadata and edits. With 10^6 photos, to get this to work I had to use old Aperture Library manager utilities to split those by album (by year for unclassified), then bring those split libs into Photos one at a time. I brought each into its own Photos library to limit blast radius of import issues, and was able to isolate which image(s) caused faults. After having an array of Photos libraries, I made a big enough store on a fast Mac that could stay online uninterrupted to act as my library host and iCloud Photos master. I imported Photos to Photos, and let it sync. Able to use logs and narrow down and retry remaining from an import when issues. Eventually, all good. There is a rate limit on syncing Photos to cloud. If Photos thinks you’re doing separate syncs, it can hit at 25K. So after that either just let it sit to catch up over the next week(s), or, if you are somehow certain of zero errors, keep cloud sync off until all Photos are imported and indexed locally then turn it on. Helping others with this, I’ve had to try both ways. All at once is best if no errors, as it doesn’t seem to rate limit the first batch. https://support.apple.com/en-us/HT202299 https://support.apple.com/en-us/HT202299 Note, with 10^6 photos in iCloud Photos and multiple devices syncing, sometimes one or more usually older items lose sync or won’t sync from an iPhone. In my experiences, nothing fixes this, not even disable/enable iCloud Photos — until the next major version number iOS release, which seems to reindex or rebuild device Photos library.
- jwr 5y ago
  I have a huge Aperture library. After Apple screwed me by abandoning it, I have no good options. I'm trying to run Aperture in VMware. Dog slow, but kind of works...
- sys_64738 5y ago
  This is why I so dislike these garbage apps with their own proprietary formats that leave you stranded when the vendors abandons you. Apple, Google. They're all guilty of it. I want my photos in a directory using open formats that I control. It's especially bad with the crap programs on Windows that encoded videos and the like.
terhechte 5y ago
I think this only works for Monterey because older macOS were never build for Apple Silicon.
- agsnu 5y ago
  Big Sur was available for Apple Silicon; presumably there are new hooks in Monterey to support this virtualisation that Apple didn't see the need to backport. It's something of a sore point for Mac devs, as it means it's basically impossible to test their apps on Big Sur on Apple Silicon without having a dedicated box for it...
nix23 5y ago
Something like that? https://github.com/myspaghetti/macos-virtualbox https://github.com/myspaghetti/macos-virtualbox

by hoherd 5y ago

SmellTheGlove 5y ago

Would RAM be a limiting factor there? I suppose macOS is ok on 8gb so as long as you have 16 to give another 8 to the guest you can do it. It’d also depend on the resource needs of that legacy app you want to run.

isfazri 5y ago

lisper 5y ago

I have a whole stable of machines running Mavericks just because I have a huge investment in iPhoto. I would like to switch to Photos but every time I try to convert an iPhoto library to Photos it fails (after a very very long time).

orobinson 5y ago
Once it’s up and running it’s fine but importing photo libraries into Photos is truely the worst software experience I have ever had. It took me weeks of on and off tinkering to get my partner’s photo library setup correctly and syncing with iCloud Photos. The worst part is that when it does fail there’s absolutely no indication to the user what went wrong. At best you’ll get some kind of generic error message, at worst it just hangs forever. Perfectly demonstrates how Apple’s “it just works” design philosophy falls apart when it doesn’t just work.
- wkearney99 5y ago
  so. much. this.
ralfd 5y ago
Can you do it in batches?
- JKCalhoun 5y ago
  Yeah, that would be my advice. Either export all images from iPhoto, original files (not compressed, down-scaled). Then pull them into Photos. Or literally open the iPhoto Library folder and go rescuing your photos. There are all sort of thumbnail versions in there for performance, so you'll have to discover the folder hierarchy to find your originals, but they're there.
  - lisper 5y ago
    The problem is not rescuing the original photos. That's easy. The problem is that we have put a lot of effort into editing the photos, curating them into albums, and adding captions.
    - Terretta 5y ago
      How many? I came from Aperture into modern Photos after holding out as long as possible. As versions updated, Photos understood more and more Aperture metadata and edits. With 10^6 photos, to get this to work I had to use old Aperture Library manager utilities to split those by album (by year for unclassified), then bring those split libs into Photos one at a time. I brought each into its own Photos library to limit blast radius of import issues, and was able to isolate which image(s) caused faults. After having an array of Photos libraries, I made a big enough store on a fast Mac that could stay online uninterrupted to act as my library host and iCloud Photos master. I imported Photos to Photos, and let it sync. Able to use logs and narrow down and retry remaining from an import when issues. Eventually, all good. There is a rate limit on syncing Photos to cloud. If Photos thinks you’re doing separate syncs, it can hit at 25K. So after that either just let it sit to catch up over the next week(s), or, if you are somehow certain of zero errors, keep cloud sync off until all Photos are imported and indexed locally then turn it on. Helping others with this, I’ve had to try both ways. All at once is best if no errors, as it doesn’t seem to rate limit the first batch. https://support.apple.com/en-us/HT202299 https://support.apple.com/en-us/HT202299 Note, with 10^6 photos in iCloud Photos and multiple devices syncing, sometimes one or more usually older items lose sync or won’t sync from an iPhone. In my experiences, nothing fixes this, not even disable/enable iCloud Photos — until the next major version number iOS release, which seems to reindex or rebuild device Photos library.
jwr 5y ago
I have a huge Aperture library. After Apple screwed me by abandoning it, I have no good options. I'm trying to run Aperture in VMware. Dog slow, but kind of works...
sys_64738 5y ago
This is why I so dislike these garbage apps with their own proprietary formats that leave you stranded when the vendors abandons you. Apple, Google. They're all guilty of it. I want my photos in a directory using open formats that I control. It's especially bad with the crap programs on Windows that encoded videos and the like.

terhechte 5y ago

I think this only works for Monterey because older macOS were never build for Apple Silicon.

agsnu 5y ago
Big Sur was available for Apple Silicon; presumably there are new hooks in Monterey to support this virtualisation that Apple didn't see the need to backport. It's something of a sore point for Mac devs, as it means it's basically impossible to test their apps on Big Sur on Apple Silicon without having a dedicated box for it...

nix23 5y ago

Something like that? https://github.com/myspaghetti/macos-virtualbox https://github.com/myspaghetti/macos-virtualbox