please help, big bug

heh, i have experienced this too. are you sending any messages to a thispatcher on the topmost level via a closebang?

no im pretty sure i dont, why what happend in your case ?

well, I think I had a few patchs that would send a write message to thispatcher on closebang. when i would reopen it, every connection seemed to have "been moved over one', very similar to yours. I've had trouble being able able to reproduce the behavior successfully.

thanks jamez but i dont think thispatcher is anything to do with it as some back up of my work in the early stages definitly didnt use thispatcher, but ill bare it in mind

kochcw what do you mean by abstractions? i do have alot of thing which have names as im using the pattrstore object

Hi,

I had this bug too some weeks ago, even posted it but no reply. I
think it had to do with a coll file saved within the patch. It also
had to to with saving: I saved the ok patch a couple of times with
different names and some of them were destroyed and some not.

If you save a coll contetnt in the patch, try to load it manually.

good luck

Falk

Am 11.03.2007 um 19:39 schrieb samer:

>
>
> this is the weirdest thing ever !!
>
> ok because of this problem im down to my last back up of the file,
> this is why
>
> when i load my max patch up its ok ish (missing a few images and a
> few minor problems)
> then i go to save it and load it up again, and all the patch
> cords are all over the place and connected to random objects !! its
> like cords have exploded every where!
>
> first i thought ok this patch is bugerd so i loaded up last weeks
> back up and saved that after doing some work on it to get it up to
> date, and the same thing happend !
>
> (same thing with a back up a made a month ago)
>
> at this point i was getting scared, i loaded up a simple patch and
> saved that and that was ok when i loaded it up
>
> but then i loaded a more complex patch after saving it (with
> graphics, buffers and pattrstorage so on) that had the same problem
>
> i thoght it could be the application it self so i renstalled max
> and jitter and that didn't solve anything either
>
> and the worse thing is that this is part of my university degree
>
> please anybody, help ?
>
> heres a few pics
>
> http://i61.photobucket.com/albums/h41/coolsamer86/before.jpg
>
> http://i61.photobucket.com/albums/h41/coolsamer86/after.jpg
>
> the max window (its mad )->
> http://i61.photobucket.com/albums/h41/coolsamer86/aftermax.jpg
> --
> www.myspace.com/lablowjazz

Seems like the exact same problem happened to me when I was reading writing
pattrstorage xml files: closing, then re-opening the patch. Objects
disappeared (including all colored panels). New objects that weren't in the
original patch appeared and patch cords were totally scrambled resulted in
the huge list of error messages in the Max window. No changes to my system
except some security and daylight savings updates from apple (OS 10.3.9 and
max 4.5.7 jitter 1.5.2)

On 3/11/07, Falk Grieffenhagen wrote:
>
> Hi,
>
> I had this bug too some weeks ago, even posted it but no reply. I
> think it had to do with a coll file saved within the patch. It also
> had to to with saving: I saved the ok patch a couple of times with
> different names and some of them were destroyed and some not.
>
> If you save a coll contetnt in the patch, try to load it manually.
>
> good luck
>
> Falk
>
> Am 11.03.2007 um 19:39 schrieb samer:
>
> >
> >
> > this is the weirdest thing ever !!
> >
> > ok because of this problem im down to my last back up of the file,
> > this is why
> >
> > when i load my max patch up its ok ish (missing a few images and a
> > few minor problems)
> > then i go to save it and load it up again, and all the patch
> > cords are all over the place and connected to random objects !! its
> > like cords have exploded every where!
> >
> > first i thought ok this patch is bugerd so i loaded up last weeks
> > back up and saved that after doing some work on it to get it up to
> > date, and the same thing happend !
> >
> > (same thing with a back up a made a month ago)
> >
> > at this point i was getting scared, i loaded up a simple patch and
> > saved that and that was ok when i loaded it up
> >
> > but then i loaded a more complex patch after saving it (with
> > graphics, buffers and pattrstorage so on) that had the same problem
> >
> > i thoght it could be the application it self so i renstalled max
> > and jitter and that didn't solve anything either
> >
> > and the worse thing is that this is part of my university degree
> >
> > please anybody, help ?
> >
> > heres a few pics
> >
> > http://i61.photobucket.com/albums/h41/coolsamer86/before.jpg
> >
> > http://i61.photobucket.com/albums/h41/coolsamer86/after.jpg
> >
> > the max window (its mad )->
> > http://i61.photobucket.com/albums/h41/coolsamer86/aftermax.jpg
> > --
> > www.myspace.com/lablowjazz
>
>

had some similar issues with a patch few months ago. saved, without
any signs of problems, reopened - right side of the patch was
missing. luckily, i had another similar bit of the patch so i could
copy and paste..... bizzare tough..

klif

well i deleted any abstractions and that didnt do the trick :-(

i deleted the modula that contains pattrstorage, that didnt work either :-(

the strange thing is that the more picture objects i delete the better the patch gets, as in the less messed up cords are, but why ?

there are a lot of pictctrl objects that i really need, ie act as buttons