[Andy Neil]

Could you try a behavior in the Motion project? There’s a parameter behavior called Ramp that should accomplish what you’re trying to do. Just publish all the parameters and you should be good to go.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

create a range, mark it as a keyword collection. twirl open clip and you can write individual notes to each keyword collection.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

Not sure what you’re asking. Are you asking how to do that level of rigging? Because that is some expert level rigging.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

[Bret Williams] “Still there’s nothing for clip HEIGHT. Except in the event. Why oh why can’t it work the same in the timeline?”

Oh man, that and have programable window configurations. Sometimes I need space for the angle viewer, other times I need the project window to be big. Half my time is spent resizing and adjusting my various windows.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

[Douglas K. Dempsey] “The denigrating appellation “FCPX is iMovie Pro” a couple years back … turns out to be true.”

I’d say, “iMovie is really FCPX Lite” is a more accurate description. iMovie’s code and engine and overall design have changed more due to FCPX than FCPX has changed due to iMovie.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

If you mean that the keyframes are no longer synced with the points you’re ducking than you can just select the range tool, lasso all your keyframes and move them left or right to correct.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

Yes, and there’s also key commands that select the next clip view / previous clip view.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

Here’s the top of your crash thread:

Process: Motion [3400]
Path: /Applications/Motion5.app/Contents/MacOS/Motion
Identifier: com.apple.motionapp
Version: 5.0.6 (213121)
Build Info: Motion-21312001002000000~1
App Item ID: 434290957
App External ID: 12596437
Code Type: X86-64 (Native)
Parent Process: launchd [953]
Responsible: Motion [3400]
User ID: 503

Date/Time: 2014-06-19 07:11:30.814 +0530
OS Version: Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID: 42578A31-1758-5D83-D8AF-3313C0637F5C

Sleep/Wake UUID: BE29FDA6-C2E1-4BEE-B751-66A723EE2FFE

Here’s where it tells you which thread crashed:

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT

These are the parts that reference the thread that crashed:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff87e180e6 objc_release + 22
1 libobjc.A.dylib 0x00007fff87e1765a (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 502
2 com.apple.CoreFoundation 0x00007fff8a978b72 _CFAutoreleasePoolPop + 50
3 com.apple.Foundation 0x00007fff89b7de17 -[NSAutoreleasePool drain] + 147
4 com.apple.AppKit 0x00007fff8da6fbd8 -[NSApplication run] + 725
5 com.apple.prokit 0x00000001000dfd3f NSProApplicationMain + 296
6 com.apple.motionapp 0x0000000100002b2b 0x100000000 + 11051
7 com.apple.motionapp 0x0000000100001a24 0x100000000 + 6692

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0xbaddc19fabc3bead rbx: 0x00006000002660c0 rcx: 0x00000001076db340 rdx: 0x00000000a1a1a1a1
rdi: 0x00006000002660c0 rsi: 0x00000001076db010 rbp: 0x00007fff5fbff320 rsp: 0x00007fff5fbff310
r8: 0x0000000000000fff r9: 0xffff9f7fffdbff6f r10: 0x0000000123edfc60 r11: 0x00007fff745bb390
r12: 0x00007fff87e15000 r13: 0x000060800005ff20 r14: 0x000000010582a070 r15: 0x000000010582a000
rip: 0x00007fff87e180e6 rfl: 0x0000000000010246 cr2: 0x0000000000342000

[Praveen Nu] “Can we able to figure out which parameter/filter/layer is creating problem from the crash report?”

As I said, I’m not a computer programmer and neither are most of the people on this forum. I have no idea what this is telling about your system. Try rebuilding your template or remove effects and re-add on a Mavericks machine.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

Be careful when posting crash threads. Most of the information is of no value to your particular problem. Near the top of the crash thread it will tell you which thread crashed (in your case Thread 0). You need only post that thread and not all the others to people who understand these things.

Having said that, I work with the program, I’m not a computer programmer and most the people in this forum are not going to be able to help beyond vagaries with a crash thread. You’re better off posting the project sans media if you want help.

But my advice without knowing your project is that an effect or something in the project is not playing nice with your updated OS. It could be a number of factors; your project might open on other systems at 10.9.2 and only crash on yours. I’d recommend rebuilding the motion project.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

Well, I finally got past the first couple pages before hitting this…

It made me chuckle. It’s currently 4pm EST. At least I got to see one smallish AE video. Can anyone run down what exactly is new about the site? I don’t lurk adobe’s site much so I’m not sure what’s new or not. Or maybe Steve could link to the demo he was watching?

Andy

https://plus.google.com/u/0/107277729326633563425/videos