On Mon, 2004-03-22 at 04:45, Chris Cannam wrote:
> On Sunday 21 Mar 2004 12:23 am, Larry Battraw wrote:
> > Another small bug... Start RG and load a song. Press play then
> > stop. Bring up the notation editor and try dragging the horizontal
> > scroll bar; it flashes back and forth repetitive
Guillaume Laurent <[EMAIL PROTECTED]> wrote:
>On Monday 22 March 2004 11:47, Chris Cannam wrote:
>> Anyone know any reason we shouldn't call setsid() to get a new process
>> group right at the start of the GUI's main()?
>
>A quick googling didn't reveal any, and I can't think of any either.
Neithe
Guillaume Laurent wrote:
>William wrote:
>> If you've the time to implement it a "Delete All Empty Tracks" in the
>> Edit menu would save quite a bit of mouse-work on some files.
>
>That's a good idea... Can you add a feature request ?
Yes. Shall I also log the 20-30(?) bug reports and feature re
I have a repeatable crash when merging one particular Rosegarden file
into another. Because it's repeatable I should be able to fix it
tomorrow, but I want to mention it now (just before logging out) in
case it's obvious to someone else. So, what would cause this?
The crash follows a warning
On Monday 22 March 2004 11:47, Chris Cannam wrote:
> Anyone know any reason we shouldn't call setsid() to get a new process
> group right at the start of the GUI's main()?
A quick googling didn't reveal any, and I can't think of any either.
--
Guil
On Monday 22 March 2004 17:25, William wrote:
> If you've the time to implement it a "Delete All Empty Tracks" in the
> Edit menu would save quite a bit of mouse-work on some files.
That's a good idea... Can you add a feature request ?
--
Guillaum
Chris Cannam wrote:
>William wrote:
>> Does rc3 support the import of MIDI marker events as per the devel
>> CVS commit you announced earlier today?
>
>Yes. I probably shouldn't have done that in this RC phase, but I did.
Well, thanks for doing it. It's slightly ironic that a release candidate
l
On Monday 22 Mar 2004 4:30 pm, William wrote:
> Does rc3 support the import of MIDI marker events as per the devel
> CVS commit you announced earlier today?
Yes. I probably shouldn't have done that in this RC phase, but I did.
Chris
---
Thi
Chris Cannam wrote:
>[...]
>http://www.rosegardenmusic.com/tmp/rosegarden-4-0.9.7-rc2rc3.patch.bz2
Thanks. It's only 10158 bytes long and very quick to download.
Does rc3 support the import of MIDI marker events as per the devel CVS commit
you announced earlier today?
William
-
Chris Cannam <[EMAIL PROTECTED]> wrote:
>
>On Monday 22 Mar 2004 3:16 pm, William wrote:
>> It seems like the UI is organised such that segment selections and
>> track selections are mutually orthogonal in all parts of the UI
>> except for the Up/Down shortcuts which couple the segment selection
>>
http://www.rosegardenmusic.com/tmp/rosegarden-4-0.9.7-rc3.tar.bz2
http://www.rosegardenmusic.com/tmp/rosegarden-4-0.9.7-rc2rc3.patch.bz2
Chris
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel
On Monday 22 Mar 2004 3:16 pm, William wrote:
> It seems like the UI is organised such that segment selections and
> track selections are mutually orthogonal in all parts of the UI
> except for the Up/Down shortcuts which couple the segment selection
> to the track selection.
No, if you click on a
Richard Bown wrote:
>
>the way the functionality works makes much more sense if you use the
>keyboard shortcuts and the sweep selector on the segment canvas.
>Sweep out some segments and hit the delete key.
Thanks. That's a very useful tip.
I had to change the shortcut to BackSpace because of conf
> Admittedly I'm not a big fan
> of Cage's 4 minutes 33 seconds of silence.
That's because most recorded interpretations sucks.
--
Guillaume
http://telegraph-road.org
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tut
Firstly bear in mind that we'll not be making any changes of this magnitude to
the UI core functionality this close to 1.0 - secondly the way the
functionality works makes much more sense if you use the keyboard shortcuts
and the sweep selector on the segment canvas. Sweep out some segments and
Chris Cannam wrote:
>William wrote:
>> I notice that the playback cursor always continues moving beyond the
>> end of the longest segment which is track 1 (by a fraction of a second)
>
>This has been covered several times before. No, it generally isn't
>desirable, and it'll probably change at som
In the tracks editor, there are several ways of doing deletions:
1 "Delete" in the "Edit" menu which is for deleting any segments which
you have previously selected by clicking or, in the case of multiple
segments, Shift-clicking. These selected segmented are drawn in
a darker shade
On Monday 22 Mar 2004 11:19 am, William wrote:
> Any chance you might run a
> diff -Naru rg-release-a rg-release-b | bzip2 -9 >
> rg-release-a-b.patch.bz2 on future releases to help those of us
> with low-bandwidth connections?
OK, for the next one. I won't take any responsibility if the result
On Monday 22 Mar 2004 1:49 pm, William wrote:
> I notice that the playback cursor always continues moving beyond
> the end of the longest segment which is track 1 (by a fraction of a
> second)
This has been covered several times before. No, it generally isn't
desirable, and it'll probably change
Chris Cannam <[EMAIL PROTECTED]> wrote:
>
>On Monday 22 Mar 2004 1:39 pm, William wrote:
>> When you say "not pretty", I assume you're talking about the view
>> from the Expert Event List Editor since this type of MIDI event is
>> invisible in other parts of the GUI?
>
>No, markers are shown in the
Referring again to my example in my earlier email
Message-Id: <[EMAIL PROTECTED]>
I notice that the playback cursor always continues moving beyond the end of the
longest segment which is track 1 (by a fraction of a second) because
the composition duration is 5522 bars (how that came about I do not
Chris Cannam <[EMAIL PROTECTED]> wrote:
>
>No, I do a cvs update from within a release directory and then run
>"make dist". Unfortunately I don't even entirely understand what
>make dist does, because it's one of those hugely overcomplicated
>things we inherit from either the KDE build config o
Anyone know any reason we shouldn't call setsid() to get a new process
group right at the start of the GUI's main()?
When you run Rosegarden from the KDE desktop it starts up with the
same process group ID as kdeinit, which means if anything gets in a
panic and tries to kill the process group,
On Monday 22 Mar 2004 9:55 am, Chris Cannam wrote:
> Rosegarden loads lyric
> events, but discards marker events. What it should do is turn them
> into markers in the composition
OK, fixed in CVS. The results for the particular file you referred to
are not pretty, but that's what happens when y
On Sunday 21 Mar 2004 6:14 pm, William wrote:
> it seems RG will load any MIDI file, which contains what I think
> are termed "MetaMarker" (or "lyric") MIDI events, such as the MIDI
> file I gave in my example, but when it loads the file RG will
> silently discard all of these MIDI events.
Ah, so
On Sunday 21 Mar 2004 3:08 pm, William wrote:
> I'm not sure how you generate the release tarballs but I guess you
> probably copy the CVS RG tree into a release directory and then run
> tar.
No, I do a cvs update from within a release directory and then run
"make dist". Unfortunately I don't ev
On Sunday 21 Mar 2004 5:27 pm, Silvan wrote:
> I've heard traffic about a new mixer console. I can't figure out
> where it is.
>
> Is this something that only makes itself available if Jack is
> running?
Yes. It's an audio mixer only -- doesn't yet contain MIDI level
faders, although it will.
On Sunday 21 Mar 2004 12:23 am, Larry Battraw wrote:
> Another small bug... Start RG and load a song. Press play then
> stop. Bring up the notation editor and try dragging the horizontal
> scroll bar; it flashes back and forth repetitively and it won't
> allow you to scroll at all
Did you me
28 matches
Mail list logo
