Re: [Rosegarden-user] Rosegarden DSSI plug-in synthesizers open and editor issues
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 -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] Rosegarden DSSI plug-in synthesizers open and editor issues
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 -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
[Rosegarden-user] Rosegarden DSSI plug-in synthesizers open and editor issues
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 -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
