Author Topic: Crash when turning "Output to lights" on in 4.2.13  (Read 4030 times)

Offline Steamyrotter

  • Jr. Member
  • **
  • Posts: 80
    • View Profile
Crash when turning "Output to lights" on in 4.2.13
« on: October 01, 2015, 03:42:43 PM »
Bit of a weird one, and wouldn't have noticed as i am using FPP for proper output....

Tried turning Output to lights on and crashed almost immediately.
Restarted and happened again.

Back tracked to 4.2.11 and it worked OK (All same setup, models and seq files)
OK on 4.2.12

Crashes every attempt on 4.2.13


Might be just me and can cope with it (as if i want output to lights I'll drop to 4.2.12) but a bit strange!

Offline JonB256

  • Hero Member
  • *****
  • Posts: 832
    • View Profile
    • My Christmas Website
Re: Crash when turning "Output to lights" on in 4.2.13
« Reply #1 on: October 01, 2015, 08:53:05 PM »
Had to try. I also am using FPP, not xLights output, so I had never tried it.

My xlights setup is a very simple 128 universes (512, not 510) of all multicast. 
Clicking output to lights did not crash v4.2.13.

Bonus:  I did get lights received on my F16V2 on the appropriate universe (starting at 33)

What is your xLights channel setup?

Offline Steamyrotter

  • Jr. Member
  • **
  • Posts: 80
    • View Profile
Re: Crash when turning "Output to lights" on in 4.2.13
« Reply #2 on: October 02, 2015, 07:08:42 AM »
Universe 1 = 1 - 512. On USB dmx pro
Universes 2-5 set unicast @ length 510.

Same setup in the earlier versions so know that worked..

As said was just trying them to test pixels and controller (e682)
Now I know they work and the FPP matches I'll be testing with that from now on anyway.

Chances are when I turn my lappy on tonight it will probably work OK???

Offline gerry

  • Hero Member
  • *****
  • Posts: 695
    • View Profile
Re: Crash when turning "Output to lights" on in 4.2.13
« Reply #3 on: October 02, 2015, 07:12:43 AM »
Can u post an image of your setup screen ?

Have u defined each e131 universe separately or are they grouped on one line ?

Is the enable flag ticked  ie  is it enable yes ? You can highlight the row and double click to change.

Any diff if set to multicast ?
Gerry

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Crash when turning "Output to lights" on in 4.2.13
« Reply #4 on: October 02, 2015, 07:32:42 AM »
When I see a report that appears a specific version causes a crash I usually look at all the checkins to see if its even possible that any of the checkins could have been responsible.  In most cases it's obvious that nothing changed that could cause it to happen in the new build.  But in this case one checkin does fall into this area so I'm not sure if it could be causing this for you.  The change looked simple enough it was just enabling an output if the Enabled flag is set.

"-- bug(dkulp) The "Enable" flag is only honored when changed while outputting to lights"

Line of code added:
  netobj->SetEnabled(enabled);

Offline Steamyrotter

  • Jr. Member
  • **
  • Posts: 80
    • View Profile
Re: Crash when turning "Output to lights" on in 4.2.13
« Reply #5 on: October 02, 2015, 01:18:09 PM »
Thanks all

please see below for screen dump of setup page

When tried this eve it crashed at the same point.

Set to Multicast and did the same...



[attachment deleted by admin]

Offline gerry

  • Hero Member
  • *****
  • Posts: 695
    • View Profile
Re: Crash when turning "Output to lights" on in 4.2.13
« Reply #6 on: October 02, 2015, 01:27:06 PM »
Do you have any ,odel with a channel number greater than 3062.
Have you tried to save before output to lights to See if u get any message ?
Gerry

Offline Steamyrotter

  • Jr. Member
  • **
  • Posts: 80
    • View Profile
Re: Crash when turning "Output to lights" on in 4.2.13
« Reply #7 on: October 02, 2015, 02:39:05 PM »
Hi Gerry

Last channel is 1712.  nothing higher and no conflicts..

I have tried opening several different ones (inc those with just universe 1)
Tried the following before trying output to lights:-
New Sequence
Render
Save
Play with House View
Play without house view
Universes Enabled
Universes disabled
USB Pro plugged in and out

all crash when selecting Output to lights.
It dumps the fault logs the waves bye bye!!!

btw
Win7 Ultimate on Quadcore Alienware

Offline gerry

  • Hero Member
  • *****
  • Posts: 695
    • View Profile
Re: Crash when turning "Output to lights" on in 4.2.13
« Reply #8 on: October 02, 2015, 08:25:03 PM »
Post the zipped output . Hopefully the developers can see what is wrong.

the last thing I can suggest is to delete the fseq file and save again, then try.

Gerry

Offline Steamyrotter

  • Jr. Member
  • **
  • Posts: 80
    • View Profile
Re: Crash when turning "Output to lights" on in 4.2.13
« Reply #9 on: October 03, 2015, 03:04:42 PM »
Hi Gerry

As above even tried a brand new sequence from scratch and it did it then too....

Here is the ZIP.

Cheers


Offline dkulp

  • Supporting Member
  • Hero Member
  • *
  • Posts: 812
    • View Profile
Re: Crash when turning "Output to lights" on in 4.2.13
« Reply #10 on: October 03, 2015, 08:05:51 PM »
can you change the DMX output to a Null output or another e1.31 output or something temporarily and then try the output to lights?  That may help narrow to see if it's the DMX output or not.
Daniel Kulp
Framingham, MA

Offline Steamyrotter

  • Jr. Member
  • **
  • Posts: 80
    • View Profile
Re: Crash when turning "Output to lights" on in 4.2.13
« Reply #11 on: October 04, 2015, 03:01:00 PM »
OK

Tried DMX disabled (& Saved setup) - Crash
Deleted DMX - Crash
Added NULL - Crashed.....
Changed it to another E1.31 (setup for CH 1-512) - Crash.
Tried other Sequences - Crash....

Sorry!

Also tried Open DMX, Renard, etc on different USB port settings....
All same result......

« Last Edit: October 04, 2015, 03:05:18 PM by Steamyrotter »

Offline Steamyrotter

  • Jr. Member
  • **
  • Posts: 80
    • View Profile
Re: Crash when turning "Output to lights" on in 4.2.13 - Resolved
« Reply #12 on: October 08, 2015, 02:15:18 PM »
Just an update - Now fixed in 4.2.15

Thanks