drum machines do have a soul
Ok, the lists for to-do’s, to-learn’s and to-program’s are growing pretty as far as Fluke is concerned. Add to that the already humongous lists of alcoholic drinks and ice cream flavours I want to try and a new job I recently got, and that definitely provides for something to do over the weekends.
In the next post I will summarize the main to-do’s that were requested in the comments and clarify some issues that I may not be able to fix in the next version of Fluke. After all I’m not Gendalf.
Ever since I wrote the post about listening to FLACs in iTunes I had received quite a few responses indicating public’s general interest in the topic. And while I tried to keep the instructions simple, it was still not quite… Mac-like (damn you Jobs, how spoilt hath we become).
So, to celebrate my weblog being moved to a dedicated host, and after two sleepless nights, I humbly present to you Fluke, a Mac approach to listening to FLACs. Download, install and use. No moving files around, dragging libraries or following stupid instructions by someone who thinks he’s funny.
I’ve written out a pretty clear how-to on Fluke’s main page, but to sum it all up, all you really have to do is download and install the thing, and open your FLACs with it. Or just drag them onto Fluke’s icon.
Let me know how you like it, and make sure to leave a comment if it acts up. Not too complicated a program to act up but it is my first effort.
No matter what music you compose, you’ll eventually have to deal with compressors. There is just no escaping. Compressors are what you apply to make music better. That’s right. They help you make your music beyond studio quality. You’re one plug-in away from stardom!
All the glamour aside, compressors are one of the studio workhorses that are applied to achieve anything from subtle smoothing to downright squashing. It does help to know how the tools you use work though, and I’m hopefully going to provide you with just that. Let’s go from knob fiddling to consistent predictable results! Follow the link for an easy FREE introductory promotional kit (order the full 3 x video tape kit NOW and receive an instant $3.00 rebate!)
Machines are designed to help us. While they mostly cause nothing but headaches, they can come in handy when you program them right. The continuing story of the Beatles bootlegs has prompted me to start learning AppleScript to automate a number of tasks I typically perform on tags within iTunes, but then I realized that my problems are probably far from unique. Indeed, there are other nerds out there who have already written a number of useful scripts of us to use. Unfortunately, it takes being a geek to find geeky things, so here is a nice pretty Best Of compilation of useful iTunes scripts for all you people who don’t feel like dipping into the nerd scene.
UPDATE: Nevermind all this. Some time ago I had acquired a collection of certain Beatles recordings in FLAC format (65 pounds of Beatles vinyls on my shelf keep me guilt-free), and since the only lossless format iPods would play was Apple Lossless, converting to that format was my only option. Now, while I support the great idea of open lossless that is FLAC, Apple has really been a bitch about implementing it into iTunes. There have been rumours support for it will be present when Leopard comes along, but I think we’ll more likely see native support for WMA files than FLAC.Before today, the method I used to use was: I would take the album in FLAC, put it through xACT which would convert it to .AIFF, effectively doubling the number of song files on my hard drive and getting rid of all the tags entirely; then importing those .aiff files into iTunes, tagging them by hand a little bit, converting the result to Apple Lossless, getting rid of the intermediate .aiff files, and then putting everything through iEatBrainz, the automatic tagging software which bases its algorithm on a checksum of the audiofile, and not the length of all tracks like iTunes does. Now, on their website, the creators of iEatBrainz failed to mention that it doesn’t fucking work most of the time, so I would end up tagging almost everything by hand.Today, I got seriously pissed off at not being able to instantly listen to A Hard Day’s Night, and instead of ripping the LP like I wanted to, I found a workaround for this. Here is what you do.
I know I said I’d like to keep the blog free of discussions of software or hardware. But then, I also wanted the blog to enrich Internet with original content valueable to newcomers and professionals alike, or something like that, so that’s my excuse.
Besides, people constantly ask the versus questions, which fuels all sorts of flame throwing. I’m using both DAWs equally often now, so I’ll try to give you an idea why/when you’d use one over the other without all the “Logic just sounds better” crap.
UPDATE: Now that I’ve used Logic for quite some time, I have a bit of an update.
A while ago, I’ve read about digitalmusician.net in Sound on Sound. The idea seemed super great - you could collaborate with other users by inserting a VST plugin on a track or a bus in your sequencer, and all the sound from that source would get transcoded into mp3 and sent to the other user in real time. That, coupled with webcam support, seemed like a really cool way to collaborate. You could basically jam via Intertron, quickly bounce ideas, send files over, and do whatever it is you want to do with the webcam during your jam breaks. I’ve tried the plugin personally, and it worked great, but for some reason the idea didn’t really take off.
Now, the guys at digitalmusician have released a new piece of standalone “internet-enabled” multi-track software. Pretty much the same idea as the plugin, but now you don’t even need a host to run the plugin. That, by the way, could have been why it didn’t take off too - the plugin, from what I remember, was VST only, shutting the doors on all the bedroom users of Pro Tools, Logic, and DP.
I’ll give it a run, and I suggest you do too, but personally I think that nothing can replace the beauty of human collaboration, with all the sweating, physical abuse, and peace pipe sessions during tape rewinding time. Ye.
We had a guy drop in the store with a machine today. He just couldn’t get the MIDI to work at all, and the problem appeared to happen on the OS and not the software level.
We would go into the Audio MIDI Setup utility, and after spinning the beach ball for a little while, the MIDI tab would tell us that it was “Unable to Launch MIDI server”. Turns out, Digidesign was to blame. I think they are quickly turning into the audio world scape goat ala Microsoft, and for a good reason too.
UPDATE: One of the people who commented on this post, franck, may have come up with a solution, or at least a temporary fix. I don’t have an Ultralite on hand so let me know if it works out for you. And make sure to comment if it doesn’t - maybe we can at least make MOTU listen and absorb the costs of getting this worked out. Seriously, what the fuck.
Continue reading ‘PowerBook + Ultralite: Unable to Launch MIDI server’
Since May, MacBook has been one of Apple’s best-selling computers. Up until the Core 2 Duo upgrade of MacBook Pro’s, it matched its ‘pro’ bro in specs quite closely, with up to a 2.0 Ghz Core Duo CPU and 2 GB of RAM.
As many others, I saw the MacBook as a smarter option for the work I do, plus it would be far more powerful than my then current tower. I do quite a bit of audio and MIDI recording with Cubase outside of my full-time job here at a Mac reseller store, and got one of the 2.0 Ghz white Core Duo MacBooks as my main computer.
I found it quite suitable for audio work, except for a few quirks, which, depending on the audio work you do, will either not bother you, or drive you nuts.
From what I see working at an Apple Reseller store here in Vancouver, MacBooks are currently the hottest selling computers by Apple. Despite the infamous random shutdown, despite the occasional overheating, and yellowing of the case, the sales are quite high.
Now, a lot of people don’t understand why you have to always have two identical RAM sticks in the MacBook. Especially those whiny PC users - they always want to buy one 1gb stick of RAM, and keep the other slot empty in case they want to upgrade later (pff). Well, I am a MacBook owner myself now, so I decided to find out what really happens if you just use one stick of RAM. (Spoiler: There are lots of explosions, naked girls, and Bill Gates jokes involved, so read on).
|
