Skip to main content

Filter by idea status

10000+ Ideas

gregbenzInspiring

Add Rec.2020 as a default colorspace option in PhotoshopOpen for Voting

The Rec2020 colorspace (aka ITU-R BT.2020) is a critical colorspace for photography and not a standard option in Photoshop. You can only install it yourself or open a file which already has it embedded, which makes things cumbersome and prone to error (there are different Rec2020 profiles on the web with different gammas, etc). Rec2020 is the preferred colorspace for HDR (and is LRC's working primaries when in HDR mode). Rec2020 is also very ideal for print-related work as it includes many printable colors which fall outside Adobe RGB / P3, and yet avoids the excess of ProPhoto (which includes many imaginary values outside the range of human vision). Request: please add default support in Photoshop for Rec.2020 colorspace (ie just as we have default support for sRGB, ProPhoto, etc). Ideally this colorspace would use a D65 white point and rec709 EOTF to faciliate SDR workflows for print. That ETOF would be most consistent for SDR editing controls in curves, color picker, etc under the roughly gamma 2.2 used most often with sRGB, AdobeRGB, and P3 (note that the EOTF would be linear by default in 32-bit mode and therefore consistent with opening an image in Rec2020 ACR). Note: If you set LR external editing colorspace for ProPhoto and then open a RAW smart object in PS, it will use Rec2020 as the closest match. So this creates a path for some Rec2020 support, but it is a confusing/hidden option and does not support SDR. Rec2020 is a better choice in SDR for many workflows. Rec2020 is an explicit and always available option in ACR, and should be in LR as well.

ElectricMayhem2Participant

Allow AEP files to be imported as an asset inside of AEOpen for Voting

Similar to the idea of how InDesign works (where you can nest InDesign files in other InDesign files) and designs have rippling impact, I'd love to be able to import an AEP into a current file. Not only import it, but selectively choose composition I'm interested in. That comp would act simply like a layer in my timeline. Bonus points, any Essential Properties created would be surfaced. Like with Photoshop or Illustrator files, any changes made in the source (once saved) would be refreshed and pulled back into my existing composition.Extra bonus points if this is something that could be somewhat without limit. Coming from the world of UI / UX motion, this would solve a massive need for standard components. We could build out individual elements and bits of motion that are effectively classes of elements, that we'd continue to plug into additional projects.  So a key UI element could have easily 4 or 5 different "AEP layers" in it.  Treat it like a layer. It has all the usual transforms cause it should likee footage. Treat it like a layer. I can apply effects to it, because its basically like a precomp.Esssential Properties allow for nuanced control, if they're set up by the creator.Live changes push out to all instances of it, like a visual design updating a design I'm currently animating.Instance control and branching/forking becomes the same mindset as version control for other assets. High-level and lofty requests: a way to see how many times this is being referenced / used in someone else's projects. Similar to how many times a comp is used, it could be nice to know if someone else is using my comp on the same network before I go and make a destructive change that could ruin things for them.