Author Topic: 4.01.10 - crash whilst trying to change effect property  (Read 2465 times)

Offline AussiePhil

  • Newbie
  • *
  • Posts: 23
    • View Profile
4.01.10 - crash whilst trying to change effect property
« on: July 13, 2015, 07:05:30 AM »
Recreated this tonight, steps used were:
Open XL4
Create new model for matrix, save
go to sequencer tab
Create new 40fps animated sequence
add model to sequence
create single timing mark around 10 seconds
add affect
drop the dots (searchlight) effect over the top as replace
go to effect property and try and change number of dots
immediate crash

Windows 8.1 update2 with all current patches

Attached is tonights debug plus two others relating to similar cause.


Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: 4.01.10 - crash whilst trying to change effect property
« Reply #1 on: July 13, 2015, 08:06:28 AM »
Are you talking about the Circles effect?  You can see the name in the effect settings dialog combo-box.

Offline dkulp

  • Supporting Member
  • Hero Member
  • *
  • Posts: 812
    • View Profile
Re: 4.01.10 - crash whilst trying to change effect property
« Reply #2 on: July 13, 2015, 10:34:22 AM »

Another note:  the crashes from above are definitely not from the sequence of events you describe above.   They have Text effects being rendered with specific text in them ("Now playing ..").   
Daniel Kulp
Framingham, MA

Offline gerry

  • Hero Member
  • *****
  • Posts: 695
    • View Profile
Re: 4.01.10 - crash whilst trying to change effect property
« Reply #3 on: July 13, 2015, 09:02:20 PM »

Another note:  the crashes from above are definitely not from the sequence of events you describe above.   They have Text effects being rendered with specific text in them ("Now playing ..").

Hi Gil,

I had posted a similar item about week before last re crashes with the text effects (for a matrix) , though I managed to get one to work without crashing so I could see how it appeared on the P10 panels . When you say "specific text", do you mean that only some text content will cause a crash ? Because I don't really care about the words , just need to play with the font and scroll speed and direction working , so can fine tune and then replicate. This is (for now) the most useful effect to test on the P10s.
Gerry

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: 4.01.10 - crash whilst trying to change effect property
« Reply #4 on: July 13, 2015, 10:22:58 PM »
You quoted Dan and addressed me. :)  I have no idea I've put plenty of text on my sequences with no issues.

Offline gerry

  • Hero Member
  • *****
  • Posts: 695
    • View Profile
Re: 4.01.10 - crash whilst trying to change effect property
« Reply #5 on: July 13, 2015, 10:31:38 PM »
You quoted Dan and addressed me. :)  I have no idea I've put plenty of text on my sequences with no issues.

Sorry Gil , Dan !

I am guessing that the issue is somewhat recent.
Gerry

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: 4.01.10 - crash whilst trying to change effect property
« Reply #6 on: July 13, 2015, 11:23:25 PM »
I haven't seen it.  Not sure what's causing it.  One of those log kind of appeared that multiple threads were trying to render the same effect on the same model and layer.

Offline AussiePhil

  • Newbie
  • *
  • Posts: 23
    • View Profile
Re: 4.01.10 - crash whilst trying to change effect property
« Reply #7 on: July 14, 2015, 07:50:30 PM »
Are you talking about the Circles effect?  You can see the name in the effect settings dialog combo-box.

Yes Gil, I was, sorry


Another note:  the crashes from above are definitely not from the sequence of events you describe above.   They have Text effects being rendered with specific text in them ("Now playing ..").   

Dan, sorry looks like it confused things by adding multiple files... the newest debug file came precisely from the sequence of events described.

I haven't seen it.  Not sure what's causing it.  One of those log kind of appeared that multiple threads were trying to render the same effect on the same model and layer.
in one of the log files I would have had 2 or 3 matrixes with similar names all running copies of the same effect.
Phil

Phil