I have the same problems as above.

Also:

How do you save a preset when running as an AU? Standalone gives you the File menu but not in Digital Performer (although it will be saved as a part of the sequence.) The work-around would seem to be create your presets in standalone and then open within the program.

EDIT: okay I see "save settings" on the Display GUI menu. I guess we're stuck putting these files where they're directed which is okay I suppose.

Also when I load VI-14 Perf-Leg Speed+porta the porta strings do not play.

@musos said:

So, I saved the file in the main folder, and only then did the <New folder> dialog become live.

Some kind of interface/graphic bug....?

Regards - Colin

Colin,
we consider this as a feature: Only when you store a matrix/preset in this
special folder it can be found by VI and automatically added to the browser
list.
Personally as a user I go crazy locating the right folder, I prefer programs which
rather point me to the correct place.


christian teuscher
development

@musos said:

I mentioned elsewhere that the VI interface when running as an Audio Unit always stays on top, even when you hide the host application. You just can't get rid of it without actually closing the GUI window.

Well, it seems that you can't even hide the Standalone! (Mac OS 10.4.5)-

Regards - Colin

Colin,
again, we thought this being a treat rather than a bug:
1) When you close the GUI Window you actually hide it - clicking "Show GUI" makes it appear again
2) You can minimize standalone.
3) Staying on top: Consider if VI GUI won't be a floating window - it will disappear whenever you click another window - then you start searching for it.

We have undertaken a quite unusual approach here which has many benefits, these display issues are the tradeoffs at the moment, but we keep investigating.

christian teuscher
development

@musos said:

Another one:
Open one or more instances of VI in Logic. Open the GUI interface.

we are aware of this also trying to find a solution.

Colin, please don't be upset when we don't answer right away, especially when you post something on saturday evening and wonder on sunday that nobody had responded.
We appreciate feedback very much and we listen and instantly start evaluating suggestions/bug reports. But I personally don't want to clutter this forum too much and I usually won't post if it isn't a problem burning under the nails which prevents the user from working.

christian teuscher
development

@dpcon said:

I have the same problems as above.

Also:

How do you save a preset when running as an AU? Standalone gives you the File menu but not in Digital Performer (although it will be saved as a part of the sequence.) The work-around would seem to be create your presets in standalone and then open within the program.

EDIT: okay I see "save settings" on the Display GUI menu. I guess we're stuck putting these files where they're directed which is okay I suppose.

Also when I load VI-14 Perf-Leg Speed+porta the porta strings do not play.

Dave,
pls use Logic's "settings' menu from within the "official" AU window.
Personally I never use any dedicated saving for it gets saved automatically anyway but I understand that you wish to build further on a preset.

The other problem is adressed in another thread...

christian teuscher
development

Christian,

Thanks for responding so quickly an thoroughly. Your software is fantastic and is working fine. Saving is easy, I just didnt see where the menu was. I would have had the same problem with any AU since I'm new to OSX. Also I don't like looking for folders so this is good too.

No need to respond: it seems that whatever problems with OSX are that it runs outside of the sequenceing program. For example the sequencer won't respond if the program is on top and even after quitting Digital Performer, VI has remained open. I'm sure this will all be worked out.

Great work!

Hi Christian and thanks for your replies!
re saving:

@Another User said:

Colin, please don't be upset when we don't answer right away, especially when you post something on saturday evening and wonder on sunday that nobody had responded.

My sincere apologies for that. I'm under serious work pressure, working day and night and weekends, so I forget what day of the week it is. [:O]ops:

Anyway, please accept these posts with real good intentions. Vienna Instruments are the most amazing things I have ever heard or worked with. I am constantly impressed and grateful.

Regards - Colin

@golem said:

Personally I never use any dedicated saving for it gets saved automatically anyway but I understand that you wish to build further on a preset.

The other problem is adressed in another thread...

christian teuscher
development

Hi Christian,

