Skip to main content
Participant
Oct 20, 2017 9:31 PM UTC
Question

AE 2018 JSON character encoding....

It appears that the JSON support in AE 2018 is somewhat limited.

I have been doing some experimenting and it looks like it will only work with files encoded in Western (Windows Latin 1). When I tried using a UTF-8 encoded file with Hungarian characters they came out all messed up.

Anyone have any ideas?

Chris

    This topic is closed to new replies. Start a new post to keep the conversation going.

    10 replies

    Participating Frequently
    Jun 2, 2022 7:47 AM UTC

    This problem still exists with large json files. It happens somewhat random. Sometimes it doesn't happen and I can't tell why. All I can say adobe products are never worth their money... truly abysmal software. The worst I ever used.

    Trash adobe software has cost 2 people 3 days of work just for figuring out the bug and creating a workaround. The day adobe is replaced by a better product company the world will be a better place.

    Translate
    Roland Kahlenberg
    Legend
    Jun 2, 2022 12:55 PM UTC

    1) Are you batch rendering - if yes, approximately how many Comps at one go? 
    2) Are you using the new Multiframe Rendering Engine (MFR)? 
    3) Have you faced issues if MFR is turned off?

    Translate
    Very Advanced After Effects Training | Adaptive & Responsive Toolkits | Intelligent Design Assets (IDAs) | MoGraph Design System DEV
    Participating Frequently
    Jun 2, 2022 2:26 PM UTC

    1) one comp queued 93 times media encoder with different texts and images
    2) yes, and now I tested it with the MFR Emgome off

    3) yes, exactly same problem. Non english characters are converted to word salad

    Translate
    Premiopolis
    Inspiring
    Nov 21, 2017 5:51 PM UTC

    Thanks goose023​ & r2-no-d2 for posting.

    One partial solution that works in limited circumstances is to to save the JSON encoded as Western (Windows Latin 1)

    On Mac OS this approach covers all of goose023's characters except for the double acute accented u: ű

    So this hardly not intended as a solution -- r2-no-d2's example characters, for instance, won't work with this approach -- but it got me through a few challenges.

    Filing the following bug report:

    Concise Problem Statement

    JSON data files used in AE Expressions don't handle full UTF-8 charset

    Steps to Reproduce the Problem:

    1. Create a JSON file with values that include non-standard characters (like åéüÂàñÿåò Kompakt és felhaznát, kisméretü padlótisztitó ű∂ ñÑ ÿåî Ă ă  â Đ đ Ê ê Ơ ơ Ư ư ờ ắ ờ) (non US alphabet w/ accents / diacritics)

    2. Use that JSON data in an expression to generate on-screen text (e.g. footage("sample1.json").sourceData)

    3. Make sure JSON file is encoded as UTF-8

    Results:

    Different characters on screen than in JSON file

    Expected Results:

    Same characters on screen as JSON File

    See following Adobe Forums discussions for more detail:

    https://forums.adobe.com/message/9904160#9904160

    https://forums.adobe.com/message/9927469#9927469

    Translate
    Legend
    Jul 29, 2018 3:46 PM UTC

    It seems like the UTF-8 for imported JSON files issue was resolved in 15.1.1, but what about double quotes?  If a string value has an escaped double quote, AE 15.1.1 still interprets it as faulty JSON.  Is there a best-practice for inserting double quotes into the string?

    Here is a sample:

    [

      { "description" : "This is a sample with \"standard\" double quotes" }

    ]

    If you save that as a .json file, and try to import AE will throw an error.  If the escaped double quotes are removed then the .json file imports fine.

    Is escaping double-quote characters in JSON not supported by AE?  Single quotes / apostraphe's seem to work.

    Thanks,

    Arie

    Translate
    Kevin J. Monahan Jr.
    Legend
    Nov 17, 2017 12:30 AM UTC

    Hi Chris,

    Sorry for the frustration. Please file a bug here.

    Thanks,
    Kevin

    Translate
    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    Inspiring
    Oct 21, 2017 9:28 PM UTC

    Same problem ) 1251 does not work. utf8 does not work.
    hkcfibZ.jpghttps://i.imgur.com/hkcfibZ.jpg

    Translate
    goose023Author
    Participant
    Oct 21, 2017 9:36 PM UTC

    This is what I'm inputting and what I'm getting out...

    Translate
    Szalam
    Community Expert
    Community Expert
    Oct 23, 2017 8:01 PM UTC

    I would recommend filing a bug report.

    Translate