Which round.mxo?
Just noticed a warning that I have round.mxo in both Max externals and Jasch externals.
Should I rename the Jasch one to something else?
probably. That’s what i did anyway ; i wouldn’t mess with any external of vanilla build.
ok — it’s a bit odd (or nuisance) that the jasch collection has an object with the same name. I’m assuming there’s some historical reason for this (perhaps the function behaves slightly differently). I’ll rename it to jasch.round, I suppose.
Thanks
—–
Hmmm, looking at it, I’m wondering if I need to rename the ’round’ that’s inside the package contents as well?
I think I’ll just delete it for now — it’s in my version control system anyway
wha tdo you mean by "version control system" ?
Anyway, the jasch round is called round because the jasch library author created that object before the round external was added to vanilla Max (was it one of the Max 5 updates ? or Max 6 ?). Also it indeed does behave quite differently, according to helpfile it’s an "unaltered c function" which outputs floats, and rounds the incoming value to next higher integer ; whereas Max’s round performs a closest-integer rounding. You can recreate this behaviour using the vanilla round by adding 0.499999 to the incoming value, but indeed, it’s not the same operation…
Yeah, I figured that was the difference.
Version control systems allow developers to keep track of all changes made to files (and groups of related files) over time. Very strongly recommended for both individuals and teams.
See (for example) http://en.wikipedia.org/wiki/Revision_control for more information.
but i have no idea ho to use such a thing with a max library ! is it your own custom verison control system, or some well known program you’re using ?
Version control systems are very well known and there are many different kinds. These days I’m using Git (thanks, Peter!)