Shreddage 2 v2e Update - Now available!

[SSN688]

Yes. Though keep in mind, this is only when a fret position has not yet been established (i.e. no active notes). If a fret position HAS been established, then the script will try to find nearby frets to use instead.

Does this system of an established fret only apply to chords?

Or the same can be applied to consecutive notes within a certain time threshold?

[zircon]

Once a fret position has been established it applies as long as a note is held on any string. There IS a time threshold (about 350 ms) before the position resets, so if you are playing a very fast lead line where the notes aren't actually legato, the fret position will still stay mostly accurate.

[SSN688]

There IS a time threshold (about 350 ms) before the position resets

Is it possible to add that parameter to the interface in the next beta version?


Also, one quick observation.
Not sure if this is intended or not, but I noticed that the hammer-on/pull-off legato range parameter seems to override chord detection, such that even if I play a chord with notes within the chord time threshold, the engine would count it as legato and play only the last note if the notes I played were within the range of the hammer-on/pull-off range.

[zircon]

Yes, I will add a parameter for that - basically the 'position reset time'.

In terms of hammer-on vs. pull-off... it's a tricky situation. Often times I play very fast hammer-on/pull-off parts. I would not want those to be played as chords instead. You can always adjust the hammer/pull range though. Is there a setting or solution you would want to see to help with this?

[zircon]

The default setup still has the problem with lowest and highest velocities playing staccato and choke sounds instead of sustains or powerchords.

I have been looking into this and I'm not sure what the problem is. The default setup should now have Tremolos enabled. If you hit v=1 you get tremolo. v=127 gives you pinch squeal. The full chokes will only appear if you play a velocity that is not actively mapped, generally speaking.

Is there a specific use case that is problematic?

BTW I've identified the bad sample with the 5 string high G, that will be fixed shortly. I also have a working implementation of LFO-based "smooth" vibrato however I can't include this in the beta because of how NI's encoding works.

[SSN688]

In terms of hammer-on vs. pull-off... it's a tricky situation. Often times I play very fast hammer-on/pull-off parts. I would not want those to be played as chords instead. You can always adjust the hammer/pull range though. Is there a setting or solution you would want to see to help with this?

Hm.....I guess it's personal preference then.
Since I usually play chords neatly, I usually set the chord time threshold pretty low to avoid turning legato lines into chords.

Under the current system, even if I set the hammer-on/pull-off range to be fairly small, a lot of the chords I play still wouldn't come out properly since many of them contain notes of very small intervals...

Is it possible to implement a switch that determines whether hammer-on/pull-off legato overrides chord detection or not ?

[Truemas]

In another thread i have been told that with version 1.1. it will be possible to save/load presets everywhere on the harddrive.
Now, everytime i load my project, the kontakt 5 player is emty and i have to reload the multi and re-link the channels to my DAW. I tried to save the multi settings in kontakt but it says "could not save patch" when i try to "save multi as..."
What could be the problem here?

[zircon]

Hm, that sounds like it could be an issue with your DAW's plugin wrapper? Does it happen with any other libraries? Could you try it in another DAW as well (like REAPER, www.reaper.fm, which is free to download)?

[Truemas]

I will check this tomorrow and post the results afterwards.

[Truemas]

Now, i just tried everything with reaper and both options are working fine. I can save the shreddage 2 patch presets AND the Multi.
I closed and re-opened reaper and my user presets 1 for the guitar patch where loaded correctly. So it seems that Cubase 6 is the origin of this problem. Or is it shreddage 2's compatibility with cubase?

[metalheart]

Hi Zircon I've downloaded beta version of Shreddage 2 but I've noticed that like the old version,at some notes,portamento slide isn't triggered,I have full chokes instead...
have you any idea when we might see a revisted version of Shreddage?

and another suggestion!

since with my guitar I often use multiple legato slides I guess if is it possible to see some kind of poly legato function in future updates.

[zircon]

Can you provide any more info on the situations where portamento is not triggering? Preferably a MIDI sequence, screenshot, etc. Not sure why this would be happening.

As for the actual release version of this update, I am waiting on new recordings so I can integrate them (new releases, slides, scrapes)

Poly legato is a big challenge... I can't promise anything there. It tends to be very fiddly too even in libraries that do have it.

[warfighter67]

Poly legato can be done using many instances of shreddage set to their own MIDI channel. Kontakt 5 does not use up extra memory for multiple loaded instances of a same library, too.

[metalheart]

here's a screenshot.



http://i44.tinypic.com/j9957d.jpg

for tremolos there's no problem but all the slides are full chokes.

[metalheart]

Poly legato can be done using many instances of shreddage set to their own MIDI channel. Kontakt 5 does not use up extra memory for multiple loaded instances of a same library, too.

yes but loading 7 shreddage instances for poly legato only is a bit annoying...