Rosegarden Developers Interviewed by O'Reilly
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 absolutely fantastic. Unfortunately, its dependancy on KDElibs and QT make it impractical for me to build it in a reasonable amount of time (I'm on gentoo, so binaries for everything isn't really an option) and its layout makes it impossible for me to use it in ratpoison (my WM of choice) anyway.
Looks nice, but definitely could use some work in the dependancy and UI area.
Disconnect and self-destruct, one bullet at a time.
Thats is what i love about oreilly, they have so much good info.
Freedom or George Bush
...but the story submitter said so.
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.
Trolling using another account since 2005.
Harmony Navigator
I've tried Rosegarden a couple of times - looks to be a very promising package - i've even contributed some stuff to the project. Last time i tried it though (probably 6-12 months ago) it had a tendancy to die unexpectedly rendering it fairly useless for anything serious. Its good to see its now approaching a final release. I will be trying this out to see how its been coming along - and maybe ... just maybe I can actually write some tunes under linux...
Electronic Music Made Using Linux http://soundcloud.com/polyp
GUI should be the top priority of Rosegarden development. It has progressed a lot since the earlier versions, but there is still a long way to go.
Wow! I haven't looked at the rosegarden project in a long time, but from looking at those screenshots, they have come a LONGGGG way. I remember when it used to just be a very simple notation program.
Open Source is getting there. Wherever there may be.
...for all those who've been told they were never promised Rosegarden.
I only post comments when someone on the internet is wrong.
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 on this .
Brainless Manager: Where's my deliverables! We're past our due date!
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>
You see? You see? Your stupid minds! Stupid! Stupid!
Am I the only one who thinks Rosegarden is one of the most unstable FLOSS applications out there? I would love to give it an in-depth try, but every time I do, it just crashes on me.
Been wrestling over it for 3 months :(
.. here I come ..
:P
Can't even output a simple Do-Re-Mi
I know, I know its me! - it's all my RTFM fault - I just don't get that whole jack-ass konfingeration stuff *sigh*
Windows Cubase
Nah - not really
I will try again when I test-drive Fedora Core 3.
They have a great paper on this.
Lilypond seems to compare themselves to some of the biggest music PUBLISHING companies in the world. They compare their typesetting to that of Schott, Bärenreiter, Henle, etc which release REPRINTS of previous editions. So all of these comparitive examples hold no weight at all.
If you actually look at 2004 works by PRESENT-DAY composers by those publishing companies, you will see their typesetting is flawless, as they are done with computers.
REPRINTS are exactly that- originally published in the pre-computer age; but REPRINTED and released in a newly bound edition, stamped with a present year copyright date. So why the heck is Lilypond comparing themselves to reprints from the 1950's?
Try comparing yourself to a 2004 composition published by Schott, CF Peters, or others if you want a fair comparison. Not a reprint.
a rosegarden.
now did they?
And I know Soundgarden.
Im just a musical geek girl who cant say no.
A girl posting on slashdot.
Did hell finally freeze over?
...and has many other sequencer features I haven't even properly fathomed (read the article.)...
RTA... you're kidding, right?
You know you're a geek if you've ever replied to a tagline.
NoteEdit is also decent for sheet music to Lilypond if that's what you're looking for.
Unfortunately the project is half-dead due to percieved disinterest. Doesn't make it less functional though.
Seems like a wise decision would be to follow Audacity's example and to release an OSX port...Windows would be nice as well, but I guess OSX is more likely. In all honesty, many musicians aren't going to want to take the time to futz with compiling relatively unproven software on Linux.
ZuluPad, the wiki notepad on crack
Er...maybe if they trained up some help, they'd have more time...
Of course they don't seem to be unhappy about the lack of help, and they can run their project however they want. And seem to be building something great to boot. But I do think a lot of opensource developers are remarkably shortsighted about this sorta thing.
Mod me troll if you want (uh but flamebait preferred :) ), but i'm getting tired of Linux-only releases in a cross-platform world.
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 development. This is when major structural changes can be done with nobody noticing.
And finally... for those of you who want to flame me with "this is NOT a Windows thread", I respond: If I don't come in the Linux zone and say that window users needs cross-platform versions of already existing linux apps, then who's going to tell them?
My 2 cents.
Even one that uses Cygwin? I'd hate to have to try to run this thing in VMware (Unless somebody can point out a faster way to run Linux in Windows)
like O'Reilly's last interview!
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.
Human performance, by nature is not perfect, the task of cleaning up notation created with midi can be very daunting indeed.
I have a client who uses Lilypond for music notation, and he tried capturing into rosegarden, then cleaning it up, but since he was used to playing pianos without pedals, he tends to bleed notes over, so it was unfeasable.
Speaking of Lilypond, help is needed compiling it for Arch Linux. You know. FYI.
Please stop stalking me, bro.
I always think "Shut up! Shut up! Cut his Mike."
What "MIDI problems"? Can you give real examples of what you can do in these other apps that you cannot do with Rosegarden?
BO: Tell me comrades, what makes you want to give away these products and go open source? Communism? Beatles music? Liberal guilt!?!?!
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!
If you want a Windows version of Rosegarden so badly, I'm sure you could find ten of your Windows-loving friends and family, get together and each pay $150 towards the $1500 Qt licence fee. That's what it will cost to get you your Windows version of Rosegarden.
Rosegarden's notation and typesetting is good enough for a lot of single stave and 2-stave classical music. The What's wrong with music notation software section you cited gives only one serious typographical flaw -- the misplaced accidental -- in the output of Finale. The other flaws are really just nit-picking.
Not yet but it could do very quickly if you were to provide a pointer to any freely available documentation about the design of the PT file format - is there any such documentation available?
yes but??? can I compile it --without alsa and jack. Or install the notation gui without the midi inyourface guis. Same thing as Noteedit no tse or some godforsaken midi button gui crap... no compile, period. I will have another look at the ./config and makefiles to see if it can be done. However I doubt it. In my experience (5 years) nothing causes more crashes in KDE and Gnome than button driven midi interfaces! BTW it was Stravinsky...Stavinsky was a two bit Hollywood copycat.
I'd like to understand what you're saying but your English is very hard to understand (sorry if English is not your first language). You were originally complaining about Rosegarden requiring "MIDI input". That's a different problem from compiling without alsa and jack, which should work ok.
What do you mean "install without the midi inyourface guis"? Which "in-your-face GUIs" are you talking about?
I haven't mentioned Stravinsky until now. What are you talking about?
Lilypond 2.4.1 fails completely on several Mutopia files including chopin-op-25-01.ly and also Lilypond itself doesn't compile without a lot of tweaking. Do you have a bug tracker? I couldn't see any mention of one on Lilypond - Development - Participate.webpage
.ly file:
/usr/local/share/lilypond/2.4.1/scm/lily.scm: ...) /usr/share/guile/1.6/srfi/srfi-1.scm: ...) ... /usr/local/share/lilypond/2.4.1/scm/lily.scm: /usr/local/share/lilypond/2.4.1/scm/lily.scm:
./out/volta-engraver.dep; DEPENDENCIES_OUTPUT="./out/volta-engraver.dep ./out/volta-engraver.o" g++ -c -DHAVE_CONFIG_H -DSTRING_UTILS_INLINED -Iinclude -I./out -I../flower/include -I../flower/./out -I../flower/include -O2 -finline-functions -g -pipe -I/usr/share/texmf/include/ -I/usr/include/python2.3 -O2 -finline-functions -g -pipe -I/usr/share/texmf/include/ -I/usr/include/python2.3 -W -Wall -Wconversion -o out/volta-engraver.o volta-engraver.cc ./out/lexer.dep; DEPENDENCIES_OUTPUT="./out/lexer.dep ./out/lexer.o" g++ -c -DHAVE_CONFIG_H -DSTRING_UTILS_INLINED -Iinclude -I./out -I../flower/include -I../flower/./out -I../flower/include -O2 -finline-functions -g -pipe -I/usr/share/texmf/include/ -I/usr/include/python2.3 -O2 -finline-functions -g -pipe -I/usr/share/texmf/include/ -I/usr/include/python2.3 -W -Wall -Wconversion -o out/lexer.o out/lexer.cc ./out/parser.dep; DEPENDENCIES_OUTPUT="./out/parser.dep ./out/parser.o" g++ -c -DHAVE_CONFIG_H -DSTRING_UTILS_INLINED -Iinclude -I./out -I../flower/include -I../flower/./out -I../flower/include -O2 -finline-functions -g -pipe -I/usr/share/texmf/include/ -I/usr/include/python2.3 -O2 -finline-functions -g -pipe -I/usr/share/texmf/include/ -I/usr/include/python2.3 -W -Wall -Wconversion -o out/parser.o out/parser.cc
Here's the error for that
error: Error found in this music expression. Ignoring it
Backtrace:
In unknown file:
?: 0* [lilypond-main ("chopin-op-25-01.ly")]
In
596: 1* (let* ((failed #) (handler #)) (for-each (lambda # #) files)
598: 2* [for-each # ("chopin-op-25-01.ly")]
In
661: 3 (if (null? rest) (letrec ((lp #)) (lp list1))
665: 4 (begin (f (car l)) (lp (cdr l)))
666: 5* [# "chopin-op-25-01.ly"]
In
600: 6 [catch ly-file-failed # #]
In unknown file:
?: 7* [#]
In
600: 8* [ly:parse-file "chopin-op-25-01.ly"]
In chopin-op-25-01.ly:
205: 9* (paper-set-staff-size (* 6 mm))
chopin-op-25-01.ly:205:26: In expression (paper-set-staff-size (* 6 mm)):
chopin-op-25-01.ly:205:26: Unbound variable: paper-set-staff-size
Here's the error for compiling 2.4.1
rm -f
flex -Cfe -p -p -oout/lexer.cc lexer.ll
"lexer.ll", line 638: warning, -s option given but default rule can be matched
rm -f
out/lexer.cc:3457: warning: 'yy_start_stack_ptr' defined but not used
out/lexer.cc:3458: warning: 'yy_start_stack_depth' defined but not used
out/lexer.cc:3459: warning: 'yy_start_stack' defined but not used
out/lexer.cc:3461: warning: 'void yy_push_state(int)' declared `static' but never defined
out/lexer.cc:3464: warning: 'void yy_pop_state()' declared `static' but never defined
out/lexer.cc:3467: warning: 'int yy_top_state()' declared `static' but never defined
bison -o out/parser.cc parser.yy
mv -f parser.yy.tab.c out/parser.cc # bison 1.30
mv: cannot stat `parser.yy.tab.c': No such file or directory
make[1]: [out/parser.cc] Error 1 (ignored)
rm -f
out/parser.cc: In function `int yyparse(void*)':
out/parser.cc:5540: error: expected primary-expression before "__attribute__"
out/parser.cc:5540: error: expected `
" 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."
So are there any commercial entities using Rosegarden, or Lilypond?
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)
Methinks your attempt at wit has over-extended your faculties.
I did have Rosegarden running without alsa and jack but found that it crashed big time when I used the notation window. There was no indication of why, doing a demesg didn't help and KDE gave me the usual equivelent of a windows illegal operation message after it crashed.
Yes, BTW, I am dyslexic and find writing complex polyphony easier than the English language.
My original post was not a flame. All I was trying to say was that to write a great music notation GUI the kiss principle somehow gets missed by just about everyone. Look into (the late) Frederick Noads Mac program Speedscore, http://www.noad.com/Nsoft.htm he resisted midi for years...for good reason, too bad the guy who now owns the code won't let it out!
I will give Rosegarden another try though, as I do really enjoy causing software crashes. Gives me a good excuse to get out the pen and paper, and do real music notation!
The league for abused ESL bots
Ok, thanks for the clear explanation.
You're right you cannot run the notation GUI without also running it as a child of the main window, but why does it bother you? Did you know you can type "rosegarden myfile.rg" which automatically opens your previously saved composition from "myfile.rg", hit Control-A which selects all segments on all tracks and hit Enter which immediately opens the notation GUI? You can ignore the main window most of the time and do all your composing using the notation GUI which incidentally has improved a lot since two years ago.
If you compile Rosegarden after "configure --enable-debug", you can use "gdb rosegarden" to start it and "run --nofork" from inside gdb to run it. That should always get you a useful stack trace from gdb ("bt" command in gdb) if Rosegarden crashes.
I don't have a Mac so I can't try the software you mentioned. I'll look at the website instead.
But the problem is, Rosegarden *shouldn't* be frequently crashing, especially if the project is this mature. Not everyone knows how or wants to compile and debug applications in order to use them -- they're just going to give up.
Disclaimer... parent not written by original dyslexic musician!
"Rosegarden *shouldn't* be frequently crashing" Which version are you using? The old versions like 0.9.8 did have quite a few crashes but not the more recent ones. Try out 0.9.91. I haven't seen it crash yet.
If people insist on spending money for Windows, they can also spend money on programs for Windows - especially when relevant APIs are very different (MIDI and audio stuff). I've noticed a number of open source projects that provide the source for free (as in beer and freedom) but sell the (supported) Windows build. Sounds reasonable to me.
If I take the .lily out and use Lilyponds polyphonic abilities and special characters I should be able to effectively notate complex polyphony. Cross bar ties, as polyrythms in the inner voices are very important in my musical notation.
I am currently writing a piece for 6 voices, and setting some beautiful Canadienne Francais folk songs for orchestra, with the idea to combine the two.
Just put each voice in a different Rosegarden segment in the main window, and put each segment on a different track (if you want each stave to have only one voice) and then move some or all the segments onto the same tracks (if you want some staves to have more than one voice) and finally select all the overlapped segments using Control-A and re-open the notation GUI.
/usr/include headers to the latest Slackware 10.0 or latest versions. It's a straightforward upgrade from ftp.slackware.com
The gcc tool chain in Slack 8 has problems with modern C++. You'll definitely need to upgrade kde, qt autoconf, automake, gcc, libc and
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 do, the words are separate from the chords, with the chords commonly in groups of 4 bars per each line, as above.
Need a Linux consultant in New Orleans?
>...we neither have the time to fully document the code...
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 project, lack of good documentation causes time and quality losses to go through the roof.
It does take a bit of discipline. A couple rules of thumb help tremendously: 1) code must be commented the same day that it is written, and 2) never check in code that's not documented.
I use Rosegarden regularly and I love it. I wouldn't say it works flawlessly all the time, but certainly well enough to be getting on with some composition. I find it all relatively easy because I'm using AGNULA/DeMuDi - based on Debian GNU/Linux - which pretty much set the whole sound system up for me and installed all the applications, although I did compile this version of Rosegarden from source.
./ I don't see what's wrong with developing for a Linux Audio platform. Rosegarden does what it needs to do and does it well.
It's really worth considering double booting if you're a Windows user, because the beauty of Rosegarden is in its interaction with other Linux Audio tools. Windows & Mac already have plenty of Music software, I don't really understand the whingeing to be honest. If you can't/don't want to pay the price of a new version of Cubase or Logic, why not buy a copy of Fervent's 'Studio to Go!' and support the development of a wide range of alternatives.
I'm really grateful to Linux Audio Developers because now I have a complete home studio for an initial outlay of about a couple of hundred quid. It all depends on your perspective I guess. Getting used to Linux is a learning curve yes, but this is
Happy 'Customer'