Hi Everyone,

A serious bug has turned up in 0.87. If you try to save your modules after resizing a pattern (changing its length), then it is likely that the resized pattern will not save correctly. Also, this might cause some problems when the user attempts to load the module back into reViSiT. Therefore, I am releasing a quick patch for just this problem - in the form of v0.87.1. All the features previously destined for this version will now be part of a new v0.87.2.

Because of reViSiT's flexible XML saving mechanism, it may be possible for you to recover part (or even most) of the modules that haven't saved correctly. Here are two approaches: the first is simpler and quicker; the second takes a little bit longer, but might get you some of the corrupted patterns back.

Backup your saved module before you try this.

To remove corrupted patterns from a module manually (Easy):

1) Open the module's .zip file in WinZIP or another archive utility.
2) Extract and open the file, "module.xml", in a text editor.
3) In this file, scroll down to the pattern entries "<pattern ...".
4) If the "index" parameters for the pattern's rows are mostly "0", then this is a corrupt pattern.
5) Remove everything from <pattern> to the next </pattern> (including the tags themselves) to delete the corrupt pattern.

To repair corrupted patterns in a module manually (Medium):

1) Open the module's .zip file in WinZIP or another archive utility.
2) Extract and open the file, "module.xml", in a text editor.
3) In this file, scroll down to the pattern entries "<pattern ...".
4) If the "index" parameters for the pattern's rows are mostly "0", then this is a corrupt pattern.
5) If you can remember the row's where each note should be, simply change the index values to what you recall. Note that the row entries will already be in the correct order. Also, if there is a particular part of the pattern you are desperate to get back, you can simply delete any <row>...</row> and even <track>...</track> entries you don't care about - reViSiT will adapt. So, if you knew you had a really good melody on channel (track) 12, and that's all you care about: Find <track index="12">, fix it, and delete every other <track></track> entry in the <pattern></pattern>. (Note: if you can't remember the correct positions for each of the notes/rows, whilst in the text editor, you should simply number them 1,2,3,4,5, etc. Then you will be able to load the module back into reViSiT and move the row's around in the Pattern Editor with the insert/delete keys).
6) For patterns other than 64, users should also add length="x" (replacing x for the length of your pattern) to the relevant <pattern></pattern> and also each <track></track> object. For example...

<pattern index="0" length="32">
  <track index="2" length="32">
    ...
  </track>
  <track index="3" length="32">
    ...
  </track>
</pattern>

If anyone has any questions, feel free to pose them on the forum - or to me directly by email, via revisit@nashnet.co.uk. For more information, see the reViSiT website @ http://revisit.nashnet.co.uk.

Enjoy!

All the best,
Chris