Re: [LAD] LV2 Achievement of GMPI Requirements

On Fri, 2012-08-03 at 14:18 +1200, Jeff McClintock wrote: > > > For historical interest. I did complete the GMPI prototype. > > > I don't suppose the code for those modular synthesis plugins is > > available? :) > > I release as many as possible open source. Unfortunately before I used > plugins

Re: [LAD] LV2 Achievement of GMPI Requirements

> > For historical interest. I did complete the GMPI prototype. > I don't suppose the code for those modular synthesis plugins is > available? :) I release as many as possible open source. Unfortunately before I used plugins I coded everything as part of my application, so a most of the good filt

Re: [LAD] Floating point Denormals: C++ and Waf

[Harry van Haaren] >Thanks all for the replies, I've certainly learnt a lot. > >On Thu, Aug 2, 2012 at 9:11 PM, Tim Goetze wrote: >> >> I think it's almost always a better idea to add an inaudible DC offset >> or a square wave at the block interval or at Nyquist > > >How small is inaudible? Or be

Re: [LAD] Floating point Denormals: C++ and Waf

On Thu, Aug 02, 2012 at 09:56:51PM +0100, Harry van Haaren wrote: > How small is inaudible? Or better yet, how small is way beyond inaudible, > but enough to eliminate any denormals? > > The other problem is locating exactly where the problem exists: I'm using > Faust to

Re: [LAD] Floating point Denormals: C++ and Waf

On 08/02/2012 10:56 PM, Harry van Haaren wrote: > Thanks all for the replies, I've certainly learnt a lot. > > On Thu, Aug 2, 2012 at 9:11 PM, Tim Goetze wrote: >> >> I think it's almost always a better idea to add an inaudible DC offset >> or a square wave at the block interval or at Nyquist >

Re: [LAD] Floating point Denormals: C++ and Waf

Thanks all for the replies, I've certainly learnt a lot. On Thu, Aug 2, 2012 at 9:11 PM, Tim Goetze wrote: > > I think it's almost always a better idea to add an inaudible DC offset > or a square wave at the block interval or at Nyquist How small is inaudible? Or better yet, how small is way be

Re: [LAD] Floating point Denormals: C++ and Waf

[David Robillard] >On Thu, 2012-08-02 at 20:31 +0200, Martin Homuth-Rosemann wrote: >[...] >> // denormals are zero >> static inline float daz( float f ) >> { >>// define an aliasing type to perform a "reinterpret cast" >>typedef __u32 __attribute__ (( __may_alias__ )) u32bit; >>if ( *

Re: [LAD] Floating point Denormals: C++ and Waf

On Thu, 2012-08-02 at 20:31 +0200, Martin Homuth-Rosemann wrote: [...] > // denormals are zero > static inline float daz( float f ) > { >// define an aliasing type to perform a "reinterpret cast" >typedef __u32 __attribute__ (( __may_alias__ )) u32bit; >if ( *( (u32bit*)&f ) & 0x7F0

Re: [LAD] Floating point Denormals: C++ and Waf

Am 02.08.2012 17:13, schrieb Charles Henry: Hi Martin, Can I pick your brain on how this works? My biggest question is why to use the typedef__u32__attribute__ line inside an inline function. Don't you only have to do this once? If so, wouldn't you place that line outside the function? You'r

Re: [LAD] Floating point Denormals: C++ and Waf

On Thu, Aug 2, 2012 at 9:40 AM, Paul Davis wrote: > > > On Thu, Aug 2, 2012 at 12:02 PM, David Robillard wrote: > >> On Thu, 2012-08-02 at 11:28 -0400, Paul Davis wrote: >> > >> > >> > On Thu, Aug 2, 2012 at 10:46 AM, David Robillard >> > wrote: >> > >> > Is there a reason Jack can't do

Re: [LAD] Floating point Denormals: C++ and Waf

On Thu, Aug 2, 2012 at 12:02 PM, David Robillard wrote: > On Thu, 2012-08-02 at 11:28 -0400, Paul Davis wrote: > > > > > > On Thu, Aug 2, 2012 at 10:46 AM, David Robillard > > wrote: > > > > Is there a reason Jack can't do this for everything? I am not > > really > > kee

Re: [LAD] Floating point Denormals: C++ and Waf

On Thu, 2012-08-02 at 11:28 -0400, Paul Davis wrote: > > > On Thu, Aug 2, 2012 at 10:46 AM, David Robillard > wrote: > > Is there a reason Jack can't do this for everything? I am not > really > keen on putting a bunch of mysterious assembler crap in a host >

Re: [LAD] LV2 Achievement of GMPI Requirements

