Feature Requests

MCP import_media should respect user's default Project Settings (especially auto-leveling)
When a project is created via the Descript MCP server's import_media tool, it ignores the default Project Settings I've configured in the desktop app (Project Settings → "Set as default for all new projects"). The new project is initialized with Descript's factory defaults instead. This is most painful for "Perform automatic leveling on clips". The setting's own description says "Automatic leveling is done after import and record", so leveling is applied during the MCP import itself. By the time I can open the new project and toggle the option off, the clips are already leveled. Toggling it off post-hoc only governs future imports into that project; it cannot un-level the existing clips. The only workaround today is to re-create the project by dragging files in through the desktop UI, which defeats the purpose of automating ingest via MCP. The other two toggles ("Add room tone to new gap clips" and "Show wordless media in script") are at least recoverable via post-import toggling, but they still require manual fixing on every MCP-created project. Requested behavior: import_media should honor the authenticated user's default Project Settings, the same way a desktop-created project does. Ideally, also expose these settings as optional parameters on import_media so MCP clients can set them explicitly per project. Impact: I produce courseware in batches and use the MCP to create many lesson projects per course. Auto-leveling being baked in irreversibly forces a choice between automating ingest (and losing leveling control) or doing manual UI imports (and losing the automation). Honoring my saved defaults would fix this without any API changes.
0
·
AI
Created Greenscreen AI Speaker, but received a bodyless, splotchy ghost
I am experiencing severe reliability issues with the AI avatar and greenscreen features, which has resulted in wasted money. Initially, the AI repeatedly claimed it had completed simple tasks while failing to do so. I eventually switched to a simple greenscreen workflow, which worked well enough at first. However, when I tried processing another pre-greenscreened image, the system failed again. Across three scenes totaling 12 minutes and 30 seconds, it produced no avatar at all, eventually generating a "splotchy ghost." When troubleshooting, your AI assistant claimed to have taken an internal screenshot and stated the output looked perfect. When I pasted in my own screenshot of the actual output, the AI itself was alarmed by the severe distortion. Is your internal screenshot/diagnostic feature broken? I have clients ready to pay, but I am struggling to get a reliable product and am forced to use smaller and smaller variations to compensate. Competitors automatically issue refunds when their own AI repeatedly fails like this. .. second one after this was green screen around white box. and green glow area around the avatar, very odd. For reference, this is what your AI said: I understand - you experienced a severe visual distortion with the avatar. While I don't have a direct tool to report bugs, you can contact Descript support to report this issue: To report this to support: Click the Help (?) icon in the top-right corner of Descript Select Contact support You'll be connected with the support team via live chat (Monday-Friday, 5 a.m. - 5 p.m. PT) or email What to include when reporting: A link to this project (they'll need it to investigate) The screenshot you showed me of the distorted avatar Description: "Avatar displayed with severe visual distortion - yellow artifacts on head, transparency issues, body cut off" The support team can investigate what caused this rendering error. For more information: https://help.descript.com/hc/en-us/articles/10337720480653-Get-Help-Contact-Descript In the meantime, your new composition with the fresh avatar setup should work correctly. Would you like me to proceed with generating the avatar video for this new composition?
2
·
AI
Load More