Page 1 of 3 123 LastLast
Results 1 to 10 of 23

Thread: Openbox (NOT-kde) no sound for games after zypper dup 12.2>12.3

  1. #1

    Default Openbox (NOT-kde) no sound for games after zypper dup 12.2>12.3


    I recently followed the on-line upgrade path outlined in:

    http://<br /> http://en.opensuse.org..._upgrade<br />

    By and large I'm quite happy with the results. But I've noticed something
    about sound output from games such as "Amoebax, KBreakOut, & FreeDink"
    Namely, there isn't any. Though the system bell still works as does sound
    output from "music on console" and mplayer. Also streaming audio works from
    sites like:

    http://<br /> http://upchucky.org/Ju...yer.htm?<br />

    And streaming audio/video from sites like:

    http://<br /> http://www.youtube.com...eAcpFkL8<br />

    But when I play a game... No sound!

    Suggestions anyone?

    Don't know if it matters but:
    I symlinked default.target to runlevel3.target, so I login on a virtual
    console, and use startx when I'm ready for the GUI...

    my ~/.xinitrc:
    Code:
    qterminal --drop &
    lxpanel &
    xrandr -s 3
    synclient TouchpadOff=2
    /usr/bin/openbox-session
    --
    JtWdyP


  2. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: Openbox (NOT-kde) no sound for games after zypper dup 12.2>12.3

    There are different types of "sounds"

    From your description I suspect your game uses MIDI (a type of synthesized sound).
    Recommend you download a sound clip and try to play to verify.
    If the sound <does> play, then my guess is that the problem is more likely an app setting.

    TSU

  3. #3

    Default Re: Openbox (NOT-kde) no sound for games after zypper dup12.2>12.3


    It would appear that on Mar 22, tsu2 did say:

    > There are different types of "sounds"
    >
    > From your description I suspect your game uses MIDI (a type of
    > synthesized sound).
    > Recommend you download a sound clip and try to play to verify.
    > If the sound <does> play, then my guess is that the problem is more
    > likely an app setting.


    I suppose that's possible, But these same games played sounds just fine
    when my system was still version 12.2...

    I suppose the upgraded version might have a different setting. Though as I
    recall I had wanted Amoebax bad enough that I temporarily enabled a 12.3 repo
    to get it.

    Still, I don't see what it could hurt to test a sound clip... Any suggestions
    on where to get the kind your talking about?

    Thanks

    --
    JtWdyP


  4. #4
    Join Date
    Jun 2008
    Location
    Sogndal, Noreg
    Posts
    1,103

    Default Re: Openbox (NOT-kde) no sound for games after zypper dup 12.2>12.3

    I don't think this is related to MIDI, open a terminal and start any of the games from there and see what it outputs.
    OpenSuSE 13.1, KDE 4.11.5, 64bit
    Gigabyte 990FXA-UD3, AMD FX8350, MSI GeForce GTX 760, RME HDSP9632, 16GB HyperX Kingston DDR3, Samsung 840-Pro SSD 128GB, WD Desktop Black 1TB, Hitachi Deskstar 7K1000 750GB

  5. #5

    Default Re: Openbox (NOT-kde) no sound for games after zypper dup12.2>12.3


    It would appear that on Mar 23, F Sauce did say:

    > I don't think this is related to MIDI, open a terminal and start any of
    > the games from there and see what it outputs.


    Quote Originally Posted by konsole:amoebax:
    Couldn't open sound system: No available audio device
    [IMG]
    http://i62.tinypic.com/28jk477.png
    [/IMG]

    Quote Originally Posted by Yast:
    --
    JtWdyP


  6. #6
    Join Date
    Jun 2008
    Location
    Sogndal, Noreg
    Posts
    1,103

    Default Re: Openbox (NOT-kde) no sound for games after zypper dup 12.2>12.3

    Hi.

    What does KBreakout output?
    You mentioned something about amoebax coming from a third party repo, so it might not be that relevant for this test; and it did not reveal much anyhow.

    Couldn't open sound system: No available audio device
    I'm guessing that this indicates that the device is reported to be busy, not necessarily 'not found'; do you use PulseAudio, and does outputting sound from multiple applications/sources simultaneously work?

    This command will give some information about audio applications/processes currently running:
    Code:
    lsof /dev/snd/*
    OpenSuSE 13.1, KDE 4.11.5, 64bit
    Gigabyte 990FXA-UD3, AMD FX8350, MSI GeForce GTX 760, RME HDSP9632, 16GB HyperX Kingston DDR3, Samsung 840-Pro SSD 128GB, WD Desktop Black 1TB, Hitachi Deskstar 7K1000 750GB

  7. #7
    Join Date
    Jun 2008
    Location
    Sogndal, Noreg
    Posts
    1,103

    Default Re: Openbox (NOT-kde) no sound for games after zypper dup 12.2>12.3

    Might also be worth checking the SDL libs, check where they originate from. If you have the games repo ( or education + similar ) enabled in addition to the -oss, mixing packages from these repoes may cause trouble. As long as they are provided, and suffice, I would stick to using packages from the official repoes (-oss, non-oss, updates).

    BTW, I just tested amoebax (never heard of it before) it ran fine and sound was never an issue.

    Olav
    OpenSuSE 13.1, KDE 4.11.5, 64bit
    Gigabyte 990FXA-UD3, AMD FX8350, MSI GeForce GTX 760, RME HDSP9632, 16GB HyperX Kingston DDR3, Samsung 840-Pro SSD 128GB, WD Desktop Black 1TB, Hitachi Deskstar 7K1000 750GB

  8. #8

    Default Re: Openbox (NOT-kde) no sound for games after zypper dup12.2>12.3


    It would appear that on Mar 24, F Sauce did say:

    > What does KBreakout output?


    Quote Originally Posted by konsole:kbreakout:
    Code:
    JtWdyP -> ~
    > kbreakout
    Object::connect: No such slot MainWindow::loadSettings()
    Object::connect:  (sender name:   'settings')
    Object::connect:  (receiver name: 'MainWindow#1')
    JtWdyP -> ~
    > kbreakout
    JtWdyP -> ~
    >
    Note: my 2 line bash prompt includes an leading "> "
    In the first instance I peeked in settings to make sure there wasn't a
    "sound off" setting in play... (only use a few kde apps since kde4 got me to
    look elsewhere... So much of kde is not installed) {didn't interfere with
    sound in 12.2??}

    > You mentioned something about *amoebax *coming from a third party repo,
    > so it might not be that relevant for this test; and it did not reveal
    > much anyhow.


    True that! Though about sound, kbreakout is saying even less... :sigh:

    > > Couldn't open sound system: No available audio device

    > I'm guessing that this indicates that the device is reported to be busy,
    > not necessarily 'not found'; do you use PulseAudio, and does outputting
    > sound from multiple applications/sources simultaneously work?


    Only use pulseaudio to the extent forced to by applicable distro devs...
    As to multi-sources... see below.

    > This command will give some information about audio
    > applications/processes currently running:
    >
    > Code:
    > --------------------
    > lsof /dev/snd/*
    >
    > --------------------


    Code:
    JtWdyP -> ~
    > lsof /dev/snd/*
    JtWdyP -> ~
    > man lsof
    JtWdyP -> ~
    >

    After some empirical poking around I found lsof more informative from inside
    an midnight commander session...

    Which in itself reveled:



    Code:
    JtWdyP -> ~
    > mc
    
    JtWdyP -> /dev/snd/by-path
    > lsof /dev/snd/*
    COMMAND  PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
    mc      3781 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    bash    3783 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    lsof    3863 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    lsof    3864 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    JtWdyP -> /dev/snd/by-path
    > amoebax &
    [1] 3971
    JtWdyP -> /dev/snd/by-path
    > Couldn't open sound system: No available audio device
    
    JtWdyP -> /dev/snd/by-path
    > lsof /dev/snd/*
    COMMAND  PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
    mc      3781 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    bash    3783 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    amoebax 3971 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    lsof    3981 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    lsof    3982 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    JtWdyP -> /dev/snd/by-path
    > ls
    pci-0000:00:14.2
    JtWdyP -> /dev/snd/by-path
    >
    I tested running sound from multiple sources with these results:

    Code:
    JtWdyP -> /dev/snd/by-path
    > lsof /dev/snd/*
    COMMAND    PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
    mc        3781 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    bash      3783 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    amoebax   3971 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    opera:lib 4062 jtwdyp  mem    CHR  116,4          8147 /dev/snd/pcmC0D0p
    opera:lib 4062 jtwdyp   13r   CHR 116,33      0t0 5443 /dev/snd/timer
    opera:lib 4062 jtwdyp   15u   CHR  116,4      0t0 8147 /dev/snd/pcmC0D0p
    mocp      4374 jtwdyp    8u   CHR  116,8      0t0 8153 /dev/snd/controlC0
    lsof      4386 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    lsof      4387 jtwdyp  cwd    DIR    0,5       60 6571 /dev/snd/by-path
    JtWdyP -> /dev/snd/by-path
    >
    I note that Music on Console had a stronger signal, But if I selected a tune
    with quiet spaces built in AKA something from Gordon Lightfoot, I could hear
    both that, and the tune from:

    http://<br /> http://upchucky.org/Ju...yer.htm?<br />

    (at the same time)

    It would appear that on Mar 24, F Sauce also said:

    > Might also be worth checking the SDL libs, check where they originate
    > from. If you have the games repo ( or education + similar ) enabled in
    > addition to the -oss, mixing packages from these repoes may cause
    > trouble. As long as they are provided, and suffice, I would stick to
    > using packages from the official repoes (-oss, non-oss, updates).


    Not sure how to check the "SDL libs"...

    Have games, never enabled during "zypper up" (nor of course "dup")


    > BTW, I just tested *amoebax *(never heard of it before) it ran fine and
    > sound was never an issue.


    Can't remember where I first found it. But discovered it was addictive enough
    to want in any distro I spend much time using... Didn't have any sound issues
    with it in 12.2, Nor do I on my old 'nvidia' HP desktop which just did an:

    "12.2 > 12.3 zypper dup"

    yesterday... But on this almost as old gateway laptop... :sigh:

    --
    JtWdyP


  9. #9
    Join Date
    Jun 2008
    Location
    Sogndal, Noreg
    Posts
    1,103

    Default Re: Openbox (NOT-kde) no sound for games after zypper dup 12.2>12.3

    SDL http://www.libsdl.org/ is often used by games, though you could use it for instance as the audio-output 'driver' for MPlayer also. To check which repo packages come from, go in to YaST Software Manager search for 'sdl' and scroll through the sdl packages with the Versions tab open.

    I found the picture of 'alsamixer' a bit strange, have you modified channel views or similar?
    Maybe this shows something interesting:
    Code:
    aplay -l
    You could also show us the repository list:
    Code:
    zypper -ls
    OpenSuSE 13.1, KDE 4.11.5, 64bit
    Gigabyte 990FXA-UD3, AMD FX8350, MSI GeForce GTX 760, RME HDSP9632, 16GB HyperX Kingston DDR3, Samsung 840-Pro SSD 128GB, WD Desktop Black 1TB, Hitachi Deskstar 7K1000 750GB

  10. #10

    Default Re: Openbox (NOT-kde) no sound for games after zypper dup12.2>12.3


    It would appear that on Mar 24, F Sauce did say:

    > SDL http://www.libsdl.org/ is often used by games, though you could use
    > it for instance as the audio-output 'driver' for MPlayer also. To check
    > which repo packages come from, go in to YaST Software Manager search for
    > 'sdl' and scroll through the sdl packages with the Versions tab open.


    I'll have to check that out then...

    > I found the picture of 'alsamixer' a bit strange, have you modified
    > channel views or similar?


    Nope it opens by default on the "playback channels" view... Or is it that your
    used to seeing more playback channels? I'm not sure of the technical details.
    But I've had the impression that for the past few years, most Linux distros
    have pretty much embedded pulseaudio dependencies that interfere with some
    alsa tools. I quickly realized that I didn't have the skill or time to keep
    things running with all things pulseaudio completely purged. But, if memory
    serves... ever since pulseaudio gained such favor with the devs, my laptop's
    list of available channels in the alsamixer have been reduced. Not that
    I really used the missing channels. Nor can I say if I was even running
    opensuse at the time.

    But it's the reason I dislike pulseaudio almost as much as I dislike software
    written by a certain company in Redmond...

    > Maybe this shows something interesting:
    >
    > Code:
    > --------------------
    > aplay -l
    > --------------------


    Code:
    ~
    UnderTree=-> aplay -l
    **** List of PLAYBACK Hardware Devices ****
    card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
    card 0: SB [HDA ATI SB], device 6: Si3054 Modem [Si3054 Modem]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
    ~
    UnderTree=->

    > You could also show us the repository list:
    >
    > Code:
    > --------------------
    > zypper -ls
    > --------------------



    Code:
    ~
    UnderTree=-> zypper -ls
    Unknown option 'l'
    Missing argument for -ls
    ~
    UnderTree=-> zypper lr |grep "Yes     |"
    6 | packman                   | Packman repository (openSUSE_12.3) | Yes     | Yes
    10 | repo-non-oss              | openSUSE-12.3-Non-Oss              | Yes     | Yes
    11 | repo-oss                  | openSUSE-12.3-Oss                  | Yes     | Yes
    13 | repo-update               | openSUSE-12.3-Update               | Yes     | Yes
    14 | repo-update-non-oss       | openSUSE-12.3-Update-Non-Oss       | Yes     | Yes
    ~
    UnderTree=-> zypper lr |grep "No      |"
    1 | X11:QtDesktop             | X11:QtDesktop                      | No      | No
    2 | X11_Utilities             | X11 Utilities (openSUSE_12.3)      | No      | No
    3 | games                     | games                              | No      | No
    4 | libdvdcss                 | DVD Repository                     | No      | No
    5 | openSUSE:Tools            | openSUSE:Tools                     | No      | No
    7 | repo-debug                | openSUSE-12.3-Debug                | No      | No
    8 | repo-debug-update         | openSUSE-12.3-Update-Debug         | No      | No
    9 | repo-debug-update-non-oss | openSUSE-12.3-Update-Debug-Non-Oss | No      | No
    12 | repo-source               | openSUSE-12.3-Source               | No      | No
    15 | server:mail               | server:mail                        | No      | No
    16 | server:proxy              | server:proxy                       | No      | No
    ~
    UnderTree=->

    BTW Don't know what or why, But every now and then while doing something
    inside a "konsole" I've been noticing a notification pop-up that claims the
    "multi-media" sound something or other "does not work" switching to "default"
    It goes away before I can read it properly. The last time was while I was doing
    something with my alpine mail/usenet client. I think it was while saving about
    a hundred messages from opensuse's NTTP forum access server to a local folder.
    But I'm not sure... It might even have been when I first opened the
    reply/followup composer session for this message. But I'm sure that I wasn't
    even using sound at the time, unless maybe it was the system bell??

    Not a all sure those notifications are relevant though. Because I used to see
    them once in a while before the zypper dup. Back when the games still had sound.

    --
    JtWdyP


Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •