<HTML>
actually this thread and another rant about some jack packaging issue on Suse... I'm sure everyone knows what I mean. <BR>
<BR>
<BR>
<BR>
<B>On Thu Dec 18 9:53 , "sonofzev@iinet.net.au" <SONOFZEV@IINET.NET.AU>sent:<BR>
<BR>
</B>
<BLOCKQUOTE style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #f5f5f5 2px solid; MARGIN-RIGHT: 0px">Here Here Geoff.... <BR>
<BR>
Having been following this thread for the last couple of days, I've found it both amusing and frustrating... <BR>
I found it amusing because when I first started I was much like the OP.. very hot headed ... <BR>
<BR>
I've learned a few lessons since then and these are good things to keep in mind as a non developer user. <BR>
<BR>
1. Most developers are doing this in their spare time, appreciate that, be nice to them and help where possible... Some (one of note for this list :) ), have given up having regular and (possibly) very well paid careers to develop this stuff.. (Yes people you should subscribe if you are using Ardour). The people who are actually paid to work on Linux code are often absolutely stretched to the limit too, they will have targets e.t.c... If you have something that is not going to affect many people, it's not likely that they are going to be able to dedicate alot of time to your issue. <BR>
<BR>
1a. Ask questions nicely and respectfully.. regardless of your coding/developing experience, the developers know their own code and architecure more intimately than you.. (this is more an observation, I am merely an application engineer for propietary telecomms software so I don't really touch code only get deep into configuration areas).<BR>
<BR>
2. Due to the nature of things with hardware some things will not always get fixed.. the developers often have no access to the hardware and the relevant documentation is not always available.(this has been my experience with MIDI time clock in external MIDI racks from MOTU ... and emagic)... Research very carefully and if you try to go with something that isn't 100% supported then have a backup plan for when your deisred operation is not available. <BR>
<BR>
3. When upgrading to new hardware, especially motherboards, research every component thoroughly, often when buying very new release components the support isn't always there yet. This was my experience when I bought my first AMD-64 939 system (nvidia SATA drivers were only in their infancy and required work to get going) and my core2 duo system for which again the SATA drivers on the jmb chip were developed but not included on any distro releases at the time I bought it.... <BR>
<BR>
4. Patience is a virtue..... Cliche as it might be this is a truth that cannot be ignored... If you have deadlines with your music production (or any other work) and you have a system that covers your needs, don't upgrade (software or hardware) until you can afford some time to work through some issues. If you can get a dev box or make sure you have an image of your stable system that you can reference should an update/upgrade fail. <BR>
<BR>
I hope this helps someone, otherwise it may sound a bit arrogant. <BR>
<BR>
regards<BR>
<BR>
Allan <BR>
<BR>
<BR>
<B>On Thu Dec 18 8:34 , Geoff Beasley <GEOFF@LAUGHINGBOYRECORDS.COM>sent:<BR>
<BR>
</B>
<BLOCKQUOTE style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #f5f5f5 2px solid; MARGIN-RIGHT: 0px">On Wed, 17 Dec 2008 10:42:45 pm John Rigg wrote:<BR>
> Doing your research first and then asking targetted,<BR>
> concise questions is much more likely to get your problems fixed.<BR>
<BR>
...and they are ALL fixable and Linux is by far and away the best multimedia <BR>
platform PERIOD.<BR>
<BR>
g.<BR>
-- <BR>
Geoff Beasley<BR>
Laughing Boy Records<BR>
www.laughingboyrecords.com<BR>
_______________________________________________<BR>
Ardour-Users mailing list<BR>
<A href="javascript:top.opencompose('ardour-users@lists.ardour.org','','','')" target=_blank>ardour-users@lists.ardour.org</A><BR>
<A href="parse.pl?redirect=http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org" target=_blank><SPAN style="COLOR: #ff0000">http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org</SPAN></A><BR>
)<BR>
</BLOCKQUOTE><BR>
</BLOCKQUOTE></HTML>
<BR>