View Issue Details

IDProjectCategoryView StatusLast Update
0001610OpenMPTPlugins / VSTpublic2022-06-30 21:02
ReporterExhale Assigned To 
PrioritynormalSeverityminorReproducibilitysometimes
Status newResolutionopen 
Platformx86OSWindowsOS Version8
Product VersionOpenMPT 1.30.05.00 / libopenmpt 0.6.4 (current stable) 
Summary0001610: Issue with Trance Gate 2 plugin
Description

I have been working on a goa tune for the last couple of days and I am using a vst called 't force trance gate 2' just as one plugin for an example, I have used other plugins that have done similar things in the past, but this one is really bugging me right now because the plugin does exactly what I need it is just modplug is definately sending weird signals to it.
I will put a link here where you can download a slightly trimmed version of the mptm, and if you load it with t force trance gate 2 (fx9) on, and start to play you will see that 1 big problem is the resonance parameter goes to 0 as soon as you start any pattern (ERROR 1), which is utterly baffling me, so what I did was a added a pc code after the first downbeat on the first pattern as a sort of plaster to get my setting where it is supposed to be... none of the zxx macros are set to control that parameter and it does it at the beginning of every pattern bafflingly, now this isnt actually my worst problem with this particular track...
Sometimes if you, idk, breath on your keyboard wrong or something, it will open the mptm file with the zxx macro on sf1 controlling the resonance instead of the cutoff (ERROR 2)!! which sounds terrible and means every time I get that I have to close and reopen the project a few times hoping it will work...
Is this a known problem with trance gate 2? if so, what is going on? Does the plugin have some kind of random yet predictable parameter swapping code in it or something?

Steps To Reproduce

play any pattern with trancegate open, you will see the resonance go to 0, if you are on pattern 0 my code will kick in and bring it back to where it is supposed to be, but you will still see it.
Open the track a few time and guaranteed the resonance will start to be controlled by sf1 in channel 2 instead of the cutoff at least once.

TagsNo tags attached.
Has the bug occurred in previous versions?n/a
Tested code revision (in case you know it)

Activities

Exhale

Exhale

2022-06-30 00:06

reporter  

goa1EG.zip (955,173 bytes)
Saga Musix

Saga Musix

2022-06-30 16:45

administrator   ~0005231

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.

Exhale

Exhale

2022-06-30 18:20

reporter   ~0005232

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.

Saga Musix

Saga Musix

2022-06-30 18:32

administrator   ~0005233

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").
OpenMPT could be modified to not send the All Controllers Off message to this particular plugin, but in general I wouldn't want to omit it for all other plugins.

Exhale

Exhale

2022-06-30 18:54

reporter   ~0005234

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 resonance.jpg (170,249 bytes)   
tftg2 error1.jpg (166,545 bytes)   
tftg2 error1.jpg (166,545 bytes)   
tftg2 error2.jpg (163,115 bytes)   
tftg2 error2.jpg (163,115 bytes)   
Exhale

Exhale

2022-06-30 18:56

reporter   ~0005235

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)

goa1EG2.zip (580,961 bytes)
Exhale

Exhale

2022-06-30 19:00

reporter   ~0005236

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

Exhale

Exhale

2022-06-30 19:01

reporter   ~0005237

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

Exhale

Exhale

2022-06-30 20:18

reporter   ~0005238

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...

guide to pattern 0.jpg (725,656 bytes)
Exhale

Exhale

2022-06-30 20:24

reporter   ~0005239

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.

Exhale

Exhale

2022-06-30 21:00

reporter   ~0005240

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
anyways, yeah thanks that sounds like it could be just what this plugin needs as a fix :)
I appreciate your time to look into it saga

Exhale

Exhale

2022-06-30 21:02

reporter   ~0005241

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.

Issue History

Date Modified Username Field Change
2022-06-30 00:06 Exhale New Issue
2022-06-30 00:06 Exhale File Added: goa1EG.zip
2022-06-30 16:45 Saga Musix Note Added: 0005231
2022-06-30 16:45 Saga Musix Summary there is soomething very wrong with how some plugins are handled in modplug - in this case trance gate 2 => Issue with Trance Gate 2 plugin
2022-06-30 18:20 Exhale Note Added: 0005232
2022-06-30 18:32 Saga Musix Note Added: 0005233
2022-06-30 18:54 Exhale Note Added: 0005234
2022-06-30 18:54 Exhale File Added: tftg2 resonance.jpg
2022-06-30 18:54 Exhale File Added: tftg2 error1.jpg
2022-06-30 18:54 Exhale File Added: tftg2 error2.jpg
2022-06-30 18:56 Exhale Note Added: 0005235
2022-06-30 18:56 Exhale File Added: goa1EG2.zip
2022-06-30 18:58 Exhale Description Updated
2022-06-30 19:00 Exhale Note Added: 0005236
2022-06-30 19:01 Exhale Note Added: 0005237
2022-06-30 20:18 Exhale Note Added: 0005238
2022-06-30 20:18 Exhale File Added: guide to pattern 0.jpg
2022-06-30 20:24 Exhale Note Added: 0005239
2022-06-30 21:00 Exhale Note Added: 0005240
2022-06-30 21:02 Exhale Note Added: 0005241