Hey guys, I'm new to the plugin here. I've tried to find help but can't seem to address my problem.
So I'm trying to use the Metal-GTX and Standard Bass from here: https://unreal-instruments.wixsite.com/ ... nstruments
If I open the Regions menu and click on the sample region, it plays. But clicking on the piano roll or my MIDI keyboard does nothing.
I've tested SFZ files from elsewhere with no trouble - both the piano roll and keyboard work fine.
I'm using Waveform 10 Pro. Aside from this issue everything seems to be working straight out of the box with the plugin. And I'd rather not use Sforzando anymore!
Metal GTX Guitar sample (SFZ) - doesn't work?
-
- KVRist
- 113 posts since 4 Mar, 2016
-
- KVRAF
- 2550 posts since 27 May, 2005 from Stockholm
The Metal-GTX and friends SFZ:s are from what I can tell broken, in that they seem to utilize an unspecified "feature" of Sforzando. (They also rely on the poorly documented and specified "version 2" extensions to the format).
Most groups have something like this (taken from the first sub-patch, "Noise_Picking_Noise.sfz"):
sw_lokey=e-1
sw_hikey=d7
sw_last=f0
This says: Play the region when the last key played in the range e-1 - d7 was f0. However, the region itself of course is also in this range. Wtf?
Sforzando seem to treat region range as excluded when interpreting this. TX does not, because I can't find any clear specification on how this is supposed to work. Imho, the SFZ says clearly: never play me. I.e. the author should have set the control range properly. And trying to handle this on a parser or switch level would basically be doing stuff that the user did not write. If you say the control range is e-1 - d7, it should be e-1 to d7, not some value the program thinks is better.
/C
Most groups have something like this (taken from the first sub-patch, "Noise_Picking_Noise.sfz"):
sw_lokey=e-1
sw_hikey=d7
sw_last=f0
This says: Play the region when the last key played in the range e-1 - d7 was f0. However, the region itself of course is also in this range. Wtf?
Sforzando seem to treat region range as excluded when interpreting this. TX does not, because I can't find any clear specification on how this is supposed to work. Imho, the SFZ says clearly: never play me. I.e. the author should have set the control range properly. And trying to handle this on a parser or switch level would basically be doing stuff that the user did not write. If you say the control range is e-1 - d7, it should be e-1 to d7, not some value the program thinks is better.
/C
TX16Wx Software Sampler:
http://www.tx16wx.com/
http://www.tx16wx.com/
-
- KVRist
- Topic Starter
- 113 posts since 4 Mar, 2016
Thanks for your reply! I figured there must be something like that going on. I'll have a dig into the format and see what I can learn - at the moment I'm only using one particular 'program' in the set so I'm sure I'll be able to tweak it and get it up and running
-
- KVRist
- Topic Starter
- 113 posts since 4 Mar, 2016
Ok so with no success tweaking a few things (apparently I don't understand what I'm doing even after having read the SFZ website), I loaded it into Sforzando again and it turns out there are control switches both below and above the playable range of notes. So I'm guessing that explains the sw_lokey and sw_hikey values. I'm guessing that it was written to work in Sforzando with no consideration to anything else. I used Google Translate to translate the Japanese readme file but it only outlines how to use it. Had another look at the download page and translated to get this line: "Confirmed operation with sforzando v1.916" so... I guess that's as far as it goes 
-
- KVRAF
- 2550 posts since 27 May, 2005 from Stockholm
Let me also expand why I am reluctant to just exclude the region-mapped keyboard area: For me it would be quite valid to set up a "chain" of (overlapping) regions where triggering samples in "layers" is dependent on were you last played, so for example you play C3 -> sample A, then D3 -> sample B, then hitting F3, depending on whether you played C3 or D3 last, a different layer is selected. Etc. So this is why I think both the SFZ in question as well as the interpretation of it is invalid.
TX16Wx Software Sampler:
http://www.tx16wx.com/
http://www.tx16wx.com/
-
- KVRist
- Topic Starter
- 113 posts since 4 Mar, 2016
It's all good! I'm not questioning you at all . I'm still getting used to MIDI programming and for this particular scenario I'm going to keep using Sforzando purely because it works as intended and the guitar is the best freebie I've found. I just find Sforzando itself a little unintuitive in some respects so I don't want to use it unless I have to.
As far as the SFZ format goes, I know very little and am not really in a position to comment - but I appreciate you taking the time to explain the issues with this particular instrument as it may help me in future. Plus if I start customising my own sound packs I'm sure it will be good to know what is expected of the format. Most of the information seems to be at least 6-10 years old at this point.
. I'm still getting used to MIDI programming and for this particular scenario I'm going to keep using Sforzando purely because it works as intended and the guitar is the best freebie I've found. I just find Sforzando itself a little unintuitive in some respects so I don't want to use it unless I have to.As far as the SFZ format goes, I know very little and am not really in a position to comment - but I appreciate you taking the time to explain the issues with this particular instrument as it may help me in future. Plus if I start customising my own sound packs I'm sure it will be good to know what is expected of the format. Most of the information seems to be at least 6-10 years old at this point.