VectorLinux

Please login or register.

Login with username, password and session length
Advanced search  

News:

Visit our home page for VL info. For support and documentation, visit the Vector Linux Knowledge Center or search the Knowledge Center and this Forum using the search box above.

Pages: 1 2 [3] 4 5 ... 10
 21 
 on: January 08, 2017, 02:34:00 am 
Started by vector - Last post by Lyn
any updates on this? 

 22 
 on: December 20, 2016, 10:01:38 am 
Started by Rytz - Last post by Rytz
Greetings:

I spent many hours yesterday scouring the interwebs on how to configure ALSA for a single source, multiple device output configuration.  I have a standard internal analog jack (onboard Intel) and HDMI audio through my NVidia video card.

Thus far, I can get both audio devices working correctly individually, but not jointly.  Technically, I was able to get both devices working together, however I was only getting random pops and crackles as an output.

I also noticed that with single working HDMI audio output, there is 100-200 milliseconds behind its visual counterpart.

Any suggestions on how to get both audio outputs working together at the same time appreciated.  Also, any information on how to remove the HDMI audio latency / delay appreciated. Thanks!

Here's the configuration stuff and asound.conf files used:

aplay -L
Code: [Select]
null
    Discard all samples (playback) or generate zero samples (capture)
default:CARD=PCH
    HDA Intel PCH, ALC887 Analog
    Default Audio Device
sysdefault:CARD=PCH
    HDA Intel PCH, ALC887 Analog
    Default Audio Device
front:CARD=PCH,DEV=0
    HDA Intel PCH, ALC887 Analog
    Front speakers
surround40:CARD=PCH,DEV=0
    HDA Intel PCH, ALC887 Analog
    4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
    HDA Intel PCH, ALC887 Analog
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
    HDA Intel PCH, ALC887 Analog
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
    HDA Intel PCH, ALC887 Analog
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
    HDA Intel PCH, ALC887 Analog
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
hdmi:CARD=NVidia,DEV=0
    HDA NVidia, HDMI 0
    HDMI Audio Output
hdmi:CARD=NVidia,DEV=1
    HDA NVidia, HDMI 1
    HDMI Audio Output

aplay -l
Code: [Select]
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC887 Analog [ALC887 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

speaker-test -D default:CARD=PCH -c 2
Code: [Select]
speaker-test 1.0.26

Playback device is default:CARD=PCH
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 2048 to 8192
Period size range from 1024 to 1024
Using max buffer size 8192
Periods = 4
was set period_size = 1024
was set buffer_size = 8192

speaker-test -D hdmi:CARD=NVidia,DEV=1 -c 2
Code: [Select]
speaker-test 1.0.26

Playback device is hdmi:CARD=NVidia,DEV=1
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 64 to 16384
Period size range from 32 to 8192
Using max buffer size 16384
Periods = 4
was set period_size = 4096
was set buffer_size = 16384

asound.conf (working analog) (works by default without asound.conf)
Code: [Select]
defaults.pcm.card 0
defaults.pcm.device 0
defaults.ctl.card 0

asound.conf (working HDMI, 100-200 ms lag behind visuals)
Code: [Select]
defaults.pcm.card 1
defaults.pcm.device 7
defaults.ctl.card 1

asound.conf (static+pops dual)
Code: [Select]
pcm.!default {
        type plug
        slave.pcm both
        ttable.0.0 1.0
        ttable.1.1 1.0
        ttable.0.2 1.0
        ttable.1.3 1.0
}

pcm.ana {
        type hw
        card 0
        device 0
        channels 2
}

pcm.digi {
        type hw
        card 1
        device 7
        channels 2
}

pcm.both {
        type multi
        slaves.a.pcm "digi"
        slaves.b.pcm "ana"
        bindings.0.slave a
        bindings.0.channel 0
        bindings.1.slave a
        bindings.1.channel 1
        bindings.2.slave b
        bindings.2.channel 0
        bindings.3.slave b
        bindings.3.channel 1
}

# tested with/without, no difference
#ctl.!default {
#        type hw
#        card "NVidia"
#}

 23 
 on: December 19, 2016, 12:09:00 am 
Started by vector - Last post by vincent2
expecting vl7.2  xmas  beta  soon!

 24 
 on: December 16, 2016, 05:05:10 am 
Started by metvas - Last post by nightflier
Maybe I should specify: my "Kodi box" is a Raspberry Pi running OpenElec.

If you're talking about the "tvKodiBOX" (http://tvkodibox.com/), I would not know, but I see an ethernet port in pictures of it.

 25 
 on: December 15, 2016, 06:17:30 pm 
Started by metvas - Last post by nightflier
I have one, and yes, it is networked. What in particular are you looking for?

 26 
 on: December 15, 2016, 04:52:28 am 
Started by metvas - Last post by metvas
Hi has anyone figured out if a KODI box can be networked ?
Thanks

 27 
 on: December 12, 2016, 05:38:34 pm 
Started by macondo - Last post by macondo
I changed the keybind for the menu, a la icewm, now I just press the winkey on the left:

Code: [Select]
<Key mask="" key="Super_L">root:1</Key>

 28 
 on: December 09, 2016, 07:47:07 am 
Started by retired1af - Last post by retired1af
Apparently there's a way to configure the wrapper to look in places other than the defaults. I'll do some digging on it today and see what I can come up with.

 29 
 on: December 09, 2016, 07:32:13 am 
Started by retired1af - Last post by M0E-lnx
I'm not positive that will work on firefox.

These are the paths where the slack packages places the stuff at

Code: [Select]
usr/lib64/chromium/PepperFlash/manifest.json
usr/lib64/chromium/PepperFlash/libpepflashplayer.so

We can certainly copy these over to FF, but like I said... i'm almost positive it wont work.

 30 
 on: December 09, 2016, 04:03:02 am 
Started by retired1af - Last post by retired1af
OK. Got to digging. The wrapper does not include pepperflash. It just looks for it in the default locations that Chrome installs it to.

Installed chrome. Still not finding it.

I did find this:  http://taper.alienbase.nl/mirrors/people/alien/slackbuilds/chromium-pepperflash-plugin/

Problem is, I did install that package but cannot find the required file using find. So it's doubtful that the package worked.

Pages: 1 2 [3] 4 5 ... 10