| studiobot | <Go_Diego_Go> I have an issue, when Ubuntu Studio Controls are on, I got sound coming from the laptop's speakers, but not when I plug in my headphones | 01:57 |
|---|---|---|
| OvenWerks | Go_Diego_Go, If you open alsamixer in the terminal (or qasmixer on the desktop) can you turn the speakers down and the headphones up? | 01:58 |
| studiobot | <Go_Diego_Go> @OvenWerks [<OvenWerks> Go_Diego_Go, If you open alsamixer in the terminal (or qasmixer on t …], Yes, I did it from terminal, but still no sound. | 01:59 |
| OvenWerks | Go_Diego_Go: -controls is a work in progress. There are plans to support headphone plugin. | 02:00 |
| OvenWerks | Go_Diego_Go: when you open alsamixer, which controls do you see? | 02:00 |
| studiobot | <Go_Diego_Go> Master, headphones, speaker, pcm, mic, mic boost, s/pdif and beep. | 02:01 |
| studiobot | <Go_Diego_Go> Would you like to see a picture? | 02:01 |
| OvenWerks | that is fine | 02:01 |
| studiobot | <Go_Diego_Go> Master and speaker both have a 00 on the sliders, but headphones have mm | 02:02 |
| studiobot | <Go_Diego_Go> Not sure if that matters. | 02:02 |
| OvenWerks | so the headphone column does it both show the level is up and that the mm should be change to 00 | 02:02 |
| studiobot | <Go_Diego_Go> It shows the volume all the way up, but still mm | 02:03 |
| OvenWerks | if you use the arrow keys to get tto the HP column and press the M key does that help? | 02:03 |
| OvenWerks | MM means mute by the way | 02:03 |
| studiobot | <Go_Diego_Go> @OvenWerks [<OvenWerks> MM means mute by the way], Yes, I assumed that and yes that worked! | 02:03 |
| studiobot | <Go_Diego_Go> But I hear a constant beeping sound | 02:04 |
| studiobot | <Go_Diego_Go> Also with the speakers | 02:04 |
| OvenWerks | That I don't know. just in the phnes? or in the speakers too? | 02:04 |
| studiobot | <Go_Diego_Go> Headphones and speakers | 02:04 |
| OvenWerks | and if you mute the speakers does that help? | 02:04 |
| OvenWerks | does your headset have a built in mic? | 02:05 |
| studiobot | <Go_Diego_Go> No, actually, I just noticed it has to do with my guitar to USB cable that I use to record. I just unplugged and the beeping stopped. | 02:05 |
| studiobot | <Go_Diego_Go> I didn't have a beep on previous Ubuntu releases. | 02:06 |
| OvenWerks | ok | 02:06 |
| OvenWerks | when you plug the guitar back in is it ok now? | 02:06 |
| studiobot | <Go_Diego_Go> No, still beeping on both | 02:07 |
| OvenWerks | -controls needs to detect headphone plug and automaticically make changes. | 02:08 |
| OvenWerks | ok one more thing to try. turn jack off before plugging in phones then turn jack back on. | 02:08 |
| studiobot | <Go_Diego_Go> No sound at all. | 02:11 |
| OvenWerks | That should not be. well anything that uses jack will need to be restarted or reconnected to jack of course. | 02:12 |
| studiobot | <Go_Diego_Go> Yeah, I closed everything and opened it again | 02:12 |
| studiobot | <Go_Diego_Go> Checking alsamixer shows both headphones and speakers at 0 and mm | 02:13 |
| OvenWerks | Thats no help. | 02:14 |
| OvenWerks | I started working on headphone detection... but have found that every computer does it differently. Some have separate level controls and switch that (as your appears to) but these channel names are not always the same | 02:17 |
| OvenWerks | for example, my "speaker" control is called "Front" | 02:17 |
| OvenWerks | I found that others actually switch the jack use on HP detect and use the same control | 02:18 |
| OvenWerks | So if you now use level and M on the hp does get you sound without the oscilation? | 02:19 |
| studiobot | <Go_Diego_Go> Okay, disconnected and closed everything. I restarted jack, opened alsamixer and master, headphone and speaker are mm, but speaker show the slider all the way up. I had left all unmuted and all the way up, for some reason it changed it. | 02:22 |
| studiobot | <Go_Diego_Go> @OvenWerks [<OvenWerks> So if you now use level and M on the hp does get you sound without t …], It's still there. | 02:23 |
| OvenWerks | But with the HP off it goes away? Or the beep was not there in the speakers alone before you inserted the HP? | 02:24 |
| studiobot | <Go_Diego_Go> @OvenWerks [<OvenWerks> But with the HP off it goes away? Or the beep was not there in the s …], Nope, it doesn't go away | 02:24 |
| studiobot | <Go_Diego_Go> The beep is present all the time speakers on and hp off, speakers on and hp on and any other combination haha | 02:25 |
| OvenWerks | wonderful :P | 02:26 |
| OvenWerks | Does the beep change if things are moved around (like moving the computer)? | 02:27 |
| OvenWerks | If not I am wondering if there is an internal loop | 02:28 |
| OvenWerks | Does the pitch of the beep change if you change jack buffer size or periods? | 02:29 |
| OvenWerks | (and apply settings) | 02:29 |
| studiobot | <Go_Diego_Go> @OvenWerks [<OvenWerks> Does the beep change if things are moved around (like moving the com …], Nope, it's always the same | 02:29 |
| studiobot | <Go_Diego_Go> @OvenWerks [<OvenWerks> Does the pitch of the beep change if you change jack buffer size or …], Let me check | 02:29 |
| OvenWerks | I should ask if the beeping is a constant tone or a bunch of beeps in a row | 02:30 |
| studiobot | <Go_Diego_Go> Constant tone at about 55bpm | 02:33 |
| OvenWerks | lets try: cd /tmp && wget http://jackaudio.org/downloads/adevices.sh && bash ./adevices.sh |pastebinit | 02:35 |
| OvenWerks | That should all be on one line in a terminal. | 02:35 |
| studiobot | <Go_Diego_Go> @Go_Diego_Go [Constant tone at about 55bpm], Possibly a b or a b flat lol. | 02:35 |
| OvenWerks | it should give to a url of a paste I can look at | 02:37 |
| studiobot | <Go_Diego_Go> Okay, one moment | 02:37 |
| studiobot | <Go_Diego_Go> Before I do that, I changed the periods to 15 cable is connected, no beep, but no sound from guitar (cable) | 02:37 |
| OvenWerks | 15 is a bit odd :) and drastic | 02:38 |
| studiobot | <Go_Diego_Go> Never mind, it's still there | 02:38 |
| studiobot | <Go_Diego_Go> Same pitch and same tempo | 02:38 |
| OvenWerks | I meant if the buffer size goes from 1024 to 512 or 2048 | 02:38 |
| OvenWerks | ok, so not feed back it seems. | 02:39 |
| studiobot | <Go_Diego_Go> @OvenWerks [<OvenWerks> lets try: cd /tmp && wget http://jackaudio.org/downloads/adevices.sh …], I'll do this | 02:39 |
| studiobot | <Go_Diego_Go> http://paste.ubuntu.com/p/jJ4pjhznfj/ | 02:41 |
| OvenWerks | Ok, next :) jack_lsp -c | 02:45 |
| OvenWerks | opps... | 02:45 |
| studiobot | <Go_Diego_Go> Opps? | 02:45 |
| OvenWerks | jack_lsp -c |pastebinit | 02:45 |
| studiobot | <Go_Diego_Go> http://paste.ubuntu.com/p/8JG7HdXv5K/ | 02:46 |
| OvenWerks | So you are listening to your guitar and a keyboard at the same time | 02:48 |
| OvenWerks | it looks like the guitar is direct and you have an MPKmini (24 keys?) | 02:49 |
| OvenWerks | That should be ok | 02:49 |
| studiobot | <Go_Diego_Go> Yes, the keyboard's not a problem. If I unplug it the beeping is still there. If I unplug the guitar the beeping stops. If I just plug the guitar there's a beep. If I just plug the MPKmini there's no beep. | 02:49 |
| studiobot | <Go_Diego_Go> @OvenWerks [<OvenWerks> That should be ok], Yes, it used to work fine on previous releases. | 02:50 |
| OvenWerks | When you say plug the guitar, do you mean the 1/4 jack or the USB? | 02:50 |
| studiobot | <Go_Diego_Go> It's a 1/4 (guitar part) to USB cable (connects to pc, duh lol) | 02:50 |
| OvenWerks | And where do you plug you headphones into? The computer or the usb? | 02:51 |
| OvenWerks | (I think the computer) | 02:51 |
| studiobot | <Go_Diego_Go> It's this one https://www.alesis.com/products/legacy/guitarlink | 02:51 |
| studiobot | <Go_Diego_Go> The computer | 02:51 |
| studiobot | <Go_Diego_Go> Wait, the description of the cable say it outputs 44.1 kHz, but jack is running on 48, could that be it? | 02:52 |
| OvenWerks | I was just about to ask... | 02:52 |
| studiobot | <Go_Diego_Go> Let me see | 02:53 |
| OvenWerks | Alesis has bad engineers :P | 02:54 |
| OvenWerks | zita-a2j does not check the device sample rate so it would try to use 48k | 02:55 |
| studiobot | <Go_Diego_Go> Okay, beep chaged to about 300bpm and it seems like it's an A, not a B anymore | 02:56 |
| studiobot | <Go_Diego_Go> It's not as constant tho, it seems like every now and then it skips a beat... kinda like an xrun | 02:56 |
| OvenWerks | also, your guitar to usb says it has an output which it obviously doesn't | 02:56 |
| studiobot | <Go_Diego_Go> Yeah, it doesn't | 02:57 |
| OvenWerks | But the chip inside does... | 02:57 |
| studiobot | <Go_Diego_Go> Patchage shows input and output for the cable, but when I used qjackctl it didn't, it would just show an input | 03:00 |
| OvenWerks | how did you use qjackctl? | 03:01 |
| OvenWerks | (qjackctl is still available if all else fails) | 03:01 |
| studiobot | <Go_Diego_Go> When I worked with qjackctl in order the cable to show up I would run alsa_in -d hw:01 | 03:01 |
| studiobot | <Go_Diego_Go> Or something along those lines | 03:01 |
| OvenWerks | so similar but using alsa_in instead of zita-a2j | 03:02 |
| OvenWerks | well set -controls to turn jack off and try setting it up with qjackctl | 03:04 |
| studiobot | <Go_Diego_Go> Doing just that right now haha | 03:04 |
| OvenWerks | qjackctl is now in Audio Production->Audio Utilities | 03:04 |
| studiobot | <Go_Diego_Go> Capture open error: Device or resource busy | 03:05 |
| studiobot | <Go_Diego_Go> I'm assuming it could have a different hw:? | 03:05 |
| OvenWerks | hw:device | 03:05 |
| OvenWerks | or hw:2 | 03:06 |
| OvenWerks | hw:1 is you keyboard | 03:06 |
| OvenWerks | but if you use hw:Device it should work whatever it ends up being | 03:06 |
| studiobot | <Go_Diego_Go> ALSA lib pcm_hw.c:1822:(_snd_pcm_hw_open) Invalid value for card … Capture open error: No such device | 03:07 |
| studiobot | <Go_Diego_Go> It's showing up in Pavucontrol, which it shouldn't | 03:07 |
| studiobot | <Go_Diego_Go> Or should it? | 03:07 |
| OvenWerks | if you have turned jack off in controls then it should show up in pavucontrol | 03:07 |
| studiobot | <Go_Diego_Go> @OvenWerks [<OvenWerks> if you have turned jack off in controls then it should show up in pa …], Oh okay, yes, I did that | 03:08 |
| OvenWerks | turning jack off in controls reverts the system to stock | 03:08 |
| OvenWerks | (easier to trouble shoot) | 03:08 |
| OvenWerks | using hw:0 hw:1 etcis mostly no longer used because the same device may be a different number each boot. hw:name should stay the same. | 03:10 |
| OvenWerks | on your system you have hw:PCH (internal) hw:mini (keyboard and hw:Device guitar. | 03:11 |
| studiobot | <Go_Diego_Go> @OvenWerks [<OvenWerks> using hw:0 hw:1 etcis mostly no longer used because the same device …], Oh interesting, before I would always used the same number without any issue at all. | 03:12 |
| OvenWerks | just luck, some systems are more stable than others | 03:12 |
| OvenWerks | in this case you were pluging and unplugging things and so the keyboard and the guitar got switched | 03:13 |
| studiobot | <Go_Diego_Go> Ohh okay, I see | 03:14 |
| studiobot | <Go_Diego_Go> Got this with hw:Device … Capture open error: Device or resource busy | 03:14 |
| studiobot | <Go_Diego_Go> @Go_Diego_Go [ALSA lib pcm_hw.c:1822:(_snd_pcm_hw_open) Invalid value for card … Capture open er …], I had gotten this because I had typed it all lowercase | 03:15 |
| OvenWerks | ps x |grep zita | 03:15 |
| OvenWerks | does that show a process other than the grep? | 03:15 |
| studiobot | <Go_Diego_Go> 14741 pts/3 S+ 0:00 grep --color=auto zita | 03:15 |
| studiobot | <Go_Diego_Go> That's all it's showing | 03:15 |
| OvenWerks | so we need the: cd /tmp && wget http://jackaudio.org/downloads/adevices.sh && bash ./adevices.sh |pastebinit again | 03:16 |
| OvenWerks | That will show what is hanging on to the Device | 03:16 |
| studiobot | <Go_Diego_Go> http://paste.ubuntu.com/p/wyx6kBgMBP/ | 03:16 |
| OvenWerks | pulse wierd | 03:17 |
| OvenWerks | so in pavucontrol Configuration tab set the Device to the profile called "Off" | 03:18 |
| OvenWerks | then try using alsa_in again | 03:19 |
| studiobot | <Go_Diego_Go> So dumb, I could have checked that, I didn't think of it. It worked. | 03:19 |
| studiobot | <Go_Diego_Go> Wait, let me check the beep | 03:19 |
| studiobot | <Go_Diego_Go> No beeping just a regular B sine wave/buzz sound | 03:20 |
| OvenWerks | I notice it has moved back to hw:1 again and the keyboard is gone. | 03:21 |
| studiobot | <Go_Diego_Go> Which is something I've always had, I guess because of the guitar jack or the usb itself. | 03:21 |
| studiobot | <Go_Diego_Go> I'm guessing Controls somehow chops that signal and makes it sound like a beep? | 03:21 |
| OvenWerks | guitars always pick up some hum. it should change when you handle the strings | 03:21 |
| studiobot | <Go_Diego_Go> Yes, it does, I put a gate and it's taken care of | 03:22 |
| OvenWerks | normally, zita-a2j gives better quality than alsa-in... but I guess in this case. | 03:23 |
| OvenWerks | so did you use alsa to connect the mini to the synth input? | 03:24 |
| OvenWerks | does starting a2jmidid -e in a terminal bring the tone back? | 03:24 |
| * OvenWerks would like to know what was causing your beep... | 03:25 | |
| studiobot | <Go_Diego_Go> Oh that was another problem I had with qjackctl, I was never able to use the MPKmini because it would only show on the alsa tab, not the midi. | 03:26 |
| OvenWerks | a2jmidid -e & | 03:26 |
| OvenWerks | then it will show up | 03:26 |
| studiobot | <Go_Diego_Go> Yup, it's there and no beep just the regular hum from the guitar. | 03:27 |
| studiobot | <Go_Diego_Go> My guess the beeping was just the regular hum chopped up, oscillating or something. | 03:28 |
| OvenWerks | And pluging the headphones in and out works? | 03:28 |
| OvenWerks | (it should be controlled by pulse in this case) | 03:28 |
| studiobot | <Go_Diego_Go> Yes, it's working too | 03:28 |
| OvenWerks | So we still have some work to do in -controls :( | 03:29 |
| studiobot | <Go_Diego_Go> Is there anything I can send? Like a log or something? | 03:29 |
| studiobot | <Go_Diego_Go> Anything that could help you guys identify the issue. | 03:29 |
| OvenWerks | The headphones I can figure out... at least for your machine and mine :) | 03:30 |
| studiobot | <Go_Diego_Go> I must say that this is a cheap HP computer and I've had a lot of problems with its drivers and Ubuntu/Linux | 03:30 |
| studiobot | <Go_Diego_Go> So it could be related to that | 03:30 |
| OvenWerks | could be. what command line did you use for alsa_in? | 03:31 |
| studiobot | <Go_Diego_Go> alsa_in -d hw:Device | 03:32 |
| studiobot | <Go_Diego_Go> But Pulse picked it up before jack and had to turn it off (what you told me). Before if jack was running Pulse wouldn't pick it up, it'd go straight to jack. | 03:33 |
| OvenWerks | I was just wondering what sr, period size, period number you were using. | 03:35 |
| OvenWerks | but obviously default | 03:35 |
| OvenWerks | default sr is same as jack and the others don't say but I would assume they are the same, the man page says the buffer size has to be at least the same size as jack, but may be higher | 03:37 |
| OvenWerks | with zita-a2j it is quite normal to use a lower buffer size than jack. | 03:38 |
| OvenWerks | I am wondering if the problem was that the guitar playback was being used. | 03:38 |
| studiobot | <Go_Diego_Go> Nope, I actually change it because with the default settings the latency is too high. I actually use this settings: … Realtime checked … Frames: 256 or 512 … Periods: 2 … Port Maximum: 128 … Force 16bit checked … Latency result: 11.6msec | 03:39 |
| studiobot | <Go_Diego_Go> @Go_Diego_Go [Nope, I actually change it because with the default settings the latency is too …], Sorry and with sample rate 48, I'd get 10.7msec, slightly better so that's why I used that one. | 03:40 |
| OvenWerks | yup, I was talking about alsa_in though. which from your command above you don't set | 03:41 |
| studiobot | <Go_Diego_Go> Ohh sorry, I still don't understand a lot of this, so I thought you meant qjackctl settings | 03:41 |
| OvenWerks | So it would follow whatever you use for jack | 03:41 |
| studiobot | <Go_Diego_Go> I think that the humming sound also comes from the computer itself because when the laptop's charger is connected I get another extra hum lol | 03:43 |
| OvenWerks | It is possible to use 44k1 for the guitar and 48k for internal with alsa_in, but I don't think that would help as the latency on the guitar will be more noticable than with keyboard. | 03:43 |
| studiobot | <Go_Diego_Go> But that's something that's always happened and I've managed to solve with a gate. | 03:43 |
| OvenWerks | I start to notice it with the buffer set to 256 | 03:44 |
| OvenWerks | I like 128 or lower | 03:44 |
| OvenWerks | but many internal audio cards (HDA/PCH) will not even start in jack at 64 | 03:44 |
| OvenWerks | Can we try some thing? | 03:47 |
| studiobot | <Go_Diego_Go> Sure | 03:47 |
| studiobot | <Go_Diego_Go> I was actually going to ask you if I should try with 128 | 03:47 |
| OvenWerks | 128 should be fine. see if it pops or anything. | 03:47 |
| studiobot | <Go_Diego_Go> Okay, I'll try | 03:49 |
| OvenWerks | in another terminal: zita-j2a -d hw:Device -r 44100 -p 128 | 03:49 |
| OvenWerks | and see if the beep shows up. | 03:49 |
| studiobot | <Go_Diego_Go> @OvenWerks [<OvenWerks> in another terminal: zita-j2a -d hw:Device -r 44100 -p 128], With jack running? | 03:50 |
| OvenWerks | with you setup the way it is using qjackctl and alsa_in | 03:50 |
| studiobot | <Go_Diego_Go> Okay, wait for some reason jack is not starting | 03:51 |
| OvenWerks | 128 may be too low | 03:51 |
| studiobot | <Go_Diego_Go> Yeah, it was that | 03:51 |
| OvenWerks | if all else fails try killall -9 jakcd jackdbus | 03:52 |
| OvenWerks | (my spelling is bad) | 03:52 |
| OvenWerks | The 128 in my line above may need to be 256 then. | 03:53 |
| studiobot | <Go_Diego_Go> @OvenWerks [<OvenWerks> in another terminal: zita-j2a -d hw:Device -r 44100 -p 128], Tried 128 and 256, beeping sound is there. It's what I was thinking, same pitch as the hum from the alsa_in | 03:54 |
| OvenWerks | Oh... I think I know the problem. try adding an -L at the end of that line. | 03:54 |
| OvenWerks | so zita-j2a -d hw:Device -r 44100 -p 128 -L | 03:55 |
| studiobot | <Go_Diego_Go> The terminal showed this "Detected excessive timing errors, waiting 10 seconds." | 03:55 |
| OvenWerks | it may still beep | 03:55 |
| OvenWerks | maybe it needs 256 | 03:56 |
| studiobot | <Go_Diego_Go> Still beeping with both 128 and 256 | 03:56 |
| OvenWerks | right, so the problem is using the output side of the chip tha goes no where but has leads close enough to cause a loop | 03:57 |
| studiobot | <Go_Diego_Go> Ohh okay, so it's the cable itself | 03:58 |
| OvenWerks | can you replace your alsa_in line (means stop the alsa_in) with: | 03:58 |
| OvenWerks | zita-a2j -d hw:Device -r 44100 -p 256 -L | 03:59 |
| studiobot | <Go_Diego_Go> zita-j2a still running or do I stop and restart? | 03:59 |
| OvenWerks | stop that one. | 03:59 |
| OvenWerks | we only want one running | 03:59 |
| studiobot | <Go_Diego_Go> Can't open ALSA capture device 'hw:Device'. | 04:00 |
| OvenWerks | I want to make sure it is not zita-ajbridge itself. | 04:00 |
| OvenWerks | killall -9 alsa_in | 04:00 |
| OvenWerks | then try again | 04:00 |
| studiobot | <Go_Diego_Go> alsa_in: no process found | 04:00 |
| studiobot | <Go_Diego_Go> After that tried again and still same result | 04:01 |
| OvenWerks | without the -L? | 04:01 |
| studiobot | <Go_Diego_Go> Warning: only 1 channels are available. … Starting synchronisation. | 04:02 |
| OvenWerks | any beep? | 04:02 |
| studiobot | <Go_Diego_Go> No beep, but no sound | 04:02 |
| OvenWerks | the port you need to connect will have a different name] | 04:03 |
| studiobot | <Go_Diego_Go> Warning: only 1 channels are available. … Starting synchronisation. … Detected excessive timing errors, waiting 10 seconds. … Starting synchronisation. … Detected excessive timing errors, waiting 10 seconds. … and so on. | 04:03 |
| studiobot | <Go_Diego_Go> wait, let me try with 128 | 04:03 |
| studiobot | <Go_Diego_Go> I have sound, but 128 distorts the sound every now and then, it's like if it had a flanger/chorus effect for some seconds | 04:04 |
| studiobot | <Go_Diego_Go> Warning: only 1 channels are available. … Starting synchronisation. … Starting synchronisation. … Starting synchronisation. … Detected excessive timing errors, waiting 10 seconds. … Starting synchronisation. … Starting synchronisation | 04:04 |
| OvenWerks | but no beep. | 04:04 |
| studiobot | <Go_Diego_Go> No beep | 04:05 |
| OvenWerks | OK, so the problem with the beep is the output circuit for sure | 04:05 |
| studiobot | <Go_Diego_Go> And the sound quality is much better, clearer, except when the flanger/chorusy effect is "on" lol | 04:05 |
| OvenWerks | can you: cat ~/.log/autojack.log |pastebinit | 04:06 |
| OvenWerks | so when you were using -controls to run jack was sound clearer there as well (aside from beep) | 04:07 |
| studiobot | <Go_Diego_Go> http://paste.ubuntu.com/p/VvG7S7wwrx/ | 04:07 |
| studiobot | <Go_Diego_Go> @OvenWerks [<OvenWerks> so when you were using -controls to run jack was sound clearer there …], Actually no, it was very similar to alsa_in | 04:09 |
| studiobot | <Go_Diego_Go> But I could try and compare again now, if you'd like | 04:09 |
| studiobot | <Go_Diego_Go> Getting lots of this though … Starting synchronisation. … Detected excessive timing errors, waiting 10 seconds. | 04:10 |
| studiobot | <Go_Diego_Go> @Go_Diego_Go [Getting lots of this though … Starting synchronisation. … Detected excessive timing …], Could that be related to the computer's power? I don't have a lot of RAM. | 04:11 |
| OvenWerks | Yeah, but I am not seeing that in the log, just the Warning: only 1 channels are available. | 04:11 |
| studiobot | <Go_Diego_Go> Yeah, it's not showing | 04:11 |
| OvenWerks | That could be I am only seeing either stdout or stderr | 04:11 |
| OvenWerks | I can't see anyway, I can easily fix this problem in -controls | 04:12 |
| OvenWerks | I expect I will have to fully rewrite a good chunk of it | 04:13 |
| studiobot | <Go_Diego_Go> But that would be for this case in particular? | 04:13 |
| OvenWerks | It appears we need a configuration for each device rather than just for jack master. | 04:14 |
| OvenWerks | yes that is for this case, but I am sure your case is not unique | 04:14 |
| OvenWerks | I need something like pavucontrol has with profiles for each device. | 04:15 |
| Eickmeyer | Big oof. | 04:16 |
| studiobot | <Go_Diego_Go> Ohh I see, yeah I guess I won't be the onnly one | 04:16 |
| OvenWerks | except more complex | 04:16 |
| OvenWerks | I was working on channel count, after that I will work on headphone/speaker switching | 04:17 |
| OvenWerks | then maybe I can deal with per device config | 04:18 |
| studiobot | <Go_Diego_Go> Well, if I'll gladly help with anything I can. I don't think it's much but at least testing lol | 04:19 |
| Eickmeyer | @Go_Diego_Go: Believe it or not, this is a case where testing goes a long, long way. We wish we had more testers before. | 04:20 |
| OvenWerks | you have been quite a help actually. I have learned some things I could have only learned by going out and buying what you have. | 04:20 |
| studiobot | <Go_Diego_Go> Oh man, that's nice! I love Ubuntu Studio, I've tried many media oriented distros, but Ubuntu Studio is the one I've felt more consistent and complete, and also the support is great. I've always gotten help from this chat. | 04:21 |
| * OvenWerks is going off to be with his Yf | 04:24 | |
| studiobot | <Go_Diego_Go> Thank you for the help! Let me know whenever you need testers of some kind! | 04:24 |
| Eickmeyer | @Go_Diego_Go: Would it be ok if I ping you when we need you to test your hardware against any fixes we might have? | 04:25 |
| studiobot | <Go_Diego_Go> @Eickmeyer [<Eickmeyer> @Go_Diego_Go: Would it be ok if I ping you when we need you to test …], Yes, it's okay, I'll get the Telegram notification | 04:27 |
| Eickmeyer | Perfect. :) | 04:28 |
| studiobot | Héctor Chela was added by: Héctor Chela | 05:44 |
| universestudios | Hello | 10:21 |
| universestudios | ubuntu studio 19.04 LTS its available? | 10:22 |
| studiobot | <Sakrecoer> Thanks for the info regarding calf plugins ovenwerks and eickmeyer :) | 15:03 |
| Universe_Studios | hi | 19:55 |
| Universe_Studios | exist Ubuntu Studio 19.04 LTS? | 19:56 |
| Universe_Studios | ?? | 19:57 |
| Eickmeyer | !lts | Universe_Studios | 20:01 |
| ubottu | Universe_Studios: LTS means Long Term Support. LTS versions are supported for 5 years on the desktop and server. The latest LTS version of Ubuntu is !Bionic (Bionic Beaver 18.04). Ubuntu !flavors may have different support durations, check their release notes for information. | 20:01 |
| Universe_Studios | #ubottu tanks for you explications | 20:03 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!