Shake Rendering File out Node Crashing problem

I have 4.1 with leopard installed on my Imac intel 2.16 core duo machine and every time I try to render a file out node, it crashes or quits unexpectedly. Does this happen with anyone else or can anyone tell me how to fix this problem? Apparently, there have been some issues with this but I cant get a straight answer. Any help would be appreciated. Thanks

To trash preferences, close down Shake, go to your user directory, then navigate to Library/Preferences and delete the file called com.apple.shake.plist. Empty the trash, then fire up Shake again.
I had a weird bug today. I was trying to output a single-frame PNG and it came out garbled. I tried all kinds of things like trashing prefs, changing settings, etc. In the end, I outputted it as a TIFF, and converted it in Photoshop, which worked perfectly.
For your issue, try outputting it as a sequence of TIFF images and see if it works. Just do a short range of frames to test it.

Similar Messages

File out node settings

I use shake and I have trouble with the final image quality. After I export it to quicktime movie I can see that the picture is not clear and there is a lot of noise.
So I would like to ask you about the best way to export (file out node) my project. Is quick time good enough for that? Is there another renderer for shake that reaches great quality?
Please let me know....thanx a lot

ctually the problem I have is the quality of the final video, I dont care about the format type I just care about the "great possible quality" So I was wondering if there is a separate compressor that I can render my video so I can reach "movie quality"to understand better my problem I ll give you a simple example:
I exported a single shot from final cut pro to uncompressed quicktime format. Then I imported this shot in Shake. After that I put a person as a chroma key layer with my first video. It looks good in shake , almost perfect but when I render it quicktime uncompressed I see that shity noise!!! What am I doing wrong?

Trouble with File Out rendering

When rendering File Out nodes, Shake sometimes are not overwriting the existing file (when rendering multiple times..)
How can I get Shake to overwrite the existing File Out file?

It has been my experience that if Shake encounters an error writing to the FileOut (say if FCP has the file open), you encounter NO error message. Shake will spend the time rendering but never write out the file. In general, just prior to rendering, I delete the output at the finder level...
Patrick

File Out Tiff Image Sequence

Hello! Can anyone recommend/explain the correct settings in the File Out node to output a TIFF Image Sequence?
Thanks!

Wow, I just figured out the Shake problem. First off you are right, my "black background" is an alpha mask. But why is it there?!? It is a "bug" in Shake:
FileOut - Quicktime Movie - Animation - Options - Compression Settings - "MillionsofColors" - Okay
Now, when I reopen the FileOut node to double check my Compression Settings, it has defaulted BACK to "MillionsofColors+" So yeah, "MillionsofColors" should result in an alpha-free export BUT SHAKE WILL NOT RETAIN A SELECTION OF ANYTHING OTHER THAN "MillionsofColors+" I tried setting it to "Black and White," "ThousandsofColors" - same issue - the export still has an alpha because Shake took the Compression Setting back to "MillionsofColors+"
So thanks for all your help on this, I'm glad your system is not operating with this quirk.
I'm pretty sure I hate Shake.

Help locating rendered files for relinking after a crash.

I am working on an adobe premier pro project and my computer crashed yesterday. the project file no longer opens as it is asking where certain rendered files are located... I do not know where premier is hiding them so when I hit skip or try to offline them the project tries to open and it freezes up. I was able to open an auto save file but now the project runs very very slowly... every click or action takes the computer about 2 minutes to respond and if I click while it is thinking... it crashes.
HPZ400 workstation
win 7
CS5

Maybe a shot in the dark, but did you at anytime change your project scratch disk settings at any time. If not maybe have a look at the Default folder for scratch disk settings. Can't remember exactly where it is but it will be on your boot drive under user/ your name or failing that try relocating it by copying the file asked for when PP loads and do a search on your entire machine. This may reveal something usefull like a location where stuff has been saved.
Hope that helps.
Dave.

If tempdb .mdf file out of disk space and we do nothing to fix, what could happen? Will anything crash?

Will anything crash or stop working if tempdb .mdf file out of disk space?

It might crash, sql server will stop responding or you may not able to perform any action until space allocated to tempdb.
Running out of disk space in tempdb can cause significant disruptions in the SQL Server production environment and can prohibit applications that are running from completing operations.
Refer below article to troubleshoot Temp db out of disk issue
http://technet.microsoft.com/en-us/library/ms176029(v=sql.105).aspx
Please click the Mark as answer button and vote as helpful if this reply solves your problem

