-
Notifications
You must be signed in to change notification settings - Fork 633
The actual playback time is much larger than the timestamp #1372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Could you replace this Line 154 in 3a7c80e
with this if sleep_period > 1e-3:
sleep(sleep_period) and check if it gets better? You have a very high message rate, i assume the |
try this branch please: https://github.com/zariiii9003/python-can/tree/message_sync |
I replace with _create_bus(results, **additional_config) as bus:
with Msg_List = list(BLFReader(results.infile))
It only takes 44 s to play a 120 s BLF file Then I will try your suggestion |
|
Thank you for your feedback, then i'll merge it into develop. |
Describe the bug
I have a 120 s long message ,then I find that It takes me 324.2 s to play. The Timestamp is still about 120 s, but the difference from the actual playback time is nearly 2.7 times . The file is https://github.com/hardbyte/python-can/blob/develop/can/player.py

To Reproduce
Expected behavior
The actual time spent is the same as the timestamp duration
Additional context
OS and version: Ubuntu 1804
Python version: 3.9.9
python-can version: 4.0.0
python-can interface/s (if applicable):
Traceback and logs
The text was updated successfully, but these errors were encountered: