acid pro 6?

Audio Plugin Hosts and other audio software applications discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

sounds like its a directx plug.

Post

Igor 4000 wrote:I have an interesting issue with AP6. When I'm scanning my VSTi folder, I know exactly which plug crashes it. The problem is that I have no idea what this VSTi is, and I can't seem to find it anywhere :bang:

Anyone know how I can find a plug on my pc by name so that I can delete it? It doesn't seem to be in my VSTi folder.
Hmmm...if the plug is not in your VST/VSTi folder then ACID won't scan it. Unless you've added another VST/VSTi path to the VST/VSTi options in ACID. It must be one of the plugins in the folders that ACID is scanning.

Post

Igor 4000 wrote:I have an interesting issue with AP6. When I'm scanning my VSTi folder, I know exactly which plug crashes it. The problem is that I have no idea what this VSTi is, and I can't seem to find it anywhere :bang:

Anyone know how I can find a plug on my pc by name so that I can delete it? It doesn't seem to be in my VSTi folder.
I use PowerDesk Pro, but you can do a search in Windows Explorer. Just click on search, select "All Files and Folders," enter the name in the "All or part of the file name" box, and then in "Look in:", select "Local Hard Drives." BTW, if it's a DirectX plug-in, there is a utility called DirectX Uninstaller. It's a freeware utility you can find with a google search. It will list every DirectX plug-in installed on your computer. You don't have to delete anything. You can just look and see what's installed. If you are sure you don't a particular plug-in installed, DX Uninstaller can delete it from your registry immediately. It's safe and I have been using it for many years.

Post

I personally am not even upgrading to 6, after trying out sonar i'm hooked, so i'm saving up for that instead. Way easier to work with than Acid ever was.
"You are going to let the fear of poverty govern your life and your reward will be that you will eat, but you will not live."

Post

bnmoore wrote:
bduffy wrote: It's almost as cool as Apple forcing you to install iTunes just to use Quicktime - even if it's the "Pro" version. F***ing criminal, man.
Even with Quicktime 7 (Pro) you can still download the stand-alone installer. It's kept up to date. I don't have iTunes installed here. It takes your reg code just fine.
Yeah, Apple doesn't completely hide the stand-alone version but one has to be aware of its existence and actually seek it out because Apple just wants to have everyone hooked up to an iPod like it was a freakin' morphine drip! 8)
aMUSEd wrote:If you don't install the manager can you get away with not installing NET too? (whatever NET is)
I haven't tried the ACID demo yet but I know that Vegas flat-out won't launch without the .NET Framework... Sound Forge will run but you'll just get an error on startup telling you that some script or another won't load... but anyway if you don't want to mess around with installing .NET Framework v1.1, Service Pack 1 and the ASP patch separately, this guy has a pre-updated/patched version of v1.1 on his website...

http://ryanvm.msfn.org/

(Like arke and others have said, v1.1 and v2.0 are different beasts; you gotta use v1.1) I took a chance and installed RyanVM's modified version instead of the individual Microsoft releases and I haven't had anything go wrong with my computer... but I'm still keeping my fingers crossed (although I Googled around a bit and deemed the "hack" to be safe...)

Post

SonyPCH wrote:
Hold down the Shift Key and when you move the mouse over the envelope line, draw away.

By default, the drawn curve will be thinned. To disable this, go to the Prefs "External Control & Automation" page and uncheck

"Smooth and thin automation data afeter recording or drawing"
Thanks Peter :) That sound great, just don't tell me this was already available in Acid 4 :lol:

Post

munchkin wrote:
Igor 4000 wrote:I have an interesting issue with AP6. When I'm scanning my VSTi folder, I know exactly which plug crashes it. The problem is that I have no idea what this VSTi is, and I can't seem to find it anywhere :bang:

Anyone know how I can find a plug on my pc by name so that I can delete it? It doesn't seem to be in my VSTi folder.
Hmmm...if the plug is not in your VST/VSTi folder then ACID won't scan it. Unless you've added another VST/VSTi path to the VST/VSTi options in ACID. It must be one of the plugins in the folders that ACID is scanning.
I experienced something similar, both with v4 and now v6. The prefs set "program files\vstplugins" as the only directory for effects and synths. However, I can see all sorts of audio codecs (installed with nero, divx and whatnot, and definitely not in the vstplugins folder) among my effects. Naturally, they cannot be loaded, but their being there doesn't crash Acid either, so I don't mind. I've just renamed them to zzz##, so I don't have to look at them...

