Here is a summary of bugs that has been reported for version 0.4.3
- Fixed arpeggio behaves incorrectly in the tracker. NSF export is fine.
- Using the preview full row option will affect all channels when muting / unmuting channels. Disable that option to avoid that.
- Toolbar icons is missing on windows XP
- NES export is broken
The arpeggio bar in the FDS instrument editor seems to be lower than the grey line normally and not in it. I also believe this is in 0.4.2. Also, as I move the bar up or down, its steps are not in sync with the lines.
_______________________
It's 2026. You shouldn't be here....... YouTube Dropbox
There is another weird bug that I found (This seems possible on a 2A03 module with speed 8 or 9). If your FTM has multiple tracks, here's what happens: if your song is playing at the last row and you change the track right before the song loops, then the other song plays for the first time and its rows look arranged in such a way that makes itself look like it was supposed to continue the previous song. I am uploading the module where this issue was seen. (It happens when I change the track from Clockwork Act 1 to Act 2 in the conditions I have stated). Also to avoid any copyright conflict, I am not responsible for this module, but only uploaded this because I can't make the bug happen on a different module.
EDIT: Actually the same song is displayed twice.
_______________________
It's 2026. You shouldn't be here....... YouTube Dropbox
Using VRC7 with other expansions (multichip) makes everything much quieter and it sounds nothing like it used to. I cannot do what I do with this problem. I'll attach a multichip song and I want you to listen to it in 0.4.2 and then in 0.4.3. Is there any way to fix this?
_______________________
Alas, poor Yorick, I knew him, Horatio...
No. Multi-chip songs are still completely unsupported and I do not recommend using it at all. There is a reason the application itself doesn't allow you to select multiple chips.
If you want to create actual working multi-chip songs, then PPMCK is the only option (as I'm aware of).
Who said nobody uses it? I am well aware that plenty of people still do. But Microsoft discontinuing support for it makes it officially outdated, regardless of how many people choose to continue using it.
Microsoft's support for it is irrelevant. They have a completely different agenda than users or developers. There's a lot of good reason to continue developing XP-compatible applications at the present.
Edit: and for the record, Microsoft actually does continue to support development tools for XP. They were forced to re-instate a compiler that targets XP for VS 2012 because of the overwhelming demand from developers.
I don't plan to drop XP support yet, but I don't use it much anymore so bugs might happen without me getting to know it. I'll still try to fix bugs in these cases.
Maybe the Qt port will help? After all, MFC is Microsoft. XP is Microsoft. Qt is *not* Microsoft. "One of these things is not like the others..." hum hum
I am almost done upgrading the Qt port to 0.4.3 -- and will try a build of it on XP.
.png)
"One of these things is not like the others..." hum hum
