In an earlier posting I described oddities in the operation of the GUI of V.1.1 of the VI software in Logic and Digital Performer. Perhaps I was not clear in my description or perhaps the source of the problems lies somewhere other than in the Vienna Instruments software, but, whatever the case, no one from the VSL team has yet responded - - hence I am directly addressing the team in this posting.
Anomalies in interface behavior:
Logic:
1. Once you’ve opened the GUIs for several tracks, pushing the “show window” button on the floating VI AU server interface panel brings to the fore the last accessed GUI instance rather than the GUI instance that is supposed to be attached to the panel containing the “show window” button.
2. Logic does not consistently retain the track name if the track is named on the track channel strip - - it does appear to retain the track name if the user uses the “create track name” command from the track menu of the arrange window.
3. Neither the VI AU server interface panels, nor the GUIs reflect Logic’s track or channel strip names but are simply named “untitled,” “untitled 2,” etc.
4. The VI AU server interface names are incorrectly numbered. For example, in a current file. Instrument 1 is labeled “Untitled,” Instrument 2 is labeled “Untitled 2,” BUT, Instrument 3 is labeled “Untitled 4,” while Instrument 4 is labeled “Untitled 3."
Digital Performer:
1. The VI AU server interface panels do not float above the DP windows.
2. Neither the VI AU server interface panels, nor the GUIs reflect DP’s track names but are simply named “Vienna Instruments 1,” “Vienna Instruments 2,” etc.
3. In contrast to what happens in Logic, pushing the show window button on a VI AU server interface panel brings to the fore the associated GUI.
4. In contrast to Logic, the VI AU server interface panels are correctly numbered.
In Logic one can work around the “Show Window” problem by carefully positioning the GUI windows so that some portion of them is visible behind the open Logic window or by linking the VI AU server interface panels so that only one is open and one can change instrument by using the instrument number on the panel. I have found no solution for the incorrect numbering of the panels or their failure to reflect track or channel strip names.
In Digital Performer, one can work around the fact that the VI AU server interface panels do not float by positioning them so that they are not covered by any of DP’s windows.
These issues - - especially those that pertain to Logic represent an impediment to workflow. Clearly, one would, for example, expect that pushing the button on a given the VI AU server interface panel would bring to the fore the GUI associated with that panel and that the panel numbering would reflect the instrument number.
That said, I want to congratulate the VSL team on the very significant enhancement of the VI software represented by V 1.1
My first question is: do the issues I've mentioned have their origin in the VI software, Logic 7.2.3, or OS 10.4.8?
In the past, I have been very pleased by the quick response of the VSL team to issues users have mentioned on these forums, so I was surprised that my first posting received no response. Again it may be that my initial posting lacked clarity, so I'm hoping that this one is more clear.
I would like some reassurance that the VSL teams recognize that, whatever the cause, these problems exist and, especially in the case of Logic, are not entirely trivial. I would also like to have some reason to hope that if the source of these problems is the VI software, that VSL intends to address them.
Thanks!
Anomalies in interface behavior:
Logic:
1. Once you’ve opened the GUIs for several tracks, pushing the “show window” button on the floating VI AU server interface panel brings to the fore the last accessed GUI instance rather than the GUI instance that is supposed to be attached to the panel containing the “show window” button.
2. Logic does not consistently retain the track name if the track is named on the track channel strip - - it does appear to retain the track name if the user uses the “create track name” command from the track menu of the arrange window.
3. Neither the VI AU server interface panels, nor the GUIs reflect Logic’s track or channel strip names but are simply named “untitled,” “untitled 2,” etc.
4. The VI AU server interface names are incorrectly numbered. For example, in a current file. Instrument 1 is labeled “Untitled,” Instrument 2 is labeled “Untitled 2,” BUT, Instrument 3 is labeled “Untitled 4,” while Instrument 4 is labeled “Untitled 3."
Digital Performer:
1. The VI AU server interface panels do not float above the DP windows.
2. Neither the VI AU server interface panels, nor the GUIs reflect DP’s track names but are simply named “Vienna Instruments 1,” “Vienna Instruments 2,” etc.
3. In contrast to what happens in Logic, pushing the show window button on a VI AU server interface panel brings to the fore the associated GUI.
4. In contrast to Logic, the VI AU server interface panels are correctly numbered.
In Logic one can work around the “Show Window” problem by carefully positioning the GUI windows so that some portion of them is visible behind the open Logic window or by linking the VI AU server interface panels so that only one is open and one can change instrument by using the instrument number on the panel. I have found no solution for the incorrect numbering of the panels or their failure to reflect track or channel strip names.
In Digital Performer, one can work around the fact that the VI AU server interface panels do not float by positioning them so that they are not covered by any of DP’s windows.
These issues - - especially those that pertain to Logic represent an impediment to workflow. Clearly, one would, for example, expect that pushing the button on a given the VI AU server interface panel would bring to the fore the GUI associated with that panel and that the panel numbering would reflect the instrument number.
That said, I want to congratulate the VSL team on the very significant enhancement of the VI software represented by V 1.1
My first question is: do the issues I've mentioned have their origin in the VI software, Logic 7.2.3, or OS 10.4.8?
In the past, I have been very pleased by the quick response of the VSL team to issues users have mentioned on these forums, so I was surprised that my first posting received no response. Again it may be that my initial posting lacked clarity, so I'm hoping that this one is more clear.
I would like some reassurance that the VSL teams recognize that, whatever the cause, these problems exist and, especially in the case of Logic, are not entirely trivial. I would also like to have some reason to hope that if the source of these problems is the VI software, that VSL intends to address them.
Thanks!