Forum Replies Created

Page 64 of 597
  • Kevin Camp

    July 24, 2015 at 8:15 pm in reply to: AE4 settings

    the info panel is usually in the upper-right corner of the ae workspace, but it might be behind another tab (like audio). when you first start a render it can often display what ae is doing… with rmfs it will usually say ‘saving project’ as it saves an instance of the project to load into available cpus, or it might say that rmfs was disabled due to some reason.

    as for the cpus to leave for other apps, i think you have a mac that is similar to mine (Mac Pro 4.1, early 2009 — you can check ‘about this mac’ to see). these machines have 8 physical cores, apple often referred to them as dual quad-core. with hyper threading it looks like 16 cores. one of the general rules-of-thumb for setting up rmfs is to tell ae to use only the physical cores. also, due to some overhead in managing all those cores, you won’t see much of any performance gain past 10 cores anyway.

    and like i said, ae will still use the other cores for any process that are natively multi-threaded, and not reliant on rmfs (which is quite a bit even in cs4), so you’re not really losing performance and could actually gain performance due to having more ram for the other cpus.

    as for the disk cache, i think you’re fine. i typically leave disk caching off… adobe says that after effects will only cache frames that take longer to render than to cache, but it’s been my experience that with standard/mechanical/spinning (how about non-ssd) drives, that disk caching often slows things down, though i don’t think it’s a major contributor to your problem.

    if rendering with rmfs is still slow, you might try disabling it and see if that helps. as i said before, many process are already multithreaded, so it may help to have more ram available for caching.

    Kevin Camp
    Art Director
    KCPQ, KZJO & KRCW

  • Kevin Camp

    July 24, 2015 at 6:40 pm in reply to: AE4 settings

    looking at your screen shots, either you have an effect of an expression that is disabling ‘render multiple frames simultaneously’, or your settings are preventing it from working well.

    if you can see the ‘info’ panel in ae when you start a render, it will tell you if rmfs is turned off for some reason (effects or expression) when you start a render. if it does say that, then you might try disabling refs in the preferences (though i don’t know if that would help).

    your rmfs settings look pretty good, though i think you should set the cpus reserved for other apps to 8 (i’m assuming you have only 8 physical cores, with 8 more being logical/hyperthreaded cores). that may allow you to assign more ram to each core, though cs4 may be limited to 2gb per core. also, ae will still use as many cores as it can for multi-threaded process so you’ll typically see the logical cores get used quite a bit, so don’t think you are losing out on performance.

    i’d also try quitting all other open apps to leave as much ram as possible for ae.

    Kevin Camp
    Art Director
    KCPQ, KZJO & KRCW

  • it wasn’t related to the version of yosemite, it worked fine on yosemite 10.10.1 (that was the installer i had disk imaged to a usb stick). it’s an issue with the install of my current (soon to be late) yosemite which is up to date. there must be some settings somewhere that are creating issues between C4D and AE when using the Cineware plugin.

    to troubleshoot, i had partitioned my drive, installed mavericks, installed ae cc14 and checked the C4D integration. when that worked, i wiped that partition and installed yosemite (10.10.1) and cc14, and when that worked I updated that os to the latest, and it still worked.

    so then, i went back and started to try and ‘reset’ my current yosemite install (on the main partition), reset network settings, no firewall, cleared a bunch of preferences, re-installed ae cc14, but nothing worked… so i’ve cloned the main partition and as i have time, i’m rebuilding that system drive.

    Kevin Camp
    Art Director
    KCPQ, KZJO & KRCW

  • Kevin Camp

    July 21, 2015 at 10:07 pm in reply to: Wiggle expression on scale, but only make smaller

    i may be missing what you’re after, but here’s a file with a solid that has that wiggle expression that makes the scale only change to a smaller value:

    9065_wigglenegonly.aep.zip

    i added a transparent red square of the same size (w/o the expression) to show that the wiggle scale never exceeds that size.

    Kevin Camp
    Art Director
    KCPQ, KZJO & KRCW

  • i did finally find a solution and posted it here:

    https://forums.creativecow.net/thread/50/862862

    Kevin Camp
    Art Director
    KCPQ, KZJO & KRCW

  • Kevin Camp

    July 21, 2015 at 7:23 pm in reply to: Using Cineware effectively

    after trying everything i could find to fix this issue, including suggestions from maxon support, the only fix worked was to do a clean install of yosemite without using migration assistant (last suggestion by maxon), then reinstall everything form the ground up. then it works beautifully (i’ve only test on CC 2014, but i’d expect 2015 to work too).

    things that i tried, but did not work for me:

    • turn off wifi (already off, but toggled it on/off anyway)
    • reseting AE prefs
    • reinstall AE CC 2014, tried both the original 2014 and updated/latest 2014 — the original had cineware v1.0 and C4D lite r14.0, the updated hade v 2.0 and r16.0, respectively.
    • reset network settings.

    Kevin Camp
    Art Director
    KCPQ, KZJO & KRCW

  • Kevin Camp

    July 21, 2015 at 5:04 pm in reply to: Wiggle expression on scale, but only make smaller

    we needed to remove the base value from the wiggled value, then subtract it… this seems to work:

    freq = 5;
    amount = 35;
    w = wiggle(freq, amount);
    s = scale[0] - Math.abs(w[0] - scale[0]);
    [s, s]

    just link your sliders to the corresponding variables.

    Kevin Camp
    Art Director
    KCPQ, KZJO & KRCW

  • Kevin Camp

    July 21, 2015 at 3:38 pm in reply to: Wiggle expression on scale, but only make smaller

    you could just subtract the wiggle from the scale value…

    try changing w to something like this:
    w = value[0] - Math.abs(wiggle(thisComp.layer("frequency").effect("Slider Control 2")("Slider"),thisComp.layer("amounts").effect("Slider Control 2")("Slider"))[0]);
    [w, w]

    Kevin Camp
    Art Director
    KCPQ, KZJO & KRCW

  • Kevin Camp

    July 21, 2015 at 5:16 am in reply to: Expression Suggestion for Adobe

    I think you’re asking for something like spring loaded folders, where you would drag the pick whip, hover over a layer for a second or two and then the properties would open up (twirl down) so you could select one.

    I think that would be pretty useful. You would want to request that here:

    https://www.adobe.com/products/wishform.html

    Kevin Camp
    Art Director
    KCPQ, KZJO & KRCW

  • Kevin Camp

    July 18, 2015 at 9:07 pm in reply to: counter with slider and percentage

    Try simplifying the expression to this:

    slider = effect(“slider control”)(“slider”);
    “” + Math.floor(slider) + “%”

    Kevin Camp
    Art Director
    KCPQ, KZJO & KRCW

Page 64 of 597

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy