Hi Rusty, What the error means is that Nama doesn't recognize the code for Ecasound's volume operator. The first, easiest thing you could try is starting nama with the -r flag. This will regenerate Nama's list of effects and all the associated indexes. It might solve the problem you reported with changing volume levels. If that doesn't help, it might be helpful to see the result of starting nama with some logging. NAMA_LOGFILE=debuglog nama -r -L EffectsRegistry Then send me the debuglog file that this creates in the directory you start nama from. Cheers, Joel Rusty Perez wrote: > Hi Julien, > Well, this has been going on for a while now, usually I get these > aronious settings, but occasionally, and I'm not sure when or why, I > get the right ones. > I am also getting an error, or actually about 5 errors when ever I > start or stop the engine > ea: effect code not found. skipping. > Use of uninitialized value in array element # then a file path > > I feel like I'm always causing trouble! :-) > > Thanks > Rusty > > On 10/10/13, Julien Claassen <julien@xxxxxxxxxxx> wrote: > > Hello Rusty! > > The vol and pan defaults are set in the Nama source code, so you > > shouldn't > > normally touch them, unless you take great pains to do so. I can't think of > > an > > accident, that would make a volume setting of 120 a default. If you had > > created a template, then such settings should only apply to the tracks > > created > > by that template, but not new ones, you add afterwards. If this persists, > > then > > this would need to be debugged. > > Kindly yours > > Julien > > > > ---------------------------------------- > > http://juliencoder.de/nama/music.html > > > -- Joel Roth