MeterzPak 0.8.5-b67 (dev build release)

[plover]

MeterzPak - version 0.8.5-b67

This release requires QCD development build b67 or later.

This is mostly a release to fix some long standing bugs. Details about installation and use of the skin features can be found in the release notes for the previous version here.

The only added feature is that the color picker now reports (in the config dialog status bar) the coordinates and color for the current cursor position. (For some reason this report does not work everywhere on the screen, e.g. on the taskbar. But colors can still be grabbed from those areas.)

As people seem to be using the setting, I also restored the input widget for the number of resonators on the config dialog. Note that there are two separate problems related to how QCD responds to changes in this value:

1) For certain numbers of resonators, several resonators will appear "dead", i.e. act as if their value is always 0. This is a known problem with the QCD spectrum analysis code which will apparently be a real devil to fix.

2) Changing the number of resonators while QCD is playing doesn't work right. The correct number of meters displays in the vis window, but the spectrum analyzer apparently does not receive the notification of the change -- if the number of resonators was increased, the high-end will appear "dead". If play is stopped and restarted, this problem goes away (presuming problem 1 is not also occurring... http://beta.quinnware.com/forum/images/emots/rolleyes.gif ). I don't know what is going on with this yet.

Bug Fixes:



Saving from config dialog should now work under win9x.
Fixed problem which caused QCD to crash during shutdown.
Double click on vis window to bring up config dialog should now work in all skins.

---> See next post for download... <---

[plover]

This is a bugfix for the previous bugfix (made necessary because Micrhttp://beta.quinnware.com/forum/images/emots/skull.gifsoft's API documentation was wrong...http://beta.quinnware.com/forum/images/emots/robot.gif)

Anyway, now the save problem for Win9x really should be fixed...

[ace2701]

This is a bugfix for the previous bugfix (made necessary because Micrhttp://beta.quinnware.com/forum/images/emots/skull.gifsoft's API documentation was wrong...http://beta.quinnware.com/forum/images/emots/robot.gif)

Anyway, now the save problem for Win9x really should be fixed...
Plover .. check my PM to you.. it works this time! Thanks for all your efforts to get this vis to work on my OS.

[ace2701]

A small question, plover. When I add a new resonator to the .ini file, the first character is always a"@". I have to change it to a ":". Any reason for this to happen?

[plover]

When I add a new resonator to the .ini file, the first character is always a"@". This is a detail that I keep forgetting to write into the MeterzPak.ini file.

The line starting with the '@' character tells MeterzPak which configuration to treat as the default. (If there's no line with an '@', the plugin uses the first configuration.)

On saving from the config dialog, the default is set to whichever configuration is currently shown in the dialog. (Which was not actually my intention -- it should be set to whichever configuration is actually being used in the vis window. Of course, this only makes a difference when 'Auto apply' is turned off.)

[ace2701]

This is a detail that I keep forgetting to write into the MeterzPak.ini file.

The line starting with the '@' character tells MeterzPak which configuration to treat as the default. (If there's no line with an '@', the plugin uses the first configuration.)

On saving from the config dialog, the default is set to whichever configuration is currently shown in the dialog. (Which was not actually my intention -- it should be set to whichever configuration is actually being used in the vis window. Of course, this only makes a difference when 'Auto apply' is turned off.)
Thanks for the explanation plover. That makes sense. I really don't care about the "@" now that I know why it's there.:)

[shaohao]

Crash QCD when I try to playing music in MeterzPak mode.

[plover]

Crash QCD when I try to playing music in MeterzPak mode.
So far, this problem seems to happen only with b71, and only with the QCD default skin.

Has anyone found that MeterzPak 0.8.5-b67a crashes QCD under other circumstances?

[plover]

The crash apparently occurs in the code used to detect configurations included in the skin file. The current version should work ok if "Default to skin" is turned off in the configuration dialog.

[ace2701]

So far, this problem seems to happen only with b71, and only with the QCD default skin.

Has anyone found that MeterzPak 0.8.5-b67a crashes QCD under other circumstances?
Matter of fact! I was making a new configuration for Retrobox, and the whole system froze. Had to do the 3 finger salute to restart. Was going to mention it, but read your "uncheck default to skin" suggestion, and that seems to have done the trick. Using B67 at home with 0.8.5-b67a.

[plover]

I was making a new configuration for Retrobox, and the whole system froze.
Do you know what settings you were tweaking that caused the freeze? Or do you mean that you added a configuration to the ini file in the RetroBox archive?

[ace2701]

Do you know what settings you were tweaking that caused the freeze? Or do you mean that you added a configuration to the ini file in the RetroBox archive?
It happened while I had the color picker activated and was moving the mouse around the skin to choose a particular color. Didn't have that problem making a new resonator set on an earlier skin, however. Small point.. in Retrobox, I was trying to capture a color from a moving title.:ermm: It worked after using your workaround.