Logic 8 and 3rd party plugins after upgrade

has anyone upgraded yet??????, whats the word on compatability on the 3rd party plugins
are they not going to work until they are updated again ???
has anyone tried or has anyone got the good word?
becasue mine will be here tomorrow
rock on

there are issues with multi-Output Instruments in the AU side; other than that so far so good .

Similar Messages

Will Lion work ok with Logic Pro and 3rd party plugins?

Will Lion OS work ok with Logic Pro and 3rd party plugins?
Any help would be much appreciated,
Regards James

Well, Sylenth I know... works under Logic Pro 9 and it should be found by left clicking and holding... the Software Insturment Button (The one just below where it says i/o and then scrolling down in the menu that appears to the Instrument section below the Apple Plugins...
I don't know about Massive 1.01 because i think that one is not Logic 9 compatible because it is so old.... and I have never used Vanguard... but according to it's specs the latest version should be found in the same place as Sylenth...
Both Sylenth and Vanguard are 32bit plugins...
...and.. it probably doesn't help that you are using older/not 'legal' copies of these plugins.... *ahem*

Lost all my actions and 3rd party filters after upgrading to Photoshop CC 2014

How do I get all of my actions and 3rd party filters from Photoshop CC to Photoshop CC 2014?

If you migrate your CC presets you should get your Actions, Pattens, Sahapes, Shapes etc back. Menu Edit>Presets>Migrare Presets. You need to copy or to install you 3rd Party plug-ins into CC 2014.

Leopard, ps cs3 and 3rd party plugins

help again please.
I have PS CS3 and numerous 3rd party plugins but as soon as I installed the new OS 10.5 I get the msg. one or more plugins are currently unavailable on your system. They worked before the upgrade of os10.5. I even upgraded to 10.5.1..The plugins I can't get are Nik color efex pro complete and Nik sharpener pro complete. The Nik website states they are compatible. Other 3rd party plugins like Fluid Mask 3, Genuine Fractals and Flaming Pear all work. Help if you can please. I already have a msg. to Nik software for help but have not gotten an answer from them..
Thank you.
sincerely
karen

To use your Nik Software products on a new Intel-based Mac Computer with Photoshop CS3, simply follow these three easy steps below:
1. Quit / Exit out of Adobe Photoshop CS3 and navigate to the Adobe Photoshop CS3 application file which is typically at the following location: Macintosh HD | Applications | Adobe Photoshop CS3
2. Highlight the Adobe Photoshop CS3 application file icon and press Command + I (+ I) to open File Info.
3. On the File Info window (as shown on the right), check the box next to "Open using Rosetta", then close the window.
That’s all there is to it. Photoshop and Nik Software filters will work without a problem.

CS4 and 3rd party plugins - icons disappear

I'm having problems with CS4 on Vista 64bit with 3rd party plugins. I'm aware that 64bit issues exist but even on the 32bit CS4 Photoshop's toolbar icons disappear once Nik, OnOne etc are installed. I've left CS2 installed as well on the same system and this works fine.
This could be a problem with for the 3rd party developers of course but obviously CS4 has changed something.
I have Vista 64bit with 8gb RAM. Disabling the GPU functions doesn't help nor does running CS4 in XP compatibility mode. Removing the plug ins is the only way to resolve the problem.
Just wondering if anyone else has hit this problem and even better found a solution to it.

I think I can recall the behavior being confirmed for Nik and they are working on a fix/ update. The situation may be the same for other tools/ vendors, so you'll probably have to live with it for a moment or resort to using older versions of PS...
Mylenium

FInal Cut X and 3rd Party Plugins from Previous Versions

will they be compatible?
i've got plenty of 3rd party plugins i've normally used with fcp 6.
will i be able to use them with fcp x ? or is it a completely new platform?
cheers.

I've said it elsewhere, but using FCX is like being asked to carve a roast and being handed knife purposely dulled to keep me from hurting myself.
However, while it is not a viable tool for the broadcast professional, I am sure there are many professionals who can use it to do their job.
To the OP, FCP 6 plugins, will work in FCP 7.
BenB wrote:
...snip...
As for plugins, FCP X uses a whole new underlying framework, totally, radically different technologies under the hood than legacy FCP 7 versions. So those plugin developers will have to port their wares over to the new platform.
...snip...
This is in fact, largely untrue. FCX effects are Motion wrappers, often interfaces directly to FxPlug plugins that have been around since Motion started. The FxPlug plugins developed for earlier versions of the software need to be rebuilt with the new frameworks and Motion wrappers constructed, but FxPlug 2 is not radically different technology from FxPlug 1.2.5.
Patrick

Photoshop CC 2014 and 3rd party plugins

When I installed Photoshop CC2014 my 3rd party plugins didn't port over. Do I have to reinstall them?

Moving this discussion to the Photoshop General Discussion forum.
Petermclennan considering Photoshop CC 2014 is a new version of Photoshop you will need to reinstall your third-party plug ins.

Leopard logic pro 8 3rd party plugins

Hey all,
are all 3rd Party Plugins working in Leopard??

All the ones I use are. Hope this helps!

Lost AUplugins and 3rd Party Plugins

I recently switched my logic pro 9 to open in 64-bit and while scaning my audio units and plugins,it froze so i restarted my comp and switched it back to 32 and it started scanning them again and the same thing happend,so i restarted again and opened it up again.this time it opened up my project but i couldnt find my auplugins,not in the channel strip or nothing.i looked in library/audio/plugins/components and there were there but logic and garageband arent reading them.help plz

In another thread the suggestion to run Logic 9.0 was made, and in yet another thread the suggestion was to run Logic in 32bit mode first (that it would find the missing/upgraded AU) I tried running the Applications->Logic 9.0 and ype it found the upgraded "Play" plugin (2.1.2, which by the way in /library/Audio/Plug-Ins/Components/Play.component says it is 2.1.02 instead). I Quit Logic Pro 9.0 and tried to run Logic 9.1.3 in 64 bit mode, and the error "Something is using Logic. Ask it to let go" (OK that is lame but I didn't make a note of the exact msg sorry) It turned out that Force Quit on FInder/restart allowed Logic to run. Now if Play was only 64 bit so I didn't need the 32 bit AU bridge... which continuously crashes....

10.5 and 3rd party plugins LP8

If i install Leo 10.5, will i have to reinstall all my 3rd party plugs?
sorry if this is a lame subject but i just don't know who to ask.
Sie

my recommendation is that you should do a clean install of 10.5 and yes you will need to install 3rd party plugs, however, others have done upgrades without issues but your mileage may vary.
I found doing a clean install with full reinstall, while time consuming, gave me a system that runs like a charm.
R

Logic 64bit - slow 3rd party plugin adoption

One of the biggest and long awaited feature in the recent Logic upgrade was it's 64bit support. The breaking through the 4GM Memory barrier. No more holding back on the amount of memory hungry plugin channels. After a long struggle with the proper Intel adoption, Spectrasonics came back big time and is now the shining start in the 64bit plugin universe. VSL ditched their clumsy home-brewed UI solution last month and even Kontakt4 is on the 64bit team, although other plugins in their product line (Kore2) are still pending. Even a poor marketing stunt called "Komplete 7" is more of a money generating effort because all the product in that bundle are not "kompletely" up-to-date in the 64bit universe.
One big villain seems to be PACE, the maker of the iLok. They are holding all the developer hostage that rely on their iLok for copy protection. ITt is said that their copy protection scheme was cracked and now they have to fix it before releasing the 64bit verion. Their inability to get their "copy protection" act together is getting pathetic. While they are still looking for the unbreakable copy protection (note to PACE: "There is none!!!), they don't realize that they created a perfect "virtual" copy protection. A product that can't be released, can't be stolen. Problem solved.
Although EastWest claims that their 64bit AU version for Play is ready but waiting for PACE (another of their victim), I don't understand why IvoryII (finally announced today for a Sept 13 release) is still in development for the 64bit version. Wasn't that version announced for a spring 2010 release?
Why isn't there more pressure from plugin developers on PACE to get their act together and why don't plug-in developer feel the urge to speed up their 64bit development for the Mac?
I was waiting all those month to finally spend the money and buy Ivory II and now it is out but still in 32bit. But due to my own rule, I'm not buying any product that isn't released in native 64bit AU version and that includes Ivory II. Maybe for us Logic users, two things could speed things up a bit:
1) Let the developer hear our opinion about the need of full 64bit AU support
2) Get an Apple engineer over to PACE and help them get their sh... together.

Justin, it seem that you have more knowledge regarding the under the hood stuff than I do and I appreciate your clarification.
However there are two things that I still can't understand:
1) Spectrasonics, VSL, Kontakt all that works amazingly good already in 64bit AU considering the amount of time they had with such a major shift. Even EastWest claims that they are ready but waiting for the PACE guys. I don't argue with you that it is a simple task but those examples show that it is possible and I think those developers have the same careful considerations in mind that you explained. That leads to the next point:
2) Hesitation? 64bit support seemed to be the main demand from users regardless of the full understanding of the matter, at least to extend the 4GB barrier. There is no small market share. There is the market share that demands and needs it. Spectrasonics, VSL make professional products with a professional price tag. And I guess the majority of professional users that use those products feel the daily pain of the 4GB memory limitation in the 32bit environment, not a kid that tinkers with Garageband after school. If the software developer for Ivory II at this moment still evaluating the priority of a 64bit AU plugin then I guess they live in a different universe if they don't realize that they targeting the same professional clients as Spectrasonics and VSL.
Again it is up to the (Logic Pro) users to give those developers a wake up call, Summer vacation over, let's get that stuff out before Christmas for Christ sake (so to speak).

