The UB Public Beta has arrived
Jun 23, 2006 at 6:45pm
The UB Public Beta has arrived
For all of you who have already purchased one of the fancy new Intel
Please be aware that this is a public beta version, so I recommend
Knock yourselves out, kiddies!
Jun 23, 2006 at 8:45pm
Thanks for the great work – this is huge! Ive already been playing
Being a beta however – we need some bug reports :here are some issues
1) imageunits html doc file points to jit.gl.slab’s – small annoyance
and lastly, is it possible to render an entire scene to a texture
thanks for all the hard work – quite a beautiful update.
v a d e //
Jun 24, 2006 at 2:17am
Thanks for the note and the report!
>2) where should we post about beta software, in the respective
Just post everything here, or to support@
There is no beta forum
Jun 24, 2006 at 11:04am
On 24.06.2006, at 04:17, Andrew Pask wrote:
ceci n’est pas un beta forum ;-)
to the subject of this mail:
g5 dual2.33, osx10.4.6
jan ‘croissant’ klug
Jun 26, 2006 at 2:59am
Bug: when creating a standalone, the runtime at /Contents/Mac OS/
Otherwise, looking quite good here, very nice work. Now I just have the LObjects/shell/findfolder blues.
Jun 26, 2006 at 7:17am
I’m getting the following error at the end of a more complex standalone build process:
Including File Info.plist
Then the app .mxf file and my custom icon are getting placed in the same folder as the main patch I’m building from (not in the standalone /Contents/ and /Resources/ folders)
My custom .plist isn’t getting included.
Jun 26, 2006 at 7:39am
More standalone fun. From ChangeLog.rtf:
“Standalones properly build their local search path, consistent with 4.5 behavior — this includes the support folder, which wasn’t being added to the search path.”
This doesn’t appear to be behaving here. Building the test patch below as a standalone produces the same error noted in my previous post during build:
Starting Build for support folder.app…
then throws a similar error when run:
• error: folder: ./support: not a folder
#P window setfont “Sans Serif” 9.;
Which builds and runs fine using Max 4.5.7
Jun 26, 2006 at 10:23am
On 26-Jun-2006, at 4:59, John Pitcairn wrote:
Cycling ’74 made a particularly good effort this time to help 3rd
That said: this is is, I think, the biggest set of changes external
Like all transition periods, it will take a while for everything to
Back to porting…
————– http://www.bek.no/~pcastine/Litter/ ————-
iCE: Sequencing, Recording & |home | chez nous|
Jun 26, 2006 at 12:21pm
At 2:59 PM +1200 6/26/06, John Pitcairn wrote:
John, I’m not getting the same behavior here – what platform are you
One thing I have noted (and this on both Intel and PPC), is that if I
>Otherwise, looking quite good here, very nice work. Now I just have
You and I have very similar 3rd party dependencies…. ;-)
Jun 26, 2006 at 3:06pm
On 26 juin 06, at 12:23, Peter Castine wrote:
> On 26-Jun-2006, at 4:59, John Pitcairn wrote:
That’s true: I could compile my sfmarkers~ external for intel in less
A David suggested, I started from his maximum project, changed the
Centre de Recherches et de Formation Musicales de Wallonie asbl
Jun 26, 2006 at 10:51pm
Otherwise, you might try reinstalling MaxMSP and see if that clears things up.
For future reports, please start a separate thread (instead of replying to this one), as this thread has become rather complex.
Jun 26, 2006 at 11:08pm
Quote: Dan Nigrin wrote on Tue, 27 June 2006 00:21
PPC, OS X 10.4.3, CFM support not installed – I don’t want legacy object support in Max 4.6, I’d like to do it clean.
> You and I have very similar 3rd party dependencies
I’ve replaced shell/findfolder using mxj syscommand for now, might stay that way, I just need to check the license.
LObjects I’ll just make abstractions for the subset of functionality I need, then replace those when I can for improved efficiency. I’ve dealt with most of it, I only use a few objects.
Jun 26, 2006 at 11:34pm
Yup, same here. Peter Elsea, are you listening? :-)
Jun 26, 2006 at 11:42pm
Quote: Dan Nigrin wrote on Tue, 27 June 2006 11:34
He’s working on it…
You must be logged in to reply to this topic.