Rendered Files problem

In my latest project some rendered footage does not correspond to the actual clip!!!??? I thought that the renderd files are attached to the clip. After moving the transparency back and forth it does show the actual unrendered footage. I moved the clip back and forth few times. But before I never had any problems.
Deleting the preferences did not help. Also I noticed if I change something in the clip and lose the red bar appears on the top the undo will not bring my rendered files back.
What is wrong?

Render files are completely different files. When you add a filter and render, a new clip is made, and the original is left alone. The render file takes the place of the original in the timeline.
If you match frame, you will find the original clip.
I am not understanding your issue. Can you re-state it?
Shane

Problems of executive files after PC crash

My developing PC was crushed last week when LabView project was programming. The culprit is due to device driver conflict from both Keithley USB driver and NI 488.2 driver. After recovered the corrupted project, the executive files started showing errors like"LabVIEW:Memory is full"; "LabVIEW Load error code 33: Could not load front panel data logging...";"LabVIEW:End of file encountered" ; "LabVIEW load error code 12: Could not load connector type map" etc... when executive files were distributed to run-time PC.
I removed all LabView 8.0 developing suite and re-installed LabView 8.2. However, the problem was not resolved. The executive files are ruuning no problems on developing PC but failed on run-time PC.
I brought same source files to another developping PC and made executive files. They are also running fine on run-time PC. Really, I totally have no idea what's wrong with developping PC after crushed. How comes the installer and execution files start having problems even I re-installed LabVIEW? Thanks your kinding answer.

Some of those error codes have two possible causes. They are usually given as:
Possible reason(s):
LabVIEW: Some system capacity necessary for operation is not enabled.
=========================
NI-488: File system operation error.
Since you had problems with the NI-488 driver, my guess is that the possible reason is the second listed . Uninstalling and installing LabVIEW does not automatically uninstall and re-install the hardware drivers. Try doing a repair of NI-488 or completely uninstall that and re-install.

My new iMac with FCPX crashes when rendering complex templates and crashes when exporting with Motion 5

My new iMac with FCPX crashes when rendering complex templates and crashes when exporting with Motion 5
Using Motion 5.0.6 and Final Cut Pro X 10.0.7 on New iMac (December 2012) Mountain Lion,
Intel Core i7 quad-core a 3,4GHz, Turbo Boost fino a 3,9GHz
32GB di SDRAM DDR3 a 1600MHz - 4 x 8GB
Fusion Drive da 3TB
NVIDIA GeForce GTX 680MX 2GB GDDR5
During the rendering of complex FCPX mac crashes and I have to force a restart.
I also happens when I try to export movies with Motion 5.
Does anyone have the same problem with my new iMac?

Problems such as yours are sometimes caused by files that should belong to you but are locked or have wrong permissions. This procedure will check for such files. It makes no changes and therefore will not, in itself, solve your problem.
First, empty the Trash.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Triple-click anywhere in the line below to select it, then drag or copy it — do not type — into the Terminal window:
find . $TMPDIR.. $ -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 -o -acl $ 2> /dev/null | wc -l
Press return. The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
The output of this command, on a line directly below what you entered, will be a number such as "35." Please post it in a reply.

IPhoto 09 Book and Crashing Problems

