Posted
How is this meant to work?
I have loaded a Violin sound which has the physical playing range G2-C6, and set the sound category to Violin.
Then I scan the playing range automatically and get the following ranges:
Lower: C2-D4
Middle: A2-C6
Upper: E3-G7
I would have expected the Lower range to start at G2, and the Upper to end at C6 (as per the actual minimum and maximum pitches). As this is not the case, I don't understand the purpose of this utility.
Tue, 2014-01-14 - 10:23 Permalink
Automated scanning uses the audio signals produced by the plugin to determine whether a note is mute or not. For sounds with a very slow attack or low volume, this may fail. If the engine could wait 10 sec per note, it might work better, but that would make a scan take an unbearable long time. It's already quite slow now.
It does also fail if the plugin does not stop all sound output on receiving an ALL SOUND OFF message (release phase smears into next note).
That said, the scan works for most sounds, but not all.
Wed, 2014-01-15 - 00:02 Permalink
This must be the latter problem then because it's not missing notes, but is including mute ones. It must be an issue with the Play engine as I'm finding most EWQL instruments fail the auto scan.
Are you saying the highest physical note (C6) "smears" all the way up to G7, a pretty big difference of an octave-and-a-half?
Sat, 2014-01-18 - 16:11 Permalink
Yes, the long release of C6 may still be sounding when G7 is tested.
Synfire does not test note by note. That would take a very long time. It uses a fast way to probe in larger intervals first and then narrow down to smaller intervals at the edges of the range.
I see it has its weaknesses with some sounds. Will have a look when I get around to the engine next time.
Mon, 2014-01-20 - 12:10 Permalink
Oh I get it now. I had wrongly assumed that it was important to get it right for the template, forgetting the ranges could be changed for each arrangement.
This has given me a new feature idea:
Instead of (or as well as) the 'scan automatically' function, there could be an option to enter the lowest and highest possible notes only. Synfire could then make an intelligent guess of the three playing ranges, together with a sensible sweet spot for each?
Thu, 2014-02-20 - 22:33 Permalink
I've noticed that when scanning playing ranges, Synfire is trying to find the lowest and highest notes. Sometimes I can see that it hits a keyswitch which changes the normal range. For example, it may hit a 'Trills' or 'Effects' switch which can sometimes narrow the range to around one single octave.
It is not surprising that in these circumstances, the scan will not work correctly.
I still think my idea of being able to physically enter the actual lowest and highest notes manually is a good one. After all, it would then only do what Synfire is trying to do automatically.
Even if (for some reason) it is a bad idea, I would appreciate a response. Thank you.
Fri, 2014-02-21 - 11:59 Permalink
Trapping on a key switch can mess with the scan, absolutely. There is no way to prevent this.
I still think my idea of being able to physically enter the actual lowest and highest notes manually is a good one. After all, it would then only do what Synfire is trying to do automatically.
Just pull the end of the low range to the lowest and the end of the upper range to the highest note.
I still find your idea great. I'll see if I can add a "tap in" button for the ranges, as is used for the metronome and remote control setup.