From: Silvan <si...@wi...> - 2002-12-10 23:55:20
|
In the spirit of Open Source, release early, release often, I've put up a= =20 pre-release peek at my tutorial. My web host sucks, and rather than go=20 through their stupid web interface to upload all of these files into=20 different directories, five at a time, I just threw the whole thing up as= a=20 tarball. I'm hoping when it goes up for real somebody with a less obnoxi= ous=20 host can put it up... http://www.geocities.com/Paris/Rue/5407/tutorial-0.pre1.tar.gz I still have a long way to go, and am nowhere close to a release. The TO= DO=20 list is so long I won't even bore you with it, and everything is subject = to=20 change. I want to get you developers to look at it first, then I'll ment= ion=20 it on the user list. I've spent the majority of the last five days working on this thing, and = it's=20 starting to shape up pretty well. This look at what I've done so far sho= uld=20 give you an idea of whether or not this endeavor is worthwhile, and how I= =20 might make some improvements to what I've already done. I'm avoiding the Studio until it settles down more, and I'm avoiding audi= o=20 because I don't have a clue what's wrong with my setup that's causing RG = to=20 crash when I compile it with Jack. I'll put the stuff that doesn't work = off=20 until later, assuming that it will work some day, and then I can write ab= out=20 it. :) I'm nowhere close to being out of ideas about where to go with this (just= out=20 of time... damn job... hi ho hi ho and stuff), so you can expect much m= ore=20 to come. I'll diff future releases against this one to avoid having to=20 upload the entire thing by modem again. --=20 Michael McIntyre USDA zone 6b in SW VA, USA Silvan Pagan [si...@wi...] Linux Druid ---------[ registered Linux user #243621 ]--------- http://www.geocities.com/Paris/Rue/5407/index.html |
From: Richard B. <bo...@bo...> - 2002-12-11 07:52:32
|
On Tuesday 10 December 2002 23:55, Silvan wrote: > In the spirit of Open Source, release early, release often, I've put > up a pre-release peek at my tutorial. Excellent. I hope you don't mind but I've put it up here already: http://www.bownie.com/rosegarden/silvan There's certainly enough information in there to make it useful to loads of people as it stands. Nice work. Looking forward to more. B |
From: Guillaume L. <gla...@te...> - 2002-12-11 11:22:03
|
On Wednesday 11 December 2002 08:45, Richard Bown wrote: > > There's certainly enough information in there to make it useful to loads > of people as it stands. Nice work. Looking forward to more. I concur. I think it's worth putting up on sforge, where you could update it. Do you have an sforge account ? If not, I suggest you get one. Then we'll import your files in cvs (in a new component, say rosegarden_tutorial), and I'll set up a script so the files are mirrored on the sforge website daily. Then we add a link to the tutorial from the main site, and also a nice "Show Tutorial" menu item on rg itself. Only thing, it would be nice to use the CSS from the main site, so as to have a common look & feel. -- Guillaume http://www.telegraph-road.org |
From: Chris C. <ca...@al...> - 2002-12-11 11:36:56
|
Silvan wrote: > In the spirit of Open Source, release early, release often, I've put > up a pre-release peek at my tutorial. This is really good stuff. I'm impressed with the number of illustrative pictures -- they're what I always find most of a pain to produce myself when I write documentation. The conversational style comes across very well too. I think the Background section could be clearer. You could probably do with some sort of list of exactly what you're about to try to achieve -- it took me a couple of reads through it before I understood why you were spending so much time on notation when you'd started by saying you wanted to make a CD. (When I read the bit about the CD, I'd assumed your aim would be to get the best performance-quality MIDI, so I was surprised that you were doing things like quantization for notation, until I re-read and realised that was the part that had to be printed out and played on a real instrument. I realise all the facts are there, but it could be more explicit.) I also found the Tweaking the Import section (about program numbers) a bit confusing, probably because this sort of thing will always depend on what instruments you have and what was in the MIDI file (which I haven't actually looked at yet), and because I don't really know anything about GS drum kit programs (I assume you're talking about GS here?). I'm sure this stuff is rather hard to write a tutorial about, just because it does depend so much on the user. Other trivial typos and glitches: "stacatto" should be "staccato". You describe the notation view's Note Font menu option as not available graphically... I thought it was on the same toolbar as the Size sliders. The large version of the notation view screenshot doesn't seem to be there on Bownie's server so I can't cross-check with that -- perhaps the font dropdown has just got squished out because there wasn't enough space. And finally, with regard to the discussion of overlapping segments, the text gives the impression that RG won't allow you to assign more than one track to the same channel, which isn't true at all. I was also about to pedantically correct your spelling of "practicing" to "practising", but was amazed to discover that the former is correct in the US. (Google even tries to correct my UK spelling back to the US version if I search for it.) Damn. At least I got the "staccato" pedantry in, though. I think those are all my complaints, anyway. I look forward to reading some more. It'd be nice to get a version of this into the Rosegarden help file as well, perhaps -- but we can worry about that sort of stuff later. Chris |
From: Silvan <si...@wi...> - 2002-12-12 07:17:53
|
On Wednesday 11 December 2002 06:02 am, Chris Cannam wrote: > This is really good stuff. I'm impressed with the number of > illustrative pictures -- they're what I always find most of a pain > to produce myself when I write documentation. The conversational > style comes across very well too. Just takes discipline... :) I'm trying to cut out a bit of whatever and= slap=20 it in whenever I talk about something that requires more than a few words= to=20 describe. > I think the Background section could be clearer. You could > probably do with some sort of list of exactly what you're about > to try to achieve -- it took me a couple of reads through it First I need to figure out exactly what I'm going to achieve... I agree = with=20 you 100%. I won't really know until it's done though, since I just jumpe= d in=20 and started writing about what I was doing, rather than deciding on a=20 framework and then populating it with stuff. I'll eventually figure out=20 where to stick everything so that it's cohesive. > out and played on a real instrument. I realise all the facts > are there, but it could be more explicit.) Noted... Part of the reason it seems aimless is because it _is_ aimless.= I=20 haven't really fooled with that composition in a long time, and don't rea= lly=20 want to do anything with it in particular, so I'm seeing what I can do wi= th=20 it with the goal of making use of as many RG features as possible along t= he=20 way, even when I have to make up an excuse to use those features. I've g= ot a=20 lot further to go with it than what I've done so far. Also a question... RG doesn't seem to interpret the performance instruct= ions=20 in the notation. Is that planned? =20 Notworthy Composer, for example, did at least a rudimentary job of=20 interpreting almost everything at playback. Staccato notes were shortene= d=20 fractionally, accented notes got higher velocity, etc. It didn't interpr= et=20 everything, but playback didn't leave a lot to the imagination either. I'm asking maily because of how I'll deal with it. If this is planned, I= 'll=20 leave it alone and come back when that works. If it isn't planned, I'll = take=20 the users through creating a performance track and hand-editing the data = with=20 the Matrix to manually implement this sort of thing for situations where = they=20 want one clean track to use for generating a nice score, and a dirty trac= k=20 for a good MIDI performance. As a half-assed musician, I like being able to do that kind of thing so I= can=20 hear what I'm supposed to be doing. I don't read very well. I'm much mo= re=20 of a "by ear" player, and I don't have a lot of musical discipline. I ca= n't=20 read rhythms worth a damn unless they're simple, so I need to hear them. = =20 Thus even if the part is supposed to be printed and played live, I'll sti= ll=20 want to hear an accurate performance. That's one of the things I use MID= I=20 for. Until I hear somebody else play a piece of music, I usually can't g= et=20 it, even though I'm playing all the right notes. (This isn't a feature request per se. I realize that interpreting the=20 notation is a big can of worms. I'm just asking what's in the works... =20 Maybe RG already interprets some stuff, and I just didn't add the right m= arks=20 to discover that fact... Call it "if it doesn't do it, I'm not whining a= bout=20 it but I certainly wouldn't mind seeing it.") > (I assume you're talking about GS here?). I'm sure this stuff > is rather hard to write a tutorial about, just because it does > depend so much on the user. I figure I'll add a "My Gear" section or something, but yes, this probabl= y=20 does need more thought. > Other trivial typos and glitches: "stacatto" should be "staccato". Not in my splel chker... I'll fix it. > You describe the notation view's Note Font menu option as not > available graphically... I thought it was on the same toolbar Duhhhhhhhhhhh. BTW. CVS from two days ago, click on that button and watch it crash. > segments, the text gives the impression that RG won't allow > you to assign more than one track to the same channel, which > isn't true at all. Don't know what I was thinking really. Assign channel 10, un-check "bank= " and=20 un-check "program" and it should transmit nothing, right? So I just dial= up=20 the channel, and it won't try to tamper with whatever program that channe= l is=20 already using. Seems to work that way. Might make this less confusing by removing the name from the drop-down li= st=20 when that attribute is turned off... Currently I'm looking at [ ] bank GS Capital Tones [ ] program Harpsichord channel 10 It's working, but it isn't immediately obvious that that track isn't tryi= ng to=20 send a conflicting patch change. Maybe keep the state so that if you [x]= a=20 box it will restore what's associated with the track, but if you [ ] the = box,=20 the list beside it goes blank or displays "none" or something... Anyway, I'll re-think that bit of the tutorial. May as well do that, sin= ce I=20 have the pictures, but I'll put it in a different context. > I was also about to pedantically correct your spelling of > "practicing" to "practising", but was amazed to discover that I don't even try to touch hemidemisemiuberdubersuperflummies either. I'm= glad=20 you got a chance for a bit of pedantry, though. Hey, I owe you that much= at=20 least. :) > I think those are all my complaints, anyway. I look forward to > reading some more. It'd be nice to get a version of this into > the Rosegarden help file as well, perhaps -- but we can worry > about that sort of stuff later. Yeah, let me get it further along. Thanks for the input. I probably won't have another five-day stretch to work on this for some t= ime=20 to come, but I'll work on it as time allows, and I'll post again when I h= ave=20 something else to look at. --=20 Michael McIntyre USDA zone 6b in SW VA, USA Silvan Pagan [si...@wi...] Linux Druid ---------[ registered Linux user #243621 ]--------- http://www.geocities.com/Paris/Rue/5407/index.html |
From: Silvan <si...@wi...> - 2002-12-12 07:41:01
|
On Wednesday 11 December 2002 02:45 am, Richard Bown wrote: > Excellent. I hope you don't mind but I've put it up here already: > > http://www.bownie.com/rosegarden/silvan > > There's certainly enough information in there to make it useful to load= s > of people as it stands. Nice work. Looking forward to more. Nope, I don't mind. It's gratifying, in fact. It also gives me motivati= on to=20 get it to a better condition quickly, because it's not _really_ ready for= =20 human consumption yet... It's going to get a lot better as it ages, but = I'm=20 glad to see everyone likes the initial offering. I just don't have the skills to help you code this thing, but I can hamme= r=20 this stuff out all day long, and the time just flies by. I've barely sle= pt=20 in the past several days. It's good to give a little something back, and= it=20 gives me an excuse to talk. You've doubtless noticed that I love to hear= =20 myself talk. :) --=20 Michael McIntyre USDA zone 6b in SW VA, USA Silvan Pagan [si...@wi...] Linux Druid ---------[ registered Linux user #243621 ]--------- http://www.geocities.com/Paris/Rue/5407/index.html |
From: Chris C. <ca...@al...> - 2002-12-12 17:37:06
|
Michael -- I notice the "bugs" file in your tutorial directory=20 contains a couple of interesting ones. You have one saying that if=20 you try to open two segments at once in the notation view, it doesn't=20 work. Are they on different tracks? Do they overlap? You should=20 certainly be able to open any number of segments at once, and I do so=20 routinely. Even if they're on the same track, it should work fine=20 unless they overlap, in which case it won't really bother to=20 reconcile them and you'll get a bit of a mess. Also, the reason your Annotation text doesn't appear is probably that=20 you have annotations switched off in the settings menu. There should=20 be some sort of visible cue in the status bar or somewhere that you=20 might be missing some annotations, but at the moment there isn't. Chris |
From: Silvan <si...@wi...> - 2002-12-12 08:04:47
|
On Wednesday 11 December 2002 06:21 am, Guillaume Laurent wrote: > I concur. I think it's worth putting up on sforge, where you could upda= te > it. Do you have an sforge account ? If not, I suggest you get one. Then Yes, but I don't know how to do anything more with it than submit bug rep= orts. > we'll import your files in cvs (in a new component, say > rosegarden_tutorial), and I'll set up a script so the files are mirrore= d on > the sforge website daily. Then we add a link to the tutorial from the m= ain > site, and also a nice "Show Tutorial" menu item on rg itself. Sounds good... I have no experience working with CVS from the perspectiv= e of=20 someone originating the changes, but I can figure it out with a little=20 direction. > Only thing, it would be nice to use the CSS from the main site, so as t= o > have a common look & feel. CSS? Colors and Screen Shots? CSS Cascading Style Sheets (HTML, WWW, JavaScript) Oh. You scared me. I thought you were going to ask me to re-do 35 pixma= ps=20 using the aqua-like theme or something, and I was going to have to=20 demonstrate some of the things I can say in French that my young daughter= =20 shouldn't hear. :) Yeah, that's no problem. I don't know a CSS from a hole in the wall, but= I'll=20 figure it out. --=20 Michael McIntyre USDA zone 6b in SW VA, USA Silvan Pagan [si...@wi...] Linux Druid ---------[ registered Linux user #243621 ]--------- http://www.geocities.com/Paris/Rue/5407/index.html |
From: Chris C. <ca...@al...> - 2002-12-12 10:09:07
|
Silvan wrote: > RG doesn't seem to interpret the performance instructions > in the notation. Is that planned? Yes, but you won't necessarily get it very soon. It will probably take an explicit menu operation ("interpret dynamics in selection" or something) which will set the notes' velocities and durations according to reasonable guesses. (This is another feature that Rosegarden 2.1 actually had, but the code doesn't transfer across very directly.) It's one of my top-three features I want to do, but considering the amount of time I have available just at the moment... >>You describe the notation view's Note Font menu option as not >>available graphically... I thought it was on the same toolbar > > Duhhhhhhhhhhh. > > BTW. CVS from two days ago, click on that button and watch it crash. Hmm. Doesn't crash for me here. I assume you mean "change the value in that dropdown" rather than just click on it? And yet the menu option in the View menu doesn't cause a crash? Can you file a report with a stack trace? Chris |
From: Chris C. <ca...@al...> - 2002-12-12 21:36:16
|
On Thursday 12 December 2002 10:08, Chris Cannam wrote: > Silvan wrote: > > BTW. CVS from two days ago, click on that button and watch it > > crash. > > Hmm. Doesn't crash for me here. I assume you mean "change the > value in that dropdown" rather than just click on it? I think I've worked it out. Your flute segment crashes when displayed=20 with the rg21 font because there's a C-major (or A-minor) key in it=20 that the code stupidly tries to make into a zero-width pixmap. Should be fixed in CVS now. Chris |
From: Silvan <si...@wi...> - 2002-12-12 23:24:40
|
On Thursday 12 December 2002 04:34 pm, Chris Cannam wrote: > I think I've worked it out. Your flute segment crashes when displayed > with the rg21 font because there's a C-major (or A-minor) key in it > that the code stupidly tries to make into a zero-width pixmap. > > Should be fixed in CVS now. OK, I guess I'll hold off on that bug report. :) I have some ready to file when I get around to it. Picky things... --=20 Michael McIntyre USDA zone 6b in SW VA, USA Silvan Pagan [si...@wi...] Linux Druid ---------[ registered Linux user #243621 ]--------- http://www.geocities.com/Paris/Rue/5407/index.html |
From: Guillaume L. <gla...@te...> - 2002-12-12 13:18:24
|
On Thursday 12 December 2002 09:04, Silvan wrote: > On Wednesday 11 December 2002 06:21 am, Guillaume Laurent wrote: > > I concur. I think it's worth putting up on sforge, where you could update > > it. Do you have an sforge account ? If not, I suggest you get one. Then > > Yes, but I don't know how to do anything more with it than submit bug > reports. Well, cvs ain't very difficult. I've added you to the list of RG members, and already imported your tutorial in cvs (except for the get-rg.tgz which I've unpacked). Here's to get you started for cvs access : https://sourceforge.net/docman/display_doc.php?docid=768&group_id=1 You need an ssh client, and to generate an ssh key. It's a bit tedious to set up at first but then it's fairly innocuous. Once you're done cvs checkout your tutorial like you do for the RG sources : cvs -z3 -d "sil...@cv...:/cvsroot/rosegarden" co tutorial and go ahead. > Sounds good... I have no experience working with CVS from the perspective > of someone originating the changes, but I can figure it out with a little > direction. It's dead simple. Once you have checked the files out, you simply edit them and use 'cvs commit' to upload your changes. KDE has a nice cvs GUI called cervisia, I suggest you try it. I'll set up a cron job on my machine to mirror the files on rosegarden.sf.net, so you won't have to worry about that. > Yeah, that's no problem. I don't know a CSS from a hole in the wall, but > I'll figure it out. Just see how the html files in docs/web/site look like. Basically it should just be a matter of cp'ing rose.css and fiddling a bit with the html. Don't worry too much about that part for the moment. Don't hesitate to post here in case of problems. -- Guillaume http://www.telegraph-road.org |
From: Richard B. <bo...@bo...> - 2002-12-12 13:43:00
|
On Thursday 12 December 2002 13:18, Guillaume Laurent wrote: > I'll set up a cron job on my machine to mirror the files on > rosegarden.sf.net, so you won't have to worry about that. URL? BTW could we move the web stuff to its own module do you think too? Someone was complaining recently that it's a big and unnecessary download and I do tend to agree. And what with you being the CVS whizz and all.. B |
From: Guillaume L. <gla...@te...> - 2002-12-12 14:42:16
|
On Thursday 12 December 2002 14:35, Richard Bown wrote: > On Thursday 12 December 2002 13:18, Guillaume Laurent wrote: > > I'll set up a cron job on my machine to mirror the files on > > rosegarden.sf.net, so you won't have to worry about that. > > URL? It's not there yet :-). I'll put it on http://rosegarden.sf.net/tutorial, probably, then add a link on the main pages. > BTW could we move the web stuff to its own module do you think too? > Someone was complaining recently that it's a big and unnecessary > download and I do tend to agree. We could avoid packing it in the release tarballs, but moving it to a seperate module will just spare a 732K download (300K compressed) when you checkout the whole cvs tree, which isn't something you do very often. And as I said, that won't help people who download the daily cvs tarball from sforge. > And what with you being the CVS whizz and all.. Well, it's already in a seperate module, "rosegarden" is actually a meta-module holding several others, including docs. So I could just remove docs from it, but that would remove the whole thing. Moving 'web' to a seperate module will require asking the sforge guys. -- Guillaume http://www.telegraph-road.org |
From: Guillaume L. <gla...@te...> - 2002-12-12 19:18:00
|
On Thursday 12 December 2002 14:35, Richard Bown wrote: > On Thursday 12 December 2002 13:18, Guillaume Laurent wrote: > > I'll set up a cron job on my machine to mirror the files on > > rosegarden.sf.net, so you won't have to worry about that. > > URL? Tutorial is up on http://rosegarden.sf.net/tutorial, and the link is added on the navbar for the main site (Chris, can you push rosenav.js ?). Silvan, I'll set up the rsync cronjob once you're up to speed with cvs. -- Guillaume. http://www.telegraph-road.org |
From: Guillaume L. <gla...@te...> - 2002-12-12 19:33:22
|
> Tutorial is up on http://rosegarden.sf.net/tutorial, and the link is added > on the navbar for the main site While I was at it I also cp'ed rose.css and included it in the tutorial, but I can't get the background color to change... Ah well. -- Guillaume. http://www.telegraph-road.org |
From: Silvan <si...@wi...> - 2002-12-14 04:34:46
|
On Thursday 12 December 2002 02:33 pm, Guillaume Laurent wrote: > > Tutorial is up on http://rosegarden.sf.net/tutorial, and the link is > > added on the navbar for the main site > > While I was at it I also cp'ed rose.css and included it in the tutorial= , > but I can't get the background color to change... Ah well. I've got it. It's going to be a PITA to get your CSS and stuff to play n= ice=20 with Open Office, but I've worked up a script to automate the process. I= t's=20 looking OK, and I think that's going to work out. I'll figure it out. I need to go do the CVS thing and stuff to get up to= =20 speed with that before I start doing anything else anyway. I'm about to = do=20 that. I'm just trying to find that other message you sent. I know I hav= e it=20 somewhere. :) --=20 Michael McIntyre USDA zone 6b in SW VA, USA Silvan Pagan [si...@wi...] Linux Druid ---------[ registered Linux user #243621 ]--------- http://www.geocities.com/Paris/Rue/5407/index.html |
From: Silvan <si...@wi...> - 2002-12-13 00:50:41
|
On Thursday 12 December 2002 11:49 am, Chris Cannam wrote: > Michael -- I notice the "bugs" file in your tutorial directory > contains a couple of interesting ones. You have one saying that if That's my scratch pad... Not really part of the tutorial, and it shouldn= 't=20 really have been in there. I was going to submit those properly one of t= hese=20 days... But since you already found it, let's talk notation editor bugs.= =2E. First... Found one, and figured it out. Try to export one of my samples= to=20 =2Ely and notice that the "Orchestral bass, crash & snare" breaks Lilypon= d. =20 Export needs to deal with that &, because it's what's causing the lilypon= d=20 export problem I referred to awhile back. Changed the track name, and it= =20 worked fine. ! Misplaced alignment tab character &. <argument> ...MMBo \hbox {Orchestral bass, crash & snare} l.439 ...MBo\hbox{Orchestral bass, crash & snare}} > you try to open two segments at once in the notation view, it doesn't > work. Are they on different tracks? Do they overlap? You should OK, you have my files, so let's test. Today's CVS as of an hour ago... Open rgsamples/step2.rg Select the "Flute" track. Both of the flute segments should be selected,= and=20 they don't overlap in any way. Open as Notation. See the mess? It's a mess here. I'll send you a screenshot if you can't= =20 repeat it. Let me load the cleaned up version. step8.rg This time I have much less ugly notes floating in the ether, and bar line= s. =20 Still no lines for the staff in the first segment, and the first measure = is=20 still screwed up. Definitely repeatable. ( Oh wow, you mean I can edit segments on two different tracks simultaneous= ly=20 too??? Cool! I didn't know that. In fact, I thought I tried that, and = it=20 didn't work. Maybe I misremember. Anyway, it works now, and I'll docume= nt=20 it in the tutorial. Tasty. ) Um... I get a lot of doubled clefs too. Still with step8.rg, highlight = the=20 big segments on tracks 4 and 5, open as notation, and the notation render= s=20 OK, except there are two treble clefs on the first staff, and a very smal= l ?=20 on the F line just past the time signature. I've seen the doubled clef t= hing=20 a lot, it's just that I wasn't able to keep the Notation Editor running l= ong=20 enough to do much with it until recently. :) View -> Page Layout is borked. It looks like it's trying to make the pag= e=20 about 40 measures wide. In-house printing doesn't work either. You prob= ably=20 already know this. > Also, the reason your Annotation text doesn't appear is probably that > you have annotations switched off in the settings menu. There should Yeah, OK. Notice I said "bug? feature?" So don't think I always think = bug. =20 :) Reminds me... wishlist: some way to export just certain staffs to lilyp= ond=20 for printing. For this project, eg, I only want to export the flute staf= f. =20 Could be done from the Notation Editor instead of the main window. Expor= t=20 what I'm looking at now, and ignore everything else. Or else a dialog wi= th=20 checkboxes for which tracks to export. wishlist: Being able to print right out of RG would be nice too. Could y= ou=20 avoid writing your own print engine by piping it all through a script to=20 lilypond? eg instead of the internal print engine that doesn't work yet= ,=20 you could file -> print and that would export to /tmp/$RANDOM.ly, process= it=20 with ly2dvi, then dump the output via lpr or whatever. file -> print pre= view=20 could do the same, then run kghostview (or configurable viewer) to view t= he=20 =2Eps file. That way you could use lilypond to do the work without users= =20 having to deal with it directly. I have all the scripts to do this job, = but=20 there's no way to automate dealing with the export from within the GUI, s= o I=20 have to export and then run ly2lpr or ly2kgv manually. Would just be=20 convenient. Maybe don't replace the mainline print stuff, but have file = ->=20 export [ ] process with external program ____________ or something... --=20 Michael McIntyre USDA zone 6b in SW VA, USA Silvan Pagan [si...@wi...] Linux Druid ---------[ registered Linux user #243621 ]--------- http://www.geocities.com/Paris/Rue/5407/index.html |
From: Silvan <si...@wi...> - 2002-12-13 01:06:36
|
On Thursday 12 December 2002 08:18 am, Guillaume Laurent wrote: > Well, cvs ain't very difficult. I've added you to the list of RG member= s, > and already imported your tutorial in cvs (except for the get-rg.tgz wh= ich > I've unpacked). OK... > Here's to get you started for cvs access : > > https://sourceforge.net/docman/display_doc.php?docid=3D768&group_id=3D1 > > You need an ssh client, and to generate an ssh key. It's a bit tedious = to > set up at first but then it's fairly innocuous. Whee. OK, I'll go fool with it. Actually, not tonight. Wife's recoveri= ng=20 from surgery. Over the weekend. I don't have anything new to add yet=20 anyway. I've done ssh with keys stuff before, so I can figure it out. > It's dead simple. Once you have checked the files out, you simply edit = them > and use 'cvs commit' to upload your changes. KDE has a nice cvs GUI cal= led > cervisia, I suggest you try it. OK, I got it. I'll have to play with it. Can I commit just the one modu= le? =20 I have extra bits of crap in my rosegarden directory that relate to the=20 working of my get-rg script's automatic package creation/management, and = I=20 don't want those to show up in CVS. > Just see how the html files in docs/web/site look like. Basically it sh= ould > just be a matter of cp'ing rose.css and fiddling a bit with the html. D= on't > worry too much about that part for the moment. I'm going to steal your header. I think I can get that working in fairly= =20 short order. It may be the only thing I actually do get done today. No=20 time. Almost time to go back to work again. Plus I'm trying my hand at=20 being a nurse. Reminds me, she needs her medication... While I sat in various waiting rooms, I sketched out an outline for the r= est=20 of the tutorial. Better organization and stuff. It'll be good. When I get all this CVS stuff working for me and I begin work on the tuto= rial=20 again, I'll start making incremental updates regularly. > Don't hesitate to post here in case of problems. I'll see how far I get with what you've said... Tomorrow, Saturday... A= s=20 time allows. I guess you guys can relate to that bit, and I don't need t= o=20 make excuses. I'll deliver. Looking forward to getting it to a more sta= ble=20 state where it can continue to develop as RG does. --=20 Michael McIntyre USDA zone 6b in SW VA, USA Silvan Pagan [si...@wi...] Linux Druid ---------[ registered Linux user #243621 ]--------- http://www.geocities.com/Paris/Rue/5407/index.html |
From: Chris C. <ca...@al...> - 2002-12-13 12:29:15
|
Silvan wrote: > notice that the "Orchestral bass, crash & snare" breaks Lilypond. > Export needs to deal with that & File that one as a bug assigned to Hans. The rest are definitely me, though... > OK, you have my files, so let's test. Today's CVS as of an hour > ago... > > Open rgsamples/step2.rg > > Select the "Flute" track. Both of the flute segments should be > selected, and they don't overlap in any way. > > Open as Notation. > > See the mess? Oh yes. Nasty. Looks like the width of the first segment's staff has been completely miscalculated. > ( Oh wow, you mean I can edit segments on two different tracks > simultaneously too??? Cool! I didn't know that. Yes, you can... although I'm noticing now that the editing tools only appear to work on one staff, in your example, although they work on either in something like glazunov.rg. Sigh. > Um... I get a lot of doubled clefs too. Yeah, we really do seem to have two clefs there. That's quite strange, because MIDI has no clef event so they can't have come from the MIDI file, and although we do try to guess a clef for each segment imported from MIDI, we only do it once... ooh, and if I just import ultima.mid, I only see one clef. Weird. I'm pretty sure you didn't deliberately add the other one, so I'll investigate, maybe it's some sort of file save/load problem. There's also an old problem visible here with time signatures sometimes being duplicated before the start of the staff. > a very small ? on the F line just past the time > signature. That's a controller event -- the notation view shows any event it doesn't know as a small ?. I should add an option to turn that off. It's handy sometimes, because you can double-click on it to open an event editing window. > View -> Page Layout is borked. Ugh! And it is in glazunov.rg too. That's a serious regression. > In-house printing doesn't work either. > You probably already know this. Yes, I know that. Those two wishlist items look fair enough -- why not enter them in the Feature Requests tracker on sourceforge? Chris |
From: Silvan <si...@wi...> - 2002-12-14 09:29:15
|
On Friday 13 December 2002 07:27 am, Chris Cannam wrote: > File that one as a bug assigned to Hans. I can assign it to a category, but that's as far as I can go at present, = so I=20 left it unassigned. > Yes, you can... although I'm noticing now that the editing tools > only appear to work on one staff, in your example, although they > work on either in something like glazunov.rg. Sigh. Damn user data. :) No, the editing tools seem to be working OK here. Well. Sort of. I was deleting and adding notes to both staffs, but I cr= ashed=20 it eventually. Repeatable, but I don't see the pattern. I get this output: rosegarden: RosegardenCanvasView::polish() rosegarden: Returning chord-label ruler width as 10200.000000 RosegardenGUI - Failed to contact Rosegarden sequencer rosegarden: Sequencer exited rosegarden: RosegardenGUIDoc::saveIfModified() rosegarden: RosegardenGUIApp::slotSaveOptions() rosegarden: ~RosegardenGUIApp() rosegarden: ~RosegardenGUIDoc() rosegarden: ~RosegardenGUIView() (it just crashes here... no segfault message) When you guys ask for a stack trace, what do you mean? Rather, how do I=20 produce one? Um... Let's see... No, I can't get it to repeat at will. I'll get CVS=20 before I spend any more time on it. The only thing I see is the cursor. It's only coming down to the bottom = of=20 the first staff, which could be a problem if you're editing the bottom of= six=20 staffs or something. Also, when one staff is a lot longer, there are tho= se=20 ugly extra long bar lines, if I didn't mention that already. > if I just import ultima.mid, I only see one clef. Weird. I'm > pretty sure you didn't deliberately add the other one, so I'll > investigate, maybe it's some sort of file save/load problem. Maybe so. I've seen it crop up quite often. I'll watch it too, and see = if=20 there's a pattern... > That's a controller event -- the notation view shows any event > it doesn't know as a small ?. I should add an option to turn > that off. It's handy sometimes, because you can double-click on > it to open an event editing window. OK. Yes, an option to turn that off is probably good, but leaving the fe= ature=20 in sounds like a plan, now that I know what it does. > Those two wishlist items look fair enough -- why not enter them > in the Feature Requests tracker on sourceforge? Done... --=20 Michael McIntyre USDA zone 6b in SW VA, USA Silvan Pagan [si...@wi...] Linux Druid ---------[ registered Linux user #243621 ]--------- http://www.geocities.com/Paris/Rue/5407/index.html |
From: Guillaume L. <gla...@te...> - 2002-12-14 09:52:11
|
On Saturday 14 December 2002 10:27, Silvan wrote: > When you guys ask for a stack trace, what do you mean? Rather, how do I > produce one? From your favorite terminal : export KDE_DEBUG=1 (or setenv if you're using tcsh - this disables the KDE crash handler) Start rosegarden, reproduce the crash. You should now have a nice core file in your current directory, named either "core" or "core.<number>". Then run gdb rosegarden <name-of-core-file> and once you get the gdb prompt, type "where". The output is the stack trace. I'll add that to the faq. -- Guillaume. http://www.telegraph-road.org |
From: Guillaume L. <gla...@te...> - 2002-12-13 12:32:28
|
On Friday 13 December 2002 02:06, Silvan wrote: > OK, I got it. I'll have to play with it. Can I commit just the one > module? commit is a per-file operation. You can commit several files at once, of course. > When I get all this CVS stuff working for me and I begin work on the > tutorial again, I'll start making incremental updates regularly. Great. Thanks a lot for your help. :-) -- Guillaume http://www.telegraph-road.org |
From: Silvan <si...@wi...> - 2002-12-14 17:04:28
|
On Friday 13 December 2002 07:32 am, Guillaume Laurent wrote: > > When I get all this CVS stuff working for me and I begin work on the > > tutorial again, I'll start making incremental updates regularly. > > Great. Thanks a lot for your help. :-) Thanks for _letting_ me help. I need to get into sourceforge though to establish myself before I can ge= t=20 with the program. I think I mentioned already that the silvan-silvan acc= ount=20 is defunct and untouchable, and I'm using the dmmcintyr account. I'd hav= e=20 mentioned it sooner, but it took me a moment to realize where you got the= =20 "silvan-silvan" from when you described this earlier. As soon as someone makes that switch I'll get on board with CVS. I think= I=20 know the magic words to say to get it all going once I can ssh into=20 sourceforge. --=20 Michael McIntyre USDA zone 6b in SW VA, USA Silvan Pagan [si...@wi...] Linux Druid ---------[ registered Linux user #243621 ]--------- http://www.geocities.com/Paris/Rue/5407/index.html |
From: Guillaume L. <gla...@te...> - 2002-12-14 17:39:32
|
On Saturday 14 December 2002 18:04, Silvan wrote: > On Friday 13 December 2002 07:32 am, Guillaume Laurent wrote: > > > When I get all this CVS stuff working for me and I begin work on the > > > tutorial again, I'll start making incremental updates regularly. > > > > Great. Thanks a lot for your help. :-) > > Thanks for _letting_ me help. That's the whole point of this thing, actually :-). > As soon as someone makes that switch I'll get on board with CVS. I think I > know the magic words to say to get it all going once I can ssh into > sourceforge. I did the change already, and mailed you about it but couldn't reach you (cf. my mail on rg-user). -- Guillaume. http://www.telegraph-road.org |