May 16, 2011

Get Busy, Y'all...

by Chris Randall
 



'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. Two thumbs way up. If you have film to scan, you need this, plain and simple.
 
 
 

28 comments:

Page 2 of 3
 
 

 
May.17.2011 @ 3:15 PM
puffer
Fucking Sonar.
 
 

 
May.17.2011 @ 7:21 PM
DBM
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 .
 
 

 
May.17.2011 @ 7:31 PM
7point62
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...
 
 

 
May.18.2011 @ 1:56 AM
Peppe
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?
 
 

 
May.18.2011 @ 8:51 AM
bleen
@ 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.
 
 

 
May.18.2011 @ 11:47 AM
Chris Randall
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
 
 

 
May.20.2011 @ 2:57 AM
Peppe
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.
 
 

 
May.20.2011 @ 12:03 PM
seancostello
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.
 
 

 
May.20.2011 @ 1:53 PM
Chris Randall
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
 
 

 
May.20.2011 @ 1:57 PM
Peppe
@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.
 
 

 
Page 2 of 3
 
 

Comment:

 

Sorry, commenting is closed for this blog entry.