Quote:
Originally Posted by
kirkwoodwest
➡️
Regardless if this is the way. i appreciate the post on this forum and any way to get it resolved. I too am running RME and thought it was their driver.
I mean how are you going to report a bug when you are 4 levels deep into hardware and software. its ****ing difficult. So i'm running OSX High Sierra, Fireface UC, Ableton, 30 different plugins. It glitches intermittently. What do i say? If you have any advice about how to write a bug that would be useful to apple I would love to hear it.
OK, here are some ideas on how to structure a bug report:
-- give it a descriptive title
This could be something like 'intermittent CPU spikes in audio applications'
-- list all hardware and software in use when the issue occurs
That includes hardware specs like Mac model, CPU speed, RAM specs - how much is installed, and whether it's original or 3rd party RAM, OS version, exact version numbers of all software in use, driver versions, etc
-- give an exact, step by step description on how to reproduce the issue
Word this like you're speaking to a child, meaning, include things that you wouldn't think are necessary, because they are so obvious. Every step matters. Also, be clear on whether the issue is intermittent.
-- state the 'expected behaviour'
..like, for example, 'continuous audio playback without interruption'
-- state the 'observed behaviour'
Again, be precise, like 'audio drop outs during monitoring input while recording, not audible on the recording itself when listening back to it'
-- list all the troubleshooting steps you have taken, and your observations
This includes all the basics, like testing without any external hardware connected, testing with just the audio interface and nothing else connected, testing with a fresh user account, testing with all plug-ins disabled, etc.
Example: 'the issue occurs when the RME interface is connected, it does not occur when only internal audio is used'
-- optional: if you think you've found relevant log entries, copy and paste them into the bug report
..again, be precise, state which logs they come from. Including logs is not necessary in most cases - if engineers reproduce the issue, they can look at their own logs, and sift through them in a much more systematic manner, and with a much better understanding of what is important, and what is normal behaviour.