Jump to content

Noizyboy

Members
  • Content count

    35
  • Joined

  • Last visited

About Noizyboy

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  1. I would always recommend that you experiment with a cloned drive and not your original! I have two system drives for this very purpose. This way, it is highly unlikely that you will ever have downtime with your system. So, yes get a second sata drive, clone your drive, and then update. N Yep, you are at stage one. You video card is certainly not working optimally yet, since it's still using a generic driver. Did you follow the section in the guide regarding installing kexts directly from the script? If no, then do that. If yes then there are a few missing that you will need to install manually (using kext helper), or add to the kexts folder in the script and install from there. The next thing you need to do is install the missing kexts to get everything working optimally. First for video, do a search for OSX86 tools, and use this to generate a graphics string for your video card. This is pretty easy! You should find detailed instructions on how to do this on here somewhere. Next, find the correct kext for your motherboard's audio chipset. I already gave somebody else info on how to get this working, so if you search around on here you should find it. I think I used vodoo's kext, but I'm not entirely sure right now. Lastly, install the correct driver for your wireless adapter. If you followed my build, then go to the manufacturers site and download the latest SL driver. N I had the same problem with my legit mac using 10.5.6. You should just upgrade to SL. Everything works better in SL for 8.0 and above. Also, I didn't think that 8.0.3 was leopard compatible. Thought it was snow leopard only...... N
  2. Hey! Sounds good! Is your 192 i/o expanded, so you're getting 32 ins and outs with this? Hmmmmm? Never thought of using the legacy port plus ADAT bridge to get another 16 ins and outs. Good idea. I'm running a 192 i/o with analogue expansion card, and a 96 i/o with an Apogee connected to the Adat port, so 32 in and out. I use all 32 ins back in the days of manually dumping midi production from my Logic setup, but nowadays I just export the files via ethernet, so everything past channel 24 never sees signal. I do have a large ensemble occasionally which may get to channel 26 though......... Which plugs are you running? Liquid mix HD? I love this plug, but it has really been a problem for me. Hope focusrite/ Digi gets off their but and codes a Snow Leopard compatible version soon! N
  3. Okay, so just to be clear. You have installed OS X 10.6.2 using Chameleon 2 RC4, and not EFiX? Did you use a standard 10.6 install, and then use software update to get to 10.6.2? (you would have to update sleepEnabler before rebooting otherwise you'd get a KP on restart) Did you update your SleepEnabler.kext to the 10.6.2 compatible version? And, one more time, is your EFix dongle not plugged into your USB and on the other side of the room, under the couch? As far as Protools, of course you have trashed preferences, rebuilt databases, etc, right? This is happening in a completely fresh session? Where are your files playing from? Which drive and bus are they on. Your problems sounds like it's either disk or memory related. Pro tools will still be visually okay in such an instance because it is reading the waveform and meter info from wave cache. The only time I have ever seen this type of issue, is right before Pro tools is about to crash, but you say your system will play like this and then continue to function logically? Check this thread. I know this for the EX58 UDR3 Mobo, but installation should be the same, except for a couple of kexts. http://www.insanelymac.com/forum/index.php?showtopic=185097 Check your Bios for memory and Sata settings. I would erase the system drive and do a completely fresh 10.6 install using PC EFI 10.3 (I haven't tested 10.5 yet). Test this setup with your system and just the core card. Should be cool. Add a card at a time and continue to test. Success, then...... As an option update to 10.6.2. I only updated because I wanted to use the new Apple bluetooth magic mouse, which require 10.6.1 or later. Oh, I also just realized that PC EFI 10.3, as used in the X58 Mobo Script, uses Chameleon 2, and not the latest 2 RC4 update that is in PC EFI 10.5 (I believe) so this could be your problem?
  4. Okay, just checked and for sound I'm using VoodooHDA.kext. A quick search on here should find you a link to the latest version. For sleep, as I said, you should use the ex58 mobo script to install sleep enabler. This script uses PC EFI 10.3 though, unless they updated since I last downloaded. Regarding the start up time, pro tools always takes longer the first time you launch it, for two reasons; 1. Because it scans for plugins on the first launch. 2. Because, unless you did something memory intensive since the last launch, it's loading from memory. Also, if you have DSP caching switched on, this will make most subsequent session loads after the initial one, faster. I try to stay away from DSP caching though, as it messes with certain plugins, and also causes problems with ADC (Auto delay compensation). Are you switching between different installs in between launching or making changes to your plugin folder? This will make Pro tools do a complete plugin scan, which is slower. I clock the load time at 30 secs for a fresh start from login, and 25 secs from re-loading after immediately quitting pro tools. Either way, if you have many plugins, as I do, this is ridiculously fast! At least twice as fast as my Quad G5. I think once you install your third party plugs, you load and re-load times will be consistently around 25 secs. Let us know how you get on with your plugins.
  5. Cool, I was just about to tell you that your tdm ribbons are backwards, but you figured it out. Okay, did you get your sound, and sleep. For sleep you should use the X58 script to install the sleep enabler kext. You're in 10.6 right? 10.6.1 upwards uses a newer sleepenabler kext. For audio, I'm gonna have to take a look when I get to the studio tomorrow, so I can see what I used. I tried a couple of different kexts. Verify your bios settings with this guide; http://www.insanelymac.com/forum/index.php?showtopic=185097
  6. Best way to find your graphics card is through research on the forums or the Snow Leopard compatibility WIKI. Geforce 9400 GT seem to be doing pretty well. That's what I'm using. I actually installed mine using a custom graphics string I made using OSx86 tools. Hey, I've never done this before, but I can tell you that my firewire is working perfectly in all way, besides fire wire target disk mode (which will not work on any hackintosh machine, and will leave your mobo smoldering). What device does this method play to? What's on the end of the firewire cable? Well.....not necessarily. Most windows machine do not have firewire ports, so this could be the reason for it's omission on the windows version of Pro Tools. Can you verify this as working in Snow Leopard? Does the peripheral connect to firewire cable draw power from the firewire bus? If the first is true, and the second isn't, I think you have pretty good chance of it working if you use an EX58 mobo.
  7. I actually used PC EFI 10.3, but it shouldn't make a difference. You'll also need OSx86 tools for the graphics string and a kext for the audio, unless these are now included in PC EFI 10.5. Also, you may just want to use the 'X58 Mobo script' that's floating around here somewhere. This will simplify things significantly. N
  8. Do you have any accel cards in your rig. I ask because the only downside to using RTAS is the extra voice usage within TDM. If you're planing on doing large mixes you're going to need accel's 192 voice count.
  9. Okay, just for redundancy's sake, hav you tried to either innitialize the media dive, or use a different drive. Which bootloader are you using? It sounds like an installation problem. I would try a fresh install using the X58 motherboard script using PC EFI 10.3. I had some weird drive and USB stuff happening with my first install. Re-installing with the above script fixed it.
  10. Hmmmmm.....Seems like the problem is related to the install. Is the install vanilla? I think vanilla with a few kexts in an extras folder is the way to go. I'm pretty sure that the issue you're having doesn't have anything to do with normal pro tools behavior. When you load up a session and look inside disk allocation, which volume does it say you're using? Is the volume formatted for Mac OS extended journaled? Which bus is the drive connected to? Firewire, USB, Sata, or ATA? Is the song folder on the same drive as the one you intend to record to?
  11. Update: Now on 10.6.2 running with Pro Tools HD 8.0.3 (Official release). I'm using a Magma PCI chassis (the one with the pericom chip. There are two. One 7 slot 64 bit chassis, and one 6 slot PCI chassis with daughter board attached. I'm using the 7 slot version which I found on ebay for $150!!!!!), so I now have and HD 5, since I'm using all my cards via the expansion chassis. Still working flawlessly with zero issues! Actually the extra HD cards, beyond HD 2 are kinda redundant, since the computer performs to the level of an HD 8 (at least) in RTAS mode with a buffer of 64, giving the same amount of latency as TDM plugs! This is a substantial breakthrough because, digidesign (those people I invested $30,000 with to get the HD 5 rig), completely turned their back on their PCI-X / expansion chassis market by discontinuing support for their hardware. Also, the actually said in the release PDF for Pro Tools HD 8.0.3 that this would not work. I guess they are lazy coders, who 1. did not recode 8.0.3, 2. do not write separate code for windows and mac, or 3. The addressing of the cards is handled by the bios, so it doesn't matter whether you use PCI or PCI e, because to the OS it looks the same. Either way, I'm glad it works!!! It saved me another $20,000 in upgrade fees.
  12. I've been pretty lucky. So far I've only had one software conflict, and I think that is to do with this particular software's incompatibility with Snow Leopard. I'm using a plugin called Liquid Mix HD. Which ever version of this plugin I load first (There are stereo and mono versions) prevents the other version from loading up. I get both a DAE error and a fatal error warning. Very strange, but I've noticed on focusrite's site that they don't list Liquid Mix HD among the plugins that have been tested with Snow Leopard. I wrote them an email to see if they can suggest anything as a work around. Of course I can just use routing to get around the problem myself anyway. Update: I got a reply from focusrite and they say that they will not test for Snow Leopard compatibility until digi release it's official version of 8.0.3, which has now happened. Still waiting for Focusrite.......... For now, I'm just deciding which version I'll use in each session, since I love this plug!!! It may be quicker to just troubleshoot and fix this one myself......
  13. It seems to have worked. It, being Carbon Copy Pro. I just cloned the drive and now when I boot, if I hit a key when Chameleon loads, it gives me a choice of two OS X volumes to start from. Pretty Cool! Now I have to test it by removing the original drive and just starting the computer up with one drive in the machine, to simulate a drive failure. I've been pretty lucky. So far I've only had one software conflict, and I think that is to do with this particular software's incompatibility with Snow Leopard. I'm using a plugin called Liquid Mix HD. Which ever version of this plugin I load first (There are stereo and mono versions) prevents the other version from loading up. I get both a DAE error and a fatal error warning. Very strange, but I'm noticed on focusrite's site that they don't list Liquid Mix HD among the plugins that has been tested with Snow Leopard. I wrote them an email to see if they can suggest anything as a work around. Of course I can just use routing to get around the problem myself anyway.
×