2014-10-08, 16:42
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156
2014-10-08, 16:50
(2014-10-08, 16:42)pikoli Wrote: [ -> ]Hey, are this helix builds suitable for 256Mb pies?
Should be. I'd recommend you ensure gpu_mem=112 and cachemembuffersize is unset (so it uses a lower default on 256M Pi).
2014-10-08, 16:53
On a 256MB Pi, you might want to consider adding swap by running configrpi256.sh.
2014-10-08, 19:10
(2014-10-06, 21:04)BoBeRzE Wrote: [ -> ]Hi popcornmix,
i tested around with the new builds. The sound is fine without GPU acceleration except for 24Bit/192kHz files. The sound is not like white noise. I think the playback is to fast.
In the log file i see the following error:
Code:20:23:51 44307.937500 T:3033527376 ERROR: CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover
20:23:53 44309.691406 T:2699031632 ERROR: Previous line repeats 34 times.
Here is a debug log
Playback via HDMI to my TV is fine. Here is a log
But at the moment i am very happy to use my HifiBerry again
Thanks to all persons which helped me!!!
EDIT
If i set the output to 96khz the playback to slow. When i set the output to 44.1khz the playback is even slower
Hi,
with build #1007 the problem is gone . Now the HiFiBerry DAC is full usable
MANY thanks !!!
EDIT: resample via GPU is not working but this is no problem for me
2014-10-08, 22:25
Hi BoBeRzE,
what are your loaded modules in '/storage/.config/modules-load.d/hifiberry.conf'.
I hear only 'white noise' with build #1007.
Or still you have other special settings?
what are your loaded modules in '/storage/.config/modules-load.d/hifiberry.conf'.
I hear only 'white noise' with build #1007.
Or still you have other special settings?
2014-10-08, 22:50
Hi a4741488,
here is my hifiberry.conf
It could be that u use GPU accelerated resampling
System -> Settings -> Audio output -> Resample Quality and chose High or another value exept gpu accelerated.
popcornmix meant that the accelerated resample path is buggy at the moment
BoBeRzE
here is my hifiberry.conf
Code:
#snd_soc_bcm2708
snd_soc_bcm2708_i2s
bcm2708_dmaengine
snd_soc_pcm5102a
snd_soc_hifiberry_dac
It could be that u use GPU accelerated resampling
System -> Settings -> Audio output -> Resample Quality and chose High or another value exept gpu accelerated.
popcornmix meant that the accelerated resample path is buggy at the moment
BoBeRzE
2014-10-08, 23:08
(2014-10-08, 22:50)BoBeRzE Wrote: [ -> ]Hi a4741488,
here is my hifiberry.conf
Code:#snd_soc_bcm2708
snd_soc_bcm2708_i2s
bcm2708_dmaengine
snd_soc_pcm5102a
snd_soc_hifiberry_dac
It could be that u use GPU accelerated resampling
System -> Settings -> Audio output -> Resample Quality and chose High or another value exept gpu accelerated.
popcornmix meant that the accelerated resample path is buggy at the moment
BoBeRzE
Thanks a lot....'changing the resample quality'...thats was it.
2014-10-09, 02:44
New OpenELEC Helix build: #1008
(Supercedes previous build)
Based on tip of OpenELEC master (dc51895f, changelog) and tip of XBMC master (e0db1d8a, changelog) with the following modifications:
(Supercedes previous build)
Code:
# uname -a
Linux rpi512 3.17.0 #1 PREEMPT Thu Oct 9 01:17:22 BST 2014 armv6l GNU/Linux
# vcgencmd version
Oct 6 2014 22:06:47
Copyright (c) 2012 Broadcom
version a363c9d4a3ff3c2f367d45044015674a8639dbeb (clean) (release)
# lsb_release
OpenELEC (Milhouse) - Version: devel-20141009011610-r19342-gdc51895 [Build #1008]
Based on tip of OpenELEC master (dc51895f, changelog) and tip of XBMC master (e0db1d8a, changelog) with the following modifications:
- Includes newclock4 patches
- Excludes the OpenELEC fernetmenta patches due to conflicts with newclock4
- Excludes the OpenELEC linux-01-RPi_support patch in favour of sourcing these and possibly more recent patches directly from kernel branch rpi-3.17.y
- Excludes the OpenELEC xbmc-001-newclock4 patch in favour of sourcing these and possibly more recent patches directly from newclock4 branch
- Default setting for "Show RSS Feed" changed to disabled
- Disabled "Total Duration" in Confluence (see build #0221 for details)
- Adapted service.openelec.settings to take advantage of PR5217
- Includes latest libnfs master (ab1af695)
- Includes latest libcec master (81e38211)
- Includes latest xbmc-pvr-addons master (259d1506)
- Includes latest xbmc-addon-xvdr master (a3724213)
- Includes libcec double-key suppression
- Includes libcec CEC Standby Fix
- Increase scan interval of PeripBusCEC from 5000 to 60000, reducing CPU loading by about 2% (1GHz Pi) every 5 seconds (even when CEC is "disabled")
- Includes CONFIG_COREDUMP=y to allow creation of coredumps (see here)
- Includes PR:5312: dvdplayer: do a seek after having changed subtitle stream
- Includes PR:5324: Add setting to hide library clean progress bar.
- Includes PR:5454: json-rpc: add possibility to force using the default player through Player.Open
- Includes PR:5463: [python] add *all* module dependencies to path
- Updated to 3.17.0 kernel
- kernel 3.17.y:
- Add bcm2708_gpio driver
- ARM: bcm2708: Limit the boot time interrupt allocation
- ARM:bcm2708: Add Support for Wolfson Audio Card
- ASOC: RPI : Add support for Wolfson Audio Card
- config:RPI: Add config support for wolfson audio card
- ASoC:RPI: DMA channels 2 and 3 to be set in FAST mode
- ASOC: RPI: Avoid build issue with 3.17
- Add bcm2708_gpio driver
2014-10-09, 02:49
It's entirely possible the switch to 3.17.y may have broken existing functionality, particularly USB/GPIO audio, so please test and let me know.
It would also be great to hear from anyone using a Wolfson audio card, ie. whether it's working or not.
At a guess, the Wolfson may need the following /storage/.config/modules-load.d/wolfson.conf:
The Wolfson config may also require one or more of the following:
It would also be great to hear from anyone using a Wolfson audio card, ie. whether it's working or not.
At a guess, the Wolfson may need the following /storage/.config/modules-load.d/wolfson.conf:
Code:
snd-soc-wm5102
snd-soc-wm8804
The Wolfson config may also require one or more of the following:
Code:
snd-soc-arizona
gpio-arizona
extcon-arizona
arizona-i2c
arizona-spi
snd-soc-wm-adsp
2014-10-09, 14:09
(2014-10-09, 02:44)Milhouse Wrote: [ -> ]New OpenELEC Helix build: #1008
Is force_turbo=0 ignored in this build? Dynamic overclock seems not working fine.
My config.txt:
Code:
arm_freq=900
core_freq=450
over_voltage=4
hdmi_force_hotplug=1
program_serial_random=1
config_hdmi_boost=4
emmc_pll_core=1
hdmi_ignore_cec_init=1
hdmi_force_cec_address=65535
temp_limit=62
force_pwm_open=1
pause_burst_frames=1
avoid_fix_ts=1
2014-10-09, 14:59
(2014-10-09, 14:09)slack3r Wrote: [ -> ]Is force_turbo=0 ignored in this build? Dynamic overclock seems not working fine.
Yes, looks like it's not scaling the frequency - I probably set one of the kernel options incorrectly, though not sure which one. Popcornmix?
This is the dmesg for a system booted without force_turbo, arm=1000 and it runs continuously at 1000Mhz, even while idle.
Edit: Hmm... well, I stopped xbmc.bin and then the ARM and Core speeds briefly dropped from 1000/500 to 700/250, so it looks like frequency scaling is active, but maybe too sensitive? bcmstat output.
2014-10-09, 15:57
(2014-10-09, 02:49)Milhouse Wrote: [ -> ]It would also be great to hear from anyone using a Wolfson audio card, ie. whether it's working or not.I had a quick look at it, but didn't get very far.
A fresh installation without any additional config shows these modules loaded - question: where do they come from, some device tree config?
Code:
Module Size Used by
arizona_ldo1 2335 0
fixed 1425 0
arizona_spi 1109 0
snd_soc_wm8804 7092 0
snd_soc_bcm2708_i2s 5585 0
snd_soc_pcm512x_i2c 1481 0
snd_soc_pcm512x 6356 1 snd_soc_pcm512x_i2c
snd_soc_tas5713 4760 0
regmap_spi 1465 2 snd_soc_wm8804,arizona_spi
regmap_i2c 1974 3 snd_soc_wm8804,snd_soc_pcm512x_i2c,snd_soc_tas5713
regmap_mmio 2181 1 snd_soc_bcm2708_i2s
snd_soc_core 104264 4 snd_soc_pcm512x,snd_soc_wm8804,snd_soc_tas5713,snd_soc_bcm2708_i2s
snd_compress 7084 1 snd_soc_core
snd_pcm_dmaengine 2935 1 snd_soc_core
snd_pcm 63094 3 snd_soc_wm8804,snd_soc_core,snd_pcm_dmaengine
snd_timer 17712 1 snd_pcm
snd 41549 4 snd_soc_core,snd_timer,snd_pcm,snd_compress
lirc_rpi 6008 3
lirc_dev 7885 1 lirc_rpi
rc_core 16223 1 lirc_dev
bcm2708_rng 812 0
One thing to note is that it's a good idea to either blacklist lirc_rpi or set it's gpios to 14/15 - otherwise it'll conflict with the wolfson card.
After some tests with minor success I tried disabling a few modules which I though maybe could conflict with the wolfson drivers (not sure, though, will have to check later):
Code:
blacklist lirc_rpi
blacklist lirc_dev
blacklist snd_soc_pcm512x
blacklist snd_soc_pcm512x_i2c
blacklist snd_soc_tas5713
blacklist snd_soc_wm8804
And enabled these modules:
Code:
arizona_i2c
gpio-arizona
extcon-arizona
snd-soc-wm5102
snd-soc-pcm5102a
snd-soc-wm-adsp
snd-soc-rpi-wsp
This lead to the following lsmod:
Code:
Module Size Used by
arizona_ldo1 2335 0
fixed 1425 2147483647
arizona_spi 1109 0
regmap_spi 1465 1 arizona_spi
snd_soc_bcm2708_i2s 5585 0
regmap_mmio 2181 1 snd_soc_bcm2708_i2s
snd_soc_rpi_wsp 7123 0
snd_soc_pcm5102a 1050 0
snd_soc_wm5102 308081 0
snd_soc_wm_adsp 15949 1 snd_soc_wm5102
snd_soc_arizona 16599 2 snd_soc_wm5102,snd_soc_wm_adsp
extcon_arizona 11196 0
extcon_class 8790 1 extcon_arizona
snd_soc_core 104264 7 snd_soc_arizona,snd_soc_wm5102,snd_soc_wm_adsp,extcon_arizona,snd_soc_rpi_wsp,snd_soc_pcm5102a,snd_soc_bcm2708_i2s
snd_compress 7084 1 snd_soc_core
snd_pcm_dmaengine 2935 1 snd_soc_core
snd_pcm 63094 4 snd_soc_arizona,snd_soc_core,snd_soc_rpi_wsp,snd_pcm_dmaengine
snd_timer 17712 1 snd_pcm
snd 41549 4 snd_soc_core,snd_timer,snd_pcm,snd_compress
gpio_arizona 1495 0
arizona_i2c 1133 0
regmap_i2c 1974 1 arizona_i2c
bcm2708_rng 812 0
"Failed to allocate IRQs" certainly doesn't look OK - but at least the voltage warnings are only temporarily at the beginning. Edit: but the "fixed" (fixed voltage regulator) module usage count seems to be strange.
Edit #2: here's /proc/interrupts:
Code:
CPU0
3: 6778 ARMCTRL BCM2708 Timer Tick
16: 0 ARMCTRL bcm2708_fb dma
20: 918 ARMCTRL DMA IRQ
32: 25714 ARMCTRL dwc_otg, dwc_otg_pcd, dwc_otg_hcd:usb1
52: 0 ARMCTRL BCM2708 GPIO catchall handler
65: 12 ARMCTRL ARM Mailbox IRQ
66: 406 ARMCTRL VCHIQ doorbell
75: 1 ARMCTRL
77: 9 ARMCTRL DMA IRQ
79: 6 ARMCTRL bcm2708_i2c.0, bcm2708_i2c.1
80: 78 ARMCTRL bcm2708_spi.0
84: 3362 ARMCTRL mmc0
FIQ: usb_fiq
Err: 0
Another try, without blacklisting snd_soc_wm8804 gives this modules:
Code:
Module Size Used by
arizona_ldo1 2335 0
fixed 1425 2147483647
arizona_spi 1109 0
snd_soc_wm8804 7092 0
snd_soc_bcm2708_i2s 5585 0
regmap_spi 1465 2 snd_soc_wm8804,arizona_spi
regmap_mmio 2181 1 snd_soc_bcm2708_i2s
snd_soc_rpi_wsp 7123 0
snd_soc_pcm5102a 1050 0
snd_soc_wm5102 308081 0
snd_soc_wm_adsp 15949 1 snd_soc_wm5102
snd_soc_arizona 16599 2 snd_soc_wm5102,snd_soc_wm_adsp
extcon_arizona 11196 0
extcon_class 8790 1 extcon_arizona
snd_soc_core 104264 8 snd_soc_arizona,snd_soc_wm5102,snd_soc_wm8804,snd_soc_wm_adsp,extcon_arizona,snd_soc_rpi_wsp,snd_soc_pcm5102a,snd_soc_bcm2708_i2s
snd_compress 7084 1 snd_soc_core
snd_pcm_dmaengine 2935 1 snd_soc_core
snd_pcm 63094 5 snd_soc_arizona,snd_soc_wm8804,snd_soc_core,snd_soc_rpi_wsp,snd_pcm_dmaengine
snd_timer 17712 1 snd_pcm
snd 41549 4 snd_soc_core,snd_timer,snd_pcm,snd_compress
gpio_arizona 1495 0
arizona_i2c 1133 0
regmap_i2c 1974 2 snd_soc_wm8804,arizona_i2c
bcm2708_rng 812 0
Now I'm stuck. Any ideas what I might be missing?
so long,
Hias
2014-10-09, 17:42
Thanks for the feedback, HiassofT. I'll be keeping an eye on PR:705 where you've asked the Wolfson developer for details, and make any changes as necessary though hopefully it's now just a matter of getting the right modules loaded.
2014-10-09, 19:00
@popcornmix
Hi popcornmix,
As you can read above, Milhouse is not able to test and fixe the drops I have when playing HD audio files.
So, now you are my only hope.
Could you tell me if you can fixe and test, with my help of course, the issue in a reasonable delay? (2-3 months I'd say?)
If you can't I'll have to consider to buy another hardware player and maybe software as I can't listen these audio files.
Thank you in advance for your answer.
(2014-10-07, 11:21)Milhouse Wrote: [ -> ]Just so you know, my Pi is connected to a monitor using HDMI, which then has its stereo line-out connected to the stereo line-in on a Windows PC which is connected to 2.1 speakers. I tested one of your demo files and had no problem with playback.
As I'm unable to reproduce your testing environment let alone your problem, I can't really contribute more than this.
Reproducing your issue is crucial to understanding and finding a solution, but obviously reproducing is not easy otherwise I'm pretty sure it would have been solved already.
Hi popcornmix,
As you can read above, Milhouse is not able to test and fixe the drops I have when playing HD audio files.
So, now you are my only hope.
Could you tell me if you can fixe and test, with my help of course, the issue in a reasonable delay? (2-3 months I'd say?)
If you can't I'll have to consider to buy another hardware player and maybe software as I can't listen these audio files.
Thank you in advance for your answer.
2014-10-09, 19:08
(2014-10-09, 19:00)MrNice Wrote: [ -> ]As you can read above, Milhouse is not able to test and fixe the drops I have when playing HD audio files.
So, now you are my only hope.
Could you tell me if you can fixe and test, with my help of course, the issue in a reasonable delay? (2-3 months I'd say?)
If you can't I'll have to consider to buy another hardware player and maybe software as I can't listen these audio files.
Thank you in advance for your answer.
I added the audio latency gui settings hoping it would help you.
I tested a couple of the 2L files on 50ms, 100ms and 300ms and with channels set to 2.0, 2.1 and 5.1 and they all played fine for me, so I'm not sure what to suggest.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156