I've been running into significant problems while constructing a 100pg book within iPhoto 09 that came pre-installed on my macbook pro. To start, the issue seems to be only affiliated with the iphoto book function (calendars seem to work just fine).
Here's what I'm experiencing:
I was in the process of creating a 100pg book. I had approximately 80 pages constructed. During my last session, I constructed the remaining 20 pages, and then began the process to submit the file for printing. It had significant issues suggesting that there were problems throughout my book. When submitting for printing, it indicated I had a problem and needed to resolve it before submission. At this point, looking through the book in iphoto appears to work absolutely fine with no exclamation points of any type.
As a troubleshooting step, I attempted to preview the file to a PDF. It had multiple errors and took a significant time to output because 20-or-so times, I had to click on a message indicating there was an error on a specific page.
So, continuing on, the file output with various problems. I then attempted to adjust the pages that had the problems (replacing photos, etc). During this process iphoto crashed. Upon reopening iphoto, I was unable to access the book at all - iphoto would simply crash.
In desperation, I restored the initial 80-page version. Now I've got that, and I certainly could go through the process of recreating the next 20 pages, but I wanted to verify that I wouldn't run into problems. In testing that, the crashing behavior is still present.
Next, I renamed the iphoto library and allowed iphoto to create a new and blank library. I readded the 5200 photos that I am sifting through for the book. Attempted to create a new book, added the 5200 photos, and then, without even putting an image on a page, tried to remove a photo from the book listings. At this point, it crashes. This is a new library, new file, new import, and same crash.
I've spent hours and hours and hours, and I'm no technological luddite. I am needing some solutions. Can anyone out there help me out?
If need be, I could provide a detailed error log that the crash produces, but as it's pages and pages of info, I thought I'd wait until someone asks me for it.
Thanks for your insights.
-Cody

1 - Apple does not have a problem - you do - this is a problem with your set up not with iPhoto
2 - this is a user to user forum so addressing Apple here has no value
3 - how are you previewing that fails - using the directions here - http://support.apple.com/kb/HT1040 ? How does the preview fail? BTW the fact that you can not create a preview is directly connected to your inability up upload and is connected to the problem with your system
LN

Exporting files out of LR3?

Has anyone had problems exporting files out of LR3? This was very simple in LR2. I receive orders via email, print them out, and then pull up the selected images 1 or 3 or 50 @ a time. LR3 is not exporting over 1 or 2 images and then it freezes up.

Reinstallation will not do anything except aggravate you.
Try:
1. Run Lr from a new user account.
2. Try not exporting to the external drive if you are. If you catalogue or photos are on the external drive, see if you can create a new catalogue containing this photos (import from the other catalogue) and try exporting from that one.
3. If it freezes get the Sample output from the process via Activity Monitor. If it crashes collect the crash log out of your Library.

Renderfarm error: Pre-Flight Error: Unable to import previously rendered file

I have an error message I am receiving during network rendering on a renderfarm, and was hoping for some help. The error is this: "Pre-Flight Error: Unable to import previously rendered file."
Here is my setup and some details:
The user makes a comp, and adds it to the render queue set to render as a quicktime movie file. Then they run a script which precomps everything and sets it to render as a image sequence with "Skip existing files" checked. This comp also has a post-render action set to import & replace usage. After this comp is rendered, it gets pulled back into the project and the original render item starts rendering the movie file using the previously rendered image sequence as it's only layer.
This project gets saved to a server where our render nodes are watching the folder. All the render nodes pick up the project and proceed to render the image sequence. Then, after they are done, 1 machine will pick up the second render item and begin rendering the image sequence into the final quicktime movie.
All of this goes smoothly about 90% of the time. However, in some cases an error shows up in the watch folder html page for the 2nd render item (the one converting the image sequence to the movie). The error says "Pre-Flight Error: Unable to import previously rendered file." After the error occurs, no machines will start rendering the project.
My first guess is that the render engine on one machine somehow skips rendering the image sequence comp, and then tries to render the quicktime movie comp and fails because the image sequence has not yet been rendered. However, I can't figure out why After Effects would skip rendering the first comp.
Does anyone have any idea?
Thanks for the help, and let me know if you have any more questions about the setup,
Adam

Well, you should get used to the fact that it's simply gone... Just looking at your screenshot makes me grind my teeth. From delayed writing of files to fragmentation in user folders to Windows doing obscure things this could be anything, but seriously, saving important files on the desktop? That is simply sloppy data management. There is no other way to say it. Read up on what proper file naming, incremental saving and backups are good for and why keeping work files separate and away from your user home directories is actually a quite simple, yet effective concept to avoid exactly that kind of issue.
Mylenium

IMac (March 2009) - Invalid Node Structure problem

