It seems it was fixed in an update. Haven't tried it recently, though. ... View more

Yes... There should be options, as I suggested in the original post. ... View more

No, it's not fixed on the Windows platform. Truly ridiculous. ... View more

Just as a follow-up... I also noticed that a few of my licensed assets are, strangely, no longer available on Adobe Stock, so if I wanted to re-use them, how would I do that? ... View more

It's only the *default* folder that Photoshop should choose. It shouldn't force anything on the user - that's not what I'm suggesting. When you do a quick export, Photoshop should display the Save As dialog, with the chosen default folder selected (an assets folder, or the folder where the image you're currently editing resides, or the last folder where you exported an image). You can navigate away from there if you wish. This used to be the default behavior, until Adobe changed it for the worse. ... View more

What we're discussing is the presence of the "assets" folder. That's what you want to get rid of. What I'm saying is that this has implications you may not have thought about. That may be what you are discussing, but that's not what we are discussing.   We are discussing Photoshop forcing us to either save in an Assets folder or as a Location.  Photoshop used to allow us to save in the same location as the file currently being edited, by default. That option was removed. We want it back as the current options create a messy workflow. Rather than delete the current Preference options, I suggested adding back the original functionality, but not forcing it on anyone by adding it as a third option in the Preferences. Those who are happy with the current functionality would not lose anything. Those who want the orginal functionality would get it back. "Export" would simply start the Export File dialog box in the location chosen by the user in Preferences (on of the three options).   Accidentally or automatically overwriting the original file during the Export function is not an issue. ... View more

For you they might be different file types, but for the next guy not. So my point stands: there has to be rules. Should it overwrite or not?   That's not a valid argument. The Export option would always show the "Save As" dialog box, which would allow you to navigate to any folder you want. But the starting point should be one of the three options given in the Preferences that we are suggesting. ... View more

It's pretty simple... 1) "Export assets to the location of the current document" This does what it says: if you're editing a PSD in C:\My Documents, when you export in another format, it exports the file to "C:\My Documents". 2) "Ask where to export each time" Asks where you want to save it... eg. "C:\My Documents\My Project\Images" rather than "C:\Photos" 3) "Export files to an assets folder next to the current document"... ...Is in no way the same as #1. #3 forces the user to save documents in a new "Assets" folder, rather than in the folder where the document that is currently being edited. Your concern about overwriting the document currently being edited is not an issue. For a start, you can't overwrite (using "Save As" or "Export") a document that's currently being edited in Photoshop. Photoshop won't let you. Secondly, if you could, you would receive a warning, just as you do when you try to overwrite ANY already existing file. All the 3 choices do is tell Photoshop which folder to serve up as the starting folder for the Export action. You can still navigate away from there to any other folder, using the dialog box options, if you wish. Just as it did before. We understand the point of an Assets folder. We just don't want it to be forced on us. We want the option that was available to us in earlier versions and taken away from us, which was to be able to Export to the same folder as the document that's currently being edited - not a subfolder. That's why I suggested three options, rather than just two. Right now, to save the Exported file in the same folder along with the original, we have to navigate from wherever the last project was (which may be on another drive, 12 folders deep!) to the current folder. It's clumsy. It's annoying. If people want to choose where to save the file each time, there's options #2 and #3, or just navigate to where you want to save it. -- PGP Encryption Available -- Request my Public Key ... View more

It's been over a year, with dozens of updates, and it still has not been (re-) implemented. ... View more

Yes, it seems a simple thing to (re-)implement, but Adobe is so busy adding new features that they are not paying attention to things that simplify workflow. Annoying. ... View more

It seems clear that something is not working correctly with the Export dialog settings. Adobe has given us settings to change the default location of exported files, but those options are inconsistent between the two Export options and they don't seem to work correctly for all users. I have previously given a suggestion on the 3 options that should be selectable by the user on where to export files which, if correctly implemented, would cover all of the options a user would want, specifically: 1) "Export assets to the location of the current document", 2) "Ask where to export each time" and, 2) "Export files to an assets folder next to the current document"   Number 2 would, I assume, default to the last folder used. ... View more

It seems starnge that there would be two different options for essentially the same thing... exporting a file... and those two options give you different choices!   Why would "Quick Export" give you the options: 1) "Ask where to export each time" and 2) "Export files to an assets folder next to the current document"   Whereas "Export As" gives you the options: 1) "Export assets to the location of the current document" and 2) "Export assets to the last location specified"   It seems to me that the options for BOTH Export features should be: 1) "Export assets to the location of the current document", 2) "Ask where to export each time" and, 2) "Export files to an assets folder next to the current document"   The labelling of those settings is also confusing and inconsistent. There's a setting which says: "Use legacy 'Export As'"  (notice the quotation marks) ...but  "Quick Export Location" and "Export As Location" are missing quotation marks which makes "Export As Location" seem to mean that you will be exporting something as a "location" rather than an image. Relabelling those settings as: Default "Quick Export as PNG" location       and Default "Export As" location ...would be consistent and the meaning clear.   I would assume that Photoshop knows the current working folder of the file it's working on (or else "Save" would not work), therefore an "Export PNG to current working folder" should be fairly trivial. Photoshop can already do it for "Export as..."!   The change we made was to the "Ask where to export each time" setting.   Yes! That's what I've been ssaying. I've never wanted Photoshop to create the separate assets folder, so never used that option. What Adobe changed is exactly what is now causing problems (for me). The "Ask every time" option has to start from some predetermined folder. [For me] it always started in the current working folder, which seems logical. Now it starts in the last folder used, which could be anywhere on the system. Maybe my workflow is unusual, but if I'm working on an image and want to export it, I'm probably going to export it to the same folder as the original, or in a subfolder of the current working folder, rather than to the folder of the last project I was working on. Regardless, the new workflow is a real pain. ... View more

