2 of 2
2
cvTokens in R21
Posted: 15 October 2019 08:25 AM   [ Ignore ]   [ # 16 ]  
Total Posts:  1
Joined  2019-09-19

Same here. I’ve used CV-Tokens (in my default “new.c4d” file to work within my project hierarchy) for so long now that I’m lost without it! Haha. It’s not that dramatic, but it just shows what an indispensable tool it is. Thanks for creating it, and really looking forward to using it in R21.

Profile
 
 
Posted: 16 October 2019 09:29 AM   [ Ignore ]   [ # 17 ]  
Total Posts:  1
Joined  2011-12-28

hey,

it’s been some time – any news on this one?
thanks & best

Profile
 
 
Posted: 17 October 2019 06:34 AM   [ Ignore ]   [ # 18 ]  
Total Posts:  9
Joined  2019-05-08

I’m also hoping for an update at some point. Appreciate the hard work and the challenges I’m sure the larger changes going on with C4D there at Maxon.

The beta of cvTokens *appears* to work, at least for my set of conditions — except (big one) — this annoying habit of it using the $frames tag and translating that into the frame number twice. This makes the image list non-digestable by Premiere, meaning I have to use another script to rename all the files. Not great for workflows. And I can’t riddle while the frame numbers writing twice (e.g. 0001_0001) would be of any use.

Could you please add this to the issues list.

Thank you for your efforts!

Julian

Profile
 
 
Posted: 23 October 2019 04:51 AM   [ Ignore ]   [ # 19 ]  
Total Posts:  2
Joined  2013-05-22

Hey!

Any news on availability yet?

Really missing this…

Cheers,
Tobias

Profile
 
 
Posted: 23 October 2019 06:35 AM   [ Ignore ]   [ # 20 ]  
Total Posts:  2
Joined  2019-10-22

While you’re at updating CV Tokens for R21 could you add a token that would allow incremental saving renders? E.g. $ver## - saves render file with the suffix ver01, ver 02 and so on. It would be useful when rendering quick iterations from the same project.

Profile
 
 
Posted: 23 October 2019 06:55 AM   [ Ignore ]   [ # 21 ]  
Total Posts:  1
Joined  2016-03-06

Still no news here? It would be great to get this functionality back. To be honest, I don’t understand why this hasn’t been added to the general release by now?

Profile
 
 
Posted: 23 October 2019 02:40 PM   [ Ignore ]   [ # 22 ]  
Administrator
Avatar
Total Posts:  162
Joined  2013-12-06

CV-Tokens is now available for R21. CV-Toolbox is also live for R21 as well.

We thank you for your patience as we got these releases available.

Profile
 
 
Posted: 07 November 2019 03:11 AM   [ Ignore ]   [ # 23 ]  
Total Posts:  2
Joined  2018-12-12

Hi Bleekerij,

how did you get CV Tokens working in R20?

I tried to install manually, but they don’t apear in the list.

thanks
Mike

Profile
 
 
Posted: 14 November 2019 08:21 AM   [ Ignore ]   [ # 24 ]  
Total Posts:  9
Joined  2019-05-08

@mohnrich — sorry for the tardy reply. The notification may have gotten lost. I am using R21. I believe that the CV Tokens I was beta testing was specifically updated for R21, and thus may not work in R20. I had no problem installing it in R21. (There are still some issues, as mentioned in the posts I made above, specifically with the $frames tag which products the frame number twice, unfortunately. I have to run a re-name script on all my frames to make it work with a workflow to translate the frames into a video file using Media Encoder.)

Profile
 
 
Posted: 18 January 2020 08:15 AM   [ Ignore ]   [ # 25 ]  
Total Posts:  9
Joined  2019-05-08

Hello — any chance the CV Tokens could be modified to not output the frame number twice? Or perhaps I’m missing something? When I use the $frames token, my output might look something like this:

Main_0023_0023

for $cvTake_$frame

The problem is that the ingester for Premiere and Adobe Media Encoder won’t work with this. I have to use a tool and some Regex Jujitsu to rename all the files. Seems like a needless additional step, unless I’m missing something with the usage?

Thanks for your assistance.

Julian

Profile
 
 
   
2 of 2
2