11
Help and Questions / Re: Find / Replace Can't Find / Replace Anything
« Last post by LPChip on October 18, 2018, 16:20:25 »Well spotted Saga. I'm pretty sure that's what's going on here seeing the other channels.
Recent Posts
12
Compos / Re: OpenMPT FM+PCM example song compo (preliminary deadline 2018-10-12)
« Last post by Saga Musix on October 18, 2018, 07:01:50 »Yes, this is how the OPL chip is supposed to work.
13
Help and Questions / Re: Find / Replace Can't Find / Replace Anything
« Last post by Saga Musix on October 18, 2018, 06:55:26 »If those volume commands appear with a slightly faded-out color (i.e. an even darker green than the others), then they are "default" volume commands, i.e. they represent the default volume as configured in the sample properties (or global volume in instrument properties for plugin-based instruments). Those commands do not actually exist in the pattern, and OpenMPT only shows them for convenience. If you want to search for those, you need to search for an empty instead.
14
Help and Questions / Re: Find / Replace Can't Find / Replace Anything
« Last post by teimoso on October 18, 2018, 04:47:51 »My bad, the volume data should've been replaced anyway. Saga Musix is right; those are most likely default volume commands.
Quote
I was going to isolate it to only one channel and instrument, but since that seemed too hard, I thought I'd just select the ones I wanted to change.
In the "Find" tab, have you tried checking the "Only in channels" checkbox and limiting the range to the specific channel you want, as well as selecting the instrument you want to find in the Instrument drop-down? See the attached image for an example (assuming you want to find all instances of Instrument 1 on Channel 1).
15
Help and Questions / Find / Replace Can't Find / Replace Anything
« Last post by I-S3-O on October 18, 2018, 02:54:20 »I'm having a problem getting Find / Replace to do even the simplest of tasks. Maybe I'm doing it wrong, but I don't know.
All I want to do is replace v64 with v48; that's it. I was going to isolate it to only one channel and instrument, but since that seemed too hard, I thought I'd just select the ones I wanted to change. It just doesn't want to cooperate.
The attached pictures best show what I'm trying to do.
Can someone help? Please and thank you.
All I want to do is replace v64 with v48; that's it. I was going to isolate it to only one channel and instrument, but since that seemed too hard, I thought I'd just select the ones I wanted to change. It just doesn't want to cooperate.
The attached pictures best show what I'm trying to do.
Can someone help? Please and thank you.
16
Compos / Re: OpenMPT FM+PCM example song compo (preliminary deadline 2018-10-12)
« Last post by Exhale on October 17, 2018, 10:32:25 »I dont know if it is just my version of 1.28.00.31 but sometimes (and it seems in a predictable way) I get sporadic sound interpretation on these instruments, is it a glitch or is it how the instruments are supposed to behave?
You can replicate what I mean by starting a new mptm, making the first instrument an OPL, taking the modulator attack rate to 12, and playing a few chords... at first it will slide in, and if you keep playing chords it will hit at 100% sometimes then eventually all the time... the other part of the behavior, which I admit I used on one of the songs I sent means that when you track with an instrument like this and save it, the slide in will happen on the first play through in a once off way.
If that is the way it is going to behave at all times, thats fine, the song I sent will behave fine, but if not that is also fine because it would be nice to have the instrument behave more predictably. I did it earlier and hit chords over and over again and somehow it played the muffled like at the beginning of the climb and then sometimes at 100%... so yeah its a bit unpredictable in its current form.
(example attached to this reply)
I admit I wasnt able to get the sporadic showing up in the tracked example and it might just be the way this laptop keyboard works or something else about how I am playing it... I put some c+f chords after those chords I played in the example in what seems like the way I play them by hand and they work fine at 100% with note cut and note off
You can replicate what I mean by starting a new mptm, making the first instrument an OPL, taking the modulator attack rate to 12, and playing a few chords... at first it will slide in, and if you keep playing chords it will hit at 100% sometimes then eventually all the time... the other part of the behavior, which I admit I used on one of the songs I sent means that when you track with an instrument like this and save it, the slide in will happen on the first play through in a once off way.
If that is the way it is going to behave at all times, thats fine, the song I sent will behave fine, but if not that is also fine because it would be nice to have the instrument behave more predictably. I did it earlier and hit chords over and over again and somehow it played the muffled like at the beginning of the climb and then sometimes at 100%... so yeah its a bit unpredictable in its current form.
(example attached to this reply)
I admit I wasnt able to get the sporadic showing up in the tracked example and it might just be the way this laptop keyboard works or something else about how I am playing it... I put some c+f chords after those chords I played in the example in what seems like the way I play them by hand and they work fine at 100% with note cut and note off
17
Compos / Re: OpenMPT FM+PCM example song compo (preliminary deadline 2018-10-12)
« Last post by Saga Musix on October 16, 2018, 07:43:09 »You will be able to listen to the songs that made it past the pre-selection once OpenMPT 1.28 is released. This may still take a few weeks, so anyone who wasn't able to submit their tune in time can of course still upload it and contribute to the release package.
18
Compos / Re: OpenMPT FM+PCM example song compo (preliminary deadline 2018-10-12)
« Last post by ballacr75 on October 16, 2018, 07:15:03 »Hi all, where can I listen to compo songs?
19
Help and Questions / Re: Volume Commands with VSTs
« Last post by I-S3-O on October 15, 2018, 21:17:42 »So essentially, they don't work because they're not supposed to. OK. At least I know now.
I guess I'll have to fiddle around with this plugin to get it to do what I want. It's a shame I don't a better granular control of the fade out, though. Like I said, it's very finicky. But at least I still have those Zxx macros to use.
Thanks for the insight on this. I appreciate it.
I guess I'll have to fiddle around with this plugin to get it to do what I want. It's a shame I don't a better granular control of the fade out, though. Like I said, it's very finicky. But at least I still have those Zxx macros to use.
Thanks for the insight on this. I appreciate it.
20
Help and Questions / Re: Volume Commands with VSTs
« Last post by Saga Musix on October 15, 2018, 13:06:29 »The most important thing that must be understood is that the volume concept in trackers is inherently incompatible with that of MIDI, and VST is based on MIDI. The concept of tracker note volume where you can change the volume of a single note after it has been triggered does not exist in MIDI as a standardized concept; there are some ways to change the volume of a MIDI note after it was triggered, including channel volume (which affects all notes on that specific MIDI channel) and polyphonic aftertouch (few devices and plugins support this, and it can be used to modulate anything, not just volume).
What OpenMPT does by default is treat volume commands next to notes as MIDI velocity, i.e. the volume at which a note is triggered. By default volume commands that are not next to a note do not do anything, but they can be configured to change the MIDI channel volume (affecting all notes on that channel) or change the dry/wet ratio of the plugin (affecting all notes on that plugin). You can uncheck "volume commands with notes are velocities" to also apply this behavior to volume commands next to notes.
You can send the results of Mxx, Dxx and other volume commands to plugins as well, but since there is no standardized way to do so, you will have to do it yourself using Zxx macros. Macro letters u and v take these volume commands into account.
Hxx works as well. But again, pitch bends in trackers are inherently incompatible to those in the MIDI world, so OpenMPT needs to know the pitch bend range the plugin is internally configured to use. You need to configure it properly in the instrument settings or the pitch bends / vibrato will sound wrong.
Last but not least, guess what... the concept of Note Cut / Note Off / Note Fade also does not translate to the world of MIDI. There is only "note off", which is what == and ~~ map to. ^^ on the other hand sends a note-off for all playing notes, and in addition sends the "all notes off" and "all sound off" CCs in order to hopefully kill all sound instantly. Not every plugin handles these CCs very well though. How the plugin responds to a Note Off in particular is completely up to the plugin and nothing that OpenMPT can influence. OpenMPT's fade-out does not influence the plugin, unless you send MIDI macros including the "u" macro letter, as described above.
What OpenMPT does by default is treat volume commands next to notes as MIDI velocity, i.e. the volume at which a note is triggered. By default volume commands that are not next to a note do not do anything, but they can be configured to change the MIDI channel volume (affecting all notes on that channel) or change the dry/wet ratio of the plugin (affecting all notes on that plugin). You can uncheck "volume commands with notes are velocities" to also apply this behavior to volume commands next to notes.
You can send the results of Mxx, Dxx and other volume commands to plugins as well, but since there is no standardized way to do so, you will have to do it yourself using Zxx macros. Macro letters u and v take these volume commands into account.
Hxx works as well. But again, pitch bends in trackers are inherently incompatible to those in the MIDI world, so OpenMPT needs to know the pitch bend range the plugin is internally configured to use. You need to configure it properly in the instrument settings or the pitch bends / vibrato will sound wrong.
Last but not least, guess what... the concept of Note Cut / Note Off / Note Fade also does not translate to the world of MIDI. There is only "note off", which is what == and ~~ map to. ^^ on the other hand sends a note-off for all playing notes, and in addition sends the "all notes off" and "all sound off" CCs in order to hopefully kill all sound instantly. Not every plugin handles these CCs very well though. How the plugin responds to a Note Off in particular is completely up to the plugin and nothing that OpenMPT can influence. OpenMPT's fade-out does not influence the plugin, unless you send MIDI macros including the "u" macro letter, as described above.