Plug-Ins Working On Input(Incoming) Single?

Hey all, just wanted to know if i applied a plug-in,say a compressor to my incoming vocal signal,is that effect a pre effect?..Is the compressor working and getting recorded with the incoming signal or are all the plug-ins an after effect?

You could try turning it off. That would prove whether it's being recorded or not.
But I can tell you it is not being recorded.

Similar Messages

Do Bombfactory Plug-ins work with STP?

Do Bombfactory or Waves plug-ins work with STP? I'm particularly hoping the Bombfactory ones do. Thanks.

Waves plugins work since they're available as AudioUnits. Bombfactory won't work because they're only RTAS.

TUTORIAL: How to make PPC Plug-Ins work on Intel Macs!

Hi guys, I wanted to share this brillant method with you all, collect ideas and create a list of Plug-Ins, you have succeeded to make work (I guess nearly all PPc Plugs will work this way but lets better stick to facts). Maybe there is a way to work with more than 1 Plug - Feel free to report and contribute! Kudos goes to a dear friend of mine... Let' share some power...
"I noticed some people complaining about not being able to use Trilogy and Atmosphere on Intel Macs. There's a tricky way to do it that takes about ten minutes to set up the first time and after that is easy. It probably works for other PPC-only instruments as well.
Here's the outline: OSX for Intel contains a layer called Rosetta, which runs PPC software that hasn't been updated. (You might run Microsoft Word via Rosetta and not even know it.) In general, Rosetta is no good for audio software: you can't use it for a sequencer or a recording application. But it's good enough for a lightweight plugin host like Rax, which does nothing but serve as a host for Atmosphere. So you can load Atmosphere into Rax via Rosetta, then run it alongside a UB sequencer like Live or Logic.
The only tricky part is connecting the two together. You need to get MIDI out of your sequencer and into Rax, and you need to get audio out of Rax and back into the sequencer. The MIDI can go via an internal IAC bus. The audio can go via the handy freeware audio-routing utility Soundflower.
Here's how to set up:
-- download Rax version 1.2.3. (Version 2 and up won't work.) You can find it at http://macmusic.org/software/view.php?id=395 . Use the serial in SerialBox to install.
-- download and install Soundflower from http://www.cycling74.com/downloads/soundflower
-- in Audio MIDI Setup, create a new IAC bus. Instructions on how to do this are at http://www.spectrasonics.net/news/Creating-an-IAC-Bus.html . Name it Rhino. (You can name it whatever you want, but in these instructions I'm going to call it Rhino.)
Now you're ready to go.
-- Open your sequencer and create a MIDI track and an audio track. Set the MIDI track's output to Rhino. Set the audio track's input to Soundflower 2ch.
-- Open Rax and load Atmosphere. In the Preferences, go to the Audio tab and set Audio Device to Soundflower 2ch. Now go to the MIDI tab and, under MIDI Inputs, make sure Rhino is the only thing checked.
You should now be able to send MIDI from your sequencer to Atmosphere, and then hear the audio through the sequencer. One last stage is to sync Atmosphere to your sequencer's MIDI clock, so that tempo-synched effects will work properly.
-- Still in Rax Preferences, on the MIDI tab, set the MIDI Clock dropdown menu to Rhino. Close the Preferences window. At the top of the main Rax window, make sure the Ext. Sync box is checked. The Tempo window should say 0, which means Rax is following the sequencer's master tempo.
And you're done. Save the Rax document and you can open Atmosphere with a single click. Trilogy works the exact same way, obviously.
If you want to use multiple instruments from Rax, you'll need to use SoundFlower 16ch and send MIDI on a different MIDI channel for each instrument (using the same IAC bus).
Anyone who's tried this, please post your results in this thread. Especially, try out other PPC instruments, and try using multiple instruments at the same time, and let us know how it works for you."
Maybe one of the Admins wants to sticky this
With my very best,
Vic.

There's another shortcut I've used successfully in order to access 'old' PlugIns on an Intel MBP :
Just use Logic 6 - and take full advantage o' that ole rotatin' rosetta
Meaning : Other than with native Logic versions 7 and 8, Logic 6 has to be fully emulated by the rosetta engine, and if your intel mac is fast enough, it does so very well - thus including all PPC PlugIns you still may have installed. Also works fine for PlugIns that were converted via FXpansion's VST-AU manager.

My Photoshop Elements 6.0 suddenly can't download plug-ins to read input from my cf photo card, or s

My Photoshop Ele
ments 6.0 suddenly stopped loading ph
otos from my CF Card with the message that it could not download
plug-ins to read the device. It al
ways worked before. Would it help to re-install Elements, or should I look for a way to download the Plug-in. Don't even know what it is called. Thanks

When you browse to Computer is your CF card shown as a removable drive?
If not try shutting down the computer and re-starting and then inserting the CF card or plugging in the USB again.
Open Elements Organizer and press Ctrl+G to bring up the downloader and under Source click refresh to locate your CF card.

1) More clip art? 2) Do plug-ins work in CS55?

