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

Re: [Linuxsampler-devel] docs

[Raphaël M. <rmo...@gm...>]

Le 30 avr. 2015 à 11:01, Christian Schoenebeck <sch...@li...> a écrit :

> On Wednesday 29 April 2015 22:21:09 Raphaël Mouneyres wrote:
>> The display format is really good, and pleasant to read, this is really
>> good work.
> 
> Thanks!
> 
>> Now It's a good reason to try to script the Hihat behaviour i need (and was
>> only made workable with some tricky midi treatment before the sampler).
>> But i may lack some timing tools (i need a sort of enveloppe tool)... Is
>> there a way so i could make a arithmetic operation every 10ms for example
>> ?
> 
> You "could" write a note event handler and use the wait() function:
> 
> http://doc.linuxsampler.org/Instrument_Scripts/NKSP_Language/Reference/wait_function/
> 
> and then update all required synthesis parameters directly in a while loop.
> I said "could" because I did not have time yet to fully implement the wait() 
> function. As the document states, a wait() call currently ignores the 
> parameter passed to it, because the required scheduling code is yet missing. 
> Instead the script is always resumed in the next audio period.
> 
> But since the wait() function is one of the most fundamental functions for 
> writing useful scripts, this is probably one of the next things I'm going to 
> do. So stay tuned!
> 
> Best regards,
> Christian Schoenebeck

So this could still be tested with a uncontrollable but fixed wait time (audio period).
I'll let you know how it goes when I put my hand in the code.

Raphaël

Re: [Linuxsampler-devel] Building on OSX / Xcode 6

[Raphaël M. <rmo...@gm...>]

Le 30 avr. 2015 à 11:12, Christian Schoenebeck <sch...@li...> a écrit :

> On Wednesday 29 April 2015 13:38:14 Balogh Mihaly wrote:
>> Hi! Anyone here had any luck with building on OSX. I’m using Yosemite with
>> Xcode 6 but I’m getting:
>> 
>> make: aclocal: No such file or directory
> 
> Building the sampler on OS X is currently not very easy. You have to deal with 
> various dependencies. Probably you might just want to use the latest 
> automatically built snapshot for OS X, which includes LinuxSampler (stand-
> alone, VST, Audio Unit), QSampler, JSampler/Fantasia, gigedit and command line 
> tools:
> 
> 	http://download.linuxsampler.org/packages/osx/snapshots/
> 
> It is automatically rebuilt on every Subversion commit.

I confirm the snapshot worked perfectly on OSX 10.9.5

Raphaël

Re: [Linuxsampler-devel] Building on OSX / Xcode 6

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

On Wednesday 29 April 2015 13:38:14 Balogh Mihaly wrote:
> Hi! Anyone here had any luck with building on OSX. I’m using Yosemite with
> Xcode 6 but I’m getting:
> 
> make: aclocal: No such file or directory

Building the sampler on OS X is currently not very easy. You have to deal with 
various dependencies. Probably you might just want to use the latest 
automatically built snapshot for OS X, which includes LinuxSampler (stand-
alone, VST, Audio Unit), QSampler, JSampler/Fantasia, gigedit and command line 
tools:

	http://download.linuxsampler.org/packages/osx/snapshots/

It is automatically rebuilt on every Subversion commit.

CU
Christian

Re: [Linuxsampler-devel] docs

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

On Wednesday 29 April 2015 22:21:09 Raphaël Mouneyres wrote:
> The display format is really good, and pleasant to read, this is really
> good work.

Thanks!

> Now It's a good reason to try to script the Hihat behaviour i need (and was
> only made workable with some tricky midi treatment before the sampler).
> But i may lack some timing tools (i need a sort of enveloppe tool)... Is
> there a way so i could make a arithmetic operation every 10ms for example
> ?

You "could" write a note event handler and use the wait() function:

http://doc.linuxsampler.org/Instrument_Scripts/NKSP_Language/Reference/wait_function/

and then update all required synthesis parameters directly in a while loop.
I said "could" because I did not have time yet to fully implement the wait() 
function. As the document states, a wait() call currently ignores the 
parameter passed to it, because the required scheduling code is yet missing. 
Instead the script is always resumed in the next audio period.

But since the wait() function is one of the most fundamental functions for 
writing useful scripts, this is probably one of the next things I'm going to 
do. So stay tuned!

Best regards,
Christian Schoenebeck

Re: [Linuxsampler-devel] docs

[Raphaël M. <rmo...@gm...>]

The display format is really good, and pleasant to read, this is really good work.

Now It's a good reason to try to script the Hihat behaviour i need (and was only made workable with some tricky midi treatment before the sampler).
But i may lack some timing tools (i need a sort of enveloppe tool)... Is there a way so i could make a arithmetic operation every 10ms for example ?

Raphaël 

Le 29 avr. 2015 à 15:11, Christian Schoenebeck <sch...@li...> a écrit :

