@4Tey: yep, all sorts of batch operations can be done with the data available in the sqlite database
(that’s also a reason we didn’t want to obscure this - I enjoy a good creative workaround myself).
But, all ffx really wanted was the ability to delete/trash results from within Sononym itself - a very reasonable request
The amount of depth/reverb.
Indeed. This was also suggested by one of my friends who is working extensively with reverb in his music.
He called referred to it as panorama, which I think is a good fit - sufficiently abstract so that it’s open to interpretation.
But technically, this is a very hard thing to realize. Sure, you can get an idea about the discrepancy between left and right channels, assuming that the file has more than one channel of audio.
Also, you could get reasonably good results if you had optimal conditions for detecting reverb (e.g. a one-shot with trailing reverb) - but this is often not the case.
So it could become quite a hit-and-miss affair, worst case example being a densely populated monophonic sound drenched in reverb and effects -
any human would be able to tell that it was very reverbey, but it’s tricky to translate this into something a computer would understand.
Of course, if you have come across any research or software that does something like this, I’d be interested to hear about it
(for instance, Accusonus have made a reverb-removal plugin called ERA-R)
Where do I find the log about this crash?
In the case of a crash, the log might contain some of the steps leading up to the crash, but the crash itself won’t appear.
But Sononym can send anonymous crash reports (minidump files) - by default, this option already enabled in the help menu.
If Renoise is opened in the background, the default audio setup crackles
[…] If I then choose my audio device manually
OK, just to make sure I understood - you’re saying that
- The order in which you open the programs is important
- opening e.g. Renoise before Sononym works, but not the other way around?
- so, it’s not “just” a driver that doesn’t like to be multi-client ?
- The problem can only be solved by manually selecting the audio device
- does that mean you have to do this every single time?
- what choice of audio device is actually working without crackling?
Note that we are going to replace the audio framework used by Sononym with our own (currently using PortAudio).
Of course that won’t magically fix any problems with drivers that aren’t multi-client capable,
but it certainly will make sure that we better understand and are able to fix any problems that might arise.