Paul - you can send email to the list (cc'd) and this is a good way to start a discussion. Or you can use chat.gnuradio.org, or both. There are cases where changing rate could be useful, e.g., survey. There was a related discussion recently on automatically propagating rates through a flowgraph so blocks did not need to be manually configured for rate. That's harder than just recording metadata where the tag is already propagated. Any idea if SigMF can handle this (there is an OOT gr-sigmf).
You can also put this in as an issue at https://github.com/gnuradio/gnuradio/issues, where we handle bugs and feature requests. On Thu, May 20, 2021 at 7:00 AM Paul Otto <[email protected]> wrote: > Hi Jeff, Thanks for the quick response. Let me know if this isn't the way > to reply to the list serve. I looked at the section on replying in > https://wiki.gnuradio.org/index.php/ReportingErrors but it wasn't clear > to me how you email your reply so it is picked up as a reply and not a new > thread. > > What is the best approach to updating the the Wiki documentation for the > File Meta Sink block? Besides the main focus of describing the core usage > of the block I want to include a section on issues to be aware of. Assuming > my tests are valid I would consider having the file meta sink block write > the incorrect sample rate meta data into the file would be an issue to make > people aware of in the rare case they want to change the sample rate while > the flow graph is running. Since it doesn't sound like it is an error, > would I just update the documentation or should I open a GitHub issue to > verify the behavior is as intended? Thanks for your help, Paul >