> Some news: I thought it's time to write some decent documentation about the 
> new instrument script feature. This is an introduction to the NKSP language 
> itself:
> 
> 	http://doc.linuxsampler.org/Instrument_Scripts/NKSP_Language/
> 
> And this is the reference documentation, covering all built-in functions, 
> built-in variables and constants, etc.:
> 
> 	http://doc.linuxsampler.org/Instrument_Scripts/NKSP_Language/Reference/
> 
> There is also a short explanation how to stick scripts to your .gig files:
> 
> 	http://doc.linuxsampler.org/Gigedit/Managing_Scripts/
> 
> Along with those new articles, I also wrote a new online documentation 
> software system which this new site is using to make writing and maintaining 
> documentation as simple and easy as possible, while still preserving all the 
> powerful abilities of HTML & co (if really required in some cases). And guess 
> what, there is even already an article about it: ;-)
> 
> 	http://doc.linuxsampler.org/Writing_Docs/
> 
> My plan is to move our (meanwhile completely outdated) manuals and tutorials 
> to this dedicated new site. Anybody interested to help writing some 
> documentation is very much invited!
> 
> I still have some hope, that somebody might put its hands on creating the 
> first publicly available documentation for the SFZ(2) file format.
> 
> CU
> Christian
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

[Linuxsampler-devel] docs

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

Some news: I thought it's time to write some decent documentation about the 
new instrument script feature. This is an introduction to the NKSP language 
itself:

	http://doc.linuxsampler.org/Instrument_Scripts/NKSP_Language/

And this is the reference documentation, covering all built-in functions, 
built-in variables and constants, etc.:

	http://doc.linuxsampler.org/Instrument_Scripts/NKSP_Language/Reference/

There is also a short explanation how to stick scripts to your .gig files:

	http://doc.linuxsampler.org/Gigedit/Managing_Scripts/

Along with those new articles, I also wrote a new online documentation 
software system which this new site is using to make writing and maintaining 
documentation as simple and easy as possible, while still preserving all the 
powerful abilities of HTML & co (if really required in some cases). And guess 
what, there is even already an article about it: ;-)

	http://doc.linuxsampler.org/Writing_Docs/

My plan is to move our (meanwhile completely outdated) manuals and tutorials 
to this dedicated new site. Anybody interested to help writing some 
documentation is very much invited!

I still have some hope, that somebody might put its hands on creating the 
first publicly available documentation for the SFZ(2) file format.

CU
Christian

[Linuxsampler-devel] Building on OSX / Xcode 6

[Balogh M. <spi...@ya...>]

Hi! Anyone here had any luck with building on OSX. I’m using Yosemite with Xcode 6 but I’m getting:

make: aclocal: No such file or directory

I used Homebrew to install autotools:

$ which aclocal
/usr/local/bin/aclocal

Any feedback appreciated,
Thanks!

[Linuxsampler-devel] musicbitz.org

[RDP <gli...@gm...>]

The idea ( amongst other things ) was a for an  Open Source sample library
collection.

At present it is a blank canvas, open to suggestion, if anyone cares to
respond.

Cheers,


Chris P.

[Linuxsampler-devel] [ANN] QjackCtl 0.3.13, Qsynth 0.3.9, Qsampler 0.3.0 released!

[Rui N. C. <rn...@rn...>]

The pre-LAC2015 [1] release frenzy continues... ;)

Now for the next batch...


* QjackCtl - A JACK Audio Connection Kit Qt GUI Interface [2] *

   QjackCtl 0.3.13 is out.

   QjackCtl is a simple Qt application to control the JACK [4] sound 
server, for the Linux Audio infrastructure.

website:
   http://qjackctl.sourceforge.net

downloads:
   http://sourceforge.net/projects/qjackctl/files

- source tarball:
   http://downloads.sourceforge.net/qjackctl/qjackctl-0.3.13.tar.gz

- source package:
 
http://downloads.sourceforge.net/qjackctl/qjackctl-0.3.13-22.rncbc.suse132.src.rpm

- binary packages:
 
http://downloads.sourceforge.net/qjackctl/qjackctl-0.3.13-22.rncbc.suse132.i586.rpm
 
http://downloads.sourceforge.net/qjackctl/qjackctl-0.3.13-22.rncbc.suse132.x86_84.rpm

change-log:
- Added application description as freedesktop.org's AppData [9].
- Setup dialog form is now modeless.
- Introducing brand new active patchbay reset/disconnect-all user 
preference option.
- Current highlighted client/port connections are now drawn with thicker 
connector lines.
- New user preference option on whether to show the nagging 'program 
will keep running in the system tray' message, on main window close.
- Connections lines now drawn with anti-aliasing; connections splitter 
handles width is now reduced.
- Drop missing or non-existent patchbay definition files from the most 
recent used list.


* Qsynth - A FluidSynth Qt GUI Interface [3] *

   Qsynth 0.3.9 is out.

   Qsynth is a FluidSynth [6] GUI front-end application written in C++ 
