Why are all the best free/cheap plugins windows only?

[mrfracas]

dblue Glitch? Daft Funk? Two awesome plugs that I just can't find equals for on the Mac.

This doesn't bode well for my live performances.

I've yet to test out Audio Damage's Automaton; but is it really on a par with Glitch?

Can anyone show me a Mac alternative to Klang Labs's Daft Funk glitch accelerator?

[mutilatedlip]

I'd say Automaton is by far the most complex and best 'glitch' plug-in there is out there.

I love it. However, I must confess that a lot of the results are random, as I haven't quite got my head around the cell programming as yet.

Still, I'm happy!

[Monarch]

Originally Posted by mrfracas

dblue Glitch? Daft Funk? Two awesome plugs that I just can't find equals for on the Mac.

I think the reason there are so many more free and/or cheaper plugins on Windows is because of Windows OS market share. A dev. will very likely start a project based on the potential customer base. It will be much larger on Windows.

I've yet to test out Audio Damage's Automaton; but is it really on a par with Glitch?

I have used Glitch and between Replicant and Automaton your needs should be covered IMO.

While Audio damage do not offer demos...they do IIRC offer money back guarantees. I think it is 7-14 days or similar.

If you have not seen these videos already have a look at the following...

Replicant Overview and tips

Automaton Part 1

Automation Part 2

HTH

[sijarvis]

Greenoak Crystal is a very well spec'd freebie VST and AU softsynth.

Download it here: Crystal VST Instrument

It's multi-timbral, PC and Mac ready.

Sounds good too.

[tyronehowe]

Not sure why - but I've noticed this too.

Maybe it's because AUs are harder to program than VSTs?

No that can't be right because there are fewer Mac free VST plug-ins as well.

This used to bother me but not so much now. Think I realised that it is more the quality of the plugins that's important (and generally you have to pay for quality).

[cane creek]

Originally Posted by tyronehowe

Not sure why - but I've noticed this too.

Maybe it's because AUs are harder to program than VSTs?

No that can't be right because there are fewer Mac free VST plug-ins as well.

This used to bother me but not so much now. Think I realised that it is more the quality of the plugins that's important (and generally you have to pay for quality).

I would assume its because theres more PC owners than mac owners outhere hence more PC programers and if you make free AU plugins theres only Logic & DP owners that can use them where as VST is run on many hosts catering for more users making Logic owners like myself more of a specialised market.

[tyronehowe]

Originally Posted by cane creek

I would assume its because theres more PC owners than mac owners outhere hence more PC programers and if you make free AU plugins theres only Logic & DP owners that can use them where as VST is run on many hosts catering for more users making Logic owners like myself more of a specialised market.

Yup - that makes sense to me. And DP6 is having problems running certain AUs at the moment.

[EdRyan]

Programming a VST and Au are actually pretty similar.

Before the invention of Core audio and AU, Apple used to run plugs on VST2.

The coding underneath in either format is quite close, you just have to relate commands for CoreAudio and ASIO.

The real pain in the arse is the way that each platform handles there gui.

For that reason, I was told it's good advice to basically break the program in 1/2. I part audio process the other gui/front end code. It makes it a lot easier to port over later..

I've done a VST (it didn't do anything fancy. It was just a gain) but not done an AU. It's next on the list...

[tyronehowe]

Originally Posted by EdRyan

Programming a VST and Au are actually pretty similar.

Before the invention of Core audio and AU, Apple used to run plugs on VST2.

The coding underneath in either format is quite close, you just have to relate commands for CoreAudio and ASIO.

The real pain in the arse is the way that each platform handles there gui.

For that reason, I was told it's good advice to basically break the program in 1/2. I part audio process the other gui/front end code. It makes it a lot easier to port over later..

I've done a VST (it didn't do anything fancy. It was just a gain) but not done an AU. It's next on the list...

Ah ok – I didn’t know that. I’m originally a computer programmer by trade and have occasionally thought about delving into writing a VST/AU. I even downloaded the VST 2 SDK from Steinberg (and for some odd reason, they would only ever let you download it once, so don’t lose it!) But because I’m a lazy git, I’ve never actually looked at it.