Re: [Faudiostream-users] FOF in faust

Hi Stéphane, Thanks for looking in to it. Does the -sch compile use huge amounts of RAM for you too? I only have 4Gb, so probably swapping is my main problem.. Which Faust version are you using? If version 2, did you check whether it produces sound when you input sound? Sorry for bombarding you

[Faudiostream-users] Fwd: Incorrect argument order with recursive composition and named parameters

-- Forwarded message -- From: jimbo1qaz Date: Sat, May 21, 2016 at 4:54 PM Subject: Re: [Faudiostream-users] Incorrect argument order with recursive composition and named parameters To: Bart Brouns I solved Bug 1 by referencing "_"

Re: [Faudiostream-users] Calling functions using arguments taken from lists?

EDIT: Use par(), not seq(). The problem in my case was that par(i...) has zero-indexed "i", but take(i...) has one-indexed i. Additionally, the error message was very confusing and didn't which line of code, and which variable access was bad. Instead, it spit out a long and confusing template

Re: [Faudiostream-users] Possible bug - "vslider(step=1) : int" vs. "rint"

FaustLive on Linux. x = vslider("Integer?", 5, 1, 64, 1):int; // Replace 64 with 65 for "partially" incorrect values. // Replace :int with :rint to workaround. y = vbargraph("Not!", 0, 65); process = attach(_, y(x)); On Sun, May 22, 2016 at 12:40 AM, Albert Graef wrote: >

Re: [Faudiostream-users] Possible bug - "vslider(step=1) : int" vs. "rint"

On Sun, May 22, 2016 at 1:44 AM, jimbo1qaz wrote: > I spent hours trying to find why my plugin didn't sound right. Eventually, > I discovered that even integer sliders have roundoff errors. I didn't > realize earlier because the GUI displays them as integers, which advanced