around the Qt4 toolkit using Qt Designer.

website:
   http://qsynth.sourceforge.net

downloads:
   http://sourceforge.net/projects/qsynth/files

- source tarball:
   http://downloads.sourceforge.net/qsynth/qsynth-0.3.9.tar.gz

- source package:
 
http://downloads.sourceforge.net/qsynth/qsynth-0.3.9-5.rncbc.suse132.src.rpm

- binary packages:
 
http://downloads.sourceforge.net/qsynth/qsynth-0.3.9-5.rncbc.suse132.i586.rpm
 
http://downloads.sourceforge.net/qsynth/qsynth-0.3.9-5.rncbc.suse132.x86_84.rpm

change-log:
- Added application description as freedesktop.org's AppData [9].
- New user preference option on whether to show the nagging 'program 
will keep running in the system tray' message, on main window close.
- Application close confirm warning is now raising the main window as 
visible and active for due top level display, especially applicable when 
minimized to the system tray.
- A man page has been added.
- Translations install directory change.
- Allow the build system to include an user specified LDFLAGS.
- Czech (cs) translation updated (by Pavel Fric, thanks).


* Qsampler - A LinuxSampler Qt GUI Interface [4] *

   Qsampler 0.3.0 is out.

   Qsampler is a LinuxSampler [7] GUI front-end application written in 
C++ around the Qt4 toolkit using Qt Designer.

website:
   http://qsampler.sourceforge.net

downloads:
   http://sourceforge.net/projects/qsampler/files

- source tarball:
   http://downloads.sourceforge.net/qsampler/qsampler-0.3.0.tar.gz

- source package:
 
http://downloads.sourceforge.net/qsampler/qsampler-0.3.0-13.rncbc.suse132.src.rpm

- binary packages:
 
http://downloads.sourceforge.net/qsampler/qsampler-0.3.0-13.rncbc.suse132.i586.rpm
 
http://downloads.sourceforge.net/qsampler/qsampler-0.3.0-13.rncbc.suse132.x86_84.rpm

change-log:
- Added application description as freedesktop.org's AppData [9].
- Added this "Don't ask/show this again" option to some if not most of 
the nagging warning/error message boxes.
- Mac OS X: Fixed default path of linuxsampler binary.
- When closing qsampler and showing the user the dialog whether to stop 
the LinuxSampler backend, set the default selection to "Yes".
- Master volume slider now getting proper layout when changing its main 
toolbar orientation.
- Messages standard output capture has been slightly improved as for 
non-blocking i/o, whenever available.
- Adjusted configure check for libgig to detect the new --includedir.
- A man page has beed added (making up Matt Flax's work on debian, thanks).
- Translations install directory change.
- Added support for SF2 instrument names/preset enumeration.
- Added instrument list popup on channel strip which shows up when the 
instrument name is clicked. Allows faster switching among instruments of 
the same file.
- Adjusted configure check for libgig to detect its new --libdir 
(impolitely forcing the user now to have at least libgig 3.3.0).


License:
   QjackCtl, Qsynth and Qsampler are free, open-source software, 
distributed under the terms of the GNU General Public License (GPL) 
version 2 [8] or later.


Weblog (upstream support):
   http://www.rncbc.org

See also:
   http://www.rncbc.org/drupal/node/877


References:

[1] LAC2015@JGU-Mainz - Linux Audio Conference 2015
     The Open Source Music and Sound Conference
     April 9-12 @ Johannes Gutenberg University (JGU) Mainz, Germany
     http://lac.linuxaudio.org/2015/

[2] QmidiCtl - A JACK Audio Connection Kit Qt GUI Interface
     http://qmidictl.sourceforge.net

[3] Qsynth - A FluidSynth Qt GUI Interface
     http://qsynth.sourceforge.net

[4] Qsampler - A LinuxSampler Qt GUI Interface
     http://qsampler.sourceforge.net

[5] JACK Audio Connection Kit
     http://jackaudio.org

[6] FluidSynth - A SoundFont Synthesizer
     A real-time software synthesizer based on SoundFont 2 specifications
     http://www.fluidsynth.org

[7] LinuxSampler - The Linux Sampler Project
     A modular, streaming capable, realtime audio sampler
     http://www.linuxsampler.org

[8] GPL - GNU General Public License
     http://www.gnu.org/copyleft/gpl.html

[9] AppData Specification
     http://people.freedesktop.org/~hughsient/appdata/


Enjoy && have some fun!
-- 
rncbc aka. Rui Nuno Capela

Re: [Linuxsampler-devel] SFZ design tool "sfzd" soon for Linux..?

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

Another project that features a "sfz import / export" is Polyphone: 
http://www.polyphone.fr ... and it's also GPL3 ! :-)

Il 01/03/2015 16:10, Christian Schoenebeck ha scritto:
> On Sunday 01 March 2015 13:20:15 Frank Neumann wrote:
>> just found this via bedroomproducersblog.com:
>>
>> http://mildon.me/sfzdesigner
>>
>> It's Windows-only for now, but it states "Linux & OSX: coming soon..."
>> at the bottom. Might be a little more handy than editing text files :-).
> On first view I don't have the impression that a cross-platform GUI toolkit
> was used. So I am a bit skeptical that a Linux version might be released soon.
> But would be nice of course.
>
> However I would already be glad if at least some kind of open specification of
> the SFZ2 format would be available in public, free for everybody.
>
> Either one of the two would certainly push the SFZ format forward.
>
> CU
> Christian
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel


-- 
Nicola

Re: [Linuxsampler-devel] SFZ design tool "sfzd" soon for Linux..?

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

On Sunday 01 March 2015 13:20:15 Frank Neumann wrote:
> just found this via bedroomproducersblog.com:
> 
> http://mildon.me/sfzdesigner
> 
> It's Windows-only for now, but it states "Linux & OSX: coming soon..."
> at the bottom. Might be a little more handy than editing text files :-).

On first view I don't have the impression that a cross-platform GUI toolkit 
was used. So I am a bit skeptical that a Linux version might be released soon. 
But would be nice of course.

However I would already be glad if at least some kind of open specification of 
the SFZ2 format would be available in public, free for everybody.

Either one of the two would certainly push the SFZ format forward.

CU
Christian

[Linuxsampler-devel] SFZ design tool "sfzd" soon for Linux..?

[Frank N. <bea...@we...>]

Hi all,

just found this via bedroomproducersblog.com:

http://mildon.me/sfzdesigner

It's Windows-only for now, but it states "Linux & OSX: coming soon..."
at the bottom. Might be a little more handy than editing text files :-).

Greetings,
Frank

Re: [Linuxsampler-devel] global amp_velcurve

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

Il 07/02/2015 16:55, Andreas Persson ha scritto:
> Nicola Pandini skrev den 2015-02-03 16:24:
>> Hi, is there a way to apply an "amp_velcurve_X" value globally on all
>> groups of a .sfz file? I'd like to avoid to define the amp_velcurve on
>> each group...
> No, sorry, for that you would need the "<global>" opcode, but that one
> is not yet implemented in LS.
>
>> Another question: how LS interpolate the velcurve between two points?
>> i.e. between amp_velcurve_1=0.5 and amp_velcurve_50=0.8?
> It's linear interpolation between each specified point.

Thank you Andreas, could you also give me the formula to calculate the 
amp_velcurve points of a standard gain curve(amp_veltrack=100)? I need 
to find the differences between the points of the standard gain and the 
one I made.

     Thanks again!

-- 
Nicola

Re: [Linuxsampler-devel] SFZ2 Format Specification?

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

Philip Bennefall skrev den 2015-02-06 18:21:
> Hi all,
> 
> I signed up to this mailing list primarily because I am very interested 
> in the SFZ format. I have read the original format specification, but a 
> bit of googling indicates that there is an unofficial version 2 
> specification floating around.

The sfz v2 format is not really a single format with a specification, at
least that's not how it started. It started as different extensions to
the sfz v1 format used in different Cakewalk synthesizers.

But the extensions were then documented in an appendix in the book
"Cakewalk Synthesizers: From Presets to Power User" by Simon Cann, and
after that other sampler software started to support subsets of the opcodes.

 I am looking to implement at least a
> subset of the SFZ format for a sampler that will be integrated in a 
> package for adaptive video game music rendering, and it would be great 
> to start from the 2.0 specification if this is the direction in which we 
> are headed. I submitted a request to get access to the format 
> specification on Google docs, but haven't heard back. Is there a way in 
> which I could possibly read the specification? Also, is it acceptable to 
> write an implementation based on the specification (is it public domain, 
> in other words)?

I think much of the spec on Google docs you refer to was typed in right
from the book, so maybe that's why it's now inaccessible.

You can find a list of all sfz v2 opcodes here:
http://www.linuxsampler.org/sfz/, but unfortunately there are no
descriptions of what they do.

/Andreas

Re: [Linuxsampler-devel] global amp_velcurve

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

Nicola Pandini skrev den 2015-02-03 16:24:
> Hi, is there a way to apply an "amp_velcurve_X" value globally on all 
> groups of a .sfz file? I'd like to avoid to define the amp_velcurve on 
> each group...

No, sorry, for that you would need the "<global>" opcode, but that one
is not yet implemented in LS.

> Another question: how LS interpolate the velcurve between two points? 
> i.e. between amp_velcurve_1=0.5 and amp_velcurve_50=0.8?

It's linear interpolation between each specified point.

/Andreas

[Linuxsampler-devel] SFZ2 Format Specification?

[Philip B. <phi...@el...>]

Hi all,

