linuxsampler-devel — This list is for discussing LinuxSampler development issues and ideas

Re: [Linuxsampler-devel] Maximum Disk Streams Segfaults [Nastiest backtrace ever]

[Yclept N. <orb...@gm...>]

On Mon, Oct 24, 2011 at 7:03 PM, Yclept Nemo <orb...@gm...> wrote:
> Versions:
> Salamander Grand Piano V2
> liblscp-svn 2132
> libgig-svn 2274
> linuxsampler-svn 2277
> qsampler-svn 2271
>
> For the most part the setup works very well, except that it is limited
> in the number of voices (amount of notes). Too many notes, and
> LinuxSampler only plays silence.
>
> If during runtime (via qsampler), I increase the maximum number of
> voices and the maximum number of disk streams to 128 and 180
> respectively, LinuxSampler segfaults. The backtrace is too large to
> attach, so I mirrored it as an attachment at
> http://hpaste.org/raw/53096. [Note: An identical email containing the
> attachment is still awaiting moderator approval]
>
> If I compile LinuxSampler with --enable-max-streams=180
> --enable-max-voices=128, then while loading the SFZ file, LinuxSampler
> gives the following error:
> LSCPServer: Client connection established on socket:4.
> LSCPServer: Client connection established on socket:5.
> Starting disk thread...OK
> Scheduling '/storage/samples/gigasamples/piano/salamander.grand.piano.v2/SalamanderGrandPianoV2_48khz24bit/SalamanderGrandPianoV2.sfz'
> (Index=0) to be loaded in background (if not loaded yet).
> Loading sfz file
> '/storage/samples/gigasamples/piano/salamander.grand.piano.v2/SalamanderGrandPianoV2_48khz24bit/SalamanderGrandPianoV2.sfz'...OK
> Loading sfz instrument
> ('/storage/samples/gigasamples/piano/salamander.grand.piano.v2/SalamanderGrandPianoV2_48khz24bit/SalamanderGrandPianoV2.sfz',0)...OK
> Caching initial samples...sfz::Engine error: Failed to load
> instrument, cause: Unknown exception while trying to parse sfz file.
>
> I've narrowed the problem down to the maximum number of disk streams.
> For example I can increase the maximum number of voices to 256 without
> problem (> maximum number of disk streams which is 90), but the
> error/segfault occurs when the maximum number of disk streams reaches
> somewhere around 105-115.
>
> Solution would be great. I'm not playing a symphony here, just a
> simple one-piano piece (no more than 6 1/8 notes at a time).
>

Clarification:

1] Segfault:
The segfault is only triggered when changing the number of disk
streams during runtime *and* when an instrument/channel is currently
loaded

2] Error:
The error only happens if GetChannelInfo is called before
EngineChannelBase finishes caching the samples. For example, if the
cache is not finalized you see something like the following. (Notice
"INSTRUMENT_STATUS: -4", this is the error QSampler displays).

EngineChannelBase: progress 36EngineChannelBase: progress 36
RenderAudio(Samples=1024)
Condition::WaitIf: bCondition=0  TimeoutSeconds=0  TimeoutNanoSeconds=0
Condition::Waitif() -> LOCK()
Condition::Waitif() -> LOCK() passed
Condition::Set() -> LOCK()
Condition::Set() -> LOCK() passed
Condition::Set() -> broadcasting 'false' condition
Condition::WaitIf: bCondition=0  TimeoutSeconds=0  TimeoutNanoSeconds=0
Condition::Waitif() -> LOCK()
Condition::Waitif() -> LOCK() passed
Condition::Waitif() -> waiting for 'true' condition
RenderAudio(Samples=1024)
RenderAudio(Samples=1024)
RenderAudio(Samples=1024)
RenderAudio(Samples=1024)
RenderAudio(Samples=1024)
LSCPServer: Got command on socket -1, calling parser.
LSCPServer: [GET CHANNEL INFO 0
]
LSCPServer: GetChannelInfo(SamplerChannel=0)
LSCPServer::AnswerClient(ReturnMessage=ENGINE_NAME: SFZ
VOLUME: 1.000
AUDIO_OUTPUT_DEVICE: 0
AUDIO_OUTPUT_CHANNELS: 2
AUDIO_OUTPUT_ROUTING: 0,1
MIDI_INPUT_DEVICE: 0
MIDI_INPUT_PORT: 0
MIDI_INPUT_CHANNEL: 0
INSTRUMENT_FILE:
/storage/samples/gigasamples/piano/salamander.grand.piano.v2/SalamanderGrandPianoV2_48khz24bit/SalamanderGrandPianoV2.sfz
INSTRUMENT_NR: 0
INSTRUMENT_NAME:
INSTRUMENT_STATUS: -4
MUTE: false
SOLO: false
MIDI_INSTRUMENT_MAP: 0
.
)LSCPServer: Done parsing on socket -1.

