Author |
Message |
tony
Joined: Oct 07, 2006 Posts: 21 Location: indonesia
Audio files: 2
|
Posted: Sat Oct 14, 2006 12:33 am Post subject:
Audicle-1.0.0.4 Subject description: what different |
|
|
thanks you all. for your advice now I can run mini audicles and make sound with its. and I try to download Audicle-1.0.0.4 but when I try to make command in Audicle-1.0.0.4
thet can work this for exsamples:
in mini-audicle
SawOsc s => dac;
this langguage have no error in mini-audicle
in audicle
chuck %> SawOsc s => dac;
[chuck] not recognized command
so I must ask you what diffrent beetwen audicle and mini audicle and how way to run Audicle
thanks |
|
Back to top
|
|
|
Kassen
Janitor
Joined: Jul 06, 2004 Posts: 7678 Location: The Hague, NL
G2 patch files: 3
|
Posted: Sat Oct 14, 2006 6:15 am Post subject:
|
|
|
Hi again.
The thing is with chuck; you have to save your commands in a file. So; you would write a file that would go like;
SinOsc s => dac;
1::second => now;
and you would save this as beep.ck in (for example) a directory called "my_files" in your chuck folder.
Then you call chuck like this;
c:/chuck/my_files/> chuck beep.ck
And you get a beep.
What you can also do instead is call chuck like this;
c:/chuck/examples/>chuck --loop
the "--loop" makes sure chuck keeps running even when it's not doing anything.
You can then give it something to do from a second command window by using "+" like this;
c:/chuck/examples/>chuck + otf_01.ck
later you might add another file like this;
c:/chuck/examples/>chuck + otf_02.ck
See what's running;
chuck --status
And perhaps take the first one oput again;
chuck - 1
All of this is also in the manual under "on the fly commands", I recomend you look for the pdf manual that came with your chuck install because all of the basics are in there.
Hope that helps. _________________ Kassen |
|
Back to top
|
|
|
kijjaz
Joined: Sep 20, 2004 Posts: 765 Location: bangkok, thailand
Audio files: 4
|
Posted: Mon Oct 16, 2006 10:33 am Post subject:
|
|
|
in Audicle.. you can use chuck shell command in there..
so if you wanna write lines of code on Audicle..
you can start all that with {
and end with }
for example
in a shell in Audicle
{ Noise s => dac; second => now; }
and then enter..
that'd add the program to a new shred immediately.
that'd work well in Audicle.
if you don't wanna write all codes there in Audicle..
you can prepare them in .ck file just like Kassen tell you..
and + to add shred with the file(s) later. |
|
Back to top
|
|
|
Kassen
Janitor
Joined: Jul 06, 2004 Posts: 7678 Location: The Hague, NL
G2 patch files: 3
|
Posted: Mon Oct 16, 2006 1:59 pm Post subject:
|
|
|
kijjaz wrote: | in Audicle.. you can use chuck shell command in there..
so if you wanna write lines of code on Audicle..
you can start all that with {
and end with }
for example
in a shell in Audicle
{ Noise s => dac; second => now; }
and then enter..
that'd add the program to a new shred immediately.
that'd work well in Audicle.
|
True, but I wouldn't recomend using the ChucK shell for entering code right now. To be clear; I think it's a great idea and it has great potential because you can modify bits without replacing the whole file (and all it's internal data!) but it's in a rather early stage and crorecting mistakes is a b**** and the "scope" thing is tricky. _________________ Kassen |
|
Back to top
|
|
|
kijjaz
Joined: Sep 20, 2004 Posts: 765 Location: bangkok, thailand
Audio files: 4
|
Posted: Tue Oct 17, 2006 1:50 am Post subject:
|
|
|
so normally i use the shell in Audicle to
add shred
+ filename (the .ck file name)
and status, - (to remove), = (to replace) just like Kassen said.
i still haven't explored any more Audicle shell commands hehh ^^" |
|
Back to top
|
|
|
|