I signed up to this mailing list primarily because I am very interested 
in the SFZ format. I have read the original format specification, but a 
bit of googling indicates that there is an unofficial version 2 
specification floating around. I am looking to implement at least a 
subset of the SFZ format for a sampler that will be integrated in a 
package for adaptive video game music rendering, and it would be great 
to start from the 2.0 specification if this is the direction in which we 
are headed. I submitted a request to get access to the format 
specification on Google docs, but haven't heard back. Is there a way in 
which I could possibly read the specification? Also, is it acceptable to 
write an implementation based on the specification (is it public domain, 
in other words)?

Thanks in advance for any help.

Kind regards,

Philip Bennefall
Elias Software AB
http://www.eliassoftware.com/

[Linuxsampler-devel] global amp_velcurve

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

Hi, is there a way to apply an "amp_velcurve_X" value globally on all 
groups of a .sfz file? I'd like to avoid to define the amp_velcurve on 
each group...
Another question: how LS interpolate the velcurve between two points? 
i.e. between amp_velcurve_1=0.5 and amp_velcurve_50=0.8?

     Thanks!

-- 
Nicola

[Linuxsampler-devel] docs.linuxsampler.org

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

Hi!

Since documentation and website are currently in a horrible old condition, I 
thought about launching a new site for documentation, probably as new 
subdomain docs.linuxsampler.org (or under www.linuxsampler.org/docs/).

Flat layout: Here is a mockup as an overall layout suggestion for that 
documentation site:

http://download.linuxsampler.org/pix/screenshots/mockup_docs_linuxsampler_org.png

I am not the biggest fan of flat layout (especially since many companies 
already brought their layouts on "kindergarten flat" level), but in this case 
I though it makes sense. The suggested font used is a free one called
"Ek Mukta", a modern sans serif font, providing a large set of font weights 
(ultra thin, thin, normal, semi bold, bold, ultra bold) and is well readable 
for human beings. You can preview this font in various styles i.e. on Google 
Fonts.


Visual structure:

- On the very top there is a hard coded dark gray bar with global links to 
  important topics, i.e. links to the documentation entry points for our 
  various apps, links to other servers, etc.

- Just below the hard coded link bar, there is an auto generated light gray 
  navigation bar, showing the current overall tree location on the 
  documentation web server, which allows to jump back to some parent article.

- Main block to the right with white background; the current article.

- On the very left there is table of contents of the currently visible 
  article. The user may auto scroll the current article by clicking on an item 
  of that table of contents, and vice versa the table of contents 
  automatically highlights the currently visible paragraph when the user 
  scrolls the article on the right.

- Hard coded footer on the very bottom, copyright notice, and probably some 
  more links, etc.


File & Directory Structure:

My suggestion is to write the actual articles as stripped-down HTML input 
files, without "html" tag, without "body" tag, root tag would be an "article" 
tag, everything inside that root "article" tag would be regular html (and CSS) 
with all its possibilities. The html input files would be managed on svn and 
our build server would auto generate the actual (static) website by processing 
those input html files whenever somebody commits something new, thus auto 
generating especially navigation bar, table of contents, website header and 
footer for each page. Each input HTML file would be named "index.html" and 
thus being in its own directory on svn. The resulting input directory names 
and input directory structure would be taken to auto generate the navigation 
structure of the website.

Besides the actual articles files, there would be couple other input files 
defining the overall look of the website globally, separate from the 
individual articles.

An example input article file based on these suggestions might look like this:

<article title="Conditional Statements">
  <p>Conditional statements are bla bla bla.</p>

  <h3>A deeper view</h3>
  <p>Bla bla bla.</p>

  <h3>And even more</h3>
  <p>Bla bla bla. <a href="foo">Read more about topic foo ...</a></p>

  <h3>Starting the hack</h3>
  <p>
    Bla bla bla.
    <code lang="nksp">
on init
  declare $a := "bla"
  declare @h := "Hello "
  declare const @w := "world!"
  message(@h)
  message(@w)
end on
    </code>
    bla bla bla bla.
  </p>

  <h2>The next level</h2>
  <p>Bla bla bla.</p>

</article>

So table of contents of an article would be auto generated by reading the 
regular "h2" and "h3" html tags. Article name and thus website page title 
would be defined by the "title" attribute of the "article" tag.

Syntax highlighting for example code blocks would also be auto generated. The 
"lang" attribute of the "code" tag would be mandatory to give the build server 
an idea which programming language was meant for being able to produce correct 
syntax highlighting.

Opinions, suggestions and tomatoes appreciated!

CU
Christian

Re: [Linuxsampler-devel] LV2 plugin crashing after loading it in Ardour

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

On Monday 26 January 2015 17:10:34 Fernanda Monteiro wrote:
> Hi Christian, thanks for the tip. I've just recompiled with debug symbols
> but I'm in doubt about how to backtrace it as a LV2 plugin, since if I run
> LinuxSampler prior to it, plugin will just fail due to can't bind to the
> right port anyway, so I can't have LS running before that in gdb. Any
> suggestions?