On Thu, 2012-08-02 at 10:59 +1200, Jeff McClintock wrote: > > I have adapted the GMPI requirements final draft document to a > > comparison with the current state of LV2: http://lv2plug.in/gmpi.html > > For historical interest. I did complete the GMPI prototype. > Now running on Windows (GUI + DS

Re: [LAD] Floating point Denormals: C++ and Waf

On Thu, Aug 2, 2012 at 10:46 AM, David Robillard wrote: > > Is there a reason Jack can't do this for everything? I am not really > keen on putting a bunch of mysterious assembler crap in a host meant to > be a relatively clean example, and it's even worse to make plugins have > to do this... >

Re: [LAD] Floating point Denormals: C++ and Waf

On Thu, Aug 2, 2012 at 10:13 AM, Charles Henry wrote: > On Thu, Aug 2, 2012 at 7:39 AM, Martin Homuth-Rosemann > wrote: >> { >> // define an aliasing type to perform a "reinterpret cast" >> typedef __u32 __attribute__ (( __may_alias__ )) u32bit; >> if ( *( (u32bit*)&f ) & 0x7F00 ) // E

Re: [LAD] Floating point Denormals: C++ and Waf

Hi Martin, Can I pick your brain on how this works? My biggest question is why to use the typedef__u32__attribute__ line inside an inline function. Don't you only have to do this once? If so, wouldn't you place that line outside the function? On Thu, Aug 2, 2012 at 7:39 AM, Martin Homuth-Rosem

Re: [LAD] Floating point Denormals: C++ and Waf

On Thu, 2012-08-02 at 13:06 +0100, Harry van Haaren wrote: > Hi all, > > > I've working on a LV2 instrument plugin, and it consumes about 1-2% > CPU on idle. When I leave it for about 20 seconds, the CPU usage jumps > to 38 / 40 % of a core, and JACK xruns. The code contains IIR's for a > reverb

Re: [LAD] [ann] out now petri-foo 0.1.85 / NSM

On 08/02/2012 03:17 PM, Paul Davis wrote: On Thu, Aug 2, 2012 at 5:43 AM, rosea.grammostola mailto:rosea.grammost...@gmail.com>> wrote: 3) it works also with other audio servers like KLANG :) i imagine that this is supposed to be facetious, but if you had understood anything about KLANG

Re: [LAD] [ann] out now petri-foo 0.1.85 / NSM

On Thu, Aug 2, 2012 at 5:43 AM, rosea.grammostola < rosea.grammost...@gmail.com> wrote: > > 3) it works also with other audio servers like KLANG :) i imagine that this is supposed to be facetious, but if you had understood anything about KLANG it should have been that it is NOT intended to be, o

Re: [LAD] Floating point Denormals: C++ and Waf

Hi, that's my solution regardless of CPU type: // // DENORMALS ARE EVIL // // 32 bit float // SMMM // E = 0, M != 0 -> denormal // processing denormals uses lot of cpu. // problem: an IIR feeds back 0.7*y. // a value > 0 will decay until the smallest float is reached:

Re: [LAD] Floating point Denormals: C++ and Waf

> More info is at http://carlh.net/plugins/denormals.php Interesting numbers ... I just don't understand the 32-bit pentium 3 numbers. Where is the reference from which the factors displayed in this table for this CPU are derived ? J.

Re: [LAD] Floating point Denormals: C++ and Waf

On 08/02/2012 02:06 PM, Harry van Haaren wrote: > Hi all, > > I've working on a LV2 instrument plugin, and it consumes about 1-2% CPU on > idle. When I leave it for about 20 seconds, the CPU usage jumps to 38 / 40 > % of a core, and JACK xruns. The code contains IIR's for a reverb effect, > so I'm

[LAD] Floating point Denormals: C++ and Waf

Hi all, I've working on a LV2 instrument plugin, and it consumes about 1-2% CPU on idle. When I leave it for about 20 seconds, the CPU usage jumps to 38 / 40 % of a core, and JACK xruns. The code contains IIR's for a reverb effect, so I'm going to blame this CPU burning on denormal values. I'm us

[LAD] [ann] petri-foo 0.1.86 fix

Hello again, Seems like only five minutes ago we last sp0ke!? Have to say I am sorry for the pretty majorly catastrophic show stopping bug in Petri-Foo's Non Session Manager support. You know the one, the one which made it not work when you first tried it out and thought "huh well that's a bit c

Re: [LAD] [ann] out now petri-foo 0.1.85 / NSM

On 08/01/2012 01:52 PM, Louigi Verona wrote: Is JACKSession really dead? And fellas, to a non-coder, can you explain why isn't session handling done through JACK, which seems like a logical thing to do? I'm not a coder. Advantages are imo: 1) you can leave JACK apps outside a session on purp