i got this bad boy to compile on windows however i had to comment a identifier called "rint" , it lead to an unresolved external . does any one know where i could find this external, or was it part of one of the old pd release but is not longer included ? i am jsut worried that the variable that is defined with this "rint" identifier might not be doing it job properly . here is he line of code and the modification i made to it :
/* Then, the exact "continuous" IOI is discretized (quantized) */
/* ioi_index = (unsigned)rint (ioi / ge->ioi_resolution); */
ioi_index = (unsigned) (ioi / ge->ioi_resolution);
it can be found in the file rhythm_ioi_histogram.c
also there is another occurence of "rint" in rhythm_quantum.c . it reads :
/* first_index = (unsigned)rint (ge->min_quantum/ge->ioi_resolution); */
first_index = (unsigned) (ge->min_quantum/ge->ioi_resolution);
thanks again !
joge .
"joge ." wrote:
i got this bad boy to compile on windows however i had to comment a identifier called "rint" , it lead to an unresolved external . does any one know where i could find this external, or was it part of one of the old pd release but is not longer included ? i am jsut worried that the variable that is defined with this "rint" identifier might not be doing it job properly . here is he line of code and the modification i made to it :
from "man rint":
<snip> SYNOPSIS #include <math.h>
double nearbyint(double x);
double rint(double x);
DESCRIPTION The nearbyint functions round their argument to an integer value in floating point format, using the current rounding direction and without raising the inexact exception.
The rint functions do the same, but will raise the inexact
exception when the result differs in value from the arguÂ
ment.
</snip>
then "man round" says something like:
<snip> DESCRIPTION These functions round x to the nearest integer, but round halfway cases away from zero (regardless of the current rounding direction), instead of to the nearest even inte ger like rint(). </snip>
mfg.cdas.dr IOhannes
ah yes, and it is obviously unix-only. so you have to replace it by something (or write your own rint)
mfg.cd.sadf IOhannes
Hello everyone,
I'm having trouble with the ZEXY "msgfile" object--I can't get it to write it's contents to a text file using Win98SE. Has anyone else experienced this?
Thanks, Greg -- Greg Rippin, Graduate Assistant Music Technology Program New York University 35 West 4th Street, Suite 777 New York, NY 10012
phone 212-998-5422 fax 212-995-4043 musictechgrad.info@nyu.edu www.nyu.edu
Greg Rippin wrote:
Hello everyone,
I'm having trouble with the ZEXY "msgfile" object--I can't get it to write it's contents to a text file using Win98SE. Has anyone else experienced this?
no... what does it say ? what does it do ?
i developped the msgfile mainly on win32-platforms (win98se and win2k) so it should run and work....
mfg.cd.sasd IOhannes
hi,
not that I know the answer...
Let me add another, slightly related question (although mine is about reading files under Windows, rather than saving):
I wonder if among VC users (and there are so many here!) somebody knows, why open_via_path(), if called from a .dll, always returns an invalid fd? I have to reopen the file, which looks stupid. Or is it only a deficiency of my .dlls?
Krzysztof
IOhannes m zmoelnig wrote:
Greg Rippin wrote:
...
I'm having trouble with the ZEXY "msgfile" object--I can't get it to write it's contents to a text file using Win98SE. Has anyone else experienced this?
...
i developped the msgfile mainly on win32-platforms (win98se and win2k) so it should run and work....
-
Greg Rippin -
IOhannes m zmoelnig -
joge . -
Krzysztof Czaja