[00:28] <raven> hello I am new to ubuntu studio and I am trying to get things set up correctly
[00:28] <zequence> raven: What are you wanting to set up?
[00:29] <raven> using jack and patchage along with idjc  none of the pulse audio jack modules are showing in patchage and I need to get them listed somehow
[00:30] <zequence> raven: That's cause patchage does not start jackdbus by default (think)
[00:30] <zequence> raven: You can check by doing, in a terminal: ps -eo comm | grep jack
[00:31] <zequence> raven: It is possible to start the jack sink and source modules for pulseaudio manually, but they won't start automatically unless you start jackdbus
[00:32] <zequence> raven: you can also start jackdbus manually, before starting patchage
[00:32] <zequence> starting jackdbus manually: jack_control start
[00:32] <raven> the list that came up from console is:  jackd
[00:32] <raven> qjackctl
[00:32] <raven> qjackctl.real
[00:32] <raven> jackdbus
[00:32] <zequence> Then you have both of them running, all though, I think jackdbus is probably not processing audio right now
[00:32] <raven> idjc wont run without jackdbus
[00:33] <zequence> Close patchage
[00:33] <raven> ok
[00:33] <zequence> Kill jack, and jackdbus: killall -9 jackd*
[00:34] <raven> ok
[00:34] <zequence> raven: Wait, that won't work
[00:34] <zequence> killall -9 jackd
[00:34] <zequence> Then, killall -9 jackdbus
[00:34] <raven> ok
[00:34] <zequence> raven: You can close qjackctl too, btw
[00:35] <zequence> if you want
[00:35] <raven> i did
[00:35] <zequence> raven: Hopefully the right device is chosen to be used with jack
[00:35] <zequence> raven: Actually, it might be smart to use qjackctl for starting jack
[00:36] <zequence> for this reason
[00:36] <raven> it's set for default which HW0:0
[00:36] <zequence> I usually always set it to use my device by name ID, instead of number ID
[00:36] <zequence> If you have more than once device, there's no garantee that they will boot in the same order
[00:37] <zequence> you can see the name of your card, by doing: cat /proc/asound/cards
[00:37] <zequence> This is the card I use:
[00:37] <zequence> 0 [M66            ]: ICE1712 - M Audio Delta 66 M Audio Delta 66 at 0xd040, irq 21
[00:37] <zequence> The name ID is "M66"
[00:38] <raven> okay so my id is nvidia
[00:38] <zequence> raven: HDMI?
[00:38] <raven> hdmi and analog
[00:38] <zequence> My HDMI doesn't even start with jack
[00:39] <raven> i was worried till i brought up idjc and heard my stream through my speakers
[00:39] <zequence> Anyway, you can write it manually into the "Interface" field in "Setup" of qjackctl
[00:40] <zequence> The relevant config file for jackdbus is in ~/.config/jack/conf.xml
[00:40] <zequence> Mine looks like this
[00:40] <zequence>  <drivers>
[00:40] <zequence>   <driver name="alsa">
[00:40] <zequence>    <option name="device">hw:M66</option>
[00:40] <zequence>    <option name="capture">hw:M66</option>
[00:40] <zequence>    <option name="playback">hw:M66</option>
[00:40] <zequence> qjackctl will write that for you
[00:41] <zequence> those were the relevant lines
[00:41] <zequence> So, either use qjackctl to start jackdbus, or from the commandline (if your config file is right): jack_control start
[00:42] <zequence> let me try patchage with jackdbus..
[00:42] <raven> okay
[00:45] <zequence> raven: Yeah, working
[00:46] <raven> okay
[00:46] <zequence> raven: So, all you need to do is make sure you start jackdbus, not jackd, if you have pulseaudio-module-jack installed, and the module will auto start the jack sink and source
[00:47] <raven> qjackctl starts both jackd and jackdbus
[00:47] <zequence> raven: It will only start one of them
[00:47] <zequence> not both at the same time
[00:48] <raven> how do i have it start jackdbus over jackd
[00:48] <zequence> raven: The setting for that is at: Setup -> Misc -> Enable D-Bus Interface
[00:49] <zequence> But, once you've made the settings you want, with qjackctl, and you are sure they will always work, you can just start it from the terminal with: jack_control start
[00:49] <raven> i had that set already but i still don't get the pulsejack sync and such in patchage
[00:50] <zequence> You could even make your won desktop file, or script, starting patchage by first starting jackdbus
[00:50] <zequence> raven: Worry about making the module start first. Then worry about patchage
[00:50] <zequence> Is pulseaudio-module-jack installed?
[00:51] <zequence> And sometimes, if you've been starting stopping jack for many times, the module may not initialize. Happens to me sometimes
[00:51] <raven> yes i have it installed
[00:51] <zequence> raven: Make sure jackd is not running now
[00:52] <raven> by running the command you gave me earlier?
[00:52] <zequence> raven: You can check if the module is running by doing: pactl list | grep jack
[00:53] <zequence> you should see a bunch of lines about jackdbus detect and things like that
[00:53] <zequence> raven: First, close all applications that you are using for jack. Then kill all jacks
[00:53] <raven> it is only showing module-jackdbus-detect
[00:54] <zequence> raven: That means the module did not initialize the sink and source
[00:54] <zequence> raven: To kill jacks: killall -9 jackd
[00:54] <zequence> killall -9 jackdbus
[00:55] <raven> okay
[00:55] <zequence> raven: confirm they are all dead, by doing: ps -eo comm | grep jack
[00:55] <zequence> It should return nothing
[00:56] <zequence> If you're still seeing something, kill it
[00:56] <zequence> Then, open qjackctl, and start jack. Confirm that you see the PA sink and source in "Connect"
[00:56] <raven> okay all jack is dead
[00:57] <zequence> If you don't see it, we need to restart pulseaudio
[00:57] <zequence> Just kill it, and it will respawn: pulseaudio -k
[00:57] <zequence> and then, also, restart jack
[00:57] <zequence> ..if needed
[00:58] <raven> brb
[00:59] <raven> back
[01:00] <raven> omg i finally see them thank you
[01:04] <zequence> raven: If you are using "hw:nvidia" as your card ID, you could write a starter script for patchage, like this http://paste.ubuntu.com/5700232/
[01:04] <zequence> And, then, if you want, make your patchage desktop file point to the script
[01:04] <raven> okay ty
[01:06] <zequence> np
[01:09] <raven> zequence i did notice i am still missing one thing in my patchage the jack_capture
[01:09] <zequence> raven: hmdi doesn't have capture, as far as I know
[01:09] <zequence> Ah, that's why I can't start it, of course
[01:10] <zequence> I need to specify output only
[01:12] <raven> okay i might be able to do what i need without it
 i am having some problems with my ViewSonic Monitor. it is acting as if there is no input, when it is enabled.
