[00:10] <Guest79344> I just found out about alt+right click for window resizing. Solves my issue above.
[00:11] <Guest79344> I'm now trying to set up Jack Bridge. It was listed in the Connections dialog of QJackCtrl my first day with Ubuntu Studio, but it is no longer there.
[00:11] <Guest79344> Any ideas?
[00:54] <fieryfennix> [kubuntu 13.04 KDE]   hello all.  a quick question, if i may.  how to add the "run command" box permanently to kde desktop?  not a shortcut, but the box itself?
[14:15] <blazemore> does anyone know of a nice way to dynamically adjust the sample rate of Pulseaudio according to the maximum sample rate of the source file being played? Or should I just leave it on the maximum my DAC supports, and use speex 10 to just resample 44.1k to higher frequencies?
[14:15] <blazemore> For example, if I'm playing a CD, it'd be nice to have it actually setting my DAC to 44.1k, whereas if I'm playing a 96k source file I don't want it downsampled
[14:15] <blazemore> At the moment I have pulse set to 96k the entire time, and it just resamples 44.1k, but that's not ideal
[14:16] <holstein> blazemore: i wouldnt worry about that
[14:16] <blazemore> I'm not using the Ubuntu Studio variant (so no JACK etc), but I was directed here from #Ubuntu in the hope one of you would know
[14:16] <holstein> blazemore: the device should be doing the best it can
[14:16] <holstein> and, you wont hear/notice the difference anyway
[14:16] <holstein> unless you do. then, worry about it
[14:17] <holstein> you can try #opensourcemusicians
[14:17] <blazemore> I think my problem stems from the fact I don't *really* understand how it works. Let me explain what I think is happening
[14:17] <holstein> blazemore: i think the problem is, you dont have a problem ;)
[14:17] <holstein> so, dont make one for yourself
[14:17] <blazemore> My DAC will natively play 44.1k, 48k and 96k (it connects over USB)
[14:18] <holstein> if you are using consumer-grade equipment, its likely not even capable of providing you the fidelity to be able to hear the different between what you are worried about
[14:18] <holstein> the device will be playing back at the rate that linux likely can support, as best it can
[14:18] <blazemore> By default, playing a 96Khz file, Pulseaudio downsamples (using speex 1 by default) to 44.1Khz
[14:18] <holstein> if you are "worried" about it, you can check out JACK, where you can set those rates.. but JACK has its own issues
[14:19] <holstein> !proaudio | blazemore
[14:19] <blazemore> Now, I can set Pulseaudio to do 96Khz, and then the display on my DAC changes to show it's recieving 96Khz, but then that means Pulseaudio is upsampling to 96Khz instead
[14:19] <holstein> blazemore: you shouldnt need to set pulse audio to 96k
[14:19] <blazemore> It's consumer-grade hardware, it's a Fiio E17 (Love it btw)
[14:19] <holstein> blazemore: im not debating your affection fo the device
[14:19] <holstein> nor, am i saying its "crap"
[14:19] <blazemore> Now I'm no mathematitian, but 44.1 doesn't go into 96 :)
[14:20] <holstein> blazemore: sure.. but, can you hear a problem?
[14:20] <blazemore> No but it annoys me
[14:20] <holstein> blazemore: i personally cant hear 44.1 vs 96..
[14:20] <holstein> blazemore: what annoys you?
[14:20] <blazemore> On Windows if I play a 44.1Khz in Foobar it sends 44.1Khz to my DAC. If I play a 96Khz file it displays 96Khz on my DAC
[14:20] <holstein> blazemore: that you push play? and the file plays back at a quality that is acceptable?
[14:20] <blazemore> I just want to replicate that functionality
[14:20] <holstein> blazemore: sure
[14:21] <holstein> blazemore: you can use JACK to do that
[14:21] <blazemore> OK I'll look into it with the resources you already provided :)
[14:21] <holstein> blazemore: otherwise, you cant hear the difference, so i dont see that there is a problem
[14:21] <holstein> plus.. does windows do that?
[14:21] <blazemore> I'm not really interested in a discussion on whether or not higher sampling rates are "worth it", since most people enter into one already having their mind made up
[14:21] <blazemore> holstein: Windows XP does, yes
[14:22] <holstein> even if it actually does, and is not just reporting that, you have to keep in mind, that can be on a hardware driver level
[14:22] <holstein> and, you know who is *actuall* responsible for providing alsa with that information
[14:22] <holstein> actually*
[14:22] <blazemore> Yes on Windows XP I did have to install the ASIO driver from FiiO
[14:22] <holstein> blazemore: im not debating that XP "reports" it is doing that
[14:22] <blazemore> The DAC's display gets updated
[14:22] <holstein> blazemore: but, you wouldnt hear the difference if it were or not
[14:22] <blazemore> I'm not sure where the DAC gets its information
[14:22] <holstein> blazemore: so
[14:23] <blazemore> The thing is, some music I have is only in 96Khz
[14:23] <holstein> blazemore: thats just a UI update.. and again, im just being realistic.. not trying to be combative
[14:23] <holstein> blazemore: so
[14:23] <holstein> blazemore: there is not issues playing the music, correct??
[14:23] <blazemore> If I only do one thing, should I set the resampling algorithm in pulse to speex 10?
[14:23] <holstein> blazemore: does it sound "bad" ?
[14:23] <blazemore> no
[14:23] <blazemore> well
[14:23] <blazemore> sometimes pulse crackles
[14:23] <holstein> blazemore: i mean, you *can* "fix" this
[14:24] <holstein> blazemore: pluse crackles
[14:24] <blazemore> But that's just when Java is open and is entirely unrelated
[14:24] <holstein> blazemore: pulse is doing what it is designed to do
[14:24] <holstein> blazemore: java is working with pulse that is working with alsa to the best of its abilities with the support that is available
[14:24] <blazemore> I sort of just mentioned it in #ubuntu as a quick aside to an existing discussion on Pulseaudio
[14:24] <holstein> blazemore: the vendor likely doenst supply alsa with information
[14:24] <blazemore> Java + pulse is a mess IMO
[14:24] <holstein> blazemore: no
[14:25] <holstein> blazemore: JAVA is a messs
[14:25] <blazemore> Yeah
[14:25] <holstein> pulse is doing what it is designed to do
[14:25] <holstein> and, its not made for high priority audio
[14:25] <holstein> thats why we still use, and need JACK
[14:25] <holstein> but, that is a different conversation
[14:25] <OvenWerks> blazemore: as far as I know pulse will try to set the hw rate to the source rate
[14:25] <holstein> blazemore: anyways.. getting back to the end of my rant
[14:25] <blazemore> I'll admit to not knowing completely what JACK does; I assumed it was a way of routing audio signals between devices and applications
[14:26] <holstein> blazemore: you *can* "fix" this "issue"
[14:26] <blazemore> I don't notice an audible difference
[14:26] <blazemore> If that's the point you're getting at
[14:26] <holstein> blazemore: its all open, and freely available for you to change, or for your vendor to provide support for
[14:26] <OvenWerks> If the application sets the rate to less than the souce file rate that is an application problem.
[14:26] <holstein> blazemore: but, you *will* waste a lot of time "fixing" something that will have literally no benifits to you
[14:26] <OvenWerks> the VLC video player for example will resample internally to 48000
[14:27] <holstein> blazemore: and, what if, at the end of a long process, the actual "issue" is the driver support in alsa?
[14:27] <blazemore> OvenWerks: If the sample rate in /etc/pulse/daemon.conf is set to 44.1Khz, and I play a 96Khz file in Aqualung, Pulse resamples it on-the-fly to 44.1Khz using the algorithm defined in that same file
[14:28] <OvenWerks> If there are more than one audio stream and pulse is already streaming at 44100 then the application will be forced to resample
[14:28] <holstein> if not, it should be utilizing the hardare the best that it can
[14:28] <blazemore> I'd prefer it to upsample than downsample though
[14:28] <holstein> blazemore: why?
[14:28] <holstein> blazemore: either, one could argue, is "bad"
[14:28] <holstein> blazemore: plus, you cant hear any probles either way
[14:28] <OvenWerks> most linux (and I think windows) applications resample on the fly to fit what the OS will allow at that time.
[14:28] <blazemore> Because I paid for a FiiO E17 which supports three different sample rates
[14:28] <holstein> yup
[14:29] <holstein> windows would be doing the same, but could have much better driver support
[14:29] <blazemore> And there's not much point if it's just constantly using one
[14:29] <holstein> blazemore: does the device support those rates in linux?
[14:29] <blazemore> Yes holstein
[14:29] <holstein> blazemore: does the device support linux at all
[14:29] <blazemore> Yes
[14:29] <blazemore> But only if I manually set the sample rate in pulse and then restart pulse
[14:30] <OvenWerks> you can set pulse default rate to 96k if you like.
[14:30] <blazemore> OvenWerks: Exactly
[14:30] <blazemore> That will do, to be honest, and is what I am doing currently
[14:30] <blazemore> I also set resample-method = speex-float-10
[14:30] <holstein> blazemore: so, on the box, and in the documentation, the vendor states "linux support"
[14:31] <holstein> ?
[14:31] <blazemore> checking
[14:31] <holstein> otherwise, the support you are experiencing is just the "magic" or alsa
[14:31] <blazemore> It seems to work
[14:31] <holstein> blazemore: seems?
[14:31] <blazemore> In that, it makes my speakers move air
[14:32] <holstein> blazemore: the audio seems to sound fine to you
[14:32] <blazemore> Their website is slow just waiting
[14:32] <blazemore> On an aside, it really is a lovely amp
[14:32] <holstein> blazemore: if you want to be overly particular about the fidelity, you cannot accept "seems"
[14:32] <blazemore> got a battery and aux in
[14:32] <holstein> you must know, for certain
[14:32] <OvenWerks> the config file is in /etc/pulse/
[14:32] <blazemore> Yes OvenWerks /etc/pulse/daemon.conf
[14:32] <holstein> blazemore: and, the alsa driver might not support the full range of functions on that device
[14:33] <OvenWerks> however, even if you do that, if the application decides to downsample internally to 48k, then pulse will set the hw to 48k
[14:33] <blazemore> OvenWerks: I use mpd, and sometimes aqualung
[14:34] <OvenWerks> pulse has no idea that the apllication has a 96k file to play with it only knows what rate the application wants to send the audio to pulse in.
[14:34] <blazemore> Yes I'm aware of that, I'm assuming here that the application isn't resampling (neither mpd or aqualung do)
[14:34] <holstein> what would i do? use JACK and audacious to set the rate.. test the files to see that i cant tell the difference in the quality... then, relax and use the defaults
[14:35] <holstein> but, i have already done such tests
[14:35] <blazemore> Out-of-the-box it sounds a lot better than the dac/amp on my motherboard anyway, so I am very happy with ootb configuration
[14:35] <holstein> then, i wouldnt make an issue for yourself
[14:35] <blazemore> It's *just* a matter of getting native 96Khz playback when I open a 96Khz file, and 44.1Khz when I play a CD
[14:35] <OvenWerks> The pulseaudio-discuss mailing list might be the best place to find answers then.
[14:36] <OvenWerks> The pulseaudio devs use that list to do their development work as well as answer questions
[14:36] <blazemore> I am not taking this further than this channel, I don't care *that* much
[14:36] <holstein> this is something, that, assuming the driver in alsa can support the 96k of the device, you literally will waste days on this, and only your dog would be able to hear a difference, assuming the speakers and the equipment can produce the audio in that range
[14:37] <blazemore> I was kind of hoping one of you would say "yes blazemore just uncomment the line saying pulse-automatic-resampling in daemon.conf" or something :P
[14:37] <OvenWerks> All known computer IFs reporduce 20 to 20k hz only no matter what rate they use.
[14:37] <holstein> assuming the device can be supported by the alsa driver, you can
[14:37] <blazemore> erm
[14:37] <blazemore> I am talking about sample rate of digital audio, not the pitch of a note
[14:37] <holstein> sure
[14:38] <holstein> but, if the device cant produce the frequencied that would be effected, it literally doesnt matter
[14:38] <blazemore> Anyway, I enjoy wasting silly amounts of time on issues like this
[14:38] <holstein> frequencies*
[14:38] <blazemore> I mean, why else would I use Linux?
[14:38] <holstein> lol
[14:38] <holstein> :)
[14:38] <blazemore> I will come out of this knowing *way* more than I did before about Alsa, pulse and jack, and the nature of digital audio in general
[14:38] <OvenWerks> There are good reasons to use 96k even for 20K max audio, but getting frequency output over 20k is not one of them.
[14:39] <holstein> yup ^^
[14:39] <blazemore> My reasoning is, I have files in 96Khz, and obviously on-the-fly resampling isn't ideal
[14:39] <holstein> why?
[14:40] <blazemore> perhaps I should resample them and save the resampled files
[14:40] <holstein> for listening back, on a system that is covering other audio, i would say playing the file is ideal
[14:40] <blazemore> For a system which is only used to play music?
[14:40] <holstein> blazemore: i would literally push the play button, and deal with it if i hear a problem
[14:41] <blazemore> I ask because I'm considering using my Raspberry Pi, FiiO e17 and mpd to make a neat little remote-controlled jukebox
[14:41] <holstein> blazemore: again, setting the system to 96k can be done several ways, assuming the alsa driver supports the hardware, and, you have a system on which the fidelity would report a noted difference, which as OvenWerks states, still wont be a big deal
[14:41] <blazemore> Yeah I know :)
[14:41] <blazemore> Thanks for the tips and resources
[14:42] <holstein> blazemore: set it to 96k, and give it a listen
[14:42] <OvenWerks> There has been a good discusion about the RPi on the LAU mailing list you may be interested in the archive of that mailing list
[14:42] <blazemore> OK thanks OvenWerks
[14:42] <wachin> Hi all, I would like to change the icon of an application which is mousepad, which is equal to that of gedit
[14:42] <wachin> I searched Google but can not find a solution
[14:42] <blazemore> wachin: Ask in #Ubuntu
[14:43] <blazemore> wachin: What distro are you using? Ubuntu Studio?
[14:43] <wachin> could any of you help me
[14:43] <holstein> wachin: on the desktop? in the menu? are you using XFCE?
[14:43] <wachin> Ubuntu Studio 13.04
[14:43] <wachin> Yes, I use XFCE4
[14:44] <OvenWerks> There are two ways to change that icon
[14:44] <wachin> The icon theme that I use is "ubuntustudio-icon-theme" on synaptic
[14:44] <OvenWerks> in both cases you need to look for the desktop file in /usr/share/applications/
[14:45] <wachin> great, I search now
[14:45] <OvenWerks> (I didn't think we shipped mousepad actually)
[14:45] <holstein> AFAIK, we dont, but the process should be the same
[14:46] <cub> no mousepad is not included in default installation
[14:47] <wachin> OH
[14:50] <wachin> I Found /usr/share/applications/mousepad.desktop
[14:50] <wachin> open this with root
[14:50] <wachin> the file said
[14:50] <wachin> Exec=mousepad %F
[14:50] <wachin> Icon=accessories-text-editor
[14:50] <wachin> Terminal=false
[14:50] <wachin> StartupNotify=true
[14:50] <wachin> Type=Application
[14:50] <wachin> Categories=Application;Utility;TextEditor;GTK;
[14:50] <wachin> MimeType=text/plain
[14:50] <holstein> !paste | wachin
[14:51] <wachin> I think that "Icon=accessories-text-editor" is the image of the icon
[14:51] <wachin> Ups
[14:51] <holstein> wachin: you can see the icon listed there
[14:51] <wachin> Thanks
[14:51] <wachin> OK
[14:51] <holstein> wachin: no worries.. its slow-ish in here.. in #ubuntu that would be an issue
[14:52] <wachin> ok
[17:25] <studionovice> When I start jack - background audio from my browser (chrome) quits - is this expected?
[17:25] <holstein> yup
[17:25] <studionovice> I am assuming its a pulseaudio issue from what I have researched?
[17:25] <holstein> there is no issue really
[17:25] <holstein> you are asking JACK to take over the audio device, so it does
[17:26] <holstein> you should have the pulse sync after that to route what you like, if needed
[17:27] <studionovice> Jack runs completely off alsa, correct? would it be okay to unistall pulseaudio completely from my system - as I don't think it's needed?
[17:27] <studionovice> thanks!
[17:28] <holstein> no reason ot
[17:28] <holstein> to*
[17:28] <holstein> i wouldnt suggest it, unless you are having issues
[17:28] <holstein> you can disable the pulse bridge
[17:28] <holstein> untick the dbus checkbox in qjackctl
[17:29] <studionovice> I'm not seeing that option...
[17:30] <studionovice> Is it on the settings tab of qjackctl
[17:30] <holstein> in setup, under the "misc" tab
[17:31] <holstein> Enable dbus interface
[17:32] <studionovice> Got it.  Can you explain what the Dbus interface actually does? thanks for your help - I appreciate it.  I'm fairly versed in *buntu systems but am trying to setup a home recording studio
[17:32] <holstein> the pulse interface we were talking about
[17:32] <holstein> check out #opensourcemusicans .. handy community :)
[17:33] <studionovice> awesome - will do
[17:34] <studionovice> I just got a lexicon pro alpha interface, and I have a nice midi keyboard too
[17:34] <holstein> i have an omega
[23:18] <angel> i'm here again to ask help about wifi and hotspot
[23:24] <angel> someone to help me