For some strange reason, it seems the greater the number of disk
streams, either the longer it takes for the sample cache to be
generated, or the sooner GetChannelInfo is called.

The error basically prevents LinuxSampler from working: any subsequent
operations, such as Quiting or Removing-the-Channel, all throw the
same Error:-4.

[Linuxsampler-devel] Maximum Disk Streams Segfaults [Nastiest backtrace ever]

[Yclept N. <orb...@gm...>]

Versions:
Salamander Grand Piano V2
liblscp-svn 2132
libgig-svn 2274
linuxsampler-svn 2277
qsampler-svn 2271

For the most part the setup works very well, except that it is limited
in the number of voices (amount of notes). Too many notes, and
LinuxSampler only plays silence.

If during runtime (via qsampler), I increase the maximum number of
voices and the maximum number of disk streams to 128 and 180
respectively, LinuxSampler segfaults. The backtrace is too large to
attach, so I mirrored it as an attachment at
http://hpaste.org/raw/53096. [Note: An identical email containing the
attachment is still awaiting moderator approval]

If I compile LinuxSampler with --enable-max-streams=180
--enable-max-voices=128, then while loading the SFZ file, LinuxSampler
gives the following error:
LSCPServer: Client connection established on socket:4.
LSCPServer: Client connection established on socket:5.
Starting disk thread...OK
Scheduling '/storage/samples/gigasamples/piano/salamander.grand.piano.v2/SalamanderGrandPianoV2_48khz24bit/SalamanderGrandPianoV2.sfz'
(Index=0) to be loaded in background (if not loaded yet).
Loading sfz file
'/storage/samples/gigasamples/piano/salamander.grand.piano.v2/SalamanderGrandPianoV2_48khz24bit/SalamanderGrandPianoV2.sfz'...OK
Loading sfz instrument
('/storage/samples/gigasamples/piano/salamander.grand.piano.v2/SalamanderGrandPianoV2_48khz24bit/SalamanderGrandPianoV2.sfz',0)...OK
Caching initial samples...sfz::Engine error: Failed to load
instrument, cause: Unknown exception while trying to parse sfz file.

I've narrowed the problem down to the maximum number of disk streams.
For example I can increase the maximum number of voices to 256 without
problem (> maximum number of disk streams which is 90), but the
error/segfault occurs when the maximum number of disk streams reaches
somewhere around 105-115.

Solution would be great. I'm not playing a symphony here, just a
simple one-piano piece (no more than 6 1/8 notes at a time).

Re: [Linuxsampler-devel] [PATCH] Fix crash when restoring LV2 plugin in Ardour

[Dan M. <al...@gm...>]

Hi Christian!

I've only been testing using soundfonts and qsampler to load them but
I get the crash every time I try loading an A3 session on my 64bit Deb
Wheezy box. I posted a backtrace took from the 2277 svn linuxsampler
to the Ardour tracker (which unfortunately seems to be down right now
for me) but I would expect it would be the same errors for Dave's
patched LS I'm running now as it crashes at the same point.

Dan



On Fri, Oct 21, 2011 at 12:49 PM, Christian Schoenebeck
<sch...@cr...> wrote:
> On Thursday 20 October 2011 13:25:48 Dan MacDonald wrote:
>> Hi Dave!
>>
>> On Wed, Oct 19, 2011 at 11:22 PM, David Robillard <d...@dr...> wrote:
>> > Hello,
>> >
>> > Attached is a patch that fixes a NULL pointer dereference problem that
>> > occurs when LinuxSampler is restored as an LV2 in Ardour 3.0.
>>
>> Just tried your patch under Wheezy x64 and the latest A3 still
>> segfaults here when trying to open a session containing the LS LV2
>> unfortunately.
>
> Hi guys!
>
> Does this crash occur under certain conditions, e.g. when gigedit was opened
> before or something? Or does this crash always happen, no matter what the
> exact circumstances are?
>
> CU
> Christian
>

