Feature Requests

I'd love to be able to do interviews with people who don't speak the same languange as me via live translation during recording.

project is stuck at rendering when downloading for 90% since an unusual time, but was not notified as a user in the Windows program, in detail it was stuck for over an hour and I only was able to complete rendering by force closed the Windows client, hit "update" button there and let the whole process do again from 0% after waiting for over an hour in vain. I know about the local method to render too, but I am using the cloud method because it is supposed to be quicker. Why not fixing the thing and implementing a monitoring that warns the user if there is an issue and it's stalling? I expect the program to tell me when there is an error and not stuck at 90% without any progress for literally over an hour.

Support persian language for video editing, translations, transcription, etc.

Make Underlord reliably mute high-intensity curse words (with strict timeline preservation, no cutting or ripple edits) in one step, without repeated prompting or manual fixes. The current process requires multiple attempts and constant reminders, even with clear instructions. This is a common editing need, and having it work seamlessly would save a ton of time and frustration.

When I'm editing a video with Underlord, if I've got multiple edits I want to make in parallel or as I'm going through it, I want to make edits, it'd be great for me to do a lot of them at once and not have to wait until Underlord finishes one to send the next one.

I find that when editing the video time lines and stacking more elements that the video viewing screen just keeps getting smaller I do have a bit of a workaround in that I open the web descript in two browser windows and using Chromes split screen in with 2/3's for the larger screen and 1/3 for the Editing side. But that is not ideal as I have to keep starting and stopping both sides to do edits. And also I prefer to use the desktop app. Please can you make it so the video can pop out in a full screen view - Like Googles Picture-in-Picture extension. https://chromewebstore.google.com/detail/hkgfoiooedgoejojocmhlaklaeopbecg?utm_source=item-share-cb Unfortunately this does not work for the descript screen - But this would be awesome to have and with the option to sync play from both sides or move timelines independently. An easy solution to this for you is just to add timeline editing t as an option in the right hand panel that i can now open Media AI Tools etc.

Project: Cathy Hockey Multi Cam Video (project ID 7e92d24b-454a-4bb0-bd07-49b1caba3624) Setup: Descript desktop app on Mac, working alongside the Descript project agent / API, which operates on the cloud copy of the project. The problem: There is no way to see whether the desktop app has finished syncing to the cloud, and no way to force or confirm a sync. When every edit happens in one app this is invisible, but the moment the project agent is involved it becomes a real hazard: the agent edits the cloud copy, so any agent job fired while desktop changes are still uploading runs against a stale composition. The workflow guidance ends up being "wait and hope," because the app exposes no sync state at all. What this cost us in practice, on one episode: Manual setup done in the desktop app (sequence build, track fader changes, speaker labels) wasn't verifiably in the cloud before agent jobs ran — the only available check was comparing composition durations by eye between the desktop timeline and an API read. At one point the cloud copy reported the composition at 2:47:38 (duplicate sequence insertions) while we were troubleshooting in the desktop app — with no way to tell whether we were looking at a synced state, a mid-sync state, or divergence, and no timestamp anywhere saying "cloud last updated at X." Track volume changes made in the desktop app appeared not to take effect in cloud reads for an extended period — impossible to distinguish "not synced yet" from "changed the wrong control" (both turned out to be true at different points, and diagnosing which was which took hours). Suggested fixes: A visible sync indicator in the desktop app — synced / syncing / offline, with a "last synced to cloud" timestamp on the project. A manual "Sync now" action. On the agent/API side: expose the project's last-synced timestamp, and have the project agent warn (or refuse) when the cloud copy it's about to edit is older than the most recent desktop session — an "editing a possibly stale composition" guard. Longer term: a conflict/divergence warning when desktop and cloud states differ materially (e.g. composition duration mismatch). For a workflow where a human edits in the app and an agent edits via the cloud — which your project agent actively encourages — sync state can't stay invisible.