1) Is there more clip art or is it the same batch that was in PrE9?
2) Does the 64-bit version have 64 bit plug-ins that will work in PrPro CS55?
cheers,
Petey

Hi Hunt,
I guess I was wondering if the PrE9/10 clip art is actually installed on the hard drive or embedded into a DLL library and one can only see it within the program, then export it.
SORRY.... I JUST FOUND IT ON MY HD..... it's PNG FORMAT.... no problem.
thanks...
cheerio,
Petey

I can not make visualizer plug-ins work in iTunes

I did a search and I did not see anything helpful.
I am using an up-to-date version of iTunes with no other plug-ins installed.
I have followed the instructions on this plug-in:
http://www.dr-lex.34sp.com/software/spectrograph.html (updated 12-06)
I know of other people that have had no problems getting it to work. I have reopened and closed iTunes, rebooted my machine several times, nothing.
If anyone else can point out a spectograph plug-in that might work, help is appreciated.

As an update, the plug-in installed perfectly fine, and it works on my MacBook Pro. So I tried moving the .bundle package from my MacBook Pro to my Mac Pro.
Upon moving it to my Mac Pro, the icon changed from the normal iTunes .bundle icon to a normal folder. It also behaved like a normal folder. Double-clicking opened up the contents. And the plug-in still didn't work.
So the breakdown here:
MacBook Pro - Plug-in works fine.
Mac Pro - When the .bundle was moved from MBP to MP, it turned right into a folder, not a bundle, and all attempts to turn it into a bundle failed.
Any idea what is going on here?

How to make my NIK LR/CS4 plug-ins work on Aperture

I'm new to Aperture and I absolutely love it (so far). I also have Lr and PS CS4, for which I have NIK Color effex and Sharpener Pro plug-ins. I went to NIK website and downloaded their plug-ins for Aperture, but they do not take the products keys that came with my LR/CS4 versions. I cannot believe that I would have to pay twice for using the same Nik software on 2 different apps on the same iMac. Does anyone know what I should do to make these Nik programs also run with Aperture ?
Thanks for help ! Frederic

fredericpaeps wrote:
figure out how to work in 32 bit mode
Frederic,
I found the NIK people as well as the Topaz people to be very responsive and helpful.
Actually, it seems to me that the 32/64-bit thing pretty much takes care of itself.
These are my observations and I do not profess to be an expert.
First- If you have a 64-bit computer Aperture 3 will open in 64-bit WITHOUT any extra effort on your part.
Second- When you wish to use one of the NIK plug-ins you will be told the software needs to close and reopen Aperture in 32-bit mode. Click OK and that happens.
I have yet to see any difference in Aperture whether in 32 or 64 bit mod but if I am not planning to use the plug-ins soon I quit and reopen Aperture just in case there is some benefit to 64-bit I have not yet discovered.
Jerry

Will my Komplete 8 plug-ins work in Logic X

I'm looking to buy Logic Pro X to work in an environment with Ableton Live 9 and Komplete 8 with Maschine Mk2. I notice that Logic Pro X is 64 bit only and I know I can download the Ableton Live 64 bit but I am a bit unsure as to which ( if any) of my Komplete 8 plug ins will work or are they all 32 bit?
Thanks
JT

The plugins in Komplete 8 are all 64bit compatible if you have the latest versions of them.

CS2 Plug-Ins Works in CS3 ?.

Dear All,
Here I have created the Small Plug-Ins in CS2, Is it Possible to work in CS3?...
Could you please give me the Great Solutions...
Yes! I have created the "Anchored Id" generation Plug-Ins... Its most useful for us....
So Is it Possible to use the same plug-Ins in CS3? or We are able to create another one in CS3?.
Thanks & Regards
T.R.Harihara SudhaN

