Latest file won't open

[mgj32]

Hi Sherry,
Actually I was updated from 2.51 according to Add/remove programs. You had sent a 2.5.2 exe which worked and which I've been using for many months, so still can't figure out why only the one file (and the same under two other names) wouldn't open with the same setup as I've been saving and opening it since June.

Nevertheless, I am ready to try again.
I will disable Threatfire this time, just in case. I can't see anything else that would have caused the mididev.cfg that I copied to the Composer folder get stripped.
I have been using New Configuration Detected for ages, using the Ports to include only what 's there. (I had the original Audigy 2, the Soundblaster I tried, since A and B worked together on the previous computer, as well as the replacement and current Audigy two.
In Setup/Device, I listed "Creative" as a new manufacturer and moved everything on the left that is actually present to it, then saved as Composer.mdd and to be safe, also saved as Creative Composer.mdd.
I backed up again, my latest mididev.cfg file.
I put the backups in three places on two hard disks.
Can you think of any other precaution to take?

If not, I will give the update another try. For the brief time I had it going, I really liked the speed of 2.61.

all best,
mgj

[Sherry C]

Howdy MG,

There were a couple of conditions, one of which was if a staff had either the staff name or the abbreviation deleted and then save/closed the file, the file would not reopen in 2.5.2. This and another "cannot reopen" bug that I can't recall off the top of my head were fixed in 2.6.1 Perhaps one of those conditions existed in the file, and therefore it wouldn't reopen. They should open in 2.6.1.

It sounds like you've got everything backed up quite safely. Tally ho!

Let us know how it goes!
Sherry

[mgj32]

Hi Sherry,
It went quite well. I feel the problem was not giving Threatfire the correct answer. With that disabled, there was my old mididev.cfg file. It took me a while to figure out that I had to import from the right side of Composer.mdd what I had exported. Once done, no typing was necessary. I suppose it would be a good idea to make a new Composer.mdd eacj if I change the bank in Sound Font Mgr, or add new instruments to existing banks.

Thanks for the help.
mgj

PS. 2.6.1 does, indeed, seem to respond faster than 2.5.2.

[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