[00:45] MaynardWaters: with JACK? [00:45] MaynardWaters: i would stop JACK, and install/open pavocontrol [00:46] get a known good file with a known good system codec playing the file, and check the routing.. using a player you know well that is configured for pulse [00:47] then, you can mess about in "alsamixer" .. and also refer to main #ubuntu or the main ubuntu suppport, since that is not ubuntustudio specifically [11:04] Hi, I'm looking for a bit of help. We have a tiny computer that we use as information radiators that are plugged on two different tvs, and we'd like to be able to play sounds on either one of them selectively. Both are connected through HDMI, and ubuntu seems to recognize both HDMI sound outputs. How can I play a sound on only one of those? [15:03] mister_zombie: im not following [15:03] mister_zombie: i would confirm the audio is working via HDMI, because that can be challenging [15:04] i would specifiy what exactly you are trying to play and how.. im not sure if you are talking about streaming or not [15:04] sounds like pulse is capable or doing what i think you are tring to do... and you could ask in the main #ubuntu channel [15:06] They told me to ask here. [15:07] mister_zombie: they? [15:07] I confirmed that both HDMI outputs were connected and working using the sound settings. [15:07] holstein: #ubuntu [15:07] mister_zombie: "they" likely dont understand what you are asking [15:07] mister_zombie: and, you *can* and should ask here.. but im just telling you where to ask and how [15:07] mister_zombie: this is *not* an ubuntustudio specific issue [15:07] Really the plan is just to use a cli command to play a sound on either one of the tvs. [15:08] Fair enough, thank you for your time. [15:08] mister_zombie: then, ssh in,a nd play the file [15:08] paplay should work [15:08] I only get one sink in pactl though. [15:08] i have used cvlc and mp3blaster [15:09] mister_zombie: what "sink" where? if audio works, ssh into the machine, and play the file [15:09] you can use screen to leave the file playing, and reconnect [15:09] !info screen [15:09] screen (source: screen): terminal multiplexor with VT100/ANSI terminal emulation. In component main, is optional. Version 4.0.3-14ubuntu9 (raring), package size 584 kB, installed size 885 kB [15:10] i used to use screen to connect in and play files with cvlc (command live VLC) or mp3blaster [15:10] That I understand. What I don't know is how to play a sound on only one tv at a time. [15:11] mister_zombie: and, i have no idea what TV's you are talking about, or how they are connected to what where or why [15:11] mister_zombie: if you have a machine connected to TV 1, ssh into the computer connected to TV 1 and play the file [15:12] the computer connected to TV2 will be the one you play from to play music on TV2 [15:12] I have two tvs connected through HDMI to one computer. [15:12] mister_zombie: you should be able to specify the output device [15:13] mister_zombie: so you have two hdmi ports on the computer? [15:13] Yes [15:13] mister_zombie: i would want to forward a desktop and just use "pavucontrol" [15:13] i would not assume that *either* or *both* of those HDMI ports are working with audio [15:13] and you also have onboard sound? [15:13] otherwise, pavucontrol is a nice easy way to route audio like that [15:13] !info pavucontrol [15:13] pavucontrol (source: pavucontrol): PulseAudio Volume Control. In component universe, is optional. Version 1.0-1 (raring), package size 140 kB, installed size 953 kB [15:14] OvenWerks: holstein: I confirmed it worked with Ubuntu's Sound preferences, where I selected Left-right for both outputs and it tested fine [15:14] I'll ask my network guys to install it [15:14] So you just want to be able to route from command line. [15:15] mister_zombie: you'll ask who to install what? [15:15] mister_zombie: are you ssh into the box then? [15:16] If so you need to dbus-launch screen for the pulse cl tools to work properly [15:16] pulse depends on there being a running session [15:17] ssh does not provide that on it's own, screen does [15:18] The dbus-launch makes sure that the dbus info is in the environment of any screen terminal [15:18] holstein: I don't have admin rights on the box. OvenWerks: So if I already have a running session, SSH should work fine, correct? The TVs are mainly used to output firefox tabs [15:19] once screen is running, a new ssh would do screen -dr to reconnect to the running session [15:19] Darnit, screen not even installed. I'll just mail them right away. [15:21] you can test without screen.. and i would.. since you literally dont konw if that is going to work out for you yet [15:21] Right. [15:21] Vnc, here I come [15:21] i know, i would just forward a destkop.. [15:21] but, i have admin rights to my hardware, and i dont use hdmi audio.. [15:23] I only get one sink in pulseaudio, still, called "alsa_output.pci-000_00_1b.0.hdmi-stereo" [15:24] mister_zombie: if this is not a headless machine (as I assumed) then screen will not work for you. If you are already running a graphic session, an ssh login will need the dbus info for that session [15:25] mister_zombie: i have asked if you tested both HDMI outputs in pulse.. if you havent, then do so [15:25] you will need to add a script to your session startup that saves three of the environmental variables to a file and then set up a script that restores them when you log in ssh [15:26] you need to be able to talk to the same PA instance as the graphic session is running [15:27] you are testint too many things at once [15:27] testing* [15:27] there are two dbus lines plus you may also need $SCREEN [15:27] connect a monitor and keyboard and mouse.. and test the 2 audio source outputs on a normal desktop.. then, test remotely doing that in a terminal or whatever.. and *then* headless [15:27] sorry $DISPLAY [15:29] holstein: the sound is from Firefox, so it is not headless., just remote audio control [15:29] OvenWerks: holstein: I think you guys put me on the right path, thanks a lot, I'll try some things [15:31] mister_zombie: good luck.. and keep the troubleshooting simple! [16:06] Hey, anybody know what Xorg could want to do every two minutes on the dot that spikes its CPU use and triggers XRUNs over in Jack+Ardour? [16:06] I left the machine running overnight to see whether it would keep doing it. I'm running the .48 true-preemptive realtime kernel right now. [16:07] Otherwise 12.04LTS, last security-updated about a week ago. [16:07] solarbird: realtime or -lowlatency? [16:08] solarbird: screen saver? [16:15] Realtime. And I have screensaver disabled. [16:15] I compiled it yesterday, trying to solve the _other_ big XRUN problem. [16:16] just watching top on my machine. It is mostly idle. Nothing gets to more than 2% [16:17] but if I mouse a lot that goes up. [16:17] (Which, on a related note, I've gone through this: http://wiki.linuxaudio.org/wiki/system_configuration#sysctlconf in excrutiating detail and my system passes all those tests, and I still get an XRUN every time I enable master record, unless I set latency up to over 330ms-ish.) [16:17] maybe try unplugging your mouse and see. [16:17] Is your mouse USB by chance? [16:18] (Despite running on a quad-core CPU with 4G of RAM, mostly idle, and not paging _at all_,) Nope. [16:18] could be graphics [16:18] I kept it off the USB chain intentionally. [16:18] do you have wireless? [16:19] Nope. Kept it off that intentionally as well. [16:20] Also, yanking the network has zero effect. [16:21] theoretically, the use of the rtirq script should ensure the audio device receives priority [16:21] solarbird: Have you checked variables around that? [16:21] cat /proc/interrupts [16:21] if it is set up to do so [16:22] solarbird: ps -eo comm,rtprio [16:23] what are you looking for in the interrupt table? [16:23] solarbird: To make sure your audio device isn't sharing IRQ with other devices [16:24] Oh, I've been through that. It's not. [16:24] It's a USB device which yes I know is not awesome. But it's what I have. [16:24] (TASCAM US-800.) [16:28] oh, right, I forgot. the link to the rtirq script 404s, so I didn't do that. [16:31] solarbird: It was installed with linux-lowlatency [16:31] you can find it in /etc/init.d/rtirq [16:31] the package is called rtirq-init [16:32] the config file is at /etc/default/rtirq [16:32] Assuming you will always be using the same usb plug, use lsusb to find out which usb you are using [16:32] it autostarts, and is compatible with linux-lowlatency, but not -generic [16:32] well, not by default [16:32] it needs a kernel parameter to be used [16:33] then in /etc/default/rtirq on the first non-comment line: [16:33] it can be hardcoded into the kernel, using a config option [16:33] RTIRQ_NAME_LIST="rtc snd usb i8042" [16:33] linux-lowlatency includes this kernel parameter - it's hardcoded [16:34] might be that you need to set the -rt kernel to use a kernel parameter [16:34] change that to: "rtc usb3 snd usb i8042" [16:34] if you happen to be using usb3 change it to what you are using [16:34] if not. [16:34] In /etc/default/grub, change GRUB_CMDLINE_LINUX="" into GRUB_CMDLINE_LINUX="threadirqs" [16:34] should that change-it-to be usb2? I'm on usb2, not 3. [16:35] yup [16:36] okay both changes made. [16:36] reboot [16:36] bbiab... [16:37] (becuase I'm on that machine, lol.) [16:41] Same XRUN on record-enable; waiting now to see whether we get the every-two-seconds XRUNs... [16:42] Yep. Right on schedule. [16:42] does lsmod show the wireless module is loaded even thoghturned off? [16:42] I have a meeting but will leave this up if you have any other ideas to throw in there... [16:43] ipw isn't it? if so: no. [16:45] * solarbird cancels tomorrow's recording session pending figuring this out. [16:53] how can I tell which version of ubuntu studio is running ? [16:54] cat /etc/os-release [16:55] thank you !! [18:32] holstein: thanks for the advice, when I am not at work I will give it a go again and let you know what i find. [18:52] * solarbird returns === Fyodorovna is now known as wilee-nilee === ShapeShi- is now known as ShapeShifter499