On 9/2/22 7:26 AM, Lorenzo Sutton wrote:
I think it would make sense to be able to place controllers in a
non-continuous way on the (horizontal) time-scale depending on the
selected matrix Grid or quantization.
Snap to grid for the controller rulers. Sounds like a valid feature
request.
The standard way is to kill the process. This doesn't actually kill
the process. It sends a SIGTERM (15) which politely asks the process to
close.
I have no idea how well rosegarden handles SIGTERM. But you can try
it and open a bug report if you don't like the results.
Ted.
On
I noticed two things with whatever version of ZASF I have in Ubuntu
22.04:
1. There is a program change at the beginning of the segment. It's at
001-02-16-00 and it selects program 6. Removing that seems to sound
"better", but I have a feeling I need your patch set to do this right.
The channel auto/fixed field is now hidden by default and can be
shown via the preferences (Auto Channels (Experimental)). Please test
latest git.
Ted.
On 6/28/22 4:23 AM, Lorenzo Sutton wrote:
On 28/06/22 02:03, msk...@ansuz.sooke.bc.ca wrote:
On Mon, 27 Jun 2022, Ted Felix wrote
not crashes!
Il 28/06/22 01:20, Ted Felix ha scritto:
On 6/27/22 1:01 AM, Mario Moles wrote:
(gdb) start
Use the "run" command instead of "start".
Ted.
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net
The idea was to allow rosegarden to allocate channels as needed on a
synth to make it appear as if there were more than 16.
In practice, it was a rather complicated change to the code that
wasn't fully tested before it was merged.
You can achieve the same effect manually by including
On 6/27/22 1:01 AM, Mario Moles wrote:
(gdb) start
Use the "run" command instead of "start".
Ted.
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
Il 26/06/22 17:51, Ted Felix ha scritto:
Ok. Are you doing a debug build? If so, you can get a backtrace
using gdb. That will tell us exactly what's going on.
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the
Ok. Are you doing a debug build? If so, you can get a backtrace
using gdb. That will tell us exactly what's going on.
Ted.
On 6/26/22 11:44 AM, Mario Moles wrote:
I use rosegarden-git.
I use Manjaro.
Rosegarden continues to crash
Il 26/06/22 13:53, Ted Felix ha scritto:
Have you built
lE
[Composition] 0x5569688f66a0 : N10Rosegarden12TrackButtonsE
[Composition] getTrackById( 0 ): WARNING: Track ID not found.
[Composition] Available track ids are:
[AlsaDriver] renameDevice(): WARNING: Cannot find device 1 in port map
Errore di segmentazione (core dump creato)
[mario@mario-pc~]$
Il 25/0
Sounds like your security settings aren't configured to let you run
fluidsynth. See the "audio group" section of my Linux MIDI page:
http://www.tedfelix.com/linux/linux-midi.html#audio-group
Ted.
On 6/25/22 3:54 AM, Mario Moles wrote:
Hi!
From the terminal:
"rosegarden
Cannot lock down
On 5/21/22 5:09 AM, Lorenzo Sutton wrote:
I tried to activate advanced looping (and admittedly did not read the
whole discussion on the bug, wonder if it would be useful to have
these discussions possibly impacting feature changes / updates in the
user list ;-)
The idea is to discuss in
Thanks, Chris. I'll let you know if I run into anything.
Ted.
On 6/16/22 7:04 AM, Chris Cannam wrote:
I've just moved the Rosegarden site to a new server and updated the Dokuwiki
instance to the current stable version. Everything should work unchanged, and
it looks ok to me at first
On 6/9/22 1:59 AM, david wrote:
I used the GIT method and got 22.12 instead but it looks lovely and
works. :)
You are on the bleeding edge!
Ted.
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to
== ROSEGARDEN 22.06 RELEASED ==
The Rosegarden team is proud to announce the release of version 22.06
of Rosegarden, a MIDI sequencer that features a rich understanding of
music notation along with basic support for digital audio.
http://www.rosegardenmusic.com/
Included in this
On 6/8/22 3:03 PM, prad wrote:
and learned that by default
preempt=full
and that i append it to
GRUB_CMDLINE_LINUX_DEFAULT=
(and not the way i was doing it).
also, to not go lowlatency you can append:
preempt=none
Good stuff. Thanks for this. I will work it into my next update for
my
On 6/8/22 9:07 AM, Lorenzo Sutton wrote:
Hey I hope I'm in time... took a while to do the re-build on my Linux
machine
Just starting the release now, so you definitely made it.
Everything seemed to work well.
Good to hear. Thanks for testing. 22.06 shortly...
Ted.
On 6/6/22 1:49 AM, prad wrote:
uname -a
Linux schnell 5.18.1-arch1-1 #1 SMP PREEMPT_DYNAMIC
PREEMPT_DYNAMIC is something new. It doesn't guarantee you are
running a preemptible kernel. It allows for turning on PREEMPT via the
kernel command line parameters (preempt=full).
This post
On 6/5/22 1:40 PM, prad wrote:
i tried linuxsampler and amsynth.
both show up in the instruments parameters, but i can't do a thing with
either.
There are certainly synths that are a bit hard to get started with.
These might be two of them. I've not tried either. I would come back
to
On Fri, 03 Jun 2022 18:03:44 -0700
prad wrote:
what is the recommended|prefered way to get sound in rg?
Avoid the plugins (at least at first). Run your softsynths standalone.
the problem with yoshimi is that i have to set everything outside rg.
i presume that with a plugin, from what you
On 6/5/22 5:19 AM, Philip Leishman wrote:
The most puzzling aspect for me is why the bug does not happen with the
Ctrl+Z shortcut - this is going through exactly the same code as the
toolbar !!
Yeah. My theory is that there is some refresh code in Qt that gets
confused when the toolbar
We've made a last minute Matrix editor change to fix a refresh bug.
I know it's really late in the cycle, but if you have a moment, please
build the latest from git and give the matrix a good beating prior to
Wednesday. Focus would be on deleting notes via undo, via selection and
delete,
On 6/4/22 1:24 PM, mark_at_yahoo via Rosegarden-devel wrote:
I have no idea where the second update is coming from.
Interesting. I tried tracking it down with gdb, but I guess I don't
have the source installed, so it didn't let me. Or I did something
wrong. gdb is still not as much fun
behavior.
Philip
On 6/2/22 20:38, Ted Felix wrote:
On 6/2/22 1:06 PM, mark_at_yahoo via Rosegarden-devel wrote:
I'm looking forward to seeing the fix. :)
Yeah. This is a strange one. So everyone sees it no matter what
version of Qt. I'm guessing it was introduced when we added the
too
On 6/2/22 1:06 PM, mark_at_yahoo via Rosegarden-devel wrote:
I'm looking forward to seeing the fix. :)
Yeah. This is a strange one. So everyone sees it no matter what
version of Qt. I'm guessing it was introduced when we added the toolbar
undo history dropdown. 21.06 doesn't seem to
This one's pretty esoteric. I only have Qt 5.12.8 on my machine and
I have a feeling this is a bug in Qt that has probably been fixed. If
anyone has a later version of Qt than 5.12.8, can you give this test
case a whirl?
- Create a big segment. 8 bars or so.
- Open the matrix on that
String freeze for 22.06 begins today. .ts files have been updated
against the latest code. Get the latest from git and start translating.
https://www.rosegardenmusic.com/wiki/dev:building_rosegarden_from_source
Be sure to use Qt5 when working on translations:
$ QT_SELECT=qt5
Edit > Keyboard Shortcuts... in case anyone else is looking for it.
Let us know if you find any bugs. We're about to deliver 22.06 in a
week and a half.
Ted.
On 5/29/22 5:47 PM, Mario Moles wrote:
Editor found! Thank you!
Il 29/05/22 14:42, Ted Felix ha scritto:
Follow the "
No need to wait. Instructions for building the latest from git are here:
https://www.rosegardenmusic.com/wiki/dev:building_rosegarden_from_source
Follow the "use git" path and you'll have the shortcut editor now.
If you run into any problems building from source, we can help you
On 5/28/22 1:19 AM, mark_at_yahoo via Rosegarden-user wrote:
That
said, I've found it lags behind GCC's compiled C++. I've regularly
crashed it (crashing the debugger, never a good sign) trying to step
though Qt MOC code, to the point where I've given up trying.
Ah. Yeah. I don't usually
There's one more thing to check if core dumps still aren't being
created (/proc/sys/kernel/core_pattern). See the wiki for details:
https://www.rosegardenmusic.com/wiki/dev:building_rosegarden_from_source#core_dumps
Ted.
On 5/27/22 10:07 PM, Ted Felix wrote:
On 5/27/22 9:57 PM, Ted Felix
On 5/27/22 9:57 PM, Ted Felix wrote:
I'll see if I can dig up any hints. They can be a bit difficult to
get going at first.
Ok, I found my notes on getting core dumps working everywhere:
/etc/security/limits.conf is the right way to do this. Add these lines:
* hard
On 5/27/22 6:18 AM, mark_at_yahoo via Rosegarden-user wrote:
Sorry, no. Something in my distro turns them off despite ulimit showing
unlimited.
I'll see if I can dig up any hints. They can be a bit difficult to
get going at first.
I haven't used corefiles for many years because they were
On 5/27/22 4:34 AM, mark_at_yahoo via Rosegarden-user wrote:
Update: I did get one crash with the new commit but can't recreate it.
Had something to do with changing back and forth between selecting in
the grid and in the ruler. I think I also deleted segments before it
happened. Maybe it's my
a Segment that is being edited
in Matrix and/or Notation with the velocity ruler visible.
Thanks.
Ted.
On 5/24/22 7:03 PM, Ted Felix wrote:
Looks like my "fix" for the velocity ruler issue (not being able to
adjust velocity bars freely) has introduced a new crash. Try deleting
Looks like my "fix" for the velocity ruler issue (not being able to
adjust velocity bars freely) has introduced a new crash. Try deleting a
segment that is open in the matrix with the velocity ruler visible. Boom.
I'll keep digging...
Ted.
I'm glad you're interested in this. It really does need some
documentation, and it is incomplete, lacking indicators and as you
noticed, a way to access via something other than the mouse. Hence the
"experimental" status.
I'll look into writing up some documentation and then we can
was being
iterated over (EventSelection).
This was indeed lurking for a very long time. Looks like it might go
back to before the directory reorg of 2006-02-24.
Ted.
On 5/19/22 11:39 AM, Ted Felix wrote:
On 5/19/22 7:08 AM, Will Godfrey wrote:
Unfortunately in the process I uncovered an
On 5/19/22 4:40 PM, Will Godfrey wrote:
Just a matter of curiosity, but what exactly does Rosegarden use as the system
timer?
Is it a direct count of something like get_time_of_day or is it a re-triggered
soft timer?
... or something else entirely?
Rosegarden uses many different kind of
On 5/19/22 4:58 PM, Lorenzo Sutton wrote:
There is still a quirk: if one or more notes are selected and you try
and 'grab' the velocity of another (un-selected) note in the ruler and
try to drag the velocity, the velocity(ies) of the selected notes will
move...
Yes. That's been that way
On 5/19/22 7:08 AM, Will Godfrey wrote:
Unfortunately in the process I uncovered an unrelated bug:
If you have quantize on, then select a large group of notes, intending to
move them, but realise you didn't want them quantized, so (while they are still
selected) switch quantize off Rosegarden
On 5/16/22 7:41 AM, Will Godfrey wrote:
I frequently have the velocity ruler open, to make tweaks to individual notes.
At one time, without selecting anything in the matrix you could run along the
ruler adjusting each note. These days you can't do that. It will pick up the
first one, but then
On 5/16/22 8:12 AM, Lorenzo Sutton wrote:
Ted, any other outstanding stuff you'd like us to test / check?
Since I've been doing periodic announcements to the user list, the
biggies should have been tested already: audio file improvements and the
keyboard shortcut editor.
If you can
On 5/16/22 9:04 PM, Ted Felix wrote:
Ok, I see. Yeah, this wasn't in 21.12, so it's something recent. I
will track it down. This is probably related to my changes for bug #1601.
It is indeed related to changes for bug #1601. I've added a
description of the issue there. I'll have
Thank for testing.
On 5/16/22 7:41 AM, Will Godfrey wrote:
I frequently have the velocity ruler open, to make tweaks to individual notes.
At one time, without selecting anything in the matrix you could run along the
ruler adjusting each note. These days you can't do that. It will pick up the
22.06 will be released on June 8. Please test the latest version of
Rosegarden in git as much as you can. See the release notes for areas
that need testing:
https://www.rosegardenmusic.com/wiki/dev:22.06
If you've not built Rosegarden before, give it a shot and let us know
if you run
Proposed Schedule for 22.06...
May 11: feature freeze, testing period begins
June 1: string freeze, translation period begins
June 8: Rosegarden 22.06
Ted.
___
Rosegarden-devel mailing list
Rosegarden-devel@lists.sourceforge.net - use the link below
Interesting. svn should be really stable, so introducing a conflict
should require a monumental amount of effort. Ah, svn. I don't miss you.
Maybe put an "Update from live wiki" process document on the wiki for
future reference? Then you can forget svn completely. Free up the
brain
On 4/7/22 4:15 AM, mark_at_yahoo via Rosegarden-devel wrote:
On 4/6/22 4:09 PM, Ted Felix wrote:
On 4/6/22 5:30 PM, mark_at_yahoo via Rosegarden-devel wrote:
But as I've written before, I'm an optimization freak
It's one of my specialties as well. So I'm really glad you are
looking
On 4/6/22 5:30 PM, mark_at_yahoo via Rosegarden-devel wrote:
Note: This post is going to make me even less popular with the
Rosegarden developer community than I already am.
No judgment. I'm just glad you are looking at these things and doing
something about it. There are a lot of
On 3/28/22 2:53 AM, mark_at_yahoo via Rosegarden-devel wrote:
On 3/27/22 4:17 PM, Ted Felix wrote:
Should be something of a performance bump. Please test latest git.
I tried the change (in the context of my branch's HEAD) and didn't see
much difference, either positive or negative. Maybe
On 3/27/22 6:53 PM, Ted Felix wrote:
I'll take a look and fix this. We have a Preferences class that we
introduced to solve this exact problem in other places.
Turns out no one was ever writing to those settings, so they weren't
actually being used at all. I removed the use
On 3/27/22 4:57 PM, David Faure wrote:
The main reason why this operation uses lots of CPU is the following:
LoopRuler::paintEvent() and others call GUIPalette::getColor() which *creates*
a QSettings object every time. That's slow, it means parsing one or multiple
config files from disk! The
On 3/27/22 1:49 AM, Ron Murray wrote:
I have the same problem here. Removing lmms and fluidsynth-dssi made no
difference.
I did a debug build and ran it with gdb. The resullt is attached.
Thanks. In your case it looks like something called "whysynth" is
the issue:
On 3/27/22 1:49 AM, Ron Murray wrote:
I have the same problem here. Removing lmms and fluidsynth-dssi made no
difference.
I did a debug build and ran it with gdb. The resullt is attached.
Thanks. In your case it looks like something called "whysynth" is
the issue:
OP informs me that he tracked the problem down to the ZynAddSubFX
DSSI plugin. He switched to the ZynAddSubFX standalone app and all is
well for him.
This bug can be closed for rosegarden.
OP informs me that he tracked the problem down to the ZynAddSubFX
DSSI plugin. He switched to the ZynAddSubFX standalone app and all is
well for him.
This bug can be closed for rosegarden.
I just pushed improved plugin logging as [3a07309c]. If you can,
please test latest git:
https://sourceforge.net/p/rosegarden/git/ci/master/tree/
A debug build should now let you know when it is trying to load a
plugin. And that should be the last thing you see from rosegarden when
a
I just pushed improved plugin logging as [3a07309c]. If you can,
please test latest git:
https://sourceforge.net/p/rosegarden/git/ci/master/tree/
A debug build should now let you know when it is trying to load a
plugin. And that should be the last thing you see from rosegarden when
a
On 3/19/22 7:08 AM, Rainer Hans Liffers wrote:
> I compiled the latest version of rosegarden with debugging enabled
and subsequently ran gdb as shown in attached file. Is this information
sufficient?
Yes. Thanks.
The first line relevant to rg is this:
#19 0x55e3188e in
On 3/19/22 7:08 AM, Rainer Hans Liffers wrote:
> I compiled the latest version of rosegarden with debugging enabled
and subsequently ran gdb as shown in attached file. Is this information
sufficient?
Yes. Thanks.
The first line relevant to rg is this:
#19 0x55e3188e in
malloc_consolidate(): unaligned fastbin chunk detected Aborted
We've not seen this upstream. Best bet would be to do a debug build
from source and run under gdb. Then do a backtrace when it crashes.
That should help us determine whether it is Rosegarden or one of the
many libraries it
malloc_consolidate(): unaligned fastbin chunk detected Aborted
We've not seen this upstream. Best bet would be to do a debug build
from source and run under gdb. Then do a backtrace when it crashes.
That should help us determine whether it is Rosegarden or one of the
many libraries it
On 2/5/22 7:36 PM, Ted Felix wrote:
- If one or two audio files out of many have gone missing, you may end
up in a situation where you can't open the .rg file until all the audio
files are in one place.
Just pushed a fix for this [134f0bae]. You can now skip an audio
file if you can't
Philip has been working on a new GUI keyboard shortcut editor and it's
ready for some initial testing and feedback. Grab the latest from git,
build, and go to Edit > Keyboard Shortcuts...
Be sure to rename any .rc files you might have in:
~/.local/share/rosegarden/rc
On 2/20/22 4:03 PM, mark_at_yahoo via Rosegarden-devel wrote:
Could someone (Ted?) make an executive-level decision on how I should
handle this? I'm guessing it will be something like:
1) "Hey, we're cool with it. Removing the extraneous spaces slightly
improves the code."
If you are in
On 2/20/22 6:51 AM, Philip Leishman wrote:
I can confirm this. I have openSUSE too. Luckily I didn't install the
rosegarden package.
I downloaded the package (without install) and I can see all the rc
files would go to /usr/share/rosegarden/rc/
This is surely not a good idea ?
All the
On 2/19/22 1:55 PM, mark_at_yahoo via Rosegarden-devel wrote:
The problem actually wasn't ~/.local/share/rosegarden/rc (that directory
didn't exist), but rather /usr/share/rosegarden/rc from my distro's
17.12 installed package.
That seems really wrong. What distro is this?
Ted.
On 2/18/22 1:18 PM, mark_at_yahoo via Rosegarden-devel wrote:
Is the intent to add a "triad/black-keys" control to
the GUI to allow switching it on the fly (for users who liked it the
old way)?
Yes. We try to preserve the old behavior in some way that the user
can control it. If changes
This feels to me like a bug.
In Step Recording mode, Matrix should take over the keyboard and
route the note to the selected Segment's device/channel (Instrument).
It shouldn't go through the usual main window routing. Of course, this
could get confusing when a user forgets to turn off
Thanks, David. I've committed and pushed. Also pushed the switch to
QString::endsWith().
Ted.
On 2/17/22 2:47 AM, David Faure wrote:
On jeudi 17 février 2022 07:36:10 CET mark_at_yahoo via Rosegarden-devel
wrote:
Will do. I had temporarily commented out the code in my working tree
Wow, thanks for tracking all this down.
That cmake change came from Scott Snyder back in November for the
case of building with pipewire-jack. I guess the options would be to:
1. Remove that.
2. Come up with an alternative that works in cmake 3.1.
3. Bump the required version as you've
Currently, the knobs work as follows:
- Right-click resets to default.
- Center-click sets to center (64 usually).
- Double-click allows for specification of a precise value.
Ted.
On 2/13/22 12:02 PM, AV via Rosegarden-user wrote:
I would like the parameter knobs on the track and instrument
Thanks for the input. I've opened Feature Request 499 to track this:
https://sourceforge.net/p/rosegarden/feature-requests/499/
Ted.
On 2/13/22 12:02 PM, AV via Rosegarden-user wrote:
I would like the parameter knobs on the track and instrument parameters
to be bigger so that they can be
I've just pushed a number of changes [673a5f] in an attempt to
address various complaints about audio path handling. Here's what's new...
On first save of a document with audio files you will now be prompted
to select an audio path. The audio files will be moved there during
that first
To solve the audio file location issue (i.e. why is everything always
just dumped in ~/rosegarden), I was thinking we could have a dialog pop
up when saving with audio files for the first time. It would ask where
you would like the audio files saved and provide the following options:
- To
Does anyone use JACK transport? If so, we've changed the "stop"
behavior in response to bug 1051:
https://sourceforge.net/p/rosegarden/bugs/1051/
Now Rosegarden no longer sends out a JACK Transport Stop when the end
of the composition is reached. It still sends one out if you press
On 1/20/22 8:31 PM, Kevin Cole wrote:
This is just general information that may be of use to others. I've
made a wee README.md and attached it, in case it should find it's way
into the wiki -- or is of help to someone else, since I didn't find
this info when I searched the wiki. I've also pasted
Just posted a new Rosegarden Device File (.rgd) Developer's Guide to
the wiki:
https://www.rosegardenmusic.com/wiki/dev:device_files
It's mostly done with a few sections that need expanding. Should be
quite helpful. Let me know if it needs anything.
Ted.
On 1/17/22 4:05 PM, Kevin Cole wrote:
OK, I'll split them out again into "Panel" and "GM" files.
GM is already covered by GM.rgd. GM is a standard. No need to
reinvent the file for the PSR-220.
The programs in GM2.rgd pretty closely match the GM programs listed in
the Yamaha manual.
Just pushed an update to git that should help address the issues
people are having with ~/rosegarden filling up with a mess of audio
files for multiple projects.
It's always been possible to change the audio file path in the
document properties (View > Document Properties... > Audio; or
On 1/17/22 8:07 AM, Kevin Cole wrote:
But, even though sending from the computer to
the keyboard uses the GM mappings, playing on the keyboard directly
uses the Panel mappings. So I suppose question 0 is "How do I make
sense of that?"
That's just how Yamaha designed it. It makes sense in
Thanks for the info. I just pushed a fix for these to master. I
left the duplicate Casio file just to be safe. It's tiny.
Ted.
On 1/12/22 2:06 PM, Kevin Cole wrote:
They say a foolish consistency is the hobgoblin of small minds... I
guess my mind is small. ;-)
I'm using rosegarden
Just changed the "For notation" checkbox in the Segment Parameters
box to "Exclude from Printing". It now has the exact opposite sense.
If it is unchecked, the Segment will be included in printing (the
default). If it is checked, the Segment will not be included in
printing. Also changed
On 1/12/22 2:06 PM, Kevin Cole wrote:
* `HammondSK1.rgd` is not gzip'd.
This was fixed in a later version. I think I caught it when I was
fixing all the Expression controller defaults. Might have been somebody
else, though.
Good catch on the others. I'll add to my todo.
Ted.
Just pushed a change to volume/pan handling that I hope only affects
loading older files.
Please test latest git.
Check for any problems with initial volume and pan as loaded from
your files. This should only affect MIDI instruments and not audio or
soft synth, so check those too if
On 1/11/22 9:04 PM, Kevin Cole wrote:
So you may have a much better handle on what's to be
added.
If you look at the two most recent ones that I made, you'll get an
idea of what these should look like:
Yamaha-P105.rgd
Kawai-CA95-CS10-MT1.rgd
A keymap for percussion is the other thing
that can be removed.
Ted.
On 1/11/22 9:04 PM, Kevin Cole wrote:
On Tue, Jan 11, 2022 at 8:10 PM Ted Felix wrote:
Cool. Thanks. I've taken a quick look at it. There are some more
things that likely need adding. But this is a good first version.
We'll at least include this in the next
Cool. Thanks. I've taken a quick look at it. There are some more
things that likely need adding. But this is a good first version.
We'll at least include this in the next release.
I'll see if I can piece together some info on the missing pieces for
you. It's mostly boilerplate that
Perfect. Then it's probably set up on channel 10 by default.
It's probably just the usual GM mapping, so the key mapping should be
the usual. Otherwise they would have included a key mapping in the manual.
Regardless, get some experience with GM mode, then play around with
panel mode
.
On 1/11/22 12:54 PM, Kevin Cole wrote:
On Tue, Jan 11, 2022 at 12:43 PM Ted Felix <mailto:t...@tedfelix.com>> wrote:
On 1/11/22 10:57 AM, Kevin Cole wrote:
> However, the manual for the PSR-220 contains two lists of
instruments:
>
> Since I'm really quite
On 1/11/22 10:57 AM, Kevin Cole wrote:
However, the manual for the PSR-220 contains two lists of instruments:
Since I'm really quite new to it all, I'm not sure which one to use.
GM is already covered by RG in the GM.rgd and GM2.rgd files.
Since they can't be used at the same time (bank
Just pushed the changes to the Copy/Cut/Delete behavior in the
Notation editor to go with the changes I made for Matrix. Previously
there were two sets of copy/cut commands in the menu. One for notes in
Notation (e.g. Edit > Cut) and one for control changes in the current
ruler (e.g.
Off the top of my head, that looks like one of those errors you get
when there's something wrong with sf's servers. Maybe try again
tomorrow? However, it looks like your new "change_okular_description"
branch is indeed there. But using dfaure_kde for the user doesn't work:
On 1/8/22 7:51 AM, David Faure wrote:
However I found the following issues, can you let me know if you want to fix
them or if I should look into them myself (and in that case maybe you
have hints about where I should look)?
If you have time, that would be great. Otherwise I think we'll open
On 1/1/22 3:45 PM, Kevin Cole wrote:
1. Is there already a PSR-220 file somewhere? If so, where?
No. However, Yamaha uses their own standards that are pretty much
the same across a lot of their keyboards (especially the PSRs). So, you
can probably look at all the existing .rgd files for
On 12/28/21 12:17 PM, Lorenzo Sutton wrote:
This was all scored and composed in Rosegarden (with the exception of a
couple of small bits recorded 'live', e.g. the piano) and only using
FLOSS (Ardour, xjadeo, ...), in particular Yoshimi was the main
synth/instrument used.
Cool stuff.
Thanks to Philip's diligent work, we are now down from 37 to only 30
bugs open this cycle.
Please skim through the bug tracker and see if there's anything you'd
like to work on. Thanks.
https://sourceforge.net/p/rosegarden/bugs/
Ted.
___
Just pushed some changes to the Copy/Cut/Delete behavior in the
Matrix editor. Previously there were two sets of copy/cut commands in
the menu. One for notes in the Matrix (e.g. Edit > Cut) and one for
control changes in the current ruler (e.g. Controllers > Cut controller
events).
Now
== ROSEGARDEN 21.12 RELEASED ==
The Rosegarden team is proud to announce the release of version 21.12
of Rosegarden, a MIDI sequencer that features a rich understanding of
music notation along with basic support for digital audio.
http://www.rosegardenmusic.com/
Included in this
101 - 200 of 1018 matches
Mail list logo
