Csound Csound-dev Csound-tekno Search About

[Csnd] soundouts opcode problem on osx

Date2008-02-14 12:42
Frompeiman
Subject[Csnd] soundouts opcode problem on osx
Hello,

I am trying to record a soundfile to disk using the soundouts opcode (on os
x) but I am unable to read the resulting soundfile. Not even after saving it
with a header in soundhack. It seems that it is not an audio file at all.
Below is a little test csd to demonstrate the problem. 

Am I maybe doing something wrong? 

Thanks in advance...

Best
Peiman




-odac           -iadc     -d 




sr=44100
ksmps=1
nchnls=2


	instr 3	;player

asig1	oscil	10000, 440, 1

outs  asig1, asig1
soundouts asig1, asig1, "test.aiff", 4 
	endin






f 1 0 2048	10 1 

i3	0 10

e




-- 
View this message in context: http://www.nabble.com/soundouts-opcode-problem-on-osx-tp15479636p15479636.html
Sent from the Csound - General mailing list archive at Nabble.com.


Date2008-02-14 12:49
FromRory Walsh
Subject[Csnd] Re: soundouts opcode problem on osx
Hi Peiman, I've never used soundouts but I regularly write audio to disk 
using fout which has always works fine for me.

Rory.


peiman wrote:
> Hello,
> 
> I am trying to record a soundfile to disk using the soundouts opcode (on os
> x) but I am unable to read the resulting soundfile. Not even after saving it
> with a header in soundhack. It seems that it is not an audio file at all.
> Below is a little test csd to demonstrate the problem. 
> 
> Am I maybe doing something wrong? 
> 
> Thanks in advance...
> 
> Best
> Peiman
> 
> 
> 
> 
> -odac           -iadc     -d 
> 
> 
> 
> 
> sr=44100
> ksmps=1
> nchnls=2
> 
> 
> 	instr 3	;player
> 
> asig1	oscil	10000, 440, 1
> 
> outs  asig1, asig1
> soundouts asig1, asig1, "test.aiff", 4 
> 	endin
> 
> 
> 
> 
> 
> 
> f 1 0 2048	10 1 
> 
> i3	0 10
> 
> e
> 
> 
> 
> 

Date2008-02-14 13:04
FromPeiman Khosravi
Subject[Csnd] Re: Re: soundouts opcode problem on osx
Hi Rory,

I'll use fout then :-) I've not used csound for realtime performance  
much before so I'm not really familiar with these opcodes.

Many Thanks

Best
Peiman

On 14 Feb 2008, at 12:49, Rory Walsh wrote:

> Hi Peiman, I've never used soundouts but I regularly write audio to  
> disk using fout which has always works fine for me.
>
> Rory.
>
>
> peiman wrote:
>> Hello,
>> I am trying to record a soundfile to disk using the soundouts  
>> opcode (on os
>> x) but I am unable to read the resulting soundfile. Not even after  
>> saving it
>> with a header in soundhack. It seems that it is not an audio file  
>> at all.
>> Below is a little test csd to demonstrate the problem. Am I maybe  
>> doing something wrong? Thanks in advance...
>> Best
>> Peiman
>> 
>> 
>> -odac           -iadc     -d 
>> 
>> sr=44100
>> ksmps=1
>> nchnls=2
>> 	instr 3	;player
>> asig1	oscil	10000, 440, 1
>> outs  asig1, asig1
>> soundouts asig1, asig1, "test.aiff", 4 	endin
>> 
>> 
>> f 1 0 2048	10 1 i3	0 10
>> e
>> 
>> 
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"


Date2008-02-14 17:10
FromMarcel de Velde
Subject[Csnd] Check to see if I installed CSound correctly (noob)
Hello,

I'm completely new to CSound.
I intend to dive in deep and use it as my only synthesizer. Before this
I only used hardware.

I just Installed CSound 5.08 from source on Ubuntu Linux, and have no
idea wether I did it correctly.

I used scons -h to see the default and available options and then ran
scons again with the options that were off by default but did seem
desirable to me.
scons useDouble=1 buildCsound5GUI=1 useOSC=1 buildPythonOpcodes=1
buildStkOpcodes=1 install=1 useCoreAudio=0 buildTclcsound=1
buildVirtual=1 buildInterfaces=1 buildJavaWrapper=1 buildCSEditor=1

But then when compiling scons gave a lot of compile decisions saying it
would not build amongst other things the STK and Loris opcodes.

