Re: [Rosegarden-user] Rosegarden DSSI plug-in synthesizers open and editor issues

2014-09-09 Thread Michael Gerdau
  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: m...@qata.de
 GPG-keys available on request or at public keyserver

--
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

2014-09-09 Thread D. Michael McIntyre
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

--
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] (no subject)

2014-09-09 Thread Holger Marzen
On Tue, 9 Sep 2014, Pierre Bruynooghe wrote:

 Here is th config.log : http://pastebin.com/GNQ5Ybhh
 Pierre

Bonjour Pierre,

the most important line is:

configure:6265: WARNING: Required JACK library not found, building with no 
audio!

In the file configure I find:
pkg-config --exists --print-errors jack = 0.100

That's probably the cause. Please run
  pkg-config --exists --print-errors jack = 0.100 ; echo $?
in a terminal.

I am not experienced with that pkg-config stuff. But your jack might
lack a file for pkg-config.

  pkg-config --list-all | grep jack
would be interesting as well.

--
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

2014-09-09 Thread David Christensen
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