Dear Patrick Perroud
Many thanks for your kind Reply.
HTH is mean = Head to Head...?. or Else.
Yah! I saw the Porting Guide of CS3. They said, Some of Headings, Strings, Overlap Manager, ITextFrame Replaced, Scripting and etc....
So, I can open my CS2 SDK code and change as per the CS3 code after that it will run... Is it Correct?...
Please could your please give me the suggestion..
Thanks & Regards
T.R.Harihara SudhaN

Will old plug-ins work with 64bit CS4?

Will my 32bit CS3 plug-ins (Neat Image, etc) work with CS4? Also, will CS3 actions and scripts work in CS4?

>and he's always around and responsive when an issue pops up.
Then he should discover how to join the Adobe Solutions Network and get access to the development program. Adobe can't go out and scour the bushes to find people to invite (although they try). It's up to the developer to come to Adobe to get help. And, while Adobe DID require people to join ASN for a fee to get the CS2 SDK, that was changed for CS3 (and will be the same for CS4 as far as I know). And yes, to get the beta SDK one DOES have to sign an NDA...DOH!
So, one can sit on the sidelines and piss&moan about lack of access to the SDK or, if one is a "legitimate" (meaning somebody or company that is doing this for a living and NEEDS the SDK for a product that compliments Photoshop), then it's THEIR responsibility to go out and find out what they need to do to get the SDK that they need. Posting in a public forum about not being able to get the SDK isn't the way a "legitimate" developer would go about trying to get the info they need.

Why won't my plug ins work?

After finding that my Nik plug ins were not compatible with Elements 12 I reinstalled Elements 9. However, whilst the filters can be used the resulting image can not be saved. I press the ok button and nothing.

I don't know anything about PSE9 so I can't help you there. However, PSE12 is the latest version and why do you say your plugin doesn't work?
First you need to do is go to:
Help >> Updates
This should update the camera raw plugins for all new cameras since the product was released last September 2013.
Have you done this? If not do it now and post back to tell us what these plugins are that aren't working in PSE9 or are not compatible with PSE12.
Good luck.

Would my plug-ins work in Logic 7.2 and intel mac?

This may be a dumb question but would my plug-ins that work in Logic 7.1 on my Powerbook work in Logic 7.2 on an intel mac?

The statement I made is not a "blanket" one, if one is looking at the big picture.
I understand why you would consider that a blanket statement, since you are narrowly looking only at one angle.
The user did not state that this is the only reason he is getting a computer, and he did not specify that he is using the computer ONLY for Logic, and therefore, it is wise to consider all options.
In what way was my comment narrow?
Everyone's situation is different depending on what software, plugins and peripherals are used. Making a recommendation based on months makes no sense since someone's software may be ready much sooner than that, or may be available even later.
The decision to upgrade should be based on whether the things you need to run are ready or not. Doing it this way considers all options, picking a number of months out of a hat is narrowly looking at one angle.

Will PSE3 Third Party Plug-Ins Work On My New iMac ?

Over the past 5+ years I have accumulated quite a few third party plug-ins for both PSE2 and PSE3 running on my Apple eMac G4.
I will shortly be taking delivery of a new Intel based iMac,and whilst previous posts on this forum show that I can run PSE3 on the new machine,what about the third party plug-ins ?
I will be installing PSE3 on the iMac using the original discs,and, if I can use them,do I just 'migrate' the plug-ins using the Apple Migration Assistant - or what ?

It depends. Some can be transferred that way, but some require their own installer.
EDIT If you have the installer, use it. If not, you won't be any worse off if you try manually moving them. Incidentally, I'm assuming you're talking about true plug-ins (.plugin files) and not about actions and such, which can be moved, but go to very different places in PSE 6.

Since updating to 10.5.7 none of my Syncrosoft protected plug ins work.

I tried switching USB ports.
I tried downloading and re-installing the latest license control center.
Bee Jay, Justin C anybody?
Korg Legacy Collection, Rob Papen, Arturia, all use syncrosoft
Looked at thrie Web site.. nothing...
Heeeeelllllpppppp

