Menu
▾
▴
rosegarden-devel
|
From: Richard B. <ric...@fe...> - 2004-02-25 12:18:46
|
Ok then, we need to get another release out of the door soon and we still have some showstoppers. Namely: * Ghost Notes, flakey mute/soloing points to a mmapped refresh problem somewhere. We also have the situation whereby recorded MIDI events can turn up in not only the newly recorded Segment but future ones too. Lots of current problems would probably be cleared up by a good examination of the refresh system to ensure the sequencer has the latest data. * Settings Amnesia. Two cases of it - the normal one whereby window settings are lost and also in the new case keyboard shortcuts are lost. * Audio Mixer to tidy up and finish off along with audio routing, plugins and whatever else Chris is doing. Audio autosplit and audio splitting on segment canvas is also dodgy and needs attention. * Ensuring MIDI and Audio Recording are working OK. Punch in record. Those for me are all pretty high priority bugs or partially completed features that need tidying up for a good quality next release. Anything else? The next release should really try to be approaching beta quality - the only additional features after that release I can think of for 1.0 is a dinky MIDI mixer window. Again, anything else? Looking at the old task_lists/1.0_release.txt I'd say we're almost there. I shall update that with what I've mentioned here and move out the stuff we've already done. Like I say though, it'd be good to concentrate on a few things as above to enable us to ship a near beta release pretty soon. R |
|
From: William <ros...@li...> - 2004-02-25 12:45:54
|
Richard Bown <ric...@fe...> wrote: > >some showstoppers. Namely: > [...] >Anything else? One area of troublesome bugs which you didn't mention is the notation editor. It's got a lot better in recent CVS but there are still some real showstoppers. Recently I found several new serious bugs in the notation editor (CVS). I think the problem is bad enough to make RG unusable for notation editing. Clearly I need to log them all on sf, though I'd appreciate some feedback here on the list beforehand. These bugs are different from long series of bug reports which you probably recall I posted to the list before Christmas and which I had planned to log on the sf bug trackers. The main issue holding up the logging on sf is that many of the bugs seem to have changed or even disappeared. When I've confirmed the bugs over the weekend I'll look at logging them on sf. BTW, is it only Chris who works on the notation editor? It could do with all hands on deck so to speak. >The next release should really try to be approaching beta quality - the only >additional features after that release I can think of for 1.0 is a dinky MIDI >mixer window. Again, anything else? Looking at the old >task_lists/1.0_release.txt I'd say we're almost there. I shall update that >with what I've mentioned here and move out the stuff we've already done. Notation bugs excepted, I'd agree that RG is looking very promising. Isn't it beta quality now? William |
|
From: Richard B. <ric...@fe...> - 2004-02-25 12:58:11
|
On Wednesday 25 February 2004 12:39, William wrote: > One area of troublesome bugs which you didn't mention is the notation > editor. It's got a lot better in recent CVS but there are still some real > showstoppers. Recently I found several new serious bugs in the notation > editor (CVS). I think the problem is bad enough to make RG unusable for > notation editing. Clearly I need to log them all on sf, though I'd > appreciate some feedback here on the list beforehand. Send them along. We need to reconcile a load of bugs on SF too to get our priorities straight. To that end I was trying to focus us main developers on the important few showstoppers to get it finished off. > BTW, is it only Chris who works on the notation editor? Chris does everything now - he's the bitch. But yes and no, complex fiddly notation bugs where you have to know what you're talking about are reserved for him or maybe Silvan, anything more general or crash laden any of us can take a look at. > It could do with all hands on deck so to speak. Chris is ill in bed so I'm letting him off for a day or so. > Notation bugs excepted, I'd agree that RG is looking very promising. > Isn't it beta quality now? Well almost - just want to iron out the obvious stupid bugs and as many easy crashes as we can before we go officially beta. Plus beta releases should only really revolve around fixing bugs - and we have features to complete before then. R |
|
From: William <ros...@li...> - 2004-02-25 15:45:08
|
Richard Bown <ric...@fe...> wrote: > >Chris does everything now - he's the bitch. >Chris is ill in bed so I'm letting him off for a day or so. I think you've explained the reason :) William |
|
From: Silvan <dmm...@us...> - 2004-02-25 15:31:10
|
On Wednesday 25 February 2004 07:49 am, Richard Bown wrote: > Chris does everything now - he's the bitch. But yes and no, complex fiddly > > It could do with all hands on deck so to speak. > > Chris is ill in bed so I'm letting him off for a day or so. Does his wife/girlfriend/SO know he's your bitch? Isn't she jealous? -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ |
|
From: Richard B. <ric...@fe...> - 2004-02-25 15:38:52
|
On Wednesday 25 February 2004 15:21, Silvan wrote: > Does his wife/girlfriend/SO know he's your bitch? Isn't she jealous? This whole concept could probably fall under "Liasing with the Hot Librarian". R |
|
From: Silvan <dmm...@us...> - 2004-02-25 15:41:22
|
On Wednesday 25 February 2004 10:29 am, Richard Bown wrote: > On Wednesday 25 February 2004 15:21, Silvan wrote: > > Does his wife/girlfriend/SO know he's your bitch? Isn't she jealous? > > This whole concept could probably fall under "Liasing with the Hot > Librarian". I'm not sure whether to laugh or hide. -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ |
|
From: Guillaume L. <gla...@te...> - 2004-02-25 13:10:46
|
On Wednesday 25 February 2004 13:09, Richard Bown wrote: > * Settings Amnesia. Two cases of it - the normal one whereby window > settings are lost and also in the new case keyboard shortcuts are lost. I'll need a lot more input from people experiencing these before I can do anything beyond just guessing. At least the contents of the settings files (config/rosegardenrc and share/apps/rosegarden/*.rc) -- Guillaume http://www.telegraph-road.org |
|
From: Richard B. <ric...@fe...> - 2004-02-25 13:16:29
|
On Wednesday 25 February 2004 13:01, Guillaume Laurent wrote: > On Wednesday 25 February 2004 13:09, Richard Bown wrote: > > * Settings Amnesia. Two cases of it - the normal one whereby window > > settings are lost and also in the new case keyboard shortcuts are lost. > > I'll need a lot more input from people experiencing these before I can do > anything beyond just guessing. At least the contents of the settings files > (config/rosegardenrc and share/apps/rosegarden/*.rc) I think we've been firmly in the realms of guessing for a long time now. I suggest trying difficult approaches to when and where the settings get saved - and adding a load more debug (or backgrounded save points) along the way to help us out. The rc files themselves (in the case of "settings amnesia") purely show what you get. It's obviously _when_ or _how_ these files get written that is the issue. R |
|
From: Richard B. <ric...@fe...> - 2004-02-25 13:37:24
|
Weird - interestingly I just edited a shortcut on the main view and on exiting RG the XServer died. Coincidence or just too freaky? R |
|
From: Chris C. <ca...@al...> - 2004-02-26 16:22:49
|
On Wednesday 25 Feb 2004 1:28 pm, Richard Bown wrote: > Weird - interestingly I just edited a shortcut on the main view and > on exiting RG the XServer died. Coincidence or just too freaky? Had you run RG from a desktop icon? Chris |
|
From: Richard B. <ric...@fe...> - 2004-02-25 13:31:20
|
On Wednesday 25 February 2004 13:07, Richard Bown wrote: > "settings amnesia" BTW the last time I investigated this I'm sure the evidence was pointing pretty clearly to the fact that the rosegardenrc file was getting written out alright by the app but that sometimes the rc was getting overwritten with a default file (the installed default) sometimes when the app was loaded. If this is true then something similar could be happening for the edit view key bindings. Perhaps it's possible that the app is looking the global app config path and overwriting the local copy? R |
|
From: Richard B. <ric...@fe...> - 2004-02-25 14:05:35
|
On Wednesday 25 February 2004 13:22, Richard Bown wrote: > Perhaps it's possible that the app is looking the global app config path > and overwriting the local copy? (to continue talking to myself) ..but of course there is no global copy - just defaults that are hardcoded into the app. So settings amnesia just happened again - the local rosegardenrc file was unchanged from the previous RG exit but the settings were ignored and returned to default, of course on next RG exit the rc file gets overwritten with the default. R |
|
From: Guillaume L. <gla...@te...> - 2004-02-25 18:21:49
|
On Wednesday 25 February 2004 14:53, Richard Bown wrote: > > ..but of course there is no global copy - just defaults that are hardcoded > into the app. Yes, it's all in RosegardenGUIApp::readOptions() > So settings amnesia just happened again - the local > rosegardenrc file was unchanged from the previous RG exit but the settings > were ignored and returned to default, of course on next RG exit the rc file > gets overwritten with the default. Next time this happens : kill (don't exit) rg so it leaves the rosegardenrc file intact, and restart it with strace -o /tmp/trace_file -e trace=file see if the rc file is read. -- Guillaume http://www.telegraph-road.org |
|
From: Richard B. <ric...@fe...> - 2004-02-26 07:38:40
|
On Wednesday 25 February 2004 18:12, Guillaume Laurent wrote: > Next time this happens : kill (don't exit) rg so it leaves the rosegardenrc > file intact, and restart it with > > strace -o /tmp/trace_file -e trace=file > > see if the rc file is read. Well, there's not mention of an rc file in the trace when the settings get lost or when they don't. One thing that's just struck me though is that it's mainly only the windows settings (expanded/unexpanded transport, track labels showing or not) that give the amnesia away. What doesn't go away is the recent file list - so it doesn't appear to be complete amnesia. R |
|
From: Guillaume L. <gla...@te...> - 2004-02-26 09:38:15
|
On Thursday 26 February 2004 08:29, Richard Bown wrote: > On Wednesday 25 February 2004 18:12, Guillaume Laurent wrote: > > Next time this happens : kill (don't exit) rg so it leaves the > > rosegardenrc file intact, and restart it with > > > > strace -o /tmp/trace_file -e trace=file > > > > see if the rc file is read. > > Well, there's not mention of an rc file in the trace when the settings get > lost or when they don't. That's just not possible. Your strace must be broken or something... > One thing that's just struck me though is that it's mainly only the windows > settings (expanded/unexpanded transport, track labels showing or not) that > give the amnesia away. What doesn't go away is the recent file list - so > it doesn't appear to be complete amnesia. Yes, it's always been that way. A possibility is that there's still a problem with the config groups somewhere, but that wouldn't explain why I haven't seen this problem in ages. -- Guillaume http://www.telegraph-road.org |
|
From: Richard B. <ric...@fe...> - 2004-02-26 09:52:22
|
On Thursday 26 February 2004 09:28, Guillaume Laurent wrote: > > Well, there's not mention of an rc file in the trace when the settings > > get lost or when they don't. > > That's just not possible. Your strace must be broken or something... Oh, it's my computer's fault. Oh that would explain it all then. > Yes, it's always been that way. A possibility is that there's still a > problem with the config groups somewhere, but that wouldn't explain why I > haven't seen this problem in ages. Depends if you actually set your window settings to something other than default I s'pose. R |
|
From: Guillaume L. <gla...@te...> - 2004-02-26 10:05:04
|
On Thursday 26 February 2004 10:42, Richard Bown wrote: > Oh, it's my computer's fault. Oh that would explain it all then. Well the rosegardenrc file *has* to be accessed somehow, hasn't it ? If only because that's where the recent files and main window size are stored. So if strace can't see any access to it, you definitely have a problem. > > Yes, it's always been that way. A possibility is that there's still a > > problem with the config groups somewhere, but that wouldn't explain why I > > haven't seen this problem in ages. > > Depends if you actually set your window settings to something other than > default I s'pose. I do. -- Guillaume http://www.telegraph-road.org |
|
From: Chris C. <ca...@al...> - 2004-02-26 10:38:03
|
On Wednesday 25 Feb 2004 12:09 pm, Richard Bown wrote: > * Ghost Notes, flakey mute/soloing points to a mmapped refresh > problem somewhere. yep. > We also have the situation whereby recorded > MIDI events can turn up in not only the newly recorded Segment but > future ones too. Still never actually seen that one. > * Audio Mixer to tidy up > and finish off along with audio routing, plugins and whatever else > Chris is doing. Yeah, plenty of tedious stuff to do there. Plugins stuff is done well enough for 0.9.7 but the mixer needs some work (still have to connect up the buttons etc and try to shrink things down so more stuff fits in less space). > Anything else? We still haven't fixed that crash-on-Stop, partly because I've never seen it again since the show (dammit). It's probably all part of the same problem of ensuring consistency between gui and sequencer in the shared-memory copy of the segment without actually having any locks. That's something that will take a certain amount of intellect to review, so I can't see myself managing it this week. > dinky MIDI mixer window I was thinking to have MIDI, audio, master &c as optional subframes in what's currently called the audio mixer, though I don't feel strongly about it. Chris |
|
From: Richard B. <ric...@fe...> - 2004-02-26 11:13:02
|
On Thursday 26 February 2004 10:33, Chris Cannam wrote: > I was thinking to have MIDI, audio, master &c as optional subframes in > what's currently called the audio mixer, though I don't feel strongly > about it. Maybe. We need to get some keyboard shortcuts for switching between them quickly as well. Could work. R |
|
From: Richard B. <ric...@fe...> - 2004-02-26 10:42:27
|
On Thursday 26 February 2004 09:55, Guillaume Laurent wrote: > Well the rosegardenrc file *has* to be accessed somehow, hasn't it ? If > only because that's where the recent files and main window size are stored. > So if strace can't see any access to it, you definitely have a problem. Well, I'm just reporting what I saw. But if it doesn't report loading the file even when it's recovered the values stored in the rc file then somthing is either working magically or loading that file surely? R |
|
From: Guillaume L. <gla...@te...> - 2004-02-26 13:45:28
|
On Thursday 26 February 2004 11:32, Richard Bown wrote:
>
> Well, I'm just reporting what I saw. But if it doesn't report loading the
> file even when it's recovered the values stored in the rc file then
> somthing is either working magically or loading that file surely?
It *HAS* to report it :
$ strace -o /tmp/trace -e trace=file ./rosegarden --nofork --nosequencer
$ grep rosegardenrc /tmp/trace
access("/home/glaurent/.kde/share/config/rosegardenrc", W_OK) = 0
stat64("/home/glaurent/.kde/share/config/rosegardenrc", {st_mode=S_IFREG|0600, st_size=1396, ...}) = 0
stat64("/home/opt/kde3.2/share/config/rosegardenrc", 0xbfffe8c0) = -1 ENOENT (No such file or directory)
open("/home/glaurent/.kde/share/config/rosegardenrc", O_RDONLY|O_LARGEFILE) = 10
--
Guillaume
http://www.telegraph-road.org
|
|
From: Richard B. <ric...@fe...> - 2004-02-26 13:52:02
|
On Thursday 26 February 2004 13:35, Guillaume Laurent wrote: > It *HAS* to report it : > > $ strace -o /tmp/trace -e trace=file ./rosegarden --nofork --nosequencer Oh, well you never said use --nofork did you? Makes sense now. I'll wait for the next time it misses. R |
|
From: Guillaume L. <gla...@te...> - 2004-02-26 14:02:50
|
On Thursday 26 February 2004 14:42, Richard Bown wrote: > On Thursday 26 February 2004 13:35, Guillaume Laurent wrote: > > It *HAS* to report it : > > > > $ strace -o /tmp/trace -e trace=file ./rosegarden --nofork --nosequencer > > Oh, well you never said use --nofork did you? I thought it was so obvious that you'd feel insulted if I'd point it out. :-) -- Guillaume http://www.telegraph-road.org |
|
From: Richard B. <ric...@fe...> - 2004-02-26 14:06:43
|
On Thursday 26 February 2004 13:53, Guillaume Laurent wrote: > > Oh, well you never said use --nofork did you? > > I thought it was so obvious that you'd feel insulted if I'd point it out. > :-) I should say something witty here about how obviousness is only obvious to those in the know. But I can't and won't. R |
Thanks for helping keep SourceForge clean.
X