When I open an *.awj created in AWE Designer 8.C.2.4 Standard, into AWE Designer 8.C.2.7 Pro, it fails with the error:
Unable to parse the loaded file: c:\filename.awj
Unrecognized field name 'isInterpreted'.
Is it expected that this should work?
When I open an *.awj created in AWE Designer 8.C.2.4 Standard, into AWE Designer 8.C.2.7 Pro, it fails with the error:
Unable to parse the loaded file: c:\filename.awj
Unrecognized field name 'isInterpreted'.
Is it expected that this should work?
3:56pm
Hi Toby,
I tried creating pass-through .awj files using 8.C.2.4 and 8.C.2.7 (using both Standard and Pro for each version) and opening each of the 4 files using each of the 4 versions of AWE Designer. I was able to do this successfully.
The isInterpreted field relates to whether or not a custom made Audio Weaver module can be shared with users of Standard Designer. The Interpreted Module feature was rolled out in 8.C.2.5. It is surprising that you report an .awj created in 8.C.2.4 (prior to Interpreted Modules existing) contains the isInterpreted filed (the .awjs I generated using 8.C.2.4 do not), and yet 8.C.2.7 which should be able to support the isInterprted field throws the error.
Can you please share an example .awj that is giving you this error?
Thanks,
Michael
11:21am
I'm attaching a file created in 8.C.2.4 that, when opened in 8.C.2.7 Pro, yields:
"Unable to parse the loaded file: issue demo.awj
Unrecognized field name 'isInterpreted'."
Curiously, if you inspect demo.awj in a text editor, it doesn't actually contain the word isInterpreted.
3:50pm
Hi Toby,
Thanks for sharing the file. I am able to open it in 8.C.2.4 Standard but am unable to open it in 8.C.2.7 (Standard or Pro). The error message I receive is slightly different: "Reference to non-existent field 'isInterpreted".
I've attached an .awj file I generated using 8.C.2.4 Standard which I can open in 8.C.2.7.
test_8c24_standard.zip
I see the only module in your .awj file is an Inspector Panel. I created in 8.C.2.4 a copy of my attached file which also includes an Inspector Panel, and that produces the same error message when I try to open it in 8.C.2.7. To help us identify whether or not the Inspector Panel is the root of the issue, can you please try to open my .awj file (or create your own without an Inspector Panel and open that) in 8.C.2.7 and report back on the behavior on your end?
Thanks,
Michael
10:04am
Thanks.
I am able to open your test file, as shown:
2:04pm
Hi Toby,
Thanks for the confirmation. I think I have enough information to report the issue to our Platform Development team. Thanks for bringing it to our attention, and we'll circle back when we have an update.
Thanks,
Michael
7:36pm
Hi Toby,
AWE Designer 8.D.1.1 includes a bug fix for this issue. Thanks again for bringing it to our attention. You can download the latest version of AWE Designer from our website: https://w.dspconcepts.com/downloads
Thanks,
Michael