Quitter
  • Communauté internationale
    • Langue:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티

valueAtTime() for Levels Properties

Nouveau ici ,
Apr 08, 2025 Apr 08, 2025

Hi! I'm trying to export various properties to a file for each frame of an animation, and I'm a bit stumped.

 

I've been able to pick up frame data for other Effects, such as hue and saturation within Color Balance (HLS) effect. like so:

layer.property("Effects").property("Color Balance (HLS)").property("Hue").valueAtTime(time, false)

 

However, when I go to do so for various Levels properties (Input Black, Input White, Gamma), it only gives me the data for the frame I currently have selected in the timeline. The only thing I can guess is that TECHNICALLY the stopwatch icon is on the Histogram property, and those are some sort of sub-property that only show up in the effect controls. But not sure if there's a way to get these numbers from the histogram itself in a script? I've tried doing e.g. property("Histogram").property(1) but not having any luck there. Using Property("Histogram") at all seems to just make the script not run at all.

 

Any help would be appreciated! Thank you!

 

Thank you!

SUJETS
Scripting
284
Traduire
Signaler
Directives de la communauté
Restez bienveillant et courtois, ne vous attribuez pas la paternité des créations d’autrui et assurez-vous de l’absence de doublons avant de poster du contenu. En savoir plus
community guidelines

correct answers 1 bonne réponse

Community Expert , Apr 08, 2025 Apr 08, 2025

I think that data is encoded in the Histogram value, which has a propertyValueType of PropertyValueType.CUSTOM_VALUE, which means the data itself is inaccessible to scripting. I don't know if it helps, but maybe you could switch to the Levels (Individual Controls) effect, where all the individual parameters are keyframeable and accessible with valueAtTime().

Traduire
Community Expert ,
Apr 08, 2025 Apr 08, 2025

I think that data is encoded in the Histogram value, which has a propertyValueType of PropertyValueType.CUSTOM_VALUE, which means the data itself is inaccessible to scripting. I don't know if it helps, but maybe you could switch to the Levels (Individual Controls) effect, where all the individual parameters are keyframeable and accessible with valueAtTime().

Traduire
Signaler
Directives de la communauté
Restez bienveillant et courtois, ne vous attribuez pas la paternité des créations d’autrui et assurez-vous de l’absence de doublons avant de poster du contenu. En savoir plus
community guidelines
Nouveau ici ,
Apr 11, 2025 Apr 11, 2025
LA PLUS RÉCENTE

Thanks! Yes that's precisely what I ended up doing. There's lots of extra settings there that will need to be ignored for my purposes (only using the RGB controls), but it at least functions!

Traduire
Signaler
Directives de la communauté
Restez bienveillant et courtois, ne vous attribuez pas la paternité des créations d’autrui et assurez-vous de l’absence de doublons avant de poster du contenu. En savoir plus
community guidelines