Subject: Silent composition — nested track volume controls are undiscoverable, and one accepts changes it doesn't persist Project: Cathy Hockey Multi Cam Video (project ID 7e92d24b-454a-4bb0-bd07-49b1caba3624) Setup: Multicam workflow — a sequence built from one master audio file plus four camera clips (camera audio used for sync only), the sequence placed on a composition's script track. Desktop app on Mac, synced to cloud. The problem: My composition played back completely silent, and it took the better part of a morning to find out why. The cause: the same audio track effectively has three separate volume controls at different levels — (1) the track inside the sequence in the media library, (2) the composition's own copy of that sequence sub-track, and (3) the parent script track in the composition. I set the volume to 100% at levels 1 and 3, in the places the UI naturally led me, and stayed silent — because level 2, the one that actually governs playback, was at 0% and is the hardest of the three to reach. Nothing in the UI indicates that a child track is silencing playback while the visible parent shows 100%. Steps to reproduce: Create a sequence from a master audio file + multiple camera clips; set track volumes inside the sequence. Add the sequence to a composition. In the composition, set the sequence sub-track volumes to 0 (e.g. while muting camera scratch audio). Open the sequence from the media library and set its master audio track to 100% — playback of the composition remains silent. Select the composition's script track — the properties panel shows Audio 100%, while the composition still plays silent. A second, related bug (API/agent): The Descript project agent's track-modification tooling, when asked to set gain on a composition's sequence sub-track, reports success but the change does not persist — re-querying the document shows the gain reverted to 0. If sub-track gain isn't writable in that context, the operation should fail loudly instead of silently reverting. Suggested fixes: When a composition's effective output is silent because a child track is at 0, surface that on the parent — e.g. a muted-speaker badge on the script track and on the waveform, with a click-through to the offending layer. Consolidate or clearly label the volume hierarchy — "this control affects the library sequence only, not compositions that already contain it." Make the agent/API modify_track gain operation on sequence sub-tracks either work or return an explicit error, never a false success.

Great creative tools often improve because people keep sharing practical suggestions. sales coaching for sdrs https://lemcoach.com/for-sdrs fits into a broader conversation about how communities exchange ideas that make workflows more effective. Every feature request starts with someone noticing a small friction in their daily routine. Those observations may seem minor at first, but they often lead to meaningful improvements. A collaborative feedback space allows different perspectives to meet in one place. Users can explain real situations instead of only reporting problems. Others can support ideas they find valuable through discussion and voting. This creates a clearer picture of what matters most across the community. Creative work is constantly changing with new technologies and expectations. Listening to users helps products adapt to those changing needs over time. Open conversations also encourage thoughtful problem-solving instead of quick assumptions. Many practical features begin as simple suggestions from everyday users. Seeing how others approach similar challenges can inspire new ways of working. Constructive feedback benefits both creators and the wider community. It helps identify patterns that may otherwise go unnoticed. Small improvements can make everyday tasks smoother and more enjoyable. Communities grow stronger when ideas are shared respectfully. Every contribution adds another perspective to the discussion. Innovation often comes from continuous learning rather than dramatic changes. A space that welcomes feedback encourages steady progress. Meaningful discussions help shape tools that better serve real users. Simple suggestions can have a lasting impact over time. Thoughtful collaboration remains one of the strongest drivers of improvement. That is why community-driven feedback continues to be valuable for everyone involved.

While exploring account executive sales coaching https://lemcoach.com/for-aes it becomes clear how valuable structured feedback can be for product improvement. Ideas become more useful when they are supported by clear context instead of quick reactions. A well-organized discussion helps teams understand the real challenges behind each request. Community voting also highlights which improvements matter to the largest number of users. Thoughtful feature suggestions often reveal everyday workflows that deserve more attention. Constructive comments can provide examples that make requests easier to evaluate. Sharing practical experiences encourages more informed conversations among contributors. When updates are communicated openly, users feel connected to the development process. Transparency creates confidence that feedback is being reviewed with purpose. Different perspectives often uncover creative solutions that might otherwise be overlooked. Clear descriptions reduce confusion and help avoid duplicate suggestions. Respectful discussions make collaboration more productive for everyone involved. Tracking progress on requested features gives users better visibility into future changes. Organized feedback platforms make it easier to prioritize improvements based on real needs. Every contribution, no matter how small, can help shape a better experience. Listening carefully is often the first step toward meaningful innovation. A community grows stronger when ideas are shared with clarity and patience. Good feedback is not only about identifying problems but also about explaining why they matter. Consistent participation creates a valuable record of evolving user expectations. The best discussions focus on solving challenges rather than assigning blame. Simple, actionable suggestions are often the easiest for teams to evaluate. Over time, collaborative feedback helps products evolve in ways that reflect genuine user experiences. Open communication benefits both contributors and the teams building the product. Small insights shared today can become meaningful improvements in future releases.