Mylenium
Forum Replies Created
-
[Agresvig] “What could cause this?”
Simple: MP3s are evil. AE can’t handle them properly. Convert your audio to a WAV/ AIFF file.
Mylenium
[Pour Myl
-
Mmh, there must be something going on with the color profiles. This may be a bug. Once you apply the Compander, you should not get any negative values anymore. They should be clipped at worst. It is supposed to translate all float values correctly to integers and limit the range. If you e.g. have a float value of 1.2 in a HDR image, it does not directly translate to just being full white, because it already is brighter. Without the Compander a non-32-bpc effect might interpret it as too large a number(exceeding 32768) in 16 bpc and either clip values or produce just plain rubbish because it cannot handle those values. I have no ideas further since I too rarley work with film, but perhaps Chris or someone else might have an idea.
[Pour Myl
-
Sorry, I somehow possibly didn’t read your original post correctly. If you can extract the Z-Depth and only the Depth Blur effect doesn’t see it, the I’d simply use the greyscale with Compound Blur or the Lensblur filter in AE 7. Duplicate the layer, extract the depth, apply the blur on the original RGB layer and reference the depth channel in the plugin interface.
Mylenium
[Pour Myl
-
[Wim Roegels] “How do I get a propper grayscale layer for z depth of the comp to put it in lenscare?”
You can’t. Either you buy yet another plugin (Depth Cue) or you create your depth map manually using Ramps or tweaking opacity of white&black layers in a duplicate comp.
Mylenium
[Pour Myl
-
[mjL creative] “And when ever i’ve render one of the country comps (just as a video) it seems to take ages and there is no animation, is there something i’m forgetting?”
Umm, you are working with vector files, aren’t you? So this means AE needs to rasterize them and if it supposed to look good, it needs to be antialiased. For this multiple “versions” of those pixels need to be blended together to look smooth. So what does that mean? At any given time the actual memory needed is effectively larger than the end result or final pixel buffer. At times an vector image can consume up to 32 times the amount of RAM compared to a bitmap image of same size. Similarly, effects consume RAM to create temporary buffers even on still frames. Consequently, the only sensible course of action is: Rasterize your images once, then work with bitmaps in AE. Since you are doing more or less “stills” and don’t seem to be dependant on infinite resolution for zooming and know the resulting final size, nothing speaks against proceeding this way, even if it may mean you will have to work with different bitmap versions at different resolutions.
Mylenium
[Pour Myl
-
You need to install them separately, just like you did when you installed 6.5.
Mylenium
[Pour Myl
-
No, I don’t think that’s the full truth. It explains the shrinkage, but not the positional changes. The point here is, that as long as you only copy&paste a single path, AE will re-center it on the layer you paste to. Only multiple masks/ paths retain their relative positions.
Mylenium
[Pour Myl
-
You can activate the software on 2 systems at any time without jumping hoops, the logic being that you can only work on one system at a time anyways. So you will have no problem working from home and at work. The activation is derived from the serial you enter during the process and a unique install identifier that the Adobe installer generates.
Mylenium
[Pour Myl
-
Do you get the incorrect values after employing the Cineon converter plugin or before? If you use the converter properly, there should be no problems. The errors would only be “normal” without proper color space conversion as indeed AE cannot make proper sense of the logarithmic color table in Cineon files. The error going away in 32 bpc is normal, as indeed HDR images can have valid negative values., but you wouldn’t get technically correct results this way.
[imaxblue] “If I switch to 32-bit, the cyan blobs go away, but then of course I can’t do anything with them either, as 99.9% of the effects aren’t 32-bit compatible. I need to run my cineon projects in 16-bit linear mode.”
I think you are misunderstanding what 32 bpc does and what it is good for. It makes absolutely no sense to have all effects compute in full float and those that are mostly needed in film workflows are 32 bit. So the number of effectively “useless” effects is way below 99,9%. I also fail to see your point on another level: nothing stops you from using the ComPander utility to use 8 bpc and 16 bpc effects with correct results in 32 bpc workflows.
Mylenium
[Pour Myl
-
Check your project settings in Premiere. Sounds like your fields are interpolated due to incorrect footage interpretation/ project settings.
Mylenium
[Pour Myl