Ever since I sold the first MacBook, it felt like I was fighting Windows audio drivers constantly. Between latency issues, BSODs due to Focusrite's unstable audio interface drivers, more BSODs trying to get around [multiple audio interface setups in software](https://help.ableton.com/hc/en-us/articles/209071609-Using-Aggregate-Devices-and-multiple-audio-interfaces), I started steering away from in-the-box production and started looking into hardware.
results in
Ever since I sold the first MacBook, it felt like I was fighting Windows audio drivers
constantly. Between latency issues, BSODs due to Focusrite's unstable audio interface
drivers, more BSODs trying to get around [multiple audio interface setups in software](
https://help.ableton.com/hc/en-us/articles/209071609-Using-Aggregate-Devices-and-multiple-audio-interfaces)
, I started steering away from in-the-box production and started looking into hardware.
which gets rendered as
There is an extra space right before the comma. If it were to reformat to
Ever since I sold the first MacBook, it felt like I was fighting Windows audio drivers
constantly. Between latency issues, BSODs due to Focusrite's unstable audio interface
drivers, more BSODs trying to get around [multiple audio interface setups in software](
https://help.ableton.com/hc/en-us/articles/209071609-Using-Aggregate-Devices-and-multiple-audio-interfaces),
I started steering away from in-the-box production and started looking into hardware.
Yup, this is definitely unintentional. I'll find some time this week to take a look at this. I'm pretty sure I know where the fix for this needs to be. Thank you for the report!
Running
markflow
againstresults in
which gets rendered as
There is an extra space right before the comma. If it were to reformat to
it renders as intended, without the extra space.