hello. I downloaded "chuck-1.2.1.1". But --version is as follows. Chuck version: 1.2.0.8 (Dracula) Exe target: Microsoft win32 http: //chuck.cs.princeton.edu/ example/analysis does not operate :( and... chuck --bufsize950 [chuck]: no input files... (try --help) -- miya6611 http://mindblast.jp/
On 20/01/2008, miya6611
hello.
Hi, Miya! I downloaded "chuck-1.2.1.1".
But --version is as follows.
Chuck version: 1.2.0.8 (Dracula) Exe target: Microsoft win32 http: //chuck.cs.princeton.edu/
example/analysis does not operate :(
Ok, that is odd. are you sure you copied the right chuck.exe to your windows/system32 directory? That would be my first guess, this sounds like you are accidentally calling a older version. Perhaps you are working from a directory that also holds the older executable? In that case CMD will first use that one, before trying your path. and...
chuck --bufsize950 [chuck]: no input files... (try --help)
That's right. What happens here is that you start chuck with a certain buffer size, chuck starts, discovers it has nothing to do and quits. Try; chuck --bufsize950 --loop or chuck --bufsize950 my_file.ck or even chuck --bufsize950 --loop my_file.ck Also remember that if bufsize isn't a power of 2 (which 950 isn't, I fear) chuck will round it to the next power of two, being 1024 in this case. Hope that gets you up & ChucKing! Kas.
Hi Kas. ;)
hello. Hi, Miya! I downloaded "chuck-1.2.1.1". But --version is as follows. Chuck version: 1.2.0.8 (Dracula) Exe target: Microsoft win32 http: //chuck.cs.princeton.edu/ example/analysis does not operate :( Ok, that is odd. are you sure you copied the right chuck.exe to your windows/system32 directory? That would be my first guess, this sounds
On 20/01/2008, miya6611
wrote: like you are accidentally calling a older version. Perhaps you are working from a directory that also holds the older executable? In that case CMD will first use that one, before trying your path.
Oh! you are right! Old version existed in path. chuck version: 1.2.1.1b (dracula) exe target: microsoft win32 http://chuck.cs.princeton.edu/ good! :)
and...
chuck --bufsize950 [chuck]: no input files... (try --help) That's right. What happens here is that you start chuck with a certain buffer size, chuck starts, discovers it has nothing to do and quits. Try; chuck --bufsize950 --loop or chuck --bufsize950 my_file.ck or even chuck --bufsize950 --loop my_file.ck Also remember that if bufsize isn't a power of 2 (which 950 isn't, I fear) chuck will round it to the next power of two, being 1024 in this case. Hope that gets you up & ChucKing! Kas.
ok! I was saved very by your help. Appreciation! -- rozie roz@mindblast.jp http://mindblast.jp/
Oh! you are right! Old version existed in path.
chuck version: 1.2.1.1b (dracula) exe target: microsoft win32 http://chuck.cs.princeton.edu/
good! :)
Yeah, that happens. What I do is that I have a "chuck" directory on my C disc and in it are the different directories of all versions, each with it's own exe. I always copy the latest one when it comes out to /system32 but I keep the old ones in case the new one has a bug that affects me. That way I can keep ChucKing while the developers (hopefully) fix the issue. That way you can swap versions too if you need to, for example the last ASIO enabled version is a bit out of date but that's still what I use for my live setup.
ok! I was saved very by your help. Appreciation!
Great! Kas.
participants (2)
-
Kassen
-
miya6611