Arie Stavchansky
My feedback
-
26 votes
An error occurred while saving the comment An error occurred while saving the comment Arie Stavchansky
commented
Also wanted to point out that the "structure" of the JSON includes the data type for a specific property key. So if in one instance, the JSON is a String, and in the next it's a Number, AE will still throw this "JSON has changed" warning.
Arie Stavchansky
supported this idea
·
An error occurred while saving the comment Arie Stavchansky
commented
Agreed. When AE invalidates linked JSON data, it would be best if there was no modal dialog at all since it is likely that the connected JSON might change frequently.
In my scripts I've tried using the app.beginSuppressDialogs() and app.endSuppressDialogs() but those JSON warnings do not react to that code.
Please allow users to silence the "JSON has changed`" error, and just let expressions fail gracefully as they normally do.
Thanks!
-
11 votesArie Stavchansky
supported this idea
·
-
4 votes
Thanks for posting this bug, Arie.
After an extensive back and forth with our developers, we’ve concluded that yes, there’s a bug here. We’ll need to investigate further what’s going on, but the problem appears to connected to the fact that it’s a script, being run by After Effects, that is updating the JSON file.
There was some confusion as to whether we’d expect this to work automatically, without manually calling the Reload Footage command (either in the script or via UI), but that the behavior changed between releases of After Effects tells us that something in the code changed and we should understand why.
An error occurred while saving the comment Arie Stavchansky
commented
Hello,
Has any progress been made to this bug? What is the status of it?An error occurred while saving the comment Arie Stavchansky
commented
Thanks Tim, for looking into it — much appreciated. Yes, it appears to be specific to ExtendScripts writing to imported JSON footage sources. If you do the editing in something else, like Sublime, and hit save, then re-focus to AE it will update accordingly. The bug was manifest in CC 2018, but doing a simple "Reload Footage" was the work around. Thanks again for looking into it! I definitely want to push the JSON feature as far as possible, but it needs to be a bit more stable.
Arie Stavchansky
shared this idea
·
-
339 votes27 comments · Premiere Rush » Editing in the Timeline & Preview Monitor · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Arie Stavchansky
commented
This is a must have, even for on-the-go editing
Arie Stavchansky
supported this idea
·
-
355 votesArie Stavchansky
supported this idea
·
-
3 votesArie Stavchansky
supported this idea
·
-
6 votesArie Stavchansky
supported this idea
·
-
102 votesArie Stavchansky
supported this idea
·
-
126 votesArie Stavchansky
supported this idea
·
-
296 votesArie Stavchansky
supported this idea
·
-
188 votesArie Stavchansky
supported this idea
·
-
10 votes
Thanks for reporting this, and including clear details on the problem. We will investigate this for a future update.
An error occurred while saving the comment Arie Stavchansky
commented
Hi, I posted this on a different thread, but wanted to add it here as the thread's topic relates to special characters in JSON data imported into AE.
Trying to import a JSON file with a double backslash character sequence will cause AE to throw an error dialog.
For example, if an object has a property value like "\\path\\to\\something\\here" then AE will fail to import the file (at least on Windows). The double backslash should be valid string data as it is just an escaped character. However, if you change the double backslash sequence to four backslashes, then AE will import the JSON without error. Then, if you use that data in a sourceText parameter of a Text Layer, for example, it will show a single backslash as the string in the actual text layer.
So, this *doesn't* work if imported:
[ { "myVal" : "C:\\Path\\To\\A\\File" } ]
This *does* work:
[ { "myVal" : "C:\\\\Path\\\\To\\\\A\\\\File" } ]
Probably AE's JSON feature should allow for properly escaped backslash characters. In some cases the JSON file will be used by other applications other than After Effects, and so those applications would need to treat the four-consecutive-backslash characters in the same way that AE does, but as per the JSON spec, a single backslash followed by a single backslash is the documented way to escape the backslash character.
Arie Stavchansky
supported this idea
·
-
11 votesArie Stavchansky
supported this idea
·
-
5 votesUnder Review ·
AdminVictoria Nece
(Sr. Product Manager, Motion Graphics and VFX, Adobe DVA)
responded
Thanks for reporting this. It is a known issue and we’re working on a fix.
Arie Stavchansky
supported this idea
·
An error occurred while saving the comment Arie Stavchansky
commented
Trying to import a JSON file with a double backslash character sequence will cause AE to throw an error dialog.
For example, if an object has a property value like "\\path\\to\\something\\here" then AE will fail to import the file (at least on Windows). The double backslash should be valid string data as it is just an escaped character. However, if you change the double backslash sequence to four backslashes, then AE will import the JSON without error. Then, if you use that data in a sourceText parameter of a Text Layer, for example, it will show a single backslash as the string in the actual text layer.
So, this *doesn't* work if imported:
[ { "myVal" : "C:\\Path\\To\\A\\File" } ]
This *does* work:
[ { "myVal" : "C:\\\\Path\\\\To\\\\A\\\\File" } ]
Probably AE's JSON feature should allow for properly escaped backslash characters. In some cases the JSON file will be used by other applications other than After Effects, and so those applications would need to treat the four-consecutive-backslash characters in the same way that AE does, but as per the JSON spec, a single backslash followed by a single backslash is the documented way to escape the backslash character.
-
28 votesArie Stavchansky
supported this idea
·
-
18 votesArie Stavchansky
supported this idea
·
-
254 votesArie Stavchansky
supported this idea
·
-
329 votes
An error occurred while saving the comment Arie Stavchansky
commented
Check out http://dataclay.com/Templater to learn more.
An error occurred while saving the comment Arie Stavchansky
commented
You gotta check out The Templater plugin for this. It supports merging data for text, footage, color and more. Enjoy! Get the Rig edition ($30) for the simplest data merging tool for AE available.
-
119 votesArie Stavchansky
supported this idea
·
-
126 votesArie Stavchansky
supported this idea
·
Is this simple fix at least in the queue for development. We realize much is going on with the DVA team, but just silencing the modal will help a great deal.