Latest file won't open

[Sherry C]

Howdy MG,

I'm glad it went well this time. So do I understand correctly that this time the installation did not wipe out your old MidiDev.cfg file? If so, that's good news - I was a little nervous that we'd missed a potential problem!

Anytime you work on your MIDI Device Configuration, especially if it involves lots of edits or entry work, it's probably a good idea to make backup copies "just in case."

I'm also glad to hear the report that 2.6.1 is responding faster for you. Mark worked hard to make Composer more "efficient" so that it runs faster. I'm sure he'll be happy to hear that there's a noticeable improvement in others' files

Now I'm looking forward to hearing what you've been working on so arduously

Also, I haven't forgotten about The Oxen!

ttfn,
Sherry

[mgj32]

Hi Sherry,
Correct. The old mididev.cfg was the only one present in the folder. The first thing I did after re-starting was to check the \Composer folder in Explorer. I suspect Threatfire noticed that a smaller file was trying to replace a larger one and if I'd clicked for it to stop that process, I'd have been all right. Disabling it worked as well, though.

I always have two backups of the entire Notation directory at the end of the day, on a USB My Book and a flash drive. I probably don't have to re-export in Composer.mdd as long as I add instruments to banks already present because they will be added automatically to Composer.mdd. Just a guess, of course.

Mark had done some magical things under the hood. I can speak only for my machine, naturally, but all in operations I tried so far it is not only faster, it is amazingly so.

The draft of what I have been fighting with is done. I am going to try an mp3 recording later, and I suspect there will be enough under 10MB that I can add some things immediately.

all best,
mgj