student of max

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

http://i61.photobucket.com/albums/h41/coolsamer86/before.jpg

http://i61.photobucket.com/albums/h41/coolsamer86/after.jpg

http://i61.photobucket.com/albums/h41/coolsamer86/aftermax.jpg

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!

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 

the max window (its mad )->
http://i61.photobucket.com/albums/h41/coolsamer86/aftermax.jpg


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?

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

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


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.

> ok because of this problem im down to my last back up of the file, 

> when i load my max patch up its ok ish (missing a few images and a 

> 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 

> 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 

> (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

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.

>
>
> 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

> 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.

> > ok because of this problem im down to my last back up of the file,

> > when i load my max patch up its ok ish (missing a few images and a

> > 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

> > (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

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 

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..

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

it fixed its self when i removed every picture based object even knobs (it took me nerly all night to figure that out )

im going to see what happens if i put some back in

thanks for all the help! i really appreciate it !

it fixed its self when i removed every picture based object even knobs (it took me nerly all night to figure that out ) 

im going to see what happens if i put some back in 

thanks for all the help! i really appreciate it !


These are pictctrl objects? Or a mix? It would be extremely helpful 

> it fixed its self when i removed every picture based object even 

> knobs (it took me nerly all night to figure that out )

> im going to see what happens if i put some back in

> thanks for all the help! i really appreciate it !

These are pictctrl objects? Or a mix? It would be extremely helpful  
to know which object is doing this.

>
>  it fixed its self when i removed every picture based object even  
> knobs (it took me nerly all night to figure that out )
>
> im going to see what happens if i put some back in
>
> thanks for all the help! i really appreciate it !
>
> --
> www.myspace.com/lablowjazz


Here is the thread including 2 patches I posted on Feb 8th 07, which 

was very similar. It had nothing to do witch pictl.

Am 12.03.2007 um 12:33 schrieb Jeremy Bernstein:

> These are pictctrl objects? Or a mix? It would be extremely helpful 

>> it fixed its self when i removed every picture based object even 

>> knobs (it took me nerly all night to figure that out )

>> im going to see what happens if i put some back in

>> thanks for all the help! i really appreciate it !

Here is the thread including 2 patches I posted on Feb 8th 07, which  
was very similar. It had nothing to do witch pictl.

> These are pictctrl objects? Or a mix? It would be extremely helpful  
> to know which object is doing this.
>
> jb
>
> Am 12.03.2007 um 12:10 schrieb samer:
>
>>
>>  it fixed its self when i removed every picture based object even  
>> knobs (it took me nerly all night to figure that out )
>>
>> im going to see what happens if i put some back in
>>
>> thanks for all the help! i really appreciate it !
>>
>> --
>> www.myspace.com/lablowjazz
>


im not quite sure, im still slowly putting things back in

(and to be honest im strating to want a break from max lol )

my feelings are that it is to do with vpicture (when you past a pic in) my patch really doesnt like that, and when this first happend i did have alot of them i.e. 25 some small 400*400 some v.big 1200*500

ive put the majority of the pictl objects back in and its ok, altho some times it reports that it cant find the pics, arg :-S

i havent pasted a picture in it yet as im too scared lol , ill pluck up the guts and do it tonight and tell ya what happens

all in all its strange how max reacts in these situation (cords disconecting and so on)

im not quite sure, im still slowly putting things back in 

my feelings are that it is to do with vpicture (when you past a pic in) my patch really doesnt like that, and when this first happend i did have alot of them i.e. 25  some small 400*400 some v.big 1200*500

all in all its strange how max reacts in these situation (cords disconecting and so on)


It sounds to me like there's a failure while the patch is saving -- 

probably some object is overwriting some data. Figuring out which 

object it is would be really helpful! Thanks for trying to isolate 

> all in all its strange how max reacts in these situation (cords 

It sounds to me like there's a failure while the patch is saving --  
probably some object is overwriting some data. Figuring out which  
object it is would be really helpful! Thanks for trying to isolate  
the problem.

> all in all its strange how max reacts in these situation (cords  
> disconecting and so on)


yea its a problem with vpicture it doesnt seem to like tomany of the same picture pasted over and over again i.e. 16

I could never get this patch to do anything wrong, either...

Samer, did you verify that adding vpictures caused the problem 

Am 12.03.2007 um 13:14 schrieb Falk Grieffenhagen:

> Here is the thread including 2 patches I posted on Feb 8th 07, 

> which was very similar. It had nothing to do witch pictl.

Samer, did you verify that adding vpictures caused the problem  
eventually?

> Ji Jeremy,
>
> Here is the thread including 2 patches I posted on Feb 8th 07,  
> which was very similar. It had nothing to do witch pictl.
>
>
> Falk


On thing in general: If the Max window will tell you that inlets or 

outlets are out of range NEVER, NEVER save the patch over the old one. 

You can save as to see if its relevant or not...

If you do this, you will definitely destroy what had been working before...

One of the error messages is: inlet 1 of message out of range.

a message box has only one inlet. which would be inlet 0.

Maybe you named one of your subpatchers message???

If you have the first version of your patch still around, open it as 

text and rename the messages, then they will show up in the patch as 

bogus object with all connections intact...

samer schrieb:
> 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

On thing in general: If the Max window will tell you that inlets or 
outlets are out of range NEVER, NEVER save the patch over the old one. 
You can save as to see if its relevant or not...

If you have the first version of your patch still around, open it as 
text and rename the messages, then they will show up in the patch as 
bogus object with all connections intact...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


with my case tho some how it turned out to be the vpics because as soon as i deleted them all was ok

(im using pictrl for pics now, by setting them to dials with 1 frame)

but i wouldent be suprised if one of my vpics had a stupid name or somthing like that

with my case tho some how it turned out to be the vpics because as  soon as i deleted them all was ok 

but i wouldent be suprised if one of my vpics had a stupid name or somthing like that


Very interesting! Is it a bug or a feature? Is it mentioned 

somewhere? What do you mean by destroy, it turns out like samers or 

Am 14.03.2007 um 15:05 schrieb Stefan Tiedje:

> On thing in general: If the Max window will tell you that inlets or 

> outlets are out of range NEVER, NEVER save the patch over the old 

> one. You can save as to see if its relevant or not...

> If you do this, you will definitely destroy what had been working 

Very interesting! Is it a bug or a feature? Is it mentioned  
somewhere?  What do you mean by destroy, it turns out like samers or  
my patch? (see my post in this thread)

> On thing in general: If the Max window will tell you that inlets or  
> outlets are out of range NEVER, NEVER save the patch over the old  
> one. You can save as to see if its relevant or not...
>
> If you do this, you will definitely destroy what had been working  
> before...


well my patch has got a pattrstorge so it could of been been that,

(i can also email it if that link doesnt work)

if you load it up and click on one of the big buttons youll see the cords every where

well my patch has got a pattrstorge so it could of been been that, 

my messed up patch is attched at
http://www.megaupload.com/?d=7U94P1B0 if you want to compare it 
(i can also email it if that link doesnt work)

No, naturally not. But saving "good patch" doesn't yield "bad patch", 

Am 14.03.2007 um 21:33 schrieb Falk Grieffenhagen:

> So both Versions turn out the same on your maschine? -note there 

No, naturally not. But saving "good patch" doesn't yield "bad patch",  
which is what I was hoping for.

> So both Versions turn out the same on your maschine? -note there  
> are 2 patches.


> but i wouldent be suprised if one of my vpics had a stupid name or

It would be helpful to verify your last statement. It might give 

information of how to avoid such things in the future. If a problem is 

solved this is good news, if its understood its much better news, 

because it can prevent future troubles...

samer schrieb:
> but i wouldent be suprised if one of my vpics had a stupid name or
> somthing like that

It would be helpful to verify your last statement. It might give 
information of how to avoid such things in the future. If a problem is 
solved this is good news, if its understood its much better news, 
because it can prevent future troubles...

> Very interesting! Is it a bug or a feature? Is it mentioned somewhere? 

> What do you mean by destroy, it turns out like samers or my patch? (see 

neither bug nor feature. If you get a message that a loaded patch cannot 

connect an object, it will not have that connection, which had been 

there before. If you save, you get a patch without that connection, 

which refers to what I call "destroy"... (It will be changed and 

If you later find the offending object and replace it with a correct one 

Falk Grieffenhagen schrieb:
> Very interesting! Is it a bug or a feature? Is it mentioned somewhere?  
> What do you mean by destroy, it turns out like samers or my patch? (see 
> my post in this thread) 

neither bug nor feature. If you get a message that a loaded patch cannot 
connect an object, it will not have that connection, which had been 
there before. If you save, you get a patch without that connection, 
which refers to what I call "destroy"... (It will be changed and 
different as the version you loaded...)

If you later find the offending object and replace it with a correct one 
the connection will still be missing...

Am 16.03.2007 um 11:08 schrieb Stefan Tiedje:

>> Very interesting! Is it a bug or a feature? Is it mentioned 

>> somewhere? What do you mean by destroy, it turns out like samers 

>> or my patch? (see my post in this thread)

> neither bug nor feature. If you get a message that a loaded patch 

> cannot connect an object, it will not have that connection, which 

> had been there before. If you save, you get a patch without that 

> connection, which refers to what I call "destroy"... (It will be 

> changed and different as the version you loaded...)

> If you later find the offending object and replace it with a 

> correct one the connection will still be missing...

falk
Am 16.03.2007 um 11:08 schrieb Stefan Tiedje:

> Falk Grieffenhagen schrieb:
>> Very interesting! Is it a bug or a feature? Is it mentioned  
>> somewhere?  What do you mean by destroy, it turns out like samers  
>> or my patch? (see my post in this thread)
>
> neither bug nor feature. If you get a message that a loaded patch  
> cannot connect an object, it will not have that connection, which  
> had been there before. If you save, you get a patch without that  
> connection, which refers to what I call "destroy"... (It will be  
> changed and different as the version you loaded...)
>
> If you later find the offending object and replace it with a  
> correct one the connection will still be missing...
>
> Very simple, very logical...
>
> Stefan
>
> -- 
> Stefan Tiedje------------x-------
> --_____-----------|--------------
> --(_|_ ----|-----|-----()-------
> -- _|_)----|-----()--------------
> ----------()--------www.ccmix.com
>


please help, big bug