Logic Control issues again!
Details and history:
Emagic Logic Control---used to work just fine in Logic 6 and then started acting up on Logic Pro 7.
All faders and buttons work just fine. But from time to time, the PLAYHEAD jumps forward and keeps doing so. At this time the Stop and Play button lights also keep turning on and off and the SCRUB and ZOOM light come on at times too.
Rebuilding defaults does not help.
Then randomly, it starts working perfectly and might do so for hours. Very moody!
Logic Control is connected to AMT8 and is the only external midi device in my setup currently. Previously i had a Yamaha Motif as well and it would work just fine.
On Logic Pro 9.1.1, the same random behaviour, its like a cd skipping when music is playing so only solution is to turn it off. Rebuilding defaults helps at times, other times it does not. I did check/uncheck TOUCHLESS FADER option, one time it worked, other times it did not.
I updated the LC firmware to Mackie Control a few months ago. With Logic Pro 7, it greatly reduced the SEIZURES, not curing it completely.
On a PC with Presonus Studio One, it worked great, had one seizure in months, rest was awesome.
I tried booting it up on Logic Control mode night b4 last, and selected Logic Control in preferences/setup and deleted mackie control. No help.
Reverted to Mackie Control mode and things were great last night.
Today, madness again!!!
How do i diagnose this, is it hardware failure ? An issue with the AMT 8 ??
BTW, on the PC the mackie control was connected to the midi I/O of an RME card.
Today i will try connecting it via an Evolution UC33 and see if the AMT is the culprit.
Any help please ?? At this point i am seriously thinking about ditching this for a Euphonix MC Mix......but i'd rather save the cash and find a solution.
Sorry about the long post, i just want to be able to work.
Thanks
Faisal
Ok its working great now, at least for now. No SEIZURE!
Steps:
1. Delete Mackie Control or Logic Control from setup.
2. Trash preferences.
3. Boot up in Logic Control mode
4. Re-Scan.
5. Check TOUCHLESS Fader if need be.
All good. However, these steps don't always work!
Will keep u posted.
Thanks
Similar Messages
-
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? -
Any one have issues with a Logic Control surface with the new LP8?
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 -
L8 is seeing my Axiom as a Logic Control and it's wreaking havoc!
A new twist on all the control surface issues - I have a M-Audio Axiom 25 connected via USB and it's not setup in anyway as a control surface via the control surfaces preferences. I have never used it as such and never need to because I own a Logic Control.
All of the sudden, L8 is recognizing midi note input from the M-Audio as LC input - i.e. if I press an A3 it doesn't sound a midi note, but rather performs a specific Logic Control function as defined in the Key Command Preferences.
Of course, it's even worse because I have an Apogee Ensemble so Logic doesn't even recognize a potential Control Surface unless everything is powered up in just such a perfect way.
So I have a Logic Control that isn't recognized, and an Axiom 25 that is recognized as something it's not and if I go to Control Surfaces preferences, it's as if the world of cotrollers doesn't even exist because the master list of options is gone baby gone.
Anyone find a workaround for this?totally different ports!
The LC is connected via my AMT8 - the Axiom is on it's own port via USB, so that shouldn't be issue.
I've tried cabling the Axiom port directly from the input object to a monitor and then terminating the connection just so I can see what it's transmitting - the "bad" notes don't show up as anything in the monitor and even though I've broken the Sum cable from the input object and the Axiom port is only cabled to a monitor and nothing else (the Sequencer input is not connected to anything at all!), L8 is receiving those key presses as LC commands.
So strange -
Emagic Logic Control firmware install file Logic 8 pro
Can anyone help by telling me how to install the firmware on my old Logic Control. I have tried to run the Mackie midi update and now the Logic Control will not boot, I thing the firmware has been damaged. Emagic used to send a .mid file does anyone have it? I was burgled and all my software discs were taken. Please help if you can.
its not showing in my audio midi set up - but never has previously...but the device it connects via does show up - From what was said in the quick start guide, you only have to add it as a control surface within logic...Where logic already has the relevant driver; waiting to be selected from a list...As for updating anything; I havn't touched a thing. It was literally a case of one day, everything worked; the next day it didn't - mackie said logic had made a corrupt preference file (user/whatever your user nameis/library/preferences/logic) that their would be a file named should be something like
(Com.apple.logic.pro.CS) which there was, and to drag the file to the trash then restart the
computer...This did work to an extent; the 'v-pot' part of the control which had stopped working came back to life and everything now works fine...accept the jog/timeline issue...
I have added it in Audio Midi set up...in the hope that it will help - What properties should I set it to have? anything special - Appologies for seeming dense, I just make music; normally things just seem to have worked! And my technical knowledge is somewhat lacking im affraid.
Thanks for your help - it really is appriciated
Dave -
Emagic Logic Control jog wheel...
My logic control is was working fine; and then poof - No v pots and no jog wheel - mackie suggested i delete a preferences file; which has bought my v pots back to life...However the jog wheel and the timeline still misbehave...
The line skips back and forth between a couple of bars...and moves forwards jumping backswards and forwards if i spin the wheel really quickly...if, when the line is further into the track i move the jog normal scrolling pace it runs the line backwards towards zero; speed it up and it jumps all over the place.
I rang apple but the wanted to charge me £144.99 for phone advise - so im begging someone here to help me if you can...
Many thanks Daveits not showing in my audio midi set up - but never has previously...but the device it connects via does show up - From what was said in the quick start guide, you only have to add it as a control surface within logic...Where logic already has the relevant driver; waiting to be selected from a list...As for updating anything; I havn't touched a thing. It was literally a case of one day, everything worked; the next day it didn't - mackie said logic had made a corrupt preference file (user/whatever your user nameis/library/preferences/logic) that their would be a file named should be something like
(Com.apple.logic.pro.CS) which there was, and to drag the file to the trash then restart the
computer...This did work to an extent; the 'v-pot' part of the control which had stopped working came back to life and everything now works fine...accept the jog/timeline issue...
I have added it in Audio Midi set up...in the hope that it will help - What properties should I set it to have? anything special - Appologies for seeming dense, I just make music; normally things just seem to have worked! And my technical knowledge is somewhat lacking im affraid.
Thanks for your help - it really is appriciated
Dave -
Logic Control Working Properly anyone?
My logic control has not been working properly for a while.
It does most things fine but it does not do the following:
1. The Automation buttons don't do as they are supposed to; Pressing Latch, Touch or Write just enables READ mode.
2. Pressing the Down Arrow button Enables Send #8- It's supposed to scroll through the sends 1, 2, 3, 4 etc.
3. The Rotary pots for Send/Pan when turned send the Send/Pan paremeter to either 0 or 127!!
That's most of the problems. There may be more but I would really appreciate any help on this.
Thanks
FelixIf you are working in 64 bit mode, i think i can help, as i had the exact same issue.
1. Quit Logic
2. Trash the Control Surface Pref file "com.apple.logic.pro.cs"
3. Go to The Logic application - go Command-I to open up its information pane. Click the button to open Logic in 32-bit mode.
4. Open any Logic file.
5. Confirm that your automation buttons now work correctly
6. Quit Logic.
7. Go back to the information pane. De-click the 32-bit button
8. Re-opn Logic in 64 bit mode. You should be all fixed.
HTH -
Logic Control broken by Logic Pro 8
My Logic Control, which has worked fine from Logic 5 to 7, now in Logic 8 has become almost inoperative.
1. the "save" button no longer works. It should not need assigning, according to the Apple Logic support guy, who is getting the same problem with his Logic Control. No solution yet.
2. the track display behaves erratically. When moving a fader, that track suddenly reads "volume" in the display, and won't go away. the track next door to the right of it immediately loses its name. Normally, this would never happen. the track is restored to semi-normalcy by pressing the "zoom" button - which, far as I know, is not the function of the zoom button, anyway.
Tried deleting and reinstalling Logic Control in the Control Surfaces prefs. No change.
Just thought I'd post this in case anyone out there is experiencing the same, and, hopefully has come up with a solution. helpambient8 wrote:
I'm not denying that. I am quite aware that Logic 8 has issues. Being factual is important though. Especially when bringing credibility into question. If Logic causes you so many problems perhaps you should consider migrating to a new DAW. Gotta be able to enjoy your work. Pro Tools 8 looks quite tempting to me actually.
Cheers
Factual is every bit as important as literate.
I use Logic 7. In Logic 7 the control surface works perfectly, the audio output is not corrupted at the 2nd bit and all of the audio configuration functions are intact. None of this is true in Logic 8.
And please note that by saying that logic 8 is causing "me" so many problems you imply that these are not real issues, but apple have admitted to these issues and done NOTHING for "6 months".. Am I supposed to use defective software or do my job?
So please tell me why did you advise me to ditch Logic 8 (which I have stated that I DO NOT use) and moving to another DAW? -
My Logic Control is going mad. It keeps flicking the PLAY/STOP buttons automatically and the rulers keep jumping forward making the control surface useless.
Someone asked me to check if the Logic Control was receiving these commands to make sure it was not a hardware issue. I am not so savvy, can someone please offer any help in diagnosing the problem, please.
Thanks
FaisalI am told to "Disable the Mackie Control/Logic Control as a midi
controller". I don't know what this means. I have tried removing
it from the control surfaces setup but no luck
From the instructions you state, that's what I'd infer from them.
When I play the midi file I get nothing. The logic control stays
in "Waiting for MIDI upgrade" mode but no update.
Where are you playing to MIDI file to? You sure you're playing it to the MIDI port that the LC is on, and that your interface isn't filtering sysex data? -
Hi,
I'm surprised at the lack of outrage over the terrible state of the Logic Control unit implementation in Logic Pro . With earlier versions of Logic I found using the LC unit a delight, recording and mixing several projects with it. Now (8.0.1) it's simply not worth using. I've tried all I know . . . rebuild defaults, trash preferences, re-install the unit, build a new autoload template (even Logic's templates don't work any better in this respect). Global mode doesn't work and track selection is a problem in any mode. One exception: if you're content with using the up/down arrows on the LC for track selection it works better . . . even in Global mode . . . it will actually put a track into Record and not mention the dreaded "Automation Folder"! Apple has stated that the unit is "behaving as expected". Mackie advised me to check for double .cs preference files(there weren't). Nobody said "Oh yeah . . . it's a problem". Either the issue isn't as widespread as I imagine or the relevant companies are not aware of the problem. This unit wasn't cheap. I paid $1764.00 Canadian when I bought it. It was worth every penny at the time, but now it looks more like a non-usable piece of metal that cost over three times more than the software (LP8) that appears to be crippling it.
What gives?
RWYep, I'm amazed at how broken it is in LP8, both major and minor issues. It's like nobody tested the MCU when they'd reworking the GUI and other stuff for LP8.
I've certainly reported this as a bug, so it's not like they aren't aware of it. I really hope they are tackling all this stuff (as well as all the other stuff) for an update soon... -
Logic Control erased firmware problem
I'm using an Emagic (Mackie) Logic Control version 1.0 with Logic Express 7.1 and tried to update it to version 1.02 this afternoon. Whoops! It gets halfway through (the dots dash along the LCD as they should) and then it displays "Update Failed!!! - (Error Code 1) and that's as far as we get. If I then switch it off and back on again I get nothing - just a blank screen. Logic no longer recognizes it either, so I'm guessing that it has erased the firmware, but because it won't load the new firmware I'm effectively left with a wedge shaped doorstop!
Anyone got any ideas?
Many thanks!A suggestion from the Logic User Group:
http://logic-users.org/forums/LUG/thread/80451
Hope this helps.
cheers
rob -
Logic Control - XT display not resonding, noise coming thru midi....
I have a Logic Control and a Logic Control XT. XT on left, channels 1-8. Display on XT lights up, but doesn't recognize tracks (faders and other controls, do however).
"Midi in" on XT causes noise in my monitors (don't tell me it's impossible because midi sends 0 or 1 -- it IS causing interference in my monitors). Can bad midi cables or a bad midi interface cause noise?
Is my set up somehow incorrect?I have a Logic Control and a Logic Control XT. XT on
left, channels 1-8. Display on XT lights up, but
doesn't recognize tracks (faders and other controls,
do however).
So everything works, but you get nothing on the display? When you power it up, do words come up on the display then (like a "Logic Control XT" welcome message?)
If not, perhaps the display has died?
"Midi in" on XT causes noise in my monitors (don't
tell me it's impossible because midi sends 0 or 1 --
it IS causing interference in my monitors). Can bad
midi cables or a bad midi interface cause noise?
You might have some kind of ground loop issue, which seems unlikely seeing as MIDI cables don't have a direct electrical connection.
It may be that your computer causes interference when sending MIDI (nothing to do with the Logic Control). Early motherboards, for instance, gave audio problems when using USB MIDI - I had an old motherboard which gave clicks in the audio drivers when sending MIDI via USB, which is why I used the serial bus MIDI instead, and that solved the problem.
Is my set up somehow incorrect?
Difficult to tell from just the info you provide! -
Here is a little history:
Bought an iMac G5 1.8GHz in February of 2005. In October of 2005 I had the power supply and logic board replaced. In August of 2006 I had the logic board replaced again. In July of 2007 I had the logic board replaced AGAIN...
I am once again having issues with what I think is a faulty logic board. I had a "Must Restart" grey pop-up yesterday. Did an SMU reset, then restarted the computer. It worked for 24 hours. This morning it did the same thing. I restarted, but it went to a blue screen and stayed there... I did a SMU reset, and a PRAM reset. Then called Applecare and they hinted I should do a disk repair with the install disk... Tried that. The computer won't boot from the disc when pressing C on startup... just goes to Blue Screen after grey apple screen and freezes.
I tried starting up whilst holding the "Option" button. Both the Macintosh HD and OS X Tiger DVD are found, but once again, it won' boot from either. Just to the Blue Screen and that is it.
I am over 3 months from my logic board replacement time frame... besides, I think the last replacement of it should have taken care of it last July, right? I have opened up the computer, and there are 5 leaking capacitors...
I am right in thinking the Logic Board is fried, right?
What would you suggest doing? Trying to get another logic board for free from Apple, even though I am beyond warranty? I DO NOT want to pay 800-900 bucks for sure. Any other tips or suggestions? I figure I could get a SATA/USB2 enclosure for the HD if I get another mac... not to mention I am a pretty good back-upper...
Thanks!!!I have a first generation 20" iMac G5; the logic board failed about a year ago and was replaced under the "iMac G5 Repair Extension Program for Video and Power Issues" program at my local Apple store. It failed again last week; I returned to the Apple store and was advised it would not be covered as it has passed the 3 year mark outlined in the program and was offered a 20% discount on purchasing a new iMac (I did not feel this was a reasonable resolution). I contacted AppleCare via telephone regarding the issue as I felt Apple should support a product with a well documented defect. The "Product Specialist" I spoke to stated "my original logic board had been replaced with an updated one" and "the failure of this current logic board is unrelated to the Extension program failure". He then went on to contradict himself and stated "Apple could not / would not continue to support the logic board failures after the 3 year mark". I was offered no resolution; I am a long time Apple supporter, advocate and evangelist who has advised friends, family and colleagues to purchase Apple products. I am now extremely hesitant to do so after this incident. As this is a recurring and well documented issue with this product, I feel Apple should either replace or offer a replacement iMac at a HIGHLY substantial discounted rate to any customers impacted by this product. Hundreds of posts here and at other forums show there are many unhappy customers.
<Edited by Moderator> -
Anyone having volume control issues? My wife's 5s (less than a month old) is having issues with the up volume. If she mutes it using the down volume, it won't go back up. I can get it to work if I hold the volume a long time and it eventually comes back. Or last time i had to remove her case, hold the volume and release several times before it finally kicked in. Any thoughts or ideas? Thanks.
Hi,
Please test in other computer to see if the issue persists, it may be caused by the bad output channel.
But for better solution, I recommend you go to MSDN forum for further help.
http://msdn.microsoft.com/en-US/
Thanks for your understanding!
Regards,
Ada Liu
TechNet Community Support -
Hello I have fundmental question to ask;
In Struts or JSP page, you can use logic control to determine what will display. For intance, the tag on strut <logic:match> <logic:equals>. I am wondering how to have this sort logic in JSF. Thanks!Thanks guys!
the simple solution is what you said:
in JSF page, binding rendered to a propertity in the bean. on the bean create the property - method to have the logic to return true or false. Do you think if it is a better solution than using jstl -- I dont know too much JSTL - I am more service side developer such as proxy service, application server to host tcp connection from clients...
Maybe you are looking for
-
I realized this morning my iPod Touch was not charging. I left it charging all night but nothing. I read i have to reset it, but since now is fully uncharged, it does not allow me to do anything... I tried to charge it with all possible resources (US
-
Problem identifying db object for "buffer busy waits" event.
10.2.0.3 AIX 64 SELECT username, a.p1text, a.p1, a.p2text, a.p2, a.p3text, a.p3, event FROM v$session a WHERE a.status='ACTIVE' AND a.event = 'buffer busy waits' Query reports about 40 active sessions with this information: file# 3746 block# 2 class#
-
Please HELP ME !! Ever since I updated my phone to the IOS7 it has not allowed me to have push notifications on any apps. It states that I must go to itunes to get push notifications. However, I go to itunes on my phone it is just the store, I go on
-
I have a requirement where in i have to display a pop up with all the line items given by user in ME21N . The pop up has to display when user presses CHECK . I written the code in the exit EXIT_SAPMM06E_017 . its working fine for single line item. In
-
Make USB flash drive unreadable
I want to make my USB flash drive unreadable, but I don't know how to do it. I can only find threads about problems with unreadable drives, but I don't have a problem, I want to make it unreadable. Is there a way to do it (like OS X can't read NTFS,