I to had the same opinion and prefered the fact that when I saved my Logic song all my plug-ins were saved.

However two incidents have changed this - the first was a unwanted modification of all my exs instrument settings from a song and all it's back-ups. This happened whilst I was switching between 2/3 songs with the "keep common samples in memory" option on. I ended up with the wrong sounds loading on a lot of the instruments. As it also affected all the back-ups it was if there was a further hidden file soewhere that had got corrupted. I never got to the bottom of it.

The second incident and ongoing is with the Spectrasonic Atmosphere Plug-in. Currently I am doing some re-mixes of some 4 year old tracks created with Atmosphere as a VST plug-in. In Logic OSX Atmosphere now runs as an AU so when I open the old songs it looks for the Atmosphere VST Plug-in, doesn't find it and reports it as missing. Of course I can open the AU Atmosphere plug on the same channel but all the previous VST instrument settings have gone. The net result is a whole series of songs with no access to the plug-in settings, preset or edited sounds in that arrangement - just... nothing!

The only solution I can see is to dig out an old computer with Logic on OS 9 reload the songs and resave the instrument settings.

If you want access to a Vienna Instruments matrix in a few years I would save it now!

Julian

Julian,

With regard to Atmosphere (off-topic here but just trying to help):
You can get FXpansion's VST to AU converter. This "wraps" OSX VST plugins and turns them into AU's (or close enough to use).

I have successfully done this with Atmosphere, Trilogy and Stylus Classic. All my old songs load with the wrapped plugins, so I can at least see what presets were loaded. Unfortunately, you can't save a "wrapped" setting and open it in the real AU.

It certainly helps with backwards compatibility though...

Here: http://www.fxpansion.com/product-auadapter-main.php">http://www.fxpansion.com/product-auadapter-main.php

Regards - Colin

Colin,

Thanks for the reply - I've got the FXpansion software but hadn't thought of using it as I already had the Atmosphere AU version. So just to clarify I should convert my VST atmosphere to AU then load my old songs and write down the setting?

Will the converted VST Atmosphere appear as a second Atmosphere plug along with the native one and if it does how do you tell which is which when selecting a new plug-in?

Thanks

Julian

PS I'm sure Uncle Herb won't mind a bit of off topic as it does spill over into VI territory a little!

Hi Julian (and apologies to the forum for the off-topic dialogue - it may be helpful to other users):

The wrapped plugins look slightly different - they have a kind of "footer" area that is quite apparent.

One warning: I have sometimes had problems trying to open the wrapped plugs if I already had an AU version open. I'd get a UVI error or .dat file not found. Eric Persing recommeded that I re-do my aliases of the .dat files in my /Components/Plug-ins folder and that seemed to help.

I found that the wrapped plugs all opened in Logic with selected/used settings intact. Obviously if you've altered a factory preset at all, your job is more difficult, as you then have to try to work out what settings have changed.

I have actually had limited success running both AU plugs and wrapped plugs in one song, but only after serious mental focus, a small measure of prayer and a bit of voodoo thrown in. [[;)]]

Regards - Colin

Colin,

Thanks I'll try it.

julian

@golem said:

[quote=musos]

3) Staying on top: Consider if VI GUI won't be a floating window - it will disappear whenever you click another window - then you start searching for it.

We have undertaken a quite unusual approach here which has many benefits, these display issues are the tradeoffs at the moment, but we keep investigating.

christian teuscher
development

I would go along with colin here - this window floating on the top is a real pain [[:|]] i can see the advantage of it, but unfortunately in DP, say i go to change a matrix and have the window at the front, no sound will play until i click on a DP window, rather than the VI plug-in. it's pretty frustrating having to click left right and centre, just to be able to change and hear the sounds if you're auditioning by a midi keyboard.

Another rather frustrating thing with the GUI is if you refresh or change a screenset in Logic the opened VI GUI disappears so you have to re-open it every time.

Julian