Feature Requests

Many business processes involve details that are easy to overlook when everything is handled separately. Clear information can make routine tasks easier to follow and reduce confusion between different steps. For businesses dealing with international transactions, vat sales consultancy https://pearllemontax.co.uk/services/vat-consultancy/ can be one area where clear guidance matters. It can help teams understand how VAT-related sales activities fit into their wider business processes. Good documentation is also useful when several people are working on the same project. Instead of keeping important details in different places, teams can organize information around a clear workflow. This makes it easier to review what has already been completed and identify areas that still need attention. The same principle applies when recording meetings, preparing presentations, or editing business content. Tools that combine different parts of a workflow can make these tasks more manageable. A central place for notes, recordings, transcripts, and feedback can help people stay organized. It also gives users an opportunity to point out problems and suggest improvements based on real working situations. Small workflow improvements can sometimes make a noticeable difference to everyday productivity. Feedback is particularly useful because different users approach the same process in different ways. One person may need simpler navigation, while another may need better organization or additional controls. Collecting these observations helps highlight where a workflow could become more practical. It also creates a clearer connection between everyday user needs and future improvements. As business processes become more connected, keeping information clear remains important. Simple workflows, useful documentation, and accessible feedback channels can help teams work with fewer unnecessary complications. The focus is not always on adding more features, but on making existing processes easier to understand and use. That practical approach can benefit both small teams and larger organizations handling complex work.

With the focus shifting to video, please consider moving the search results box next to the transcript window. There is so much space between the transcript and the search query window, and then the results box all the way on the right hand side. This is especially true for people working with large, widescreen monitors. Or you know, you can just make all the windows movable and let us setup the screen however we want. But let's just start with moving the results window to the left hand side.

I use realign words in range allot as you transcription is often slightly wrong. Do use this function is very hard. Please make it easier.

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.

Descript insists in renaming the whole project with the title of the composition (if the project has a single composition in it). I've heard this from many of my clients who are confused why this happens. I know it was doing it before but only the FIRST time you renamed it. Now it does it every time. It does it to the point that even if the composition is deleted and a new one is created, the project takes on the name of that new composition. Please make it stop. Not only is this unpredictable, unexpected, unrequested, but some of my clients name their projects with some details such as the date of publication or other things, which get lost as soon as we rename the compositions. At least add an option to turn this behavior off if you don't want to remove it.

After that I click through and see in the change log the latest post from back in June.

Description: I regularly turn podcast recordings into short-form vertical clips, and the current workflow requires a lot of manual effort — resizing, cropping, reframing, and positioning speakers. I’d love a one-click feature that automatically converts a podcast-style video into a vertical (9:16) reel format. What the feature should do: Detect multiple speakers in the video Automatically create layout options such as: Top/bottom split screen Active speaker focus (dynamic switching) Picture-in-picture Auto-frame faces so each speaker stays centered Resize the composition to vertical (9:16) Smoothly handle transitions between speakers Why this matters: This would dramatically speed up turning long-form podcast content into short-form clips for platforms like Instagram Reels, TikTok, and YouTube Shorts. Right now this process takes several minutes per clip and requires manual adjustments. A one-click solution would be a huge workflow improvement for creators producing high volumes of content. Optional enhancement: Automatically adjust caption placement based on the layout so captions never overlap faces. Context: I’m a high-output creator using Descript to turn long-form content into multiple short-form assets. This feature would significantly increase my production speed.

show how many credits we have on the main screen with a box to buy more.