[17:50] <SunStar> are you sure it hasnt died?
[17:50] <TheBingsta> i am sure, it works on my server. (next to the pc)
[17:50] <SunStar> what video ddriver are you using? what graphics chip?
[17:51] <TheBingsta> is there a way of finding out?
[18:05] <SunStar> in terminal type lspci to see what graphics adapter you have, and launcher menu -> system -> Software Updater -> Settings -> Additional Drivers
[18:11] <TheBingsta> 00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI BeaverCreek [Radeon HD 6530D]
[18:12] <TheBingsta> recommended video driver
[18:13] <SunStar> more than likly, you need the proprietary AMD driver. you can get it in that Aditional Drivers tab in Software Updater or in the Ubuntu Software Center. Package Name: fglrx
[18:14] <SunStar> or from the AMD website
[18:14] <zequence> I'm not so sure
[18:14] <zequence> AMD free drivers are pretty functional
[18:14] <zequence> And proprietary drivers will probably not work on any release after 12.04 (at least it was so until a few months ago)
[18:15] <SunStar> i know HDMI doesnt work without it
[18:15] <zequence> Really? I was even playing HL2 on free drivers last year
[18:16] <SunStar> well at least on mine, the HDMI doesnt function using x.org driver, you need fglrx
[18:19] <TheBingsta> nope didn't work
[18:19] <TheBingsta> and its not hdmi cable.. VGA
[18:21] <zequence> TheBingsta: Sure you have the right resolution for it?
[18:21] <TheBingsta> yes.
[18:21] <TheBingsta> i have tried lower resolutions as well
[18:22] <DarkEra> TheBingsta, you installed the proprietary drivers?
[18:22] <TheBingsta> yes, still nothing.
[18:23] <SunStar> did you restart?
[18:23] <DarkEra> rebooyed to make them work?
[18:23] <DarkEra> rebooted*
[18:23] <TheBingsta> yes.. works on bios but not ubuntu
[18:23] <TheBingsta> it was a restart after using ArandR that mucked it up.
[18:23] <TheBingsta> let me go for another re-boot.
[18:24] <TheBingsta> brb
[18:34] <TheBingsta> hello
[18:34] <TheBingsta> i got the 2nd monitor working.. however now i can't setup dual screen
[18:47] <zequence> I've personally had more problems with dual monitoring using the proprietary drivers
[18:48] <SunStar> dual monitor always worked well for me untill the radeon HD series
[19:58] <FisherMack> Hey hey hey
[20:17] <TheBingsta> re-installing worked
[20:18] <SunStar> re-installing xubuntu?
[20:18] <SunStar> ubuntu studio*
[20:28] <TheBingsta> yer.
[20:37] <FisherMack> Anyone know of a good soundboard app? I searched USC but didn't find anything
[21:11] <Len-nb> FisherMack, I am not sure what a "soundboard" is. Can you describe it?
[21:47] <c4rt0m4nci3n> ola
[21:58] <SunStar> a sub-straight with buttons. each button plays a sound
[21:58] <SunStar> great for using celebrity voices to make prank phone calls
[22:09] <len-1304> SunStar, That sounds like a sampler to me. Specimen does that. It is possible to have different samples for each key. vkeyb would map the keys to the text kb.
[22:10] <len-1304> That is maybe not the most effective way of doing it though.