Just out of curiosity, have you actually tried making this layer via batchPlay? As far as I know, you can’t actually automate the creation of this particular type of layer. Yes, you can record the corresponding actions (via script listener or Alchemist) but in my experience that’s where you kind of hit a dead end. The input for this layer is a LUT which Photoshop internally converts to an ICC profile and it’s that ICC profile that gets passed around in the recorded action (not your original input LUT). Unless you know how to create this ICC yourself to the exact specifications/format that Photoshop needs I think you may have to wait until there’s an API function that can also do the LUT conversion.
By default Alchemist does not generate Raw Data into generated code due to performance concerns. But you can turn it on in settings and then you can make ColorLookup layer via batch play. Not as nice as DOM but possible. First you make a layer and then you set its content.
You should probably also change “name” properties accordingly.
In raw data it is binary encoded as base64. But I can’t really tell what is inside since I haven’t looked. As somebody suggested conversion might be necessary.
To make things simpler there is also an option to show RawData as array of numbers so it won’t be encoded as base64 and you can have quick look. This of course is not a valid descriptor and serves only for research as it cannot be replayed back in this shape.
seems that there’re two different datas:
-data in LUT3DFileData section. This is clear. It’s just encoded to base64 data from lut file.
-data in profile section. And this is the dark horse…
PS. I’ve investigated, that this profile data is generating every PS launch. Because it’s slightly differs from launch to launch. So I can’t generate or just substitute it