Rosegarden Developers Interviewed by O'Reilly 189
rayk_sland writes "Users of the Rosegarden Sequencer project will be gratified to see it featured in O'Reilly's Linux DevCenter web magazine. I am a devoted fan of this program, which allows the user to sequence music using classical music notation, and has many other sequencer features I haven't even properly fathomed (read the article.) The Rosegarden project has recently released a 'pre-1' beta. Almost time for those party streamers..."
Rosegarden looks fantastic (Score:1, Troll)
Looks nice, but definitely could use some work in the dependancy and UI area.
Re:Rosegarden looks fantastic (Score:1, Funny)
Re:Rosegarden looks fantastic (Score:2, Insightful)
I do hope someday there will be a GTK2 interface for this great program, it will minimize the compile time a lot.
Re:Rosegarden looks fantastic (Score:1)
Re:Rosegarden looks fantastic (Score:3, Informative)
Re:Rosegarden looks fantastic (Score:3, Funny)
Re:Rosegarden looks fantastic (Score:2)
But I guess someone wants to sell the package as a whole
Re:Rosegarden looks fantastic (Score:2)
But I guess someone wants to sell the package as a whole ...
OK, then! Tell you what I'm gonna do. I'll split up kdelibs and email you the 'modules' for only ninety-nine ninety nine apiece! Take your pick! Think of the convenience!
Re:Rosegarden looks fantastic (Score:2)
I wasnt talking about kde. I was talking about QT. It claims to be platform independant. But it isnt for GPL software (see windows license). Its current design is making it hard to use QT *only* for GUI stuff and using libs that are crossplatform under GPL without generating much duplicate code on the system.
Think of the convenience!
Trust your package manager, Luke.
Re:Rosegarden looks fantastic (Score:2)
Not if I want my software to be free - QT for example is not available under GPL for windows.
So its a cross platform API only for commercial software.
Re:Rosegarden looks fantastic (Score:1, Interesting)
Rosegarden doesn't work on Fedora Core3 either.
oreilly (Score:1, Redundant)
You must mean Bill O'Reilly (Score:5, Funny)
Guillaume Laurent: Well, first off..
BO: Wait, are you french?
Guillaume Laurent: Yes I am from France and I don't see why that should be held against me, in fact the relationaship between the US and France has always been one of [interuption]
BO: Shut up! Shut up! Shut up!
Re:You must mean Bill O'Reilly (Score:2, Funny)
Wrong description (Score:1)
From the page...
Rosegarden is a professional audio and MIDI sequencer, score editor, and general-purpose music composition and editing environment.
What I just want to get are specs... How many tracks at once does it promise ?
Logic Pro does more than enough and Cubase was much slower.
Re:Wrong description (Score:1)
OK, just tell me how many more tracks (no effect) it supports on similar hardware.
Prototyping Music. (Score:1, Interesting)
stability (Score:3, Informative)
Re:stability (Score:3, Informative)
Re:stability (Score:2)
Re:stability (Score:2)
This would be nice if it would import/export PT files....
Re:What? (Score:2)
Re:Are you serious? (Score:1, Insightful)
Program a graphical interface to MIDI gear.
Track automation layers.
MIDI plugins.
Even things as simple as switching programs don't work flawlessly.
If the Rosegarden developers are reading this, it would be worth their while to spend some serious time with Logic and Cubase and some moderately complex MIDI keyboards and rackmount units.
Start by copying the features from the oldest versions of these programs (I'm sure an Atari + Cubase can be had for very little money), and work
Re:Are you serious? (Score:3, Interesting)
Logic lets you create a knob-and-slider graphical interface to MIDI gear that doesn't have an interface, and it can be fully automated.
By track automation layers I kind of meant two things. First, you want to be able to record a
Re:Are you serious? (Score:1)
As for SVN, yes, we'd like to use it, but sforge doesn't provide it yet (they announced it was scheduled for 2005).
Regarding outside patches being applied : we get less than a dozen per year, most of which are very simple and can't represent stability issues. We've never had a stability problem due to an external pat
Re:Are you serious? (Score:1)
I'm sorry but you have no clue on what you're talking about here. 90% of the crash reports we get are actually due to the sound libs we depend on (generally people using old version of Alsa). Lately we've received only 1 in several months. Please don't just blindly give stereotypical arguments which simply don't apply to our case.
Re:Are you serious? (Score:1)
Re:Are you serious? (Score:1)
Uh, hello, none of us is clueless or immature enough to ever do that, nor would we even accept to work with someone who would.
Seriously: copy down what we say, make a list of the points, and present them to the dev team, if you're not on it.
Is it really that hard to log a feature request on sforge ? Anyway, we're reading you. No guarantee on when what you ask
Re:Are you serious? (Score:1)
Get real, these products have resources we'll simply never match. This is a relatively small open source project with all the usual problems applying : lack of time, lack of manpower, slowness in communications because it's all done through email, etc... We have to keep realistic about what we can do. So we prefer to have less features working correctly (and even th
Re:Are you serious? (Score:1)
The fact is, that would be a very poor goal. It's something we actively don't want to do, unless someone else is providing the resources to do it.
We have to balance the needs of quite a lot of different sorts of users. Matching all of the MIDI functionality found in Cubase may make an ideal prog
Re:Are you serious? (Score:1)
I'm afraid both programs are way too evolved for this to achieve any real results. One program would pretty much have to be thrown away and rewritten to the other's fashion.
what specific things I think would bring it closer
No problem with that, as I said a well-detailed feature request on sforge is the best thing to do. Keep it short though, A laundry list of 100+ items won't help
I hope you don't dismiss everything I've said
Not at all.
Rosegarden has come a long way. (Score:2)
Open Source is getting there. Wherever there may be.
Re:Rosegarden has come a long way. (Score:2)
Re:Rosegarden has come a long way. (Score:2)
You may not be aware, but Noteedit is no longer under development. Which is a real pity, because it was starting to become a really useful tool that had no pretensions to be anything but a notation editor.
I don't mind Rosegarden, but all I need is a notation editor, and a full blown midi environment (which is very pretty, by the way) is overkill. In actual fact, it confuses me a lot, which says more about me than the program!
Kudos to the devs th
Re:Rosegarden has come a long way. (Score:2)
Excellent news... (Score:2, Funny)
Re:Excellent news... (Score:2)
Re:Excellent news... (Score:2)
Re:Excellent news... (Score:1)
Showing my age, I guess.
Re:Excellent news... (Score:2)
"I beg your pardon"
I'm wasted here, y'know...
Lilypond (Score:5, Informative)
Looks like Rosegarden can export to Lilypond, which is by far the best music notation program AFAIAC. For years in our choir there were sheets made using Finale, and when I remade one using Lilypond people were asking me where is the book that this came from, it just looks so professional. They have a great paper [lilypond.org] on this .
Re:Lilypond (Score:1)
Lilypond is great, although it's still in a state of rapid change. I hope one day they make the project stable enough that, e.g., people can depend on the Lilypond language not to keep on
Re:Lilypond (Score:1)
No, you can print directly from Rosegarden as well. The results won't compete with Lilypond, but they're readable.
Re:Lilypond (Score:1, Informative)
There's a editor for muse here [sourceforge.net]
If you are using lilypond on windows (or not), I would highly recommend LilyTool for JEdit [sourceforge.net]
Re:Great paper? (Score:3)
Re:Great paper? (Score:4, Interesting)
the point that reprints are usually better than the 2004 material.
The quality of score layout has been steadily declining over the past 20 years. Show me a 2004 Baerenreiter score that can compare favorably with their 1950 prints. I haven't seen any and I do get to see a lot of new music.
The unfortunate reality is that revenue in the serious music publishing business is in decline. This makes good-quality engraving (which requires a lot of work and skill) unaffordable except for the most famous composers of the most prestigious publishers. LilyPond is our try to counter that trend, by making software that produces good output without requiring lots of work or lots of knowledge.
Han-Wen
Re:Bugs in Lilypond 2.4.1 (Score:2)
Re:Bugs in Lilypond 2.4.1 (Score:2)
Probably the first one, saying "error: Incorrect lilypond version".
Why don't you make lilypond 2.4 recognize 2.2 files and automatically run convert.ly on them? That would seem much more user-friendly.
because 1. some conversions need minor hand-editing 2. because we want to encourage users to upgrade their files.
Re:Why bother with Lilypond? (Score:4, Interesting)
Maybe -- but it's the same sort of nit-picking as complaining about books printed using monospaced fonts, or dot-matrix quality print. Other computer-generated scores may have the same information, and may even look superficially similar, but they do tend to be a bit robotic and inelegant. LilyPond's output is clearer, more natural, and easier to read. Which is exactly the point.
LilyPond isn't perfect; there are some things it's still not easy to do (e.g. vocal scores where lyrics are shared or voices switch between staves, or pieces in free time), and placing of marks like dynamics isn't always ideal. (Though I'm stuck with an older version, so it's probably improved since.) But it has far far better instincts about layout than anything else I've used (Cubase Score and SX, Finale, Harmony Assistant). Although the initial entry may take a little longer than other packages, it needs much much less tweaking afterwards, so it works out quicker overall, as well as producing much more professional output.
Result: even though I've shelled out lots of the folding stuff for Cubase SX, I haven't touched its score editor since installing LilyPond. Those nits can turn out to be more important than you'd think.
I'd hate to be on this project... (Score:2)
Rosegarden Developer: It'll be done when it's done. I never promised you a--DOH! Uh, I'll get those deliverables to you by noon, sir. <grumbles>stupid project names</grumbles>
RTA? (Score:1, Redundant)
RTA... you're kidding, right?
NoteEdit (Score:2, Informative)
Unfortunately the project is half-dead due to percieved disinterest. Doesn't make it less functional though.
OSX (Score:1)
Re:OSX (Score:1)
I don't think Linux has a realistic shot at beating down Apple (Logic), Steinberg (Nuendo, Cubase), Cakewalk (Sonar), Digidesign (Protools) and MOTU (Digital Performer) without any kind of differentiation. Basically, OSX and WinXP work for these kind of apps now, there's little gain to be had in moving to a new OS. Rosegarden is doing very well in that it has moved from totally impractical (a couple of years ago) to borderline usable (now) as regards actually doing anything musical. However look at what
Re:OSX (Score:2)
The project was originally funded by the European Commission, and is still going since official funding ceased. It's got some work to do still, but I'm thinking about pulling it down and having a pla
Re:OSX (Score:1)
I dunno...right now, all of the good sequencers are pretty expensive, so there's definitely a market on the Mac/PC for a somewhat decent, free sequencer. For instance, I own Logic 5.1 for Windows, which I use for recording and stuff, but I have an OSX laptop that I use for performances, etc. However, I
Re:OSX (Score:1)
My real issue with both this and AGNULA is they're still too big, while failing to provide the weight of musical features to go with the installed size. I'm really just looking for a box that has as little as possible running on it.
If you have a look at things like hardware samplers, they're basically just PCs with a very minimal amount of operating system and enough software to drive a little bit of proprietary sampler hardware. There's very little to go wrong, and if it does go wrong then re-installin
ARGH!!!! (Score:2, Troll)
And considering that the majority of music users use, well, WINDOWS... (my dad always bought windows music products. I think Rosengarden is missing a huge potential market: Windows users.
I tried freeware Windows MIDI sequencers a couple of years ago, all sucked. So I'd gladly appreciate if the Rosengarden devs made their software cross-platform, now that it's STILL IN EARLY dev
Re:ARGH!!!! (Score:4, Insightful)
Open source developers usually write software because they want to use it. If they don't want to use it with Windows, then why should they port it just to satisfy some whinging Windows users? Especially the "I couldn't code my way out of a soggy paper bag, but Doing This Would Make Open Source Succeed*!" sort.
* Succeed being defined as "do what I want it to do"
Re:ARGH!!!! (Score:1)
It's because most developers do it for themselves - as an interesting project, not considering what the user needs (not to mention 0 market research usually). That's cool (I'm a dev myself and do stuff for the fun of it), but whining about why
Re:ARGH!!!! (Score:2)
Firefox and OOo were cross-platform even from their pre-open-source roots, so they where not really ported.
FF and OO are means to keep/get critical infrastructure (the www and Office-documents) to a open standard.
Rosegarden is not comparable to this.
Re:ARGH!!!! (Score:2)
Rosegarden is GPL. If a Big Company wants to do the aforementioned, what's stopping them?
Re:ARGH!!!! (Score:2)
I just read that page. It starts OK but then it becomes a little radical... saying that porting something to Solaris will only help Sun seems a bit extreme to me.
I can easily imagine people in a situation where they need a certain open source library to work on Solaris and they have no other choice. They can't install Linux on the machine because it's not theirs to control, maybe there are some other apps running there that are solaris-only. Or they developed their own app on Linux but it turns out this pa
Re:ARGH!!!! (Score:2)
But the audio code is the sticker. There is no free cross-platform sound code (other than relativly simple stuff like SDL (simple by comparison to some of the more interesting things you can do native)). So if you were to port the audio engine, then it should be easy. Either that or write an ALSA emulation layer for Windows or OS X.
Graphics are portable thanks to toolkits and OpenGL/SDL.
Re:ARGH!!!! (Score:2)
Actually, PortAudio solves the cross-platform audio problem quite well (cf. audacity), although I don't know if Rosegarden uses it. But, the QT toolkit may be the real stumbli
Re:ARGH!!!! (Score:1)
However, MacOS/X has Garage Band and Logic, Windows has Cubase, Cakewalk... I'm not sure how much of a "market share" Rosegarden could have on those platforms, where free software is less of an issue.
Re:ARGH!!!! (Score:4, Insightful)
It's not that simple.
I maintain a couple of and contribute to a few free software projects. I can build and test on a couple of architectures and a couple of operating systems on my own. I don't have Windows installed, and if it weren't for one machine a roommate uses only to run an accounting program, there wouldn't be an installation of Windows in my home. (That machine has no network connection.)
If I want to know that that software runs on Windows, I have to rely on other programmers who not only can and do run Windows but can and do build software there. I can understand why there seem to be so few of them -- the last time I tried, it was an awful experience -- but telling developers that they should write software that works on Windows is fairly useless.
If you want good free software that runs on Windows, go to this supposedly huge, untapped market, find people capable of developing, testing, and submitting bugs, and point them at those projects that wouldn't mind running on Windows if they had a little help.
Do it! (Score:2)
Its open source. By definition that means the source code is there and waiting for you to do the work. The Rosegarden developers don't care about MS Windows, because that have linux. If you care, either do it yourself, or hire someone to do it for you. For $250,000 I'll port it for you. (It should be easy for you to find someone willing to do it for less, I hate Windows development so I'm charging a lot extra for the pain of doing something I don't like to do)
Re:ARGH!!!! (Score:2)
Your argument is akin to complaining ab
Charge for the Windows version (Score:2)
Re:ARGH!!!! (Score:2)
Re:ARGH!!!! (Score:2)
Rosegarden works a lot with sound and MIDI. It's built on top of the Linux audio architecture (ALSA). ALSA is free software, so Rosegarden can use it and still be free software.
On Windows, Rosegarden would have to use whatever API Windows has for audio, and that's not free software. Maybe there is a license conflict that prohibits the Rosegarden developers from having code that calls that windows API, or maybe they just don't want to call a non-free
Re:ARGH!!!! (Score:1)
Re:ARGH!!!! (Score:2)
Re:ARGH!!!! (Score:1)
>The problem I have is that my hardware for MIDI and
>audio (M-Audio Quattro) doesn't have Linux support
Of course it does! It even has an officialy supported ALSA driver.
>in general support for other multi channel cards is
>lacking under Linux.
Well, that's true for some, but not for others. I can find no fault, at least at the driver level, with the ALSA driver for my Delta 1010 or my Delta AP2496. I bought the 1010 because of the lack of support for my Echo Layla, but that's supported now a
Re:ARGH!!!! (Score:1)
None of the big guys will port to Linux any time soon. Linux has no installed user base of musicians, and no differentiating advantage. Where's the return on investment in porting to a platform with no new users? The reality is that most people who're both serious musicians and interested in Linux probably have a Windows or Mac system for audio use anyway. If they port to Linux they won't make any more money, they'll just lose a sale on their existing platform. It's a shame, but it's true.
Linux needs
Re:ARGH!!!! (Score:2)
Re:ARGH!!!! (Score:1)
>Sometimes you can or do (e.g. Nvidia, ATI, Lexmark).
In those cases, I usually assume that you're getting the result of a modest effort by a manufacturer who sees a need to have a bullet point ("Linux support checked yes") but still wants to be completely unreasonable about releasing specs. I don't expect the manufacturer to make as sincere an effort at driver development, as someone like an ALSA project developer who is actually passionate about their work.
Re:ARGH!!!! (Score:1)
Any chance on a Windows version? (Score:2)
Re:Any chance on a Windows version? (Score:2, Informative)
Re:Any chance on a Windows version? (Score:2)
Re:Any chance on a Windows version? (Score:2)
That's NOTHING (Score:1)
midi dependancy is a huge problem (Score:3, Interesting)
The trouble I have with Linux music notation is that to use it one practically needs to be a skilled programmer not a composer. Lilypond is on the right track, being a very powerfull parser of an input script, it has the potential to become the very best notation engine around. Rosegarden is a valient attempt to do everything for everybody. So it has the unenviable task of trying to code for midi and notation.
Human performance, by nature is not perfect, the task of cleaning up notation created with midi can be very daunting indeed. The skills of a composer are needed, unfortunately these are skills that require study well beyond what the average musician of today has.
To get to the point, having midi input totally separate from the notation gui, and reducing the program overhead to facilitate notation is a goal that cannot be ignored. Perhaps a non midi dependant gui is the only real answer. Programs like Score, (San Andreas), Musedit, Speedscore, Finale and a few others already do this. However few if any have the scoring elegance of Lilypond. It would be great if a Linux gui like KDE or Gnome included an effective music notation gui.
Re:midi dependancy is a huge problem clarification (Score:1, Interesting)
When I hear "interviewed by O'Reilly"... (Score:1)
Nashville notation? (Score:2)
What is it? I guess it's called other things, but basically it's chord progressions jotted down as numbers. Instead of
C...F...G^7...C
Am..Dm..G^7...C
you would write
1...4...5^7...1
6-..2-..5^7...1
Also, instead of putting chords directly above the words, like most guitar charts d
Re:Nashville notation? (Score:1)
Re:Nashville notation? (Score:2)
Any trumpet player who is confident of playing this note in a public setting should be quite capable of allowing for these mistunings without even thinking about it.
If they can't, I don't think changing the key's going to help.
Good point though.
Re:Nashville notation? (Score:1)
Re:Nashville notation? (Score:2)
Fussiness is good, and I think today's era of scores being proofread by midi instead of real musicians somewhat parallels the way that people think they can write because the grammar checker in Word passes whatever it is they wrote.
You got me thinking about the differences in tone in brass instruments (which is all I really know.) Even two instruments of the same make and model---even the same batch number---can be out of tune on any
Re:Nashville notation? (Score:2)
I agree, but feel that the benefits are worth it. If your band has enough brains to decypher number-based "hieroglyphics" (now there's an old term for you), it's a joy to not have to hold their hands while they figure out how to play a tune in a different key, or modulate a half-step in the middle of one.
Once I figured out Na
One reason projects are hard (Score:1)
This is so totally untrue that it is sad the people still say this. Documentation is essential for both bug fixing and new features even if it is a one-person project that is going to last more than a few months. The time saved is enormous when you have to revisit code you wrote some time back. Not only in understanding the code but also to help not writing additional code that breaks previous code. And if there is more than one person on a p
Re:One reason projects are hard (Score:1)
To say the least. There's gotta be a reason why, in my 10 years of working as a software engineer, I've never seen this done on any project in any company.
The reason is that beyond discipline, maintaining code documentation is also a huge time eater (it does save time too but it's no free lunch). That is, even a simple refactoring will take like 3 times as long because you'll have to update the doc accordingly. And when you're working in fragmented time like it's generally
Re:short-term thinking (Score:3, Interesting)
Gee, how come we never thought of this before.
Honestly, if it were that simple do you really believe we wouldn't do it ? "Training" people through email just takes too long, and many contributors have just vanished after a couple of patches. We just can't afford to invest this kind of time into some guy whom we have no way to know if he'll stick around. All projects of this scale have the same kind of problem, there's no simple solution
Re:short-term thinking (Score:2)