[01:46] hay [01:58] Hi, is anyone up? I've a quite particular question on how to redirect Mixxx-Master-Output to the internal Microphone. [01:59] I've already outlined the problem here, in the ubuntu- and mixxx-irc. the latter sent me here. [01:59] http://www.mixxx.org/forums/viewtopic.php?f=3&t=6098&p=21265#p21265 [02:29] have you tried the patchbay in qjackctl ? [02:30] there is also #opensourcemusicians [02:31] no, i dont use jack since im on ubuntu 12.04. i just tried asking you guys for the expertise. im looking for a cure on alsa-level if thats possible. [02:32] okay. ill try it there. thank you. [02:32] but if you know about sound in linux id highly appreciate your help and document it in my forum. [02:32] i really want to get into linux audio production. [02:43] @fibz_ not? [02:47] i'm not familiar with Mixx but i have a feeling qjackctl's patchbay will let you pipe the audio from mixx to microphone [02:49] how bad can jack (qjackctl is a jack utensil i suppose) mess up my configuration? [02:50] i haven't had any problems with combining it with pulse and alsa [02:52] cool! but still: i use a bluetooth audio sink. this is said to cause serious trouble with jack. [02:52] (or the other way around...) [03:07] thank you [11:40] Hi, how do I route Mixxx' Master-Output to the internal microphone? [14:24] bonafide: i use JACK [14:24] but, routing the ouput of something to a mic wont work [14:52] maybe you are trying to use a mic with mixxx.. that would be much more likely [14:52] or, maybe you are trying to route audio to a mic ouput as if you had more channels on an internal device [14:52] that wont work either, unless the hardware were to support that, and had multiple channels out [15:19] holstein: I have a bluetooth adapter for the master output and an internal soundcard for headphones, maybe it works with an external soundcard? [15:19] bonafide: no.. it works with bluetooth [15:19] bonafide: alsa will support it as best it can.. and JACK will show routing options [15:20] bonafide: but, trying to route sound output to a mic is not correct [15:20] i feel i am either misunderstanding you, or not getting the full story [15:20] feel free to just back up and state exactly what you are trying to do [15:22] holstein: hm. i want to do djing in mixxx while simoutanously streaming it to a flash-application the browser like soundcloud-live-recording or a videochat. [15:22] i outlined it here: http://www.mixxx.org/forums/viewtopic.php?f=1&t=6108&p=21274#p21274 [15:22] bonafide: i would remove the flash from teh equation [15:23] one thing i might do, since i have a bunch of hardware laying about is.. build a streaming appliance [15:23] then, route to that analog for streaming [15:23] the streaming appliance wouldnt be running JACK [15:23] i would then just use mixx normally on one machine, with the mic running for VO [15:24] then, take a cable and route all of that via an analog connection to the streaming appliance [15:24] otherwise, to do it with one machine, i would want to test streaming independently.. using the pulse-jack dbus [15:24] then, i would just route a mic to mixxx and get that streaming [15:25] *then* introduce whatever bluetooth equipment [15:25] otherwise, you are troubleshooting many many things at once.. and none of the equipment has likely promised JACK, linux or pulseaudio support [15:26] I guess one does not even see mic as input in jack [15:26] I mean output [15:26] shouldnt [15:26] analog connection = mixxx-machines-output via cable to the microphone in of the streaming-machine? [15:27] like this, holstein? [15:27] bonafide: i suggest this because its a work around i used with my firewire device years ago [15:27] bonafide: i used a seperate machine running only pulseaudio and BUTT to stream to icecast.. then, an analog cable from my audio rig from my firewire device [15:28] sound decent. [15:28] i didnt expect it so be so much trouble [15:28] bonafide: ? [15:28] bonafide: does the hardware promise you linux support? [15:29] bonafide: if not, then you are accepting the support role yourself.. and its not always trivial [15:29] bonafide: there are *many* ways to do what you are suggesting. but, you will not be able to route audio outputs to microphones [15:30] for me, it was a matter of simplicity.. i didnt need JACK running to stream, so i didnt use it [15:30] holstein: thank you a lot for your help. the idea with the second machine is very good. i'd like to have a clean setup as well and will rather go for this one than for the one with jack. [15:31] holstein: the hardware is of course not labeled "linux support". [15:32] holstein: when i started the thread, I thought someone will come up with a simple command for alsa. didnt want to discredit your solution. [15:32] bonafide: there is no solutino to routing audio to microphones [15:32] bonafide: you just cant do it [15:32] if i were going to do what you are doing, i might not use JACK at all [15:33] i might just setup a mixer.. route whatever sources to that i want (ipods, phones, tapedecks, whatever) and my microphone.. then, route that to the streaming appliance [15:34] if i dont want to record the audio, i try and not bring it in, or route it through the computer [15:36] I'd like to stream my Mixxxes to various Applications like the the browser (soundcloud recording, videochat) or Skype. [15:36] ^ you would use the included pulse-jack dbus [15:36] pulseaudio shows up as send and recieve.. you route what you like to it [15:36] So. How do I redirect my Master-Output from Mixxx to the Microphone? [15:36] ^ you dont [15:37] and, you shouldnt need to [15:37] you are asking "how to get the audio into the browser?".. not send the audio to a mic [15:37] and, the way you would do that is with the pulsejack dbus [15:37] but, i would expect issues with flash, and suggest a streaming appliance still [15:38] though, im not sure i would use mixxx or jack at all.. [15:38] feel free and check with #opensourcesmusicians [15:40] these are some very nice thoughts. thank you. i think ill just use the hardware workaround. jack is to much of a risk for me. [15:41] bonafide: i really think its ideal not to use it, if its not required [15:41] bonafide: not that JACK isnt awesome :) [15:41] i love it and use it a lot, but if its overhead isnt required... [15:43] I'm quite new to linux-audio. I think, Ill use JACK in a different setup in the future (ardour x jack x mixxx x and some nice hardware parts) but for now im fine with the workaround. [15:44] holstein [15:44] thanks a lot. [15:44] are you here frequently? [15:44] bonafide: sure.. anytime! [15:44] i try and be logged here all the time [15:44] ill come back and tell you about my experience in building it. [15:44] and share it as well in the mixxx forum. [15:44] bonafide: please do let us know.. and if you need other options/suggestions [15:45] i certainly will. really. heartfelt thanks from me again. passing on this kind of knowledge is so important. [15:45] <3 [15:45] see you in a bit [17:53] any word on when the 14.04 beta will be available? I've got a couple of machines I want to upgrade asap [17:54] em: the 14 is 2014.. the .04 is april [17:54] !14.04 [17:54] Ubuntu 14.04 (Trusty Tahr) will be the 20th release of Ubuntu. See the announcement at http://www.markshuttleworth.com/archives/1295 for more info. support in #ubuntu+1 [17:55] em: ubuntu releases, or at least has agreed to release so far, a release every 6 months [17:55] with an LTS (long term support) release every 2 years [17:55] !lts [17:55] LTS means Long Term Support. LTS versions of Ubuntu will be supported for 3 years on the desktop, and 5 years on the server; with the exception of 12.04 (Precise Pangolin), which will be supported for 5 years on the desktop. The current LTS version of Ubuntu is !Precise (Precise Pangolin 12.04) [17:55] 14.04 will be an LTS [17:56] any idea why the volume control for 12.10 was NEVER FIXED??? besides being annoying as all hell it makes ubuntu look really bad, I can't/won't put new users on it because of that. and now users are getting these really annoying warnings about 13.04 being end-of-life-you-must-upgrade... [17:56] em: nothing is "broken" here, friend [17:56] 12.10 is EOL [17:56] !12.10 [17:56] Ubuntu Studio 12.10 Quantal Quetzal is out! Go to http://cdimage.ubuntu.com/ubuntustudio/releases/12.10/release/ to download! [17:56] lol [17:56] its eol now [17:57] hlostein please do not answer any of my questions you have already established yourself as a person who DOES NOT KNOW WHAT THEY ARE TALKING ABOUT [17:57] em: 13.04 is EOL as well [17:57] em: they are factually end of life, friend [17:57] !volunteers | em [17:57] em: The people here are volunteers, your attitude should reflect that. Answers are not always available. See http://wiki.ubuntu.com/IRC/Guidelines [17:57] duh no sh***shutup and let an intelligentt person talk [17:57] em - respectfully suggest you dial down the attitude immediately [17:59] em: i do apologize that you seem to be experiencing some issues thare you are finding frustrating, but i assue you, im only stating facts [17:59] em: 13.04 *is* end of life [17:59] those "annoying" messages are notifications to the same effect.. [18:00] facts that are completly irrelevant to the question being asked!!!! is English a foriegn language for you??? becausee you seem t have severe problems with comprehension [18:00] em: the reason the volume control wasnt "Fixed" in 12.10 is likely becuse it wasnt broken, friend [18:00] em: its likely just an issue with alsa and the support of your particular device [18:01] but, if you would like to speack constructively about current support, i would be glad to help [18:01] speak* [18:02] oops... correction... when I said 12.10 I meant 13.10 but anyone who is knowledgeable would have realiszed that i was talking about the very blatently broken volume control in 13.10 because that is the only version where this problem exists [18:02] em: what is the specific issue? [18:08] i would try and isolate if its an issue with the drivers (alsa) and or kernel version supporting the hardare, rather than the volume control being broken [18:09] either one warrants a bug report.. and thats where i would start.. a bug report relating to my specific hardware case [18:11] either creating one for finding an existing one.. upstream as well, if possible [18:19] @holstein you dont know the difference between a virtual box and a hardware computer.... you also dont seem to know when the 2014 beta is going to be released, you also dont seem to know anything about the very broken volume control in 13.10 so why are you insisting on providing useless non-answers? [18:20] em, support and questions about 14.04 belong in #ubuntu+1 [18:20] @holstein have you ever actually run 13.10??? I am betting that the answer is no.... because if you had run it then you would know what I am talking about without having to ask. [18:20] em: https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule [18:21] ^ that should give you all the dates you need for 14.04 [18:21] cfhowlett thatnks I will try there [18:21] holstein THANK YOU for succeeding in being helpful [18:22] em: sure.. i just dropped "ubuntu 13.10 release schedule" in a search window [18:22] em: what specifically is the issue with your sound control in 13.10? since i dont seem to have the same issues [18:22] okay, fine, but the ubuntu STUDIO does not always track the main release [18:23] ubuntustudio *is* ubuntu.. we only skip one milestone AFAIK [18:24] the problem with the sound control in 13.10 is that the volume control widget/applet on the panel is not clickable and does not function [18:25] you can go upstream with that, since its not related to ubuntustuduio specificially [18:26] em: if you share your audio hardware specs, id be glad to help search for a bug, as i stated above, for your specific hardware [18:27] fine... but there are already a zillion people who have seen it and no doubt reported it. I even seem to recall that it was mentioned in the release notes. there is no point in me duplicating that effort. [18:28] it's been broken on every computer Ive tried it on.... multiple different hardware [18:29] it's even broken inside of virtualbox.... [18:29] !bug | em [18:29] em: If you find a bug in Ubuntu or any of its derivatives, please file a bug using the command « ubuntu-bug » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs. [18:29] em: just file, and share the link, and i'll follow up and confirm it [18:31] @holstein, tell me about yourself, how do you fit in to the eco system? what sort of follow up are you capable of doing on a bug report? [18:32] what is your area of knowledge? [18:32] em: its a community, friend. i would be able to confirm the results, and report on the bug.. i could share on the publically accessible email list and ask for assistance [18:32] em: its a process outlined above that has nothing to do with me [18:33] em: as the link i gave before states, i a volunteer here.. you are welcome to do what you like.. go upstream, go to the devel channel or list [18:34] em: i will assist you getting whatever you need.. thats what i do.. [18:34] yes, that's what I thought, in other words you are like a friendly puppy, all excited about being friendly and helping out, but not actually knowing anything useful. [18:35] em: you are free to search whatever you like or need on me, friend [18:35] em a simple "No thank you" would have sufficed. [18:35] em: i will get you assistance.. if the volume control is broken, you will outline the process, and i will confirm it, and look upstream as needed for asssistance [18:36] em: i assure you, i am not a code contributor.. if you are, or are interested in helping us with code, that would be much appreciated [18:37] thanks, but I really just wanted to find out when the beta is being released [18:37] bye [18:37] em: good luck.. just don spread FUDD [18:37] !beer|holstein, [18:38] drag.. now that guy is saying the volume control is broken.. still [18:38] whatever... [18:38] cfhowlett: rough ;) [18:38] holstein, you're a better man than I am. Thanks for setting the example in the face of - whatever that was. [18:39] cfhowlett: i think its mostly just tech support issues.. folks dont think of this as community support.. its tech support, which is frustrating, typically [18:40] in actually, we have a community here that one could join and fix what they like.. but whatever [18:40] holstein, granted but still no excuse for abuse or a**holery