Binary sent is not the same as binary received #1692
Answered
by
ysfscream
soren-olesen
asked this question in
Q&A
-
I subscribe with: I publish with: The result is that the output.dat is not the same file as the input.aac file. The first number of bytes look ok (they are "text"), but everything else is wrong. What am I doing wrong ? |
Beta Was this translation helpful? Give feedback.
Answered by
ysfscream
Jun 14, 2024
Replies: 1 comment 1 reply
-
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
soren-olesen
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @soren-olesen
I appreciate your patience. The issue lies with the
file-read
andformat
options when publishing the message. The data read from the file is already in binary format, and the conversion process was doing unnecessary transformations, which caused the discrepancy.To resolve this, omit the
--format
option when using thepub
command. This will prevent the unnecessary conversion and maintain the integrity of the data. I have tested this, and the input and output files are now completely identical.Thank you for bringing this to our attention. We will fix it soon. 🙏
Best regards,
Shifan