home.social

#gnuradio — Public Fediverse posts

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

fetched live
  1. I just realized: The discuss-gnuradio mailing list has been going on for 25 years!

    lists.gnu.org/archive/html/dis starts¹ at 2001-07!

    Got any favourite #GNURadio #MailingList moment? There's been sooo many cool projects that came across the list that it's hard to pick one!

    ¹ it doesn't even seem to be the beginning of *any* GR mailing list activity, just the preserved history of the current list.

  2. I just realized: The discuss-gnuradio mailing list has been going on for 25 years!

    lists.gnu.org/archive/html/dis starts¹ at 2001-07!

    Got any favourite moment? There's been sooo many cool projects that came across the list that it's hard to pick one!

    ¹ it doesn't even seem to be the beginning of *any* GR mailing list activity, just the preserved history of the current list.

  3. I just realized: The discuss-gnuradio mailing list has been going on for 25 years!

    lists.gnu.org/archive/html/dis starts¹ at 2001-07!

    Got any favourite #GNURadio #MailingList moment? There's been sooo many cool projects that came across the list that it's hard to pick one!

    ¹ it doesn't even seem to be the beginning of *any* GR mailing list activity, just the preserved history of the current list.

  4. I just realized: The discuss-gnuradio mailing list has been going on for 25 years!

    lists.gnu.org/archive/html/dis starts¹ at 2001-07!

    Got any favourite #GNURadio #MailingList moment? There's been sooo many cool projects that came across the list that it's hard to pick one!

    ¹ it doesn't even seem to be the beginning of *any* GR mailing list activity, just the preserved history of the current list.

  5. I just realized: The discuss-gnuradio mailing list has been going on for 25 years!

    lists.gnu.org/archive/html/dis starts¹ at 2001-07!

    Got any favourite #GNURadio #MailingList moment? There's been sooo many cool projects that came across the list that it's hard to pick one!

    ¹ it doesn't even seem to be the beginning of *any* GR mailing list activity, just the preserved history of the current list.

  6. Stupid or genius: Because radio frequencies are heavily regulated, why not use sound waves above human hearing range for wireless communications? Consumer sound interfaces go up to 192 kilohertz, providing 20-96 kHz inaudible transmission band. Software like #GGwave exists.
    Transmitting high-power radio waves is usually illegal. But what about ultrasound?. Could we run a mesh network like #reticulum over audio?
    #minimodem #gnuradio #wavest #networking #offgrid #audio #ultrasound

  7. Stupid or genius: Because radio frequencies are heavily regulated, why not use sound waves above human hearing range for wireless communications? Consumer sound interfaces go up to 192 kilohertz, providing 20-96 kHz inaudible transmission band. Software like #GGwave exists.
    Transmitting high-power radio waves is usually illegal. But what about ultrasound?. Could we run a mesh network like #reticulum over audio?
    #minimodem #gnuradio #wavest #networking #offgrid #audio #ultrasound

  8. Stupid or genius: Because radio frequencies are heavily regulated, why not use sound waves above human hearing range for wireless communications? Consumer sound interfaces go up to 192 kilohertz, providing 20-96 kHz inaudible transmission band. Software like #GGwave exists.
    Transmitting high-power radio waves is usually illegal. But what about ultrasound?. Could we run a mesh network like #reticulum over audio?
    #minimodem #gnuradio #wavest #networking #offgrid #audio #ultrasound

  9. Stupid or genius: Because radio frequencies are heavily regulated, why not use sound waves above human hearing range for wireless communications? Consumer sound interfaces go up to 192 kilohertz, providing 20-96 kHz inaudible transmission band. Software like #GGwave exists.
    Transmitting high-power radio waves is usually illegal. But what about ultrasound?. Could we run a mesh network like #reticulum over audio?
    #minimodem #gnuradio #wavest #networking #offgrid #audio #ultrasound

  10. Stupid or genius: Because radio frequencies are heavily regulated, why not use sound waves above human hearing range for wireless communications? Consumer sound interfaces go up to 192 kilohertz, providing 20-96 kHz inaudible transmission band. Software like #GGwave exists.
    Transmitting high-power radio waves is usually illegal. But what about ultrasound?. Could we run a mesh network like #reticulum over audio?
    #minimodem #gnuradio #wavest #networking #offgrid #audio #ultrasound

  11. RE: fosstodon.org/@gnuradio/117147

    I just got to merge the qt5to6 branch, after a manual re-review. Nice!
    This means a couple of things:
    1. #GNURadio is now possible to support for multiple Linux distros that reached out to us to tell us they're about to drop Qt5
    2. We got rid of a lot of cruft – programs that haven't been functional in years (and that nobody knew existed), code duplication caused by API changes among different versions of Qt5 (yes.)
    3. This necessitates some changes on the interfaces we offer, where we expose Qt

  12. RE: fosstodon.org/@gnuradio/117147

    I just got to merge the qt5to6 branch, after a manual re-review. Nice!
    This means a couple of things:
    1. #GNURadio is now possible to support for multiple Linux distros that reached out to us to tell us they're about to drop Qt5
    2. We got rid of a lot of cruft – programs that haven't been functional in years (and that nobody knew existed), code duplication caused by API changes among different versions of Qt5 (yes.)
    3. This necessitates some changes on the interfaces we offer, where we expose Qt

  13. RE: fosstodon.org/@gnuradio/117147

    I just got to merge the qt5to6 branch, after a manual re-review. Nice!
    This means a couple of things:
    1. #GNURadio is now possible to support for multiple Linux distros that reached out to us to tell us they're about to drop Qt5
    2. We got rid of a lot of cruft – programs that haven't been functional in years (and that nobody knew existed), code duplication caused by API changes among different versions of Qt5 (yes.)
    3. This necessitates some changes on the interfaces we offer, where we expose Qt

  14. RE: fosstodon.org/@gnuradio/117147

    I just got to merge the qt5to6 branch, after a manual re-review. Nice!
    This means a couple of things:
    1. #GNURadio is now possible to support for multiple Linux distros that reached out to us to tell us they're about to drop Qt5
    2. We got rid of a lot of cruft – programs that haven't been functional in years (and that nobody knew existed), code duplication caused by API changes among different versions of Qt5 (yes.)
    3. This necessitates some changes on the interfaces we offer, where we expose Qt

  15. RE: fosstodon.org/@gnuradio/117147

    I just got to merge the qt5to6 branch, after a manual re-review. Nice!
    This means a couple of things:
    1. #GNURadio is now possible to support for multiple Linux distros that reached out to us to tell us they're about to drop Qt5
    2. We got rid of a lot of cruft – programs that haven't been functional in years (and that nobody knew existed), code duplication caused by API changes among different versions of Qt5 (yes.)
    3. This necessitates some changes on the interfaces we offer, where we expose Qt

  16. There seems no #gnuradio block to encode or decode #Q65 😮

  17. There seems no #gnuradio block to encode or decode #Q65 😮

  18. There seems no #gnuradio block to encode or decode #Q65 😮

  19. There seems no #gnuradio block to encode or decode #Q65 😮

  20. There seems no #gnuradio block to encode or decode #Q65 😮

  21. downloaded #matrix to check out the #gnuradio channel or whatever.

    the first chatroom thing i click into is someone suspicious the other person is using an llm to come up with things to say.

    the second is someone saying claude told them to download some documents and that most of the system they're asking for help with was written by an llm.

    yeah no thanks. embarrassing clown shit.

    ugh, i feel gross even seeing that momentarily. i need to go read a textbook to recover

  22. downloaded #matrix to check out the #gnuradio channel or whatever.

    the first chatroom thing i click into is someone suspicious the other person is using an llm to come up with things to say.

    the second is someone saying claude told them to download some documents and that most of the system they're asking for help with was written by an llm.

    yeah no thanks. embarrassing clown shit.

    ugh, i feel gross even seeing that momentarily. i need to go read a textbook to recover

  23. downloaded #matrix to check out the #gnuradio channel or whatever.

    the first chatroom thing i click into is someone suspicious the other person is using an llm to come up with things to say.

    the second is someone saying claude told them to download some documents and that most of the system they're asking for help with was written by an llm.

    yeah no thanks. embarrassing clown shit.

    ugh, i feel gross even seeing that momentarily. i need to go read a textbook to recover

  24. is there already some statistical pattern recognizer (aka AI before the times of LLMs) that automatically guesses modulation of radio signals? working with #rtlsdr or with #gnuradio?

    update: and automatically decodes the signal into files?

    #sdr #radio

  25. is there already some statistical pattern recognizer (aka AI before the times of LLMs) that automatically guesses modulation of radio signals? working with #rtlsdr or with #gnuradio?

    update: and automatically decodes the signal into files?

    #sdr #radio

  26. is there already some statistical pattern recognizer (aka AI before the times of LLMs) that automatically guesses modulation of radio signals? working with #rtlsdr or with #gnuradio?

    update: and automatically decodes the signal into files?

    #sdr #radio

  27. is there already some statistical pattern recognizer (aka AI before the times of LLMs) that automatically guesses modulation of radio signals? working with #rtlsdr or with #gnuradio?

    update: and automatically decodes the signal into files?

    #sdr #radio

  28. is there already some statistical pattern recognizer (aka AI before the times of LLMs) that automatically guesses modulation of radio signals? working with #rtlsdr or with #gnuradio?

    update: and automatically decodes the signal into files?

    #sdr #radio

  29. While researching ways to watermark my audio, I went from #minimodem to #GNUradio to #Meshtastic and #Reticulum. Rabbit holes! Hopefully something worthy will emerge eventually.

  30. While researching ways to watermark my audio, I went from #minimodem to #GNUradio to #Meshtastic and #Reticulum. Rabbit holes! Hopefully something worthy will emerge eventually.

  31. While researching ways to watermark my audio, I went from #minimodem to #GNUradio to #Meshtastic and #Reticulum. Rabbit holes! Hopefully something worthy will emerge eventually.

  32. While researching ways to watermark my audio, I went from #minimodem to #GNUradio to #Meshtastic and #Reticulum. Rabbit holes! Hopefully something worthy will emerge eventually.

  33. While researching ways to watermark my audio, I went from #minimodem to #GNUradio to #Meshtastic and #Reticulum. Rabbit holes! Hopefully something worthy will emerge eventually.

  34. Any #GNUradio enthusiasts around here? #HamRadio people? I'm looking into ways to #watermark my sounds and then decode the watermarks to prove ownership in case of sound effect or #music theft. The watermark should be inaudible and hopefully work even if it's barely above the noise floor, survive typical audio compression etc. I looked into #LoRa and thought maybe chirps are the way to go here. My first thought was #minimodem, but it could be too fragile to decode, and probably would be audible.

  35. Any #GNUradio enthusiasts around here? #HamRadio people? I'm looking into ways to #watermark my sounds and then decode the watermarks to prove ownership in case of sound effect or #music theft. The watermark should be inaudible and hopefully work even if it's barely above the noise floor, survive typical audio compression etc. I looked into #LoRa and thought maybe chirps are the way to go here. My first thought was #minimodem, but it could be too fragile to decode, and probably would be audible.

  36. Any #GNUradio enthusiasts around here? #HamRadio people? I'm looking into ways to #watermark my sounds and then decode the watermarks to prove ownership in case of sound effect or #music theft. The watermark should be inaudible and hopefully work even if it's barely above the noise floor, survive typical audio compression etc. I looked into #LoRa and thought maybe chirps are the way to go here. My first thought was #minimodem, but it could be too fragile to decode, and probably would be audible.

  37. Any #GNUradio enthusiasts around here? #HamRadio people? I'm looking into ways to #watermark my sounds and then decode the watermarks to prove ownership in case of sound effect or #music theft. The watermark should be inaudible and hopefully work even if it's barely above the noise floor, survive typical audio compression etc. I looked into #LoRa and thought maybe chirps are the way to go here. My first thought was #minimodem, but it could be too fragile to decode, and probably would be audible.

  38. Any #GNUradio enthusiasts around here? #HamRadio people? I'm looking into ways to #watermark my sounds and then decode the watermarks to prove ownership in case of sound effect or #music theft. The watermark should be inaudible and hopefully work even if it's barely above the noise floor, survive typical audio compression etc. I looked into #LoRa and thought maybe chirps are the way to go here. My first thought was #minimodem, but it could be too fragile to decode, and probably would be audible.

  39. For chat: hit us up on #gnuradio:gnuradio.org on matrix (if you don't have a matrix account, you can get one for free via signup on app.element.io/#/room/#gnuradi ).

  40. For chat: hit us up on :gnuradio.org on matrix (if you don't have a matrix account, you can get one for free via signup on app.element.io/#/room/#gnuradi ).

  41. For chat: hit us up on #gnuradio:gnuradio.org on matrix (if you don't have a matrix account, you can get one for free via signup on app.element.io/#/room/#gnuradi ).

  42. For chat: hit us up on #gnuradio:gnuradio.org on matrix (if you don't have a matrix account, you can get one for free via signup on app.element.io/#/room/#gnuradi ).

  43. For chat: hit us up on #gnuradio:gnuradio.org on matrix (if you don't have a matrix account, you can get one for free via signup on app.element.io/#/room/#gnuradi ).

  44. The whole of digitial signal processing is a dataflow problem.

    All these frameworks, libraries and tools turning these things into steps and chugging the data along varies threads, take note this is the wrong approach. These copies are to expensive!

    This is what fundamentally undermines the performance of something like #gnuradio.

    To achieve peak performance, we need to turn these problems into a graph, then analyze and plan said graph and run the thing as a whole.

    #dsp #hpc #dag #graph

  45. The whole of digitial signal processing is a dataflow problem.

    All these frameworks, libraries and tools turning these things into steps and chugging the data along varies threads, take note this is the wrong approach. These copies are to expensive!

    This is what fundamentally undermines the performance of something like .

    To achieve peak performance, we need to turn these problems into a graph, then analyze and plan said graph and run the thing as a whole.

  46. The whole of digitial signal processing is a dataflow problem.

    All these frameworks, libraries and tools turning these things into steps and chugging the data along varies threads, take note this is the wrong approach. These copies are to expensive!

    This is what fundamentally undermines the performance of something like #gnuradio.

    To achieve peak performance, we need to turn these problems into a graph, then analyze and plan said graph and run the thing as a whole.

    #dsp #hpc #dag #graph

  47. The whole of digitial signal processing is a dataflow problem.

    All these frameworks, libraries and tools turning these things into steps and chugging the data along varies threads, take note this is the wrong approach. These copies are to expensive!

    This is what fundamentally undermines the performance of something like #gnuradio.

    To achieve peak performance, we need to turn these problems into a graph, then analyze and plan said graph and run the thing as a whole.

    #dsp #hpc #dag #graph

  48. The performance of native Python #gnuradio blocks can be significantly improved by adjusting `set_output_multiple` to a sufficiently high number.

    Naturally, there is a relation between group delay and this multiple.

    #sdr #JAX

  49. The performance of native Python blocks can be significantly improved by adjusting `set_output_multiple` to a sufficiently high number.

    Naturally, there is a relation between group delay and this multiple.

  50. The performance of native Python #gnuradio blocks can be significantly improved by adjusting `set_output_multiple` to a sufficiently high number.

    Naturally, there is a relation between group delay and this multiple.

    #sdr #JAX

  51. The performance of native Python #gnuradio blocks can be significantly improved by adjusting `set_output_multiple` to a sufficiently high number.

    Naturally, there is a relation between group delay and this multiple.

    #sdr #JAX

  52. Finally making my own Out-Of-Tree #gnuradio modules, its been fun learning to use gr_modtool.

    Wish there where some ways to reduce the overhead of Python blocks. I drop from 900 megasamples/s to 128 as soon as a single Python block is in the chain.

  53. Finally making my own Out-Of-Tree modules, its been fun learning to use gr_modtool.

    Wish there where some ways to reduce the overhead of Python blocks. I drop from 900 megasamples/s to 128 as soon as a single Python block is in the chain.

  54. Finally making my own Out-Of-Tree #gnuradio modules, its been fun learning to use gr_modtool.

    Wish there where some ways to reduce the overhead of Python blocks. I drop from 900 megasamples/s to 128 as soon as a single Python block is in the chain.

  55. Finally making my own Out-Of-Tree #gnuradio modules, its been fun learning to use gr_modtool.

    Wish there where some ways to reduce the overhead of Python blocks. I drop from 900 megasamples/s to 128 as soon as a single Python block is in the chain.