From: David C. <dpc...@ho...> - 2014-09-07 04:43:07
|
rosegarden-user: I've attempted to use Rosegarden using default Linux distribution binary packages on: a. Debian Wheezy (12.04). b. Fedora 20 (13.10). In both cases, I've run into problems with DSSI plug-in synthesizers: 1. For multi-track Rosegarden projects on both Debian and Fedora, if I assign a track to a DSSI plug-in synthesizer instrument, save the Rosegarden project, close Rosegarden, start Rosegarden, and then open the project, things look okay in the top-level Rosegarden window, but when I play the music I get wrong instruments. For example, I arranged J.S. Bach's Invention No. 8 for two violins and two cellos. When I open and play the project, I hear two violins, one cello, and one piano. 2. If I select each track in turn and click on its Track Parameters -> Instrument drop-down list, I can get three correct instruments and one silent track (the silent track depends upon the order in which I selected tracks?). 3. On one trial in Fedora, I then chose Track -> Unmute All Tracks from the menu and was able to get all four correct instruments. (This alone does not fix the wrong instrument issue.) 4. On Fedora, the DSSI Editor button doesn't work -- a process is started in the background (as shown by 'ps -A' in the console), but the plug-in editor dialog never opens. If I exit Rosegarden and attempt to start Rosegarden, Rosegarden hangs at the splash screen "Initializing plugin manager..." because the DSSI editor process is still running. If I manually kill the leftover DSSI editor process, Rosegarden completes starting. 5. On Debian, the Xsynth patch save/ load functionality in the editor doesn't work right -- if I create some patches, say #63-65, save them, and load them back into #63-65 on another Rosegarden channel, I'd get the default Xsynth patch. I seem to recall on trial where loaded them into patches #0-2, and that worked. I see that Rosegarden is now at version 14.02. What's the solution? i. File bug reports with the distribution package maintainers, wait for patches, download source, patch, rebuild? ii. File bug reports with Rosegarden, wait for patches, download source, patch, rebuild? iii. Download current Rosegarden source and build? iv. Something else? TIA, David |
From: Holger M. <ho...@ma...> - 2014-09-07 07:15:52
|
On Sat, 6 Sep 2014, David Christensen wrote: > rosegarden-user: > > I've attempted to use Rosegarden using default Linux distribution binary > packages on: > > a. Debian Wheezy (12.04). > > b. Fedora 20 (13.10). > > > In both cases, I've run into problems with DSSI plug-in synthesizers: > > 1. For multi-track Rosegarden projects on both Debian and Fedora, if I > assign a track to a DSSI plug-in synthesizer instrument, save the > Rosegarden project, close Rosegarden, start Rosegarden, and then open > the project, things look okay in the top-level Rosegarden window, but > when I play the music I get wrong instruments. For example, I arranged > J.S. Bach's Invention No. 8 for two violins and two cellos. When I open > and play the project, I hear two violins, one cello, and one piano. One problem I ran into was: Synth plugins are not assigned to tracks. They are assigned to instruments. So be sure that each track has a different instrument assigned. A good apporach is: Track 1, instrument 1. Track 2, instrument 2. And so on. |
From: D. M. M. <ros...@gm...> - 2014-09-07 12:39:24
|
On 09/07/2014 12:42 AM, David Christensen wrote: > What's the solution? Whenever I can get a user with a problem to build the development source, that's what I prefer strongly. It is quite possible and easy to build and run multiple different versions of Rosegarden, as generally only one of them has to be installed for all of them to work. Typically you run your distro Rosegarden with /usr/bin/rosegarden and any local builds run as ./rosegarden right out of the top level source directory. Once you're up and running with that, if you can reproduce the problem, then the next move is to file a bug report with us on the tracker at SourceForge. We'll look into it as soon as we get a chance, and report back. The more specific you can be in the bug report, the better. For example, which DSSI syth plugin are you using? What soundfont? If you can provide the exact .rg or .mid file you're working with, so much the better. Off the top of my head, what you're describing could be any number of things. -- D. Michael McIntyre |
From: David C. <dpc...@ho...> - 2014-09-07 20:15:58
|
On 09/07/2014 12:15 AM, Holger Marzen wrote: > Synth plugins are not assigned to tracks. They are assigned to > instruments. So be sure that each track has a different instrument > assigned. A good apporach is: Track 1, instrument 1. Track 2, instrument > 2. And so on. That's how I did it. David |
From: Holger M. <ho...@ma...> - 2014-09-08 04:08:09
|
On Sun, 7 Sep 2014, David Christensen wrote: > On 09/07/2014 12:15 AM, Holger Marzen wrote: > > Synth plugins are not assigned to tracks. They are assigned to > > instruments. So be sure that each track has a different instrument > > assigned. A good apporach is: Track 1, instrument 1. Track 2, instrument > > 2. And so on. > > That's how I did it. OK, then it could be - a buggy synth plugin - a buggy Rosegarden I never ran into this problem. One thing that can't hurt is to compile a recent Rosegarden. That's not too difficult. Another approach is using another softsynth, e.g. fluidsynth-dssi with the FluidR3_GM.sf2 soundfont. Regards Holger |
From: David C. <dpc...@ho...> - 2014-09-09 01:35:22
Attachments:
2-violins-2-cellos-20140830-111901.rg
|
On 09/07/2014 05:39 AM, D. Michael McIntyre wrote: > Whenever I can get a user with a problem to build the development > source, that's what I prefer strongly. I won't be able to get to that for a while. > If you can provide the exact .rg or .mid file you're working with, so much the better. See attached. David |
From: D. M. M. <ros...@gm...> - 2014-09-09 03:15:04
|
On 09/08/2014 09:35 PM, David Christensen wrote: > I won't be able to get to that for a while. I can repeat the problem with development code. Two violins, a cello, and a piano. Why the piano? There's nothing obvious. -- D. Michael McIntyre |
From: Michael G. <mg...@qa...> - 2014-09-09 08:01:32
|
> > I won't be able to get to that for a while. > > I can repeat the problem with development code. Two violins, a cello, > and a piano. Why the piano? There's nothing obvious. According to the OPs initial report this piano had been created and saved as a second cello. It becoming a piano on (re-)opening the arrangement is the problem :) Best wishes, Michael -- Michael Gerdau email: mg...@qa... GPG-keys available on request or at public keyserver |
From: D. M. M. <ros...@gm...> - 2014-09-09 08:20:48
|
On 09/09/2014 04:01 AM, Michael Gerdau wrote: > According to the OPs initial report this piano had been created and > saved as a second cello. It becoming a piano on (re-)opening the > arrangement is the problem :) Yes, I understand that. It's not obvious why this is happening, because everything looks good on the surface. Everything is assigned to instruments correctly, the instruments are defined correctly in the XML (the instrument in question comes out sounding as a piano even though it clearly specifies cello) and so on like that. I even managed to get a cello playing for the fourth voice just by randomly diddling controls during my exploration. Something weird is going on here. It's a valid bug report. What's causing it and when we'll solve it, I have no idea yet. I tested to confirm the problem, but haven't investigated the root cause yet. -- D. Michael McIntyre |
From: David C. <dpc...@ho...> - 2014-09-09 21:47:19
|
On 09/09/2014 01:20 AM, D. Michael McIntyre wrote: > It's not obvious why this is happening, because everything looks good on > the surface. Everything is assigned to instruments correctly, the > instruments are defined correctly in the XML (the instrument in question > comes out sounding as a piano even though it clearly specifies cello) > and so on like that. I even managed to get a cello playing for the > fourth voice just by randomly diddling controls during my exploration. > Something weird is going on here. It's a valid bug report. > What's causing it and when we'll solve it, I have no idea yet. I tested > to confirm the problem, but haven't investigated the root cause yet. One additional detail that may or may not be related to the second cello to piano mismatch problem -- I initially copied the FluidSynth general MIDI soundfont file to a folder in my home directory (/home/dpchrist/sf2/FluidR3_GM.sf2) and used that path when working on the project with Soundgarden. After wiping the machine and rebuilding it, and also when working on another machine, the home directory soundfont folder does not exist. When I open the Rosegarden project file, Rosegarden complains about the missing soundfont file, but finds the soundfont file of the same name in the system tree and loads that. (I assume the rest of you see this when you open the project file ?) HTH, David |
From: D. M. M. <ros...@gm...> - 2014-09-09 21:58:28
|
On 09/09/2014 05:47 PM, David Christensen wrote: > One additional detail that may or may not be related to the second cello > to piano mismatch problem -- I initially copied the FluidSynth general > MIDI soundfont file to a folder in my home directory Not related to the problem. I hacked the XML in my test copy of the file to reference the system path directly for all four of the plugin instruments used. -- D. Michael McIntyre |