Re: [Linuxsampler-devel] [PATCH] Fix crash when restoring LV2 plugin in Ardour

[Christian S. <sch...@li...>]

On Thursday 20 October 2011 13:25:48 Dan MacDonald wrote:
> Hi Dave!
> 
> On Wed, Oct 19, 2011 at 11:22 PM, David Robillard <d...@dr...> wrote:
> > Hello,
> > 
> > Attached is a patch that fixes a NULL pointer dereference problem that
> > occurs when LinuxSampler is restored as an LV2 in Ardour 3.0.
> 
> Just tried your patch under Wheezy x64 and the latest A3 still
> segfaults here when trying to open a session containing the LS LV2
> unfortunately.

Hi guys!

Does this crash occur under certain conditions, e.g. when gigedit was opened 
before or something? Or does this crash always happen, no matter what the 
exact circumstances are?

CU
Christian

Re: [Linuxsampler-devel] [PATCH] Fix crash when restoring LV2 plugin in Ardour

[Dan M. <al...@gm...>]

Hi Dave!

On Wed, Oct 19, 2011 at 11:22 PM, David Robillard <d...@dr...> wrote:
> Hello,
>
> Attached is a patch that fixes a NULL pointer dereference problem that
> occurs when LinuxSampler is restored as an LV2 in Ardour 3.0.

Just tried your patch under Wheezy x64 and the latest A3 still
segfaults here when trying to open a session containing the LS LV2
unfortunately.


Dan

[Linuxsampler-devel] [PATCH] Fix crash when restoring LV2 plugin in Ardour

[David R. <d...@dr...>]

Hello,

Attached is a patch that fixes a NULL pointer dereference problem that
occurs when LinuxSampler is restored as an LV2 in Ardour 3.0.

This problem does not occur in at least one other host, qsampler, and I
am not sure why.  Perhaps because the plugin has not been activated yet?
The persist extension does not specify anything about this yet, opinions
welcome.

This is admittedly a fix based on shallow understanding, a regular LS
dev might have a better idea if this will cause any problems.  It does
fix the crash, anyway.

Peace,

-dr

[Linuxsampler-devel] loopstart=0

[Nicola P. <nic...@gm...>]

Hi, I notice that if I set loopstart=0, the loop doesn't works.
To play the loop I have to set loopstart to 1 or above.
I don't know if it is right, I think it depends on which is consider to 
be the first sample of an audio file: 0 or 1?

     thanks

-- 
Nicola

[Linuxsampler-devel] Improving the portability of LS LV2 using projects

[Dan M. <al...@gm...>]

Hi LS devs!

I'm sure some of you already know me off the LAU/LAD lists as I've
been the main tester of MIDI in Ardour 3 and I've FINALLY got round to
concentrating on using LS under A3! Aren't you lucky? :D

I'm addressing the list as I'm hoping we can make some small
adjustments to the LS LV2 plugin and/or libgig and maybe LS itself
which will make it much easier (read: possible) to transfer Ardour 3
or qtractor sessions that use the LS LV2 plugin between machines/users
because at the moment the engine just gives a "sorry can't find the
instrument file" type of error if the instrument isn't located at
precisely the original path.

I don't know if the LV2 spec or any of its extensions cater for this
yet but if the instrument file isn't found in the original path then I
would like to see LS looking for the files in the same folder as the
A3 or qtractor session/project file, which is where I would like to
store them most of the time- certainly when collaborating on a
project. Paul tells me A3 wouldn't have any probs with such files
being stored within an A3 session directory. Ideally, if LS fails to
find an instrument in neither the original path nor in the same folder
as the current session/project file then it would display a dialogue
prompting you for the path to the missing file.

Big thanks to all the LS devs and contributors for bringing us such a
powerful sampler and the first really useful, poweful LV2 plugin!

Thanks for your help and a fantastic app!

Dan

Re: [Linuxsampler-devel] [Open Octave Development] cannot start jackd with oostudio anymore

[Christopher C. <st...@tr...>]

Hi Anton,

