[Csnd] Lua opcodes
Date | 2011-09-09 14:54 |
From | Francois PINOT |
Subject | [Csnd] Lua opcodes |
Hello MiKe, I just built Csound with your LuaOpcodes from git. My system is Ubuntu 11.04 32 bits. I built csound with new parser and doubles. Lua was not installed on my system, except liblua5.1 needed by some packages. Here's the report of my build. 1) get LuaJIT sources from http://luajit.org and decompress the archive, build it and install: a) tar zxf LuaJIT-2.0.0-beta8.tar.gz b) cd LuaJIT-2.0.0-beta8 c) make d) sudo make install e) cd /usr/local/bin f) sudo ln -sg luajit-2.0.0-beta8 luajit 2) get csound sources from git a) add this line in my custom.py file: customCPPPATH.append('/usr/local/include/luajit-2.0') b) modify SConstruct so that the linker links against libluajit instead of liblua (I don't want to have a symbolic link from liblua to libluajit to avoid breaking my package system integrity. So I changed line 2054 in SConstruct from luaEnvironment.Append(LIBS = ['lua51']) to luaEnvironment.Append(LIBS = ['luajit-5.1']). c) build csound with buildLuaOpcodes=1 (notice that I didn't build luaWrapper, buildLuaWrapper was not set) d) sudo python install.py 3) Change in your examples luaopcode.csd and luamoog.csd the reference to the csound API from csound64.dll.5.2 to csound64.so 4) Run your examples in realtime. Magic, everything works at the first try! Thank you for sharing this very, very nice work. Hope we'll see you in Hannover. Francois |
Date | 2011-09-09 16:19 |
From | Michael Gogins |
Subject | Re: [Csnd] Lua opcodes |
Well, I'm looking forward to seeing you there as well! Everything is progressing well after the eye surgery and barring unlikely misfortunes, I will be there. And thanks for testing the Lua opcodes. I think this approach to audio DSP coding opens up many possibilities. Regards, Mike On Fri, Sep 9, 2011 at 9:54 AM, Francois PINOT |
Date | 2011-09-12 13:54 |
From | Rene Jopi |
Subject | Re: [Csnd] Lua opcodes |
Hi, Thanks for these powerful new programming facility. Have tested on Ubuntu 10.04 with success, thanks for your report. (I use -sf instead of -sg for ln flags, may be a typo)
Have read that Lua opcode are much faster than UDO. Is luamoog.csd should show that point too? My csound output is: Opcode: moogladder
Result: 0 orch now loaded audio buffered in 1024 sample-frame blocks writing 4096-byte blks of floats to dac SECTION 1: instr 5: ielapsed = 0.041
Lua moogladder. instr 5: ielapsed = 20.952 Lua moogladder. instr 5: ielapsed = 20.993 Native moogladder. instr 5: ielapsed = 21.011 Native moogladder.
instr 5: ielapsed = 20.995 UDO moogladder. instr 5: ielapsed = 21.543 UDO moogladder. instr 5: ielapsed = 21.099 No filter. instr 5: ielapsed = 20.990
No filter. instr 5: ielapsed = 21.013 Lua moogladder. Lua moogladder. Lua moogladder. Score finished in csoundPerform(). .... I can't see the correlation between the printed times values and the moog instruments.
Regards, René 2011/9/9 Francois PINOT <fggpinot@gmail.com> Hello MiKe, |
Date | 2011-09-12 15:28 |
From | Michael Gogins |
Subject | Re: [Csnd] Lua opcodes |
Are you rendering to a soundfile? If you are rendering to audio out, all the times should be the same. Regards, Mike On Mon, Sep 12, 2011 at 8:54 AM, Rene Jopi |
Date | 2011-09-12 16:26 |
From | Rene Jopi |
Subject | Re: [Csnd] Lua opcodes |
Oups, was in real time !!! I got it, thanks, 3 time faster than UDO !! René
2011/9/12 Michael Gogins <michael.gogins@gmail.com> Are you rendering to a soundfile? If you are rendering to audio out, |