Skip to main content

Filter by idea status

10000+ Ideas

heygabecomParticipant

Respect MacOS Standards. Stop Storing App Data in the Documents FolderOpen for Voting

Problem Statement Currently, on MacOS, Adobe Creative Cloud applications (such as Adobe Media Encoder, After Effects, Photoshop, etc.) create and store application preferences in subdirectories inside: ~/Documents/Adobe/ For example:~/Documents/Adobe/Adobe Media Encoder~/Documents/Adobe After Effects 2025~/Documents/Photoshop Cloud Associates~/Documents/Lumetri This is problematic for several reasons related to both MacOS platform conventions and user workflow. 1. Violation of MacOS Best Practices According to Apple’s MacOS Human Interface Guidelines:The ~/Document directory is for user’s personal documents.The ~/Library directory is for containing application settings, preferences, and other system resources that are specific to the user. Should not contain user data. Check the Apple's Library Directory guidelines. In general the Unix-based system principles, user configuration and application support files should not be stored in the Documents folder. Instead, the following directories are recommended:~/Library/Application Support/ for app data and configuration files~/Library/Preferences/ for user preferences~/Library/Logs/ for logs~/Library/Caches/ for cache files Using ~/Documents/ for internal app data violates this convention and results in unwanted clutter. 2. Conflicts with Cloud Sync (iCloud Drive) Apple consider the ~/Documents as a directory for user's files. And they build features within their ecosystem following that principle. At WWDC 2016 they announced a new feature that when enabled, MacOS automatically uploads the contents of the ~/Documents and ~/Desktop directories to iCloud Drive. This has been a default suggested option during MacOS setup for many years, meaning many users unknowingly enable it and then face unintended syncing of app  created folders like ~/Documents/Adobe. This bechavior leads to multiple issues:Application data and logs are synced unnecessarily across machines, causing instability and sync conflicts. In the way MacOS resolve conflict is to keep both files, which is unpleasant experience.It’s not possible to maintain different app states/preferences on multiple devices because they are constantly overwritten by iCloud sync.Ambiguity of how Adobe use the ~/Documents/Adobe directory. I was not able to find documenation how Adobe use the directory and is it safe to put my own content under that directory. 3. Obstructed File Organization I rely on ~/Documents for real project files. Adobe’s hardcoded usage of the Documents folder prevents me from safely using logical folder structures like:~/Documents/Adobe/Photoshop/project-name~/Documents/Adobe/AfterEffects/project-name This is not safe or predictable given that Adobe Creative Cloud may overwrite this folder during updates or runtime.Community Feedback This issue has been raised multiple times over several years, yet remains unresolved:Adobe Forums: “Adobe folders in Documents folder – Mac & Windows”Apple Forums: “Adobe creating folders in Documents”Adobe Ideas Portal: “Stop all Adobe products from creating an ‘Adobe’ folder in the ‘Documents’ folder”Adobe Media Encoder forum threadAnd many more places Suggested Solutions Option A (my own prefference and best operation system practices) Adopt the MacOS native directory conventions. Move preferences, config files, and logs to appropriate paths within ~/Library/Application Support/, ~/Library/Preferences/, ~/Library/Logs/, etc. Option B (safe alternative) If change might break legacy workflows or it is considerd as higer risk to change the default bechavior, at least provide a user configurable option within Creative Cloud App for all apps to:• Set a custom directory for app preferences and logs• Disable creation of ~/Documents/Adobe entirely

ハナモゲラKnown Participant

I wish Premiere could encode including codec conversion by using preview files.Open for Voting

Sequences that contain heavy effects need to be rendered many times during editing.Even though the preview files are already exist after rendering,Premiere can't use those preview files when encoding.It is too inefficient to start over from rendering when encoding.For example, there is a sequence that takes 40minutes to export,35minutes are for render, 5minutes are for encode.Even if I had already rendered the sequence, it takes 40 minutes again to export.To reduce total encoding time, we need to the steps below.1. Export the movie with the same codec as the sequence. (no codec convert)2. Place the exported movie in the sequence.3. Encode. (with codec convert)If Premiere can use preview files when encoding, we just do step 3 after rendering. 高負荷なエフェクトを含むシーケンスは、編集中に何度もレンダリングする必要があります。レンダリングの結果プレビューファイルが既に存在しているにもかかわらず、Premiereはエンコード時にそれらのプレビューファイルを使ってくれません。レンダリングからやり直しになり、あまりに非効率的です。例えば書き出しに40分かかるシーケンスがあり、レンダリングに35分、エンコードに5分かかるとします。既にレンダリング済みのシーケンスであっても、書き出しにはやはり40分かかります。エンコード時間を短縮するには、以下の手順を実行する必要があります。1. シーケンスと同じコーデックでムービーを書き出す。(コーデック変換なし)2. 書き出したムービーをシーケンスに配置する。3. エンコードする。(コーデック変換あり)エンコード時にプレビューファイルを使えれば、レンダリング後には手順3を実行するだけです。