--- Joe Hartley <jh@xxxxxxxxxxxx> wrote: > Well, Paul & co. don't have any sort of marketing or sales group > pushing for a release date, so there are no artificial deadlines, > so > there's less liklihood of something pushed out as a release to make > an > arbitrary release date. Well, I wouldn't want an artificial or arbitrary date either. But it seems like when a project reaches 0.9beta19 and has been at 0.9betaX for over a year, it could appear to onlookers (like me) that things have somehow gone bad -- either the scope has spun out of control or bugs are more difficult to fix or development is not moving very fast. Again, that's the perception, not necessarily the reality. But, since it is open source and releases don't matter much, maybe we should drop the complicated release scheme altogether. Just release 1, 2, 3, 4... 49, 50, 51, etc. Or maybe give realeases a name instead of a number. Really, it's not a big deal. People who are familiar with open source methodologies will look at 0.9beta19 and not be taken aback. But to me, it seems limiting to let it get that far. Now that I'm listening to myself type, it seems like I'm making a mountain out of a molehill. > I'm surprised that you couldn't continue in Ardour at all, again, > I've > never had a project foul up badly enough to bring things to a halt > like > that. There was one time that I had to edit the XML file to remove > a > track that couldn't be loaded, but because the sessions are defined > in XML, that was trivial to do. Yeah, my transport just stopped working. I'd press "Play" and the play button would highlight, but the cursor wouldn't move and no sound would he heard. Then I'd press "Stop" and both play and stop buttons were highlighted. By that time, I was too frustrated to try and get the problem fixed, so I just imported the raw tracks into Audacity and remixed them. I forgot about the NumLock problem. I'm not sure if NumLock was on or not. > Maybe a little of both. It sounds like you might be in the wrong > "mode" > to do an operation; I found Ardour much easier to use once I'd > grasped the > concept of the object and range modes (which are selected by the > buttons > in the upper right of the editor window). I've begun to understand the mode concept a bit, but it doesn't always make sense. I'm still going to take issue with the notion that "this is just hard, complicated stuff, so the interface cannot be made intuitive." Most of my experience is with Cakewalk/Sonar and I found it relatively easy to use, though I did have to spend some time with the doc early on. IMHO, Ardour makes some choices that make it more difficult, at least for someone who is corrupted with a Windows background :-) Greg _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com