Post

I ended up fixing this in the way that someone previously suggested. I basically moved .dll files until I found the one that was causing the problem and got rid of it. The funny thing is that Acid scanned it under a different name (for whatever reason) so it was difficult to locate.

On another note...does AP6 have beatslicing capability? But that I mean slicing up a beat and being able to rearrange slices. I've been browsing the manual and although Acid has Beatmapper and Chopper, that doesn't seem to be their functionality.

Post

cloudspine wrote:
munchkin wrote:
Igor 4000 wrote:I have an interesting issue with AP6. When I'm scanning my VSTi folder, I know exactly which plug crashes it. The problem is that I have no idea what this VSTi is, and I can't seem to find it anywhere :bang:

Anyone know how I can find a plug on my pc by name so that I can delete it? It doesn't seem to be in my VSTi folder.
Hmmm...if the plug is not in your VST/VSTi folder then ACID won't scan it. Unless you've added another VST/VSTi path to the VST/VSTi options in ACID. It must be one of the plugins in the folders that ACID is scanning.
I experienced something similar, both with v4 and now v6. The prefs set "program files\vstplugins" as the only directory for effects and synths. However, I can see all sorts of audio codecs (installed with nero, divx and whatnot, and definitely not in the vstplugins folder) among my effects. Naturally, they cannot be loaded, but their being there doesn't crash Acid either, so I don't mind. I've just renamed them to zzz##, so I don't have to look at them...
I just create a folder called "unused" and shove them all in that...same here too...nero this, divx that. At least it's not as bad as flstudio, i think that lists every dx plug on your comp :lol:

Post

grymmjack wrote:
ModuLR wrote:I tried demo of Acid 6 and after finding out that DX-10, Wasp, and SimSynth (imageline plugs) were culprits for crash on scan, and removing them temporarily for evaluation of the demo, I tried to load CM-101 up, and POOF no more acid, it just POOF went away.
Are those all GUI'less plugins?

Post

The cm101 problem isn't acid related btw.

Image

Post

Acid 6 has a confirmed bug that affects VST song position pointers. All plugins that use it are affected, including Jamstix which cannot synch with Acid without this info. According to Sony, this will be fixed in the next update.

AudioM8 should work fine. Reubs, what exactly is happening (or not happening) for you with it?
Ralph Zeuner
rayzoon technologies
http://www.rayzoon.com

Post

Zauni wrote:Acid 6 has a confirmed bug that affects VST song position pointers. All plugins that use it are affected, including Jamstix which cannot synch with Acid without this info. According to Sony, this will be fixed in the next update.

AudioM8 should work fine. Reubs, what exactly is happening (or not happening) for you with it?
Great news that btw (i'm not a jamstix user, but for other people i mean.) They really should use more devs as bug/beta testers (asuming devs would be interested? that's another issue i guess.)

Post

arke wrote:
Bassballjg wrote: This cannot be emphasized enough. Sound Forge absolutely, categorically refused to work properly with 2.0, and consistantly demanded 1.1 of .NET Framework at launch. The Sony software is definitely locked into something about 1.1 that is different than 2.0.
.NET 2.0 is not backwards compatible with .NET 1.1 (and for a good reason too).

And by the way, theres nothing wrong with .NET at all - it encourages and enforces better practices and methods from a programmers perspective to make better applications. And it doesn't take that much overhead (a fraction of Javas overhead).
Not that there's anything wrong with .NET Framework per say, but my specific problem from another thread was that 1.1 will not install on my internet machine, from which I still plan to do some audio work servicing products for dangerousbear.com, and SF8 needs 1.1 and won't work with 2.0 which does install on this machine. So my solution is to use SF8 on my new DAW-only machine on which I have successfully installed .NET Framework 1.1, and stick with 7 on the web box. I only wanted to emphasize that there is a relevant difference between the two, something that is not necessarily intuitive if you're non-computer savvy like me. This knowledge will be helpful when and if I upgrade to Acid 6.

Post

nlamartina wrote:
grymmjack wrote:
ModuLR wrote:I tried demo of Acid 6 and after finding out that DX-10, Wasp, and SimSynth (imageline plugs) were culprits for crash on scan, and removing them temporarily for evaluation of the demo, I tried to load CM-101 up, and POOF no more acid, it just POOF went away.
Are those all GUI'less plugins?
No. They all have UI's.

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”