BrettN,   You are right, there are two places to make the change. However, the setting you are talking about immediately creates a separate folder for the export, called "<Name of current file>-assets" with no further input frm the user, which is not what the previous incremental version did, nor what is wanted.   In the previous incremental version, when File - Quick Export as PNG was chosen, Photoshop would bring up a dialog box so you could chose where to save the PNG, but it defaulted to the same folder as the currently edited image. That meant you could navigate to a different folder, or simply press Enter to save in the same folder as the image currently being edited. There is now no way to do this. If you set it to always ask, it starts with the last-used folder, which could be anywhere on the system. If you  select "Export files to an assets folder..." it creates a new folder.   The setting that should work, is the option wich is only given for "Export As Location":  "Export assets to the location of the current document" - but as you point out, that only for "Export As", not "Quick Export as PNG". ... View more

Sorry, it was a typo. The version I'm running is the latest version. I keep it updated whenever an update is available. Photoshop updated this morning to 23.2.1 and that's the version that's giving the issue. ... View more

Yeah, for me, it just started working. It was working for me when I used it last week and I haven't had an update since then. ... View more

If it's a known issue, then I'm not overly concerned...   I don't think my method of ingesting the clips was anything special:   The original video was captured by a Canon EOS 5D MK II onto an SD card. The clips were copied to the editing computer and then the project created. The clips were imported into Premiere Pro (version 6) by double-clicking on the project panel and selecting the clips.   I opened the old project in PPro 2022. It contained many clips and sequences that are no longer needed, so I removed unused sequences, saved the file to a PPro 2022 project and removed all unused items (File - Remove Unused). I then went to the Project Manager and tried to copy the project to a new location. That's when this problem ocurred. ... View more

After the exact same thing happened with another computer. It was working fine 5 weeks ago when it was last used. It stopped working in the exact same manner after Adobe Creative Desktop App updated automatically. After speaking with Adobe, they've agreed it's a bug in their system. They are now working on fixing it. ... View more

I have several licensed fonts, including Swiss. I have uploaded them to the font manager that's part of Adobed Creative Cloud Desktop. In that program, they show as installed and active. However, Photoshop and the other Creative suite apps can use them until the computer is rebooted, at which time the Creative Suite apps can no longer find them. They are still listed as installed and active in the Creative Cloud Desktop app. The only way I can use them, is to delete them from the Creative Cloud App and upload them again. That works until the next reboot. This is still happening, so my problem is NOT solved. ... View more

FIXED:   1) Uninstalled all my fonts. Reinstalled. Did not help. 2) Repaired Creative Cloud Desktop App. Did not help. 3) Uninstalled Creative Cloud Desktopo App. Reinstalled Creative Cloud Desktop App... froze during installation. 4) Uninstalled Creative Cloud Desktopo App. Reinstalled Creative Cloud Desktop App... froze during installation again. 5) Used Creative Cloud Cleaner Tool. Reinstalled Creative Cloud Desktop App... froze during installation. 6) Uninstalled Creative Cloud Desktop App. Used Creative Cloud Cleaner Tool.... rebooted. 7) Reinstalled Creative Cloud Desktop App. Worked!   What a waste of time!   ... View more

...I should add, that Adobe Fonts shows it as Installed and Active. ... View more

Here's what I see... ... View more

Interesting. I don't see how OneDrive could mess up metadata, when it's a direct copy of the file. The folder on the C: drive was copied to a OneDrive folder, and then copied back to the new computer's C: drive. The project never referenced OneDrive at all, as it was created on the first computer's C: drive, using assets on the C: drive. Further, since the project opens fine when going the "File - Open Project" route, but not when simply double-clicking on the project file, this suggests to me a problem with PPro. After all, it's the SAME project, whether it's opened by double-clicking the project file, or opening it from within PPro once it's running. If there was a problem with the project file, or its metadata, PPro would barf no matter how you tried to open it.   Copying the folder to and external drive, and then copying it to the new computer yields the identical results: It hangs PPro when you double click on the project file, but opens fine when inside PPro and using "File - Open Project". ... View more

Hahaha! I was just about to lambast you for not reading the post closely! 🙂 No problem... but I think there is a bug somewhere in PPro CC that causes this. I tried it on 2 computers, one with a fresh PPro installation. ... View more