Mackie Universal Controller

Hello again,
I am re posting yesterday's query to solicit even more feedback. Thanks for the very helpful feedback thus far ... all very helpful and appreciated. I was hoping to get more feedback before laying out that kind of cash .....
Here's the post:
Cheers
Hello logic guru`s.
I am looking to get a controller to save me time in mixes and edits ...
Anyone have any input on options ... what`s worked well and what doesn`t work?
The two I am looking at are the Mackie and the Jazz Mutant.
I did a cursory seach and read some of the other posts, but know that issues come and go over time.
Any more current advice or comments are much appreciated.
Cheers
Dee

Hi Bee Jay,
Thanks for feedback. I usually check the search before posting to annoyance. I did in this case ... and it was previous discussions that put the Mackie in the back of my mind for future. Just soliciting feedback re recent OS and pro apps upgrades - as well as Jazzmutant Dexter controller. No word on the later so it sounds like the Mackie is the way to go.
Cheers
Dee

Similar Messages

  • Mackie Universal Controller and Logic...

    Hi all
    I have one on order and believe it doesn't come with a manual for using with Logic.
    Any ideas on the best place to start with useful resources?
    Thanks!
    Steve

    Yes, Logic comes with a "Control Surfaces" manual, which documents all the control surfaces that Logic supports, and the full Mackie Control functionality is described there (well, apart from the undocumented features...

  • Digi Design 003 or Mackie Universal Pro

    Dumping my Roland VS2480 for Logic Pro and I need an audio interface & controller. I am looking for one complete package but so far I have not identified one. The new Mackie Universal Pro has 1 USB & 3 midi inerfaces but does not appear to have any audio interfaces, USB is not the way to go from what I have read. The Digi Design 003 has all the connections I need - yet all it mentions is Pro Tools vs being a viable alternative for Logic Pro as a controller. If I could mash the 2 together I would. Any suggestions? I have about $2,500 to spend. I have a MAC Pro Quad, 4 GB Memory , 3.0ghz and 1.5 TB storage.

    Hi
    I used to have a Digi 002 with control surface and now have an M-Box Pro and a Mackie HUI for the purposes of this discussion.
    The Mackie works fantastically with Logic as it was codesigned by the Logic and Mackie guys. It works better than the 002 control surface worked with Pro Tools.
    The Mackie also has HUI mode which allows it to control pro tools (still in a better way than the 002 did). You can get a "pro tools overlay" ($20 or something) that shows which buttons do what in the HUI/Pro Tools mode. The modes are switchable.
    The USB cautions you have seen relate to audio and not midi, midi over USB is no problem. I've got the older Mackie which is midi only which is also fine and you can pick them up around $700. It does need a free midi in out though.
    The 003 (whilst pitched as a minor augmentation of the 002) does allow for a midi mode which allows the 003 control surface to control 3rd party software, but the software has to be mapped to the controller which is potentially quite a drag. So there's no "driver/personality" for Logic or Reason etc....
    I would say (and am currently thinking about) having the 003 non-control surface (rack) version and the Mackie as the best of all worlds. The MCU Pro (±$1200 midi & USB ) and the 003 rack $1299 would be one way. Or you could get the rack factory which has a cool plugin bundle for $1695 and the midi only Mackie MCU at around $700.

  • Mackie universal control

    I want to purchase an eEmagic Logic Control. Will it work with Logic 7.1? Is there a firmware update I would need to get?
    What is the benefit of getting Mackie Universal Control?
    Thanks all!

    Yes it will work fine, no firmware update needed, allthough you can update it if your want, the firmware is downloadable.
    You don't need to upgrade the chips to MCU spec either.
    MCU gives you additional controller models, including HUI modes, which are irrelevant when controlling Logic. And a different colour scheme.
    Note there is a difference between the "Logic Control", "Mackie Control" and "Mackie Control Universal" - basically - don't get a stand Mackie Control, because it doesn't have the Logic controller handling built in, and so can't be used successfully with Logic (unless you upgrade it).
    So in short, a Logic Control will work fine. And you'll love it...

  • Q: For Mackie Universal Control users...

    How do you existing users of these wonderful Mackie and eMagic control surfaces like how the box behaves in Plug in selection/editing...?? Do you find it easy, and intuitive?
    I'm now seriously interested in getting a Mackie Universal, or eMagic Logic Control. I've been a user of the Behringer BCF for well over a year now, but hadn't utilized it much beyond the fader, and pan automation. I don't like how it works for manipulating plug-ins.
    Thanks!

    How do you existing users of these wonderful Mackie
    and eMagic control surfaces like how the box behaves
    in Plug in selection/editing...?? Do you find it
    easy, and intuitive?
    I'm now seriously interested in getting a Mackie
    Universal, or eMagic Logic Control. I've been a user
    of the Behringer BCF for well over a year now, but
    hadn't utilized it much beyond the fader, and pan
    automation. I don't like how it works for
    manipulating plug-ins.
    Thanks!
    I've had a Logic Control since it came out. The main things I use it for are:
    1. transport functions, including scrolling to a location.
    2. dedicated "save" button
    3. fader control / automation
    4. nudging objects (VERY useful)
    5. occasional plug-in parameter adjustment
    I find that searching for a plug-in parameter I need to adjust takes longer than just reaching up with the mouse and moving it. With simple plugs (few parameters) this is not an issue, but complex ones have LOTS of parameters. The abbreviations (caused by display limitations) make finding the parameter you want even more clumsy.
    Still - the control surface is the way to go to speed up your workflow, as well as helping to spread repetitive-stress injury throughout your body.
    HL

  • Universal Controller Crashing Logic - HELP!?!

    I got all excited over a product someone told me about called the Mackie Controller Universal so I ran out and rented one to try it. You can view more about the product at http://www.mackie.com/products/mcupro/index.html
    Not sure if this is an issue with a Logic setting or if I need to connect with the Mackie people, but everytime I turn on the controller then open a session and try to work with it Logic freakin' CRASHES EVERYTIME!!!
    Anyone else on this forum have this problem with a Mackie or other controller and know how to fix it?

    Couldn't figure it out so I just got rid of the controller. Please delete this thread.

  • Logic Pro 8 and Mackie HUI Controller

    I have the above running and control surface setup appears to be normal. However, while Logic is recognized on the HUI at bootup (verbiage in the display...) I get no control out of any faders, assignment buttons or channel strips. The only thing that seems to work are the jog wheel to move the playhead and the transport controls themselves. Everything else appears to be dead and I can't activate any assignment zone.
    Any clues as to why this would be? Logic or Mackie??
    any help would be appreciated.
    thanks

    It may be a corrupt preference file for the control surface:
    There have been a few issues since version 8, some of which have been rectified with the 8.0.2 update.
    Some that remain are;
    • Save LED doesn't go out after save
    • Some on screen alerts cannot be responded to via the controller
    There are a few others but overall it is working well for most people.
    Make sure you don't have a corrupt preference file for the control surfaces. In my experience, this preference file is even more sensitive than the main logic preference file. Ditch it and rebuild.. It's a pain if you have many custom features set up, but is necessary to get things going again.
    Once you have a set of logic preferences that are working well, copy the two files to the desktop and select them both, then right click and create archive... Then you'll have a pair of 'good' files that you can drop into the prefs folder when things go crazy again.
    After a crash, you will want to drop the fresh ones in there.... as a crash always seems to corrupt the prefs files in my experience.
    MacHD / Users / 'your account'/ Library / Preferences / (in here you look for, "com.apple.logic.pro.cs" for controllers
    "com.apple.logic.pro.plist" for the app

  • Will a Mackie Control Universal V.2.1.2 work with Logic Pro 9?

    Will a Mackie Universal Controller V. 1.2.1 work with Logic Pro 9?

    Mine does. There was something If I can remember how to do it about after the update selecting the controller to mackie controller. You have the option within the controller itself to be mackie controller or logic controller. If it powers up and says mackie controller, You should be fine. If you have a problem get back to me, Ill look for the link that tells you how to change it.

  • Multiple USB inputs - Keyboard/Mouse, Novation Remote, and Mackie MUC Pro

    Im running a Macbook Pro, 10.4 with Logic 8. I just got a Mackie Universal Controller Pro and also use a Novation Remote 49. Ive got an additional 20" screen, with the USB inputs as well.
    Im trying to hook up:
    - External keyboard and mouse
    - Mackie Universal Control Pro
    - Novation Remote
    If I plug in the Mackie and the Novation directly to the laptop, everything works. Of course, this then doesnt allow me to plug in the keyboard/mouse as there are only 2 usb ports on the laptop.
    Since Im using the external screen, I have the additional usb inputs on there. So, I plug either the mackie or the novation into one of the usb ports, and then the screen/aux cables into the other. Then I plug the other controller into the screen.
    With this configuration - one of the controllers wont be recognized. I generally get a message about reassigning or not reassigning them as well.
    Regardless of which I choose, the second controller wont come up. Using the midi preferences and controller parameters within Logic doesnt seem to do much either.
    Whats the work around here? If I get a multi USB hub, will this fix it? Im wondering why daisy chaining these pieces doesnt allow the midi to be properly routed or recognized.
    Hopefully this makes sense and someone has the solution! Thanks.

    Hey - Thanks for the quick response.
    'Why don't you leave the controllers connected directly to the computer, and connect your keyboard/mouse to the screen's USB ports?"
    Problem is - there are only two USB ports on the compute. In order for the external displays USB port to work, it has to be plugged in to the computer via USB as well. I have the mouse plugged in to the qwerty keyboard, but they both need to be plugged in to a USB port somewhere regardless.
    Am I missing something?
    It seems like the problem is really trying to plug an external controller in to an apple displays USB port (so that could be a power issue, although the Mackie is self powered, or just general connectivity).
    Based on the above, suggestions?

  • Midi gurus need your input please

    Hey guys,
    My question seems quite simple, but I'm just making sure I'm not doing something that's gonna cause issues.
    The setup.
    MOTU 828MkII (has 1 in 1 out midi)
    M-Audio 88es controller (just midi out)
    Mackie Universal Controller (1 each)
    Mackie Extender controller (1 each)
    Mackie C6 (1 each)
    considering the above setup, I need to get them all hooked up right to Logic. Do I simply get a MOTU MIDI Express XT USB, or ????
    Can I just daisy chain them? (out the m-daudio, into the MUC, out that to MEC, out that to MC6, out that to 828 which is connected via firewire to Mac) If so is there a drawback?
    I'm not too up and up on how to best get midi hooked and performing right, so any help would be greatly appreciated. I just got the Mackie stuff, so I am a bit baffled by what the best way to connect things is. Mackie recommends some kind of Midi 'patch bay', but before I drop another couple hundred bucks wanted to make sure I needed to and am doing it right.
    Thanks
    R

    If you can find a used Unitor 8mk2.. get it. maybe there is one on ebay.
    They work really well with Logic.
    I also have a motu midi timepiece that works well.
    Both have SMPTE ins.
    The other guys are correct, you need a separate port for each piece of control surface.
    So a multi-port midi interface is what is needed. The models I mantion have smpte (LTC) as well.

  • Importance of midi setup to Logic

    In our Utilities directory there is a midi setup assisstant. When looking at it, it seemed to setup the various connections to midi hardware.
    I don't quite get the true use of that app and how it affects logic. If I don't set things up in there properly, is it adversely affecting Logic's midi hardware performance? Does it improve anything? Does it even matter?
    Thanks in advance.
    R

    I see so just the names... k thanks. Been trying to track down why some of my midi hardware, namely Mackie Universal COntroller and extender, have been behaving a bit stragely lately. I thought this might have something to do with it. ALready re did the midi preferences, rescanned in Logic, etc... behavior still bizarre where some of the faders will group up for no reason, and I am not using automation yet.

  • Mackie controller vs mackie hui for logic

    i sold my mackie controller and i regret that
    i want to by a controller back
    on the internet i saw mackie hui controller with audio inputs
    does someone have experience with this setup: does it work like the mackie controller?
    i also use soundcard with firewire

    I've had mine for about a year and in any session it gets used about 10% of the time.
    If you have the cash spare its worth having but for me it is often far quicker to use the mouse and keyboard.
    The plug ins are also better accessed via the screen commands.
    As we all have different work methods and needs maybe its just me but its not really a necessity in a Daw set up.
    That said I prefer having it than not even for the amount I use it but if cash is a consideration there are far better things to spend the money on.
    Another thing that disappointed me was the build quality as compared to other pro mixers I have it feels distinctly on the cheap side despite the price!!
    Powermac G5 2.3 Dual 4GB Ram   Mac OS X (10.4.8)   Powerbook 17", Motu 828Mk11,MCU

  • Keystation Pro 88 (or other controller) as the Logic Control

    Has anybody got their setup like this? I've been trying to get this to work for the past 6 hours and no luck. Can someone please help me? Just bought Studio 2 days ago and haven't touched it yet cuz I can't get the keyboard to fully work.
    Joined: 17 Jan 2006
    Posts: 55
    Location: Los Angeles
    Posted: Sun Jul 15, 2007 12:03 am Post subject: Keystation Pro 88 (or other controller) as the Logic Control
    I'm sure some of you already know how to do this. I just figured I'd write this up at some point to share with others. The basic idea is to use the Keystaion Pro 88 (or some other MIDI Controller) as an actual Control Surface, or in this case the Logic Control, to have more freedom with the MIDI Controller, i.e. using the group of 8 faders (on the Keystation) to control Volume for tracks 1-8 in the arrange window, and then hitting Bank Right to automatically control tracks 9-16, and as a result making a universal controller not bound by specific channel messages, or MIDI CC Volume messages etc... in short the essence of any Control Surface.
    What I'm describing below is what this app will also do: http://www.opuslocus.com/lcxmu/index.php
    I basically just wanted to avoid using a separate application all together. Keep in mind that the app does simplify the whole process, but Logic inherently can do pretty much everything the app does.
    I recommend reading this in its entirety before attempting.
    KeyStation Pro 88 as Logic Control
    Part One: Add Logic Control as Control Surface
    1. Open Logic.
    2. Preferences / Control Surfaces / Setup...
    3. New / Install / Select your preferred device (in my case Logic Control
    4. Click the icon in the setup window for the Logic Control.
    5. On the left hand side under "Logic Control" you should see an "Out Port:" and "Input:" ... select the desired MIDI in/out through which your device is connected.
    6. Open Preferences / Control Surfaces / Controller Assignments. Make sure you select the "EXPERT VIEW" check box.
    7. You should now see a bunch of different Zones in the Zone column, one of which is "Control Surface: Logic Control"
    8. Create your own Zone, KeyStation Pro 88 (or whatever) using the Plus sign in the bottom left corner of the Controller Assignments window.
    9. Now basically go through the existing parameters already available in the Logic Control Zones, Select what you want. You can select entire Modes or individual Controls / Parameters. You can select multiple values (only multiple Control / Parameters NOT modes) by selecting and dragging or simply with select and holding command.
    10. Command-C the selected Modes and then click back onto you user zone that you created above.
    11. Click inside the Mode column (or Control / Parameter column depending upon what you selected and copied from the Logic Control zones).
    12. Command-V to paste the Modes into your user Zone.
    13. Do this for as many Modes / Controls you want, that your specific MIDI controller interface will be able to handle.
    Part Two: Assigning Input Values
    1. Open Preferences / Control Surfaces / Controller Assignments
    2. Now for each parameter that you copied, you will need to set the input MIDI value from your controller.
    3. Click on your User Zone, then Mode, then the first parameter in the 3rd column.
    4. You should see a "MIDI Input" option (this should already be set correctly as long as you set it earlier in Step 5 of Part One). If it's not set to the correct MIDI input (which I found to be the case sometimes even after Step 5), then change that here.
    5. Next to "Value Change:" you will see a box with MIDI data in it. Delete the existing date by highlight and delete.
    6. Activate "Learn Mode" (bottom right corner of Controller Assignments window) then click within the "Value Change" box, then move the corresponding fader, button etc. The "Value Change" should now show the MIDI data value for that fader. Be careful here, there should only be 3 groups of 2 for data here... if you see 2 groups, of 3 groups, of 2 then typically the FIRST group of 3 should be the value you want here. You can always delete the data, and move the fader again to be sure. The reason for the 2 groups of 3 is not in error: some buttons send TWO MIDI values, one on press and one on release. You can use this to your advantage and assign TWO different functions to these buttons, thus the first (press hold) value can do one thing and the second (release) value can do another. You can also change the MIDI controller to only send 1 message on press and nothing on release, or simply make sure that only the on value is present in the "Value Change" box.
    7. You'll have to do this for all the different knobs / faders etc. on your MIDI controller. There are many shortcuts of course. You can manually type in the Values if you know them. For the Keystation Pro, M-Audio has an app called Enigma that I recommend for changing controller parameters and much more on the Keystation. You can use this app to assign all the actual control data that each button or fader sends to the sequencer, once you know the values you can convert that data to the MIDI data values and enter them into the Value Change box.
    8. Once you're done assigning values to the controllers, you can delete all the Zones except for the user Zone you created earlier. Before you do this, it's a good idea to back up the Control Surface preference file just in case you ever want to grab something else from the Logic Control Zones. You could always add a second Logic Control and copy the Zone from that, but you'd have to reassign all the MIDI Input: values ... short version, just back up the preference file before you delete the Zones. The reason why you want to delete the Zones that you're not using is simply because if you have a controller that happens to send out MIDI data to the sequencer, and the actual Logic Control happens to have that MIDI data value already inherent it it's Zones, then you could be asking for trouble, simply put you'd be sending MIDI data to change Volume and the Logic Control maybe has that MIDI Data Value already assigned to Pan for the existing track.
    The file to backup is located here: ~Users/username/Library/Preferences/Logic/com.apple.logic.pro.cs
    As a precaution I have always backed up my Logic Preference file WITH this .cs file. Technically it's not necessary... for instance: Let's say you trash your preferences and open Logic to find that the Logic Control is missing from the Control Surfaces Setup. So you add it back and now you find out that Logic is missing the User Zone that you created. If you close Logic and copy the .cs file back to the directory above, then upon reopening Logic you should find your User Zone is in place again. But I've had mixed results with that, so just in case I copy over the preference file with the .cs file as a pair. It seems that the Logic pref file only contains information that the Logic Control is a Control Surface on your system and the .cs file is the preferences for that specific Surface.
    Another note: after a recent Logic update, maybe 7.2? ... it was whichever update added support for more Control Surfaces, I can't remember. This update basically erased all the hours of hard work linking the Keystation to Logic as the Logic Control. This only happened with this specific Control Surface update, but not with 7.2.3, probably simply because they didn't make any changes to the .cs pref file.
    Anyhow, when this happens again in the future, there seems to be a quick fix. I take NO responsibility for you somehow crashing Logic on a continual basis after applying the fix. Personally I have seen NO issues by doing this at all. I simply copied a version of the .cs file with the new update missing the Keystation Zone, as well as a version of the .cs file WITH the Keystation Zone, to a PC (I think it was a PC, don't believe I tried it with textedit, although should work as well). I opened both of the files in notepad and compared them. I noticed the word Keystation towards the bottom and realized that most all the data (gibberish) was exactly the same up until a point in which the file with the Keystation data had a group that was absent from the new .cs pref file from the new update. So I basically copied the data from the old .cs pref file, pasted it into the new .cs pref file, saved it and open Logic. Logic warned me that a pref file was corrupt or something of that nature, but loaded fine anyway, and the Keystation Zone was back in Controller Assignments.
    One last thing... the problem that some of you may run into is that by making your MIDI controller a Control Surface, or turning your Keystation Pro into a Logic Control, limits some of the functionality of the MIDI Controller. For instance, a Logic Control's main purpose is to control different faders, knobs and what not of MANY different tracks. When you move a fader for volume on the Logic control, it will move the fader corresponding to the selected track... it's not programed to say change the actual midi CC 7 for Volume, only the actual Fader. Thus, what if you want the MOD wheel to still control modulation and you want the sustatin pedal to continue to act as a sustain pedal. Well, if Logic sees that Port 1 is the input for the Logic Control, but in reality the Keystation, then it's only going to allow specific events through. The way around this issue is by using both the input options that the Keystation has... hook the MIDI out into Logic and use the USB port as well. I run the Keystation as a Logic Control through the USB port, and use the MIDI out for actual MIDI data. But the catch is you have to make sure you only connect the MIDI Port into Logic's sequencer in the environment. Thus open the environment, open Clicks & Ports, Port 1 and Port 2 are the IN/OUT for the USB port. Midi Port is the Keystation's MIDI port. Select and delete the cable for the SUM, and run individual cables for the ports you want to use. Thus, all your other MIDI interface Ports, the Caps Lock keyboard etc. Just be sure that if your using Port 1 (USB Port Out from Keystation) for the fake Logic Control, that it DOES NOT cable into the "Input View" or "to Recording & Thru". This creates yet another issue:
    The controls on the Keystation have to send SOME form of MIDI control message / data to Logic. Well if the faders on the Keystation are preset to send Ch1-9, Volume 0-127 messages, then when you move a fader on the Keystation (as the Logic Control) since the Keystation is still reaching the sequencer from the MIDI port, you will be sending MIDI values that can effect your current track possibly when you don't want to. The work around for this is to be sure that all the faders / knobs that you want to use as your fake Logic Control are sending useless MIDI data... i.e. CC 75, 76, 77, and so on. This way moving faders won't effect playback, although you could still in theory record this MIDI data into your sequencer. You could however filter this events from entering the sequencer input with a transformer since you know precisely what MIDI CC values you are changing. The easy way to assign these values is to use the program Enigma from M-Audio that I mentioned above.
    More discussion specifically related to the Keystation Pro 88:
    You can do a lot using the Controller Assignments and different Zones from the Logic Control. For instance, the real Logic Control has Solo, Mute, and Record buttons for the 8 faders. The Keystation Pro only has 1 button underneath each fader. But you could use one of the other buttons to toggle Solo, Mute, and Record mode so that depending on which mode your in, the buttons underneath each fader will correspond to Mute or Solo etc. By the way, a good setup from my experience is to use the first 8 faders of the Keystation as the track faders, and the final 9th fader for Master Volume. You can then set two of the buttons underneath the Knobs as Bank Left and Bank Right buttons to change the 8 fader tracks to correspond to the onscreen track groups of 8. Also don't forget that you can assign TWO functions to EACH button, since a button press can send a value of 127 and a button release can send a 00 value. So if you press and hold a button it can activate "Shift-select Mode" and until released it can make the buttons under the faders act as Volume to Zero resets or whatever you want. When you release the button it will go back to just Mute mode or Solo mode. The Controller Assignments window has MANY options, and parameters some of which are very confusing and take a lot of trial and error to understand... the manual helps a little but of course isn't perfect.

    I'm thinking about buying a Keystation Pro 88 (2nd hand) so I was googling around and found this:
    http://www.soundonsound.com/sos/Oct04/articles/keystation.htm
    [quote]
    I had some trouble getting the transport controls to work with Emagic's Logic, even when I loaded the 'Pro 88 Logic Preset.LSO' file on the supplied CD-ROM into Logic. I contacted the guys who designed and set up the Keystation here in the UK at the old Evolution offices, and between us we managed to work out what was going wrong. First of all, you need to enter the appropriate MIDI key commands in Logic's user preferences. These cannot be updated with an LSO file, so the commands have to be entered using the Learn Key function in Logic (see the screenshot below for the list we used). Then we discovered that the transport keys were toggling, which meant that only each second press of each key was actually working. It turned out that I had an early version of the Logic preset before this had been fixed, but the more recent one has been put on the M Audio web site for anyone else that needs it. It took about 30 seconds to change the output commands so that the buttons were no longer toggling.[/quote]
    Did you get it to work correctly eventually?

  • Where Are You @ Audition 4+???

    Hello  I really need to speak to the makers of audition.  Your product is so great i cannot for the life of me see why your letting this product slip away.  I have been using Adobe Audition my entire life.  Your product allwos me to work faster and more creative then any other product on the market.   Audition 3 is almost a perfect product.  It really dosent need anything else for me except a few features are missing for me..
    We need windows 7 64bit compatability.  Majority of pc users by now have windows 7 64bit working with audio / video these days.  The reason is we need to take advantage of all the ram and speed of a 64 bit software.  for small studios getting by with the 32 bit is wonderful.. but we use a ton of rack plugins for tube compressors, reverbs, and effects through out our sessions.   we need to keep the pc running smoothly in very large sessions.
    We absolutely need a better universal way to use our own DAE controllers.  You left us stranded here with one option.  The mackie control.  What about those of us using the Mackie Hui or other controllers?  I have searched the depths of the internet looking for a way to get my Mackie HUI working and have went as far to almost hire a programmer to help using the Audition SDK.  If anyone can help on this subject please shead you light on me here im so tired of looking for a solution.. thanks
    Your taking forever on getting your team together and taking your product to the next level... Meanwhile die hard supporters of your company are getting left in the dark and your rival companies are luring us slowly in by listening to what we need and delivering it..  For instance ive seen pro tools copy a few of your features through out their updates because people wrote them asking them to have that feature.. One nice feature they havent stolen yet is in the edit window you can highlight the area and simply move volume up and down as needed.  Love that feature while mixing down..  You guys have in my opinion the best audio functioning software and layout but your missing midi controller compatability..
    Over the years ive been listening to everyone else say adobe audition is low and how i should  upgrade to pro tools, nuendo, or something professional... But i defended my love for this software because  Its  fast, it functions with little pc load and how its professional all the way arround.
    Can you at the least release an update for the midi controllers!!!  im using the mackie hui because i like to see a meterbridge. You only have support for the mackie Universal.. But there should be a lot more controllers supported.  I also own the jl cooper cs-10 and digidesign control 24.  
    Anyways im not here to listen to the BS... im hoping we can get some insight from the developers on this one here.  Also if youve found a way to use the mackie HUI interface in audition 3 100% please help with that.  Thanks for your time.

    Thank you for the excellent reply.  This helps so much.
    a few questions in reply to your statement.
    1   Some of the more high end mastering processers and plugins that are purchased independently are corrently taking advantage of faster processing using 64 bit.  I am currently running adobe audtion in windows 7 64 bit and it works great i was just curious if they were going take advantage of technology and write a version for people who use larger stuidio sessions and more plugins whom need 64bit.. For instance putting 32 tracks with three active racks on each track creates pc load that causes jittering and errors.  UNLESS... you are running quad core extreme or i7 processors and using 6 gigs of ram.. I continue purchasing the fastest pc i can build.. i want to be able to do my job in audio smoothly and in less time.  I think more professionals would take your product more seriously knowing they can take advantage of their pc recources..  Unfortuinatly 32 bit versions are limiting us like a bottle neck and people getting in to some serious amazing mixes really need to open the pipeline with out errors and hickups.   *just for the record.. im not trying to insult the 32 bit version of Audition because i believe its a fantastic piece of software as is but as a consumer and someone who uses it daily in a comercial environment i would love to have a version made to run on my 64 bit architecture.  I work in audition daily and blow away the clients who are "pro tools this and that"  fans because ive been working in this software environment my entire life so i know the ins and outs and it delivers a much better sound IMO and proof of work.  You cant seriously tell me that because there is a few people still running xp the company hasnt released a 64 bit version.  I would suggest leaving the version 3.0 created for that version and using 4.0 to stay updated with todays technology and PC uses windows 7... My audition system uses 3 monitors.. the 1st is a 46inch that shows my workspace the second is a 32" that shows the mixer and FX rack the third is a 22" that shows the FX plugins controls.. i leave all three wondows maxamized and up to see whats going on while recording a session..  Nice you have this feature.. Just to give you an example of the setup and why multiple cores and processiong and why were using 64 bit.. we are alsio taking advantage of faster hard drives, ram,  ect..
    2.     The drivers fro the mackie board i was reffering to was made in 1997 and IMO is a great tool available for adobe to use to give us hands on production.  It features a full meter bridge and controlls basically everything your mouse regularly clicks on.. I purchased this specifically to use with my adobe audition and went in to set it up in my studio and..... i was greatly dissapointed to find only one support controller available for the mackie universal which is a slightly newer version but dosent have a meter bridge...  There is not many professional automation mixers available for us to buy so supporting the few that are out there would be nice.. and im sure if you contacted mackie or any other company making boards you will find them happy to supply you support to place them in the software...   Its a little diffrent for me as a consumer writing them now asking for a basic control driver for my MACKIE HUI which now is discontinued and asking them to make me a driver that i can mod in to your system...  thats way too difficult.. Im asking if you would look in to this for future development so we can take advantage of automation and control in all available consoles.. Profesional recording  environments use these surfaces shouldent your software support them?
    3.  Adobe audition is great dont let someone program and change the whole layout arround. this work environment is so perfect.. it really im really a die hard audition user i work in this environment and think its the best.. There really isnt much to change. IMO it just needs support in the areas noted above.. It would be cool to maby update the skin a little but you really dont need much... Im very estatic about a newer release.. I however do not work in mac and not every audio engineer does eather. However mac support is awsome to hear guys!
    IM excited to hear of updates and you guys are moving forward and the product was not dropped Audition should be a priority over soundbooth IMO.. thanks! oh and is there anyone with knowlage of how to get this mackie hui working with automation in adobe audition 3?  thanks?

  • Mini and Logic Pro7.2

    Hello
    I am a solo musician and I am in the process of completing home studio.
    Since I am starting from scratch and have a luxury of spending 10K at once I have compiled a list of gear I plan to put together:
    Audio Interface - Motu - traveler
    Midi Sync - Motu - express xt
    mic preamp - UA - 6176 channel strip
    mic - rode - ntk
    controller - mackie - universal
    monitor - yamaha - hs80m
    sound module - I am torn between yanaha MotivRack and Roland - fantom xr
    As a computer, initially I am planning to use new Apple Mini. My thinking goes as follows:
    Apple will introduce a G5 tower replacement and new operating system around Christmas. In between now and New Year I will be learn how to use logic pro midi capacity. I do not believe that I could record audio, but midi should run well on Mini. Once new G5 tower replacement Apple is available, I will sell mini and upgrade.
    What do you think?
    1) About the gear - I welcome any suggestions for improvement.
    2) Will I be able to use Mini to use midi - someone told me that he is using mini for audio but I have my doubts since HD is only 5400 mpr.
    Sincerely,
    AnyaS
    tbd Logic Pro7.2 on Mini

    hey i mean, all that stuff sounds great! but do you actually need any of it? you should buy what suits your needs and the way you like to work. what exactly are you trying to accomplish? are you looking to get into scoring, put out an album, record other bands? these are the most important questions and the answers to those should dictate what you buy. it seems to me that you are going to be seeing a lot of overlap between all those different sound sources. and most likely, a lot of unused/wasted stuff. don't forget that Logic alone comes with a pretty massive library of instruments, sounds and effects. if there is indeed something specific like say, symphony orchestra stuff then yeah something specialized like the miroslav would be great to have. but i'd really ease back and weigh your needs and focus a bit more on figuring out what you're goal is with this setup. if i had 10k to spend personally i'd buy:
    Quad G5
    2 20" Cinema Displays
    1 88 key MIDI controller
    Logic Pro
    Dynaudio monitors
    A nice desk (as in furniture, not mixer)
    A nice chair
    A decent mic
    A nice interface
    and MAYBE some kind of soft ROMpler like Atmosphere or SampleTank or something
    and i'd still have a bunch of money left over
    i think you'd be surprised how little gear you are actually going to need. of course, i don't really know what you're looking to do so maybe you do indeed need all that kit. tell us more about what you are planning to do musically and that could help better pick a smart shopping list
    if it interests you at all, i own a sound design/sample company and i also do some custom scoring work for t.v. and video and my entire setup is:
    Logic Pro
    Mac mini
    MIDI Controller
    SoundTrack Pro -wave editor
    Large Sample Library
    portable HD recorder and stereo mic for field recording
    Blueroom Minipod monitors
    i also have a few hardware synths that have become more collection pieces and don't get much use anymore. and some other software like Reason and Ableton Live that don't get a lot of use anymore. i make a nice living off this very basic setup. my studio is in my apartment in the extra bedroom. it's clearly not all about the gear for me.

Maybe you are looking for

  • When I click on certain website like youtube the screen goes blank and will to open. What do I need to do?

    when I click on certain website like youtube the screen goes blank and will to open. What do I need to do? I really need help

  • HOW CAN I GET A NEW LAYOUT/HOMESCREEN? PLEASE READ AND HELP

    Hi, I currently have the Blackberry model Curve 8530, and I have been trying to get the new update (the menu style like the torch) because all my other friends have the same phone and I can't download the update. My phone and computer say that I have

  • Requirement in Web Analysis

    Hi Experts, We are designing a new Chart report in Web analysis, in "Rows" their are three members and the "Columns" contain two members. Our Client requirement is that Two specific Dimension members Of "Rows" should show Data specific to One dimensi

  • Colour Profile Confusion

    I'm new to calibration and a bit confused. I've calibrated my monitor with Spyder Express and it looks fine. However there is a colour difference when I view a photo of a blue flower in Aperture depending on whether I use proofing or not. If proofing

  • Message Include * is used in multiple main programs (210)

    Hi, I get the message: Select a main program in Properties View on tab "Source" Include /SAPDMC/SAP_LSMW_READ_FORMS is used in multiple main programs (210). when I want to modify an include in LSMW. The effect is for example that I cannot open the de