The Open Octave Template will only work with Linuxsampler from svn that
has sfz support.

You would need to install the latest libgig, liblscp and linuxsampler
from svn source code.

Hopefully this is solved very soon by the Linuxsampler guys putting out
releases that the distros can use to get up to speed.

I will ask them.

Thanks!

Christian: ping! :)


Anton wrote:
>
> Op zondag 16 oktober
> 2011 20:40:48 schreef Alex Stone:
>
>
>
> Sorry I was trying to
> connect with qjackctl tried everything but can not get sound
> when playog the external midi keyboard connected to m-audio
> delta 1010 .
>
>
>
> By the way instruments
> are also not loading and I have sonatina installed.
>
> Manually I cannot load
> them because the instruments are no gig.
>
>
>
> Forget my question the
> default templates are not working for me no problem oomidi is
> working fine with my own gig instruments..
>
> I do not want to spoil
> your time.
>
>
>
> > > Op zondag 16
> oktober 2011 20:14:58 schreef Alex Stone:
>
> > >
>
> > > Yes its
> playing but only if I use my mouse and click on the
>
> > > keyboard
> tones from Jsampler ( linuxsamler gui) virtual keyboard
>
> > >
>
> > > > > Op
> zondag 16 oktober 2011 10:30:49 schreef Christopher Cherrett:
>
> > > > >
>
> > > > > I
> do not understand this :
>
> > > > > You
> can set -X to something like raw and your keyboard will show as
>
> > > > > a
>
> > > > >
>
> > > > >
> jack device.
>
> > > > >
>
> > > > > In
> qjackctl I have set midi to raw
>
> > > > > No
> sound
>
> > > > >
>
> > > > >
> > Anton wrote:
>
> > > > >
> > > Op zaterdag 15 oktober 2011 16:37:34 schreef Anton:
>
> > > > >
> > >
>
> > > > >
> > >
>
> > > > >
> > > sorry messed up my system now its al working again.
>
> > > > >
> > >
>
> > > > >
> > > In your templates you use linuxsampler midi device -
> with jack
>
> > > > >
>
> > > > >
> instead
>
> > > > >
>
> > > > >
> > > of alsa and audio -device - jack.
>
> > > > >
> > >
>
> > > > >
> > >
>
> > > > >
> > > I have to use midi-device with alsa for getting sound
> ?
>
> > > > >
> > >
>
> > > > >
> > > Is that normal or am I missing something.
>
> > > > >
> >
>
> > > > >
> > midi-device as in your external keyboard?
>
> > > > >
> >
>
> > > > >
> > If so that depends on the jack command.
>
> > > > >
> >
>
> > > > >
> > I use alsa for connecting my keyboard and jack for
> connecting
>
> > > > >
> > all internal midi connections.
>
> > > > >
> >
>
> > > > >
> > The jack command determines if jack registers the external
>
> > > > >
> > devices through jack or alsa. Look up -X
>
> > > > >
> >
>
> > > > >
> > You can set -X to something like raw and your keyboard will
> show
>
> > >
>
> > > as a
>
> > >
>
> > > > >
> > jack device.
>
> > > > >
> >
>
> > > > >
> > Let me know if that clears it up.
>
> > > > >
> >
>
> > > > >
> > Thanks!
>
> > > > >
> >
>
> > > > >
> > > > Did you change the command ?
>
> > > > >
> > > >
>
> > > > >
> > > > With version 2011.3.1
>
> > > > >
> > > >
>
> > > > >
> > > > I cannot startup jackd anymore with oostudio.
>
> > > > >
> > > >
>
> > > > >
> > > > jackd error no message buffer overruns ?
>
> > > >
>
> > > > Anton,
> are you getting a midi signal in the track?
>
> > > >
>
> > > > Alex.
>
> >
>
> > So the audio into
> oom is working ok. Do you have your midi output
>
> > correctly assigned
> in the track, and the output port itself connected to
>
> > linuxsampler in
> the connections manager?
>
> >
>
> > Alex.
>
>
>


-- 
Christopher Cherrett
cch...@op...
http://www.openoctave.org

Re: [Linuxsampler-devel] Sfz: sample name with spaces

[Nicola P. <nic...@gm...>]

