I've not very familiar with SubVersion or this project.
So first off, which branch should I get (svn checkout) if I want look into the details?
Seems to be no master here. But this seems to have some recent pulls: https://svn.code.sf.net/p/drm/code/branches/dream-ollie-deployed/
Or what?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
IMO, the most complete/stable branch is dream-ollie. Not certain how different it is from dream-ollie-deployed. But it appears to have made some changes to the deployed version (particularly the MDI module) to allow for URLs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi. Yes, I added the ability to stream RSCI data via http, which is a more modern and secure way of doing it than the old plain TCP connection approach. I started that branch from an older version (1381) of dream-ollie, because the last few commits on the dream-ollie branch were more prone to freezing. I also did a partial fix for the case of controlling I/Q recording using RSCI commands.
Last edit: Oliver Haffenden 2023-06-20
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's likely that you won't need any of the RSCI-related features, but dream-ollie and dream-ollie-deployed are the only branches that have built-in support for SDR front-ends using the SoapySDR library, so that might be useful to you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Were some occasional crashes with xAAC fixed in your branch? In my
branch I get some.
Rafael
On 6/20/23 08:50, Oliver Haffenden wrote:
It's likely that you won't need any of the RSCI-related features, but
dream-ollie and dream-ollie-deployed are the only branches that have
built-in support for SDR front-ends using the SoapySDR library, so that
might be useful to you.
Hi. I haven't done any work on that, and I think I started from your branch, so it's probably the same. In our monitoring receivers, I have it running as a service, so it restarts if it crashes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's interesting that SoapySDR devices like my AirspyHF can be accessed as the signal input, but I see no way to actually tune the SDR from Dream. How can I use this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd be interested to know how you get on with the AirSpy. I know @fineware was trying it at the time of this thread and there's some discussion there. I only have SDRPlay devices so I can't test others, so any reports from users of other SDRs are very welcome.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello folks!
I've not very familiar with SubVersion or this project.
So first off, which branch should I get (svn checkout) if I want look into the details?
Seems to be no
masterhere. But this seems to have some recent pulls:https://svn.code.sf.net/p/drm/code/branches/dream-ollie-deployed/
Or what?
IMO, the most complete/stable branch is dream-ollie. Not certain how different it is from dream-ollie-deployed. But it appears to have made some changes to the deployed version (particularly the MDI module) to allow for URLs.
Hi. Yes, I added the ability to stream RSCI data via http, which is a more modern and secure way of doing it than the old plain TCP connection approach. I started that branch from an older version (1381) of dream-ollie, because the last few commits on the dream-ollie branch were more prone to freezing. I also did a partial fix for the case of controlling I/Q recording using RSCI commands.
Last edit: Oliver Haffenden 2023-06-20
It's likely that you won't need any of the RSCI-related features, but dream-ollie and dream-ollie-deployed are the only branches that have built-in support for SDR front-ends using the SoapySDR library, so that might be useful to you.
Hi Ollie,
Were some occasional crashes with xAAC fixed in your branch? In my
branch I get some.
Rafael
On 6/20/23 08:50, Oliver Haffenden wrote:
Hi. I haven't done any work on that, and I think I started from your branch, so it's probably the same. In our monitoring receivers, I have it running as a service, so it restarts if it crashes.
It's interesting that SoapySDR devices like my AirspyHF can be accessed as the signal input, but I see no way to actually tune the SDR from Dream. How can I use this?
You should be able to use the "Stations Dialog" either to select a scheduled transmission or to tune manually.
On a Mac, I use GQRX and my own Frequency Browser (uses Eibi data) to tune externally from Dream.
How do you get GQRX and Dream connected to the AirspyHF at the same time? Or, are you just piping the output from GRQX to Dream?
Last edit: jcoles 2023-06-21
I'm using Blackhole 2ch to pipe the audio from GQRX to Dream.
I'd be interested to know how you get on with the AirSpy. I know @fineware was trying it at the time of this thread and there's some discussion there. I only have SDRPlay devices so I can't test others, so any reports from users of other SDRs are very welcome.