MIDI note delay / stagger using Caps Lock keyboard and 3rd party plugins

Whenever I am using any of the following plugins:
Waldorf PPG Wave, Waldorf D-Pole or Audio Damage Reverence,
with the respective plugin windows open, I can hit several notes on the Caps Lock keyboard simultaneously and some of them will trigger after the rest.
Interestingly, Reverence and D-Pole are effects, and so placing them on any audio instrument, including those that came with Logic, causes them to behave as PPG Wave always does when its plugin window is open.
The delay time seems to be variable.
When the plugin windows are closed, there is no delay.
As well, triggering many notes at once or notes in quick succession seems to cause things to stagger up more.
Sometimes the MIDI notes get stuck and continue playing until they are pushed again.
This seems strange to me, as CPU usage on the plugins is extremely low (the CPU meter does not even register a single mark).
The problem does NOT occur if I draw out a MIDI sequence that does precisely the sort of things that cause the holdups when I am using the Caps Lock keyboard.
Is the Caps Lock keyboard just not very good at certain things?
Why would this problem occur only with these specific plugins?
None of Logic's included plugins have this problem (unless of course I stick Reverence or D-Pole on them as an insert and open the Reverence window).
Naturally this is an inconvenience that can be worked around, but it is annoying.
Thanks for your time.