Il 16/10/2011 20:14, Alex Stone ha scritto:
>> Hi, I notice that LS gives me an error (Can't get sample info: System
>> error) if the sample name in a sfz file contains two spaces (i.e.
>> 'Piano  C#2.wav').
>>
>> --
>> Nicola
>>
>
> Nicola,  i've hit the same challenge. I solved it by renaming the sample (s).
>
>
> Alex

Right, it works wiith only one space :-)

     thanks

-- 
Nicola

[Linuxsampler-devel] Sfz: sample name with spaces

[Nicola P. <nic...@gm...>]

Hi, I notice that LS gives me an error (Can't get sample info: System 
error) if the sample name in a sfz file contains two spaces (i.e. 
'Piano  C#2.wav').

-- 	
Nicola

Re: [Linuxsampler-devel] Problem wit h pre-build Mac version

[Ralf M. <rm...@mh...>]

On Thu, 6 Oct 2011 16:55:41 +0200, Christian Schoenebeck wrote
> On Thursday 06 October 2011 16:13:47 Ebrahim Mayat wrote:
> > On Oct 6, 2011, at 10:07 AM, R. Mattes wrote:

> > > I using the build from
> > > http://download.linuxsampler.org/packages/osx/snapshots/ ,
> > > the tarball has 20-Sep-2011 00:06 as its date.
> >
> > Okay, that was not uploaded by myself. Andreas, Grigor ?
>
> That is not uploaded by anybody. The snapshots are automatically
> built directly by our server. Maybe nobody has tried the SFZ engine
> in that snaphot of OSX. Have you tried older snapshots as well,
>  whether the problem was introduced at a certain point?

No, not yet, but I'll try later. BTW, this problem doesn't seem to
be related to the SFZ engine - I get the same results with a GIG
sample set or a SF2 font.

Cheers, RalfD 

Re: [Linuxsampler-devel] Problem wit h pre-build Mac version

[Christian S. <sch...@li...>]

On Thursday 06 October 2011 16:13:47 Ebrahim Mayat wrote:
> On Oct 6, 2011, at 10:07 AM, R. Mattes wrote:
> > On Thu, 06 Oct 2011 09:47:40 -0400, Ebrahim Mayat wrote
> > 
> >> The pre-built binary that you are talking about was made prior to
> >> 
> >  the implemen tation of the sfz engine.
> > 
> > Hmm, I don't think that's the problem here - otherise LS would shurely
> > have reported an error loading the SFZ sample set.
> > I using the build from
> > http://download.linuxsampler.org/packages/osx/snapshots/ ,
> > the tarball has 20-Sep-2011 00:06 as its date.
> 
> Okay, that was not uploaded by myself. Andreas, Grigor ?

That is not uploaded by anybody. The snapshots are automatically built 
directly by our server. Maybe nobody has tried the SFZ engine in that snaphot 
of OSX. Have you tried older snapshots as well, whether the problem was 
introduced at a certain point?

CU
Christian

Re: [Linuxsampler-devel] Problem wit h pre-build Mac version

[Ebrahim M. <eb...@ma...>]

On Oct 6, 2011, at 10:07 AM, R. Mattes wrote:

> On Thu, 06 Oct 2011 09:47:40 -0400, Ebrahim Mayat wrote
>
>> The pre-built binary that you are talking about was made prior to
>  the implemen tation of the sfz engine.
>
> Hmm, I don't think that's the problem here - otherise LS would shurely
> have reported an error loading the SFZ sample set.
> I using the build from http://download.linuxsampler.org/packages/osx/snapshots/ 
> ,
> the tarball has 20-Sep-2011 00:06 as its date.

Okay, that was not uploaded by myself. Andreas, Grigor ?

E

Re: [Linuxsampler-devel] Problem wit h pre-build Mac version

[Ebrahim M. <eb...@ma...>]

On Oct 6, 2011, at 9:21 AM, Ralf Mattes wrote:

> Hello list,
>
> I'm trying to reuse an older Mac Mini as a sampler box. I downloaded
> and the prebuild binary from the linuxsampler webpage. Unfortunately,
> when running the sampler with a SFZ sampleset that works without any
> problems on my linux systems, the sampler only creates very loud white
> noise. Strangely the volume of that noise does _not_ depend on the
> volume settings in qsampler nor the system volume settings.
> Any ideas what's going wrong here? System information:
> Mac Mini PPC 1.5 GHz PPC G4
> Operating System 1.5.8
>
> Audio output set to:
> Coreaudio
> 3 Buffers of size 256
> 2 Channels
> with 44100 Sampling Rate
>
> TIA Ralf Mattes

