Commit e08d04b2 authored by RIOU Cedric's avatar RIOU Cedric

Fix timestamp chunks warning in Display cue image

parent b42d882a
......@@ -60,7 +60,7 @@ namespace OpenViBEPlugins
m_int32DrawnImageID(-1),
m_bFullScreen(false),
m_bScaleImages(false),
m_ui64LastOutputChunkDate(-1),
m_ui64LastOutputChunkDate(0),
m_pStimulusSender(nullptr),
m_visualizationContext(nullptr)
{
......@@ -402,9 +402,9 @@ namespace OpenViBEPlugins
m_oStimulationDecoder.decode(chunk,true);
if(m_oStimulationDecoder.isHeaderReceived())
{
m_ui64LastOutputChunkDate = this->getPlayerContext().getCurrentTime();
m_oStimulationEncoder.encodeHeader();
l_pBoxIO->markOutputAsReadyToSend(0, 0, m_ui64LastOutputChunkDate);
l_pBoxIO->markOutputAsReadyToSend(0, m_ui64LastOutputChunkDate,this->getPlayerContext().getCurrentTime());
m_ui64LastOutputChunkDate = this->getPlayerContext().getCurrentTime();
}
if(m_oStimulationDecoder.isBufferReceived())
{
......
  • Is there any reason the call were inverted ? The 2 calls can possibly return a different value, depending on the implementation.

  • Afaik its meant to return simulated time, this should stay still while in process(). Also note that this mod is a bit out of business as I changed the solution during merge.

    Edited by Jussi Lindgren
  • m_ui64LastOutputChunkDate should be set at the end. The previous call order caused the warnings. Anyway Jussi has removed this part of the code and has chosen another implementation.

Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment