[00:29] buenas madrugadas [00:29] soy nuevo en Ubuntu [03:46] configure P.A.M. [03:57] what to do before configure jack configure P.A.M.? [11:09] Something wrong with Jack .. nothing except 2 sources and 2 outputs show up [11:10] All I know I did was shutdown, connect USB cables into different ports and restarted [11:10] I restart the system again. This account is on irccloud so I have persistence over reboots [11:19] after reboot qsynth shows up in the patchbay [11:23] I have snapshots by Timeshift that I can use to revert [11:23] patchage and carla are showing different views [11:24] I guess this confusion is due to different USB ports being used [11:36] seems it got sorted, but I don't know what I did [11:36] enough restarting things perhaps [11:37] now making a backup-point [11:49] Whoaaa.. Now the touchpads that are usually connected to percussion instruments in fluidsynth is connected to 2 sounds. The percussion sound, but also some other instrument is playing when a pad is hit and hit and held [11:53] I'm also having midi issues. :( [11:53] I can't seem to get my control surface to work with ardour anymore [11:54] I dunno where this behavior is controlled... in fluidsynth or in the midi controller. So to re-cap it for some reason hitting a pad on the midi controller triggers the percussion it _is_ supposed to, but now for some reason the pads are mapped also to playing a certain note of the instrument that the keys of the keyboard are set to. [11:54] so everything is in fluidsynth? [11:59] Why don't I remember how to do this? It's Ctrl-Middle Click to put Ardour into learning mode, right? [12:03] ok. restarting qsynth solved it [12:04] Oh, you need to enable MIDI first in preferences. I totally remember that. :) [12:06] Hmm, I can't seem to get the fader to work with the knob. [12:07] Well, it works for the master but not the rest. Maybe I can manually tweak that in Ardour's config file. [12:07] Another day. This is good enough for now. :) [13:00] OvenWerks: https://paste.ubuntu.com/p/hhBT3dY2Vs/ [13:00] crashed again even after the reboot [13:00] wonko@deepthought:~/.log/jack$ ps -x | grep autojack [13:00] 6613 ? S 0:00 /usr/bin/python3 -u /usr/bin/autojack >~/.log/autojack.log 2>&1 < /dev/null & [13:00] 31990 pts/1 S+ 0:00 grep --color=auto autojack [15:04] wonko: ok, so I am not sure what crashed. There is only one daemon running (good) [15:06] wonko: that log file is strange. the second to last startup looks very normal, but the last one looks like it is missing things. [15:12] wonko: it looks to me like the USB audio device was disconected and reconnected? Did the machine go to sleep? (laptop lid close or screen blnk?) [15:40] wonko: I would suggest setting your screen blanker to not sleep. [15:41] expect to restart jack after a lid close [15:42] I do not remember if you are using the ubuntustudio iso or studio on top of kubuntu so I won't try to tell you how to change those settings :) [15:42] I think it is different for each [15:44] 21M Sep 15 23:00 jackdbus.log [15:45] thats a bit big to go searching through [15:56] I think we can actually use logrotate. It can be set to daily but run each time the daemon is started. If it is started more than once a day, it will still only work once and if the session is left open (as I do) it may be a while before it gets rotated. I could even have it run at each jack start. [16:31] This is a desktop, not a laptop and I have all the power setting set to not sleep (except to turn off the display) [16:31] Usb wonkiness wouldn't surprise me though if that were the case. [16:31] I have long (3m) usb extension cables and they might be causing issues. [16:32] I've drilled some new holes for cable routing so I may be able to get away with shorter extensions. I should try that. [16:32] I know mass storage really doesn't like them. [16:32] although to be fair it all worked flawlessly on the old 18.04 mess. :) [16:32] also: fresh install from the ubuntu studio iso [16:33] other odd things to note: sometimes unlocking the desktop behaves oddly [16:33] wonko: RE: unlocking the desktop: should be fixed in 19.10. [16:33] usually, I type in my password, the screen goes black like it's going to unlock to the desktop and then comes back to the lock screen. second try works. [16:33] ah, ok, so known issue then [16:34] Yeah, it was a conflict between xscreensaver and xfce4-screensaver. [16:34] And light-locker. [16:34] light locker is pretty much depricated. [16:35] ok, then I'll ignore that. :) [16:36] reminds me of 18.04 which was a mess of gnome and xfce and I think I had like three different screen savers fighting each other. :) [16:36] hey, while you're alive, I'm trying to build ray session but it's giving me fits [16:37] lrelease: could not exec '/usr/lib/qt5/bin/lrelease': No such file or directory [16:37] still haven't figured out what package I need to install to provide that [17:28] wonko: Did I forget to stick Raysession in the backports? (btw, Launchpad builds everything for the repos, so it's probably your system config). [17:31] wonko: Raysession will be in the backports within the hour, so don't bother. :) [18:12] Better answer. 😁 [18:31] I purge xfce4-screensaver and lightlocker and just go with xscreensaver. [22:00] I just use the power manager... blank after 15M, turn off after 30M, no lock [22:01] system sleep mode = never [22:31] yeah, same here except I do have lock [22:31] I have a 2 year old. An unlocked and unsupervised computer is a dangerous thing. :) [22:32] my youngest just turned 14 :0 [22:32] My oldest is 23. There is a bit of a gap there. :) [22:35] about the same here, my oldest is 33 [22:36] installed ray sessions [22:36] now what? :-D [22:36] ask Eickmeyer, I haven't ever used a session manager :) [22:37] I've only ever use Claudia which combines a session manager with patchbay so it's kinda intuative how they work together. [22:45] Ok, I've most got it figured out [22:45] it doesn't want to delete the "default" routes though from when jack started [23:12] wonko: in -controls the pulse ports to connect to can be set to "do not connect..." [23:13] Any jack aware client _should_ have such an option some where in the settings