Skip to main content
konto4c31193966
konto4c31193966
Participant
April 18, 2018
Answered

Problems when rendering .json-driven project in media encoder

  • April 18, 2018
  • 2 replies
  • 2251 views

Hi.

I am making a weather-forecast-thingy. Was very happy with the new data-driven update. Until I tried rendering in media encoder. Where there is supposed to be temperatures, all I get is "NaN". When I render directly in AE it works like a charm.

I get my data from a .json-file. Linked the source text directly with expressions e.g. "Math.round(footage("weather.json").dataValue([2,5,0]))". Any ideas where and why things get wierd?

    This topic has been closed for replies.
    Correct answer konto4c31193966

    I got it working. Seems like media encoder won't recognize the json-file if its only in the project-window. Although, if I use it as a layer anywhere in the project everything suddenly works. No need to re-adress any expressions or anything. Weird, but working.

    ps. Thank you Mylenium for your answer. I got a whole automation-script going and the client needs their files as h264 so excluding media encoder ins't really an option. Unfortunately. Unless you have a great, not too mind bending, render mending, top notch, ultimate combo solution.

    2 replies

    konto4c31193966
    konto4c31193966AuthorCorrect answer
    Participant
    April 23, 2018

    I got it working. Seems like media encoder won't recognize the json-file if its only in the project-window. Although, if I use it as a layer anywhere in the project everything suddenly works. No need to re-adress any expressions or anything. Weird, but working.

    ps. Thank you Mylenium for your answer. I got a whole automation-script going and the client needs their files as h264 so excluding media encoder ins't really an option. Unfortunately. Unless you have a great, not too mind bending, render mending, top notch, ultimate combo solution.

    J
    jamesw83840845
    Participant
    July 11, 2019

    Dear konto4c31193966​,

    More than a year later, I have the same exact problem - the JSON file works with AE renders, but is entirely not recognized in AME.

    I have tried my best to include the .json file:
    - as a new layer of the entire comp (on top),

    - as a new layer of the entire comp (at bottom),

    - as a new layer in the very specific sub comp that was using the text in the Json (on top),


    ....still the same lousy results on AME renders. I am CC 19 for both. Any idea?

    V
    vonacreative
    Participant
    May 7, 2020

    Yeah, I'm having this problem. I read through this thread, but couldn't see a definitive solution. Did you sort it jamesw83840845?

    Mylenium
    Mylenium
    Legend
    April 18, 2018

    Without seeing the data and the expression it generates nobody can tell you much. that said, expressions always have been sensitive with AME, so if rendering directly from AE e.g. to an image sequence and then encoding later is an option, simply use this workflow. There's usually little point in trying to debug these issues and the rubbish JSON implementation clearly hasn't made anything in that regard easier.

    Mylenium

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices