# Get Busy, Y'all...

- Site: Analog Industries
- Author: Chris Randall
- Date: 2011-05-16
- URL: https://analogindustries.com/2011/05/get-busy-yall/

[![Get Busy, Y'all...](https://analogindustries.com/images/ext/farm6.static.flickr.com/5094/5724267293_529d881a44.jpg)](http://www.flickr.com/photos/chrisrandall/5724267293/)

'Tis the season, apparently. While it may seem that little is emanating forth from the various Audio Damage facilities, that's about to change. We'll have at least two additions to the store in the near future, possibly three. One is a new utilitarian plug-in and two aren't. Neither are they Euro modules. Or anything that plugs in at all.

After these three releases occur, we're gonna lay in to the Dubstation 64-bit update, and make an attempt at some of the problems plaguing the 64-bit Logic side of things (fucking Logic.)

So anyhow, you can expect a lot of AD news in the next few days as we roll these things out. We'll also be updating the store, so we'll be offline for a while (most likely tomorrow), so don't freak out if you see that.

And finally, as you can see from the photo above, I finally got a proper photo scanner to replace my dead all-in-one. I picked up one of [these bad boys](http://www.amazon.com/gp/product/B002OEBMRU/ref=as_li_ss_tl?ie=UTF8&tag=analogindustr-20&linkCode=as2&camp=217145&creative=399349&creativeASIN=B002OEBMRU). Two thumbs way up. If you have film to scan, you need this, plain and simple.

## Comments (28)

**bleen** (2011-05-16):

Geddy Lee....

**VSTJuNkiE** (2011-05-16):

You def don't look 6 foot + tall in *that* picture Chris...

**boobs** (2011-05-16):

those rice crispy treats he's standing on sure are grey.

**myrnaloy** (2011-05-16):

and what of the Euro module(s) - are we close?

**Chris Randall** (2011-05-16):

@myrnaloy: No news on that until June, sorry.

-CR

**MrMZ** (2011-05-17):

Fresh Gundam.

All mine are in storage.

: (

**analogcre8or** (2011-05-17):

Thanks for fucking Logic in 64!

**wquoyle** (2011-05-17):

And then you can start porting stuff to ARM, http://www.reghardware.com/2011/05/06/apple_arm_laptops/

;)

**Chris Randall** (2011-05-17):

Well, it's been almost 4 years since we had to recompile everything for a new CPU on the Apple side. If we're extra lucky, the next version of Logic (if there ever is a next version; my money's on "nope") will have a new plug-in format to go with it.

I will mention once again, at the risk of belaboring the obvious, that the very first plug-in we created, Fuzz+, still runs fine on all Windows machines, in all Windows DAWs, nearly 8 years later. While I use a Mac for almost all of my interfacing with the outside world, when it comes to music, Macs fucking blow.

-CR

**puffer** (2011-05-17):

I will point out that I'm still having an interface issue with the new Discord in Sonar 8.5/XP, where the minute audio starts passing through it I can't adjust the numeric displays. So, shit can suck over here, too.

**puffer** (2011-05-17):

Fucking Sonar.

**DBM** (2011-05-18):

I don't see Mac's going ARM . It just does't beat Intel's chips for sheer power .... so no worries I think . Though I can agree with the article and see a next mac book air kind of thing with one .... think more like iPad XL though .

**7point62** (2011-05-18):

I've been thinking about buying a better scanner, so the recommendation is welcome. Just one thing: the Amazon US price is $199 and the Amazon UK price is £209, or about $340 US. Hmmm...

**Peppe** (2011-05-18):

Effing Logic, indeed.

I'm still struggling to make some 64-bit plugs work properly on my Mac Pro. Alas, they're still in 32-bit dept. in my Logic. Tried literally everything, won't validate in 64-bit due to some error. On the other hand, on my laptop they're perfectly fine. Both are running Snow Leopard.

Does anyone have any good advice, by the way?

**bleen** (2011-05-18):

@ Peppe - restart your computer and then try scanning the 64-bit ones in Logic. I've run into the same issue and a hard restart did the trick.

**Chris Randall** (2011-05-18):

Yeah, for some reason we can't discerne, some computers won't immediately auth the 64-bit versions. We haven't come up with a solution for this issue that is any more sophisticated than "keep trying, using the usual methods, and it will eventually work."

If you follow me on Twitter, this particular issue is the source of most of my "Fucking Logic" tweets. Explaining it over and over again is apparently my cross to bear.

I have one guy with two computers, identical in every way (his project involves two people in separate locations using the same system). They are two MacBook Pros that have exactly the same OSX and the same version of Logic, were purchased at the same time, and even have the same user account setups. They are, other than the system identifiers and MAC addresses, the same computer. On one of them, the 64-bit versions authed no problem at all, and on the other, we haven't, as yet, got the 64-bit versions to pass validation. There is _no_ earthly reason for this, other than the fact that the AU validation process is hanging on by a very thin thread.

Welcome to my day.

-CR

**Peppe** (2011-05-20):

Bleen: Tried that the next minute I figured out they weren't authorized. Didn't work. I've also fixed permissions, reinstalled, cleaned all caches, rescanned all my hundreds of plugins in 32 and/or 64 bits, installed an earlier version then newest again, literally everything three times - if something's missing, let me know. :-/

It really bothers me as Eos is one of my all-time favorite plugins. Not to mention the others, but Eos is used in every project.

**seancostello** (2011-05-20):

I've had customers report mysterious behavior in Logic. On my end, Logic seems to cache the previous state of a plugin, so updating the plugin results in weird changes.

I don't even bother trying to build 32/64 bit Universal Binaries. I have a dedicated 32 bit build (for Intel and PPC, although I'm tempted to drop PPC for future plugins), and a dedicated 64 bit build. The .components have different names, with the 64 bit one having AU64 at the end. Both .components have the same internal names. I haven't had any conflicts in Logic with this approach.

Of course, additional OSX builds is a pain. On my systems, the Xcode plugin builds hog the computer and take a long time - 15 to 20 minutes for a full build, with fan noise galore. Same computer, building things in VS2010 in Boot Camp, whips out a full build in about 2 minutes.

**Chris Randall** (2011-05-20):

Go, JUCE. Our builds take about 30 seconds on PC and about 15 seconds on my Mac (Adam's is probably slower) from bare metal.

-CR

**Peppe** (2011-05-20):

@seancostello: any way to clear the plugin caches manually? I haven't sorted that out and I'm more of the wash-n-go party - I wouldn't say I have dev knowledge.

I wouldn't complain if the 32-bit bridge was a nice fella, but it causing 100x mouse clicks... well, let's just say I could live without it.

**seancostello** (2011-05-20):

@Chris_Randall: 15 seconds? FUCK.

I am now officially at the point where every major bug I face is Juce related. Unfortunately, I'm pretty solidly embedded in there, due to the XML handling of Juce.

**krylenko** (2011-05-20):

So +1 and -1 for JUCE, eh? Care to elaborate on why it's so hot/not?

I used to use Tracktion heavily (which is made by JUCE's creator), have been getting into C++ heavily, and know just enough to be somewhat awed by how extensive JUCE seems to be. Given my experience with Tracktion, I'd be inclined to trust Jules's decisions on usability/flexibility.

Course it don't mean nothin' if it's full of bugs...

**Chris Randall** (2011-05-21):

@krylenko: I only know enough to know it's not for us. We've fooled with it now and again, but like most middleware, you're better off just building the things from scratch most of the time. The main argument for using JUCE is that you essentially get the RTAS and AU for free, but now we have Symbiosis for the AU, and we could give two tiny little squirts of shit about RTAS, so buh-bye, JUCE.

-CR

**robbster** (2011-05-21):

Chris - what are the chances of you & a handful of the other useful heavyweight guerrilla audio developers (yes that's how some of us see you).. all y'all gang up on the Apple Campus, Room 302, Logic Development Central... and let them know on no uncertain terms that they need to work out all the useless bullshit idiosyncrasies of Logic once and for all?

Tops on my shit list would be to make MIDI control work properly for AudioUnits.

My (purchased) copy of Axon is dusty, since I can't go beyond the built-in sounds (no offense), and I can't afford another host (DAW) in terms of my time, learning curve, and diñero.

Also on my list? I can unplug and plug in any controller I want, anytime. Stop stressing out when I do this, @$#%ing Logic!

**krylenko** (2011-05-21):

@CR Ah, I misread and that should've been -2 for JUCE. Thanks.

**Chris Randall** (2011-05-21):

@robbster: the chances are zero. I care about Logic only marginally more than I care about ProTools. That is to say that while we _do_ build for it, I wish it would die the death that 20-plus-year-old pile of code so richly deserves, whereas PT is dead to me already.

-CR

**mad ep** (2011-05-21):

Not to go off JUCE topic... but anymore hints about the new plug?

**javahut** (2011-05-27):

so... ot... but what happened to 'expect a lot of new ad news in the next few days' from 2 weeks ago?
