Warping IMac Facia

Has anyone noticed any strange gaps appearing between the LCD display and the white casing? I noticed a 2mm gap in the bottom right hand corner, no problem with the display as such, purely a cosmetic problem!
Popped into my local PC World and looked at another 17" IMac. It had same problem, not in the same place but in the middle of the bottom section! Is this due to overheating???
17" Intel Imac   Mac OS X (10.4.7)   As Standard (At The Moment)
17" Intel Imac   Mac OS X (10.4.7)   As Standard (At The Moment)

"Is this due to overheating?"
No, there is no overheating. It's poor workmanship. I believe I read that it can be adjusted or fixed. Take it back to where you got it and try to get them to fix it or replace the plastic frame. I assume it's an actual gap, not an optical illusion that makes it appear there's a gap?

Similar Messages

  • 24" iMac displaying small green lines

    I'm having a big problem with my iMac 24" when I'm using Aperture or iTunes music videos in full screen mode.
    I am getting groups of little green lines about an inch long and a pixel or two deep, stacked in groups of five or six on top of each other like a small wavey flag. These little "flags" are spread all over the display and make for one annoying interuption of either the video I'm watching or the photos I'm editing in Aperture.
    Sometimes when I'm scrolling through my shots quickly in Aperture the lines become much larger and then red and blue blocks of lines appear, they disappear again when I give the scrolling a rest for a minute or so.
    I'm using 2Gb RAM, the 9600 graphics card and all my software is bang up to date.
    Any ideas any one?
    John
    Cheers
    iMac 24'   Mac OS X (10.4.8)   2GB RAM, 256Mb,

    Clean erase and reinstall to factory conditions did not help with the graphic corruption/glitches.
    Here are the actions I've performed so far:
    •Got iMac on Tuesday (three days ago) and proceeded to immediately install all updates, including the EFI 1.1 firmware update
    •Installed Aperture, the problem started showing itself sporadically
    •As I imported more and more Aperture projects the problem started getting more widespread, it started showing up in Dashboard (problem is equal on both internal and external monitors)
    •World of Warcraft started showing the flags/squares/lines in the menus, as well as major geometrical corruption in the 3d views (planes intersecting the world, characters warping, etc.)
    •Reset SMC (unplug all cables, wait 15 seconds, plug back in without holding power button)
    •Reset PRAM/NVRAM (several times)
    •Ran without any software in background
    •Ran Memtest (5-pass, single user mode for max available RAM) all tests passed
    •Ran Apple Hardware Test three times, once the standard test, twice the extended, none show any errors
    •Wipe drive, reinstall from restore discs, no updates installed whatsoever, no additional software installed, and it still exhibits the error inside of PhotoBooth, just as it did before, and just as it did for Janet in the post I link to above. PhotoBooth seems to show the most artifacting when the effects are turned on.
    I'm taking it in tonight, we'll see what they say. I will keep this thread updated with my actions and any responses I receive.
    One thing I feel I should mention is that I don't think it's Aperture's fault. It's just the main indicator for us since we all use it and it makes heavy use of the GPU.
    Also, my problem started out small and got bigger over the 2/3 days I was using the machine, indicative of a developing hardware issue. If it was a software glitch, it would be less likely to behave that way.

  • Please help: installing FP 10.3.183.90 on iMac 10.5.8

    Attempting to download Flash Player 10.3.189.90* on an iMac using Leopard (10.5.8); after multiple tries, have gotten to a point at which clicking the Install icon opens a window asking if I want to install (considering this a victory; something is happening, at least!); then, when I choose Open, it immediately “quits unexpectedly” and offers me the chance to relaunch.  So I relaunch, choose open, and it quits (not so) unexpectedly again.  (Rinse and) repeat, presumably ad infinitum.  Help?  (prefer to stay with 10.5 rather than move to 10.6)
    *computer owner clicked on general software update without paying attention, after which there were problems with YouTube videos that had not been there previously (video area shows “missing plug in”, which changes to request to load most recent Flash Player—but the Intel iMac is running 10.5.8, with which the owner, not a computer expert, is comfortable; he prefers NOT to go to 10.6—how can we just restore what was?) (Library contains a Flash plug-in dated Oct. 5, 2013; removing it form the Library folder did nothing.)

    I wasn't trying to be insulting. The REALITY of the situation is this:
    OS 10.5.8 was the ONLY "Universal Binary" OS Mac EVER Released, and they ONLY did so because they were in a transition from PowerPC processors, to Intel. PowerPCs ran hot and IBM REFUSED to make the necessary changes to them so that they could keep up with changes in technology that were necessary for Apple to stay competitive in the marketplace. Thus the switch to Intel (faster and cooler) processors, which allowed Mac to become the dominant force in computing they are today, but then you probably KNOW all that already.
    Unfortunately, there were a lot of people who still had PowerPC Macs in 2005 and they wanted the latest OS for them so Mac made 10.5 a "Universal binary" as a concession. It was NEVER intended to be a "lifetime OS, because it was meant to run on an architecture that Apple was going to abandon, which they did in 2009. Thery no longer support ANYTHING Power PC - hardware or software. There are people who paid thousands of dollars for Final Cut video editing software for OS 10.5 and if something goes wrong with it, you know what Apple tells them? "Buy a new Mac and get the new "Intel" version of FInal Cut, but we won't lift a finger for it on THAT system."
    Backward compatibility has nothing to do with this. Providing backward compatibility for OS 10.5 now would be NO DIFFERENT than developing new software for OS7. They aren't going to do it - NOT because they want to force everyone to buy a new Mac, but because the architecture that the OS was designed for is obsolete and they no longer support it because it HASN'T been manufactured in EIGHT years. It's gone the way of VHS, phonograph records and 8 track tapes.
    THAT's what I meant by reasonable, logical and sane regarding the upgrade. Trying to force the entire computing world to "time warp" back eight years because a user is too stubborn to upgrade is unreasonable. Expecting that ANYTHING in computing will remain current, or updatable for eight years or more is illogical, and demanding companies invest hundreds of thousands of dollars to continue support for obsolete hardware and OS's when there's a $20 upgrade that will eliminate the problem... is anything but sane.
    As far as upgrading from 10.6.8 to 10.8... it's NOT as simple as one might think. There are ONLY so many Macs that will run the OS, and THAT'S no different than Windows. A six-year-old PC isn't likely to handle WIndows 8 or even 7.

  • New Mac Pro 8-core / D700 not much faster than an iMac... in PPro CC.

    So.... my very preliminary testing with our new Mac Pro using the plugin I use most (filmconvert -FC) anyway, shows that Premiere CC needs more optimization for the dual GPUs. In fact, I'd say the CPU utilization is not up to snuff either.
    I know FC only uses one GPU presently from the developer. That will change. In the meantime, using a couple of typical projects with that plugin as an example, I'm only seeing 25-45% speed up in renders over our maxed out iMac (late 2012, 27") exporting the same project. That's significant of course but not the 100%+ one would think we would be seeing at the least given the MacPro config of 8 cores and dual D700s. Premiere Pro CC seems in fact to never maximize CPU (never mind GPUs). I have yet, in my very limited testing, see it "pin the meters" like I did on the iMac.
    Of course that's just testing now two short (under 5 min) projects, and it depends on what one is doing. Some stuff is much, much faster like Red Giant's Denoiser II or Warp Stabilizer VFX. The improvement there can be 3-4x faster anecdotally.  I used to avoid them for speed reasons unless absolutely needed a lot of the time but now they are fast enough to rely on quickly. Other stuff unrelated top PPro CC like DxO PRIME noise removal on RAW stills is much faster too, as is Photoshop CC.  Some effects like blur, sharpening, resize there are nearly instant now even on giga pixel files in Photoshop CC.
    And of course FCPX is much faster on it but I hate the whole editing paradigm. The timeline is just horrid on it; simple things like replacing a word in someone's dialogue is a multi click, multistep process that is nearly instant in Premiere and most every other NLE. Just to try to see your whole timeline is a chore, to see what your edits and sound are in detail are problematic, trying to keep things in sync is a chore, and you can't even zoom your timeline window to full screen! If anybody has edited for any amount of time, I do not understand how they use FCP X. If they start with that program, for example if they are young, then that is a different beast.
    I'm sure Adobe will improve over time. They have to to stay competitive. In the meantime I'll take my 45%... but I wish I saw much more improvement given the cost and hardware differential. Unfortiunately, for now, the mainstream reviews I have seen regarding PPro performance on this machine were right.

    That statement about 4k/5k in Premiere CC with the nMP is false, insofar as performance goes.
    I just tested 5K Red raw files just dragged into Premiere Pro CC (latest version). I expected this to be slow, given my HD experience. However, on my 8 core/D700, I can play 1/2 just fine, full speed. And I even can also do that with a very streneous plugin/filter attached - FilmConvert (in OpenCL mode), also at 1/2 which is quite impressive. I can even add a bunch of other Premiere filters and SG looks and it still stays at full speed at 1/2.
    Ironically, this is quite faster than FCPX which can't seem to play back 5K at all with that filter attached (it doesn't stutter, but it's not smooth... low resolution at "best performace" and reduced frame rate). Even if I remove all filters FCPX plays back Red 4k (again not transcoded) about the same as CC at 1/2, but with a seemingly lower resolution to keep it smooth.  It's a head scratcher. It's like Adobe's Red handling is much better coded than Apple's in this case.
    Or... it has to be attrituable to that particular plugin (other FCPX motion-based plugins don't suffer the same fate and are fast). But either way, filter or no, Premiere Pro CC is definitely and sharper looking at 1/2 when cutting Red 4k/5k with no transcode, playback in real time, than FCPX which needs to bump it down to what looks like a 1/4 or less rez to keep it smooth. So I have no idea what is going on.
    This experience is the opposite with HD, where FCPX is significantly faster (using the same filters/plugin, using C300 Canon XF for HD and 4 and 5K RedRaw alternatively).  Premiere seems slower in HD than FCPX by a good amount in HD and signficantly faster with Redraw 4k. Go figure.

  • Happy Birthday iMac

    This month is the 10th birthday of the iMac! Wow, has it been that long since I stood out front of my local Comp-USA waiting for the truck to arrive with the first of the beautiful bondi-blue all-in-ones?
    I had been looking for an alternative to Windows for quite a while. At the time, my PC was actually running OS/2 Warp. A wonderful OS but there wasn't much you could do with it aside from the built in IBM Works suite and a pretty good version of Netscape. I was sick to death of Windows 95 and it's bugs.
    If I remember, my iMac came with System 7.5 or 8. The difference between Mac OS and Windows was night and day. It actually worked and it worked intuitively. No more hoops to jump thru just to get a file copied or converted. I was hooked from day one.
    Since then, I've had a Strawberry iMac, a G3 Graphite SE slot loader, a G5 flat-panel domer, and now an Intel Core 2 Duo. My original Bondi took a lightning hit thru the modem, so I sold it as a kid's computer. The Strawberry gave up just after upgrading it to OS X a few years ago. The Graphite lasted for almost 5 years of constant use before the power board failed. The warranty on the domer just expired but it's still going strong, and I love my Intel iMac.
    So Happy Birthday iMac! In the last 10 years, you've established a new standard for computing and every year you keep pushing the bar higher. I believe the next 10 will be even greater.
    And here's an ATABOY to Steve Jobs too

    Happy Birthday iMac! 
    My first was a 1999 Grape iMac DV (the colour has stuck on me even since!) which got me through university, that, my iMac G4 20" and 2.8GHz Core 2 Extreme are all going strong and all wonderful.
    cheers
    mrtotes

  • New iMac 24" or Mac Pro for Aperure

    Hi All,
    I only can get stock computers in COMPUSA or authorized resellers in PR.
    Which one do you recommend for Aperture, the new iMac 24" or the Mac Pro? It looks they both use the same video card...

    Sadly I have just asked Apple to take back my mac book pro 17" 2.16 because aperture was just to slow and it became annoying, after any adjustments to a photo the loupe tool would jump and jerk across the screen or the patch tool would do the same after around 3-4 patched dust marks, I came across to a mac purely for aperture, which incidently I think aperture is a great tool, if it would only run faster. If the MBP 17" 100gb 7200rpm HD 2 gb Ram and Radion X1600 with 256 mb memory has problems running this software what hardware setup was this programme actually built for.
    I will have to stay with my steam driven dell pc until I can make my mind up what to do, I must admit I am impressed by the mac itself and I found the service from apple outstanding, this laptop is my second machine in 3 weeks, first one had a warped top apple took it back and sent another one immediately, having also explained my problem and dissatisfaction with the second they have taken it back with full refund without any hassle whatsoever.
    Dave Hall

  • Premiere Pro CC's Warp Stabilizer BUGS...see for yourself. (7.0.1 & 7.1)

    I'd love to hear from Adobe Staff on this one. Hopefully they can focus on fixes over features for the next update, especially for one it's most touted effects.
    Warp Stabilizer works great at stabilizing clips in Premiere Pro CC...but I'm beginning to learn that it's quite buggy. The two bugs below simply cripple the user experience when you use the effect a lot like we do. Here's a link to a sample project with just 2 clips (around 1 minute in length each) on two separate timelines with each clip stabilized using the Warp Stabilizer effect. It's only a sample/test project meant to show the issue which can be MUCH larger in a longer/bigger project. Relink to any longer media and you'll quickly see what happens when you have multiple warp stabilizers applied to a Premiere Pro CC project and how problematic it can be.
    https://dl.dropboxusercontent.com/u/105331144/Warp_Stabilizer_SAMPLE_Project.prproj
    See for yourself.
    Two VERY Annoying BUGS and One Unfortunate Feature:
    BUG #1: (It affects 7.0.1 and the new 7.1 Release/Update)
    1) With GPU Acceleration Enabled and both sequences open, once the timeline render bar has turned yellow, hit save.
    2) Now toggle to the 2nd sequence and you'll notice a delay/freeze as the render bar switches back to red and then yellow again.
    3) Now toggle back to the other sequence and you have the same thing occur. Then, you can toggle back and forth with no delay...until...the project saves (or auto-saves) again...and then the delay/freeze will happen all over again.
    4) Side Note: Even when you right-click on the sequence in the Project window, there's a delay. Right-click on a sequence with no Warp Stabilizers and the drop down list pops up immediately.
    What's the Big Deal?: When you have tons more warp stabilizer effects applied to multiple sequences, not only does it take a while to save, but when it does, you are forced to wait while Premiere Pro freezes momentarily. This affects AUTO-SAVE too!!! The more warp stabilizers, the longer the wait. Our sequences have delayed up to 30-40 seconds depending on how much we've used warp stabilizer in each sequence. Imagine if you have Auto-Save set to every 30 minutes or less, well that means that every 30 minutes or less you'll be forced to stop while premiere freezes up for 30-40 seconds or so (depending on how much this effect is used). Other effects do NOT have this issue.
    BUG #2: (It affects only the new October Release/Update of Premiere 7.1...this issue is NEW and does NOT occur in 7.0.1!!!)
    1) Take the above project into Premiere Pro CC 7.1 (again, this does NOT occur in the previous 7.0.1 release) and hit FILE>EXPORT>Media.
    2) You'll notice a delay while the EXPORT SETTINGS popup opens.
    3) Toggle to different "FORMATS" in the export settings window and there's more delays every time the format is switched.
    What's the Big Deal?: Again, this is a small sample project. When you have a much bigger project with lots more Warp Stabilizers applied to many more clips this "delay" can extend up to several minutes!!! Yes, on a recent project over an hour with MANY warp stabilizers applied to lots of clips, it took 7 minutes for the Export Settings window to pop up after hitting EXPORT>Media. And there was about a one minute delay now when switching formats. This occurs whether GPU Accleration is enabled or not. It ONLY occurs on Premiere Pro CC 7.1
    UNFORTUNATE FEATURE #1:
    We obviously use Warp Stabilizer A LOT. It's a great effect. The above bugs cripple the user experience. This last issue isn't a bug, but rather a default setting on Premiere Pro's warp stabilizer that should be changed. Within the settings of Warp Stabilizer there's a section called "Method". The default setting is "Subspace Warp". That sounds pretty cool. But in practice, and we have had lots of practice (eg. THOUSANDS of clips stabilized in just the last few months alone (no exaggeration)), we've found that switching the default method to "Position, Scale, Rotation" is a MUCH more effective way to stabilize a clip. Most of the time it cuts down on that "wobble" that you might see in complex moving clips...but more importantly, 9 out of 10 times it crops the video either the same or less than when you use the default method. By "crops less" I mean that the "Auto-Scale %" is less. Of those 9 times, I'd guess 7 or 8 of them would crop in on the video less while the other 1 or 2 times there would be no change to the Auto-Scale %. Less scaling = better.
    What's the Big Deal?: Well, as cool as Subspace Warp sounds, our numbers don't lie. Again, we use this effect on HUNDREDS of clips every week. When you have to go into hundreds and hundreds of clips every week and keep switching the setting so the effect will work better, it gets old real fast. We end up wasting so much time doing this but it's worth it because the results are undeniable. Why not create a CUSTOM PRESET???! Well, that'd be nice if it worked...but it doesn't. The problem with a custom preset like that is that when you drop it on a clip, it doesn't activate/analyze the clip automatically so you have to manually go into the settings and hit analyze which negates any time saved. It's be great if the default "method" was simply changed to Position, Scale, and Rotation. Or at the very least, it'd be great if one could create a custom preset that would automatically activate/analyze the clip it's dropped on (just like the original effect does). 
    (BONUS FEATURE: It'd also be nice to have the ability to set a "max scaling %" too so you never crop in more than a preselected amount...but first things first...fixes over features.)
    NOTE: I'm on a 2011 suped up iMac running OSX 10.8.5

    [r]Evolution wrote:
    Would it help to  Render these Warp Stabaliized clips instead of leaving them in the sequence w/ the Effect applied?
    Any way to "Batch" Warp Stabalize your media before editing so the effect is not needed during the edit?
    Sounds like you guys could benefit from having your shooters use a "Stabalizer".
    Thanks for the rendering tip rEvolution. Rendering the clips does help with BUG#1, however, I'm not sure if it would truly save us any time because of the constant need to render and rerender tons of very short clips with this effect as we make adjustments to the edit. Warp Stabilizer is GPU Accelerated so playback is really smooth which is great but why does saving a project have any effect on this and cause it to freeze up? And then it works great...until the next time the project is saved. Using any other effect, there is no issue (that I've found) when a project is saved or auto-saved.
    Rendering unfortunately has no effect on BUG#2 in Premiere 7.1 (again, this bug/issue did not occur in Premiere 7.0.1)
    Regarding "batch" stabilizing...I'm not entirely sure what you mean. We do stabilize dozens of clips at a time before editing because it's imperative for us to know which clips (the sections we've pulled) will stabilize effectively. And then once the longer edit is complete we end up pulling all the best shots from that long sequence and copy/paste it to another sequence to make a 2nd shorter edit.
    To say we've gone back and forth about the use of stabilizers would be an understatement. The fact is that we've spent almost 4 years creating a unique way to shoot based almost entirely around the effectiveness of warp stabilizer. It's taken years of trial and error but our style of shooting effectively allows us to mimick and thus replace the need for stabilizers, sliders and cranes. The extra freedom allows us to get MUCH more varied coverage of live events. It's different, I know, but it's fun and rewarding having a unique style. Granted the extra work is passed on to the editing side, but it's worth it IMO especially if these issues were addressed/fixed.
    Regarding the "unfortunate feature" I mentioned, I would be satisfied knowing the default method works great for others if one were simply able to apply a custom preset of the clip with the adjusted method and it activated automatically and began analyzing the clip without the need to manually go into settings and hit analyze. That would be nice.
    Thanks again for your input.

  • Warp stabilizer cropping/position issue?

    So I don't think I've ever had this issue and I'm wondering if has to do with using it on a 13" macbook, since i've never had this issue on my iMac, but when I place the warp stabilizer effect the clip turns into a small cropped corner like so in the photo. This happens with any clip even if I try to adjust the stabilizer settings. Any help would be appreciated!

    Hi mlhidalgo,
    Please go to File > Project settings > General and change the GPU Acceleration to Mercury Playback Engine software only. After you will click ok, it will ask you to delete previews or keep previews. Choose Delete previews and see if it helps.
    Also, please report if you have Intel Iris graphics.
    Thanks!
    Rameez

  • Using iMAC screen w/a Dell Hybrid desktop

    I have a 27"iMac that I was hoping to use for trading. Unfortunately Apple does not support many Software apps that are typically reserved for native PC's. However with the intro of Virtual bridges such as VMware and Parallels, most feel this is an easy fix...IN my case it is proving not to be.
    My issue is this, I purchased Parallels 8 to run my PC based NInjaTrader software (for trading). Ninja does NOT recommenbd this however does note in their forum that MAC uses have has success using Parallels or VMWare. I am finding that although Parallels is seamless and does a very nice job for most of my Virtual needs, and frankly other PC Based trading software, it is not giving me the perfomance I need with NinjaTrader perhaps due to my data-laden PC/NT requirements.
    SO, I have this Dell Hybrid PC that I'd like to hook up to the iMAC, kick over to Target Display mode and simply let the PC run my native PC-based program so I can stop the issues. Does this sound feasible? I'm just looking for a nice solution that'll remove the inherent "virtual lag" that my MAC/Parallels and NinjaTrader platform is creating vs running NinjaTrader via a true PC-based system. I have it, might as well hook it up?
    Thx for any input/experience and/or solutions that you can recommend.
    DJ

    Because using a Virtual machine allows you to run both operating system at the same time.
    With a separate partition you have to shut down one OS to boot to the other OS.
    I don't use boot camp because I don't care for Dual Boot systems. I did that years ago with MS Windows,  IBM OS2 Warp and Redhat Linux. Every time I was in one OS and I needed to use the other I had to reboot to the other. Then reboot again to get back to the first or to another OS. I settled on using windows as it had all the software I needed.
    In other words I can't stand Dual Boot system.
    I've never used Paralles so I have no idea which VM software package is better, but then that is usually subjective anyway. Just like which type of system is better, Mac or Windows. For one thing they both use the exact same hardware. There is nothing in a Mac that is not in a Win PC. CPU, GPU, RAM, hard drives and all other hardware is exactly the same. They both to the same thing, read and write data to storage media, run programs so you can actually do something on them and display those programs on a screen. There is no difference. Mac computers have hardware and software problems just like Windows PCs.

  • I can't get cd's to play on my iMac. What could be the cause?

    what could be causing cd'sno to play on my iMac? Also what maybe some low cost but reliable fixes?

    That's a real tough one, trying to figure out why one or two CDs out of a dozen will not work...? Most likely they are slightly warped, out of round, off center or have some sort of film or blemesh that your superdrive doesn't like...?
    You might try burning them to blank discs on another Mac or PC and see if they'll work that way.

  • 24" Case Warping??

    My 24" iMac has a new problem, the white plastic on the front, directly above where the optical drive sits, has began warping. If i push on it up and down the length of the right side of the panel, it will go a few millimeters before it reaches the LCD. The left side is fine.
    Could this be due to optical drive heat dissipating and deforming the plastic that sits above it? Anyone else see this?

    I don't know what it's due to but if it happened to mine, I'd ask for a new one.
    -mj
    [email protected]

  • Premiere Pro CC - Warp Stabilizer causing "Heat Waves"

    I'm using Premiere Pro CC 2014 and when I apply Warp Stabilizer to certain clips I get this weird heat-wave, shimmer-like effect. For the life of me I can't figure out why this is happening. I've tried singling out every variable that I can but nothing matters.
    You can see what I'm talking about here: Dropbox - With WS.mp4
    And here is the clip without WS applied: Dropbox - Without WS.mp4
    The clips I'm trying to stabilize are actually pretty stable already so it shouldn't be an issue for WS normally. It doesn't seem to make a difference whether they're in a 720 timeline or 1080.
    I've tried every setting in WS that I can, including 'detailed analysis' and 'enhanced reduction' on Rolling Shutter Ripple. The only thing that kind of seems to help is applying the rolling shutter repair plugin but even then it's still somewhat choppy.
    The shots themselves don't have any noticeable rolling shutter ripple (slow moving grass shot on a monopod) and they look great UNTIL I add Warp Stabilizer and they get the weird effect. Even though the clips are already pretty stable, I just want to add WS to smooth some of these clips out a little bit. When I replace the clips with an AE comp and WS in AE it's fine! But I want to figure out why this is doing it inside Premiere so I don't have to use dynamic link every time I want to use WS.
    I just got this machine, maybe that has something to do with it...I have no idea.
    System info:
    Mid-2011 27" iMac
    3.4 GHz Intel Core i7
    12 GB 1333 MHz DDR3
    AMD Radeon HD 6970M 1024 MB
    OS X 10.9.5
    Adobe Premiere Pro CC 2014.1
    Shot on a 5D Mk. III with either a 24 (1080p) or 60 (720p) frame rate and resolution.
    Can anyone help? Thanks

    I don't have answers for you. Sorry. But I have seen that once before on a clip I stabilized. Much like the grass shot you show in your mp4. Mine was of a guy sitting at a pool and the bright plants behind him where flickering like a heat wave/desert-like effect. Only one clip had it and it made me go "hmm...never seen that before." I stabilized hundreds of clips in that project and that was the only clip with that heat wave thing happening. I was on 7.2.2 at the time. And eventually went to 8.0.1 with no change. It didn't bother me enough to do anything about it so I left it. It was shot at 1080p60 from a Panasonic PX270. Strangely I have the same computer as you (except I have 16gb of ram and I'm on 10.8.5). That is very interesting to me that it worked great in AE. Interesting indeed. I'll follow this thread in hopes of a revelation. Fortunately, I don't see that issue much or I'd be screwed.

  • Photoshop 7.0 and my new iMac hate each other

    Hi, I have just swapped to an iMac from Windows PC.  PS 7.0 which I have been very happily using for ages won't work I think my  install disc seems to be warped or corrupted.  Is there a version of PS 7.0 specifically for Mac available?  All my books and downloaded tutorials are for 7.0 so I don't want to change if I can help it.  (Not to mention the expense) No-one seems to have PS 7.0 or at least I can't find anyone who has.  Any Suggestions please.  The Mac is OS X 10.6.4.
    Thanks

    Hi,
    This forum is for queries related to 'Adobe Community Help' application. For Photoshop, post your query on the Photoshop forum at, http://forums.adobe.com/community/photoshop.
    Regards,
    Sandeep

  • Premiere Pro CS6 - Warp Stabilizer BUG causes project to crash

    Hi!
    Sometimes Warp Stabilizer causes Premiere CS6 to crash. I found out what steps cause this so hopefully a fix can be made in an update soon:
    1) Add the WARP STABILIZER to a clip. It Analyzes and then is applied to the clip.
    2) TOGGLE OFF the effect in the effect controls window
    3) Adjust the clip duration and RE-ANALYZE while the effect is TOGGLED OFF still and Premiere crashes.
    Happens every time. BUG Report was filled out.
    (If the effect is toggled ON when you RE-ANALYZE it, everything works okay.)
    So why not just not do this? Well, I usually don't but sometimes in the middle of working with hundred of clips I toggle on/off the effect to check certain things and then leave it off. If the clip is adjusted later or I come back and try to click ANALYZE again while the effect is toggled off, everything crashes.
    That's the pop up. If Premiere doesn't allow for you to re-analyze a clip while the effect is toggled off, then the ANALYZE button should not be active or at least a popup saying "Cannot Analyze this clip while it is toggled off". Instead Premiere crashes and upon reopening the project you are forced to rename the project which fortunately is usually fully recovered.
    Running 6.0.2 on a suped up 2011 27" iMac with 16gb ram and AMD 6970M 2gb video card.

    I know I'm piggy-backing on an old post here, but I've just had real issues with a similar thing on Mac. Unfortunately, my Premiere CS6 is crashing and becoming totally unresponsive whenever I simply apply the Warp Stabilizer. The moment I drop it on my clip, BLAM! I get that same pop up you posted. I click 'OK,' and then nothing. Just beachbal of death until I force quit. What's more annoying is that, not only has the camera operator made the stabilizer essential, but I've been using it for the past week with no issues up till now.
    At first I thought I was overloading Premiere by dropping the effect onto two clips at the same time. But I tried it one at a time and had the same problem. My recovery project files seem to be ok, but that's not even nearly the point. I simply can not use a great and essential tool. Help?

  • New iMac (2014), 32GB, 256 SSD, "Unable to allocate..."

    Hello. I've been searching, but not finding, answers.
    I have a new iMac with 32GB RAM and a 256GB SSD. I just updated AE to 13.0 from v 12(.2?). Same problem with both versions. I'm trying to stabilize a 28 minute video. The analysis churns adequately, then, at the end, I get the dreaded "Unable to allocate 0.000MB of RAM..." message. Then, I can't quit, and must force quit.
    My settings include "Render multiple frames simultaneously," and I've reserved 2 of the 8 cores for this task.
    The only answers I've been able to find are "restart," and "allocate cores to other applications." Oh, yes, and "update." Well, I've done those things and I'm still getting the message.
    Does *anyone* out here know what's going on and how to fix it?
    Thank you.
    Glennotf

    I assume you mean Warp Stabilize, which is entirely different than stabilize. Warp Stabilize a 28 minute video is --- well, nuts. A single 28 minute hand held shot? If the 28 minutes is not one continuous shot you cannot use any kind of stabilization. You cannot stabilize across cuts. It can't be done.
    Cut up the shot into manageable segments by finding cut points and stabilize a minute or two at a time. You are trying to cram 28 minutes of video into ram at full rez then perform calculations on it. I know of no tracking software that would be up to that task.

Maybe you are looking for