Hi Melody,
Welcome to the forum.
Peter's and Uli's signatures are a good example of how to provide deterministic detail on hardware, OS, driver, Resolve version (build, studio/free), presence of peripherals etc. The
FAQs encourage a similar approach when reporting an issue, as it helps minimize clarification requests before users can provide a useful answer.
Having said that, I'm gonna guess you're using a Macbook Air, Macbook Pro or iMac from between 2014 and 2018, and don't have any additional hardware connected. Two things help -
a. adding a URL where users with similar setups can download a sample and check if they have the same issues.
b. running some tests to isolate where the issue is - this can help you work around issues in a specific area.
I've added some sample tests that you can consider below
Regards
Shrinivas
Tests for troubleshooting monitoring/playback:
a. starting with a standard test wav file (many audio professional websites host samples to help with calibration), internal speakers and Resolve preferences set to Auto (reflecting OS device), can you play it back without issue on Resolve?
b. if you toggle Resolve's setting from Auto to Manual and back, does it help?
c. Are there differences between previewing the audio file outside Resolve, in the media page and in the fairlight and edit timelines?
d. If these are fine, does swapping out the standard file with your specific media change things?
Tests for render specific issues:
a. Does it depend on the render codec? Or do all codecs/formats show this issue?
b. Does your render sample rate differ from the clip and timeline sample rates?
c. You can right click and bounce a clip on the timeline to disk. Does this show the same symptoms?
d. If you have effects in your audio chain - internal (compressor/noise/normalise/EQ etc) or external (like AU/VSTs) - does it make a difference if you're rendering with and without the effects.