General complaints
closed
M
Matt Maruskin
I unfortunately use Descript Classic for work, to edit interviews, and in my experience, this is a faulty product and I'm saddened to see all your "positive" reviews on "trust" websites are from REOs or CEOs who don't have to interface with this inhumane product every day. First of all, a question: I'm using a late-2017 Macbook Pro with 8 GB of RAM and I must ask why is the Descript Renderer constantly running my laptop into the 100+% of CPU usage, to the extent that my laptop becomes overloaded and shuts down completely, presumably because it's overheating? I cannot fathom how that is even possible to render so frequently on what is typically 3 or 4 20 mb files; it really does not need to be devouring so much cpu power.
And now two suggestions:
- Please make the fader arrows a decently large enough size to where I'm not clicking on the wrong thing constantly. They're like pinpricks on the screen and it makes editing so incredibly slow.
- When editing a more-or-less 30-minute interview, the program reliably freezes 2 or 3 times, to where I am unable to select any of the mouse controls and the bar where the audio track becomes frozen, and I have to shut it down completely and reboot. Please fix this error, I'm not sure if it has to do with CPU consumption or not.
S
Support Team
closed
We're sorry that you've run into so many issues, and that we haven't responded until now. This feedback form is specifically for feature requests. For bug reports, urgent issues, generalized feedback or specific workflow complaints, the best option is to file a support ticket.
That way we can make sure to forward bug reports to our engineers, share workarounds, and talk through any options to improve your experience. They'll also help parse design feedback that can be sent to our product team.
You can file a support ticket here:
https://help.descript.com/hc/en-us/articles/10337720480653-Contact-Descript