This may not be a node-icy bug, but I am using metadata to decide when I'd like to save the current stream to a file and when I'd like to ignore it. Playing back a recorded file, at the start of a section that was recorded immediately after a period of ignoring the stream, there's often a few seconds of content that replay at what seem to be at least 5x normal speed. Given that what's getting written is supposed to just be the straight passed-through data from the stream, it's especially strange that the content speeds up briefly. I would think that to cause a speed-up, the bitrate index for that section would need to change, but I have no idea what's temporarily causing that. Note that I'm not using the write function of node-icy (since there's not much documentation about it), but rather just using fs.createWriteStream to open a file once, and thereafter write all emits of data to it when the last metadata emit meets my desired conditions (otherwise that data is simply ignored). Any ideas?
This may not be a node-icy bug, but I am using metadata to decide when I'd like to save the current stream to a file and when I'd like to ignore it. Playing back a recorded file, at the start of a section that was recorded immediately after a period of ignoring the stream, there's often a few seconds of content that replay at what seem to be at least 5x normal speed. Given that what's getting written is supposed to just be the straight passed-through data from the stream, it's especially strange that the content speeds up briefly. I would think that to cause a speed-up, the bitrate index for that section would need to change, but I have no idea what's temporarily causing that. Note that I'm not using the write function of node-icy (since there's not much documentation about it), but rather just using fs.createWriteStream to open a file once, and thereafter write all emits of data to it when the last metadata emit meets my desired conditions (otherwise that data is simply ignored). Any ideas?