Problem with Fader Banks and Channel in MCU PRO with Logic Pro X

I purchased a Mackie Control Universal Pro earlier this week, and I have talked with Mackie support techs twice and they have not been able to help me. My problem is that everything seems to work well with Logic X talking with the MCU with the exeption that the Fader Banks function will not move left to channels 1-8, they are stuck at channel 9-16, and will move to the right on to 17-24 and so on, but it doesnt move to 1-8 when the left fader bank motor is pressed. However when you toggle tany channel 1-8 levers on the computer screen, the corresponding lever on the Mackie goes up and down, but the reverse does not occur. The Mackie folks say this is a problem with Logic Pro X, not the MCU. Perhaps they are correct, because I still have Logic Express on my Mac and when I close Logic X and Open Logic Express the fader banks move perfectly from 1-8, 9-16, and so on as do the tracks. My computer is update with Mavericks.
I would appreciate any help! I am not a techie, an old guy who used to record on 4 track computers, and want to get away from a mouse control, but I'm going to take the Mackie MCU back if I cant get this straight, I've spent a lot of time on this. Help!

thank you Pete in Denver, I actually made some progress today, in setting up the control surface of the Logic Pro Control Surfaces Support Manual, around page sixteen gave me a partial answer. I had the Mackie icon first, then the Logic Control, and it said to drag and drop the preferred icon to the left or first place. that solved my not being able to access channels 1-8, I was able to press the fader bank left button and - voila!. so that saved my initial problem, but I still have some issues in moving faders and banks in existing projects, some tracks show up lit up in the tan colors others don't, but that is probably due to the way i would move tracks around once I received tracks on drop box from a friend and created new tracks, and I changed a lot of the order of the tracks. ANyway. I did make progress. Thanks!

Similar Messages

HT200169 Having a problem with Logic 9 on a Mac Pro.Working on a lenghty song and apparently session got corrupted.Doesnt let me export tracks,program crashes.Already tried start brand new session with the tracks imported into it but still wont export.Sug

Hello,having a problem with Logic 9 on a Mac Pro.Working on a lenghty song and apparently session got corrupted.Doesnt let me export tracks,program crashes.Already tried start brand new session with the tracks imported into it but still wont export.Suggestions?

Thanks, Ian. Yeah, that's how I do it now...or with the controls in the left side pane. Still, I would have liked that quick on-the-spot edit capability...especially while sketching.
Ian Turner wrote:
Sorry Mark, you are out of luck as it does not do that - it works the same as L8. The way I would achieve that with more accuracy and control would be to route all the tracks you want to fade to a Bus then use volume automation on the bus. To do this you will need to add a standard audio track, then re-assign it using (Control Click on the track header) to the Bus track. You can then automate volume/plugins etc on the Bus track.
Ian

The Problems With Logic (as I see them) - PART TWO!