Hi All
I was using my iMac as normal yesterday, when suddenly the system ground to a halt (something I never seen since using OS X). As I had work to do, after about an hour, I restarted, expecting it to be an app misbehaving or something straight forward, but on restart the same thing happened almost straight away.
So, I restarted again, only for the iMac to get stuck on the blue screen which follows the grey 'cog' screen. After looking through these discussions, and some other Mac forums, I booted from the installer disk, tried to run Disk Utility, which found issues and couldn't repair the disk.
I then tried Safe-User mode and fsck, which reported the aforementioned Invalid Node Structure problem. After checking a few more forums, I thought I would try to Erase the disk and reinstall Mac OS. I restored from my Time Machine backup, and finally got it to start, but the system moved at a snail's pace, and wouldn't open any apps or files.
I've tried again with fsck, and also fsck_hfs -r /dev/disk0s2 but all I get is the same error message:
disk0s2: I/O error.
Invalid Node Structure
(4, 38403)
** Volume check failed.
/dev/rdisk0s2 (hfs) EXITED WITH SIGNAL 8
So, does anyone know if there is anything I can do to save the iMac? Or does it need a new HD? It is my primary work computer, so I really need to get it back, and after buying it in the UK, am now in France for 6 weeks, so it's difficult for me to take it to an Apple specialist.
Any help would be greatly appreciated, thanks in advance,
Daniel

As the last user stated, Disk Warrior maybe able to correct it, however if you search the net, you will see there are more than one user with this problem. I had the same problem, however, my machine is out of warranty, It started like you are saying, I RAN disk warrior which corrected the problem long enough to boot the system. In a matter of 10 minutes or so, the system started pausing (apps hung, but in a matter of seconds recovered). I was checking the disk with fsck_hfs and fsck while booted from a USB drive with a maintenance install of 10.5.6. After running fsck the 5th time with different options suggested from the internet, I rebooted with my disk warrior DVD only to find the drive NOT mounted, Drive utility see's it (even can attempt to run disk repair, but it locks up the system when trying this). Disk Warrior doesn't even see the disk to run a directory repair, although in the "check s.m.a.r.t status it sees it as a sata device, and SAYS ITS NORMAL).
Since my iMac was out of warranty, I followed the online instructions to replace the hard drive (not too difficult) and everything is fine now.
The old drive still wont mount, but another utility I bought (data rescue II) has been able to quick scan it and access all the data, even though it wont clear a fsck fsck_hfs or disk warrior, anyways, get it back while you can, IT IS THE hard drive itself, and lots of other iMac users online with the same issue (can you say WHY is my iMac SOOO HOT on the apple in the back (right where the drive is and not sufficient cooling in my opinion, but hey, some people might want to lay their computers face down and fry eggs on the it or something... ))
-SD

Rendering Files Deleted by...?

Something truly effed up just happened and I'm curious to know if this is a problem with Final Cut or xmas gremlins.
I'm working on an FCE project with source files on an external drive. The drive filled up so I set project settings to point to a local drive for the rendering. I'm working on an hour-long video, which with downconverting and editing takes several hours to completely render, so I left it running overnight and went to bed.
An oh-so-helpful roommate saw the laptop idle (it had finished rendering) so he closed it. Evidently, putting a macbook in sleep mode causes the external drive to disconnect. And evidently disconnecting the source drive for an active FCE project ****** FCE off tremendously. And FCE gets spiteful and mean and exacts revenge by deleting all of your rendered files. So when I awoke, I'd lost every last one of my rendered files from the weekend. Not just the latest one, ALL of them!
On the plus side, it freed up a lot of local disk space. But between the tears, I'm also curious - how is this possible? What, exactly, happened? Which step in the chain caused this wanton destruction and was there any way to recover from it? The files weren't even in the trash - they just winked out of existence.

Have your roommate pay the FULL rent for the next three months. While that won't answer your question, it might help to keep this from happening again.
-DH

Firefox crashes when I close an e mail on AOL also it crashed once after printing some pages from my banking statement. Any ideas. I restarted a few times without any change to the crashing problem. WHat do you suggest.

Firefox crashes when I close an e mail on AOL also it crashed once after printing some pages from my banking statement. Any ideas. I restarted a few times without any change to the crashing problem. What do you suggest.
I am using Mozilla Beta 4. I volunteered to try it out. It's lightning fast. I really love using it. I see there is a new version of Firefox should I download it??

I HAVE NOW SOLVED THE PROBLEM BY RUNNING WINDOWS REGISTRY REPAIR TOOL WHICH HAS OBVIOUSLY REPAIRED CORRUPT REGISTRY FILES.

Shake Rendering File out Node Crashing problem

Similar Messages

Maybe you are looking for