Render issues in Shake on iMac

Just purchased new iMac (20", OSX 10.5.5, 2.66GHz Intel Core 2 Duo, 4GB Ram, ATI Radeon HD 2600 Pro) and Shake 4.1. So as a relatively new user to Shake (1yr VFX experience in school and work) and new to Mac, imagine my shock when I called Apple about my issue and found out their support is limited to install issues only!
Anyhow I could go into that but won't, and will cut to the real issue!
Am working on HD footage. Shake would render between 50% and 75% of 369 frames and then crash out of flipbook. So got frustrated and quit for the day... came back next day and now won't render at all. Won't render in flipbook or render from a file out node. Went to console tab in shake no errors reported, its as if Shake is not even starting render process period! Bummer ;-)!
So before I use Apples solution, uninstall and re-install Shake... thats the extent of their knowledge base....
Was wondering if any of you gurus out there have a better solution, or an idea of what caused this issue. The system and program were purchased a whopping 3 days ago, and I don't want this to be an ongoing issue.
Cheers and thanx

Just posted this on another forum..... same topic.
Hmmmm
Okay well back after having to rush out of town for the weekend, and yesterday filed in some HD footage and just tried (without success) to do a flipbook of footage with no extraneous nodes, just a straight flippy of it. LOL now I believe this should work no custom .h's involved or anything. And yes no render still, same thing no flipbook at all.... so maybe it is 10.5.5 issue...... haven't tried (10.5.4)yet and well frustration is kicking in .
Unistalled and reinstalled Shake, no change. I guess my real issue here is that render worked initially (although it crashed out around frame 250 of 369), and I wish I was more of an IT guy but am not (yes starts to rant here). It seems to me I have purchased a very sexy system and yes some very verbose software (that doesn't go unrecognized here) that is not supported by the seller (Apple) steam starts coming out of ears LOL. Now all this footage and nodes etc rendered out fine on the Linux systems at school, but won't render here on this new swanky system. So my intro to Mac has left me less than enamored with Apple. OK rant over
So can .h files effect rendering even if they are not in tree of footage being rendered? Would I have been better off with an Nvidia graphics card, if it was available for this particular iMac? And should a simple render really be this complicated (fully understanding that Shake is a powerful and complex program)? The console tab in Shake shows no errors during Shake launch other than some .h files are not being loaded.
I fully appreciate any responses to my post so far, and yes haven't tried all suggestions yet, but my desire to become an IT expert is low LOL as apposed to my desire to do compositing which is high. Maybe the 2 are synonymous with each other, boy I hope not.
So please keep the suggestions coming in I will try the ones which fall into my knowledge base and am thankful for any and all suggestions.
Frustrated new Apple customer.
Lance

Similar Messages

I have been having multiple issues lately with my iMac

I have been having multiple issues lately with my iMac - starting with insanely slow processing/run speeds.
When I run Activity Monitor, consistently the highest usage of CPU is "ReportCrash" - typically shows up as 80-200% of CPU.
What could this be caused by?
I posted only a portion of the code from Activity Monitor but not sure what exactly is relevant or not. I can certainly post more if it's needed.
Many thanks!
Analysis of sampling ReportCrash (pid 332) every 1 millisecond
Process:         ReportCrash [332]
Path:            /System/Library/CoreServices/ReportCrash
Load Address:    0x10e14a000
Identifier:      ReportCrash
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process: launchd [1]
Date/Time:       2013-04-23 18:17:29.753 -0400
OS Version:      Mac OS X 10.8.3 (12D78)
Report Version: 7
Call graph:
    2492 Thread_6876   DispatchQueue_1: com.apple.main-thread (serial)
    + 2492 start (in libdyld.dylib) + 1 [0x7fff847cd7e1]
    +   2492 ??? (in ReportCrash) load address 0x10e14a000 + 0xfb9c [0x10e159b9c]
    +     2492 -[NSConditionLock lockWhenCondition:beforeDate:] (in Foundation) + 235 [0x7fff815f1e39]
    +       2492 -[NSCondition waitUntilDate:] (in Foundation) + 357 [0x7fff815f1fe3]
    +         2492 _pthread_cond_wait (in libsystem_c.dylib) + 927 [0x7fff86326023]
    +           2492 __psynch_cvwait (in libsystem_kernel.dylib) + 10 [0x7fff8b52f0fa]
    2491 Thread_6877   DispatchQueue_2: com.apple.libdispatch-manager (serial)
    + 2491 _dispatch_mgr_thread (in libdispatch.dylib) + 54 [0x7fff887179ee]
    +   2481 _dispatch_mgr_invoke (in libdispatch.dylib) + 883 [0x7fff88717dea]
    +   ! 2481 kevent (in libsystem_kernel.dylib) + 10 [0x7fff8b52fd16]
    +   8 _dispatch_mgr_invoke (in libdispatch.dylib) + 134 [0x7fff88717afd]
    +   ! 4 _dispatch_mgr_thread2 (in libdispatch.dylib) + 43 [0x7fff887180a8]
    +   ! : 3 _dispatch_queue_drain (in libdispatch.dylib) + 180 [0x7fff88716448]
    +   ! : | 2 _dispatch_queue_invoke (in libdispatch.dylib) + 72 [0x7fff88716305]
    +   ! : | + 1 _dispatch_source_invoke (in libdispatch.dylib) + 58 [0x7fff88717022]
    +   ! : | + ! 1 _dispatch_kevent_register (in libdispatch.dylib) + 280 [0x7fff887173f4]
    +   ! : | + !   1 _dispatch_source_kevent_resume (in libdispatch.dylib) + 63 [0x7fff88717513]
    +   ! : | + !     1 _dispatch_kevent_resume (in libdispatch.dylib) + 92 [0x7fff88717588]
    +   ! : | + !       1 _dispatch_kevent_machport_resume (in libdispatch.dylib) + 96 [0x7fff887175ec]
    +   ! : | + !         1 mach_port_move_member (in libsystem_kernel.dylib) + 31 [0x7fff8b52e539]
    +   ! : | + !           1 _kernelrpc_mach_port_move_member_trap (in libsystem_kernel.dylib) + 10 [0x7fff8b52d626]
    +   ! : | + 1 _dispatch_source_invoke (in libdispatch.dylib) + 257 [0x7fff887170e9]
    +   ! : | +   1 _dispatch_kevent_unregister (in libdispatch.dylib) + 286 [0x7fff887189ad]
    +   ! : | +     1 free (in libsystem_c.dylib) + 199 [0x7fff8633a8f8]
    +   ! : | +       1 szone_free_definite_size (in libsystem_c.dylib) + 211 [0x7fff8634012c]
    +   ! : | +         1 _spin_lock$VARIANT$mp (in libsystem_c.dylib) + 13 [0x7fff8630ff9d]
    +   ! : | 1 _dispatch_queue_push_list_slow2 (in libdispatch.dylib) + 33 [0x7fff88715e10]
    +   ! : |   1 _dispatch_wakeup (in libdispatch.dylib) + 132 [0x7fff88715ecd]
    +   ! : |     1 _dispatch_queue_wakeup_global_slow (in libdispatch.dylib) + 59 [0x7fff88716073]
    +   ! : |       1 pthread_workqueue_addthreads_np (in libsystem_c.dylib) + 47 [0x7fff86324016]
    +   ! : |         1 __workq_kernreturn (in libsystem_kernel.dylib) + 10 [0x7fff8b52f6d6]
    +   ! : 1 _dispatch_queue_drain (in libdispatch.dylib) + 48 [0x7fff887163c4]
    +   ! 3 _dispatch_mgr_thread2 (in libdispatch.dylib) + 71 [0x7fff887180c4]
    +   ! : 3 _dispatch_source_drain_kevent (in libdispatch.dylib) + 172 [0x7fff887186d2]
    +   ! :   3 _dispatch_source_merge_kevent (in libdispatch.dylib) + 226 [0x7fff88718858]
    +   ! :     3 _dispatch_wakeup (in libdispatch.dylib) + 132 [0x7fff88715ecd]
    +   ! :       3 _dispatch_queue_push_list_slow2 (in libdispatch.dylib) + 33 [0x7fff88715e10]
    +   ! :         3 _dispatch_wakeup (in libdispatch.dylib) + 132 [0x7fff88715ecd]
    +   ! :           3 _dispatch_queue_wakeup_global_slow (in libdispatch.dylib) + 59 [0x7fff88716073]
    +   ! :             3 pthread_workqueue_addthreads_np (in libsystem_c.dylib) + 47 [0x7fff86324016]
    +   ! :               3 __workq_kernreturn (in libsystem_kernel.dylib) + 10 [0x7fff8b52f6d6]
    +   ! 1 _dispatch_mgr_thread2 (in libdispatch.dylib) + 61 [0x7fff887180ba]
    +   !   1 _dispatch_cache_cleanup (in libdispatch.dylib) + 30 [0x7fff88716695]
    +   !     1 szone_free (in libsystem_c.dylib) + 473 [0x7fff8633c91d]
    +   !       1 _spin_lock$VARIANT$mp (in libsystem_c.dylib) + 13 [0x7fff8630ff9d]
    +   2 _dispatch_mgr_invoke (in libdispatch.dylib) + 858,885 [0x7fff88717dd1,0x7fff88717dec]

It would help to know more about your iMac.
What year, screen size, CPU speed and amount of RAM installed?
How full is your Mac's hard drive?
How many applications do you run simultaneously in the background while working in another application?
Do you run any antivirus software on your Mac? Antivirus software can slow down the normal operation of OS X.
Do you run any "crapware" like Mackeeper or any other type of so called hard drive "cleaning" apps?
Have you downloaded and installed anything recently that might have caused the erratic behaviour of your iMac?

Render issues with text

I have made a short 1 min movie, and have rendered it. I want to download to youtube, but when I try to export using quicktime conversion, it shows render issues wherever I have text. Once I get cancel out, it shows no render problems.
When I remove the text, the render problem still remains. I can export with quicktime, but not sure youtube will allow this to be downloaded.

Please define: "render issues" and also the phrase "Once I get cancel out"
-DH

560GTX render issue help please

I've got the MSI 560GTX-Ti twin frozr video card in my Sandy Bridge system. It is NOT overclocked, I am running it at all factory resets. This is the second card I have received and they have both had some rendering issues. I'm using the latest drivers from Nvidia 266.66
Everything looks good in general usage, but when I play the game Rift (using High settings) I am getting some rendering artifacts. The card does not appear to be overheating as far as I know. I have run Furmark and it looks ok. Temps do go up to close to 70c but no graphic anomalies show up. In Afterburner the settings are all stock factory settings. At no time in the game does the fan seem to crank up to be audible.
I would include an image of the screen but don't know how. Basically the landscape will display square beams of texture protruding from random areas of the screen. Any ideas on what is going on and how it can be fixed?
Willax
edit: I ran Furmark right after getting the render issues in RIFT and the fur donut had some holes in it, the temperature was running close to 70c
Then I changed the fan speed from AUTO to 70 percent and the temp in Furmark dropped to a steady 65 but there were still render issues with holes and extended triangles in the donut.
It seems that this card is getting too hot and not rendering correctly, but it shouldn't be happening. I even turned the fan up to 100% and although it got loud the temp did not change
very much from 65c

Well, I clicked those items and told it would be active after I started afterburner. I restarted and the voltage slider was not active. Nothing I clicked would let me do anything. I hadn't really planned on doing any o/c stuff with this card, but purchased it because of the GREAT reviews on it. I prefer to run at stock settings, and it's not giving me very good performance with those
I'm glad I got the extra year warranty on it and will probably call New Egg tomorrow to replace it.

Having sound issues with Mid 2011 iMac 27"

Having sound issues with Mid 2011 iMac 27". It has 10.10.2 OS X. Could this the issue and if so how do I revert to 10.7.3

It is almost impossible to diagnose sounds over the internet, however here is a link to some failing HD sounds. If one of yours be happy, at any rate take it in for service. If you got AppleCare or it's less than a year old it's covered.
Failing hard drive sounds

Low Memory Environment Render Issues...

Howdy folks,
     I've been working on a 13 minute promotional video for a non-profit summer camp. It is made up of mostly still images with some ken burns effects, a narration track, a music track, some titles, and some logo overlays.
     I am doing this on a 3.2 Ghz P4 with only 1.5G ram under XP sp3. I realize this is not an ideal PPro box.
     Windows XP is configured to use 2 drives for VM paging (3Gigs each). All drives have over 100gigs of free space on them.
     Now until recently I've only had a couple of small issues which I suspected were related to trying to do this in a low memory environment. In one case a flash render would die at the same point every time (error was something along the lines of "did not return a valid frame"), and simply scaling down the still image clip at that point in the sequence so that it was closer to the project size took care of it. That method also helped in a few cases where some images would not render at all, and just appeared as black screens in the final video (the render process did not fail, but the end result was missing clips).
     Then there was one case it seemed to fail at random points. A simple reboot took care of that, and it exported just fine.
     But now, however..... Now it's back to failing at random points (sometimes it gets 3500 frames in... sometimes as far as 13400... or anywhere in between) and additionally, by viewing the incomplete flash video file with VLC (which I need to do in order to find out where it failed because PPro never tells me) I find that some of the images are black screens, as before.
     The problem now, is that it's never the same point of failure, and it's never the same images blacked out. And rebooting and or killing off extra processes does not help.
     Now this was rendering fine last week. Here's the kicker - I haven't changed much of anything since then. The project is still the same length, with just about the same number of cuts, tracks, and assets used. The only things I've done since then are:
     1) I duplicated the sequence so that I can make some changes unique to the web-version of the video, and still save the old sequence to go back to. The old sequence has remained untouched and I haven't even looked at it since then.
     2) Created 2 new titles and inserted them in place of some old ones in the new sequence which weren't appropriate for the web version of the video (only the text is different in these new titles... they are the same style, size, etc. as the old ones they replaced)
     3) I shortened some empty time/space/pauses between sections of the sequence.
     So those are all minor changes... but I can't shake the rendering issue no matter how many times I restart or scale down an image that was blacked out or appears at one of the random points of outright failure (again, with the "did not return a valid frame" issue).
     I did notice that after I duplicated the original sequence, the project takes much longer to open. Does having another sequence present in the asset bin use that much more resources? Even if the clips in that 2nd sequence use the same assets as another? I'm tempted to remove the original sequence and see what happens, but I don't want to lose it and have to un-edit the web version whenever I want to go back and re-render the DVD version.
     So basically I'm looking for anything that might cause the small changes I made to be giving me so much grief now.
     Any input is appreciated. Thanks.

