LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 06-04-2017, 05:59 PM   #31
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873

Also note that if you are using a HDMI to DVI adapter or a DVI connection on either side of the cable, that there is no audio channel on that connection type.
 
Old 06-04-2017, 06:12 PM   #32
notKlaatu
Senior Member
 
Registered: Sep 2010
Location: Lawrence, New Zealand
Distribution: Slackware
Posts: 1,075

Rep: Reputation: 725Reputation: 725Reputation: 725Reputation: 725Reputation: 725Reputation: 725Reputation: 725
How are you routing the output of Rosegarden? It has an internal mixer, so you need to tell your sound where to go.

Here's a pretty lengthy post about using Rosegarden:
http://slackermedia.info/handbook/do...?id=rosegarden
 
Old 06-04-2017, 08:04 PM   #33
maschelsea
Member
 
Registered: Dec 2016
Distribution: Slackware 64bit 14.2
Posts: 422

Original Poster
Rep: Reputation: Disabled
Code:
michael@caitlyn michael $ egrep -r -i hdmi /proc/asound/*
/proc/asound/NVidia/pcm3p/info:id: HDMI 0
/proc/asound/NVidia/pcm3p/info:name: HDMI 0
/proc/asound/NVidia/pcm3p/sub0/info:id: HDMI 0
/proc/asound/NVidia/pcm3p/sub0/info:name: HDMI 0
/proc/asound/NVidia/pcm7p/info:id: HDMI 0
/proc/asound/NVidia/pcm7p/info:name: HDMI 0
/proc/asound/NVidia/pcm7p/sub0/info:id: HDMI 0
/proc/asound/NVidia/pcm7p/sub0/info:name: HDMI 0
/proc/asound/NVidia/pcm8p/info:id: HDMI 0
/proc/asound/NVidia/pcm8p/info:name: HDMI 0
/proc/asound/NVidia/pcm8p/sub0/info:id: HDMI 0
/proc/asound/NVidia/pcm8p/sub0/info:name: HDMI 0
/proc/asound/NVidia/pcm9p/info:id: HDMI 0
/proc/asound/NVidia/pcm9p/info:name: HDMI 0
/proc/asound/NVidia/pcm9p/sub0/info:id: HDMI 0
/proc/asound/NVidia/pcm9p/sub0/info:name: HDMI 0
/proc/asound/NVidia/codec#0:Codec: Nvidia GPU 0b HDMI/DP
/proc/asound/NVidia/codec#0:  Pincap 0x09000094: OUT Detect HBR HDMI DP
/proc/asound/NVidia/codec#0:  Pin Default 0x18560010: [Jack] Digital Out at Int HDMI
/proc/asound/NVidia/codec#1:Codec: Nvidia GPU 0b HDMI/DP
/proc/asound/NVidia/codec#1:  Pincap 0x09000094: OUT Detect HBR HDMI DP
/proc/asound/NVidia/codec#1:  Pin Default 0x18560010: [Jack] Digital Out at Int HDMI
/proc/asound/NVidia/codec#2:Codec: Nvidia GPU 0b HDMI/DP
/proc/asound/NVidia/codec#2:  Pincap 0x09000094: OUT Detect HBR HDMI DP
/proc/asound/NVidia/codec#2:  Pin Default 0x18560010: [Jack] Digital Out at Int HDMI
/proc/asound/NVidia/codec#3:Codec: Nvidia GPU 0b HDMI/DP
/proc/asound/NVidia/codec#3:  Pincap 0x09000094: OUT Detect HBR HDMI DP
/proc/asound/NVidia/codec#3:  Pin Default 0x18560010: [Jack] Digital Out at Int HDMI
/proc/asound/card1/pcm3p/info:id: HDMI 0
/proc/asound/card1/pcm3p/info:name: HDMI 0
/proc/asound/card1/pcm3p/sub0/info:id: HDMI 0
/proc/asound/card1/pcm3p/sub0/info:name: HDMI 0
/proc/asound/card1/pcm7p/info:id: HDMI 0
/proc/asound/card1/pcm7p/info:name: HDMI 0
/proc/asound/card1/pcm7p/sub0/info:id: HDMI 0
/proc/asound/card1/pcm7p/sub0/info:name: HDMI 0
/proc/asound/card1/pcm8p/info:id: HDMI 0
/proc/asound/card1/pcm8p/info:name: HDMI 0
/proc/asound/card1/pcm8p/sub0/info:id: HDMI 0
/proc/asound/card1/pcm8p/sub0/info:name: HDMI 0
/proc/asound/card1/pcm9p/info:id: HDMI 0
/proc/asound/card1/pcm9p/info:name: HDMI 0
/proc/asound/card1/pcm9p/sub0/info:id: HDMI 0
/proc/asound/card1/pcm9p/sub0/info:name: HDMI 0
/proc/asound/card1/codec#0:Codec: Nvidia GPU 0b HDMI/DP
/proc/asound/card1/codec#0:  Pincap 0x09000094: OUT Detect HBR HDMI DP
/proc/asound/card1/codec#0:  Pin Default 0x18560010: [Jack] Digital Out at Int HDMI
/proc/asound/card1/codec#1:Codec: Nvidia GPU 0b HDMI/DP
/proc/asound/card1/codec#1:  Pincap 0x09000094: OUT Detect HBR HDMI DP
/proc/asound/card1/codec#1:  Pin Default 0x18560010: [Jack] Digital Out at Int HDMI
/proc/asound/card1/codec#2:Codec: Nvidia GPU 0b HDMI/DP
/proc/asound/card1/codec#2:  Pincap 0x09000094: OUT Detect HBR HDMI DP
/proc/asound/card1/codec#2:  Pin Default 0x18560010: [Jack] Digital Out at Int HDMI
/proc/asound/card1/codec#3:Codec: Nvidia GPU 0b HDMI/DP
/proc/asound/card1/codec#3:  Pincap 0x09000094: OUT Detect HBR HDMI DP
/proc/asound/card1/codec#3:  Pin Default 0x18560010: [Jack] Digital Out at Int HDMI
/proc/asound/pcm:01-03: HDMI 0 : HDMI 0 : playback 1
/proc/asound/pcm:01-07: HDMI 0 : HDMI 0 : playback 1
/proc/asound/pcm:01-08: HDMI 0 : HDMI 0 : playback 1
/proc/asound/pcm:01-09: HDMI 0 : HDMI 0 : playback 1

michael@caitlyn michael $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
  Subdevices: 0/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 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 9: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
michael@caitlyn michael $ aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
pulse
    PulseAudio Sound Server
sysdefault:CARD=PCH
    HDA Intel PCH, ALC887-VD Analog
    Default Audio Device
front:CARD=PCH,DEV=0
    HDA Intel PCH, ALC887-VD Analog
    Front speakers
surround21:CARD=PCH,DEV=0
    HDA Intel PCH, ALC887-VD Analog
    2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
    HDA Intel PCH, ALC887-VD Analog
    4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
    HDA Intel PCH, ALC887-VD Analog
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
    HDA Intel PCH, ALC887-VD Analog
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
    HDA Intel PCH, ALC887-VD Analog
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
    HDA Intel PCH, ALC887-VD 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 0
    HDMI Audio Output
hdmi:CARD=NVidia,DEV=2
    HDA NVidia, HDMI 0
    HDMI Audio Output
hdmi:CARD=NVidia,DEV=3
    HDA NVidia, HDMI 0
    HDMI Audio Output
I'm not sure what all this means. It's far too late in the day to make sense of the man pages...

Last edited by maschelsea; 06-04-2017 at 08:06 PM.
 
Old 06-04-2017, 08:54 PM   #34
maschelsea
Member
 
Registered: Dec 2016
Distribution: Slackware 64bit 14.2
Posts: 422

Original Poster
Rep: Reputation: Disabled
Crap! I uncommented the autospawn=yes line in /etc/pulse/client.conf and commented the autospawn=no line, saved, and rebooted and now I have NO SOUND period.
 
Old 06-04-2017, 10:15 PM   #35
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873
Translation, HDMI audio on hw:NVidia,3 (case matters)

Although looks like you have a potential 4 hdmi (or dports) outs. Not to imply that any of them are connected. Or that the connectors or cables are high enough quality to have all the bells and whistles. AKA no amount of configuration and knowledge compensates for faulty hardware.

HDMI audio potentially on:

hw:1,3
hw:1,7
hw:1,8
hw:1,9

At least as far as the alsa naming conventions goes. But again, DVI lacks the wires for the audio channel. And you would probably have to reference /var/log/Xorg.0.log to see which of the ports is connected. Or other places of reference like xrandr without parms. Or nvidia-xconfig or other options.
 
Old 06-05-2017, 03:19 PM   #36
maschelsea
Member
 
Registered: Dec 2016
Distribution: Slackware 64bit 14.2
Posts: 422

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by notKlaatu View Post
How are you routing the output of Rosegarden? It has an internal mixer, so you need to tell your sound where to go.

Here's a pretty lengthy post about using Rosegarden:
http://slackermedia.info/handbook/do...?id=rosegarden
The problem is at this moment I have no sound on my system at all. It's kind of freaking me out, seeing as how I just reinstalled slackware to fix another problem, WHILE I was working on solving this one...
 
Old 06-05-2017, 03:35 PM   #37
maschelsea
Member
 
Registered: Dec 2016
Distribution: Slackware 64bit 14.2
Posts: 422

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Shadow_7 View Post
Translation, HDMI audio on hw:NVidia,3 (case matters)

Although looks like you have a potential 4 hdmi (or dports) outs. Not to imply that any of them are connected. Or that the connectors or cables are high enough quality to have all the bells and whistles. AKA no amount of configuration and knowledge compensates for faulty hardware.

HDMI audio potentially on:

hw:1,3
hw:1,7
hw:1,8
hw:1,9

At least as far as the alsa naming conventions goes. But again, DVI lacks the wires for the audio channel. And you would probably have to reference /var/log/Xorg.0.log to see which of the ports is connected. Or other places of reference like xrandr without parms. Or nvidia-xconfig or other options.
Code:
root@caitlyn:~# grep -i audio  /var/log/Xorg.0.log
root@caitlyn:~#
I can try to post the entire /var/log/Xorg.0.log if you want it, but I honestly think it's too big to post here.

Code:
root@caitlyn:~# grep -i audio  /var/log/Xorg.0.log
root@caitlyn:~# xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
VGA-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
   1366x768      59.79 +
   1280x720      60.00  
   1024x768      75.08*   70.07    60.00  
   832x624       74.55  
   800x600       72.19    75.00    60.32    56.25  
   640x480       75.00    72.81    66.67    60.00  
   720x400       70.08  
root@caitlyn:~#
I ran nvidia-xconfig:
Code:
root@caitlyn:~# nvidia-xconfig

WARNING: Unable to locate/open X configuration file.

New X configuration file written to '/etc/X11/xorg.conf'

root@caitlyn:~#
I guess I need to restart X now so that the new config can load. I'll post again with the results...
 
Old 06-05-2017, 03:40 PM   #38
maschelsea
Member
 
Registered: Dec 2016
Distribution: Slackware 64bit 14.2
Posts: 422

Original Poster
Rep: Reputation: Disabled
X would not start with the new config file. I copied the log file to my /root before deleting it and running startx
Code:
root@caitlyn:~# grep EE Xorg.0.log 
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 67572.872] (EE) No devices detected.
[ 67572.872] (EE) 
[ 67572.872] (EE) no screens found(EE) 
[ 67572.872] (EE) 
[ 67572.872] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 67572.872] (EE) 
root@caitlyn:~#
 
Old 06-05-2017, 04:37 PM   #39
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873
Normally a reboot suffices. Although if that error persists, then rm /etc/X11/xorg.conf and try to run X again.

$ startx -- :0

Or at least rename or move it so it doesn't get used. There are pulse configurations that ONLY work in X, so if that's a persistent (OLD) issue for you, perhaps the reason you're having issues.
 
Old 06-06-2017, 03:34 PM   #40
maschelsea
Member
 
Registered: Dec 2016
Distribution: Slackware 64bit 14.2
Posts: 422

Original Poster
Rep: Reputation: Disabled
I reinstalled Slackware AGAIN to get my system sound back. I've got both jack and qjackctl, but I can't seem to figure out how to run jackd as a normal user. When I try, I see:
Code:
michael@caitlyn ~ $ jackd
jackd 0.124.1
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details


JACK is running in realtime mode, but you are not allowed to use realtime scheduling.

After applying these changes, please re-login in order for them to take effect.

You don't appear to have a sane system configuration. It is very likely that you
encounter xruns. Please apply all the above mentioned changes and start jack again!
michael@caitlyn ~ $
If this message provides any useful information AT ALL, I don't see it. I was running jackd as root before, which managed to screw up my system.
 
Old 06-06-2017, 03:40 PM   #41
maschelsea
Member
 
Registered: Dec 2016
Distribution: Slackware 64bit 14.2
Posts: 422

Original Poster
Rep: Reputation: Disabled
OK. I installed jack2. Now I have some sensible output, but qjackctl reports: Could not open ALSA sequencer as a client. ALSA MIDI patchbay will not be available. Do I need to install something else in addition to what I already have? My jack server output is:

Code:
michael@caitlyn mp3 $ jackd --realtime -d alsa --midi seq  --playback hw:0 &
[1] 32039
michael@caitlyn mp3 $ jackdmp 1.9.10
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
Could not open component .so '/usr/lib64/jack/jack_alsa_midi.so': /usr/lib64/jack/jack_alsa_midi.so: undefined symbol: jack_driver_init
Could not open component .so '/usr/lib64/jack/jack_alsa_midi.so': /usr/lib64/jack/jack_alsa_midi.so: undefined symbol: jack_driver_init
jack_get_descriptor : dll jack_alsa_midi.so is not a driver
jack_get_descriptor returns null for 'jack_alsa_midi.so'
Could not open component .so '/usr/lib64/jack/jack_oss.so': /usr/lib64/jack/jack_oss.so: undefined symbol: jack_driver_init
Could not open component .so '/usr/lib64/jack/jack_oss.so': /usr/lib64/jack/jack_oss.so: undefined symbol: jack_driver_init
jack_get_descriptor : dll jack_oss.so is not a driver
jack_get_descriptor returns null for 'jack_oss.so'
Could not open component .so '/usr/lib64/jack/jack_alsa_midi.so': /usr/lib64/jack/jack_alsa_midi.so: undefined symbol: jack_driver_init
Could not open component .so '/usr/lib64/jack/jack_oss.so': /usr/lib64/jack/jack_oss.so: undefined symbol: jack_driver_init
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
Engine profiling activated, beware 197 MBytes are needed to record profiling points...
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|-|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such device
failed to open alsa seq
ALSA: cannot attach MIDI: -19
 
Old 06-06-2017, 03:47 PM   #42
maschelsea
Member
 
Registered: Dec 2016
Distribution: Slackware 64bit 14.2
Posts: 422

Original Poster
Rep: Reputation: Disabled
I closed out the message. QJackCtl's Start button was greyed out, so I assumed that it had started jack successfully. I then launched rosegarden and loaded my most previously worked on part file and hit the play button. It didn't seem to do anything. When I double click on the track itself and hit the play button, progress begins just to the left of the bass clef, moves a centimeter, and then jumps back to it's first position.

I'm sorry that I'm being so whiney. Thank you for trying to help me in spite of that...
 
Old 06-06-2017, 03:49 PM   #43
maschelsea
Member
 
Registered: Dec 2016
Distribution: Slackware 64bit 14.2
Posts: 422

Original Poster
Rep: Reputation: Disabled
Message window from qjackctl:
Code:
15:37:01.626 Statistics reset.
15:37:01.628 Could not open ALSA sequencer as a client. ALSA MIDI patchbay will be not available.
ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such device
15:41:30.909 JACK connection change.
15:41:30.924 Client activated.
15:41:30.925 Patchbay deactivated.
Cannot lock down 207603658 byte memory area (Cannot allocate memory)
Cannot lock down 82274202 byte memory area (Cannot allocate memory)
15:41:47.350 JACK connection graph change.
15:41:47.376 JACK connection change.
15:41:47.434 JACK connection graph change.
15:41:47.578 JACK connection change.
 
Old 06-06-2017, 06:36 PM   #44
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873
With realtime (which you do not need, technically), there are things to change in /etc/security/limits.d/

$ cat /etc/security/limits.d/audio.conf.disabled
# Provided by the jackd package.
#
# Changes to this file will be preserved.
#
# If you want to enable/disable realtime permissions, run
#
# dpkg-reconfigure -p high jackd

@audio - rtprio 95
@audio - memlock unlimited
#@audio - nice -19

How it defaults on debian jessie, not that .disabled is the active configuration. The -r (lower case) as the first parm of jackd tells it NOT to use realtime scheduling. Not that it doesn't ignore it. Using jack2 (jackdbus) is more flexible with things like this, but the interface kind of sucks since you're mostly using jack_* CLI things to boss it around.

With qjackctl (whose start button starts jackd / jack1) you need to concern yourself with the [Connect] button and whether jack (and pulse?) things show up under the first tab [Audio]. If not then jack isn't running. Once jack is running then you need a sequencer like fluidsynth or timidity++. Then you can configure rosegarden and use midi sounds. Under studio the last time I set that up, but that was years ago. Otherwise the connections can be made with qjackctl (or jack_connect on the CLI). You could forgo jack and run timidity in alsa mode and use aconnect to make the connections. I made a probably harder to understand video on it a few years ago on a very old Dell (P4 processor). Some 3 years ago it seems. A horrible video with sync issues, but lacking high spec'd hardware, it would be difficult to do better at the moment.

https://www.youtube.com/watch?v=68dNginMNKY
 
Old 06-06-2017, 07:19 PM   #45
maschelsea
Member
 
Registered: Dec 2016
Distribution: Slackware 64bit 14.2
Posts: 422

Original Poster
Rep: Reputation: Disabled
In qjackctl, under Connections, I see a window with tabs for Audio, MIDI, and ALSA. I see nothing listed in either the MIDI, or ALSA tabs. In Audio tab I see System->Capture_1 and Capture_2 are readable, and System->Playback_1 and Playback_2 are writeable. The counter on qjackctl's main window is stuck at 0:00.
 
  


Reply

Tags
jack, midi, rosegarden


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
no sound in rosegarden/qsynth jpee Linux - General 1 11-11-2015 04:56 PM
Rosegarden help! Can't get sound from keyboard. jimmyjazzstl Linux - Software 0 07-22-2009 06:30 PM
No sound with Rosegarden linmix Linux - Software 27 11-25-2006 10:39 AM
Rosegarden; sound is muted? Nailgun Linux - Software 7 11-05-2006 02:20 PM
no sound for rosegarden drethenerd Linux - Software 9 08-22-2005 12:44 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 05:33 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration