Thread safety of low level transcoder about basis_universal HOT 6 CLOSED

Hi - The current design has some state in the basisu_transcoder object. There's m_lowlevel_decoder (the m_pFile_data/m_file_data_size members are dead code and I'll remove them on the next checkin). There's also m_block_endpoint_preds[], which is only temporarily used while transcoding.

m_lowlevel_decoder doesn't became valid until you call start_transcoding(), which signals your intention to start decoding texture slices. So you can use a single global instance of basisu_transcoder to query for basic file information (like get_file_info() etc.), and that would be thread safe in the current design. But once you call start_transcoding(), the local state becomes valid, and is used during transcoding.

So you can't have a single global object and call start_transcoding() on it from multiple threads. If you have multiple .basis files that you want to transcode simultaneously, you'll need multiple basisu_transcoder's.

Right now, you can't call transcode_image_level() from multiple threads on the same object, because m_block_endpoint_preds[] (which is used during transcoding) is per-object state. I will fix this this week. The intention is that you can transcode multiple images or mipmaps from the same .basis file on multiple threads.

Does this make sense?

-Rich

from basis_universal.

Thanks Rich, this is exactly what I wanted to know!

from basis_universal.

Thanks, I'll update this issue once it's possible to transcode multiple slices of a single .basis file from multiple threads.

from basis_universal.

I'm adding an optional pointer to a transcoding state struct to all the transcoding API's. For video, this state struct needs to stay persistent as it holds the last frame's indices. I'll have this checked in hopefully tomorrow or Sat.

from basis_universal.

I have checked in an optional state struct that you can use during transcoding for threading purposes.

from basis_universal.

Great stuff, thanks!

from basis_universal.