Might be a power issue - Macs (especially laptops, not sure so much about the Mac Pros) have two USB busses - one dedicated to external USB devices only, and the second one which is shared with all the internal things sitting on the bus (eg webcam, keyboard etc etc).
This can cause some issues with devices that draw too much power (wouldn't have thought the key would, but it might just be picky.)

VI Search Path not working in LV2011 for VI Server Plug-ins with exe

I have found what seems to be a problem with the search path when a LabVIEW 2011 built executable calls a Plug-in VI.
When the plug-in VI has subVI’s from vi.lib on its diagram the executable has to know where to find them. Not all VI’s in vi.lib are part of the run time engine or the dll’s that may get generated as part of the build. The things you have to do to make plug-ins work for an executable are explained in several Developer Zone articles. The article titled “How Can I Change or Set the VI Search Path for LabVIEW Executables” describes the ini file setting viSearchPath. When this is set to the vi.lib directory I have not encountered problems with previous versions up to and including LabVIEW 2010.
I have come across an example in LabVIEW 2011 where it doesn’t work. I have attached an example (I am using LV2011 SP1). It demonstrates the basic plug-in architecture. Everything works in the development environment. But it doesn’t work from a built exe. I haven’t included the actual built exe in the zip file in case that causes a problem downloading it. If you run the build spec from the src directory project file the exe should get generated in the bld directory. The problem appears to occur when certain VIs from the analysis library are in the Plug-in. In the example attached, the Plug-in VI is very simple but I have placed the troublesome SubVI on the diagram. The VI in this example where there is a problem finding it is the Butterworth Filter VI. I have placed it on the diagram in a conditional disable structure so it is easy to enable and disable. When enabled and you run the test Plug-in VI the error 1003 is raised, meaning a subVI cannot be found in the dynamically called VI (for example see this post). Note that a way round this may be to incorporate the Plug-in VI into the built exe but this shouldn't be necessary. It’s not a problem with this specific filter VI, as it occurs for other VIs I try on the diagram. However if you place an FFT VI on the diagram there is no problem. I suspect that one is built into the Run-Time Engine.
I also note I am running Win7 64 bit and 32 bit LabVIEW (note the relevant viSearchPath in the ini file – you may need to change if you are on different version of Windows). If the example is converted to LabVIEW 2010 everything works as expected for the built exe. I tried that on a colleague’s computer running XP and 2010 but I am pretty sure in still also works on Win 7.
Things I am suspicious of are that the analysis VI’s are part of a LabVIEW library (lvlib) and perhaps something has changed there? I understand there is a problem with OOP in LabVIEW 2011. Perhaps it is related to that as that seems to be an issue in 2011 (see this Discussion Forum post). Perhaps it is related to OS version?
I also tried generating a Source Distribution to extract out all the vi.lib VI’s and place them directly in the Plug-in directory. That didn’t help.
Interested in whether anyone else reproduces this behaviour. In any case something is different in 2011.
Attachments:
LV 2011 test Plug-in.zip ‏42 KB

I found some more out about this issue working with my local NI rep here in Australia. Apparently something has changed in the compiler between LabVIEW 2010 and 2011. Using the viSearchPath token in the ini file, as described in various Developer Zone articles, now guarantees that the Plug-in will not work. The only way to make it work appears to be to create a Source Distribution. I noted in my original post that I had already tried this and it would not work. It turns out that having the viSearchPath token in the ini file when using a Source Distribution causes the error 1003 to occur. When the token is taken out of the ini file the Plug-in (containing an analysis VI) with a Source Distribution works - in the simple example I posted.
Well I then found its a bit more complicated than this. It all worked for the simple example I posted. Recall we found the error when there was an analysis VI in the Plug-in VI. In our actual application (which is a large one) that calls Plug-ins - we still got the error 1003. By trial and error I found a workaround. There are certain Build Spec settings for the calling exe that I set and found worked. On the Additional Exclusions page I found that I had to make sure that I left unchecked "Modify Project Library File after removing unused members". I've always had trouble understanding the need for this setting. In the Build Spec Help on that page it notes that the build will take longer. In most builds you remove polymorphic VI instances, remove unused members of Project libraries and also Modify the project library file after removing the instances (this is a sub setting of the previous). This makes the exe smaller in size and a quicker build time. Obviously modifying the project library caused a problem. In the big application exe calling Plug-in, I probably have the same analysis VI on the diagram (I haven't actually checked and also whether it is the same polymorphic instance) and in the simple example I posted I definitely did not have VI in the calling exe example - so there may be some clue there. I should try putting the same analysis VI on the calling exe diagram in the simple example to see what happens but I'm running out of energy on this one :-(
So none of this gives me much confidence and I wish I could get a better explanation from NI regarding this behaviour to be sure I am not going to encounter a different problem for different calling exe and Plug-ins. I was advised that a CAR would be issued. Perhaps this is now expected behaviour for 2011 but it would helpful if some definitive explanation could be given about what has changed from LV2010. And an update of Developer Zone articles on the subject would be helpful.

Plug-Ins Working On Input(Incoming) Single?

Similar Messages

Maybe you are looking for