Another day, another update. This one's not "critical", but nonetheless important if you use the SDx command (and, indeed, most other effects), or seem to be having trouble unmuting channels in the Pattern Editor.

In the former case, it seems one of the fixes in v1.00.3 Pro broke all the between row processing (notably SDx). As far as I can tell, I'd written perfectly reasonable code, but I get the impression that the (MS) compiler might have "optimised" it in a way that broke it.

Download from http://experiment.nashnet.co.uk.

Chris

Hi CS_TBL,

Thanks for the feedback - though if you want to stop "floating" (?), you Dutch should lay of the weed!

Most of the problems were the result of the steps I've taken to improve thread safety. What that means is that the UI now takes a copy of the module data it wants to edit, edits the copy, and then at some point when it's safe, copies it back to the module. Trouble is, some of the ways the GUI worked means that reViSiT was sometimes getting confused about what it was working on, and not copying the right data back into your module.

I still need some more data on some issues before I release the update, but issue by issue:

Re: Advanced MIDI Settings

Fixed. This was where the settings dialog was working on the module data, and not the copy, but using the copy for display purposes. Should even be more thread-safe in the future.

Re: Pattern Update Bugs

I can't reproduce this problem. If you can establish an exact procedure (step by step, key by key, etc.) for me to follow, I'll stand a better chance of seeing what's going on.

Re: Play Song triggers

"Fixed." This isn't really a bug, but I've change the behaviour to be more intuitive. What happens is that Play Song (F5) wouldn't start a new song unless reViSiT was completely stopped. This meant that if any note trails or hanging notes were lingering around, even after pressing stop, it wouldn't start. reViSiT no longer waits for such audio activity to cease (though still won't override already playing patterns and songs), and also gives you a stronger stop feature, upon the second Stop (F8) command. This should also help with loading and saving (which also can't currently be done during playback).

Re: Overwrite vs. Insert in text boxes.

Fixed. This is due to the data copying process that I mentioned earlier being incompatible with the insert space code.

Re: Notes not playing.

I really need a demo module or exact procedure to reproduce this problem, before I can work out what's going on here. Sadly, I don't really have the time to write counterpoint to test each bug.

'Hope this helps,
Chris

Absolutely frickin' hideous - use a tissue next time, please.

Note to everyone else: this is not what reViSiT looks like - pattern display bug or no!

However, what skills CS_TBL lacks in aesthetics, he makes up for in bug reports (and the occasional ditty), so I'm now happy to confirm that the pattern display bug is sorted now, too - so, hopefully, no more phantom pattern entries.

I'm now just waiting on some feedback from another user before issuing v1.00.6 Pro.

Best,
Chris