Chris Cannam wrote:
> -- The mute buttons don't seem to show the correct state when
> you load a file
Ah, bugger, I thought I'd fixed that. Actually yeah I can't get
this to fail - I've added a slotSynchroniseWithComposition() to
TrackButtons which is probably quite a good thing to have anyway.
Wire it up when you can replicate the problem.
> -- Document isn't marked as modified when you change muting,
> rename tracks, etc.
Ok, fixed those.
> I think the only thing that changes file state but that
> shouldn't change the document's modified-ness is moving the
> playback pointer.
Actually the pointer position is stored in the document when saving
so this is behaviour is correct.
> -- I don't have audacity (yet) on my home machine
Ok I've changed this so that it we don't report when we can't find the
default external editor - we just silently blank the field. You might
want to change this behaviour (rosegardenconfiguredialog.cpp) as I can't
think of a good way of doing this right now.
> -- There are Configure Rosegarden options on all the windows'
> Settings menus, but only the one on the main window works.
> (At least the one on the notation view certainly doesn't.)
> It'd be nice if the one on the notation view took you
> straight to the notation configuration pane, etc.: any idea
> if that's feasible?
I should certainly think so. I'd like to do this kind of thing the
first time we run up too so that we can force users to examine their
audio latency settings for example.
The "configure shortcuts" and "configure toolbars" aren't wired up
in clients either. Perhaps a job for Mr L?
> I couldn't get iiwusynth to work last night either. No errors
> reported, just no sound. Rosegarden didn't pick up an
> instrument for it, and I couldn't get iiwuplay to make any
> sound either. I had it working once and I'm pretty sure I'm
> using the same soundfont now as then, but I've completely
> reinstalled the system since. Maybe some stupid mistake, or
> maybe the audio bits of my ALSA setup really are broken.
It won't be a soundfont thing - are you running is in alsa_seq mode?
Sounds like something more fundamental with your sound setup.
Now you've fixed your JACK problem I think I've worked out what it was
- of course your AWE32 is so old it probably doesn't do full duplex
audio (i.e. recording whilst playing) and this is JACK's default mode.
Hence your success with the -P option - shame the JACK error messages
aren't more useful - it might be worth submitting a patch to this effect