Re: [LAD] User eXperience in Linux Audio
2015-04-21 8:21 GMT+02:00 Gordonjcp gordon...@gjcp.net: On Tue, Apr 21, 2015 at 08:16:05AM +0200, Thijs van severen wrote: We need to be aware of the fact that most people on this list are devs and therefore do NOT represent the average user In other words : I dont like splash screens so i'm not going to implement one is (IMHO) a very very wrong attitude. The same goes for any other feature I still don't get why splash screens are a good thing. I don't want a big modal picture blotting out the middle quarter of the screen just because an app is waiting to start up. Maybe there are other things I'd like to do with the computer while I'm waiting. i dont think it has to be modal, and i'm also curious what other thing you will be doing in those 3-5 sec that the splash is there surprise me :-) -- Gordonjcp MM0YEQ ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev -- follow me on my Audio Linux blog http://audio-and-linux.blogspot.com/ ! ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] User eXperience in Linux Audio
Hi Harry Just wondering where you got your inspriation for the above list? There are of course numerous documents on ui design .Something like this http://www.ambysoft.com/essays/userInterfaceDesign.html (but there are better documents that go into the details. I just i cant find them right now :-) I,m not sure if these guidelines explicitly mention splash screens, but i'm pretty sure that getting feedback from the app about what it is doing is high on the list We need to be aware of the fact that most people on this list are devs and therefore do NOT represent the average user In other words : I dont like splash screens so i'm not going to implement one is (IMHO) a very very wrong attitude. The same goes for any other feature Keep it simple and dont use 'alt-b' for what the rest of the world knows as 'ctrl-c' because you think thats better. It's not Anyway, thumbs up for this effort ! Grtz Thijs Op 19-apr.-2015 00:40 schreef Harry van Haaren harryhaa...@gmail.com: Hi All, As promised just at the closing ceremony of LAC, an email opening the discussion of User Experience on Linux Audio. To all Developers, please use this as a checklist and consider supporting each item. It will improve the user experience. 1: Splash Screen If an app takes more than one quarter of a second to open, use a splash screen to give feedback. Feel free to contact me directly to collaborate on a splash screen graphic if necessary. Ensure the splash is shown immediately, before lengthy operations such as scanning for files or loading content. 2: Presets Synths and Effect plugins often provide presets - show a preset selection in the main UI, or 1 click away. A fast way to browse presets greatly enhances UX when searching for a sound. Ideally support scroll-wheel interaction for changing presets. 3: Hotkeys - Ctrl Q, Quit - Ctrl W, Close Project - Ctrl S, Save - Ctrl Shift S, Save As - Escape, Context sensitive close I'm aware most of the recommendations above are obvious, and that many programs support these already. Cheers, -Harry -- http://www.openavproductions.com ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] User eXperience in Linux Audio
On Tue, Apr 21, 2015 at 08:16:05AM +0200, Thijs van severen wrote: We need to be aware of the fact that most people on this list are devs and therefore do NOT represent the average user In other words : I dont like splash screens so i'm not going to implement one is (IMHO) a very very wrong attitude. The same goes for any other feature I still don't get why splash screens are a good thing. I don't want a big modal picture blotting out the middle quarter of the screen just because an app is waiting to start up. Maybe there are other things I'd like to do with the computer while I'm waiting. -- Gordonjcp MM0YEQ ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] GuitarSynth
Am Mon, 20. Apr 2015 um 23:01:07 +0200 schrieb Gerald: Hi Gerald, Thanx. Fixed that and the warnings but a git push seem to be missing yet. Guido -- http://wie-im-flug.net/ http://www.lug-burghausen.org/ signature.asc Description: Digital signature ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] User eXperience in Linux Audio
On Tue, 21 Apr 2015 04:07:15 -0700 Tracey Hytry sha...@bayarea.net wrote: As a user, a brief splash screen gives me a little feedback that I actually clicked the program icon. This is very much my view too. It also tells me that if the program is not working correctly after that, then I should start it from the command line and trouble shoot it from there. Most of what Harry stated in is post seems fine with me. I would add that the splash should be fairly small, informative, and if possible carry occasional status messages. As soon as the main interface shows, the splash should disappear. Possibly, set it with a short-ish timer, so if it doesn't get updates from the application it disappears anyway, possibly after a short delay with a failure message. -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] User eXperience in Linux Audio
On Tue, 21 Apr 2015 08:43:15 +0200, Thijs van severen wrote: i dont think it has to be modal, and i'm also curious what other thing you will be doing in those 3-5 sec that the splash is there surprise me :-) Maybe taking a look at the messages displayed in the terminal emulation where the app was launched ;). Depending on what some apps need to establish, before the next app can be launched, we sometimes need to add delay ... roxterm --tab -n ♪ foo -e foo --option=bar ; sleep 2 The app already might be running, just establishing some things might take a while after the splash screen already disappeared. It e.g. might take two seconds after loading _data_ (not the app) and the app likely displays information by the terminal emulation output or by a log message window. The script/terminal emulation approach might be out of fashion, anyway, an app still could display a splash screen, while the important part of the app already segfaulted. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
[LAD] Linux Audio Berlin user group
Hello! There were lot's of Berliners at LAC 2015 and after talking to some of them we thought it would be nice to start a linux audio user group here in Berlin. This is an open call to all Berlin based Linux Audio users and developers! Let's meet, talk and share knowledge :) So far we have a mailing list[1] and an empty twitter account[2] (thanks to Sam :)) Our first meeting will probably be held at C-Base in the next weeks. We have no agenda yet, everyone is welcome, but me and Sam are more focused on electronic music stuff. Any suggestions on the date? [1] (as soon as the DNS starts working properly we send you the link to subscribe) [2] http://twitter.com/LAudioBerlin Cheers! -- Bruno Gola brunog...@gmail.com http://bgo.la/ ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] GuitarSynth
Thanks. The pitch detection is done by aubio library, but I rectify the signal before since that stabilizes the detection. By 'the 6th string' I assume you mean the lower pitched E string? Thats due to the longer waveform of lower frequencies which would need more frames per period to be detected. Low frequencies are a problem if the algorithm detects only the fundamental freq and not the harmonic comb (I dont know if its the case with aubio' yinfft algo). I had better results with a harmonic comb algorithm at lower freq, but I used the CLAM Audio suit for that. Sadly CLAM hasn't been updated for sometime (since 2010), so I scraped it. Maybe I'll extract the relevant parts of CLAM for GuitarSynth. Gerald On 21.04.2015 03:33, Gianfranco Ceccolini wrote: FalkTX helped me with the QT4/QT5 issue and I got it working Nice to play around. Fast pitch detection and reliable in most cases. The performance drops a lot when using the 6th string though. Nevertheless, good work Gerald! Regards Gianfranco ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] [LAU] Linux Audio Berlin user group
Hello Berlin User Group! Hello Bruno, Hello Sam, that is very good to hear! On behalf of the Open Source Audio Meeting Cologne I wish you luck. We exist for a year now and our regular meetings are 4 to 10 people. Maybe you find these information useful: Most important first: - Keep it social. There is no topic and no information which people just simply couldn't look up on the internet, if they are really interested. The point of such an event is to meet real humans. - There is a small website. Everything on one page. I asked linuxaudio.org for a subdomain. http://cologne.linuxaudio.org/ - Additionaly there is an Etherpad for protocols and where people can announce if they plan to come - We started with a meeting every two month and then upgraded to monthly - There is regular content and a slot for announced or improvised talks or presentations. See here http://yourpart.eu/p/linuxaudio-cologne - Even with no planned program it is no problem to spend your time with question and answer sessions. - There is a small mailing list for internal stuff. Currently, since I've written the ML-software myself, you have to register in person. Facebook and other stuff is mainly an extended calender and declared as such. So there is really only the website as central space for information. Keep Rockin'! Nils http://cologne.linuxaudio.org http://www.laborejo.org On 04/21/2015 03:07 PM, Bruno Gola wrote: Hello! There were lot's of Berliners at LAC 2015 and after talking to some of them we thought it would be nice to start a linux audio user group here in Berlin. This is an open call to all Berlin based Linux Audio users and developers! Let's meet, talk and share knowledge :) So far we have a mailing list[1] and an empty twitter account[2] (thanks to Sam :)) Our first meeting will probably be held at C-Base in the next weeks. We have no agenda yet, everyone is welcome, but me and Sam are more focused on electronic music stuff. Any suggestions on the date? [1] (as soon as the DNS starts working properly we send you the link to subscribe) [2] http://twitter.com/LAudioBerlin Cheers! -- Bruno Gola brunog...@gmail.com mailto:brunog...@gmail.com http://bgo.la/ ___ Linux-audio-user mailing list linux-audio-u...@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-user ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] User eXperience in Linux Audio
As a user, a brief splash screen gives me a little feedback that I actually clicked the program icon. It also tells me that if the program is not working correctly after that, then I should start it from the command line and trouble shoot it from there. Most of what Harry stated in is post seems fine with me. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] User eXperience in Linux Audio
On Tue, Apr 21, 2015 at 4:26 PM, Fons Adriaensen f...@linuxaudio.org wrote: Regarding shortcuts for close/quit etc.: they are not always wanted. When I'm recording live I don't want any single key or mouse click to accidentally interfere with that. It's bad enough with e.g. Ardour's GUI - every single pixel of it will do something when clicked on, and the result is not always so benign. I've had a musician dropping his shoulder bag on a cable to a cardbus interface during a live recording. This ripped out the card and destroyed the mechanical card locking system. So having an accidental click or key pushed is not at all such a remote risk. Hence the new Lock feature which disables all GUI interaction entirely (except for a click on the lock window to unlock, of course). ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] User eXperience in Linux Audio
On Tue, Apr 21, 2015 at 04:30:14PM -0400, Paul Davis wrote: Hence the new Lock feature which disables all GUI interaction entirely (except for a click on the lock window to unlock, of course). If that is a new feature in A4 it's an excellent idea. Regarding A4: I noticed that even when it discovers that Jack is already running, it invites me to set the sample rate and period size. And the suggested values are not the ones actually used. What it the rationale for this ? IMHO no app should ever try to 'take control' of a running Jack instance at all - it's a shared service. Ciao, -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow) ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] User eXperience in Linux Audio
On Tue, Apr 21, 2015 at 08:16:05AM +0200, Thijs van severen wrote: We need to be aware of the fact that most people on this list are devs and therefore do NOT represent the average user We also need to be aware of the following: * Developers are not necessarily coding nerds who are completely isolated from the daily practice of using software. Most of them on this list are actually users themselves. * If a developer holds some views that go against those of the average user he will have some very good reasons for that. There is *no reason at all* to assume that the average user's ideas are 'the right ones'. Most people prefer unhealthy food with a high salt/fat/sugar content. Never mind if they get diabetes sooner or later. If someone goes against that and produces some healthy food then I don't think that is 'a very wrong attitude' as you put it. * They way typical Windows SW works is not dictated by user interest. If it were no user would ever have any reason to abondon Windows and go for Linux. It is determined entirely by the short-term views of marketeers. There is no reason at all to assume that the same logic should apply to free open source software. * Every time the Linux community adopts some stupid Windows 'standard' for the sole reason that it is 'what users expect', this goes against its own long term interests. If Linux ever becomes the perfect Windows clone then it has destroyed its main reason to exist, which is to be different and better. Regarding splash screens: yes, some apps take a long time to start up. In most cases that is because they have either become bloated themselves, or depend on interaction with bloated desktop environments. That is by itself good reason for concern. Using a splash screen to fix that is at best a bandaid. That doesn't mean that a splash screen is by itself a bad idea - but it certainly is if its only reason to exist is to hide the results of crappy design. Regarding shortcuts for close/quit etc.: they are not always wanted. When I'm recording live I don't want any single key or mouse click to accidentally interfere with that. It's bad enough with e.g. Ardour's GUI - every single pixel of it will do something when clicked on, and the result is not always so benign. I've had a musician dropping his shoulder bag on a cable to a cardbus interface during a live recording. This ripped out the card and destroyed the mechanical card locking system. So having an accidental click or key pushed is not at all such a remote risk. Ciao, -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow) ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] User eXperience in Linux Audio
Nobody else has noticed this to date. On Tue, Apr 21, 2015 at 4:47 PM, Fons Adriaensen f...@linuxaudio.org wrote: On Tue, Apr 21, 2015 at 04:30:14PM -0400, Paul Davis wrote: Hence the new Lock feature which disables all GUI interaction entirely (except for a click on the lock window to unlock, of course). If that is a new feature in A4 it's an excellent idea. Regarding A4: I noticed that even when it discovers that Jack is already running, it invites me to set the sample rate and period size. And the suggested values are not the ones actually used. What it the rationale for this ? IMHO no app should ever try to 'take control' of a running Jack instance at all - it's a shared service. Ciao, -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow) ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
