A dedicated community for Photoshop on the Web is highly necessary due to the fundamental differences between the web and desktop versions. Web-based users require troubleshooting for browser-specific issues, including browser performance, WebGL support, hardware acceleration, and cloud syncing. In contrast, desktop users face operating system configurations and hardware-level issues. Furthermore, Photoshop on the Web has a divergent feature set and tailored user workflows. Creating a separate community will drastically reduce clutter and confusion for users seeking targeted assistance.
I want to report a bug and request a feature update in Firefly. Currently, the ElevenLabs model supports Brazilian Portuguese voices, but it lacks the emotion mechanics that Firefly has. On the other hand, the standard Firefly model has emotion tags, but lacks Brazilian Portuguese voice support. I want them to make both features work together: Brazilian Portuguese voice support combined with emotion tags. Additionally, I would like to request the implementation of animated voice styles like 'Zozo' from ElevenLabs.
when using object transform to stretch, sheet, or skew a layer, the axis of refrence for the transform control box is locked in on the X/Y axis. now if you rotate the object, the axis of the transform control box will rotate with the object, but only until you confim the transform at which point it resets. This means that if you rotate a perfect square to be sitting at 45 degree angle, you can stretch it on a 45 degree axis into a perfect rectangle on a 45 degrees if its donew in only one transform. The issue is that after you confirm the transform, or if you have an object already at an angle you want to stretch on an angle, there is no simple built in way to rotate the angle of the transform box to match the angle of the layer/selection being transformed. This functionality is a basic necessity in all 3D modeling apps so I'm pretty surprised it hasnt been added to photoshop in the 15 years ive been using it. Before people start suggesting to just use smart shapes or some smart object mulsti step work around, or some combination of warp, sheer, and skew, thats not the point. The point is that for example, we should be able to even lasso select a group of pixels, and then quick and cleanly perform a single axis stretch at angles other than just 0 and 90 degrees. Even warp, sheer, and skew controls are effected by this as you cant perfrom a clean sheer on a box shaped object if the box is already sitting at an angle. What I propose is adding an extra control to the refrence point/rotation point crosshair that's in the middle of the transform control box. you could then rotate the crosshair in order to rotate the whole transform control box without rotating the actual selection. Another option could be holding a modifyer key when clicking to rotate the transform box, allowing you to rotate just the control box. Below is a simple example showing the limitations of the current transform controls.
Description of Feature:Add native drag-and-drop capability within the "Your files" dashboard, allowing users to drag file cards or list rows directly onto the "Deleted" trash can icon located in the left navigation sidebar to remove files.Current Behavior:Deleting a cloud document currently requires clicking the three-dot context menu on an individual file card and selecting "Delete," or using multi-selection controls. Dragging a file thumbnail directly toward the sidebar yields no interaction, as the sidebar navigation links do not function as drop targets.Proposed Functionality:- Allow users to click and drag one or more selected cloud document cards in the file browser.- Implement a clear visual hover/drop state over the left sidebar navigation items, specifically highlighting the "Deleted" trash can item when an asset is dragged over it.- Trigger standard deletion behavior upon releasing the file over the "Deleted" target, moving the document to the trash bin.Use Case & Benefit:- Workflow Speed: Significantly streamlines file cleanup workflows by providing standard, modern desktop file manager conventions directly in the web browser.- Reduced Friction: Minimizes reliance on contextual menus for basic file organization tasks, aligning Photoshop for the Web with conventional browser-based file repositories and operating system file managers.
Problem StatementCurrently, Adobe Photoshop on the web requires users to download exported files directly to local storage. For workflows centered entirely around cloud storage, users must download the image to their local hard drive and then manually upload it to Google Drive. This multi-step process introduces unnecessary friction, clutters local downloads folders, and slows down content delivery.Proposed SolutionIntegrate native Google Drive export functionality into Photoshop on the web. Alongside the standard local download option, users should have the ability to authenticate their Google account and send exported assets directly to their cloud storage.Recommended Capabilities Direct Export Destination: Include a "Save to Google Drive" option within the export menu. Folder Navigation: Provide a lightweight directory picker allowing users to select specific folders or Shared Drives. Standard Format Support: Support direct export for common file formats, including PNG, JPEG, TIFF, PSD, WEBP, and JXL. OAuth Integration: Utilize standard Google authentication to connect and disconnect storage securely. Workflow BenefitsThis enhancement would significantly streamline productivity for individuals and organizations utilizing Google Workspace for digital asset management. It would eliminate redundant file transfers and provide a seamless browser-based experience for cloud-first environments.
In C4D you can 'mute' keyframes - essentially this acts like deleting the keyframe except that a dummy 'reference' key is left there, perhaps greyed out, that stores the value(s) and interpolations it had before it was muted. Keyframes to either side behave exactly as if it was not there, until it is un-muted.
el problema viene desde hace semanas y dias
cada vez que intento generar un video con Adobe Firefly siempre hay fallos, tanto de coordinación de imagen, como de sonido en otro idioma, como de incorporar personas que no deseo, etc etc. El problema es que, aunque el programa se equivoca, los créditos se los cobra igual si después quieres repetir, o intentarlo por segunda vez. Una tomadura de pelo
I’d love to see a long-form to short-form video clipping feature added to Adobe Firefly.The feature would allow users to upload a longer video and automatically generate multiple short-form clips optimised for platforms such as Instagram Reels, TikTok, YouTube Shorts and Facebook.Ideally, there would be two clipping modes:1. Speech-Based ClippingFirefly analyses dialogue, captions, key phrases and topic changes to identify the strongest moments within a longer video. It could automatically create short clips with suggested hooks, captions and different duration options.2. Visual / Non-Speech ClippingThis is particularly important for content that doesn’t contain dialogue, such as ASMR, beauty, product videos, craft content, tutorials, cooking, cinematic footage, behind-the-scenes videos and aesthetic content.Instead of relying on speech, Firefly could analyse: Visual changes and scene transitions Camera movement Subject movement and actions Interesting or satisfying moments Changes in composition Audio peaks, sound effects and music beats Repetitive or low-interest sections that could be removed Natural start and end points for short-form clips For example, I regularly work with ASMR content where there may be no dialogue at all. I’d like to be able to upload a 4–10 minute video and have Firefly identify several visually or sonically engaging moments and turn them into 15, 30 or 60-second clips automatically.It would also be useful to have: Automatic 9:16 reframing and subject tracking Multiple clip suggestions from one video Adjustable clip length “More like this” regeneration for a selected clip Platform presets for Reels, Shorts and TikTok Automatic captions when speech is present Optional music/audio beat detection Hook or opening-frame suggestions Ability to manually refine the AI-selected in/out points Batch export of generated clips This would make Firefly much more useful as an end-to-end AI video workflow, particularly for creators and brands producing large amounts of social content.A visual-first clipping mode would also differentiate it from many existing AI clipping tools, which currently depend heavily on podcasts, interviews and talking-head content.
I’ve noticed that when sharing a board, I haven’t been able to directly include music or voice audio files. The only workaround I’ve found is to create a black video containing the voice audio, and another separate video for the music.I think it would be really useful to be able to add and share these types of audio files directly within boards, especially when working on collaborative boards, as it would make the creative process much smoother and allow all project assets to be kept together in one place.Thank youLourdes Molina
It would be great if Legacy option for Light layer would be persistent and not restored after every image close.Or bring back Brightness layer as separate layer.
Errores en la locución palabras mal pronunciadas, añadido de textos que no estabann en el prompt
você não mudou nada na imagem e mesmo assim cobrou minhas 3 gratis, sou assinante do adobe mais tenho o programa apenas no meu serviço
I switched my workstation from Windows to Linux and Adobe Lightroom is the only app I can't use now. It would be nice if Lightroom had native support including GPU acceleration on Linux. I would love to keep using it instead of migrating to something else.
This would allow people to start filenames with date-time so alphabetical order is same as capture time order, and would create unique filenames (without yet another field) and properly order bursts.... Presently, exif metadata includes subsecond field, but Lr filenaming template stops at full seconds. So for unique filenames, one would have to tack on some kind of sequence number or something as well. So, as things stand, one can have: YYYY-MM-DD_HH-MM-SS_{seq-num}_{photog/camera...} but not (as I would prefer): YYYY-MM-DD_HH-MM-SS-MS_{photog/camera...} A side benefit is that filename indicates subseconds between shots in a burst, which is otherwise unavailable in Lightroom without a plugin. Although, I could argue for displaying that too in formatted metadata display, even if only upon mouse-over. --------------- I would like to use Lightroom import dialog box for importing, instead of the plugin I use now, but it stops just shy of what I need/want still. - this is one of the things. However, if import actions were implemented, that would be enough.
The Sony DSC-RX100M5 is the predecessor model.
As you compare the grain effect beetwen Lightroom Classic and Silver Efex, you can see that SE is more natural, as the LR grain seems to be plastered on the entire image: the shadows and highlights are equaly recovered with grain while very bright zones shouldn't. It is very visible on B&W pictures.On a picture if I add film grain effect, I use a Luminance mask and reduce the grain slider to reduce grain impact on the Highlights. Not bad but not quite satisfying. I wish LR could implement a better film looking grain. Maybe a slider "preserve HL" could be added in the Grain panel, as it exists in the Vignette panel. Hope this idea helps.
Rather than using generative credits every time you click the mouse!How about only using generative credits when you click on keep!I mean TBH credits are really not a good thing at all!... Look I know that a lot of work has gone into this and yes you want to earn your money!But money is the problem here! I only just tried generative fill and I was amazed! Literally over night I thought that I can finally create something great and also over night I thought up plans for my future!Now I find out that there are generative credits!... basically everything is out of the window! So I created a really nice picture last night which looks absoloutely stunning!BUT it took countless... literally hundreds of clicks to get even close to what I was looking for! if this would have used credits then the whole process would have been pointless because I would never have gotten to where I ended up because I would not have had any credits left! So heres an example of why credits are not a good idea!...Example 1. I wanted a boy to look away from me... I wanted him to look into the distance! face away from the camera... BUT all I got is the boy smiling into the camera... smiling at me! that must have been 10 to 15 clicks alone to get a result that I clearly did not ask for! Example 2. I asked for smoke! BUT all I got was a distortion of the original image which made it look like you were seeing it through a water filled glass! I must have wasted at least 30 clicks on that... I tried using different promts instead of smoke!... so I tried swirling smoke,... Fog... Mist... I even tried Clouds... but nothing was even remotely close! Example 3. I asked for a ghost... I got a ghost BUT the ghost was always smiling... so I asked for an ANGRY ghost... BUT I still got a smiling ghost... again I wasted probably 15 clicks just on that! This is not to mention all the other clicks that I needed for other parts of the picture! so a hand was missing a finger... so I asked for a finger and was refused because it violated guidelines!!!... all I wanted was a finger to complete the hand!!!... The point is... to get anywhere close to what I was looking for I literally needed HUNDREDS of clicks! If these clicks would have been taken from the generative credits account then I would have been out of credits before I even had the basic... bare minimum theme of the picture I was tying to create!!! Now I work a normal job for a living but I was really hoping to create something in my spare time at the weekends and maybe... just maybe have a small side income from selling printed items with art that I would have created with generative fill!... printed on a cup for example... yeah I know not he best original idea... 😉 just an example 😉But with the idea of credits and how they are used I already see that I will not even have the chance to use generative fill... I simply dont earn enough money to get the full subscription for the 1000 credits and taking into account how fast they are obliterated by clicks simply makes this unusable! Adobe said they want this to be for everyone to use! BUT this is just restricting it in every way as far as I'm concerned!Please is there not a way to make this more accessible? Suggestion: at least... at the very least only charge credits when we decide to keep something! let us generate freely until we are happy with the generated image and then press keep!Also instead of generative credits let us just buy 1000 credits for £4.99 for example!... if adobe combines that with only charging when we decide to keep something then that would make it much more accessible and less wasteful of the credits themselves! If someone wants to just touch up a few areas of a photo the click option may not seem too bad from the adobe point of view!... But yesterday I created a whole CHILDHOOD MEMORY from scratch!... there is no photo of this memory nothing to alter with a few clicks... I used firefly for the basic image and then I used generative fill to alter the picture so it had everything it needed BUT this took countless clicks! I thank adobe from the bottom of my heart for making this even possible!I would just love to create MORE childhood memories... I would love to say don't charge credits at all... but that's not likely to happen so please if there is any way at all then please consider my idea! Thank you for your time! 😉 Ps... I would love to have included the image in this post but... it has such a deep meaning for me right now and I am currently in the process of dealing with my past which has not always been great!I lost my daughter to cancer ten years ago and everything is just so difficult sometimes!Last night when I created one of my memories with firefly it was unbelievable!... I just can not share it right now because to me it is not just a picture!... Again thank you for your time 😉
Subject: Serious Issues With Image-to-Video Generation in Firefly – Reference/First & Last Frame ErrorsHello Adobe Firefly Team,I would like to report a frustrating and recurring issue I have been experiencing with Firefly's AI video generation tools.I am a paying Firefly user and I have been trying to create a very simple cinematic image-to-video sequence using an image that I generated within Firefly itself. However, I have repeatedly encountered errors and limitations that prevent me from completing the workflow.My intended workflow is the following:I created a cinematic, fictional battle aftermath scene featuring an adult male character sitting in a natural environment. The character is tired and battle-worn, with mud and minor non-graphic blood marks on his clothing and face. He is sitting near a rock with a rifle resting beside him.I want to create a short cinematic video in which:The character initially sits upright and slightly away from the rock. The camera slowly moves from approximately a 60-degree angle toward a 45-degree angle. The character remains mostly still during the camera movement. During the final few seconds, he slowly leans backward and rests against the rock. Once he is resting against the rock, he takes one deep, slow breath. The environment, character, face, clothing, rifle, injuries, lighting and composition should remain consistent throughout the shot.I tried to accomplish this using Firefly's video generation tools, particularly the Kling 3.0 model.The problems I encountered are:Reference image problemsSome models appear to reject reference images containing a human face, with errors such as “reference cannot contain face.”This is particularly confusing because I am trying to use an image of the same adult character throughout the video, and maintaining facial identity is one of the main reasons I need an image-to-video workflow in the first place.First Frame / Last Frame problemI discovered that Kling 3.0 provides a workflow for using a First Frame and a Last Frame.This is exactly what I need.I created two images showing the same character and the same environment:First frame: the character is sitting upright and has not yet leaned against the rock. Last frame: the character is fully resting against the rock.However, when I attempt to upload the second image into the Last Frame field, Firefly repeatedly gives me a generic error such as:“Something went wrong.”There is no useful explanation of what caused the failure.The first image can be uploaded successfully, but the second image repeatedly fails in the Last Frame field.The images themselves are generated by FireflyThis is especially frustrating because these are not random external images. They are images generated specifically for this project using Firefly.Therefore, I would expect Firefly's own video models to handle them reliably, especially when using the officially supported First Frame / Last Frame workflow.I also tried adjusting the image dimensionsI suspected that the problem might be related to aspect ratio or resolution, so I recreated the images in a vertical format suitable for Instagram (9:16).Even after doing this, the Last Frame upload problem persisted.Different models produce different unexplained restrictionsI have tried multiple models available inside Firefly, including:Kling 3.0 Kling 3.0 Omni Veo 3.1 Veo 3.1 Fast Seedance 2.0 Seedance 2.0 Fast Runway Gen-4.5 Ray modelsInstead of being able to determine which model is appropriate for the task, I often encounter different restrictions, errors, or reference-image limitations depending on the model.This makes the workflow extremely difficult to understand.I am not trying to generate anything explicit, graphic, or unsafe. This is a fictional cinematic scene intended for creative/video production. The character is an adult, and the injuries are deliberately non-graphic and cinematic.What makes the situation particularly frustrating is that I am paying for Firefly specifically to have access to these creative tools, yet I have been unable to successfully complete even this relatively straightforward image-to-video sequence.I would really appreciate it if the Firefly team could investigate:Why the Last Frame upload produces a generic “Something went wrong” error. Whether there is currently a technical issue with Kling 3.0 and Last Frame uploads. Whether there are undocumented restrictions on faces in First Frame / Last Frame workflows. What exact image dimensions, format, resolution and aspect ratio are required. Whether First Frame + Last Frame is fully supported for Kling 3.0 inside Firefly. Why an image generated by Firefly itself may be rejected or fail when used as a video reference. Why the error messages do not provide enough information to diagnose the problem.Please provide a clear explanation of the correct workflow for creating an image-to-video sequence with a consistent human character using First Frame and Last Frame in Firefly.At the moment, the experience feels unnecessarily difficult and unpredictable. I would really like to use Firefly for my video projects, but these problems are preventing me from doing so.Thank you, and I hope this can be investigated.Best regards,A frustrated but genuinely interested Firefly user
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.