Ok, I'll let you off the hook. I feel like I can pick from where the code is now and move on. I'm gonna set it to SOLVED.

Thanks a lot for your time!!!

Hi! Almost there, almost there...

I replicated your setup and simply pasted the code above. I haven't analysed it, yet.

It works, but only the first marker for each MotionLayer gets a MotionClip. Please, try adding more markers, something that repeats like "A" "A" "B" "A" "C" "D" "A". There's no need to worry about MotionClips superimposing in the same MotionLayer because the semantics behind those markers guarantee there will never be a case where the MotionClips repeat in such a short span of time.

I'm sorry I can't reveal more about the nature of those semantics, it's not supposed to go public, but I promise I'll send you an .mp4 showcasing the amazing results this script helps come true.

Hi! Yes, I knew editing was possible, but I also thought purging posts was possible, and I messed up. Lesson learned!

The only terminology mistake from me was "Motion Clips being containers for Motion Sources". I think we'll get to the same page this time, now that I understand things a little better. Here's what I have in mind:

• all Markers exist;
• all Motion Sources exist;
• all Motion Layers exist, one for each Motion Source, because multiple Motion Clips can overlap several times;
• No Motion Clips;
• I would select the object with the Motion System tag before running the script;
• The script would start Motion Layers iteration;
• Inside Motion Layers iteration, it would start a markers iteration;
• This iteration would check if the current marker matches the current Motion Layer's name;
• If so, it would create a Motion Clip dynamically, maybe via c4d.CallCommand(465001176, 465001176), place it at the current marker in the current Motion Layer, then link the Motion Clip to the proper Motion Source with [c4d.ID_MT_CLIP_SOURCE].
• Then it would set both [c4d.ID_MT_CLIP_VIEWSTART] and [c4d.ID_MT_CLIP_VIEWEND];
• move on to the next marker and start a new iteration - until there are no more markers;
• move on to the next Motion Layer and start a new iteration - until there are no more Motion Layers;

it's no big deal if I have to manually select each Motion Layer and run the script again. I'm trying to create this tool because having to drag dozens of Motion Sources to the Timeline Markers in every project sounds like a waste of time.

I've read somewhere I'm supposed to avoid using CallCommand, it's just that I don't know if there's a method to create a Motion Clip on the fly.

I've just thought of something else: after creating a Motion Clip with CallCommand, I'd still need to find it - and it has to be the right one, before any attributes get modified. How would I make sure it's the one the script had just created, and not another one from a previous iteration? Would it always be the last on a stack? Would I have to store them in some sort of list?

Thanks again!

Hey, thanks for your reply! There's no need for apologies, Maxime, you've kept in touch and I understand it takes time to figure things out, especially in C4D with its broad range of resources. Your software is a solid robust beast.

Enough of that... lol!

I have one question right away:

When you say "you have to do it manually", you mean I have to drag Motion Sources to Motion Layers so that they become Motion Clips before I run the script?

If so, this could be a problem because I may have dozens of repetitions for each "a", "b", "c" or "d" depending on the project I'm working on... unless I could create Motion Clip copies dynamically inside a loop. Is that possible?

@m_adam Ok, thanks!

Hi! You could go for CTracks via Python. You'd have to get the track for a position parameter, for example, or create one, then get curve, then add keys. Later, you could simply range map it back to your Xpresso rig. it It's definitely doable!

Thanks, Maxime! Cheers!!!

The struggle goes on...

As long as a Motion Layer is selected, it is possible to add a Motion Clip via c4d.CallCommand(465001176, 465001176).

Motion Clips themselves show up with some interesting parameters in the AM. Among them:

Source: [c4d.ID_MT_CLIP_SOURCE]
Start: [c4d.ID_MT_CLIP_VIEWSTART]
End: [c4d.ID_MT_CLIP_VIEWEND]

How can I get access to those parameters from Python? How can I get access to the Motion Layers?

Any pointers?

Hello, there!

I have four custom Motion Sources named "a","b","c","d" and several markers named the same way spread all over the Timeline.

My Python script is supposed to look at each marker's name and place the corresponding Motion Source match at its time - the Motion Clip layers were also previously created so that different Motion Sources may overlap.

The problem is I can't find a way to go through the Motion Sources list and compare names, let alone insert them. The Script Log shows nothing when I drag'em manually to Layers in the Timeline.

I've searched everywhere and all I have found is stuff about CTrack, but I guess that's not the right path.

I'm beginning to think the solution is somewhere hidden in DescID / DescLevel and the Motion tag, stuff that I have never needed to mess with.

Could anybody help, please?

Thanks in advance,

Leo