Same thing. Just that you start Ardour instead of LinuxSampler in the way 
described. However since LinuxSampler is then launched by Ardour as plugin, 
you must install LinuxSampler before launching Ardour. Compiling Ardour with 
debugging symbols turned on as well, is definitely recommended.

Another option (instead of starting Ardour with gdb) is enabling coredump 
output on your system:

	ulimit -c unlimited

Then you can run Ardour normally (without debugger). Once it crashes it will 
automatically write a core dump file to the local directory, which is 
essentially a memory dump of the Ardour process at the time when the crashed 
happened. You can then get the back trace like this:

	gdb /full/path/to/ardourbinary /full/path/to/coredumpfile
	bt

Both solutions usually yield the same result.

CU
Christian

Re: [Linuxsampler-devel] LV2 plugin crashing after loading it in Ardour

[Fernanda M. <cri...@gm...>]

Hi Christian, thanks for the tip. I've just recompiled with debug symbols
but I'm in doubt about how to backtrace it as a LV2 plugin, since if I run
LinuxSampler prior to it, plugin will just fail due to can't bind to the
right port anyway, so I can't have LS running before that in gdb. Any
suggestions?

2015-01-23 11:28 GMT-02:00 Christian Schoenebeck <
sch...@li...>:

> On Thursday 22 January 2015 19:39:23 Fernanda Monteiro wrote:
> > Hi. LinuxSampler works ok on standalone, but when I add it into a channel
> > in Ardour it segfaults and crash the program. This is only happening with
> > LS until now. I've compiled with max debug level so I could have a trace
> of
> > its operation.
>
> When reporting a crash, please always provide a back trace. Debug messages
> alone are usually not helpful to find the root cause of a crash. Here are
> instructions how to generate a back trace for a crash happening with
> LinuxSampler.
>
>         https://bugs.linuxsampler.org/
>
> CU
> Christian
>



-- 
*Fernanda Monteiro de Oliveira*

Mobile: (+55 11) 99553 9362
Alt e-mail: nan...@ou...
Social portfolio: http://about.me/nandameik

Re: [Linuxsampler-devel] LV2 plugin crashing after loading it in Ardour

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

On Thursday 22 January 2015 19:39:23 Fernanda Monteiro wrote:
> Hi. LinuxSampler works ok on standalone, but when I add it into a channel
> in Ardour it segfaults and crash the program. This is only happening with
> LS until now. I've compiled with max debug level so I could have a trace of
> its operation.

When reporting a crash, please always provide a back trace. Debug messages 
alone are usually not helpful to find the root cause of a crash. Here are 
instructions how to generate a back trace for a crash happening with 
LinuxSampler.

	https://bugs.linuxsampler.org/

CU
Christian

[Linuxsampler-devel] LV2 plugin crashing after loading it in Ardour

[Fernanda M. <cri...@gm...>]

Hi. LinuxSampler works ok on standalone, but when I add it into a channel
in Ardour it segfaults and crash the program. This is only happening with
LS until now. I've compiled with max debug level so I could have a trace of
its operation.

mei@Meistache ~ $ ardour2
Ardour 2.8.16
   (built using 1:2.8.16+git20131003-1 and GCC version 4.8.2)
Copyright (C) 1999-2008 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel
Baker

Ardour comes with ABSOLUTELY NO WARRANTY
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This is free software, and you are welcome to redistribute it
under certain conditions; see the source for copying conditions.
loading default ui configuration file /etc/ardour2/ardour2_ui_default.conf
loading user ui configuration file /home/mei/.ardour2/ardour2_ui.conf
Loading ui configuration file /etc/ardour2/ardour2_ui_light.rc
/etc/ardour2/ardour2_ui_light.rc:123: Clearlooks configuration option
"menuitemstyle" is not supported and will be ignored.
/etc/ardour2/ardour2_ui_light.rc:124: Clearlooks configuration option
"listviewitemstyle" is not supported and will be ignored.
/etc/ardour2/ardour2_ui_light.rc:125: Clearlooks configuration option
"progressbarstyle" is not supported and will be ignored.
Loading ui configuration file /etc/ardour2/ardour2_ui_light.rc
/etc/ardour2/ardour2_ui_light.rc:123: Clearlooks configuration option
"menuitemstyle" is not supported and will be ignored.
/etc/ardour2/ardour2_ui_light.rc:124: Clearlooks configuration option
"listviewitemstyle" is not supported and will be ignored.
/etc/ardour2/ardour2_ui_light.rc:125: Clearlooks configuration option
"progressbarstyle" is not supported and will be ignored.
ardour: [INFO]: Ardour will be limited to 4096 open files
loading system configuration file /etc/ardour2/ardour_system.rc
loading user configuration file /home/mei/.ardour2/ardour.rc
ardour: [INFO]: Using SSE optimized routines
ardour: [INFO]: looking for control protocols in
/home/mei/.ardour2/surfaces/:/usr/lib/ardour2/surfaces/
ardour: [ERROR]: ControlProtocolManager: cannot load module
"/usr/lib/ardour2/surfaces//libardour_genericmidi.so"
(/usr/lib/ardour2/surfaces//libardour_genericmidi.so: undefined symbol:
_ZN5boost6system15system_categoryEv)
ardour: [ERROR]: ControlProtocolManager: cannot load module
"/usr/lib/ardour2/surfaces//libardour_tranzport.so"
(/usr/lib/ardour2/surfaces//libardour_tranzport.so: undefined symbol:
_ZN5boost6system15system_categoryEv)
powermate: Opening of powermate failed - No such file or directory
ardour: [INFO]: Control protocol powermate not usable
ardour: [INFO]: Control surface protocol discovered: "Mackie"
NSD response -5 folder = /home/mei/AudioWorks/First_Test
loading bindings from /etc/ardour2/mnemonic-us.bindings

(ardour-2.8.16:5548): Gtk-WARNING **: EnableTranslation: missing action
EnableTranslation
Session writable based on /home/mei/AudioWorks/First_Test/
Condition:: constructor, bInitialCondition=0
Condition:: constructor, bInitialCondition=0
Condition:: constructor, bInitialCondition=0
Condition:: constructor, bInitialCondition=0
Condition:: constructor, bInitialCondition=0
Condition:: constructor, bInitialCondition=0
Condition::WaitIf: bCondition=0  TimeoutSeconds=0  TimeoutNanoSeconds=0
Condition::Waitif() -> LOCK()
Condition::Waitif() -> LOCK() passed
Condition::Waitif() -> waiting for 'true' condition
Condition::Set() -> LOCK()
Condition::Set() -> LOCK() passed
Condition::Set() -> broadcasting 'true' condition
Condition::Set() -> LOCK()
Condition::Set() -> LOCK() passed
Condition::Set() -> broadcasting 'true' condition
Condition::Waitif() -> awakened from 'true' condition waiting
Condition::WaitIf: bCondition=0  TimeoutSeconds=0  TimeoutNanoSeconds=0
Condition::Waitif() -> LOCK()
Condition::Waitif() -> LOCK() passed
Condition::WaitAndUnlockIf() -> UNLOCK()
Condition::WaitAndUnlockIf() -> UNLOCK() passed
Condition:: constructor, bInitialCondition=0
Condition::WaitIf: bCondition=0  TimeoutSeconds=0  TimeoutNanoSeconds=0
Condition::Waitif() -> LOCK()
Condition::Waitif() -> LOCK() passed
Condition::Waitif() -> waiting for 'true' condition
Condition::Set() -> LOCK()
Condition::Set() -> LOCK() passed
Condition::Set() -> broadcasting 'true' condition
Condition::Waitif() -> awakened from 'true' condition waiting
linuxsampler: init feature: http://lv2plug.in/ns/ext/instance-access
linuxsampler: init feature: http://lv2plug.in/ns/ext/data-access
linuxsampler: init feature: http://lv2plug.in/ns/ext/urid#map
linuxsampler: init feature: http://lv2plug.in/ns/ext/urid#unmap
SamplerChannel: Assigning engine type...OK
Creating new Engine.
Condition:: constructor, bInitialCondition=0
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Voice::SetEngine()
Condition::Set() -> LOCK()
Condition::Set() -> LOCK() passed
gig::Engine created Giga format scriptvm
Condition:: constructor, bInitialCondition=0
ddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddStarting
disk thread...Condition::WaitIf: bCondition=0  TimeoutSeconds=0
TimeoutNanoSeconds=0
Condition::Waitif() -> LOCK()
Condition::Waitif() -> LOCK() passed
Condition::Waitif() -> waiting for 'true' condition
Condition::Set() -> LOCK()
Condition::Set() -> LOCK() passed
Condition::Set() -> broadcasting 'true' condition
Disk thread running
Condition::Waitif() -> awakened from 'true' condition waiting
OK
EQ support: no
This Engine has now 1 EngineChannels.
Condition::WaitIf: bCondition=1  TimeoutSeconds=0  TimeoutNanoSeconds=0
Condition::Waitif() -> LOCK()
Condition::Waitif() -> LOCK() passed
Condition::Waitif() -> waiting for 'false' condition
Condition::Set() -> LOCK()
Condition::Set() -> LOCK() passed
Condition::Set() -> broadcasting 'false' condition
Condition::Waitif() -> awakened from 'false' condition waiting
Condition::WaitIf: bCondition=0  TimeoutSeconds=0  TimeoutNanoSeconds=0
Condition::Waitif() -> LOCK()
Condition::Waitif() -> LOCK() passed
Condition::Waitif() -> waiting for 'true' condition
Condition::Set() -> LOCK()
Condition::Set() -> LOCK() passed
Condition::Set() -> broadcasting 'true' condition
Disk thread running
Condition::Waitif() -> awakened from 'true' condition waiting
linuxsampler: Activate
Segmentation fault

