plug-in window behavior

[fastlanephil]

I started a new file and tried to select a plug-in but when I selected a plug-in from my list it highlighted one about four above on the list. So I clicked below the list on plug-in lists that were blank but selectable until the one I wanted was selected. After dragging it to the Effects/Synth window it worked correctly again. I wonder if it is the GPO plug-in or something else. Anyway I am able to fix it when it happens.

[Scoot]

I assume you're doing what I do and dragging from the plugins and effects windows.

Can you grab the plugin from inside the graphic editor window instead?

[fastlanephil]

I do drag from the plug-ins window. I'll try selecting from the graphic editor also and see what happens if this problem comes up again.

[Jerm]

I have seen this before but I thought it was corrected. What version of Metro are you using?

[fastlanephil]

I'm using Metro 6.2.4 and OSX 10.3.8. It selects eleven plug-ins up the list when I try and select the last one which is the second ST2. If I click and drag the very bottom of the window it will drag over that plug-in. After that it works correctly. This problem does not occur with the graphic editor plug-n selection.

[Jerm]

Phil,

More details would be helpful. Are you saying that this happens only the first time you try to drag from the plug-ins window? Does it only happen when you drag the last item in the list? How many plug-ins do you have? Does changing the sort order by clicking on the column header help?

[Scoot]

The other question is does it happen if ST2 and GPO are not in the list?
(take em both out first and launch metro and then add them individually)

[fastlanephil]

I took STR2 and GPO out of the Metro VST folder and started up Metro. No problems. I then put ST2 back in the Metro VST folder and restarted Metro. No problems. Then I put GPO back in the Metro VST folder and restarted Metro. No Problems. This seems to have fixed the problem. There must have been a conflict between ST2 and GPO loaded in Metro. This may have been caused by my earlier problem when I replaced some ST2 instruments with GPO instruments and then back to the ST2 instruments and the ST2 instruments became corrupted. I'll do a test of this again and post if it produces the same results.

[fastlanephil]

I have not been able to duplicate the problem so I quess there is no problem.

[Scoot]

Low memory/resource problem?
Or maybe a resolution - 16bit/24bit colour prob?

The phantom metro menace.

[Jerm]

It may be that the plug-in was in both folders, user and system.