Global Initialization and Destruction

The sACN library has overall init and deinit functions that should be called once each at application startup and shutdown time. These functions interface with the EtcPal log (Logging) API to configure what happens when the sACN library logs messages. Optionally pass an EtcPalLogParams structure to use this functionality. This structure can be shared across different ETC library modules.

C C++

// During startup:
EtcPalLogParams log_params = ETCPAL_LOG_PARAMS_INIT;
// Initialize log_params...
 
sacn_init(&log_params, NULL);
// Or, to init without worrying about logs from the sACN library...
sacn_init(NULL, NULL);
 
// During shutdown:
sacn_deinit();

// During startup:
etcpal::Logger logger;
// Initialize logger...
 
sacn::Init(logger);
// Or, to init without worrying about logs from the sACN library...
sacn::Init();
 
// During shutdown:
sacn::Deinit();

Individual features can also be initialized separately. The rest can then be initialized separately, since redundant initialization is handled to allow cases such as the following:

C C++

sacn_init_features(NULL, NULL, SACN_FEATURE_DMX_MERGER);
 
// Later on, initialize everything else
sacn_init(NULL, NULL);
 
// During shutdown (redundant init tracking keeps DMX merger alive):
sacn_deinit();
 
// Then clean up DMX merger
sacn_deinit_features(SACN_FEATURE_DMX_MERGER);

sacn::Init(SACN_FEATURE_DMX_MERGER);
 
// Later on, initialize everything else
sacn::Init();
 
// During shutdown (redundant init tracking keeps DMX merger alive):
sacn::Deinit();
 
// Then clean up DMX merger
sacn::Deinit(SACN_FEATURE_DMX_MERGER);

You could also flip the init or deinit calls - order doesn't matter here (beyond calling init before deinit of course).