I thought I would mention here that I have been testing out the ORANGE PI PC and have been having success! This is not just a clone of the Raspberry Pi 2, it's actually BETTER on paper and has been seen for sale for as little as $15 + a small shipping cost. By better I mean that the clock frequency is 50% higher and the I/O can handle higher throughput (e.g. the ethernet gives real world speeds of over 100MB/s while the R-Pi-2 is <60MB/s). This should also translate into higher USB throughput.
Previously (1-2 months ago) I encountered problems with the OS distros that were available for the Orange Pi PC. Recently I downloaded a newly published OI-Pi PC image of Ubuntu 15.04 Mate. This seems to work well. The only problem that I found was that the monitor resolution was fixed at 1920x1080. This is likely because I am using a DVI-D monitor with an HDMI adapter, so there may not be EDID data coming from the monitor to tell the O-Pi what is on the other end of the cable. Luckily my monitor still puts out an image, but it is an odd pink color even though it is above the listed max resolution of 1440x900.
I did a couple of quick tests and all was well. I also tried out the venerable Behringer UCA202 and got immediate PnP response in ALSA. Playback was great over headphones. I may try this as analog input...
Anyway, thought I would let people know that this platform is likely good for LADSPA/ecasound/ALSA work if you want to pull the trigger on it.
Previously (1-2 months ago) I encountered problems with the OS distros that were available for the Orange Pi PC. Recently I downloaded a newly published OI-Pi PC image of Ubuntu 15.04 Mate. This seems to work well. The only problem that I found was that the monitor resolution was fixed at 1920x1080. This is likely because I am using a DVI-D monitor with an HDMI adapter, so there may not be EDID data coming from the monitor to tell the O-Pi what is on the other end of the cable. Luckily my monitor still puts out an image, but it is an odd pink color even though it is above the listed max resolution of 1440x900.
I did a couple of quick tests and all was well. I also tried out the venerable Behringer UCA202 and got immediate PnP response in ALSA. Playback was great over headphones. I may try this as analog input...
Anyway, thought I would let people know that this platform is likely good for LADSPA/ecasound/ALSA work if you want to pull the trigger on it.
I've got to get me one of those....
Here are some tips for anyone interested:
Orange Pi PC:
$19+shipping with power supply from Aliexpress:
Orange Pi PC set 4 : Orange Pi PC + Power Supply-in Demo Board from Computer & Office on Aliexpress.com | Alibaba Group
At this price it is a better alternative to the Pi Zero, which supposedly sells for $5 but all stock has been sold and vendors are currently awaiting product. But the Zero has only one microUSB OTG port, doesn't have a video output, and is a 1GHz single core system. This has 4 cores that can run at up to 1.5GHz, and the OS can actively throttle back the CPU frequency to save power and reduce heat generation.
BTW, this seller also offers other combinations w/o PS, with case, USB-->PS connector cable, etc.
The OS can be downloaded from the orangepi web site forum, here:
Linux Distributions for Orange PI H3 boards - Debian - OrangePi - Powered by Discuz!
I downloaded and used the file labeled:
OrangePI-PC_Ubuntu_Vivid_Mate.img prepared for OrangePI users, just copy to SDCard, no configuration needed !
Just like the Raspberry Pi 2, you need to get this onto a MicroSD card. See THIS for an overview. These are common for cameras and other devices that need internal storage and in my area I can buy these in my grocery store. I have also purchased several 16GB cards and a USB card reader/writer from Ebay seller 3c_expert. Has lots of reasonably priced cards, etc. Class 4,6, and 10 cards should all be fine. 16GB cards seem to strike a good balance between size and cost.
Then you need to connect the card, inserted in the USB reader/writer, to your computer and write the image to it. I use Win32diskimager:
Win32 Disk Imager download | SourceForge.net
Works like a charm. There are lots of other options for this kind of software. BE CAREFUL WHEN USING THIS SOFTWARE because it erases any existing files before writing the image - if you accidentally select your HDD as the write destination you have just wiped your disk.
After the image is written, just pop it in the OrangePi, connect USB mouse and keyboard, HDMI monitor, power supply, and fire it up. Keep the image around on your main computer in case you need to re-install it. Feel free to play around with the OS - if you totally trash it you can just reinstall again. This is at no extra cost. So, so nice.
Last edited:
I'm interested in that one as well. I read on the kodi forum that it has some early (?) issues with the vdu drivers.
I have an old TV as well in one room and also use a hdmi/dvi adapter. When using it with the pi, I need to make sure I turn on the PI first for the TV to set it to 1080, and if I have the TV on first before booting and cables connected, it defaults to a low SD resoluion (720 x480). Maybe you can trick it too??? If not, try to see if you can force it manually by the xrandr command:
https://wiki.ubuntu.com/X/Config/Resolution
I have an old TV as well in one room and also use a hdmi/dvi adapter. When using it with the pi, I need to make sure I turn on the PI first for the TV to set it to 1080, and if I have the TV on first before booting and cables connected, it defaults to a low SD resoluion (720 x480). Maybe you can trick it too??? If not, try to see if you can force it manually by the xrandr command:
https://wiki.ubuntu.com/X/Config/Resolution
I'm interested in that one as well. I read on the kodi forum that it has some early (?) issues with the vdu drivers.
I have an old TV as well in one room and also use a hdmi/dvi adapter. When using it with the pi, I need to make sure I turn on the PI first for the TV to set it to 1080, and if I have the TV on first before booting and cables connected, it defaults to a low SD resoluion (720 x480). Maybe you can trick it too??? If not, try to see if you can force it manually by the xrandr command:
https://wiki.ubuntu.com/X/Config/Resolution
I don't think your solution would work in my case. I have already tried a bunch of things using xrandr. I doscovered that the min and max resolutions (for the video "card" in the SoC of the OrangePi) is the same, e.g. both are set to 1920x1200 or whatever it was. Even if I created a new mode for my monitors native resolution (1440x900) it could not be activated even though it would show up in the monitors control panel on the desktop. I could not figure out how to change the min and max resolution, and the monitor would still display the image (albeit with an odd color tone) so I just gave up and moved on. I would typically use the Pi headless anyway, so this is no big deal breaker.
I do have an HDMI monitor on another computer that can handle 1920x1200 and I could drag it over and try it I suppose.
Too bad - worth a try but it sounds like you're out of luck. I gave up on an old computer for the exact same reason.
Anyways - keep us posted how it works out in headless audio mode.
Anyways - keep us posted how it works out in headless audio mode.
Another PI like option
Hi,
I purchased an Odroid C1+ after I had an EE friend of mine confirm that it does not have the same USB bottleneck experienced by the RPI2 - which I also have. I had previously succeeded in using the RPI2 for playback using Richard Taylor's setup but could not get it to do input and output because of the USB bottleneck.
Their website is www.hardkernel.com and the Odroid can be purchased from a vendor in California.
Has anyone else tried this little box?
I had been using a newer USB 7.1 soundcard that did not play well with Linux and have since bought an older version that I hope will work better.
I want to use the Odroid running ArchLinux as the DSP simultaneous input and output - I have successfully done this on an old PC of mine but using AVLinux. Then, I will tri amp it to a pair of open-baffle subs, and pair of open-baffle two-ways.
If I am successful I will post back.
James
Hi,
I purchased an Odroid C1+ after I had an EE friend of mine confirm that it does not have the same USB bottleneck experienced by the RPI2 - which I also have. I had previously succeeded in using the RPI2 for playback using Richard Taylor's setup but could not get it to do input and output because of the USB bottleneck.
Their website is www.hardkernel.com and the Odroid can be purchased from a vendor in California.
Has anyone else tried this little box?
I had been using a newer USB 7.1 soundcard that did not play well with Linux and have since bought an older version that I hope will work better.
I want to use the Odroid running ArchLinux as the DSP simultaneous input and output - I have successfully done this on an old PC of mine but using AVLinux. Then, I will tri amp it to a pair of open-baffle subs, and pair of open-baffle two-ways.
If I am successful I will post back.
James
Hi,
I purchased an Odroid C1+ after I had an EE friend of mine confirm that it does not have the same USB bottleneck experienced by the RPI2 - which I also have. I had previously succeeded in using the RPI2 for playback using Richard Taylor's setup but could not get it to do input and output because of the USB bottleneck.
Their website is www.hardkernel.com and the Odroid can be purchased from a vendor in California.
Has anyone else tried this little box?
I had been using a newer USB 7.1 soundcard that did not play well with Linux and have since bought an older version that I hope will work better.
I want to use the Odroid running ArchLinux as the DSP simultaneous input and output - I have successfully done this on an old PC of mine but using AVLinux. Then, I will tri amp it to a pair of open-baffle subs, and pair of open-baffle two-ways.
If I am successful I will post back.
James
Bandwidth will be proportional to the sample rate used. I am in no way dreaming of inputting, processing, and outputting 192kHz data, or even 96kHz. In my system I stream compressed MP3 (at 320k) over WiFi and then output 48kHz. The Pi 2 can handle the input and several output channels (e.g. at least 4) at this rate.
If you can live with 48kHz, you can try the Behringer UCA202. It has 2ch input and 2ch output (analog) plus a toslink (optical) digital out. Plug and play with the Pi.
PI2 vs. Odroid
Hi Charlie
Thanks for the reply. At my age, I no longer have golden ears so I have been happy with CD quality. The PI2 has been unable to process a line in to the soundcards multi outs. It can however process the audio if I have loaded the music on the SD card requiring the PI only to output.
The Odroid is supposed to have more USB bandwidth.
Thanks.
Hi Charlie
Thanks for the reply. At my age, I no longer have golden ears so I have been happy with CD quality. The PI2 has been unable to process a line in to the soundcards multi outs. It can however process the audio if I have loaded the music on the SD card requiring the PI only to output.
The Odroid is supposed to have more USB bandwidth.
Thanks.
Hi Charlie
Thanks for the reply. At my age, I no longer have golden ears so I have been happy with CD quality. The PI2 has been unable to process a line in to the soundcards multi outs. It can however process the audio if I have loaded the music on the SD card requiring the PI only to output.
The Odroid is supposed to have more USB bandwidth.
Thanks.
Was your 7.1 soundcard, or whatever you are/were using when trying audio input and audio output, rated for full duplex operation under Linux? I do not think that this is a Pi limitation per se, even with its "reduced" USB bandwidth that should be enough for this kind of thing...
USB card
Hi Charlie,
The USB card, a Sewell Sound Pro - https://sewelldirect.com/soundbox-pro-usb-sound-card - was fully recognized under Linux when I ran Aplay -l and aplay -l. However, the C-Media chip is not listed as fully supported on the ALSA webpage.
I could get it to playback only from music on the PI2 sd card and the Odroid C1+ sd card at 44.1kHz and 16 bit.
I would get an error something like the card is not recognized when I tried to input via line in.
I could see the card in alsamixer but when I tried to enable it I would get the above error.
Interestingly, the card is instantly recognized by Ubuntu and is pretty fully supported - even the hardware volume control on the card worked. I just am not a fan of the Ubuntu environment and struggle with pulseaudio.
Richard Taylor described the bandwidth issue for the PI2 as a problem. Thus, I do admit I did not explore any further.
I will keep trying as I really want a fanless source to listen to audio.
Thanks - James
Hi Charlie,
The USB card, a Sewell Sound Pro - https://sewelldirect.com/soundbox-pro-usb-sound-card - was fully recognized under Linux when I ran Aplay -l and aplay -l. However, the C-Media chip is not listed as fully supported on the ALSA webpage.
I could get it to playback only from music on the PI2 sd card and the Odroid C1+ sd card at 44.1kHz and 16 bit.
I would get an error something like the card is not recognized when I tried to input via line in.
I could see the card in alsamixer but when I tried to enable it I would get the above error.
Interestingly, the card is instantly recognized by Ubuntu and is pretty fully supported - even the hardware volume control on the card worked. I just am not a fan of the Ubuntu environment and struggle with pulseaudio.
Richard Taylor described the bandwidth issue for the PI2 as a problem. Thus, I do admit I did not explore any further.
I will keep trying as I really want a fanless source to listen to audio.
Thanks - James
This worked for me for a USB2 connected DAC on a raspian based system. Perhaps it will solve your problem too: (source: Moodeaudio.org)
Audio glitches with certain USB High Speed (UAC2) audio devices.
Cause: USB driver bug in Linux 3.18 and 4.1 kernels
Fix: Add dwc_otg.fiq_fsm_mask=0x3 to the beginning of line in /boot/cmdline.txt
Audio glitches with certain USB High Speed (UAC2) audio devices.
Cause: USB driver bug in Linux 3.18 and 4.1 kernels
Fix: Add dwc_otg.fiq_fsm_mask=0x3 to the beginning of line in /boot/cmdline.txt
Thanks
Hello again,
Thanks so much for the reply. These online communities can be so helpful.
I recall having to put in some text into a boot line but not the specific one above. I believe that the text helped me see alsamixer so it would not give a false response. (Obviously the details escape me.).
I will try that line above. The chip on the newer USB card is a C-Media CMI-6620 chip with standalone HD Audio Codec CM9882A.
It is actually made by AIMPRO21.com and repackaged by a couple of vendors I believe.
It does not appear that they are "officially" supported by ALSA at this point.
Hello again,
Thanks so much for the reply. These online communities can be so helpful.
I recall having to put in some text into a boot line but not the specific one above. I believe that the text helped me see alsamixer so it would not give a false response. (Obviously the details escape me.).
I will try that line above. The chip on the newer USB card is a C-Media CMI-6620 chip with standalone HD Audio Codec CM9882A.
It is actually made by AIMPRO21.com and repackaged by a couple of vendors I believe.
It does not appear that they are "officially" supported by ALSA at this point.
Update
Hi Odal,
I have been getting to the C1+ slowly. My main Linux PC audio server harddrive died a noisy death so I have spent time there getting it all set back up. I do not own an Orange Pi but do have a RPI2. I have only been able to grab minutes rather than hours. Frustrating.
I was able to get the Odroid to play back 5.1 so long as the music is on the SD card to a tri-amped setup. I am still working out the kinks on using it as IO though. I just bought an older USB card that I hope is fully supported by ALSA. How does one tell what the exact chip is on a board?
I am using ArchLinuxARM and am trying to figure out how to make the USB card the default. The usual cat proc/asound/modules gives me nothing. A simple file search though shows the information is hidden in the cards folder.
On my system the syntax is a little off so I just need to figure out the nomenclature and put it in the alsa-base.conf file and then set the USB as default. I am using the directions on Richard Taylor's site which works flawlessly on my PC.
Will work it this week as time allows. My hope is get this figured out so I can use the Odroid as a silent music system. I love the Linux PC I use but it has a fan that makes noise.
Hi Odal,
I have been getting to the C1+ slowly. My main Linux PC audio server harddrive died a noisy death so I have spent time there getting it all set back up. I do not own an Orange Pi but do have a RPI2. I have only been able to grab minutes rather than hours. Frustrating.
I was able to get the Odroid to play back 5.1 so long as the music is on the SD card to a tri-amped setup. I am still working out the kinks on using it as IO though. I just bought an older USB card that I hope is fully supported by ALSA. How does one tell what the exact chip is on a board?
I am using ArchLinuxARM and am trying to figure out how to make the USB card the default. The usual cat proc/asound/modules gives me nothing. A simple file search though shows the information is hidden in the cards folder.
On my system the syntax is a little off so I just need to figure out the nomenclature and put it in the alsa-base.conf file and then set the USB as default. I am using the directions on Richard Taylor's site which works flawlessly on my PC.
Will work it this week as time allows. My hope is get this figured out so I can use the Odroid as a silent music system. I love the Linux PC I use but it has a fan that makes noise.
Hi, can anybody explain why I can't test my USB Device, please?
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Device [USB Sound Device], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
michael@michael-HP-Pavilion-13-x360-PC:~$ speaker-test -D USB Audio -c 6 -t wav
speaker-test 1.0.29
Playback device is USB
Stream parameters are 48000Hz, S16_LE, 6 channels
WAV file(s)
ALSA lib pcm.c:2267🙁snd_pcm_open_noupdate) Unknown PCM USB
Playback open error: -2,No such file or directory
Thankyou
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Device [USB Sound Device], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
michael@michael-HP-Pavilion-13-x360-PC:~$ speaker-test -D USB Audio -c 6 -t wav
speaker-test 1.0.29
Playback device is USB
Stream parameters are 48000Hz, S16_LE, 6 channels
WAV file(s)
ALSA lib pcm.c:2267🙁snd_pcm_open_noupdate) Unknown PCM USB
Playback open error: -2,No such file or directory
Thankyou
Hi, can anybody explain why I can't test my USB Device, please?
speaker-test -D USB Audio -c 6 -t wav
speaker-test 1.0.29
Playback device is USB
Looks as if the space is confusing speaker-test. If so, try -D hw:2,0
ALSA lib pcm.c:2267🙁snd_pcm_open_noupdate) Unknown PCM USB
Playback open error: -2,No such file or directory
According to the aplay list, your three soundcards are called HDMI, PCH, and Device. I assume you wanted to use
Code:
speaker-test -D hw:Device ...
Last edited:
This worked for me for a USB2 connected DAC on a raspian based system. Perhaps it will solve your problem too: (source: Moodeaudio.org)
Audio glitches with certain USB High Speed (UAC2) audio devices.
Cause: USB driver bug in Linux 3.18 and 4.1 kernels
Fix: Add dwc_otg.fiq_fsm_mask=0x3 to the beginning of line in /boot/cmdline.txt
Hi: I am not sure how to do this? There is no such file in my boot folder on my Odroid system. It is running a Debian style system currently. I wonder if it is specific to the MoodeAudio app?
James
Jack
Hi, thanks for helping with my issue. My sound card I was using is a cheapy chinese thing and don't work properly.
My system is a Raspberry Pi model b with Openelec's Kodi installed. I have a Behringer DEQ2496 controlling my IB sub. I always felt the DEQ was wasted and installed it into the chain to EQ my main speakers with its AEQ room measurement system. I have replaced the DEQ sub duty with an Acer Revo, I installed Ubuntu 15:10 on it and installed Jack. I installed Jamin which provides lowpass crossover and a couple of useful bands of EQ.25hz and 31, the other 28 bands are too high to be usable.
I would rather have more bands to play with. I use my laptop and remote desktop to talk to the Revo.
Can I ask, has anybody got any thoughts or ideas on my system?
Thanks
Mike
Hi, thanks for helping with my issue. My sound card I was using is a cheapy chinese thing and don't work properly.
My system is a Raspberry Pi model b with Openelec's Kodi installed. I have a Behringer DEQ2496 controlling my IB sub. I always felt the DEQ was wasted and installed it into the chain to EQ my main speakers with its AEQ room measurement system. I have replaced the DEQ sub duty with an Acer Revo, I installed Ubuntu 15:10 on it and installed Jack. I installed Jamin which provides lowpass crossover and a couple of useful bands of EQ.25hz and 31, the other 28 bands are too high to be usable.
I would rather have more bands to play with. I use my laptop and remote desktop to talk to the Revo.
Can I ask, has anybody got any thoughts or ideas on my system?
Thanks
Mike
Attachments
- Home
- Source & Line
- PC Based
- LADSPA plugin programming for Linux audio crossovers