Hey Rob,
I opened up the Activity Monitor, and CPU usage in Logic Express is 35-40% with the plugin window open and between 16-20% with it closed.
That doesn't seem to be it, but your suggestion that the Caps Lock keyboard is probably just not good at handling many notes at once is definitely correct.
I plugged in a MIDI keyboard and the CPU usage is the same, but there is no staggering problem.
Perhaps there is something off with the CPU meter in Logic Express 7, though.
The Audio side registers activity, but the CPU side says nothing, when clearly the Activity Monitor has it right.
Anyway, thank you for answering my question--it is sort of an annoying little problem, but I just won't play fast with Caps Lock, I suppose.
Vince

AWESOME: Compressor 2 and 3rd Party Plugins

Hi all
I must admit there was an unexpected amount of positive interest to my detailed post last week on using Compressor and Final Cut Pro in tandem to encode different media types.
As a result, I would like to share the results of some of the research we have been conducting over the last week with the community. This has been research with respect to Final Cut Pro 5, and its integrated Compressor 2 workflows.
Let me recap the reason for the research.
In my opinion, one of the most powerful things about QuickTime is that it is not a media format, but rather a media architecture. It has had extensibility considered as a pivotal feature, from a very early point in development.
QuickTime allows addition of different formats via way of modules. Third party developers can literally produce a module to allow QuickTime to export media of any kind of format, no matter how foreign or how proprietary.
Some of the more popular additional formats and plug-ins available today:
Real Media - use the free Real Media export plug-in - check out:
 -- http://www.realnetworks.com/products/realexport/
Windows Media Option #1 - Popwire's - check out:
 -- http://www.popwire.com/productinfo.php?productsid=7
Windows Media #2 - Flip4Mac - check out:
 -- http://flip4mac.com/
After download and installation, these plug-ins allow us to export from any QuickTime enabled application: including Final Cut Pro.
But the strange thing, for me at least, was that we could export using QuickTime conversion in Final Cut Pro, but not via Compressor. Compressor v1 did not support QuickTime Export Component Plug-Ins.
Many people, myself included, were bothered by the additional workflow required to output to third party QuickTime Export Component Plug-Ins. It meant that Compressor couldn't be trusted to do everything And, for me, it meant the unenviable task of having to re-install the bane of my life: Discreet Cleaner 6
I had so wished I could bid the old crusty girl good-bye
Without access to QuickTime Export Component Plug-Ins in Compressor 2, an even bigger issue arises, as Compressor 2 now has distributed processing! And as such there are definite differences in performance when making the choice to encode to another format from Final Cut Pro:
File > Export > Export via QuickTime Conversion -- same as usual
File > Export > Export via Compressor -- now supports distributed processing
So, on opening up the Compressor 2 documentation, I see with great joy:
Installing QuickTime Export Component Plug-Ins
The export component feature in Compressor was developed to make it possible to add additional export plug-ins in the future. You would simply install the third-party software and then choose the corresponding output file format from the Encoder Type pop-up menu in the QuickTime Export Components Encoder pane of the Inspector window.
That said, I immediately got into touch with the following, and sought their advice as to whether their plug-ins would be supported in Compressor 2:
Real Media
At the moment neither QuickTime 7 nor Mac OS X 10.4 Tiger is supported by the free Real Media export plug-in, but they are working on it and expect to release an update soon.
Popwire
Whilst they are currently working on an update to enable QuickTime 7 / Mac OS X 10.4 support, I did get the following prompt and courteous reply from Albert Bruhner at Popwire:
We don't have any official support for that [ie. integration with Compressor 2] today. You are welcome to download and try though. The WMV-9 Component is available as demo which you are welcome to try.
We will start testing this though. But we do have our Compression Master which wouldn't sell if we did plug-ins that did all that with other programs. So we don't have any priority to do that.
[Continued]

[Continued from post above]
Fair enough, and thank you Albert for the prompt post!
Flip4mac
A much more positive and promising, and equally prompt response here from Joyce Garrett:
Yes, we're happy to be able to tell you that Compressor 2 supports the Flip4mac product family. You might want to download the Trial version of the Flip4mac WMV Studio/Studio Pro to test it.
The Trial version will allow you to play back one-half the duration of the source file and export a 30 second WMV file. Once installed, you will be able to export WMV files from Compressor 2 to test the functionality.
I'm sure you'll be pleased with the results!
I am sure I will be too, Joyce! Thank you.
So there you have it:
WMV-9 can definitely be exported via Compressor and Flip4mac's plug-in
WMV-9 might be exported via Compressor and Popwire's plug-in
Real may one day be exported via Compressor and Real's plug-in
I am going to be conducting exhaustive testing on these over the next week, and if there is interest, I will report the results in terms of quality and performance.
For me, it is very exciting, as we will be able to produce presets and job templates with groups of each of these, and apply them to sequences we encode.
Imagine a one step encoding job for a HD sequence that does the following:
Encodes to a self contained SD DV movie in NTSC and PAL
Encodes 3 versions in QuickTime/H.264 (High, Med, Low bandwidth)
Encodes 3 versions to Real (High, Med, Low bandwidth)
Encodes 3 versions to WMV (High, Med, Low bandwidth)
Encodes MPEG-2 and AC-3 for SD DVD
Encodes HD H.264 and AC-3 for HD DVD
Encodes a mastering/archival self-contained version for in native HD
Just send the sequence to compressor, apply a job template, and begin rendering. And vest of all, Compressor now has the smarts to farm out that work to all the spare Macs in the studio
And no more Cleaner! More time for lunch!
Man I love it I think it is by far the most significant update to all the apps in FCP Studio
I hope everyone gets to benefit from these excellent changes.
In the meantime, i will commence testing, and will keep you all informed!
Regards
Peter

CS 5 and 3rd Party Plugins

Hi all,
is anyone knowing which Plugins are running and tested with Premiere CS5.
I know Boris Continum Complete and Spicemaster are running with CS5. Whats happened with Prodad and all others ?
Thanks for information.
Greets
Werner

...hmmm, just wondering that there is no offical commitmend from Adobe which one are tested and running.
FYI: Pixelan has commited to me that Spicemaster PRo 2.5 runs with CS5. Also Boris FX.
greets
Werner

Flickering graphics in Logic - especially 3rd party plugins

I see a lot of people reporting (myself included) "flickering" of graphics in Logic, especially in 3rd party plugins so I decided to post a video of it occurring. Is this a "known issue"? I will be reporting it to Apple, and I hope everyone else experiencing it will do the same. Please watch the video and provide any input that you might have. Thanks!
https://youtu.be/y_G0Q8J2Egw

Hi Clancy,
Could it be related to a Retina display?
Possibly... but as you know, I cannot test for that as i don't have a Retina display... (and frankly I'm not sure I want one at this time ) and I could recreate it on a standard screen using the same 3rd party plugin as the OP used... so i think it isn't specifically a Retina issue but... maybe retina 'enhances' the problem because of the extra load placed on the Graphical hardware/routines
So...
Is the OP is using a Retina display with his Mac Pro?
I suspect however, given the video he posted, demonstrating the issue occurring with the PSP MasterQ2 plugin...that it's only happening with some 3rd party plugins.... (as again he stated "especially with 3rd party plugins" which really might mean... only with.. depending on how you 'translate' that) and therefore my comments earlier.
Finally while the number of posts about this issue is actually rather small ( as far as i can determine from some detailed searching at least).... the thread on GS seems to indicate it's been going on since early versions of LPX and is related to Yosemite rather than LPX itself...
https://www.gearslutz.com/board/logic-pro-x/987219-logic-10-1-0-crazy-flashing-g raphics-plugins.html
...and some people have been reporting the same sort of flickering issues with other 3rd party apps and also plugins for apps like Aperture for example... after upgrading to 10.10... again indicating its a general Yosemite issue rather than a specific app issue.

Logic 8 and 3rd party plugins after upgrade

Similar Messages

Maybe you are looking for