[00:02] <Doc__> My monitor died so I hooker up a spare...  Now my resolution is way more than the old LCD can handle.  I am running Ubuntu Studio 13.04.  How can I rest to a lower res or reset back to defaults?
[00:02] <Doc__> Thanks so much for any help...
[00:03] <Doc__> btw - I am currently upgrading to 14.04
[00:13] <OvenWerk1> setting manager -> Display ?
[00:19] <Doc__> sorry to say I am not sure....  (been a long time since install
[00:19] <Doc__> upgrade complete
[00:19] <Doc__> i thought is was lightdm
[06:41] <stephen_> n00b here, I am trying to record and playback with ardour and jack, I started jack with QjackCtrl but can't seem to start Ardour?
[13:20] <jws> hey there guys, wondering if someone might have an idea of what my issue could be regarding an audio problem?
[13:26] <zequence> jws: What kind of problem are you having?
[13:28] <jws> just did a fresh install of studio 14.04 and have no onboard sound. HDMI audio is showing through both my 270x's, but the sound from my motherboard is not listed anywhere. It's an asrock 990fx extreme3. I've tried installing alsa-oss, arecord -l list no devices, a cat /proc/asound/cards only lists the hdmi (which I tuned off in alsamixer) - and I'm poking around with dmidecode just to see if something is listed there.
[13:29] <zequence> jws: Sounds like alsa is not recognizing it. I'm pretty sure any configuration or installation is not going to help
[13:29] <zequence> jws: Report a bug, please. In a terminal: ubuntu-bug alsa-base
[13:30] <jws> I'd just think that the 990fx e3 has been out for quite a while now, seems a fairly distributed board..
[13:30] <zequence> jws: Most of those boards have standard chips, and you rarely get problems with those
[13:31] <zequence> jws: Sure you didn't disable it in your computer system settings (BIOS)?
[13:32] <jws> I turned the setting from auto to enabled - which was someone else's suggestion. but I've tried it both ways
[13:34] <zequence> jws: Ok. Sounds like it's a bug with ALSA then. Please report a bug, if you haven't.
[13:34] <jws> I'm wondering if the r9 270's hdmi audio may be conflicting, or if I should just go buy a $20 soundblaster audigy from bestbuy. lol I did report a bug
[13:36] <jws> hdmi audio works fine, but I really don't feel like having my tv hooked up to my computer just to be able to hear what I'm recording. I do a weekly podcast for vertcoin and it's a bit awkward to switch around. lol
[13:37] <jws> I'm hesitant to grab a usb sound solution just because I use a lightsnake xlr to usb and I don't want to cause any unknown issues with that.
[13:39] <zequence> jws: I would install either 13.10 (supported for another 3 months), or 12.04 for production use, if any of those work for you currently.
[13:40] <zequence> ..and check if the bug got fixed later. 14.04.1 comes out in about 6 months, and could have that bug fixed.
[13:40] <jws> honestly, I haven't tried the lightsnake cable on this new install of studio 14.04, but it worked excellently on my old install of 14.04. Hmmm.. think an older distribution may have a chance with the onboard audio as well?
[13:40] <zequence> jws: Ah, so you havent' tried the onboard with any other Linux distro?
[13:41] <zequence> ..or release?
[13:42] <zequence> jws: You could try a live image of an older release and give it a shot
[13:42] <jws> I recently swapped out this motherboard from an asus  m5a78l - that was with my previous install of ubuntu 14.04. Since then no sound. Decided to backup data and do a fresh install then with studio 14.04
[13:42] <jws> on the asus sound was working flawlessly
[13:43] <jws> unfortunately the asus only has room for 1 pcie x16 gpu so I upgraded to have the second card
[13:43] <zequence> Well, different MB all together. Trying an older image is a good way to make sure there isn't a regression in current versions of alsa
[13:43] <zequence> Find out what chip it is
[13:44] <zequence> IF it's a known chip, and it doesn't work, then your MB could be faulty
[13:44] <zequence> Otherwise, perhaps ALSA hasn't started supporting it. And, in that case, you need to turn to them for information and whether you can get it working at all
[13:44] <jws> true. come to think of it, I don't think I got sound working under windowz either, but I didn't throw much effort at it.
[13:45] <zequence> I need to get going. Hope you find out what the problem is
[13:45] <jws> sure.. any recommendations on a pci sound solution? bb has audigy and a few others in stock near me
[13:47] <jws> thanks for the help
[13:57] <zequence> jws: I think most cards are ok. I never use that sort of cards for recording though, only listening. For recording I use something that was made for studio recording - sometimes called semi-pro cards, such as m-audio
[13:58] <zequence> Cheap, but well preforming
[14:47] <dsockwel1`> I've got a pulseaudio device (a source/sink pair) on a linux machine that I'd like to pipe through jack to a particular port on my 7.1 sound card to interface it via patch cables with a windows machine that is too dumb to do anything but use its onboard sound card, and which will probably stay that way.
[14:47] <dsockwel1`> Jack/pulseaudio currently know about the sound card on the Linux machine through ALSA
[14:48] <dsockwel1`> and the one stereo I have set up for system audio through the patch cable works well also.
[14:48] <dsockwel1`> How can jack/pulseaudio find out about the second audio device on the Linux machine?
[14:50] <dsockwel1`> If I can manipulate the headset (that's what the second device is) within jack/patchage/qjackctl I can work out the rest, probably, but currently only PulseAudio sees the thing
[14:51] <dsockwel1`> I seem to understand that JackD needs to have access to the actual hardware, and PulseAudio is only to distribute it to software clients
[14:52] <dsockwel1`> oh - qjackctl will let me select multiple ALSA (i presume) devices. Is this what I need to be doing?
[14:56] <dsockwel1`> or else can simple redirection like this be done inside pulse with maybe a loopback module?
[15:01] <dsockwel1`> i've found http://jackaudio.org/multiple_devices and i suppose i'll just work it out for myself here for anyone who might come back around for the logs
[19:15] <Jordan_U> How can I properly convert a png to a 16 shades of grey bmp? Alternatively, since this is actually being displayed with a microcontroller (to a 16 shades of yellow OLED display), how can I get the pixel data as a simple array of pixels, 2 pixels per byte, that I can easily loop through in my code?
[20:19] <zequence> Jordan_U: Not a lot of graphic artist hanging here usually, but you could try somewhere else, like #gimp
[20:22] <Jordan_U> zequence: Thanks.