Forum Replies Created

  • Scott Barnes

    July 28, 2015 at 6:30 pm in reply to: Repeater just stops?

    Thanks so much for confirming this for me. Okay guess it is time to download the older version of AfterEffects and put in a bug report to Adobe. Thanks Ryan.

    I am not bound by what is possible.

  • Scott Barnes

    July 28, 2015 at 4:04 am in reply to: Repeater just stops?

    Well I didn’t see anything in the bug fixes related to replicators so I wasn’t hopeful but being the brave soul that I am. I updated. Alas my demon has not been slain and I must fight on. I am hoping that I am just doing something really stupid.

    I have tried the project on two different machines both with the same result.

    Can someone on 2015 and 2014 test this and see if they get the same behavior. I wanted to test my method to see if something was wrong with it so i just created a new project and comp 1920X1080 23.976 30s long . I then made a square no fill and a stroke of 20 pixels . I set a repeater on it then change the repeater transform to position to 0,0 and scale 75 percent. I then put a keyframe on copies and offset. Copies at 15 and offset at zero. I then go to the end of the timeline and copies at 155 and offset at -50. This is when I will now get an error. I think something is going on with the offset slider. All the error says is After Effects warning: Unknown Exception.

    Am I miss using the Offset slider? I think the offset slider is what is causing the problem. I don’t recall having issues like this before but I haven’t used repeaters in a while.

    I am not bound by what is possible.

  • Scott Barnes

    July 27, 2015 at 7:26 pm in reply to: Repeater just stops?

    The work area covers the entire duration of comp. Is there something else that you might be referring to when you say misadjusted?

    I am not bound by what is possible.

  • If the student comes back in I will see what drive format they have. What they ended up doing was actually starting a new project then relinking all there files. It was a bit of a pain but got it to go away.

    I am not bound by what is possible.

  • Scott Barnes

    September 28, 2013 at 6:15 am in reply to: Phantom Rigs…

    I wanted to offer up a solution for this bug as it happened for me today. First this is not for the faint of heart, so backup before you start and in a lot of cases it could just be easier to delete the object and redo it. In my case I had a lot of other rigging already done to different parameters on the same element and I would have basically had to start over. So I opened up the .motn file in a text editor (I used TextWrangler) apparently its just one great big xml document. So I searched for “Rig Behav”. This will jump you from one Rigged Behavior to the next but if you should be able to figure out what object it is applied to by following it up the tree up as well as what type of parameter your wanting un-rig. So mine was a rotation so when I ignored any Rigged parameters that were position or birthrate or anything else but rotation. Then I deleted everything in-between the tags. This worked for me and might help others out.

    I am not bound by what is possible.

  • I was wondering if this same effect could be done with items that are already in the project or created inside motion. For example I have a bunch of text layers all a single frame that I now need to sequence them out but I don’t have the option of dragging them in from the file browser.

    I am not bound by what is possible.

  • I am seeing this behavior as well. Was anyone able to figure out if this was the normal way that the new Compressor is suppose to work? Does it have to do with the fact that they are sandboxing the whole program? Has anyone figure out a workaround? I am trying to get the most out of the computers in the lab. With compressor 3.5 we were able to set up clusters and they just were always available with out the need for a password is this no longer possible?

    I am not bound by what is possible.

  • Scott Barnes

    September 16, 2011 at 12:03 am in reply to: Not all meta-data available to be filtered?

    I agree I just wanted to make sure there was not something I was over looking.

    I am not bound by what is possible.

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