Michael, thanks for giving this a good look again. I appreciate your
patience.
>> I want to make sure it works right when one changes devices,
>> especially when one deletes them.
>
> The very first time I started a new session after building the latest
> changes,
> track 1 was playing some random program, not the program for the
> track/instrument I was sitting on. That's the only really obvious and
> shocking glitch I noticed in this test session.
It's clearly something I should fix, but I can't seem to reproduce it. I
tried it with vanilla settings (no autoload.rg) and I just hear Acoustic
piano #1 correctly on track 1. Then I set my default studio with a
distinctive track #1, quit and restarted, still heard the right
instrument. I can't reproduce it. Since it happened the very first time
for you, it doesn't seem like anything you set. Still, any hint as to how
I might reproduce it would be appreciated.
> When I went back through the tracks, QSynth played with the desired
> programs.
> That is one very obvious sign that something in Rosegarden has changed.
> Previously, I would have had to go "jiggle" all the programs to get them
> set
> back up for the newly changed device. That's rather nice!
Great!
> across several different standards) and it changes the combo box to the
> "Standard 1" drum kit, but neither the bank change nor the program change
> are
> actually transmitted upon checking the box. The result is that a piano or
> whatever continues to sound until you "jiggle" the program combo box.
> This
> _could_ be a wrong channel thing, but I think it's much more likely a
> failure
> to transmit the bank/program change.
OK, why don't I make it transmit, and then we'll find out whether or not
it's concealing another bug.
> Second, after I got that track playing drums, the next couple of tracks I
> clicked on also played drums. It seems like what probably happened was
> channel X hadn't been de-allocated, and was in use the next couple of
> times I
> changed tracks. Eventually that sorted itself out after I clicked around
> long
> enough, but it was momentarily confusing.
I will look at that.
> [...]
> After I hooked the new device to an output and moved several tracks to
> point
> to the new device, they all made noise. They played with the programs
> that
> were in use by those tracks before I deleted the device out from under
> them.
> In this case, there are NO programs in the new device, so what else could
> it
> do?
>
> So I loaded some programs into the new device and tried everything again.
> After I did that, I was no longer able to get sound out of anything. It
> looks
> like something broke in a pretty permanent way after loading the programs.
I see that, but I also see it in my pre-logical-instruments copy. In both
cases, delete device+new device will grey everything, not immediately but
soon, indicating that all the tracks use some invalid device. The tracks
have to be set manually. That's been with us for a while. In both cases,
after changing the track's program manually, it makes the expected sound.
At least for me it does.
> I saved and reloaded the file. That fixed all the broken gray LEDs that
> were
> pointing at a deleted device, but it didn't get the sound issue sorted.
> After
> I got that to break, it stayed broken.
>
> Here's the resulting file for dissection. I quit and restarted with the
> same
> result. Something in the way this file is coded breaks your channel
> allocator
> thingie permanently.
Thanks, having the savefile is very helpful. I didn't see anything
obviously wrong with it by eyeball. When I loaded it, I get a glitch, but
a different one: Two tracks have sensible instruments, and they play
right, but the rest are dead.
Having another look at the file itself, I noticed that only the first two
tracks are pointed at real instruments, the rest of the tracks'
instruments don't exist.
So what I think is happening has always happened: When a device disappears
underneath a track, that track keeps indexing a dead instrument on the
dead device until it's changed manually, and it holds on even across
savefiles, which after all need to preserve a track's instrument. It
might be worth making it more convenient but I don't think it's a logical
instruments issue.
> Even so, this is still a VAST improvement. I'm very pleased with the
> result
> of your second stab at all of this.
Thank you!
Tom Breton (Tehom)
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
