 |
There is way too much going on in this example module to understand the issue. Please remove every plugin, every instrument, and anything else that is not required to demonstrate the issue. It must be clearly audible or visible where the problem is, and how you think the correct behaviour would look or sound like. The resonance parameter - if I'm looking at the correct one - is jumping wildly around in any pattern I try to play. |
 |
that sounds like you opened it and got unlucky (more common than I would want), the wrong parameter is being controlled this is happening "it will open the mptm file with the zxx macro on sf1 controlling the resonance instead of the cutoff!!"... ok I will try make the file more precise, and I will upload some visual aids here. |
|
|
After understanding the plugin GUI a bit better I think I see what's going on - OpenMPT is sending an All Controllers Off CC message. The intent here is that e.g. if there are sustain pedal messages sent to the plugin and you stop the song while the "pedal" is down, restarting playback resumes with the "pedal" being up again. This plugin also resets various other settings such as resonance - whether it should do that or not is up to interpretation ("Any Non-registered Parameters or Registered Parameters may be reset to default values"). |
|
|
ok here we go hopefully this should make it clearer, I will also edit my original post to denote what I am referring to as error 1 and error 2 tftg2 resonance.jpg (170,249 bytes) tftg2 error1.jpg (166,545 bytes) tftg2 error2.jpg (163,115 bytes) |
|
|
the cutoff on the middle left is being controlled by sf1, sf2 is controlling the direct x eq which will not be included in the new example, which will be attached here (no other vsts except tforce trancegate 2) |
|
|
if you get error 2, which is what I suspect you encountered when you opened it, close it and open it, play it, if it is still whistling do it again, and test again, until you get error 1 |
|
|
yeah error 2 sounds horrible, like it is whistling at you, and it entirely NOT what the tune is supposed to sound like, I have no clue why sf1 is taking control of the resonance when it was specifically set to control the cutoff |
|
|
ok I have attached a guide to pattern 0 of the track to help you find everything... I hope this is all enough information, and isnt too much... |
|
|
at this stage I have pretty much 'finished' the tune, so yeah, there is no rush, since I have been able to work around the weird errors, but I think you guys might want to look into it which is why I put this error report here for everyone, and hopefully you guys might find a way to sort it out so that nobody else gets these strange behaviours in the future. It was really frustrating and I had to set the tune aside because I got pretty angry with it... I suspect that is it probably t-force's fault, they probably programmed the thing with non-standard triggers for things or something, so yeah over-all I am curious to find out what you guys figure out from it. |
|
|
oh hi, I only saw your reply right now, thank you, that is very enlightening... I guess I did all of that stuff for nothing XD |
|
|
you can close this report at any time you decide to, maybe you will want to make the changes you talked about, and I guess that information I put down could help other people who might want to look into it if it turns out to be a more complex problem than just that. |
|
|
As of r17746, OpenMPT no longer sends All Controllers Off to this plugin. |
- Anonymous