Ralf

The pre-built binary that you are talking about was made prior to the  
implementation of the sfz engine.

"While the modular design of LinuxSampler allows for multi-engine and  
multi-format features, the present implementation of the Gig engine  
already has the capability for producing virtual instruments with  
realistic emulations."  - <http://www.linuxsampler.org/osx.html>

  I haven't had the time recently to build the latest version. Sorry  
about that.
Ebrahim

“Your time is limited, so don’t waste it living someone else’s life.  
Don’t be trapped by dogma – which is living with the results of other  
people’s thinking. Don’t let the noise of other’s opinions drown out  
your own inner voice. And most important, have the courage to follow  
your heart and intuition. They somehow already know what you truly  
want to become. Everything else is secondary.” - Steve Jobs

[Linuxsampler-devel] Problem wit h pre-build Mac version

[Ralf M. <rm...@mh...>]

Hello list,

I'm trying to reuse an older Mac Mini as a sampler box. I downloaded
and the prebuild binary from the linuxsampler webpage. Unfortunately,
when running the sampler with a SFZ sampleset that works without any
problems on my linux systems, the sampler only creates very loud white
noise. Strangely the volume of that noise does _not_ depend on the 
volume settings in qsampler nor the system volume settings. 
Any ideas what's going wrong here? System information:
 Mac Mini PPC 1.5 GHz PPC G4
 Operating System 1.5.8 

Audio output set to:
 Coreaudio
 3 Buffers of size 256
 2 Channels
 with 44100 Sampling Rate

 TIA Ralf Mattes

Re: [Linuxsampler-devel] tarballs

[Alex S. <ale...@op...>]

> On Wednesday 05 October 2011 11:36:28 Alex Stone wrote:
>> We've been testing with the latest SVN for some time now, and haven't
>> had
>> any problems (you know with our particular setups, the test of stability
>> and robust behaviour is going to get a hammering), so i ask if you can
>> tarball the latest SVN, so we can point users and packagers alike to
>> fresh
>> code, which of course includes SFZ.
>
> Yes, I was also thinking about automatically rolling source tarballs of
> new
> SVN versions of the sampler. Since we already have an automatic built
> system
> in place, it shouldnt be much work to also create source tarball snapshots
> automatically.
>
> I try to do that when I find a bit time.
>
> CU
> Christian
>


Thanks,

Alex.

Re: [Linuxsampler-devel] tarballs

[Christian S. <sch...@li...>]

On Wednesday 05 October 2011 11:36:28 Alex Stone wrote:
> We've been testing with the latest SVN for some time now, and haven't had
> any problems (you know with our particular setups, the test of stability
> and robust behaviour is going to get a hammering), so i ask if you can
> tarball the latest SVN, so we can point users and packagers alike to fresh
> code, which of course includes SFZ.

Yes, I was also thinking about automatically rolling source tarballs of new 
SVN versions of the sampler. Since we already have an automatic built system 
in place, it shouldnt be much work to also create source tarball snapshots 
automatically.

I try to do that when I find a bit time.

CU
Christian

[Linuxsampler-devel] tarballs

[Alex S. <ale...@op...>]

Hi fellas. Since the release of OOMidi-2011, and the strong link with
Linuxsampler, we've had a lot of queries about LS, and the latest SFZ 
included builds.

Users are installing packages from distros with outdated LS packages, and
we're trying to help them get up to date, including communication and
working in partnership with packagers.


We've been testing with the latest SVN for some time now, and haven't had
any problems (you know with our particular setups, the test of stability
and robust behaviour is going to get a hammering), so i ask if you can
tarball the latest SVN, so we can point users and packagers alike to fresh
code, which of course includes SFZ.

We're continuing to push the LS message out to all we can, and having
latest version tarballs, will help ease the sometimes daunting install
process for new users who may or may not be confident with building from
SVN.






Thanks,

Alex.

Re: [Linuxsampler-devel] build fail

[Andreas P. <and...@br...>]

