In case you cannot see anything related to HDMI or your desired audio device in pavucontrol just restart pulseaudio with pulseaudio -k ( -k kills the previous instance before restarting) and do the above steps again. The default might also work after the pulseaudio configuration you just made. In SDRangel's Preferences/Audio menu make sure something like alsa_output.pci-0000_00_1b.0.hdmi-stereo is selected.Then in the 'Output devices' tab the HDMI / display port is selected as it is normally the only one.Select HDMI from the profiles list in the 'Configuration' tab.Open pavucontrol and open the last tab (rightmost) called 'Configuration'.So in any case make sure nothing is muted there. On the Udoo x86 the HDMI output depends on the S/PDIF control and it occasionally gets muted when the HDMI monitor is turned off or goes to sleep. Check the audio config with alsamixer.Ubuntu/Debian: sudo apt-get install pavucontrol.It is included in most distributions for example: So using this example of HDMI output you can do the following: These notes are a follow-up of issue #31 with my own experiments with HDMI audio output on the Udoo x86 board. The audio devices with Qt are supported through pulseaudio and unless you are using a single sound chip (or card) with a single output port or you are an expert with pulseaudio config files you may get into trouble when trying to route the audio to a different output port. The sdrangelsrv headless variant can be used for this purpose using the Remote source or sink channels. Since version 4.1 the previously separated project SDRdaemon has been modified and included in SDRangel. More information is provided in the Readme file of the sdrsrv folder. Since version 4 the sdrangelsrv binary launches a server mode SDRangel instance that runs wihout the GUI. More details are provided in the server instance documentation in the sdrsrv folder. Since version 4 a REST API is available to interact with the SDRangel application. Since version 3 transmission or signal generation is supported for BladeRF, HackRF (since version 3.1), LimeSDR (since version 3.4) and PlutoSDR (since version 3.7.8) using a sample sink plugin. Since version 2 SDRangel can integrate more than one hardware device running concurrently. Specific features Multiple device support legacy: the modified code from the parent application hexameron rtl-sdrangelove before a major redesign of the code was carried out and sync was lost.It can run on smaller devices check the Wiki for hardware requirements and a list of successful cases. The server variant does not need a graphical display and therefore OpenGL support. It may run on beefy SBCs and was tested successfully on a Udoo Ultra. USB-3 ports are also preferable for high speed, low latency USB communication. On the other hand SDRangel is not as demanding as recent computer games for graphics and CPU integrated graphics are perfectly fine. Modern Intel processors will include a GPU suitable for proper OpenGL support. Recent (2015 or later) Core i7 class CPU is recommended preferably with 4 HT CPU cores (8 logical CPUs or more) with nominal clock over 2 GHz and at least 8 GB RAM. SDRangel is a near real time application that is demanding on CPU power and clock speeds for low latency. You can also find more information in the Wiki. SDRangel might be a bit overwhelming for you however you are encouraged to use the discussion group above to look for help. We expect you to already have some experience with SDR applications and digital signal processing in general. ⚠ SDRangel is intended for the power user. SDRangel is an Open Source Qt5 / OpenGL 3.0+ SDR and signal analyzer frontend to various hardware.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |