Does this happen to you too ? Matrix crash


    Sep 15 2008 | 4:35 pm
    hi folks !!
    quick one here
    each time I quickly activate cells on a Matrix with the mouse , Max crashes ! is this normal ?? for you guys to ? or have I been left behind ?!!!

    • Sep 15 2008 | 5:33 pm
      you mean a matrixctrl? that would be the only mouse-controllable matrix-like interface so i'm assuming you mean matrixctrl but i don't find this problem, myself. perhaps your using it to control matrix~ in a strange way. post your patch and people can try it.
    • Sep 23 2008 | 7:28 am
      sebastian schrieb: > each time I quickly activate cells on a Matrix with the mouse , Max > crashes ! is this normal ?? for you guys to ? or have I been left > behind ?!!!
      No crash is normal. If you can provide a patch along with system information, the guys at c74 are happy to get rid of the crash. Even if the underlying patching has some flaws and you might have asked for trouble, Max should not crash...
      Stefan
      -- Stefan Tiedje------------x------- --_____-----------|-------------- --(_|_ ----|-----|-----()------- -- _|_)----|-----()-------------- ----------()--------www.ccmix.com
    • Sep 23 2008 | 10:29 am
      I can't reproduce with either matrixctrl or jit.cellblock, in either newest max 4 or 5.
      Only thing i did notice was that with jit.cellblock, you can click and drag to select a field in max4, but you cannot do that in max5. Big Deal.
    • Sep 23 2008 | 10:55 am
      guys, matrix crashes all the time! the way i see it, or try to see it, is the following: matrix is as good as a random pile of ones and zeros. it's a wonder it can do anything at all, so when it actually does, no matter how small, or how wrong, just be thankful!
    • Sep 23 2008 | 11:05 am
      Uhh, what are you on?
      I suppose any software is a bunch of 0's and 1's then. Maybe that's a good way of creating programs - brute force and testing - if you have the time.
      But we don't, and i'm still not clear what object we're on here...
    • Sep 23 2008 | 4:08 pm
      On Sep 15, 2008, at 9:35 AM, sebastian wrote: > each time I quickly activate cells on a Matrix with the mouse , Max > crashes ! is this normal ??
      On Sep 23, 2008, at 3:55 AM, geoff wrote: > guys, matrix crashes all the time!
      Assuming that you're both talking about matrixctl, no this is not normal. I use matrixctl all the time, and don't have problems with it.
      Perhaps reinstalling Max would help?
      At any rate, this is probably more an issue for Cycling '74 support than the list. It is not an endemic problem.
      -C
      Chris Muir cbm@well.com http://www.xfade.com
    • Sep 24 2008 | 8:04 am
      geoff schrieb: > guys, matrix crashes all the time! > the way i see it, or try to see it, is the following: matrix is as > good as a random pile of ones and zeros. it's a wonder it can do > anything at all, so when it actually does, no matter how small, or > how wrong, just be thankful!
      Again, in the standard distribution, there is no matrix object. There is a matrixctrl, there is a matrix~. They don't crash here! Fact they don't. It is likely, that there are reasons for your experience. But how should anybody find them, and help you, if there is no patch, no system information???
      Nobody wants crashes, I want to know why its crashing on your machine, and the folks at cycling74 would love to know that as well...
      Please give us your crashes...
      (There are bug reporting guides all over the place...)
      Stefan
      -- Stefan Tiedje------------x------- --_____-----------|-------------- --(_|_ ----|-----|-----()------- -- _|_)----|-----()-------------- ----------()--------www.ccmix.com
    • Sep 24 2008 | 12:06 pm
      Hi guys !
      sorry for the slow reply I am stuck sick in bed.
      I allowed my self to attach the bug report , if one of you guys could help me out !!! that would really make my month , cos so far Max has been crashing to much (to the point that I would not even consider using it in a live gig situation , and that says a lot !) When I say so far I mean since I purchased it !!!
    • Sep 25 2008 | 4:25 pm
      sebastian schrieb: > sorry for the slow reply I am stuck sick in bed. > > I allowed my self to attach the bug report , if one of you guys > could help me out !!! that would really make my month , cos so far > Max has been crashing to much (to the point that I would not even > consider using it in a live gig situation , and that says a lot !) > When I say so far I mean since I purchased it !!!
      Ok, already more. What you attached is called crash report, which at least tells what system you are running, and what Max version. It made me test a matrixctrl, and I got a similar crash! (But only by chance)
      They way you use matrixctrl is probably different than most people use it, that's why mainly you faced this problem:
      A bugreport has to contain a description how it happens. This is mine now:
      Instantiate a reasonable big matrixctrl, like 21*19. Then just drag the mouse a lot and fast around to kind of draw a picture with the points:
      Expected result: I can do it to my liking and in any speed without problem...
      Actual result: After a short while Max will crash on my 1.5 GHz PPC Powerbook running OS X 10.4.11 and Max 5.04...
      All the best for fixing that
      And thanks to sebastian to bring it up.
      Rereading the first post might make me think you thought, you told anything necessary to reproduce it, but we see this sort of (short) question too often to actually take it seriously. That's what bug reporting guidelines are for, take them seriously, so that those who could solve the problem take it seriously as well... ;-)
      To complete the bug report a patch which exhibits this behaviour (we have seen a crash report already):
      (And for those who go into the code, I'd love to see a feature come back to matrixctrl: When "Scale When Resized" is unchecked, I'd love to see the number of collumns and rows adapt to the scaling, like it was in Max 4.x...)
      Stefan
      -- Stefan Tiedje------------x------- --_____-----------|-------------- --(_|_ ----|-----|-----()------- -- _|_)----|-----()-------------- ----------()--------www.ccmix.com
    • Sep 25 2008 | 6:47 pm
      I have logged both the bug and the feature request. FYI, the matrixctrl mousedrag issue only occurs on PPC machines.
      -Ben
    • Sep 26 2008 | 8:27 am
      OK. Here is what I have gathered on Matrix: Flaky motherboard-> cheap chipsets cosing multiple "mix-ups" rendering Huge chunk's of data inaccessible. POV filestructures not reliable. Multiple copies of objects. simultaneous managements of data arrays is going haywire, producing very chaotic output. as for mousedrag, WHEW! don't even know where to begin. it's like to the point where i'm mousing on eggshells, never know when it's going to be "too much." matrixctrl or jit.cellblock, select a field in max4, any of this stuff is working but only for a few minutes at a time and only with the folowing patch:
      ----------begin_max4_patcher---------- j4v$J%Tf*Havf:HO*4h87AIG8h9nawa782oh4&^O* SEKPG85GI&B38bgNHUmpu8jc4ww$Vs5oy3k2G&IB LH(24DVETcoji,-kuNOHUsmolkpgSV#smpvlkjgHO HNnls8u*LI&slnh9cSV#Ylt8yn9b7OTBL)x0ilk-oS# cu6d5l87ck36IV%^Cwonb*&Lcy#%$SAbo*LuVY&^GC &C#4vfi9876ty4xs3NLH(*onlIvDfuI^V5oBG*&BG&O -----------end_max4_patcher-----------
      +++++++++++++++ )*~~*( +++++++++++++++