From: Khoa T. <pip...@ho...> - 2010-06-08 13:40:55
|
Hello Michael, Thanks for the response. I appreciate the complexities involved in the porting to Qt4. I think you're probably right about the audio engine being "confused" and losing track of segments. Is there anything I can do in terms of structured testing? > Message: 4 > Date: Fri, 4 Jun 2010 16:10:28 -0400 > From: "D. Michael McIntyre" <mic...@ro...> > Subject: Re: [Rosegarden-user] Audio problem/files overwritten > To: ros...@li... > Message-ID: <201...@ro...> > Content-Type: Text/Plain; charset="iso-8859-15" > > On Friday, June 04, 2010, Khoa Tran wrote: > > > - internal routing of tracks no longer works: > > I haven't spent any time trying to be thorough about it, but this really does > seem to be broken now. > > > - sometimes, when recording (inevitably, actually, every session I've tried > > so far), the input I'm trying to record won't actually be recorded, but > > it'll pick up the output of another track, and simultaneously wipe out and > > overwrite segments in the first audio track, even though only one track > > was actually armed for recording. > > Picking up the wrong input source sounds like a typical sort of problem > Rosegarden might have suffered as a casualty of the whole porting process. I > haven't observed this myself, but that sort of misbehavior is consistent with > the way things tend to go wrong. > > This other thing though, simultaneously wiping out and overwriting segments on > some other track, I find that *incredibly* difficult to believe. Rosegarden > doesn't have any kind of destructive recording operation. Everything you > record always just piles up on top of whatever was already there, and coexists > with it. If Rosegarden is doing something truly destructive (as opposed to > merely being confusing; confusing is definitely possible!) then that will be > cause to well and truly freak out and get into panic mode trying to arrest the > damage immediately. > > At this time, however, I'm not in a panic at all, and I'm betting you're just > getting confused somehow. I haven't done any real music in going on three > years now, and I haven't actually used the new Rosegarden for much of anything > at all, but the one bit of real world production work I've done with it was a > 100% audio project. I didn't experience any gross weirdness of the magnitude > you're talking about, or I would have gone into a fit of panic long before > now. > > You probably ARE really on the tail of a serious problem, but I don't think > Rosegarden is actually doing anything that's truly destructive. For instance, > even if the audio segments somehow get lost (which are just virtual containers > wrapped around data files on disk), I'll all but bet money the actual data is > still safe and sound, and recoverable. > > Anyway, I haven't seen symptoms like this, and don't know where to begin > trying to track this down. Something weird is most likely happening, but > getting the same weirdness to occur in the laboratory where it can be observed > is another matter entirely, unfortunately. > -- > D. Michael McIntyre _________________________________________________________________ Turn down-time into play-time with Messenger games http://go.microsoft.com/?linkid=9734385 |