-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ralf Mardorf wrote: <snip> >>>>> This is called threadjacking. If that term is new to you, try googling >>>>> for it. Most of your post really belongs in a new thread instead of >>>>> cluttering up this one. The OP is talking about problems with his >>>>> maudio audiophile not working. Unless you have something to say about >>>>> this specifically then start a new thread, preferably with details. >>>>> >>>> Just a shot in the dark. There is trouble with devices, he has trouble >>>> > > A MIDIsport problem is not what the original post was about. Sure they > are both "hardware" issues, but it needs its own thread, just at it > would need a separate ticket. Can you imagine how unwieldy a single > hardware support ticket would be? > > >>>> with devices, okay, I understand, I'm definitive unwanted in this list. >>>> >>>> > I have never actually said that. I strongly believe that your presence > on this list is *solely* by *your* choice, not mine or anyone else's.
> Nobody was writing about a ticket in the original post and anyway, it's > unscientific to exclude something for a brainstorming and in addition I was using the ticket as an analogy. There is no strict one problem per thread rule, but it generally works to help keep discussions organized so that the relevant people can more easily follow and respond. Web based forums are usually more strict in this regard. It is something to keep in mind in any event. > this is a user list, errors for the brainstorming might be more > reasonable than on a developers list. Please discuss stuff that isn't User list or otherwise, there are certain procedures that can be useful. These procedures are well documented as you by now should know. My only goal here is to help you to be more effective. Take it or leave it, the choice is still yours. > for users on the developers list, so no idiot like me, will annoy you. You assume that I am annoyed. The only reason I keep replying is that I genuinely want want everyone to have as good of an experience with 64Studio as I have. In fact I want everyone to have a *better* experience. Rest assured the only strong emotion I am feeling right now is amusement. > OTOH, I'm not sure if you do know a lot about issues for audio Linux, my For someone who complains about how others treat you, you sure do not follow your own advice. > so called FUD is taken seriously by some developers and measurements are > showing that my ears are right. The next step is to find the reasons for > those issues, not on that list, but on some developers lists. As I have said before, I hope that you find a way to channel your enthusiasm into useful contributions to any FLOSS project. > I declared my 2 cents as "a shot in the dark", but they were not > causeless. Audio and MIDI devices are audio and MIDI devices and not > printers and monitors. What I am really asking of you is to do some basic research before "brainstorming". Educated guesses are very different from random guesses. For example, WiFi and wired ethernet are more closely related in that they both pass ethernet frames (ie. they both manipulate the exact same data type) yet they are treated differently when troubleshooting. A few minutes of research would help one zero in on the problem or at least ask the question that will lead to a successful resolution. A bad or wrong question is worse than a wrong answer because a wrong question will pretty much guarantees that the problem goes unsolved. Hth, -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrg2d8ACgkQwRXgH3rKGfOkyQCfQCFvptdHibW9zxYfGslrJu6l ruMAn2ntSyYUCEkuXlVK9Fkpi40phS86 =wwlJ -----END PGP SIGNATURE----- _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
