hi.
i just committed another bunch of things to the CVS, including some bug-fixes
videoV4L seems to be stable now.
zmoelnig@users.sourceforge.net wrote:
i noticed that the reference-patch was broken since all the additional inlets were gone. i have re-added them (without the void "speed") - i don't see any point in not-having them
transformed and scaled the newWave so that it behaves exactly like a square of the same dimension when there is no motion.
the most annoying thing for me with newWave used to be the excentric behaviour (pivot-point not in the center of the Geo) and the weird scaling. it is now more uniform (pivot point in the middle of the Geo)
ASK: why is this "blend" function in there ?
re-appearing every now and then, like the evil undead...
of course i have updated the help-patches (both reference and example patch)
furthermore i noticed, that the pix_film object under macOS does weird things when decoding to YUV, but i have neither found not fixed it.
is this a problem with my compilation ?
so:
please, everybody go and compile Gem again.
i would be thankful to put Gem-0.888-binaries on the server, but i am not very much into compiling Gem for 3 macOS-types. chris, jamie ?
Windows: unfortunately, i have not been able to compile the windows version with FTGL-support. daniel, could you check this out, please ? the pix_film under windows should be pix_filmNEW (thus __FILM__NEW should be defined somewhere: probably in Base/configNT.h), it works for me, but i haven't heard of others. quicktime is rather shakey about opening avis (crashes the 2nd time you open an avi) and i have seen that it is loaded before the normal AVI-loader in the pix_filmNEW_setup(). probably we should swap these ?
pix_video stuff should be traditional, since videoDS is not ported yet and we should make this standard (so don't define __NEW__)
else i think that's it. i think, the pix_kaleidoscope bug should be fixed in the first patch ;-)
mfg,asrd IOhannes
IOhannes m zmoelnig wrote:
please, everybody go and compile Gem again.
I have a problem with the cvs (it was working 2 ays ago) :
cvs -z9 login (Logging in to anonymous@cvs.gem.iem.at) cvs [login aborted]: recv() from server cvs.gem.iem.at: EOF
*****CVS exited normally with code 1*****
a CVS problem???
What can I do?
thanks
Cyrille
Cyrille Henry wrote:
actually it seems to be a problem with the sourceforge-servers.
What can I do?
retry ;-)
as i had problems today too, i was thinking again of moving the cvs-repository from sourceforge to the iem, but this will surely not take place before the release.
mfg.a.rd IOhannes