Shasta: AI-powered audio recording and editing
pages.adobe.com
pages.adobe.com
Given this, I am very concerned about Adobe's continued march into web apps. For most of my UI and web design work, I use Figma, and quite like its feature set, but that I cannot use it offline and that I cannot work in a file that requires over 2GB of RAM due to its browser RAM cap is infuriating to me when Photoshop (the supposedly worse program) enables me to manually allocate as much of my system's 64GB of RAM as I please. It's difficult to imagine any web app stably and efficiently growing to Swiss army knife-levels of capability. Not just in terms of performance and resource management, but also GUI, keyboard shortcuts, etc.
I've long assumed my CC subscription would die with me, unlike many (most?) of my peers, but if the web-based Photoshop somehow became the primary Photoshop, I may have to cancel my subscription, and then kill myself.
In my eyes the 2GB/4GB limit for browser memory caps feels like an implementation issue rather than it being the wrong platform. At least for me, I value the ability to easily collaborate with people more than the need to have code be explicitly local or for things to be offline. The browser is excellent at that, and the explosion of online SASS products over locally installed apps in the last decade has shown it to be true for most use cases.
I don't think it's difficult at all to imagine a web app "stably and efficiently growing to Swiss army knife-levels of capability". Increasing that per-tab memory limit feels like an easier hill to climb than finding a way to provide that instant access for everyone and collaboration baked into locally installed apps.
Also don't kill yourself, even if it's a joke, life is more than software.
I hear what you're saying, and definitely get how the sharing bit that has helped Figma take off like it has is good for the browser. I'm a bit at odds with the industry, though, in that that's probably one of the things I like least about Figma. But a lot of that is because I'm not always the best team player :].
I won't pretend to know enough about what goes into building these programs to say whether the RAM cap or native app collaboration is the more difficult thing to overcome, but it's clear to me that I would prioritize these differently from others.
Because they have an excellent track record of completely ignoring the glaring problems with some of their apps like become slower even though cpus and gpus are getting faster (looking at you, Lightroom team)
Not sure how this makes sense. If the performance is not good, and the stability is lacking, then the user experience cannot be the best. I rather use a video editor that makes me go through two menus instead of one, rather than having a video editor that crashes on me or takes ages to generate the proxy clips (or even need proxy clips for 4K and below footage).
If Adobe pulls all the stops and produces value corresponding to what it charges, which is crazy--then, I might reconsider my views, maybe their business incentives have aligned very well now and they can become a virtuous monopoly.
You wouldn't know it from the comments on this site, though, my GOD, all negative yours is the first positive.
Further, Figma did a good thing for the end user by selling out to Adobe--at a very steep price. Their holding out for a huge price is virtuous, yes of course more money for them, but if you're selling out, charging a lot is virtuous, taking as big a bite as you can out of the giant.
Recently I had a chance to use Photoshop 7 on an old iMac G4 that I acquired. Surely this would be like living in the dark ages, banging some rocks together?
Well, no. It turns out that this old version of Photoshop is easy to use and powerful. I can quickly do simple graphic design tasks that would take me longer in other programs or leave me frustrated. I can also do a bunch of simple photo editing tasks that I’ve been missing out on. This experience really highlighted how I’ve gotten used to missing features or poorly-designed UIs in programs like Gimp. Simple things like messing with channels, changing the brush size, working with 16-bit color and alternative color spaces, layer styles, nice text layers—it’s all just there and working and ready to use, in this nearly 20-year-old software.
CS5 Master Suite w/discs and valid serial from a reputable seller on eBay still commands $200-300+ which is nuts to me. But, when I realize that I can do all of my modern graphics workflow in this 12 year old software I get it.
I would love to use some of the newer parts of the suite but the functionality of my CS5 still 100% covers my use-case. For photography I've ended up on Darktable, and if I need to manually retouch a photo there's nothing stopping me from a Darktable <> Photoshop CS5 workflow.
As much as I want to love Gimp - I can't. It is outright ineffective and lacks features compared to even my 12 year old Photoshop. The people who continue to tout it as a 1:1 replacement have never worked in a professional graphics workflow.
Also, Procreate is amazing for doing illustrations though - I really wish I had it when I was learning digital painting!
---
Regardless, just wandering sharing anecdotes because I relate to your experiences. Hard agree that legacy versions of Photoshop (and honestly the entire suite) are still insanely powerful. I also find them to be way more stable than their newer counterparts. They're just objectively a better financial decision - I bought this a decade ago and I don't have a monthly $50-60 Adobe draw on my bank account.
PS CS5 is one of the best pieces of software ever released.
It is honestly miles better than any modern PS clone. It's kinda sad how no open source alternative has even come close.
Every other alternative is a compromise in some way or another.
Are you using yours on an older machine?
Here's my install notes - just make sure you don't launch Photoshop/Illustrator prematurely:
* Skip the "setup an adobe ID" step
* Only install "Adobe Photoshop" and "Adobe Illustrator"
* On right-hand side deselect not needed components
* Story Extension
* Browser Lab
* Air
* Media Player
* Device Service
* Site Catalyst
* Keep useful components
* Fonts
* Extension Manager
* ExtendScript
* Check both "Services" and "Task Scheduler" to make 100% the update manager did not get installed
* Disable Adobe SwitchBoard service
* Delete the OOBE directory from C:\Program Files (x86)\Common Files\Adobe
* Delete the AAMUpdaterInventory directory from C:\Program Files (x86)\Common Files\Adobe
* Launch Photoshop, Photoshop x64, and Illustrator for first time and skip past any registration screens
* Reboot system and repeat previous two steps to ensure no updaters/etc. are installed and software works without warning on first load
* NOTE: On reboot/second check it looks like a service gets scheduled so repeating these steps is important! (hooks on reboot by Adobe installer)
* Type "Startup Apps" and ensure all Adobe apps not starting with system> Note that Wine does not work well with macOS 10.15 Catalina. Apple removed 32-bit support in Catalina, which is a critical part of the macOS system that almost all of Wine relies on. You can run 64-bit applications through Wine on Catalina, but very few applications for Windows are 64-bit. If you need to use Wine, you should not upgrade to Catalina.
https://www.davidbaumgold.com/tutorials/wine-mac/#:~:text=No...
Photoshop from that era was pretty simple and easy-to-write. It worked well, and so did the alternatives. Adobe invested an incredible amount into research to build a more serious moat around 2022-era Photoshop.
I appreciate the continual new features and updates (exception: losing the Pantone solid book), but I feel the overall value proposition is better than it’s ever been. I remember spending hundreds annually on design suite upgrades. Now, a regular subscription gets me all of their software, a generous font selection, photoshop brushes, much more.
Taking Adobe for granted and kicking them around online has become a sport for some, but I suspect it’s a very loud but small segment of their customers.
I'm as eager—if not more—to take on massive greedy corporations as the next person, but my guillotine would be dull well before I got to Adobe's neck.
I agree that Figma shares many of these same issues performance wise. Truthfully the only creative software I use that I truly enjoy these days is Blender. Hopefully one day the passion of Blender will make it to other areas in the creative software space.
The new save dialog is insane. No, I don't want to save a copy just because I want to save a jpeg. Why is this even a question?
I have no idea why it isn't possible to copy/paste text with its blending options. Select All, Copy - Nope. All you get is the text, with none of the effects. (I know you can duplicate a layer - but not to a different document.)
Why does Creative Cloud install three versions? I suppose it's nice that I have v21, v22 and v23 but - why?
There still isn't a simple "paste clipboard to new document" command - something Paintshop Pro had back in the 90s.
Does anyone at Adobe actually use PS professionally? These are all simple usability issues that could be fixed with a bit of thought. But instead we get Neural Filters - useless - and the occasional core behaviour that changes for no good reason.
I don't like the new save/load stuff either, and much prefer the old versions you can toggle, but that does bring up the fact that /you can toggle stuff/ and really customize the app to your preferences. I don't know any other visual creative tools with the depth of customization that Photoshop affords, between the fully modular GUI, actions, etc. A side note: jpgs saving as a copy has always been the default when you're working with a psd. There used to be a way to turn off the 'copy' appendage (like you can when duplicating layers), but I can't remember if it's still there.
> I know you can duplicate a layer - but not to a different document.
You can, actually! Been able to for a very long time. Right-click on the layer > Duplicate layer > Destination > Document. Pick another document you have open or create a new one with that layer. Pretty handy!
Sure you can, at least as far back as CS6. In the Duplicate Layer dialog, there's a Destination group that includes a Document dropdown. You can select any open file or create a new one to serve as the target.
There are a lot of other useful settings in that panel for people (like me) who don't like a lot of the changes that have come down with Creative Cloud file handling.
> I counted 20 processes running the last time I had PS installed
I don't check how many background processes are running when I use Photoshop because I don't notice them at all. Almost every feature I use in it feels responsive, especially compared to how it used to be. If you're talking about telemetry, yeah, I hate that too, but I've more or less resigned to it as a necessary evil in all my professional tooling.
> The apps all take forever to load
Photoshop opens nearly instantly on my M1 Max Macbook Pro, as it did on my M1. It was slower on Intel, but what wasn't. I can open and close Photoshop three times before Discord even loads an empty window.
> drain battery if working remotely
I've never tried a remote workflow with Photoshop, so can't speak to that at all. Definitely does not seem like what the program is optimized for, and I would think battery drain would be the fault of whatever tool you're using to remote in, no? Or do you mean just working on an unplugged laptop? In which case, I find Electron apps that do one task poorly tend to be less efficient than even heavier desktop apps that 100 things well, Adobe or otherwise.
> and are far more unstable than in the past.
Sorry, what? I haven't had an Adobe app crash on me in probably eight years. I of course count that as good luck, but to say the current builds are less stable than older versions is just … insane to me. Thinking back to, say, the CS2/3 days, half my time in the program was spent Cmd+S-ing for fear of the inevitable hourly crash and loss of work. Photoshop crashes were a legitimate part of creative culture from like 1999 to 2012.
Sorry if I sound like an Adobe shill. We've just clearly had very different experiences with their products of late.
Where we are in agreement is that Blender is cool! I'm too much of a neophyte in 3D workflows to assess whether I think it's ultimately well designed (some bits seem to be … others not so much?), but it seems to run very well on the various machines I've tried it on and I have a great deal of respect for the nature of the program and the people behind it.
Photoshop CC 2022: 35 seconds until the workspace appears
Affinity Photo: 8 seconds
and for fun, a tool that I still frequently use even in 2022:
Jasc Paint Shop Pro 7: 1 second.
Given their position in the market, they could be cutting edge software performance wise and everything else. No one can say they don't have the resources.
Instead, they buy innovators (that solely exist in the first place because Adobe failed to keep up), do bare minimum to maintain, and charge rents.
It seems it's written in C# as it uses Avalonia UI.
It seems their intention is not only to provide AI-based audio editing and recording but also to cover the ground of what Riverside already offers.
Remote recording - Recording with others is as easy as sharing a link. Everyone’s audio is recorded in high quality locally, then Project Shasta syncs it back together in the cloud automatically.
"Soon to come features" list things we can already find in Descript, such as filler word removal or speech enhancement. And features already available in the beta include microphone checking for optimal quality and microphone distance, AI-powered audio, remote recording with guests, and project templates.
I was waiting to see what Adobe's take on AI-based audio editing and recording was, and it seems it's here. At the moment the project is referred to as Shasta; I imagine these capabilities either format a new product offering or are integrated with existing tools like Audition, Premiere, or After Effects.
What do you think?
I still think it will be a while before AI is ready to create more than a first draft edit but if it handles 95% of the easy cases that's still a huge time-saving - especially on long-form projects. I spent so, so many hours of soul-sucking, rote drudgery doing things like manual audio ducking back in the day.
A 60-90 minute episode can take 10 hours of intense editing by hand, longer if there are quality issues on material recorded in the field. My stuff sounds good but I've been making arrangements to hand off a lot of it to a junior editor and incorporate machine transcription/partial editing to take care of the 'first pass', and I can't tell you how relieved I am.
Whisper, whisper, mumble, mumble, EAR PIERCING LAUGH, whisper.
Adobe XD : Sketch :: Shasta : Descript (https://www.descript.com), right down to the advertising style
I personally don't think of making a copycat product as "Sherlocking". Wikipedia says Sherlocking is "releasing a feature that supplants or obviates third-party software". https://en.wikipedia.org/wiki/Sherlock_(software)#Sherlocked...
I also tested with wind noise (outdoor speaker) and the audio "recovery" is amazing. It rescues bad field recordings that you normally can't use. I'm impressed!
Buuuut in the meantime, we launched two of our AI features as standalone mini apps that anyone can use for free, and those are called Mic Check and Enhance Speech. They’re fun, try them out and let me know what you think.
I never know what gain I should set on my XLR mic + USB audio interface and I also don’t know how Teams/Webex will do to my signal. Is it compressing my signal? Noise gating it? No idea!
There is bunch of introduction material about "gain staging" online, here's just one to get you started: https://www.audiotechnology.com/tutorials/microphones-levels...
Not mobile friendly yet though.
I wonder if they made Descript an offer before starting this project. Although, the base problem of editing audio or video with text isn't that difficult. They probably thought it could easily be cloned. The devil is in the details however, and the rabbit hole runs deep.
What specifically is Descript doing that Adobe couldn't do relatively easily, or isn't doing already in its other NLE products (Premiere, Audition, Rush, After Effects)?
I hate that this came up AFTER I logged in...