An Idea for rx_c_file

Hi, this is just an idea for an improvement to rx_c_file. When it
outputs a file, there is no information about frequency, decimation,
sample type etc… If you forget how you sampled it the information is
useless. What if the rx_c_file program could output a file with this
info automatically? Or could it be included in a header? This could also
be read by the corresponding tx program.

I’m no programmer (ie. I don’t know how to implement this), and this
could be a stupid idea, what do you think?

Matt

On Sun, Mar 28, 2010 at 12:07 AM, Matthew Curlis
[email protected]wrote:

Matt

This could be done easily, but just as a suggestion, I’ve gotten into
the
habit of naming my files with all of the relevant information in them.

Tom

On Sat, Mar 27, 2010 at 09:07:42PM -0700, Matthew Curlis wrote:

Hi, this is just an idea for an improvement to rx_c_file. When it outputs a
file, there is no information about frequency, decimation, sample type etc…
If you forget how you sampled it the information is useless. What if the
rx_c_file program could output a file with this info automatically? Or could it
be included in a header? This could also be read by the corresponding tx
program.

Another suggestion: Modify the file to use the WAV sinks. That way, at
least the sampling rate gets saved into the file, and you can implicitly
save the sample type (I assume you mean real vs. complex?) by using mono
or stereo files.

MB


Karlsruhe Institute of Technology (KIT)
Communications Engineering Lab (CEL)

Dipl.-Ing. Martin B.
Research Associate

Kaiserstraße 12
Building 05.01
76131 Karlsruhe

Phone: +49 721 608-3790
Fax: +49 721 608-6071
www.cel.kit.edu

KIT – University of the State of Baden-Württemberg and
National Laboratory of the Helmholtz Association

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs