[08:04] <studio-user070> Hi people
[08:04] <studio-user070> i would like somebody help me with guitarix...
[08:04] <studio-user070> it sounds digital and dark
[08:05] <studio-user070> i think is a routing ports problem
[08:05] <studio-user070> i use an scarlett solo
[08:05] <studio-user070> as a usb interface
[17:23] <skoppa> thanx
[21:09] <guysoft42> hey, does anyone know how to work with jack delay?
[21:36] <JackWinter1> guysoft42: jack_iodelay?
[21:37] <studio-user065> hello my dears
[21:39] <JackWinter1> guysoft42: i see, didn't know about jack_dealy, seems similar to jack_iodelay
[21:40] <JackWinter1> 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] <JackWinter1> then it ought to report the real roundtrip latency, not only the one given by samplerate/buffersize/period
[21:43] <studio-user065> 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] <guysoft42> 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] <guysoft42> 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] <guysoft42> JackWinter1, at the moment I have a diffrent problem, jack wont start
[21:48] <JackWinter1> what does it say?
[22:14] <guysoft42> now it says: playback and capture sample rates do not match (48000 vs. 24000)
[22:27] <OvenWerks> guysoft42: are you using the same device for each?
[22:30] <guysoft42> OvenWerks, yes, here is the full output: https://pastebin.com/E7AkxT7S
[22:32] <OvenWerks> It appears jack is not correctly installed. I would suggest using ubuntustudio-controls to do that (install if needed)
[22:33] <OvenWerks> Then maybe a killall -9 jackd jackdbus
[22:33] <OvenWerks>  then try again.
[22:34] <OvenWerks> Jackd appears to have been installed with the gnome sofware installer rather than synapic or apt.
[22:48] <studio-user256> Hi All,
[22:50] <studio-user256> 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] <OvenWerks> studio-user256: close enough.
[22:52] <OvenWerks>  There are only a very few of us... and mostly busy with real life so not much gets done.
[22:54] <OvenWerks> so any help at all would be welcome
[22:55] <studio-user256> 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] <OvenWerks> sakrecoer: is our lead right now, but life has gotten the best of him these days.
[22:56] <studio-user256> 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] <OvenWerks> There is also #ubuntustudio-devel where dev stuff sometimes happens.
[22:58] <studio-user256> 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] <OvenWerks> I do not tink there are any of us much beyond that.
[22:59] <OvenWerks> Basically we take xubuntu (at this point) and set it up for audio and add applications that go there
[23:02] <OvenWerks> 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] <OvenWerks> 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] <OvenWerks>  Also look around for anything a bout Studio that bugs you and make changes.
[23:06] <studio-user256> Ok, will keep an eye on both channels and look for opportunities to participate.
[23:07] <studio-user256> 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] <OvenWerks> There is a new version of ubuntustudio-controls that can set cpufreq settings
[23:11] <studio-user256> Thanks!
[23:11] <OvenWerks> I still need to do some more  work on it
[23:12] <OvenWerks> I prolly spend too much time working on Ardour...
[23:13] <studio-user256> What kind of work on Ardour? Recording or do you mean something else like configuring or programming?
[23:14] <OvenWerks> Most of the current OSC control code is mine these days
[23:15] <studio-user256> Cool what language do you code in?
[23:16] <OvenWerks> Ardour is c++, ubuntustudio-control is python
[23:16] <OvenWerks> I learned c off and on and Ardour was my learn to code c++ tool.
[23:17] <studio-user256> Impressive! I'd say mission accomplished. :)
[23:17] <guysoft42> 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] <OvenWerks> guysoft42: qjackctl seems to set capture and playback separately.
[23:19] <OvenWerks> I do not know if this is just the way jackdbus works or not. I normally do:
[23:19] <OvenWerks> jack_control ds alsa dps capture none dps playback none
[23:20] <OvenWerks>  first to clear whatever is in those.
[23:21] <OvenWerks> That is, I never set the capture and playback devices separately, always just use device
[23:22] <OvenWerks> In the current version of qjackctl, that means not using the "Advanced" tab
[23:50] <guysoft42> OvenWerks, I figured out the commandline optoins
[23:51] <guysoft42> This work: /usr/bin/jackd -dalsa -Phw:0,0   -r48000 -p1024 -n2
[23:51] <guysoft42> This works: /usr/bin/jackd -dalsa -Chw:1,0   -r48000 -p1024 -n2
[23:51] <guysoft42> But  -dalsa -Chw:1,0 and   -Phw:0,0  fail
[23:52] <OvenWerks> guysoft42: That is two different devices so that makes sense
[23:52] <OvenWerks> hw:1 and hw:2 are not in sync
[23:53] <OvenWerks> 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] <OvenWerks> 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] <OvenWerks> The zita variant is better quality SRC and uses less CPU