On 2011-10-03 18:57, Alex Stone wrote:
> One of our users has been trying to get linuxsampler built from svn, and
> got this fail:
>
> http://pastebin.com/EM5DeFPi
>
> He tells us his libtool version is 2.4.
>
> Anything obvious in here i can pass on to him?

Weird. I have libtool 2.4 too, but I don't have any problems like that. 
Can you send the "libtool" file that was generated by configure?

/Andreas

[Linuxsampler-devel] build fail

[Alex S. <ale...@op...>]

One of our users has been trying to get linuxsampler built from svn, and
got this fail:

http://pastebin.com/EM5DeFPi

He tells us his libtool version is 2.4.

Anything obvious in here i can pass on to him?


Alex.

Re: [Linuxsampler-devel] Program Change Patch

[Christopher C. <st...@tr...>]

Andreas Persson wrote:
> On 2011-09-30 08:55, Christian Schoenebeck wrote:
>> You can probably go ahead and commit it. Just try to adjust as much as Andreas
>> suggested, and somebody of us will adjust the remainder afterwards.
>>
>> CU
>> Christian
>>
>> On Friday 30 September 2011 00:05:23 Christopher Cherrett wrote:
>>> Any word on this?
>>>
>>> Christopher Cherrett wrote:
>>>> Thank you very much for looking at this.
>>>>
>>>> I am not sure how to speak on the removal of functions but if this is
>>>> working can it be committed by you?
> I committed the patch now. I did some further cleanups, but I didn't 
> remove the functions I mentioned. They were all in the liblinuxsampler 
> API, and I thought it was nicer to change the API as little as possible. 
> Instead I made sure GetMidiProgram returns the program set by the latest 
> program change.
>
> /Andreas
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
Oh and we released:

http://www.openoctave.org

liblscp is a dependency now because we have a lot of direct tie ins to
linuxsampler. There is more about it on the release at the webpage.

Thanks!

Re: [Linuxsampler-devel] Program Change Patch

[Christopher C. <st...@tr...>]

Andreas Persson wrote:
> On 2011-09-30 08:55, Christian Schoenebeck wrote:
>> You can probably go ahead and commit it. Just try to adjust as much as Andreas
>> suggested, and somebody of us will adjust the remainder afterwards.
>>
>> CU
>> Christian
>>
>> On Friday 30 September 2011 00:05:23 Christopher Cherrett wrote:
>>> Any word on this?
>>>
>>> Christopher Cherrett wrote:
>>>> Thank you very much for looking at this.
>>>>
>>>> I am not sure how to speak on the removal of functions but if this is
>>>> working can it be committed by you?
> I committed the patch now. I did some further cleanups, but I didn't 
> remove the functions I mentioned. They were all in the liblinuxsampler 
> API, and I thought it was nicer to change the API as little as possible. 
> Instead I made sure GetMidiProgram returns the program set by the latest 
> program change.
>
> /Andreas
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
A very big thank you!

Re: [Linuxsampler-devel] Program Change Patch

[Andreas P. <and...@br...>]

On 2011-09-30 08:55, Christian Schoenebeck wrote:
> You can probably go ahead and commit it. Just try to adjust as much as Andreas
> suggested, and somebody of us will adjust the remainder afterwards.
>
> CU
> Christian
>
> On Friday 30 September 2011 00:05:23 Christopher Cherrett wrote:
>> Any word on this?
>>
>> Christopher Cherrett wrote:
>>> Thank you very much for looking at this.
>>>
>>> I am not sure how to speak on the removal of functions but if this is
>>> working can it be committed by you?

I committed the patch now. I did some further cleanups, but I didn't 
remove the functions I mentioned. They were all in the liblinuxsampler 
API, and I thought it was nicer to change the API as little as possible. 
Instead I made sure GetMidiProgram returns the program set by the latest 
program change.

/Andreas

Re: [Linuxsampler-devel] Midi support for envelopes?

[Christian S. <sch...@li...>]

On Friday 30 September 2011 13:17:25 Andrew C wrote:
> Hey all,
> 
> Is there any functionality in linuxsampler for editing the ADSR/Filter
> cutoff/res/amp envelopes in real-time via midi ccs, or do I have to
> just use gigedit and a mouse for now?

Envelope MIDI controls are not hard coded right now. They must be specified by 
the .gig file.

CU
Christian