Solo Strings
SWAM-S v3 - Questions on Specific Playing and Management Techniques

Hi AudioModelling

Thank you for the wonderful SWAM instruments! I especially appreciate the enhanced high-frequency detail, the increased range of Bow Position which now gives a truly 'edgy' sul ponticello, the enhanced Harmonics mode, and the new Pizzicato tone control.

As I am adapting my production setup to work with Strings v3, I have encountered the following questions, which I think will need your in-house expertise to be answered. Thank you in advance.

1. How to get pizzicato on multiple open strings?

I set Pizz.Poly mode to poly, and Alt.Fingering to "Nut and Open”. But the fingering algorithm always insists on playing at least one of the notes stopped. In fact, it seems very difficult to get the instrument to play an open string pizzicato under any conditions. Or am I missing something important?

2. For Detache playing, where is the “Noteoff Sustain Mode” parameter, which used to be so important in getting effective results with the sustain pedal down?

The "Noteoff Sust.Mode” parameter used to allow access to the options for “Hold (normal)” , “End with Accent” and “End with Fadeout”.
The plugin now seems to always be in “Hold normal” mode. But previously I found that “End with Fadeout” mode was needed for more realistic variety of Detache bowings. Is there a way to do this in V3?

3. Is there a way to turn off the automatic timeout when editing Curves or MIDI Assignments?

The timeout seems less intrusive than it was in the SWAM-B version, but I would like to turn it off completely, if possible.

4. How can I replicate the Volume cc response as it was in v2?

The Volume CC response in V3 is quite different than it was in V2. I’ve tried to simulate the old behaviour with the curve shaping functions of v3, but there seems to be no way to do it. In v2, the Volume dropped linearly from 0 db to -42 dB, then quickly to minus infinity. The new version allows more subtle volume control at very low levels, which is nice, but the difference in cc response means that my mixes in old projects are now very unbalanced.

5. Is the new "Early Reflection” parameter the same as the old Reverb? IF I turn it down to 0, does that effectively turn it off (and lessen the corresponding CPU load?)

Sorry for all the questions! I'm especially interested in resolving the first three.

thanks,
Bruno Degazio

Hi AudioModelling Thank you for the wonderful SWAM instruments! I especially appreciate the enhanced high-frequency detail, the increased range of Bow Position which now gives a truly 'edgy' sul ponticello, the enhanced Harmonics mode, and the new Pizzicato tone control. As I am adapting my production setup to work with Strings v3, I have encountered the following questions, which I think will need your in-house expertise to be answered. Thank you in advance. **1. How to get pizzicato on multiple open strings? ** I set _Pizz.Poly_ mode to poly, and _Alt.Fingering_ to "Nut and Open”. But the fingering algorithm always insists on playing at least one of the notes stopped. In fact, it seems very difficult to get the instrument to play an open string pizzicato under any conditions. Or am I missing something important? **2. For Detache playing, where is the “_Noteoff Sustain Mode_” parameter, which used to be so important in getting effective results with the sustain pedal down? ** The "_Noteoff Sust.Mode_” parameter used to allow access to the options for “_Hold (normal)” , “End with Accent_” and “_End with Fadeout_”. The plugin now seems to always be in “_Hold normal_” mode. But previously I found that “_End with Fadeout_” mode was needed for more realistic variety of Detache bowings. Is there a way to do this in V3? **3. Is there a way to turn off the automatic timeout when editing Curves or MIDI Assignments? ** The timeout seems less intrusive than it was in the SWAM-B version, but I would like to turn it off completely, if possible. **4. How can I replicate the Volume cc response as it was in v2? ** The Volume CC response in V3 is quite different than it was in V2. I’ve tried to simulate the old behaviour with the curve shaping functions of v3, but there seems to be no way to do it. In v2, the Volume dropped linearly from 0 db to -42 dB, then quickly to minus infinity. The new version allows more subtle volume control at very low levels, which is nice, but the difference in cc response means that my mixes in old projects are now very unbalanced. **5. Is the new "Early Reflection” parameter the same as the old Reverb?** IF I turn it down to 0, does that effectively turn it off (and lessen the corresponding CPU load?) Sorry for all the questions! I'm especially interested in resolving the first three. thanks, Bruno Degazio
edited 3 days ago at 3:19 pm

4)
There are Midi filter plugins that provide sophisticated CC traslation curves.
In Reaper there is "Midi CC Mapper X". Same is a JSFX (propriety Reaper realtime script) but there is "ReaPlugs" (free of charge by the friendly Reaper creators at Cockos), which provides a Meta-plugin (VST2) that allows for loading JSFXes. (I did not check if this works).
-Michael

4) There are Midi filter plugins that provide sophisticated CC traslation curves. In Reaper there is "Midi CC Mapper X". Same is a JSFX (propriety Reaper realtime script) but there is "ReaPlugs" (free of charge by the friendly Reaper creators at Cockos), which provides a Meta-plugin (VST2) that allows for loading JSFXes. (I did not check if this works). -Michael
edited 2 days ago at 6:10 am
29
1
2
live preview
enter atleast 1 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft