home.social

#futuresdr — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #futuresdr, aggregated by home.social.

  1. @destevez Thinking about some your proposal as I am currently implementing #SigMF support for #FutureSDR that will also be used for an #IQengine plugin... I have similar use-cases in mind for instance for SSTV decoding. Yet I do not think that embedding image in base64 directly into json would be a good idea. Or at least, I would prefer something like the img html5 tag supporting Data URLs: developer.mozilla.org/en-US/do

  2. @destevez Thinking about some your proposal as I am currently implementing #SigMF support for #FutureSDR that will also be used for an #IQengine plugin... I have similar use-cases in mind for instance for SSTV decoding. Yet I do not think that embedding image in base64 directly into json would be a good idea. Or at least, I would prefer something like the img html5 tag supporting Data URLs: developer.mozilla.org/en-US/do

  3. @destevez Thinking about some your proposal as I am currently implementing #SigMF support for #FutureSDR that will also be used for an #IQengine plugin... I have similar use-cases in mind for instance for SSTV decoding. Yet I do not think that embedding image in base64 directly into json would be a good idea. Or at least, I would prefer something like the img html5 tag supporting Data URLs: developer.mozilla.org/en-US/do

  4. @destevez Thinking about some your proposal as I am currently implementing #SigMF support for #FutureSDR that will also be used for an #IQengine plugin... I have similar use-cases in mind for instance for SSTV decoding. Yet I do not think that embedding image in base64 directly into json would be a good idea. Or at least, I would prefer something like the img html5 tag supporting Data URLs: developer.mozilla.org/en-US/do

  5. @destevez Thinking about some your proposal as I am currently implementing #SigMF support for #FutureSDR that will also be used for an #IQengine plugin... I have similar use-cases in mind for instance for SSTV decoding. Yet I do not think that embedding image in base64 directly into json would be a good idea. Or at least, I would prefer something like the img html5 tag supporting Data URLs: developer.mozilla.org/en-US/do

  6. I have started a #rust crate for #sigmf files. `sigmf-hash` command has been reimplemented. I will work soon on blocks for #FutureSDR input/output.
    github.com/loic-fejoz/fsdr-blo

  7. I have started a #rust crate for #sigmf files. `sigmf-hash` command has been reimplemented. I will work soon on blocks for #FutureSDR input/output.
    github.com/loic-fejoz/fsdr-blo

  8. Raining outside so working on an #IQEngine plugin in #rust and #FutureSDR
    Got first result and it seems promising.
    #sigmf #hamradio #hamr

  9. Raining outside so working on an #IQEngine plugin in #rust and #FutureSDR
    Got first result and it seems promising.
    #sigmf #hamradio #hamr

  10. @Ea5iyl @oh8hub Agreed, quite a some ham radio software is built and shared by individuals. And many of them are shared in a way that are not inviting to build a community. At least not a community of contributors.

    But there are also projects out there ticking all the boxes: version control, contribution guide, project documentation, and just general open source best practises. Projects like #M17project , #OpenRTX, #GNURadio, #FutureSDR to just name a few.

  11. @Ea5iyl @oh8hub Agreed, quite a some ham radio software is built and shared by individuals. And many of them are shared in a way that are not inviting to build a community. At least not a community of contributors.

    But there are also projects out there ticking all the boxes: version control, contribution guide, project documentation, and just general open source best practises. Projects like #M17project , #OpenRTX, #GNURadio, #FutureSDR to just name a few.

  12. @Ea5iyl @oh8hub Agreed, quite a some ham radio software is built and shared by individuals. And many of them are shared in a way that are not inviting to build a community. At least not a community of contributors.

    But there are also projects out there ticking all the boxes: version control, contribution guide, project documentation, and just general open source best practises. Projects like #M17project , #OpenRTX, #GNURadio, #FutureSDR to just name a few.

  13. @Ea5iyl @oh8hub Agreed, quite a some ham radio software is built and shared by individuals. And many of them are shared in a way that are not inviting to build a community. At least not a community of contributors.

    But there are also projects out there ticking all the boxes: version control, contribution guide, project documentation, and just general open source best practises. Projects like #M17project , #OpenRTX, #GNURadio, #FutureSDR to just name a few.

  14. @Ea5iyl @oh8hub Agreed, quite a some ham radio software is built and shared by individuals. And many of them are shared in a way that are not inviting to build a community. At least not a community of contributors.

    But there are also projects out there ticking all the boxes: version control, contribution guide, project documentation, and just general open source best practises. Projects like #M17project , #OpenRTX, #GNURadio, #FutureSDR to just name a few.

  15. @ekuber Working on #FutureSDR (a #sdr / #dsp crate), I also tried to be clever but the #rust #compiler always beat me. Even explicitly using `core::simd` slowed down the program because the compiler found better optimization.

    The trick is indeed to use iterators.

    Yet the conclusion varies from architecture to another has the optimising parts of the compiler are of different maturity...

  16. @ekuber Working on #FutureSDR (a #sdr / #dsp crate), I also tried to be clever but the #rust #compiler always beat me. Even explicitly using `core::simd` slowed down the program because the compiler found better optimization.

    The trick is indeed to use iterators.

    Yet the conclusion varies from architecture to another has the optimising parts of the compiler are of different maturity...

  17. @ekuber Working on #FutureSDR (a #sdr / #dsp crate), I also tried to be clever but the #rust #compiler always beat me. Even explicitly using `core::simd` slowed down the program because the compiler found better optimization.

    The trick is indeed to use iterators.

    Yet the conclusion varies from architecture to another has the optimising parts of the compiler are of different maturity...

  18. @ekuber Working on #FutureSDR (a #sdr / #dsp crate), I also tried to be clever but the #rust #compiler always beat me. Even explicitly using `core::simd` slowed down the program because the compiler found better optimization.

    The trick is indeed to use iterators.

    Yet the conclusion varies from architecture to another has the optimising parts of the compiler are of different maturity...

  19. @ekuber Working on #FutureSDR (a #sdr / #dsp crate), I also tried to be clever but the #rust #compiler always beat me. Even explicitly using `core::simd` slowed down the program because the compiler found better optimization.

    The trick is indeed to use iterators.

    Yet the conclusion varies from architecture to another has the optimising parts of the compiler are of different maturity...

  20. How many methods of generating an #SSB signal do exist in #SDR?

    So far I found three (ignore the double side band one).

    You can find them implemented in #Rust using #FutureSDR at git.sr.ht/~corvus/futuresdr_ss.

  21. How many methods of generating an #SSB signal do exist in #SDR?

    So far I found three (ignore the double side band one).

    You can find them implemented in #Rust using #FutureSDR at git.sr.ht/~corvus/futuresdr_ss.

  22. How many methods of generating an #SSB signal do exist in #SDR?

    So far I found three (ignore the double side band one).

    You can find them implemented in #Rust using #FutureSDR at git.sr.ht/~corvus/futuresdr_ss.

  23. How many methods of generating an #SSB signal do exist in #SDR?

    So far I found three (ignore the double side band one).

    You can find them implemented in #Rust using #FutureSDR at git.sr.ht/~corvus/futuresdr_ss.

  24. How many methods of generating an #SSB signal do exist in #SDR?

    So far I found three (ignore the double side band one).

    You can find them implemented in #Rust using #FutureSDR at git.sr.ht/~corvus/futuresdr_ss.

  25. Working on a command line to setup #FutureSDR flowgraph. Could also be a #csdr replacement. What are the commands you would like to see first? Come and tell me more at github.com/loic-fejoz/fsdr-cli or join the discord of futuresdr.org/

    An intermediate goal is to be usable within #openWebRX
    #dsp #hamradio #amsat

  26. Working on a command line to setup #FutureSDR flowgraph. Could also be a #csdr replacement. What are the commands you would like to see first? Come and tell me more at github.com/loic-fejoz/fsdr-cli or join the discord of futuresdr.org/

    An intermediate goal is to be usable within #openWebRX
    #dsp #hamradio #amsat

  27. This week-end?
    #FutureSDR fun by doing a replacement of the #csdr command-line called fsdr-cli, but ALSO able to interpret #GNURadio Companion file.
    ✅WFM decoding achieved
    github.com/loic-fejoz/fsdr-cli
    #hamradio #hamr #DSP