[chuck-users] [chuck] miniAudicle-0.1.3.3 release (mac + linux + win)

[Spencer Salazar]

Atte,
One other thing to try: does writing audio to a sndbuf work?  That  
could help determine whether this is a chuck-wide problem or just an  
rtaudio/alsa problem.

The default buffer size on Linux is 512, if you think this could be a  
problem and you are willing to do some minor hacking you could add
#undef BUFFER_SIZE_DEFAULT
#define BUFFER_SIZE_DEFAULT 128
to the top of miniAudicle.cpp and recompile.  Im not sure how much  
this could help, but it might be worth a shot.

The next release (coming early next week) will allow adjustable  
verbosity of the console log, and also the ability to specify virtual  
machine options through the command line or ~/.miniAudicle, in  
addition to fixes for many of the compile/run-time bugs discussed in  
this thread.  Hopefully if we can get more information out of the  
virtual machine this way, it will be easier to debug.  also it will  
be easier to do fine tuning without a recompile.  So you could also  
wait until that release.

spencer

On Jul 29, 2006, at 3:20 AM, Atte André Jensen wrote:

> Spencer Salazar wrote:
>
>> mik, Atte,
>> If you havent already, try removing the symlink to the chuck
>> directory within the miniAudicle distribution, and replacing it with
>> a symlink to the chuck directory that came from the chuck website.
>
> I tried that, still no sound...
>
>> The problem could also be that the default virtual machine parameters
>> supplied by miniAudicle dont mesh well with your system.  What
>> command line arguments, if any, do you typically pass to chuck?
>
> --bufsize128
>
>>> 1) CTRL-x doesn't do anything here. Maybe this key binding is  
>>> standard
>>> on mac, but on Linux CTRL-o is the most common key binding for
>>> "open file".
>>
>> Thats a bug that has been fixed for the next release--Ctrl-X should
>> definitely be bound to Cut, and Ctrl-O to open file.
>
> Great.
>
>>> 2) It seems it's not possible to call miniAudicle with any command
>>> line
>>> options. I guess it should possible to use the same options as with
>>> regular chuck, or...?
>>
>> Nope, not at the moment.  Within the next release or two will be a
>> GUI preferences mechanism by which you can specify common options
>> such as dac/adc, sample rate, channels, buffer size, etc.,
>
> Oh, yeah, realtime wouldn't be possible without that...
>
>> but a
>> complementary command line interface is also a good idea.
>
> I normally load a whole bunch of .ck files in the initial call to  
> chuck,
> I'd like to be able to do the same with miniAudicle. Since I haven't
> really played with it yet, maybe you shouldn't consider this a feature
> request just yet, but a mechanism for sporking and removing several
> files at once would also be very good.
>
> -- 
> peace, love & harmony
> Atte
>
> http://www.atte.dk      | quartet:      http://www.anagrammer.dk
> http://www.atte.dk/gps  | compositions: http://www.atte.dk/ 
> compositions
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users