Playback errors and stalling

[OzFalcon]

At sporadic times during game play, video/audio playback stalls with log warnings or errors.
After around 10 seconds or so Video/Audio playback resumes.

Example 1 (Video/Audio stall)

2018/03/23;16:02:38.762;INFO;800;0;ldp_vldp::nonblocking_search@471;"NOTE: converting FPKS from 23976 to 29970. This may be less accurate."
2018/03/23;16:02:53.804;WARN;800;0;ldp_vldp::play@564;"play command failed!"
2018/03/23;16:02:57.205;WARN;800;0;ldp_vldp::nonblocking_search@446;"LDP-VLDP: Could not open video file spa01d1.vob.m2v"
2018/03/23;16:02:57.205;WARN;800;0;ldv1000::write@317;"Search command was not accepted!"
2018/03/23;16:02:57.378;INFO;800;0;ldp_vldp::nonblocking_search@471;"NOTE: converting FPKS from 23976 to 29970. This may be less accurate."

Example 2 (Video/Audio stall)

2018/03/23;17:34:14.236;INFO;1108;0;ldp_vldp::nonblocking_search@471;"NOTE: converting FPKS from 23976 to 29970. This may be less accurate."
2018/03/23;17:34:16.349;ERROR;1114;0;ldp_vldp_audio_callback@592;"End of audio stream detected!"
2018/03/23;17:34:29.264;WARN;1108;0;ldp_vldp::play@564;"play command failed!"
2018/03/23;17:34:30.870;WARN;1108;0;ldp_vldp::nonblocking_search@446;"LDP-VLDP: Could not open video file spa05.vob.m2v"
2018/03/23;17:34:30.870;WARN;1108;0;ldv1000::write@317;"Search command was not accepted!"
2018/03/23;17:34:31.043;INFO;1108;0;ldp_vldp::nonblocking_search@471;"NOTE: converting FPKS from 23976 to 29970. This may be less accurate."

Example 3 (Only error message)

2018/03/23;16:01:06.205;INFO;800;0;ldp_vldp::nonblocking_search@471;"NOTE: converting FPKS from >23976 to 29970. This may be less accurate."
2018/03/23;16:01:08.162;ERROR;806;0;ldp_vldp_audio_callback@592;"End of audio stream detected!"
2018/03/23;16:01:09.173;INFO;800;0;ldp_vldp::nonblocking_search@471;"NOTE: converting FPKS from 23976 to 29970. This may be less accurate."

Using latest master/commit
https://github.com/btolab/hypseus/tree/c6af13b1274bbeb3e0406c84db6b9a5b3ce0bc72

[ghost]

this is normal daphne does this too its not something new that came in as a bug