@r_gigante Oh！Thank you！The plug-in ID is the reason for the problem，use another shorter number and everything is ok. Thank your for your help!

Please consider to sets the topic as solved if it's the case. Cheers, Maxime. EDIT: I've done it, but feel free to set it back to Open if you feel the need to ask more questions.

Hey @mrittman, i cant find the id names in documentation but i think CID_SOUND_START would be the timecode of when the audio starts (notice you are assigning a BaseTime object to it) CID_SOUND_NAME which i'm using is the audio file path. My application is taking the audio file path and the image sequence output (as defined by the render output settings) and combining them via a subprocess using ffmpeg. If there was a way i could do it straight through c4d id prefer that! Mainly cos ffmpeg is a mission! especially when you need to shift/delay audio and what not.

Yeah, definitely. When porting old code that I didn't write to new C4D releases, I always add lots of comments, so people who come after me won't have the same problems ;-)

It builds, and the source processor does not complain. Thank you!

Sebastian, Added tags. Not really a question but a request. I thought that I had read about people adding a TreeView to the AM using GetDDescription() but maybe it wasn't as well fleshed out as they (or I) suspected. I will look into the custom data type and GUI for it. Please mark as Solved. Thanks! Robert

@m_adam Hi Maxime, It works like a treat! I've ended up changing the UI to a treeView and it's still working great. Thank you very much! Andre

Hi, thanks for pointing out this issue. We'll see if can get a fix for that (not all tags visible, if zooming in with browser). In the end Maxime wasn't referring to tags at all. Instead he was talking about the Q&A Function we have in this forum. I took the freedom to mark this thread as solved (see this shiny green stamp next to the headline ). Cheers, Andreas

Seems like this is a way to go. LONG TEST_BUTTONS {CUSTOMGUI QUICKTABRADIO; CYCLE{ TEST_1; TEST_2; TEST_3; }FIT_H;} Previously my mistake was that I was writing CUSTOMGUI QUICKTABRADIOBUTTON instead of CUSTOMGUI QUICKTABRADIO

Hi, no, you are not! Really there are no stupid questions and please do not delete such posts. Especially not, if you already invested time in posting the correct answer. We'd rather see this as knowledge others might benefit from in the future. Cheers, Andreas

@cairyn Awesome! Appreciate your time! Andre

Good news. And... more good news. The best news are that, after creating a Debug version and running Cinema 4D R20 from XCode, all of a sudden, the plugin started working!!! I then created a simple build (not a Debug one) and it is still working fine :-) The other good news is that I now know how to create a Debug version :-)

@r_gigante Thank you for your help. I used the maxon::String and it works fine.

Thank you for the kind help! @m_adam: The plug-in you have linked is very useful. I could fix some problems with the "Select polygons by normal direction" function. Working with badly constructed meshes is no fun job either way. Kind regards, Julien.

Thank you! In future I will set the tags.

@mp5gosu Thank you, that is a good tip. I see that Onull=5140 is listed and it looks like all others are in there too! Thom

Thanks very much. (There is so much information to be read!). -Pim

Hi, just want to ask, if can consider this topic as solved. Bye, Andreas

Hello, I'm not really sure I understand what you are doing. Are you operating in a command line version of Cinema? Or is you code reacting to some command line arguments? Are you operating on the currently active BaseDocument? As I said, I don't have Indigo Renderer so I can't test this specific scenario. But when you "change" the renderer, you also have to "create" that renderer video post when operating in a new document. So it is not enough just to change the RDATA_RENDERENGINE parameter. This example shows how to set and create the "Hardware" renderer: renderData = doc.GetActiveRenderData() if renderData is None: return # set Hardware as active renderer bc = renderData.GetDataInstance() bc[c4d.RDATA_RENDERENGINE] = c4d.RDATA_RENDERENGINE_PREVIEWHARDWARE # add Hardware post effect # in Python a BaseList2D object must be created videoPost = c4d.BaseList2D(c4d.RDATA_RENDERENGINE_PREVIEWHARDWARE) renderData.InsertVideoPost(videoPost) c4d.EventAdd() You find general information on RenderData also in the C++ documentation: RenderData Manual. best wishes, Sebastian

That's it! :) Thank you so much, mp5gosu! Cheers, Mark.