You may have a corrupt project. Try creating a new project and importing the old one into it.
If you still experience problems then carefully do each of these troubleshooting tips. One or more of them is likely to help.
Cheers
Eddie

Apple Pro Res 422 / FCP7 render issues

Hello,
I do a lot of timelapses and have pretty good workflow for all this. However, I am experiencing one issue that makes everything a bit difficult. I appreciate if anybody could help me.
My workflow is:
1. Shoot some stills RAW
2. Develop in Adobe Camera RAW
3. Import stills sequence and render in AfterEffects CS4 to AppleProRes 422
4. Import to FCP7 and edit
5. Grading / color correction
6. Publishing
All works fine, however I am having very often an unpredictable issues with the Apple Pro Res 422 codec under FCP7.
I always render a bunch of sequences from AE using the same settings for all files. The only difference is resolution.
My render settings for exporting from AE are:
- Apple Pro Res 422 wrapped in MOV
- render in 10-bit YUV from RAW 16 bit sequence files
- AE project in 16 bit
- Resolutions of rendered all files around 3500x2500 px, this vary from file to file.
The sequences render fine in AE.
The sequences play properly in QT, I can import them to FCP properly, play in FCP properly. I can drag to timeline, scale, rotate, scrub etc.
However: Some sequences fail to render in FCP7.
When I drag them to my working sequence in timeline (Usually a Full HD 1080p, Pro Res 422, YUV), scale down (usually) and try to render timeline footage (don't mean exporting here yet) I get the following error:
"Codec not found. You may be using a compression type without the corresponding hardware card."
This happens on many computers including iMac, MacbookPro and a Mac Pro.
I discovered that setting the footage size to even width and height figures when exporting from AE eliminates the problem sometimes, but it does not help in all cases.
Also it sometimes help if i take such sequence, crop and export using QT under the same settings, just a few pixels less in size. But again - it helps sometimes.
Can anybody help me with these?
Anybody experiencing similar issues?
Thanks a lot.

I had the same problem when we started to edit on Pro Res timelines. The solution I found was to go the Sequence Settings > Video Processing > and change the Render setting to "Render in 8-bit YUV" that allowed me to actually render the timeline and view my work. Hope that helps.

Playback and render issues Premiere Pro CS6 on Mac

I have been having very "skippy" and sluggish issues when it comes to playback and editing. I have deleted all the old render files from my project and my hard drive, but nothing seems to work. Can someone please help me? I'm not sure if it is a space issue or what, but I haven't had much of these problems before. I know it's not a sequence settings issue, so I am very confused. My footage all comes from a Maxell P2 Eseries card and my computer specs are:
iMac
Processor 2.5 GHz Intel Core i5
Memory 16 GB 1333 MHz DDR3

http://helpx.adobe.com/premiere-pro/kb/cant-capture-dv-hdv-video.html
Also, Go to http://forums.adobe.com/community/premiere and, in the area just under Ask a Question, type in
maverick
or
mavericks
or
10.9
You may now read previous discussions on this subject... be sure to click the See More Results at the bottom of the initial, short list if the initial list does not answer your question

Render Issues, FCP7 - strange colours

Hi there,
sorry if this issue exists somewhere else on the forum. I couldn't find it.
I'm trying to render in FCP 7 and I'm getting strange issues where colours that shouldn't be there appear.
I'm using footage that was originally shot in HDV on an HV20 but was converted to Prores. It's also been through colour, rendered through that and then reimported.
The shot in question has a colour filter on it, crushing the blacks. It appears in anything I export. In other situations where I've come across this issue, I just rerender and it's fine. But this shot seems to not be able to shake it.
I'm uploading a video to youtube for reference. I'll post when it's up. But in the meantime if you have any suggestions or thoughts it would be much appreciated.
Thanks in advance for the help.

Thanks,
That didn't help. But it seems I've now worked around it. I removed the colour corrector filter and replaced it with a brightness and contrast filter.
If anyone else has suggestions on how to solve this issue for future issues - or an explanation as to why this happens - your insight would be much appreciated. I've come across this problem before. But I usually work around it by switching to my other computer (that seems to favour rendering better for some reason). Unfortunately, this time I'm on the 'better' computer that tends to solve my problems.
Thanks,
Tess

Dreamweaver 8 Design View render issue

I was wondering if anyone else has noticed a highly
irritating issue with DW8 that is apparently not an issue in the
Design View of DW MX 2004.
In DW 8 for some reason I'm getting an extra 150 pixels of
white space to the right of my #content container. It only appears
to happen when the content within the #content container does NOT
exceed the length of the content in my menu container (#priNav2).
In other words, if the content is longer then the menu, it renders
fine.
See here:
Dreamweaver
8
But, in DW mx2004 the exact same file shows up how it should.
Dreamweaver
MX 2004
Does anyone have any suggestions on how to resolve this issue
or have a clue as to why this is happening? It's really one of the
only bugs left preventing me from upgrading to DW 8 anymore.
Thanks,
- Paul

After some tinkering around and a call to Tech. Support I
eventually resolved this issue by pointing out a bug to Adobe.
Apparently the problem is the View / Visual Aids / Invisible
Elements option. If this is turned on, and you have a website set
up similiarly to
this one, you will
experience this sporatic, extranenous white space that shifts your
content around. It is not an issue in DW MX 2004, only DW 8.
The solution is to just simply turn OFF the "Invisible
Elements" option. Then the page will render the way it should.
A bug report has been submitted.

Save for web&.... the image exceeds the size for ....issue with AI on imac i7

Hi,
I just upgraded from using macbook Pro to Imac inte core i7 with 4GB. I use illustrator CS3 for high resolution documents i.e saving a Design for say maybe saving for iphone &ipod skin; a quality jpg that is 1300px(width) by 2000px(height.
General information
The issue is I keep getting the pop up with:
The image exceeds the size Save for Web was designed for. You may experience out of memory erros and slow performance. Are you sure you want to continue?
I click yes, but get another pop up with:
Could not complete this operation. The rastarized image exceeded the maximum bounds for save for web.
And last weekend after NOT being able to save anything I went and bought 16GB memory thinking that this ussue would be solved, but nada.
I have researched around here and google only to find about scratch disk: went to preferences then to plug-ins and scratch Disks -I seem NOT to get to the bottom of this at all.
And this morning I was trying to create a pattern Design and could not even get the design on the color swatches as I have done before with macbook pro with 4GB -IT'S NOT FUN, because I am NOT doing it right. Do you care to help me out?
Thanks a whole bunch in advance
//VfromB

Are you including a color profile? What metadata are you including with it?
How many pixels (h x v)?
50 kb is not all that big. Does your image have a lot of detail in it? Content can affect final compressed size.
-Noel

Live text template render issue when using Media Encoder?

I'm running into flash frames with Media Encoder exports of Premiere sequences using the live text templates.
Unfortunately, AME doesn't flag it as an error, so the render completes without any issues in the render log and the only way to find it is to watch the rendered file.
I have tried different combinations of having After Effects open or closed, with the live text template comp open or closed; I can't consistently reproduce the problem with any certainty and so am having trouble pinpointing the source.
My only hypotheses so far are that:
The glitches seem to be happening in the dynamic link between AME and PP, not AE and PP. The live text will pop back to the duplicated comp's text for one frame. Video playing simultaneously doesn't pop.
In other words, the AE text template said: "name here". In PP it was edited to say "John Doe", then that comp was duplicated and edited to say "Bob Smith". Everything looks fine in PP. There are no keys on the source text in AE (I have noticed that if there are keys on the source text in AE, the text will pop back to the original AE text at that key in PP).
When rendered out of AME, halfway through Bob Smith's title, it will read "John Doe" for a single frame, then pop back to being Bob.
I've only had this happen so far with AME renders. The renders out of PP haven't given me any issues so far.
It might happen more frequently on longer segments? If a title is up for 45 sec instead of 10 sec, it may be more likely to pop.
The issue seems to occur more often in batch renders out of AME (happened to 3 of 5 files rendered in a batch, AME 2014.1) and/or with unrelated AE comps open (on a single render from AME 2014.2)
Again, it doesn't happen every time or to the same title, or in the same spot. Files are being rendered to ProRes 422 HQ. Unchecked "Use Previews" in AME.
Would be nice to get to the bottom of what's happening so I can recommend something to the editors when I hand off these live text templates to them.
I realize that the live text is a new feature as of 2014.1, but haven't found anyone else talking about this. Would love if this was a very simple fix that I'm missing.
I was able to reproduce the error on 2 different machines, with similar specs:
Premiere CC 2014.1 and 2014.2
Media Encoder CC 2014.1 and 2014.2
Mac tower 2010
2x 6-core Intel Xeon
RAM: 64 GB
Graphics: ATI Radeon HD 5770 and NVidia Quadro K5000 (or K4000)
OS: 10.8.5 Mountain Lion

I'm running into flash frames with Media Encoder exports of Premiere sequences using the live text templates.
Unfortunately, AME doesn't flag it as an error, so the render completes without any issues in the render log and the only way to find it is to watch the rendered file.
I have tried different combinations of having After Effects open or closed, with the live text template comp open or closed; I can't consistently reproduce the problem with any certainty and so am having trouble pinpointing the source.
My only hypotheses so far are that:
The glitches seem to be happening in the dynamic link between AME and PP, not AE and PP. The live text will pop back to the duplicated comp's text for one frame. Video playing simultaneously doesn't pop.
In other words, the AE text template said: "name here". In PP it was edited to say "John Doe", then that comp was duplicated and edited to say "Bob Smith". Everything looks fine in PP. There are no keys on the source text in AE (I have noticed that if there are keys on the source text in AE, the text will pop back to the original AE text at that key in PP).
When rendered out of AME, halfway through Bob Smith's title, it will read "John Doe" for a single frame, then pop back to being Bob.
I've only had this happen so far with AME renders. The renders out of PP haven't given me any issues so far.
It might happen more frequently on longer segments? If a title is up for 45 sec instead of 10 sec, it may be more likely to pop.
The issue seems to occur more often in batch renders out of AME (happened to 3 of 5 files rendered in a batch, AME 2014.1) and/or with unrelated AE comps open (on a single render from AME 2014.2)
Again, it doesn't happen every time or to the same title, or in the same spot. Files are being rendered to ProRes 422 HQ. Unchecked "Use Previews" in AME.
Would be nice to get to the bottom of what's happening so I can recommend something to the editors when I hand off these live text templates to them.
I realize that the live text is a new feature as of 2014.1, but haven't found anyone else talking about this. Would love if this was a very simple fix that I'm missing.
I was able to reproduce the error on 2 different machines, with similar specs:
Premiere CC 2014.1 and 2014.2
Media Encoder CC 2014.1 and 2014.2
Mac tower 2010
2x 6-core Intel Xeon
RAM: 64 GB
Graphics: ATI Radeon HD 5770 and NVidia Quadro K5000 (or K4000)
OS: 10.8.5 Mountain Lion

Any fix for CC render issue with the new MacPro Firepro D700. Getting lines and flicker as documented in threads

Hi,
We're facing some critical problems with our new MacPros, CC, and the Firepro D700's. It appears that after we upgraded to 10.9.3 the D700's no longer work with Creative Cloud. Our Premiere renders are full of artifacts, lines, and drop out. Same issue as documented in RENDER PROBLEM - AME and Premiere Pro CC causing random horizontal lines on H.264 Renders Can you advise as to when the fix will be pushed? We have turned to "software only" render, which is killing us for time. We have a huge amount of work that goes through 4 edit bays and its putting us days behind.
Please let us know,
Sincerely, Jim Janicek
Janicek Media, Inc.
720-891-6276
[email protected]

You need to ask in Community: Premiere Pro | Adobe Community but do not expect Adobe to discuss future plans
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform for bug reports or feature requests
This forum is about the Cloud as a delivery process, not about using individual programs
If you start at the Forums Index https://forums.adobe.com/welcome
You will be able to select a forum for the specific Adobe product(s) you use
Click the "down arrow" symbol on the right (where it says All communities) to open the drop down list and scroll
Also, this is an OPEN forum, not Adobe support... please do not post personal information

MXM graphics card issue on (white) 24" iMac #2

Because the original thread is closed, I will start here a sequel...
As mentioned there are A LOT of people who experience massive MXM card related problems with their white 24" iMacs. It seem that it's near normal that these Geforce 7300 / 7600 modules will "decease" after two or three years...
Perhaps this affects only a certain production line of these Geforce 7300 / 7600 MXM cards, nevertheless according posts and blogs on the web, this problem seem to be very widespread.
Out of my view it is clearly to "widespread" to say that this are just some "average" contingencies...
Yes, I will go so far to say that there are some similarities to the horrible "iMac Vertical lines problem".
Unfortunately similar is Apple's official reaction on the issue here, if your are not a lucky owner of an Apple Care Protection Plan, you have simply no other choice than pay for the repair $700.
Well, well, it seems that there is actually no other option then to go the way of "cross flashing" the MXM firmware of standard (PC) MXM modules. Whatever this matter is very complex and risk full...

Keep cool. It's not to late... Yes, you are now affected by the same error described by me. For the moment, DO NOT USE the iMac FOR LONGER TIME. Especially DO NOT USE it for intensive graphical things!
If you have Apple Care take the iMac to your next Apple Partner. If there is NO WARRANTY, I advice to do it yourself. This will spent you A LOT of money.
Ok, what do you have exactly to do? No big thing, - just completely disassembly your iMac. More precisely, you have to change the original thermal grease between the graphics chip and the heat pipe. Exactly that's the reason of all these failures here. It seems, that Apple has used here some debased material...
It sounds hard, but at the end, it isn't really. Check the following sites:
http://www.techdc.com/imac-24-opened-and-upgraded
http://www.flickr.com/photos/litmus/4480251432/

HP 2475w Issue-Image "Shakes"

Hello,
I recently picked up a second 2475w LCD on the used market and after a week of using it, I have noticed a very minor but constant shaking of the image.
The shaking seems slightly more pronounced when using an HDMI cable when compared to a DVI.
The issue seems apparant when the LCD has been off for a while and cool as well as when it's warm. There seems to be little to no differnce.
I was wondering what would be the best way to troubleshoot this problem or which internal circuit board might be faulty.
Is there a service manual available? I have a Fluke 189 DVM and so can perform some testing if the monitor's circuit boards.
My sytem is running a pair of Nvidia 580 cards in SLI. I have tried switching the cable to another card and the screen still shakes a bit. I'm pretty sure the cards are fine.
Thanks in advance,
Ed

Hi @HPS01
I have brought your issue to the attention of an appropriate team within HP. They will likely request information from you in order to look up your case details or product serial number. Please look for a private message from an identified HP contact. Additionally, keep in mind not to publically post ( serial numbers and case details).
If you are unfamiliar with how the Forum's private message capability works, you can learn about that here.
Regards,
George
I work for HP

Render issues in Shake on iMac

Similar Messages

Maybe you are looking for