There's a few things to check here when tracking down the problem (if indeed there is one). Most people who've reported an actual problem have had files disappear while they were watching the folder. This was due to certain inconsistencies in filters and XMP based data. Unfortunately, the same mechanism that allows you to instantly update other programs with changes you make in your current front application is the mechanism that may be causing this problem. Some of the programming for the opening of projects forces the XMP data to change, which calls the render engines in the filters to re-render in case there have been changes. By turning this off, you lose the ability to instantly update open programs with cached data. The way to combat this last part is to reopen any program you need to or switch to it, and see if the dialogue comes up to update the data.
There are quite a few who report a problem but don't actually try to give any kind of detail about their system or the circumstances that go along with the problem. Their cause may be completely different. Some report better results with an existing empty sequence selected, which may update the XMP of only that sequence on closing, and only the xmp of that sequence on opening. Hard to tell when they won't give any other info.
"I rendered and closed the file, but now it's not rendered" is not a legitimate problem description.
"I rendered a 1080i 29.97fps 48k sequence with ProRes clips with the main sequence selected in project panel and a clip selected in the timeline, a warp filter about halfway through, a few crossfades in audio and video throughout; on a mac pro, i7 x.xghz with 16gb of ram (cuda\no cuda) NNN graphics card at MMM VRAM; AV source is on a network server\local drive, caches are on main drive\network\external, previews are on a network drive\internal\external; with these preferences for Metadata: Write XMP on import\open on\of, keep cached copies next to originals on\off, render audio with video on\off; AND when I reopened the project, the render was completely undone" THAT is a problem description that can be used for troubleshooting. Please be as specific as possible. It helps troubleshooters work backwards to recreate, narrow down and eventually patch the problem; it also allows programmers who troubleshoot to compare functions for the common operations and trace the data in those operations as well as the logic of the algorithms to find and fix the problem with either an added value\function or by removing\adjusting existing functions.
It is entirely conceivable that the XMP rewrites are causing issues with linkage, and when filters are involved, the newer being compared with the older causes the files to be deleted or at least unlinked. However, recent updates seem to have patched this for some, while other continue to contend that their program doesn't have the fix, and they have not even described their work environment. One or two have actually seen this "fixed" on its own, apparently because they didn't realize that there was so much data coming from their network drives... Remember, if you render previews, it takes a while to load them, since they all have their own headers with metatags. IF they are on an external or network drive, if the format of said drive is in any way different from your main drive, you may experience this issue. WAIT for up to 10 minutes per hour of video previews to load fully before opening sequences. Close all your timelines and save before you close the program\project. This will keep your view fresh when it opens, and if you wait for the 10min it takes to brew a pot and pour a cup, you may find that the problem is all in your "IG" addicted mind (IG is instant gratification).
I work primarily in CS6 on a 10.9.x 2008 MBP with 4gb ram, 256mb Geforce video card, 2 internal 1tb drives, several firewire\esata RAID, network Storage for render farming, and I haven't seen this ever occur, unless I load up from a network location. That is why I use disk images on network drives. Headers are loaded locally into swap, caching is done locally, and previews are all on disk images while I'm cutting. When I render, it sees local connections in the VOLUMES mount location, so when it loads on open, it loads the render headers, and shows them as rendered; I've tried to play back quickly on open... ...which shows the networking speed even when rendered, and occasionally chops a little, especially over wireless when done immediately after open of a project. It would appear that this problem is mostly attributed to XMP headers and caching for one part, but more to networking and patience for another. When I can, I keep my previews and copies next to originals in preferences, but they do have to be relinked to Watch folders when rendering out the whole movie from after effects using a render farm.
My workflow:
sources to after effects together, color balance, Renderfarm to image folders, RAR split and burn to discs, rip audio out using AME, render out to new source video when done. It allows a lot more versatility in resizing for zooms. I'll be putting up a little tutorial on this process but I just wanted you to see how easy it can be to keep your renders small and easy to manage. Simply size your images appropriately, and you can create lossless proxy videos. You can also use compressed encodes to build proxies that actually have better quality zooms, and reduces artifacts and noise.
167
Replies
AdChoices