Skip to main content
Carl Colijn
Participating Frequently
February 11, 2025
Answered

Endianness when saving bytes to Sequence Data in After Effects/ Premiere

  • February 11, 2025
  • 1 reply
  • 232 views

I'm writing plugins for Premiere Pro using the After Effects SDK.  I'm going to start using sequence data too.  In it I will be writing some 32-bit integers and 32 bit floats.  I can see endianness playing a role here though.

 

Does Premiere Pro run on any platform which is big endian, now or in the future?

Correct answer Bruce Bullis

>...now or in the future?

 

We can't comment on the future; what does your testing show you, in the present? 

The SDK Guide discusses saving sequence data, and indicating whether or not it was saved 'big endian':

https://ae-plugins.docsforadobe.dev/effect-details/global-sequence-frame-data/?h=#flattened-and-unflattened-sequence-data

1 reply

Bruce Bullis
Community Manager
Bruce BullisCommunity ManagerCorrect answer
Community Manager
February 11, 2025

>...now or in the future?

 

We can't comment on the future; what does your testing show you, in the present? 

The SDK Guide discusses saving sequence data, and indicating whether or not it was saved 'big endian':

https://ae-plugins.docsforadobe.dev/effect-details/global-sequence-frame-data/?h=#flattened-and-unflattened-sequence-data

Carl Colijn
Participating Frequently
February 12, 2025

Thanks for the link!  For anyone interested, two snippets:

 

  • If your sequence data references external memory (in pointers or handles), you must flatten and unflatten your data for disk-safe storage.
  • You must handle platform-specific byte ordering.

 

I didn't test it at all yet (still busy adding it to the plugin), but I thought it would be a potential issue unless Adobe is sure big-endian machines won't be supported, so I wanted to double-check first.

 

And, indeed endianness plays a role, as was to be expected.  Maybe not in practice (for now), but at least in theory.