Shreddage 2 Development Thread

[EvilDragon]

Double-tracking can be done within a single instrument, too. Check out Orange Tree guitars

[metalheart]

hi Zircon,just for curiosity,how many Mb will fit in the library approxymatively?

[zircon]

Double-tracking can be done within a single instrument, too. Check out Orange Tree guitars

Hmm, I've never really looked into doing multiple outs from within one patch before... where is that in the KSP spec? Can you really send, say, one note to stereo out 1&2 and another note to 3&4?

metalheart: Still working on it, but currently the library is 4.45gb uncompressed. I don't have an exact file count on hand but most likely upward of 5000 samples, so well-over double the size of Shreddage+X combined.

[EvilDragon]

You can duplicate the groups, then set group output differently between the original set of groups, and the duplicated set of groups. However that's slightly inefficient (even though it doesn't increase the RAM load).

However the way OTS libs do it is just utilizing the regular stereo output I think, not using anything more than that. My assumption is that on each play_note() event there are actually two play_note() events, except after them there goes change_pan() and they get panned adjacently. Perhaps adding slight pitch offset, too, with change_tune(). Also likely possible to use different RR for the second play_note() by using differently set up disallow/allow_group().

[zircon]

Well we've got several hundred groups already, so I probably wouldn't use the first method... it would make things more bulky and inefficient. I thought about the second method you brought up (as it came to my mind as well), however I think that is problematic with some daws. For example, in FL Studio, the default routing is to send one stereo output from Kontakt to one stereo mixer track. FL doesn't have mono mixer tracks. Thus, if you wanted each 'track' of the guitar to go to its own mixer track, you would have to change Kontakt's output routing from the FL wrapper to send just one channel from the first stereo output pair (L) to one mixer track and the other (R) to the next mixer track. That adds another step of possible confusion for users.

I think the best way would just to have a second patch instance where you click 'Double Track'. Then my only problem becomes synchronizing the RRs properly, which is probably not doable without some kind of multiscript, OR using preset RR patterns (which I was trying to avoid).

Edit: Just did a sample count. 7200 so far

[EvilDragon]

Yep, you cannot synchronize between instruments unless you use a multiscript, I think.

I still think that doing it all in one patch is easier on the end user. It's not our fault that FL has the routing that it has. Reaper has is a lot easier/more flexible.

[J-Rokujuushi]

Regarding the stereo mixer tracks, I've actually used that a few times since Amplitube supports stereo input and can route the left channel through one signal chain and the right channel through another. Is that an Amplitube-only feature or do other amp sims have that as well?

[zircon]

Yep, you cannot synchronize between instruments unless you use a multiscript, I think.

I still think that doing it all in one patch is easier on the end user. It's not our fault that FL has the routing that it has. Reaper has is a lot easier/more flexible.

You have clearly not had to walk many a user through both FL Studio and REAPER routing Whatever we can do to reduce the burden of knowledge on the end-user for routing is the ideal case, IMO. But perhaps we'll give the all-in-one patch a shot.

Regarding the stereo mixer tracks, I've actually used that a few times since Amplitube supports stereo input and can route the left channel through one signal chain and the right channel through another. Is that an Amplitube-only feature or do other amp sims have that as well?

Guitar Rig does as well, but I'm not sure ReValver does.

[EvilDragon]

I think ABG HeadCase can do that as well, I think. I'm not sure, though.

[EvilDragon]

Yep, you cannot synchronize between instruments unless you use a multiscript, I think.

I still think that doing it all in one patch is easier on the end user. It's not our fault that FL has the routing that it has. Reaper has is a lot easier/more flexible.

You have clearly not had to walk many a user through both FL Studio and REAPER routing Whatever we can do to reduce the burden of knowledge on the end-user for routing is the ideal case, IMO. But perhaps we'll give the all-in-one patch a shot.

It would actually make sense to provide both individual NKI versions and all-in-one NKI, if you find that plausible.

[Aloysius]

bx_rockrack

Stereo Sounds (aka DOUBLED guitars) For best results insert bx_rockrack on a subgroup (aux input) and route 2 DI guitar tracks into this bus, panned hard L/R (100%).

[metalheart]

Hi Zircon I have a question.
For the palm mutes sounds (half,full...) is it possible to have knobs that let the user select the decay time,the attack and the pick noise value for every type of it? a sort of adjustable level which determines the intensity of the mutes.

[metalheart]

hei Andrew any news??

[zircon]

Whoops, didn't see that post. We do have a control for mute decay times and mute release times, which will let you control the tightness of JUST the mutes. We have the same kinda thing for sustain releases (but not sustain decay, since that doesn't quite make sense).

[metalheart]

perfect!!