This one goes to Michael, I think...
Since you're in charge of documentation, I'd like to open discussion about
what you call Making noise by default. Nowdays the situation has improved in
many ways regarding MIDI on linux. My expectation was that KDE4 developers
would eventually make midi sounds
On Monday 21 April 2008, Vladimir Savic wrote:
We have wiki now. Maybe we could make general guidelines on the easiest way
of setting up various distribution to play something.
Either the wiki, or add a new mini-tutorial to the series I started during
this release cycle.
Arguments for a wiki
OMG! My handwriting to the T! I must have been sleepwalking, it wasn't
me, it was just someone who looked like me, honest!
I did that with a mouse. No pen and tablet, no scanner. I think it turned
out impressively well under the circumstances. :)
--
D. Michael McIntyre
I finished the Spanish translation, though it's probably rough, and maybe even
total gibberish to a native speaker. Nobody else was doing it. We can't
keep a Spanish translator around here.
We've had updates for Italian (Alessandro) and French (Yves.) Unfortunately,
Jan began work on the
D. Michael McIntyre wrote:
On Monday 21 April 2008, Vladimir Savic wrote:
We have wiki now. Maybe we could make general guidelines on the easiest way
of setting up various distribution to play something.
Either the wiki, or add a new mini-tutorial to the series I started during
this
On Mon, 21 Apr 2008 09:39:29 +0200
Vladimir Savic
[EMAIL PROTECTED] wrote:
This one goes to Michael, I think...
Since you're in charge of documentation, I'd like to open discussion
about what you call Making noise by default. Nowdays the situation
has improved in many ways regarding MIDI on
On Mon, Apr 21, 2008 at 09:52:37AM -0400, D. Michael McIntyre wrote:
On Monday 21 April 2008, Vladimir Savic wrote:
We have wiki now.
Arguments for a wiki usually involve the idea that other people can edit and
add to it. In practice, the only way anybody can write to our wiki is if we
On Monday 21 April 2008, Shelagh Manton wrote:
I did that without any difference to the big button
I hate problems like this, where someone out there can repeat them all day,
and I can't get them to happen.
They're almost impossible to figure out.
Maybe this might be related to the build
On Mon, 21 Apr 2008 18:51:19 -0400
D. Michael McIntyre
[EMAIL PROTECTED]
wrote:
On Monday 21 April 2008, Shelagh Manton wrote:
I did that without any difference to the big button
I hate problems like this, where someone out there can repeat them
all day, and I can't get them to happen.
On Monday 21 April 2008, Shelagh Manton wrote:
Timidity is the least intrusive option.
Well, you have a point. His thinking was that for people who have one, the
asfxload route is the best thing to try first. It is, and I can agree with
that, but on second thought, let's look at the first
You guys may regret this. (giving me the go-ahead to look at the manual
that is)
I have been looking at the manual, going through and changing
Rosegarden to rosegarden; as suggested and hopefully improving style a
bit.
But I've also been trying some of the things in the manual as I've gone
On Tuesday 22 April 2008, Shelagh Manton wrote:
Pitch split by range for piano parts. Oh how I've wanted this!
It has existed for years.
shows the lower clef only. I was hoping that it would behave something
like selecting two tracks and getting to see both in the notation
editor.
For this
Today I can't reproduce the error, but I suspect it might be due to not
checking all the options on the lilypond export page. I might not have
marked the export all tracks or maybe only the un-muted tracks (with no
un-muted tracks)
So cross that one off the potential list.
Shelagh
--
On Tue, 22 Apr 2008 00:43:25 -0400
D. Michael McIntyre
[EMAIL PROTECTED]
wrote:
On Tuesday 22 April 2008, Shelagh Manton wrote:
Pitch split by range for piano parts. Oh how I've wanted this!
It has existed for years.
shows the lower clef only. I was hoping that it would behave
14 matches
Mail list logo
