Timecode field not accepting a certain numbers/data

Hey all, I’m having difficulty trying to get a timecode populated in a cell in shotgun, all the other codes are accepted but there seems to be the odd straggler that won’t add. The field just goes red and doesn’t accept the code, is there any reason for this? Timecode seems to obey the right format too (01:00:26:26)

I appreciate any help in solving this :slight_smile:
Steve.

2 Likes

Hi Steve, welcome to the community!

I’m sorry to hear about the issue you’re having with the timecode field. When you input the timecode in the cell and it turns red, if you hover over the red cell, is there an error message in a tooltip?

2 Likes

Thank you for getting back to me Bouchep, much appreciated :slightly_smiling_face:

It seems to flash red, clear the field out in a split second, a tooltip does show but for a flash if that but I’ve managed to print screen it. It’s claiming that 01:00:26:26 is somehow an invalid timecode format then states a range the number fits withing :S

2 Likes

I did realize as well that your frame count is 26 as well which is outside the bounds of our default.

Timecode fields support framerates of 23.976fps.

1 Like

Ah right I think I understand now, I’ll just opt for the text field as a compromise as these were for takes/shoots on set :slight_smile:

Much appreciated for your time in looking into this Bouchep

2 Likes

Are there any news on this side? It’d be lovely to see non-24 fps timecodes for us mortals who work on broadcast content :cry:

2 Likes

Hi @alfonso,

Would you be willing to add this as a feature request on our roadmap site (How do I submit an idea or feature request?) , so it can get in front of the product team? It would greatly help out.

1 Like

Hey @bouchep
Just did! Hope it goes through! :slight_smile:
Thanks!!

2 Likes