In fact,

when working in logic, all is saved with the song. Everything is called back when re-opening. I don't work with presets in VI. I open a blank VI instance and I make, patch after patch, what I need for the track. I didn't saved anything because I was not use to need it and the problem I encounter now (blank VI track evrywhere) is pretty unpredictable.

I think it's pure PPC / Intel issue…

Although time consuming, could you open the file on a ppc mac (even a slow one you don't need playback capability) and then save each of your presets and set ups carefully named on a per track basis so that when you open the file on the mac pro you can load in the presets. Time consuming perhaps but better than starting completely from scratch. The other alternative is to again open the file in a ppc mac and print the files off in 24 bit and load them in to the mac pro that is if you are finished and just want to mix.

How is the Mac Pro by the way - I heard they have quad cpu processors coming in November (possibly that soon) - 8 cpu's per machine, and I also saw an article where somebody has already got their hands on two of those processors and swapped them with the xeons in the mac pros, and it worked! he booted up the machine, and activity monitor showed 8 cpu cores running, - he posted screen shots. Very cool that you can upgrade these new macs more like a pc.

Miklos.

I seem to remember someone from VSL (possibly CM?) saying there was no need to save presets in Logic as they were saved with the song. This is indeed true. however when I swapped my Spectrasonic Atmosphere installation a few years back from A VST plug to an AU I lost all the presets on loaded songs. The workround was to load the old Logic songs then used Atmosphere as a VST plug in an AU wrapper!

I would hope that as the VI's are an AU in PPC and Intel that they will retain their Logic created settings and that the problems you are having are maybe a bug that needs to be fixed.

It would be good (imperitive!) that we find out the answer - I currently still work in PPC when using Logic so when I change over to MacIntel the last thing I want is a load of blank archived songs.

Can someone from VSL offer some guidance

Thanks

Julian

The problem from vst to au would make sense as the plug in files are two different plug ins technically - two different files - so logic doesn't know that it's the same plug in, it just sees a different plug in file and loads the blank presets, the having a problem with the same plug in on the same platform from one cpu to another, doesn't make sense, unless logic is loading a universal binary of the plug in? Then perhaps the plug in itself is again different, or logic is reading a different part of the plug in file and therefore not loading the presets. Are plug ins required to be universal binaries too?

This is an interesting problem - what about Mac users transferring project files between machines - one being a G5 the other a Mac Pro - will we lose all the settings? that could be a major problem! Is there any comment from the VSL team on this issue? Could a fix be implimented if there is a problem?

Miklos.

I gave a song to a MacPro user (I have a G5) and it crashed Logic every time he tried to open it. Could be an isolated incident, but makes you wonder. however, I assume he woudl have to be running 7.2.2 and i am running 7.2.0. I don't want to upgrade until my CD is finished - this week!! - for fear of problems.

@Another User said:

....when I swapped my Spectrasonic Atmosphere installation a few years back from A VST plug to an AU I lost all the presets on loaded songs. The workround was to load the old Logic songs then used Atmosphere as a VST plug in an AU wrapper!

I imagine this will be a problem once again when one upgrades to an Intel Mac. All plugins need to be Universal Binaries (UB) to work in Logic, so they may not even be recognised at all, never mind their settings!

I'm already preparing to set aside a week or 2 to go through important songs and make sure I have saved every setting wherever possible (in the plugin's format as well as in Logic). [the reason for this is that settings for wrapped VST versions do NOT work in AU's - the only solution is in a native plugin format, as far as I can see....]

Hopefully, the VI settings that one has saved will also work in a newer UB version on Intel Macs.

Colin

Let me change this post to say more specifically: This would s**k if it were Apple not bothering with allowing compatibility: if it is a VSL thing, then obviously an update needs to have time to be made - in other words I didn't at all mean to say it s**ks on part of VSL at any time! It never crossed my mind! I was talking about apple, ppc to intel, and logic pro - I was venting.... but not re VSL. Sorry! [:O]ops:

@alman said:

Hi,

when I load an old Logic (7.2, PPC) project into my new mac (MacPro Quad 2.6), VI opens but without any patch loaded in. A perfect virgin VI track.

My project was not builded with presets matrices… so I dont't know what to do.

Thanks.

A.

Hi,

this incompatibility will most likely be fixed in the upcoming software update.
Thx for your patience.

Best regards,

Good to hear.

Thanks!

Julian