CONFIGURATION DECISION: Using double-precision floating point for audio
samples.
CONFIGURATION DECISION: Not building with new parser
CONFIGURATION DECISION: Building static Csound library
Parsed fltk-config.
CONFIGURATION DECISION: Not building Csound interfaces library.
CONFIGURATION DECISION: Not generating PDF documentation.
Checking for C library png... (cached) yes
CONFIGURATION DECISION: Building image opcodes
CONFIGURATION DECISION: Building Virtual Keyboard plugin.
CONFIGURATION DECISION: Not building CoreAudio plugin.
CONFIGURATION DECISION: Building ALSA plugin.
CONFIGURATION DECISION: Building PortAudio module.
Adding Jack library for PortAudio
CONFIGURATION DECISION: Building JACK plugin.
CONFIGURATION DECISION: Not building with PortMIDI.
CONFIGURATION DECISION: Not building OSC plugin.
CONFIGURATION DECISION: Building UDP plugins.
Checking for C header file fluidsynth.h... (cached) yes
CONFIGURATION DECISION: Building fluid opcodes.
CONFIGURATION DECISION: Not building vst4cs opcodes.
Checking for C header file Opcodes/Loris/src/loris.h... (cached) no
CONFIGURATION DECISION: Not building Loris Python extension and Csound
opcodes.
CONFIGURATION DECISION: Not building STK opcodes.
CONFIGURATION DECISION: Building Python opcodes.
CONFIGURATION DECISION: Building FLTK GUI CSOUND5GUI frontend.
CONFIGURATION DECISION: Not building CsoundAC extension module for
Csound with algorithmic composition.
CONFIGURATION DECISION: Not building CsoundVST plugin and standalone.
CONFIGURATION DECISION: Not building Tclcsound
CONFIGURATION DECISION: Not building Winsound
CONFIGURATION DECISION: Not building OSX GUI frontend
Checking for C header file ladspa.h... (cached) yes
CONFIGURATION DECISION: Building DSSI plugin host opcodes.
CONFIGURATION DEFAULT:  Building csLadspa.
CONFIGURATION DECISION: Not calling TAGS
CONFIGURATION DECISION: Not compiling zip file for release.

This gives me the feeling I'm not getting all I should.
A week ago I did a quick try of Chuck and ran into the STK instruments
there, and I kinda liked some and would like to use them in CSound as
well.
Do I need to recompile? And if so how do I get them to work?
Any advice on other opcodes / things I'd like to get working too?
Or should I just try the binary? (though I read in the manual building
from source is best for Linux)

Many thanks for any advice!

Marcel


here some more output from scons in case it's helpfull: (sorry for the
long mail)

System platform is 'linux'.
Using options from 'custom.py.'
Build platform is 'linux'.
SCons tools on this platform:  ['default', 'gnulink', 'gcc', 'g++',
'f95', 'gas', 'ar', 'dvipdf', 'dvips', 'gs', 'latex', 'lex', 'm4',
'pdflatex', 'pdftex', 'rpcgen', 'tar', 'tex', 'yacc', 'zip']
Using Istvan localisation
Checking for C header file stdio.h... (cached) yes
Checking for C library sndfile... (cached) yes
Checking for C library portaudio... (cached) yes
Checking for C library portmidi... (cached) no
Checking for C++ library fltk... (cached) yes
Checking for C++ header file FL/Fl_Spinner.H... (cached) yes
Checking for C++ header file boost/any.hpp... (cached) no
Checking for C library asound... (cached) yes
Checking for C library jack... (cached) yes
Checking for C library lo... (cached) no
Checking for C++ header file Opcodes/stk/include/Stk.h... (cached) no
Checking for C header file m_pd.h... (cached) no
Checking for C header file tcl.h... (cached) no
Checking for C header file zlib.h... (cached) yes
Checking for C++ header file funknown.h... (cached) no
Checking for C header file /usr/include/tcl8.4/tcl.h... (cached) no
Checking for C header file /usr/include/tk8.4/tcl.h... (cached) no
Checking for C header file lua5.1/lua.h... (cached) no
Checking for SWIG... no
Checking for C header file Python.h... (cached) no
Checking for C header file /usr/include/python2.5/Python.h... (cached)
yes
Checking for C++ header file jni.h... (cached) no
Checking for C++ header file /usr/lib/java/include/linux/jni_md.h...
(cached) no
Checking for C++ header file /usr/lib/jvm/java/include/linux/jni_md.h...
(cached) no
Checking for C++ header
file /usr/lib/jvm/java-1.5.0/include/linux/jni_md.h... (cached) no
Checking for C header file io.h... (cached) no
Checking for C header file fcntl.h... (cached) yes
Checking for C header file unistd.h... (cached) yes
Checking for C header file stdint.h... (cached) yes
Checking for C header file sys/time.h... (cached) yes
Checking for C header file sys/types.h... (cached) yes
Checking for C header file termios.h... (cached) yes
Checking for C header file sys/socket.h... (cached) yes
Checking for C header file dirent.h... (cached) yes
Checking for libsndfile version 1.0.16 or later... (cached) yes



Date2008-02-14 19:51
FromAndres Cabrera
Subject[Csnd] Re: Check to see if I installed CSound correctly (noob)
Hi,

Welcome. Csound will work fine even with a minimal build, but you'll
have less opcodes available. If you want to build more stuff, just
adding the dev packages for each needed package and rebuilding does the
trick.

Also, don't forget to set the OPCODEDIR variable, otherwise csound will
not find your opcode libraries:

http://www.csounds.com/manual/html/BuildingCsound.html

Cheers,
Andrés


El jue, 14-02-2008 a las 18:10 +0100, Marcel de Velde escribió:
> 
> Do I need to re