Feature Requests

Advanced Audio Export Settings for Cloud Destinations
I'd like to request that advanced audio export settings (channels, normalization, bitrate, and sample rate) be made available for cloud export destinations like web links and Google Drive — not just Local Export. Currently, I can only configure mono/stereo channels, LUFS normalization, bitrate, and sample rate when exporting locally. When exporting to cloud destinations, these options are hidden and Descript applies its own defaults. This is a problem for my workflow because: Platform-specific requirements: I produce YouTube mid-roll ad content that requires mono audio normalized to -16 LUFS. Without control over these settings on cloud exports, I can't guarantee my deliverables meet spec. Unreliable internet connectivity: I frequently work on Starlink and mobile connections where upload speeds are inconsistent. Descript's cloud sync and editing work fine on limited bandwidth, but exporting locally and then manually uploading large video files to cloud storage is a significant bottleneck. If I could export directly to Google Drive or a web link with the correct audio settings, I'd eliminate an entire step and a major bandwidth pain point from my workflow. Workflow efficiency: The current workaround — export locally with advanced settings, then manually upload — defeats the purpose of having cloud export destinations in the first place. Bringing advanced settings to all export destinations would make Descript a true end-to-end solution for creators working in bandwidth-constrained environments.
0
·
Exporting/Publishing
AI inserted chapters, etc uses typography characters and breaks RTF export
RTF transcript export with AI-generated content produces corrupted characters Description: When exporting a transcript as RTF from the Mac desktop app, any AI-generated content (for example, from Add Chapters) that includes smart punctuation results in corrupted characters in standard editors. Steps to Reproduce: 1. Open Descript (Mac desktop). 2. Generate or edit a transcript using an AI tool (e.g., Add Chapters). 3. Export transcript → RTF. 4. Open the exported RTF in macOS TextEdit or Microsoft Word. Expected Result: All punctuation (curly quotes, non-breaking hyphens, en/em dashes) displays correctly. Actual Result: Unicode typography characters appear as garbled text (mojibake), for example: • Curly single quote (‘) → ‘ • Curly single quote (’) → ’ • Non-breaking hyphen (‑) → ‑ ASCII characters (straight quotes, standard hyphens) display correctly. Additional Notes: • Exporting the same transcript as Markdown (.md) or DOCX does not reproduce this issue, indicating a problem in the RTF export encoding or Unicode handling in Descript. • This occurs immediately upon opening the RTF; no copying or pasting is involved. Environment: • Descript Mac desktop app (latest version) • macOS [insert version] • Test editors: TextEdit, Microsoft Word Impact: Breaks transcripts that contain AI-generated content and forces manual encoding fixes, making RTF export unreliable for workflows that require Unicode-safe punctuation.
0
·
Exporting/Publishing
Load More