From: Richard B. <ric...@fe...> - 2004-04-30 08:44:52
|
Well, I don't want to sound premature here but I think we might have nobbled it this time. G and I have been discussing various things and prodding and poking - and since the latest set of small changes (beginning of this week I think) I've not noticed it happen again. So I _really_ hope it's gone this time. I can't seem to find a BR for it? Was it attached to something else? If you've had if in the past then please keep an eagle out for reappearance if using CVS. R |
From: Guillaume L. <gla...@te...> - 2004-04-30 09:13:52
|
Richard Bown wrote: >Well, I don't want to sound premature here but I think we might >have nobbled it this time. G and I have been discussing various >things and prodding and poking - and since the latest set of >small changes (beginning of this week I think) I've not noticed >it happen again. So I _really_ hope it's gone this time. > > Er, sorry to sound off on this one, but what small changes ? :-) The read/saveGlobalProperty thing ? >I can't seem to find a BR for it? Was it attached to something >else? > > Don't think we had one, actually. Speaking of which, the logging function which I had added to help trace the problem is still in cvs. I think it wouldn't hurt to leave it, in case other people report the problem again. -- Guillaume http://telegraph-road.org |
From: Richard B. <ric...@fe...> - 2004-04-30 09:18:01
|
On Friday 30 April 2004 10:15, Guillaume Laurent wrote: > Er, sorry to sound off on this one, but what small changes ? :-) The > read/saveGlobalProperty thing ? Well, I think that moving it from read/saveProperties and perhaps putting in that reparse thingy might have done something. I'm still not convinced that the read/saveProperties thing with that passed KConfig is any good but at the same time I take your point that there's no logical reason why it would make any sense. Just reporting what I see though - and tentatively I like it. > Speaking of which, the logging function which I had added to help trace > the problem is still in cvs. I think it wouldn't hurt to leave it, in > case other people report the problem again. I agree. Early days on this one anyway - it's been around for so long I'm taking nothing to chance. R |
From: Guillaume L. <gla...@te...> - 2004-04-30 09:41:53
|
Richard Bown wrote: >Well, I think that moving it from read/saveProperties and perhaps >putting in that reparse thingy might have done something. I'm >still not convinced that the read/saveProperties thing with that >passed KConfig is any good but at the same time I take your point >that there's no logical reason why it would make any sense. > > As far as I can tell, the readProperties() methods (global and not global) aren't even called unless RG is started by KDE as part of a session restore... Better check that with an actual trace, though :-). -- Guillaume http://telegraph-road.org |
From: Richard B. <ric...@fe...> - 2004-04-30 09:58:32
|
How do you capture the Cancel button on a Rosegarden/KProgressDialog? Is there a cancelled() signal or what? I can't see us using this anywhere yet but I might of course be wrong. R |
From: Chris C. <ca...@al...> - 2004-04-30 10:07:02
|
On Friday 30 Apr 2004 10:58 am, Richard Bown wrote: > How do you capture the Cancel button on a > Rosegarden/KProgressDialog? Is there a cancelled() signal or what? > I can't see us using this anywhere yet but I might of course be > wrong. Can't remember offhand -- can check -- but note that the one in the progress dialog that shows when you're opening a notation view (with lots of stuff in it -- the dialog is on a timer) has a cancel button that already does work. Chris |
From: Richard B. <ric...@fe...> - 2004-04-30 10:19:31
|
On Friday 30 April 2004 11:12, Chris Cannam wrote: > Can't remember offhand Second stupid question. Where is the Metronome configuration stored these days? In Rosegarden::Configuration sure - and one of these is owned by Document yeah? So then when I write out an autoload.rg (default studio) or even save an RG file after a metronome mod why don't I get a metronomedevice written to the .rg file? R |
From: Chris C. <ca...@al...> - 2004-04-30 11:06:00
|
On Friday 30 Apr 2004 11:15 am, Richard Bown wrote: > Where is the Metronome configuration > stored these days? In Rosegarden::Configuration sure Now you see I thought it was stored as part of the Studio. And that's relevant because... > when I write out an > autoload.rg (default studio) or even save an RG file after a > metronome mod why don't I get a metronomedevice ... it seems I removed it in base/Configuration.C:1.25, when removing the fetch latency option. Looks like I just spotted something I thought was obsolete because the metronome had moved to the studio, and went ahead and removed it Guillaume-style. http://cvs.sourceforge.net/viewcvs.py/rosegarden/base/ Configuration.C?r1=1.24&r2=1.25 Chris |
From: Richard B. <ric...@fe...> - 2004-05-04 07:56:28
|
On Friday 30 April 2004 12:11, Chris Cannam wrote: > ... it seems I removed it in base/Configuration.C:1.25, when removing > the fetch latency option. Actually I think there is a need for a DocumentConfiguration in some form. At the moment DocumentConfig stores the ZoomLevel and the only sensible alternative for this field is probably the document MetaData Configuration object. However MetaData is in a free form editable presentation currently in the Document Properties dialog and so we'd have to hide a few config options from the user - which starts to make this Configuration class a bit messier. Plus as an aside I really don't like that you can just remove the four starting metadata tags from the meta data object - I think that this is just a "programmer's solution" to show off how flexible it all is rather than being something that's useful - I'd rather have fixed fields there or maybe just a core set of fixed fields and some other free form ones. (I still don't like giving the user free form metadata fields to play with though as their liable to break something). Ok, aside over. So what I'm saying is: I'd like the the DocumentConfiguration thing for stuff that we want to store against the document that we don't want the user to edit, and actually I think Metronome Device and Instrument does go in here as first thought. I'd also like to change the Document Properties dialog to have just fixed fields there (or at least a subset of fixed field that you can't remove plus a load of free form ones) depending on how people react. I dunno, some people might really like it. Or an alternative solution. Some really vague thoughts anyway. Today feels very Monday owing to the bank holiday we had yesterday, rain which has somehow appeared to avoid all my attempts to fix the guttering and an incapable brain that needs support rather than deceptively easy things to do. R |
From: Chris C. <ca...@al...> - 2004-05-04 08:12:18
|
On Tuesday 04 May 2004 8:56 am, Richard Bown wrote: > So what I'm saying is: I'd like the the DocumentConfiguration thing > for stuff that we want to store against the document that we don't > want the user to edit Fine. > I'd also like to > change the Document Properties dialog to have just fixed fields > there (or at least a subset of fixed field that you can't remove > plus a load of free form ones) depending on how people react. I don't mind if you make the default four un-deletable. I don't think anything more complicated than that is worth the effort now though. Chris |
From: Richard B. <ric...@fe...> - 2004-04-30 11:14:02
|
On Friday 30 April 2004 12:11, Chris Cannam wrote: > Now you see I thought it was stored as part of the Studio. And that's > relevant because... Can we get rid of the Rosegarden::Configuration yet? Don't we have enough configuration shit? BTW this metronome problem was being obfuscated slightly by a couple of other issues - firstly the metronome pitch spinbox wasn't sending previews (fixed) plus QSynth for some reason is not sounding the metronome despite the fact it's getting the events (as I can see from the MIDI activity light). All most perplexing and barely fun. Now what about the logged bugs - did you say you could tell me how to capture the cancel button press from a ProgressDialog? R |
From: Chris C. <ca...@al...> - 2004-05-12 13:36:52
|
On Friday 30 Apr 2004 12:12 pm, Richard Bown wrote: > [...] QSynth for some reason is not > sounding the metronome despite the fact it's getting the events (as > I can see from the MIDI activity light). Fixed this one yesterday. We were sending absurdly short notes -- 30 microseconds -- as the code hadn't been properly updated when I switched RealTime from usec to nsec resolution. 30ms was probably a bit short in the first place too, so I've upped it to 100ms. Chris |
From: Silvan <dmm...@us...> - 2004-05-13 00:12:22
|
On Wednesday 12 May 2004 09:45 am, Chris Cannam wrote: > Fixed this one yesterday. We were sending absurdly short notes -- 30 > microseconds -- as the code hadn't been properly updated when I > switched RealTime from usec to nsec resolution. 30ms was probably a > bit short in the first place too, so I've upped it to 100ms. Ah, that *would* explain it. I never thought of that, but I should have. I have observed that QSynth has real problems with very short notes. I have a number of things here and there with drum tracks that were done with extremely short notes. My Sound Canvas plays them fine, but QSynth stutters. -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ |
From: Chris C. <ca...@al...> - 2004-04-30 11:23:07
|
On Friday 30 Apr 2004 12:12 pm, Richard Bown wrote: > On Friday 30 April 2004 12:11, Chris Cannam wrote: > > Now you see I thought it was stored as part of the Studio. And > > that's relevant because... > > Can we get rid of the Rosegarden::Configuration yet? Don't we have > enough configuration shit? DocumentConfiguration is certainly a pretty pointless class -- all it does is store zoom level and (it should store) metronome data. But hey, you invented it. There's a much more relevant and necessary Configuration object in the Composition that stores composition metadata (author, copyright etc). That'll be the one I wrote. > - did you say you could tell me how to capture the cancel button > press from a ProgressDialog? It emits cancelClicked(). In notationview.cpp (the example I gave) that's connected to the layout's slotCancel. The layout is a ProgressReporter, so it notes that a cancellation has happened, and when the next suitable moment occurs it throws an exception which comes back to the notation view at that point. (It's not always easy to cancel directly, the layout has to have a chance to tidy up what it's doing.) Chris |
From: Richard B. <ric...@fe...> - 2004-04-30 11:29:19
|
On Friday 30 April 2004 12:28, Chris Cannam wrote: > DocumentConfiguration is certainly a pretty pointless class -- all it > does is store zoom level and (it should store) metronome data. But > hey, you invented it. Did I? Oh yeah maybe I did. I'll tidy it up then and get the metronome into the Studio. > There's a much more relevant and necessary Configuration object in the > Composition that stores composition metadata (author, copyright etc). > That'll be the one I wrote. Ah ok. > > - did you say you could tell me how to capture the cancel button > > press from a ProgressDialog? > > It emits cancelClicked(). In notationview.cpp (the example I gave) > that's connected to the layout's slotCancel. Ok, thanks, sorry I missed that. R |
From: Chris C. <ca...@al...> - 2004-04-30 11:34:29
|
On Friday 30 Apr 2004 12:27 pm, Richard Bown wrote: > On Friday 30 April 2004 12:28, Chris Cannam wrote: > > DocumentConfiguration is certainly a pretty pointless class -- > > all it does is store zoom level and (it should store) metronome > > data. But hey, you invented it. > > Did I? Oh yeah maybe I did. To be fair, I have a vague recollection of your remarking that it was a piece of crap at the time. I think it was something of an interim measure. Or should I say, "interim measure". Chris |
From: Vladimir S. <vl...@ro...> - 2004-04-30 11:45:57
|
I've reported some problems with metronome data storing, but cann't remember what exactly it was. It was 2-3 weeks before, I think!? Vladimir -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ |
From: Richard B. <ric...@fe...> - 2004-04-30 11:51:33
|
On Friday 30 April 2004 12:40, Chris Cannam wrote: > > Did I? Oh yeah maybe I did. > > To be fair, I have a vague recollection of your remarking that it was > a piece of crap at the time. I think it was something of an interim > measure. Or should I say, "interim measure". Ok I'll fix that and hopefully keep things backwards compatible which shouldn't be too hard considering how small it is. Plus I'm just adding a reporting structure for XRuns and JACK dying so that the user can get some feedback if they so wish. R |
From: Chris C. <ca...@al...> - 2004-04-30 16:19:46
|
On Friday 30 Apr 2004 12:51 pm, Richard Bown wrote: > I'm just adding a reporting structure for XRuns and JACK dying > so that the user can get some feedback if they so wish. Can you outline how this is intended to work? At the moment sometimes when Rosegarden is just sitting there idle and I switch desktops away from it, it rudely switches me straight back again with a message saying the audio subsystem is losing resolution (which I presume is some code for whatever "xrun" is also code for). Fine, but it's not happening at a time when I'm likely to care. Chris |
From: Richard B. <ric...@fe...> - 2004-04-30 17:11:24
|
On Friday 30 April 2004 17:25, Chris Cannam wrote: > Can you outline how this is intended to work? At the moment sometimes > when Rosegarden is just sitting there idle and I switch desktops away > from it, it rudely switches me straight back again with a message > saying the audio subsystem is losing resolution (which I presume is > some code for whatever "xrun" is also code for). Fine, but it's not > happening at a time when I'm likely to care. Right, we should only be processing these when we're playing. I'll fix. R |
From: Richard B. <ric...@fe...> - 2004-04-30 17:51:23
|
On Friday 30 April 2004 18:11, Richard Bown wrote: > Right, we should only be processing these when we're playing. > I'll fix. Ok should be less annoying now. This just copes with the main cases of interest now - frames dropping now through our fault or JACK booting us or dying during playback. R |
From: Silvan <dmm...@us...> - 2004-04-30 23:42:02
|
On Friday 30 April 2004 07:12 am, Richard Bown wrote: > BTW this metronome problem was being obfuscated slightly by a couple of > other issues - firstly the metronome pitch spinbox wasn't sending previews > (fixed) plus QSynth for some reason is not sounding the metronome despite > the fact it's getting the events (as I can see from the MIDI activity > light). Didn't I blather about that at some length already? Maybe I didn't file the bug report after all, but I remember dicking around for quite a long time until I figured out that it was Q/FluidSynth misbehaving somehow. I looked at the MIDI stream and everything. It was receiving everything, but it just wasn't playing the damn notes for some reason. Everything we were sending looked perfectly fine. I even tried a hacked up soundfont where anything anywhere (any program/bank/channel) would come out as a snare drum. Nada. The metronome worked from Hydrogen and my Roland no problem. Maybe I never said any of this out loud. I ended up just using Hydrogen as my metronome, I think. I only have one line-in, so if I want to record my electric guitar, I have to unhook the audio feed from my Roland, so I have to use something else for a metronome... I haven't yet actually managed to record anything that didn't include the noise the metronome was making though. Fucking mixer. I swear either ALSA has changed since 0.9.x or my new motherboard is negotiating a different deal with this card. My mixer has been fucked ever since I got the new computer. New kernels, new ALSAs, even a clean distro install absolutely from scratch, and it's still fucked. I've tried everything short of digging up an old version of ALSA. I need to buy one of those cards Chris was talking about. Pro Audio some flummy. What the hell was that thing again? -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ |
From: Chris C. <ca...@al...> - 2004-05-04 09:26:33
|
On Saturday 01 May 2004 12:42 am, Silvan wrote: > I need to buy one of those cards Chris was talking about. Pro > Audio some flummy. What the hell was that thing again? The one I have is an M-Audio Audiophile 2496, but there's a range of similar things with different I/O configurations from various different brands, all based on the envy24 chipset. The Audiophile is a PCI card without a separate breakout box, with line-level stereo analogue in and out via dual phono plugs on the card itself, plus stereo digital in and out via SP/DIF on an adapter cable that also includes MIDI in and out. Not that many sockets, then, but as I already have an external mixer I preferred something that fits in a single card to something with an external box. The M-Audio Delta range generally have the same chipset but with a breakout box, and Terratec do something similar. Dynamic range is supposedly a little better on the external devices, but it's not at all bad on the PCI card either. These cards also do zero-latency monitoring, which I assume is handy if you're recording -- recording from external sources is the one thing I almost never do. Chris |
From: Silvan <dmm...@us...> - 2004-05-05 00:04:25
|
On Tuesday 04 May 2004 05:31 am, Chris Cannam wrote: > all bad on the PCI card either. These cards also do zero-latency > monitoring, which I assume is handy if you're recording -- recording > from external sources is the one thing I almost never do. Thanks for the info. As soon as I get a few things settled, I'm going to go shopping for one of those things. This mixer nonsense is driving me nuts, and it has rendered my soundcard all but useless. Incidentally, on this subject... I tried RG on Mom's new computer. She's a total computer newbie who's been studiously avoiding these things for years, but she finally found some reason to get online. Dad and I set her up with a 1.3 GHz box. Nothing fancy, but still slightly more respectable than my old computer. The audio is on-board i810/ac97, which I seem to remember is more or less equivalent to my ens1371. I fired up Jack, Rosegarden, and QSynth. All the combination was good for was producing flatulence. The xruns were rampant, and the audio quality dismal. I think, therefore, that the reason it took me so long to be able to do anything with any of these various Jack-related flummies was indeed that my computer wasn't fast enough. The only reason I got any use out of RG at all before this new box was because I had a Roland Sound Canvas to use for making noise. Since she doesn't have an external sequencer, and no on-board synth, Rosegarden is absolutely useless for everything except pure notation editing on that box. Not really a big deal, since she's tone deaf anyway. It's just that I didn't make a very good impression showing her what I've been working on. :) -- 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-05-05 06:57:00
|
On Wednesday 05 May 2004 01:02, Silvan wrote: > Dad and I set her > up with a 1.3 GHz box. Nothing fancy, but still slightly more respectable > than my old computer. The audio is on-board i810/ac97, which I seem to > remember is more or less equivalent to my ens1371. It's standard fare. > I fired up Jack, Rosegarden, and QSynth. All the combination was good for > was producing flatulence. The xruns were rampant, and the audio quality > dismal. Quite honestly with your track record for setting up JACK I'm not surprised. The spec of the machine you're talking about is abolutely fine for running MIDI and audio with no xruns if it's set up right. So yes, I _do_ indeed point the finger. I suggest you tryout CCRMA or AGNULA for how it should be done right and work backwards from there. Definitely try out AGNULA's Live CD (boots from the CD) on any of your machines to try out distro - a great way of showing off RG and other Linux Audio apps to your friends. > I think, therefore, that the reason it took me so long to be able to do > anything with any of these various Jack-related flummies was indeed that my > computer wasn't fast enough. Nope, your computer was plenty fast enough - you had the same as I yes, a 1GHz Athlon? I run that with a cheapie SBLive and it works fine. On my laptop (1.2GHz with an ac97) I can get glitch free audio and MIDI. From now on RG will report back to the user when JACK gets into trouble with xruns so this nagging will either make your drop JACK support or get it running right as it should be. R |