Problem with Tool Set files...

[Mattias Henningson]

I have some problem with the performance tool and the tool set files.

1. When starting the performance tool and selecting a legato instrument, not all of the instrument's range is available before opening the options page and pressing apply for the channel in the tool. The same thing happens when loading up a tool set file with channels set to legato. It becomes a bit tedious to "options/apply/ok" for all legato channels when you load performances with several perf tools on more than one machine.

2. It seems like the port setting is not saved in the tool set file. When starting more than one perf tool and loading different tool set files for these instances they all get some default port instead of the one I used when saving the file.

/Mattias

[Mattias Henningson]

bump.

cm, herb - Do you know about this problem or are all settings in the perf tool restored when a tool set file is loaded?

/Mattias

[herb]

Sorry Matthias,

it seems, that I missed the topic.

1. You can generate your own default template of each mode.
For example legato: go into the edit mode, setup your template and save it over the "legato default.pal" file.

2. If you are using multiple tools for multiple ports it's not possible to save the different port settings. As far as I know, it's a windows restriction, that you can't save different port settings for one application. Only the last setting will be saved.

I'm sure Christian Marin can explain this problem much better.

Chris Teuscher is working on the next version of the tool, which will support multiple ports in the application directly.

best wishes
Herb

[Mattias Henningson]

Herb,

Thanks for answering, I figured you missed it the last time... [:)]

I certainly use multiple tools on a single computer but I can't see why the port setting should be impossible to save. It's still just a setting for the perf tool...? Ah...whatever. This problem will obviously be solved by the next version, I'm happy with that.

The range problem described in question 1 is far more annoying. Is that a known problem? I just loaded my rather big template across my three boxes the other day and played some songs for a friend of mine who came by the studio. It sounded really wierd and it took a while before I realized that all legato instruments were quiet below C3...

/Mattias

[herb]

As far as I know are midiport settings for an application also saved into the Windows OS settings. And if there is only one application (one performance tool installed on your engine - independently how much instances you open), windows can save only one setting.

Your problem with your template sound strange.
I'm storing my tool setups normally in my individual project folder, (gsp files, audio renderings etc).
I just made a test:

I made a setup in one tool instance: 3 different legato settings on the first 3 midichannels.
Left the legato edit mode, and saved the whole tool setup as "test-port_1"
Than opened a second instance, set in to port 2, made also a setup with three different legato templates amd saved it as "test-port_2"

Then closed both tool instances, opened again two instances and loaded the two different sets. Everything loaded right.

Is this a problem which occured only one time on your system, or everytime you open your setups?

[Mattias Henningson]

Thanks for the update!

Strange...it happens everytime on my three systems! The thing is the legato channels correctly show legato after loading the tool set file, but the entire play range is just not there. It's been like that since I first installed the tool. I'll have to check I'm not doing anything stupid again...

/Mattias

[herb]

Maybe an uninstall and reinstall of the tool could help?

[cm]

mattias, midi in windows is a little bit tricky. i noticed, that even if you set midi-source to another port within another application, the last selected port opens. last year i had a short look into the multimedia-SDK, but gave up immediately - this is a task for specialists. i'm still questioning myself, why we need virtual midiports, the OS should inherit this all, but obviously it doesn't work for some reasons (maybe jeff could shed some light on that?)
christian