Codecs/unpacking

Support
1

For a data file generated by MWorks 0.4.3, getCodecs returns:

1 #codec
2 #termination
3 #task_mode
4 #system
5 #announceMessage
6 #stimDisplayUpdate
7 #beamPosition …

For a data file generated in MWorks 0.4.4 using the same protocol, I get:
4 #state_system_mode
5 #announceMessage
6 #stimDisplayUpdate
7 #beamPosition …

It seems like something is different with how the first 4 variables are named in the new MWorks data files (#1-3 don’t even appear). I use the payload information in 4 #system to get my protocol name, but in MWorks 0.4.4, I find the same info in codec 1 (not listed when I do getCodecs). Trying the newer(?) getCodecs.mexmaci included in MWorks 0.4.4 did not resolve the problem.

This is not a critical problem since I have found a workaround, but I thought I would bring it to your attention.

2

Hi Elias,

Thanks for the report. I believe the changes you describe are intentional.

As noted in the 0.4.4 release notes, “task_mode” has been replaced with “state_system_mode”. The others appear to have changed as part of some refactoring of the event-handling code. I suspect they were never meant to be “user accessible” events, hence their removal from the codec.

Chris