actually TABbed back -- not very intuitive
I forgot to set up the correct tab order for this dialog - will be fixed in the next release. Also the shortcut issues should be resolved at some point.
Now that you've moved the Transpose amounts to a more efficient submenu (good idea), can you now reconsider implementing a long-time FR to include Transposition by sevenths and possibly fourths? This would save us keypresses.
See my response here: http://bugs.openmpt.org/view.php?id=269
Still have a persistent problem: AIFFs still cannot be previewed from the Folder Tree when double-clicking them, which has always been SOP. Should i submit a FR to get that "fixed" at some time in the future?
This seems to happen with only a few types of AIFF files, I'll look into that shortly.
Don't know what you're talking about. I selected one sample as well as all the samples in a typical waveform, right-clicked in a selection of the sound data, and selected "Zoom". The first time it adjusted the zoom to the right level to show the whole selection. Right-clicking again and selecting "Zoom" did not change anything and was not grayed out.
This fix only applies to overly long sample selections which would previously not have adjusted the zoom at all. This fix does not apply when zooming into the same selection twice as in your example.
After extensive testing, i see you have completely fixed this. This fix gets my biggest thanks, as i do a lot of work with the M1 (it was after all my first synth). The fix also applies to the other VSTs in the Legacy bundle, including, as in my case, the original, unpatched package, version 1.0.0, which included the WaveStation VSTi and the MDE-X VST FX). I'm so glad i don't have to revert to an older build of MPT. Thanks again...
Good to hear that it's working. This was actually not a bug in OpenMPT but an oversight by the Korg programmers, which was apparently fixed in the latest versions of the M1 plugin, but not the Wavestation plugin. I have sent an email to Korg, but I have not received an answer as of yet...
Many times you mentioned that fixed functions now work as the original tracker intended them to. Only problem is, how do we know what they were "supposed" to do? Can you clarify what they were doing and what they do now, in these particular cases?
Qxy fix: The note would not have been retriggered if for example the current speed is 6, and there is a Q06 command and a pattern delay on the same row. Now the note is retriggered as one would expect it to do.
E5x fix: The correct finetune values were already displayed in the note properties dialog, but other finetune values were applied. E5x is now only applied when found next to a note.
Txy fix: The most notable difference is that the tremor on/off state is preserved even after the effect has been applied. So if the volume is turned of on the last tick of a row and there is no tremor command on the next row, the next row will remain silent.
E5x fix: Contrary to the XM E5x fix, this one is really just a very small difference that you won't notice under normal circumstances and I'm not even sure how to explain in words (been a while since I fixed this).
So for XM tracks, do these apply fully when used at the same time? Does one get processed first or are their values added? Does the fact that Volume Column commands use decimal and Channel FX commands use hex have any bearing on the portamento processing?
From the manual: "Combining the effect [gxx] with 3xx will double the effect parameter (e.g. g01 would act like g02) and ignores the 3xx command."
For IT-compat tracks, does this mean that, for example, calling SD8 for a row that has 4 ticks to it will delay the note for two full rows?
No, SDx never affects upcoming rows. As an example, SD5 didn't do anything at speed 5, even if there was a fine pattern delay on the same row (which would have increased the row's length by a few ticks).