Hello again,
It seems to be a tradition now that as I compose on a track, I keep a text editor open so that I can jot down all the annoyances and problems that I encounter during my creative process... Anyone who missed the previous edition of this topic, please visit PART ONE, here:
http://discussions.apple.com/message.jspa?messageID=3605456#3605456
That said, here I give you "The Problems With Logic Part II":
1. Logic should clear the playback buffer everytime you play. Quite often you start playing and there is trailing reverb/note events from various audio instruments and plug-ins.
2. The sample edtor "save selection as" has no memory of where you previously were in the file browser.
3. If you double click on a wave form, the sample editor opens up with the wave form you double clicked on... Great.. But now, if you go and double click on another wave form somewhere, it just takes you back to the sample editor with the same previous wave form selected (not great). This is incredibly annoying if you are attempting to save out certain edits-- Quite often you will end up saving 5 or 6 of the same exact waveform, thinking you were saving each individual one. GRR!
4. Key commands.. if you try to assign a key command to something that is already used by another feature, you are presented with a window warning you that it already exists.. If you click cancel, then you can no longer enter any keys in the key field.. You are forced to close the key commands preferences window and start over.
5. Key command window: You should be able to search by command.. For example, if I want to find out what "o" is assigned to, I should be able to search by O-- Further, you should be able to sort the key commands by clicking the column titles "key", "command" -- or "midi"... After all, we can sort by name, date, size, etc in the finder by clicking on these column titles.
6. Tempo Tap feature-- I am quite confused by this. There should be a simple way to tap and define a tempo. When ever i try to do this, the tempo is only temporarily changed until I stop playing, and most of the time I get error alerts about trying to sync audio and midi (mind you, when there are absolutely no parts in the entire arrange window). The manual states that with "tempo recording" checked on the tempo interpreter window, that the taps will record tempo changes, but this does not work. I tried doing this, tapping the key command I defined to tempo tap (ctrl-shift-t), and I was tapping at various speeds-- many taps fast.. and Logic recorded tempos of 99-101bpm.. I was tapping atleast around 175-180bpm. I then tried tapping slowing, and Logic recorded tempos of 99-101 again... so this feature obviously is full of bugs.
7. When loading songs, as soon as various plugins such as Kontakt, exs24 begin loading samples, it brings logic to the front. If you're working in the background in other applications while waiting for your songs to load, you are rudely interrupted from what you're doing (such as, selecting from a menu, typing a document, etc) only to be forced to watch a status bar fill up.. and then all key presses at that point become error beeps.
8. Logic's sample memory easily becomes messed up and crazy. Quite often when using AU instruments such as BFD, Culture, and even Synthogy's Ivory. I will switch to that particular track to play on my keyboard, and each sample will be full of horrible pops and clicks-- the kind that destroy speakers. Other times, in a sample of a string for instance, all of a sudden after one second will be a pop and then the sample will be playing at a completely different pitch... I have to remove the AU instrument and reload it at this point.. This happens quite often. Logic should offer a 'buffer reset' so that you can just flash plugins but they reload whatever preset they were set to.
9. Volume faders resolution are lame! There is no reason why you shouldnt be able to access +1.0, +1.1, +1.2, +1.3, +1.4, +1.5, +1.6, +1.7, +1.8, +1.9... Further the display is only so wide and you can't even read the decimal values for numbers -10 and lower. They just appear as 10.
10. When a movie is open, and you are viewing the video output via FIREWIRE, there is a mini-floating window which contains the smpte, position, and movie start information-- However you cannot modify any of these values. You have to switch video output back to "WINDOW" to change the start position of the movie. This is obviously a bug.
11. Changing the movie's start time is very user unfriendly. There should be a simple way to specify to start at a moment of time relative to SMPTE-- So you can just say "+9:15" for example, and it would take you in 9 minutes and 15 seconds, rather than how it is now where you have to think backwards from SMPTE code and subtract.
12. You cannot view video as a window AND output to firewire. There is no reason why you shouldn't be able to do this. For example, if I wanted to output my video to a monitor in a vocal booth-- I can do this.. but I can't see what the vocalist is seeing on my own screen! This is just nonsense. You should be able to output to the screen (desktop mode or floating window) as well as an external firewire device.
13. Saving a song with a movie open should mean that when you load that song, the movie should be up and exactly as it was prior to saving. As it is now you have to select "open movie again".
14. There is still definitely a bug in track automation-- this was really bad back in version 4, but there is still something not quite right here where starting playback will not always guarantee that the automation data is being read.. And in my experiences it results in volumes being incorrect until you stop and play again, and in some cases it will not work at all unless you plot some automation points. This is an intermittent issue-- but quite often activated by placing an audio region from the audio window on a track (SEE VIDEO).
WATCH VIDEO OF THIS BUG:
http://collinatorstudios.com/www/logicbugs/logicautomationbug.mov
15. In the arrange window, sometimes when zoomed in tightly, all parts on a track are selected, and you think that only the part that you are looking at is selected.. you move this part, and now all of your parts are off. Logic should have some kind of visual aid to let you know when ever you are moving multiple selections... Something like, the parts you are moving will highlight a dfferent color or something... This is a similar problem I have with the loop area of the screen.. You can accidentally turn it on when in the matrix window, and have no idea unless you look down at the transport, but with me for example, my transport is at the very bottom of the screen and I am not looking there most of the time.
16. Automation data, when two points are semi-close to each other, suddenly the value of the data is no longer shown.. I can understand that when you are zoomed out, and there is simply no space for this to visually appear, that's appropriate. But as it is now, it doesn't display this information when there is plenty of space for it to be visible.
17. Logic should let you set audio track inputs to the various outputs (1-2, 3-4, etc) and buses.
18. clicking on a track selects ALL parts. This is so so so annoying. How many times have I been editing voice over, and selecting a track, thinking I am shrinking the length of a part, and to find that ALL parts have been shrunk.. SO ANNOYING!!!! This needs to not happen, and there should be a simple way to right-click a track and it will have an option "select all regions"... also, when you click on a track and all parts are selected, if you horizontally zoom, logic zooms into the beginning of the track, rather than the song locator. I don't know what the LOGIC behind this is, but it's not very helpful, it actually is very frustrating.. Zooming should always move towards the song locator position.
19. EXS 24 should have a "reverse/backwards" button so that samples played are backwards.
20. Logic should offer a way to globally increase or decrease a specific automation type (especially volume) globally for all tracks... So if you have detailed crescendos that start at -3.8 and end at +1.6, you can add 3db to this and it will now be at 0.8 and end at 4.6.
21. If you have multiple tracks of the same track (such as three Audio track #1's)-- say you are recording guitar parts, and just copying the track and muting the previous track as a method of maintaining multiple takes for later auditioning. If you draw automation volume data on this track (it appears on all 3 tracks), and then if you delete the audio from one of the muted tracks and tell logic to KEEP it, suddenly all automation data is gone. GRR!!!
22. Several times I have opened Kontakt, and attempted to load an instrument while outputting a movie via firewire video to my monitor. As soon as I try to load the instrument, the firewire video output on my monitor goes crazy, and then comes back on.. Logic then crashes. This has happened 3 times randomly...
23. UNDO does not work on every function. for example, if you change an output to bus 1 instead of 1-2, you cannot undo this. Undo should undo whatever the last command was, no matter what it was. This is what the word LOGICal is supposed to represent.
24. Floating windows (as in plugin windows) should close with apple-w!!!
25. *BUG* If you are in a part that is say 10 measures long, zoom in horizontally 100% in the matrix window-- You then isolate one specific quarter note pitch in the middle of this measure, and have cycle turned on, looping over this one quarter note, if you are not looking at this note event/loop region when you hit play, the display will jump to the beginning of the part and never show you this note event as it loops. However if you have the note event on screen when you hit play, then it will behave properly. This makes it extremely difficult and frustrating to perform detailed hyper-draw work. (SEE VIDEO)
WATCH VIDEO OF THIS BUG:
http://collinatorstudios.com/www/logicbugs/logicloopbug.mov
26. *BUG* Host Automation is not accurate. I assigned Kontakt's tune knob to C#000, and If I place a dip, the knob begins to move way before the automation data is even present.... So basically what I was trying to do, can't even be accomplished because Logic screws everything up by pitching the instrument too early... Such a shame.. By the way, I previously mentioned the importance of being able to display part data in the arrange window as matrix data (horizontal lines) rather than score data. Someone argued what good this would do-- Well this is a perfect example, if I am attempting to affect a particular section of a note with automation, I can't possible visually see where this is because the length is not described by the current score representation. Having a horizontal representation would solve this problem... (SEE VIDEO)
WATCH VIDEO OF THIS BUG:
http://collinatorstudios.com/www/logicbugs/logicctrlchngbug.mov
27. There should be a way to convert stereo samples to mono in the sample editor.
28. When you view "as text" in the environmentt, you cannot drag an object to the arrange window-- Such as to create a bus track.. Now mind you I don't know why you can't just select "BUS" when editing a track in the arrange window in the first place, however there is no reason why 'view as text' should behave differently than when it's viewed as icons.
29. When you drag a bus from the environment to the arrange window, it replaces whatever track was there. It should ADD a track instead of replace-- atleast there should be a preference for how this behaves.
30. Occasionally when dragging a bus from the environment, there is some visual garbage in the track automation (see screenshot).
31. There should be a way to LOAD and SAVE selections in the arrange window. Quite often when editing audio from a countless number of parts/regions, it becomes painful when you have to select and move 100s of audio files. There should be a way that you can just select a ton of regions and save that selection, and reload it at anytime. There are a few 'select' tools/options under the edit window, however they are song specific-- not track specific. So they are completely usesless for what I need.
32. Logic should offer a feature to collect sysex data from midi devices so that patch names show up and can be selected via program change.
33. When no track or part is selected, and you vertically zoom in, Logic should zoom into the center most track.. It behaves very oddly and zooms in more towards the top. This becomes extremely annoying when dealing with a sequence involving 100 tracks, and a part is selected but you scroll far below where the part is.. When you begin to zoom in, it takes you towards the selected part, yet it's not displayed on the screen and you have no reference for what you are even looking at. The rule should be this: If the part is on the screen, zooming vertically will bring you to it. If it's off the screen, you will zoom into the center track of whatever is currently on the screen.
34. I mentioned this in a thread earlier... http://discussions.apple.com/thread.jspa?threadID=752485&tstart=0
There is a bug when using the transform tool involving the 'position' variable. In my example, I was attempting to reverse the time placement of three chords, that occured in a part somewhere in the middle of my song. By selecting the measure start and end of this part, Logic was unable to select or operate with the transform tool (and I tried a variety of transform options). If I moved this part to the beginning of the song, then the transform tool would suddenly work. After some research, I found online someone had said "Position Time position of the event, referenced to the start of the MIDI Region (not of the song)."--- But if I still doubt this is true, because I then placed the part on a new track with no other data, and placed it in the middle of the sequence and in the transform tool under position I selected '1 1 1 1' to '5 5 5 5' as well i tried setting the position to 'all', and none of this worked. This obviously is a bug... If it's not then it's a very serious design flaw. The position should relate to measure numbers of a song, and nothing else.
WATCH VIDEO OF THIS BUG:
http://collinatorstudios.com/video/transform.mov
That is all for now...
For those who firmly agree with me and all of the points that I have brought up now and in the past, I encourage you to contact Peggie Louie, (the Logic HR department contact) at (408) 996-1010 and suggest that she hire me as a consultant to help eliminate Logic's many annoyances. I have tried to pursue this heavily in the past, but sadly I was completely ignored by her on all levels. Maybe you all can help make a difference?
Fighting the good fight,
Patrick J. Collins
http://collinatorstudios.com

11. Changing the movie's start time is very user
unfriendly. There should be a simple way to specify
to start at a moment of time relative to SMPTE-- So
you can just say "+9:15" for example, and it would
take you in 9 minutes and 15 seconds, rather than how
it is now where you have to think backwards from
SMPTE code and subtract.
For this one I'd suggest getting SMPTE calculator. Entering timecode numbers and having to add and subtract is not so difficult, and AFAIC part of a composer's gig. But what I would add, instead, is that it would be fantastic if Logic provided a timecode calculator (edit: even if it was in the form of a custom Logic widget).
13. Saving a song with a movie open should mean that
when you load that song, the movie should be up and
exactly as it was prior to saving. As it is now you
have to select "open movie again".
This doesn't always happen. I've struggled with this for a long time, and I don't know why sometimes the movie will load and not other times. I would also add here that Logic should show the file pathname to the movie. Somewhere...
18. clicking on a track selects ALL parts. This is
so so so annoying.
You can prevent this from happening if you have cycle turned on and set to a set of locators that "contain" the parts you might want to select en masse. I always work with cycle=on so this is not a problem.
21. If you have multiple tracks of the same track
(such as three Audio track #1's)-- say you are
recording guitar parts, and just copying the track
and muting the previous track as a method of
maintaining multiple takes for later auditioning. If
you draw automation volume data on this track (it
appears on all 3 tracks), and then if you delete the
audio from one of the muted tracks and tell logic to
KEEP it, suddenly all automation data is gone.
GRR!!!
Never had that happen. In my experience, telling Logic to keep the data always works.
23. UNDO does not work on every function. for
example, if you change an output to bus 1 instead of
1-2, you cannot undo this. Undo should undo whatever
the last command was, no matter what it was. This is
what the word LOGICal is supposed to represent.
Undo in Logic is highly problematic for other reasons. Here, I think there should be a specific Environment Undo, just like there's a separate undo for audio edits.
29. When you drag a bus from the environment to the
arrange window, it replaces whatever track was there.
It should ADD a track instead of replace-- atleast
there should be a preference for how this behaves.
Right. This is a matter of personal preference. But still there are other ways to get an object assigned to a track. The "thru tool", for instance. No dragging required.
32. Logic should offer a feature to collect sysex
data from midi devices so that patch names show up
and can be selected via program change.
My guess: considering how much sheer time it takes to write this kind of software, let alone debug it with every conceivable device, it's not likely this is going to happen.
That is all for now...
For those who firmly agree with me and all of the
points that I have brought up now and in the past, I
encourage you to contact Peggie Louie, (the Logic HR
department contact) at (408) 996-1010 and suggest
that she hire me as a consultant to help eliminate
Logic's many annoyances. I have tried to pursue this
heavily in the past, but sadly I was completely
ignored by her on all levels. Maybe you all can help
make a difference?
Wait in line buddy!
(LOL)
I must say, I'm very impressed with your list and attention to detail. And I feel your pain, trust me. But many of the things you've listed are feature requests and not bugs. And some of the behaviors you've described I have yet to run across. So this is typical with Logic, that it can be operated in so many diverse ways that no two people run it in the same way, nor would two people conceive the program's capabilities in the same way. But I digress...
I also think there's a certain amount of Logic convention that I don't think you've adopted yet, hence your wish for behaviors that don't yet exist.
I don't disagree with most of your feature requests, and I'm (quite unfortunately) able to say that I'm familiar with most of these bugs and about 9 dozen more. But again, it's important to distinguish between bug, feature request, time to RTFM, and errant behavior that's experienced by a very limited number of users.
There's no doubt that this program has its problems. In particular, your #1 re the playback buffer. And I'm glad you've brought many of the bugs into the light for people to read. Good work.

Problems with Logical Components

Hi All,
I am having problems with Logical Components with our project. We are implemeents SAP HCM and we have defined a logical component Z_ERP for the ECC server. now when you look at the transaction from SOLAR02 it seems they also have a logical Component SAP Learning Solution that is assigned to them. what could be the cause of this???

Hi Trevor,
If you brought them in from the Business Process Repository, the logical component is going to be the default one. If you want to use your own, you need to replace the default one with yours.
You can do this in SOLAR_PROJECT_ADMIN by going to the System Landscape tab > Systems tab > highlight the SAP Learning Solution logical component row > press F4 > replace it with Z_ERP.
If for some reason SAP Learning Solution isn't listed as a logical component you may have to add it, you can also just go to SOLAR02 > Edit > Replace Log. Comp > Enter SAP Learning Solution in the top box and Z_ERP in the bottom one > click Save.
regards,
Jason

Problem with Logical Database DDF

Hey All,
I have a problem with Logical Database DDF.
In my program I am typing this
GET KNA1 based on selection screen. It is bringing back everything I want except BRAN1 whereby the field is ''. However in SE16 for KNA1 and for the same KUNNR, the field is populated with 'T180'
I am not understanding this?! I thought LDB where menat to make things easy!!

I think it's not used by DDF.
so you must check it with:
check kna1-bran1 in s_bran1.
A.

Problem with logic:equal tag when used with bean:write

Hi All,
I have a problem with logic:equal.When i tried to use the following piece of code its not working
<logic:equal name="var in session" value="<bean:write name='var in request'/>">
Do some thing
</logic:equal>
its not working i know we cant use nested tags
is thr any alternative instead of using a scriplet

A scriptlet expression is about all you can do.
<bean:define id="tempVar" name="var in request"/>
<logic:equal name="var in session" value="<%= tempVar %>">
...If you have a JSP2.0 container with EL enabled, then you could use an EL expression instead of the standard <%= expr %>

Problem with Logic 9 and Alesis MasterControl

Hi!
I have a problem with the faders on my mastercontrol becoming unresponsive, after a few minuttes of use, have anyone else experienced this?
Logic doesn't respond to changes made on the controlsurface and the control surface doesn't respond to changes in Logic.
All software and drivers are up to date.
/Jan

I've been having trouble with it since I installed the snow leopard drivers…
my faders didn't react to anything anymore
also my macbook kept crashing when i turned the mastercontrol on…
the only way to make sure it doesn't crash is to turn it on before i start my computer…
didn't have any fader problems since i've changed to logic 9 though…
do you get a panic report of some sort if you restart your computer?

Problem with Logic 8 and Ik Multimedia's CSR

I am having a strange problem with Ik Multimedia's CSR and Logic 8. I installed CSR on my computer. It is listed in the Audio Units manager. For some reason, however, CSR is only showing up in one saved Logic project --- when I open up any other project or start a new project, CSR no longer shows up. I have trashed preferences, reloaded all AUs, etc... I am stumped. Any suggestions?

Aside from having the proper version, make sure you are trying to open CSR onto a STEREO channel strip. Otherwise, it won't be available from the AU pull down menu.

HT4623 Update problem? Fade in and out while updating

As I was updating the phone to iOS6 there was an error. Now the phone just fades in and out with the start Apple symbol and there is no way to shut it off.

If the ISP modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems: Link>http://www.practicallynetworked.com/networking/fixing_double_nat.htm and http://cognitiveanomalies.com/cisco-nat-how-nat-works/. If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ.
I recommend that you phone contact your regional Linksys support office and ask for help and information regarding this. Or [email protected]
Let us know how it goes please.

Problem with Logic Pro and Soft eLicenser on Mountain Lion?

Hi!
I have a bunch of Arturia synths, which requires the Soft eLicenser to work. This has always worked great with Lion, never any problems with eLicenser (never had to open it etc.)
Now - I upgraded to Mountain Lion, and tested my synths to make sure everything was OK, experienced a bunch of problems, and did a full recovery to clean Mountain Lion.
After installing the Arturia synths, and adding my licenses, I installed Logic. Everything worked fine!
BUT!
When I closed an Arturia synth within Logic, or closed Logic after running a project with one of these synths, I couldn't reopen any of these synths within Logic afterwards - In fact, I couldn't open the stand-alones either! And when I tried to open the eLicenser Control Center, it would just say "Reading eLicensers" forever. After a reboot, everything is OK.
I can open and close eLicenser Control Center and standalone synths as many times as I want, as long as I don't open Logic, and then Arturia synths as an AU in Logic.
I found a workaround: Open the eLicenser Control Center, and let in run in the background (cmd+H), and then open Logic. Then I could open Arturia synths and close them, close Logic and reopen etc. without any problems at all. NO PROBLEMS.
Until I close the eLicenser Control Center, then I have to reboot to be able to start it again.
I hope you understand what I mean here. It's a bit hard to explain.
In short terms: Logic makes Soft eLicenser crash when a eLicenser synth has been opened as an AU.
The same problem is when scanning the AU with AU manager. eLicenser window should be open before scanning.
Does ANYBODY have the same problems? Can anyone who has these applications test it out?

So it definitely seems to be a issue with Logic.
I can't force this error in 10.7.X no matter how hard I try, but in 10.8.2 it's definitely Logic messing things up.
Could it be auvaltool which has a bug? Or is that only run with AU manager on validation?
Hopefully this discussion can get some attention, and maybe it could be corrected. I guess a lot of Logic Pro users also has eLicenser Control Center for validation of their products.

Tcode BDLS and BDLSS problem with logical system names

Hello!
I have following problem.
During the SAP ECC 6.0 installation we have forgotten to give the clients the logical names.
Now, during the customizing it is necessary to have all the tables with logical names, so I have given for all the systems a logical name.
Now I have problem to convert all the tables that were customized without logical to such with one.
<b>Is there some (semi)-automatical mechanism to do this or should I go to the SE16 and do it there?</b>
Thank you very much indeed
regards
Thom

Hi,
You need to do it from SE16 or SM30
Regards
Sudheer

Problem with logic 7.2 and digi002 with latency

Hello,
I have a G4 mac mini with Logic Express 7.2 and ProTools 7.1. and a Digidesign Digi002 Rack.
The probem I am having is that when I set my buffer sixe in PT everything is fine. I can set it down to 64 or even 128 with no latency.
But when I set up by buffer size in Logic I always have latency issues, even when I set it down to 64.
Does anyone know why I am having these problems.
Is it an issue with the Digi002, do I need a firmware update or something?
Any help will be much appreciated.
Thanks in advance

Hello,
I have a G4 mac mini with Logic Express 7.2 and ProTools 7.1. and a Digidesign Digi002 Rack.
The probem I am having is that when I set my buffer sixe in PT everything is fine. I can set it down to 64 or even 128 with no latency.
But when I set up by buffer size in Logic I always have latency issues, even when I set it down to 64.
Does anyone know why I am having these problems.
Is it an issue with the Digi002, do I need a firmware update or something?
Any help will be much appreciated.
Thanks in advance

Compatible problems with Logic 9.1.6 and 96 i/O Digidesign

Hi There,
I am on Mac OSX 10.6.8.
When loading Logic, the 96 i/O displays various signals on the input channels and for some reason, I can not use the dsp card of the interface with Logic on the DAE page and the signal are still continuous with selecting HD in and out in the Core audio page of logic...
Thanx for your help.

By perseverence if not gnius I cracked the solution
Heres what I did
I UNCHECKED 'Ignore Ownership on this volume' and selected 'Apply to enclosed items'
Took about 10 mins (I have about 300GB of samples)
Any ideas WHY this worked

Constant problems with logic 8 (only in last 2 weeks)

Hi,
I've been using logic pro 8 since the day it came out, and have had hardly any problems with it.
Now all of a sudden it is crashing all the time, sometimes it just totally loses sound and my monitors just click and pop, or other times i get random 'blasts' of white noise through my left monitor!!
I put snow Leopard on a few days ago and it appears to be worse than ever for crashing now.
Anyone else had similar problems or know what the deal is here?
Many thanks
Tom

John Alcock wrote:
Interesting. There are many reports of this noise, but all (AFIAK) with Logic 9, not 8. I've had the same problem with LP9 but haven't with 8.
http://discussions.apple.com/thread.jspa?threadID=2144002&tstart=200
See if there's anything in that thread which helps.
Today I had this white noise bursts for the 1st time since I upgraded to LP9...the project is super simple...an audio track - flexed and muted ...and the bounce in place regions created from that on a second audio track...I was doing some fades so I was moving back and forth to the regions to listen and adjust the fades...
It's really loud and I'm glad I wasn't wearing headphones...
I check the link you posted ......
A

Problem with logic pro 7 & jam pack

Hello,
first sorry me for my english....but I need help
I'v a big problem with my jam pack.
1/
when I want to hear some loop with the navigator loop, the sound is deformed like with a tremolo and a reverb...
when I take a midi loop and I put it on my arrangement the sounds is ok
It makes the research of loop very difficult(it does'nt sound right).
2/
I've the same problem in the navigator loop with the audio loop.
But when I put it in my arrangement the sound isn't ok (deformed, tremolo...)
On the other hand the deformation disappears when I put a faster tempo
(around 100 bpm)
Precision; my arrangement is at 50 bpm
Thank you so much for your help
g5 Mac OS X (10.4.9)

hi, you are play the loop back too slow.
there's a limit to how far a loop may be slowed down.
apple loops are generally played back via the last audio channel available, whether you are using in your song or not.
check this channel to see if it has effects inserted or is using the bus sends. if so, switch these off to hear your loops properly.
DR9

Problem with Fader Banks and Channel in MCU PRO with Logic Pro X

Similar Messages

Maybe you are looking for