Hello @HolgerBiebrach , I'm wondering if your question has been answered. If so, please mark this thread as solved. best wishes, Sebastian

Hi @zhhm156 I'm wondering if your question has been answered. If so, please mark this thread as solved. Cheers, Maxime.

Note c4dpy does not work with a R20 free educational license. But c4dpy runs fine with a paid R20 student license.

Hi @Hexbob6 I'm wondering if your question has been answered. If so, please mark this thread as solved. Cheers, Maxime.

@m_adam Cool. Thank-you for your time and patience.

Hi Maxime. Thanks a lot. That helped me.

Hi @mikeudin, I'm wondering if your question has been answered. If so, please mark this thread as solved. Cheers, Yannick

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

Hi @Swinn are you sure in your script you define in line 19/20 settings[c4d.VOLUMETOMESHSETTINGS_ISO] = -5.51 settings[c4d.VOLUMETOMESHSETTINGS_ADAPTIVE] = 0.0 With the same value, you got in your volume mesher object? The voxel range threshold can't be directly passed as an argument, but you can expand this parameter in the volume mesher and then you get the Use Absolute Value (ISO) check box, which let you choose an ISO value. Cheers, Maxime.

Hi, @y_puech I may find a bug of the forum about "mark a post correct answer", discussion post here: Cannot mark post as answer Once this bug solved, I will re-edit this topic and posts correctly.

Hi @dmp, sadly as you already figurate out datarate want a BytesValue, which is not yet implemented in the maxon API (as it's been said, currently the python maxon API is still on progress and they are some flaws or missings class like this one, which will be fixed in futures release). And I'm afraid there is no workaround for it except switching to C++. With that said. For all other parameters, maxon API also introduces some new types like maxon.Int (which point to maxon.Int64 if available or maxon.Int32). According your issue with custom samplerate and audio kilobitrate, only few values are accepted. MAXON_ATTRIBUTE(Int, AUDIO_SAMPLERATE, "net.maxon.mediasession.mf.export.audio.samplerate", RESOURCE_DEFINE(ENUM_32000, 32000) RESOURCE_DEFINE(ENUM_44100, 44100) RESOURCE_DEFINE(ENUM_48000, 48000)); MAXON_ATTRIBUTE(Int, AUDIO_KILOBITRATE, "net.maxon.mediasession.mf.export.audio.kilobitrate", RESOURCE_DEFINE(ENUM_96, 96) RESOURCE_DEFINE(ENUM_112, 112) RESOURCE_DEFINE(ENUM_128, 128) RESOURCE_DEFINE(ENUM_160, 160) RESOURCE_DEFINE(ENUM_192, 192) RESOURCE_DEFINE(ENUM_224, 224) RESOURCE_DEFINE(ENUM_256, 256) RESOURCE_DEFINE(ENUM_320, 320)); If you have any question left, please let me know. Cheers, Maxime.

@m_adam said in R20 Startup script location - python_init.py: This will be fixed within a future release. Well, that's a relief then. Good to know. Thank you Maxime for the clarification. Kind regards, Tom

Hello, Set Driven Keys is just some workflow to create an Xpresso setup connecting two parameters. This has nothing to do with scripting or CallCommand(). Can you maybe explain somehow differently what you want to achieve? best wishes, Sebastian

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

@m_adam Thanks Maxime, I'll check that out. The customer was using R23.110

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

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!!!

@mike No need to apologize, we are all new here. No worries. Especially during the starting phase of this new forum, we try to point even at small issues, hoping it will lead to a cleaner forum in future.

Hi, just a small request from our side: Please do not cross post to different forums (this topic on CGSociety). Chances are, you'll make people work for you redundantly. Cheers, Andreas