[08:04] Hi people [08:04] i would like somebody help me with guitarix... [08:04] it sounds digital and dark [08:05] i think is a routing ports problem [08:05] i use an scarlett solo [08:05] as a usb interface [17:23] thanx [21:09] hey, does anyone know how to work with jack delay? [21:36] guysoft42: jack_iodelay? [21:37] hello my dears [21:39] guysoft42: i see, didn't know about jack_dealy, seems similar to jack_iodelay [21:40] if so you need to connect a cable from an output to an input, and then run the program specifying the right ports [21:41] then it ought to report the real roundtrip latency, not only the one given by samplerate/buffersize/period [21:43] I I would like to make my Edirol Fa 66 firewire external sound board to be recognised by UbuntuStudio. Anyone can help me to do that, please? [21:47] JackWinter1, I got a little further since that message, i had a jack server stuck which didnt stop which was why qjackctl was not using the settings I gave it [21:48] JackWinter1, I got a little further since that message, i had a jack server stuck which didnt stop which was why qjackctl was not using the settings I gave it [21:48] JackWinter1, at the moment I have a diffrent problem, jack wont start [21:48] what does it say? === Unit193 is now known as JackFrost [22:14] now it says: playback and capture sample rates do not match (48000 vs. 24000) [22:27] guysoft42: are you using the same device for each? [22:30] OvenWerks, yes, here is the full output: https://pastebin.com/E7AkxT7S [22:32] It appears jack is not correctly installed. I would suggest using ubuntustudio-controls to do that (install if needed) [22:33] Then maybe a killall -9 jackd jackdbus [22:33] then try again. [22:34] Jackd appears to have been installed with the gnome sofware installer rather than synapic or apt. [22:48] Hi All, [22:50] I've been using Ubuntu Studio for about a year and would like to contribute in some way. My day job involves a lot of technical writing and I have some experience in programming nothing too indepth. Contribute page directed me here. This might not be the right forum. If not, can someone direct me? [22:51] studio-user256: close enough. [22:52] There are only a very few of us... and mostly busy with real life so not much gets done. [22:54] so any help at all would be welcome [22:55] Well you guys do well for a small group. Studio is a great distro. I switched from Win10 and have not looked back. [22:55] sakrecoer: is our lead right now, but life has gotten the best of him these days. [22:56] Are there any low hanging fruit that I could pick at to learn the ropes? I am new to the community, to IRC, etc. [22:57] There is also #ubuntustudio-devel where dev stuff sometimes happens. [22:58] Would love to be involved at that level but I am hobbyist programmer at best. Afraid I would need too much hand holding at the start to be of any value. [22:58] I do not tink there are any of us much beyond that. [22:59] Basically we take xubuntu (at this point) and set it up for audio and add applications that go there [23:02] We worked off of the vanilla ubuntu at one time back when gnome2 was a thing. Audio stuff did not like unity when it came out (I hear it has gotten better) and now gnome3 gnome session is a thing. So we have been using xfce which is quite gnome2 like and uses less cpu resources [23:04] Most of us got our start doing testing. But as we have just released and not started doing anything yet... there is not much to test. [23:05] Also look around for anything a bout Studio that bugs you and make changes. [23:06] Ok, will keep an eye on both channels and look for opportunities to participate. [23:07] Only issues I have with Studio is wifi interferes with Ardour but I think that is a hardware issue too many devices on same interrupt maybe? Computer boots up in Powersave but saw that this will be resolved in v17.1. [23:11] There is a new version of ubuntustudio-controls that can set cpufreq settings [23:11] Thanks! [23:11] I still need to do some more work on it [23:12] I prolly spend too much time working on Ardour... [23:13] What kind of work on Ardour? Recording or do you mean something else like configuring or programming? [23:14] Most of the current OSC control code is mine these days [23:15] Cool what language do you code in? [23:16] Ardour is c++, ubuntustudio-control is python [23:16] I learned c off and on and Ardour was my learn to code c++ tool. [23:17] Impressive! I'd say mission accomplished. :) [23:17] ok, i figured out what is going on, if i set jack to playback only it works, if i set it to capture only it works, i fails on duplex [23:19] guysoft42: qjackctl seems to set capture and playback separately. [23:19] I do not know if this is just the way jackdbus works or not. I normally do: [23:19] jack_control ds alsa dps capture none dps playback none [23:20] first to clear whatever is in those. [23:21] That is, I never set the capture and playback devices separately, always just use device [23:22] In the current version of qjackctl, that means not using the "Advanced" tab [23:50] OvenWerks, I figured out the commandline optoins [23:51] This work: /usr/bin/jackd -dalsa -Phw:0,0 -r48000 -p1024 -n2 [23:51] This works: /usr/bin/jackd -dalsa -Chw:1,0 -r48000 -p1024 -n2 [23:51] But -dalsa -Chw:1,0 and -Phw:0,0 fail [23:52] guysoft42: That is two different devices so that makes sense [23:52] hw:1 and hw:2 are not in sync [23:53] The only time using cap and play as different devices works is something like hw:0,1 and hw:1,0 where they are really the same device and use the same clock. [23:56] if you must use two devices... for example internal HDA for playback and a USB mic for input... set one of them up on jackd and use a bridge for the other. The two bridges are alsa_in/alsa_out and zita_ajbridge. [23:56] The zita variant is better quality SRC and uses less CPU