​In other occurrence for the same failure I've got something like
"JackTemporaryException :" instead of "Segmentation fault". Maybe it's
something between Jack and LS some clue? Thanks in advance.​

-- 
*Fernanda Monteiro de Oliveira*

Mobile: (+55 11) 99553 9362
Alt e-mail: nan...@ou...
Social portfolio: http://about.me/nandameik

[Linuxsampler-devel] Mac installer now available

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

For the Mac users out there: We finally have a convenient installer for the
OS X version of LinuxSampler:

	http://download.linuxsampler.org/pix/screenshots/mac_installer_1.jpg
	http://download.linuxsampler.org/pix/screenshots/mac_installer_2.jpg

This is integrated in our automatic build system. So from now on all daily 
snapshot builds for Mac are automatically built with an installer.

If you encounter any issues, let us know!

CU
Christian

Re: [Linuxsampler-devel] Understanding LV2 Plugin Sourcecode

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

Christian Schoenebeck skrev den 2015-01-16 00:45:
> On Friday 16 January 2015 00:13:02 Nils Tonnätt wrote:
>> because of bug #235 I'm trying to understand how the LV2 Plugin works.
>> I'm a wannabe programmer but maybe I have found two things.
> 
> Disclaimer: I did not write the LV2 plugin, Andreas wrote it. And I am not 
> into the details of the LV2 API either. I just had a glimpse at the code ...

I wrote the LV2 plugin initially, but the current Save and Restore code
comes from patches by David Robillard (who happens to be the main
inventor of the LV2 standard, so I guess he knows what he's doing...)

>> 2. LV2_State_Status Save() stores NS_LS "state-file" with flag
>> LV2_STATE_IS_PORTABLE but
>> http://lv2plug.in/doc/html/state_8h.html#afb5cc1033410d51fdcdbfdd09fc7d808
>> says "Portable values MUST NOT contain filenames."
> 
> Well, no idea about the LV2 aspects here. I mean I currently don't know what 
> the actual use case of "portable" data in a LV2 session data is for. Or is 
> there any LV2 plugin/host out there that allows to store a plugin state on one 
> machine and allows to restore it on another machine (with different OS)?

I haven't thought about this much, but I guess you want to be able to
save your Ardour song (which includes plugin state) and give it to a
friend who can load it on his/her computer.

>> 2. Why are the old MapPath and MakePath restored after saving and
>> restoring the state?
> 
> No idea about that one. :) Maybe Andreas can bring some more clues into it.

Sorry, I don't understand that either. That's David's code.

/Andreas

Re: [Linuxsampler-devel] Understanding LV2 Plugin Sourcecode

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

On Friday 16 January 2015 00:13:02 Nils Tonnätt wrote:
> because of bug #235 I'm trying to understand how the LV2 Plugin works.
> I'm a wannabe programmer but maybe I have found two things.

Disclaimer: I did not write the LV2 plugin, Andreas wrote it. And I am not 
into the details of the LV2 API either. I just had a glimpse at the code ...

> 1. The function LV2_State_Status Restore() has the parameter flags in
> PluginLv2.h but rflags in .cpp. I think that's a typo?!

Looks intentional. The "flag"/"rflags" argument is there, because Andreas 
resembled the method prototype with the respective LV2 save/restore function 
callback signatures:

	http://lv2plug.in/doc/html/structLV2__State__Interface.html

So yes, the "flags" argument is not used, but he retained it for clarity with 
the LV2 API. And he renamed the argument "flags" (.h) -> "rflags" in the cpp 
file, because he added a local variable "flags" in the method body which would 
clash with the argument's name. That's no issue. You can name the argument in 
the .cpp file whatever you want. It does not affect the compiled behavior.

> Why is there actually a flags parameter when we want to retrieve it
> afterwards (or rflags when we don't use it).

See above.

> 2. LV2_State_Status Save() stores NS_LS "state-file" with flag
> LV2_STATE_IS_PORTABLE but
> http://lv2plug.in/doc/html/state_8h.html#afb5cc1033410d51fdcdbfdd09fc7d808
> says "Portable values MUST NOT contain filenames."

Well, no idea about the LV2 aspects here. I mean I currently don't know what 
the actual use case of "portable" data in a LV2 session data is for. Or is 
there any LV2 plugin/host out there that allows to store a plugin state on one 
machine and allows to restore it on another machine (with different OS)?

> And two questions:
> 1. Why don't we store the absolute path?
> http://lv2plug.in/ns/ext/atom/#Path --> "effectively any Path sent to or
> received from a plugin instance MUST be absolute."

Because it seems MapPath is used to transform the "abstract" relative paths 
back to absolute paths. Looks valid to me.

> 2. Why are the old MapPath and MakePath restored after saving and
> restoring the state?

No idea about that one. :) Maybe Andreas can bring some more clues into it.

CU
Christian