REAPERDenoiser VS inkscape

My favourite free denoiser for room noise https://github.com/nbickford/REAPERDenoiser . Combined with a gate for voiceover can be v effective.

https://github.com/Nbickford/REAPERDenoiser says hold my pint. As good as RX in many cases.

The best denoiser results require you to sample just the hiss by itself. They then try to remove that noise from the recording. The RX one has a setting for this. This free one from Neil Bickford also does a fantastic job , far better than ReaFIR subtract https://github.com/nbickford/REAPERDenoiser

Try this instead. Far better denoiser than ReaFIR. Simple to use too. https://github.com/nbickford/REAPERDenoiser

I don't think you can get a really good result, the sounds overlap in the frequency spectrum too much. This is the best free denoiser I know. Far better than ReaFIR and can sometimes be better than RX. Worth a try. V easy to use. https://github.com/Nbickford/REAPERDenoiser

The best free denoiser I've come across is a JSFX one coded by computer scientist Neil Bickford. It's easy to use and often gives better results than commercial ones, like RX9. Far better than ReaFIR for this. https://github.com/nbickford/REAPERDenoiser

The contents are rendered through gtk/cairo which not only goes through https://www.xquartz.org/ but also doesn't use GPU rendering (it was experimental 3 years ago, maybe better now). The main issue seems to be that neither Inkscape nor gtk people have much low level Darwin experts or time available to invest in debugging the whole rendering stack. See for example https://gitlab.com/inkscape/inkscape/-/issues/1614 and all the other referenced issues for all the gory details.

There's a year old issue https://gitlab.com/inkscape/inkscape/-/issues/3227 with no visible progress and a medium priority label. I hope it gets more dev focus soon.

Here's a bug report related to this. Also here's a video of this bug with the oldest version of Inkscape that I still have lying around (0.94.2 i.e. 2019, but it's likely the bug is even older than that), and a similar thread on here from more than two years ago.

Yes. Only in specific circumstances, though. It's not really that big of a deal.

Arc handles can't be snapped and it's a known issue. It seems like you're using guides, though, so you can just double click the guide to get its angle and manually enter it as the 'Start' or 'End' angle in the toolbar.

This is a known issue. It seems like it's related to a new setting that was added in recent versions. In the preferences under 'Behavior → Selecting' disable 'Paste above selection instead of layer-top' to get the old, non-buggy behavior back.

See the ASCII table at https://www.rapidtables.com/code/text/ascii-table.html. Have seen it happen in Inkscape on Windows, too: https://gitlab.com/inkscape/inkscape/-/issues/4071

Inkscape bug: https://gitlab.com/inkscape/inkscape/-/issues/4043