Cutoff previous midi note with next

Spock · February 02, 2011, 07:38:07

Hi,

I'm using some VSTi's in Modplug (no midi keyboard set up, so just entering the note data directly) and if I trigger a note on a track, when I play another note on the same track the previous note still stays on. Is there any way to set up Modplug to auto key off the previous note when a new midi note is called on that track without having to use '='.

Thanks for your help.

Saga Musix · February 02, 2011, 08:07:37

That should not happen. Do you use Portamento (3xx or Gxx) on that note?

psishock · February 02, 2011, 08:53:50

QuoteI'm using some VSTi's

VSTi specialist here. That is most possibly not OMPT, but VSTi related issue (unless its a tricky bug, but i didnt experienced it yet). Some of them can feature multiple "virtual channels" or polyphony channels in them (up to 64 or even more in other cases) and if the internal envelope, sustains, loops are not setup correctly, the sounds will just continue to gather up in the background with every additional new note entered.

Solution is to setup your VSTi correctly. Either by checking the loops and the envelopes, or by switching the polyphony to "mono", means only 1 sound will play at the time, no matter what. The second is nice for pitch glided lead sounds for instance.

Spock · February 02, 2011, 09:46:04

Quote from: psishock on February 02, 2011, 08:53:50
VSTi specialist here.

Solution is to setup your VSTi correctly. Either by checking the loops and the envelopes, or by switching the polyphony to "mono", means only 1 sound will play at the time, no matter what. The second is nice for pitch glided lead sounds for instance.

As far as I am aware the VSTi's are perfectly set up, it happens with any patch I use within Omnisphere and also Stylus RMX (set to groove mode) and trigger a loop with a specific note. Every time the sequence loops around, another note is played whilst the other continues in the background. The reason I believed it to be an issue within Modplug is because I downloaded a demo of Renoise and tested this issue there and the VSTi's work perfectly and as intended with no adjustment to the VSTi itself. However, after using Modplug for years now, I would prefer to stick with a program that I am familiar with.

Setting to monophonic isn't an option as I want to use these sounds as polyphonic instruments.

Thanks.

Spock · February 02, 2011, 09:48:01

Quote from: Jojo on February 02, 2011, 08:07:37
That should not happen. Do you use Portamento (3xx or Gxx) on that note?

I agree, and it doesn't happen in a different tracker therefore I thought there was a required setting I'd missed within Modplug. I'm not using any portamento commands.

Spock · February 02, 2011, 10:10:20

I think I have found the issue.

I normally use samples and write in XM format and even though I can add VSTi's to an XM I noticed in the instruments tab that under 'New Note Action / Action = Note Cut' this was greyed out. I started a new song in IT format and it works fine now.

What would be the best song format for me to use to get the best VSTi compatibility? What do you use when using VSTi's?

Thanks.

Rakib · February 02, 2011, 12:15:05

Use the modplugs own fomat. mtpm or what its called (dont have modplug here). It has lots of extra options regarding vst.

psishock · February 02, 2011, 13:46:43

QuoteI think I have found the issue. I use XM format.

Yep, that's a problem. XM doesnt support VST plugins at all, no matter that you can "theoretically" load up external plugins in OMPT to it. It is a sample-only based legacy module format.

As Rakib suggested, use OMPT's own native ".mptm" format to get the best compatibility result.
Or if you prefer use ".it" (some lesser control over external plugins). Those two will work just fine.

LPChip · February 02, 2011, 14:36:02

Ah, I had this problem too when converting from one format to the other. .itp to .it in my case.

I mentioned this to Jojo and he guided me through getting my song to work.

In the General Tab, Song properties, there are some flags (check boxes) I had to change these. You should compare them with a new .IT song and set them the same to get it right again. That should allow you to change the new-note action on your adjusted .xm file.

Saga Musix · February 02, 2011, 19:38:23

Quote from: LPChip on February 02, 2011, 14:36:02
Ah, I had this problem too when converting from one format to the other. .itp to .it in my case.

No, It's not a problem with any flags, it's a general problem with VSTis not working in the XM format. Since this has been the case since like forever, there are two possible things to do:
- Remove VSTi support from XM alltogether (that's what I prefer)
- Fix it

psishock · February 02, 2011, 19:56:21

QuoteNo, It's not a problem with any flags, it's a general problem with VSTis not working in the XM format. Since this has been the case since like forever, there are two possible things to do:
- Remove VSTi support from XM alltogether (that's what I prefer)
- Fix it

Please solution #1.

You are a compatibility driven person. I would go even fas as: VSTi "support" (together with all the non legacy extras) should be removed from all the legacy module formats. Including our new "hacked" .IT format. These hacked modules are only playable with ompt only anyway, if you try to load a vsti extended song to a normal, .IT compatible tracker or player, it will fail to play, or in the worst cases even fail to load. Basically we're speaking about format features and standards that every related programs are following*.

Our special extended command list, channels, rows and all the plugins, other fixes, "hacks", etc. should strictly stay in the OMPT's native .MPTM format. Every other tracker is working* like this with the non legacy stuff, for an obvious reason.

*(or at least, we would expect that

)

Spock · February 02, 2011, 20:28:47

Thanks for all of the replies and advice, I think I will use the MPTM format. I'm guessing that most of the general commands are still the same?

Thanks again.

Saga Musix · February 02, 2011, 20:32:07

The most obvious difference are different effect letters (ScreamTracker notation instead of ProTracker notation), and also subtle and not-so-subtle differences in effect handling, mostly because of how fucked up some XM effects are (e.g. arpeggio).

psishock · February 02, 2011, 20:39:09

QuoteThe most obvious difference are different effect letters (ScreamTracker notation instead of ProTracker notation), and also subtle and not-so-subtle differences in effect handling, mostly because of how fucked up some XM effects are (e.g. arpeggio).

i think he should be safe, most of the standard tracker effect don't really work with VST(i)s. I would even advise to avoid them altogether and use midi automation instead. Because VSTs were invented for midi sequencers in the first place, its the most natural way to control them.

Tracker effects are basically for the tracker's embed sampler engine.

Saga Musix · February 02, 2011, 21:09:07

Well, it would be much nicer to have some commands like panning working directly with plugins, and I don't see a point in not using them (when they actually work). It's simply more convenient to use pxx instead of Zxx or PC notes. And it's in no way inferiour to Zxx, simply because it's noted the same way in the pattern.