Messages

1

Do You Need Help? Post it here / Re: No Lights, Lights Not Working

« on: December 12, 2018, 08:12:09 PM »

Can you ping the controller from the xlights machine? If so make sure "Output to lights" is enabled in the console or use the "Test" utility in the Tools menu.

2

Do You Need Help? Post it here / xSchedule API

« on: December 12, 2018, 05:05:55 PM »

Hi guys,

I am creating an interactive web page for my audience and I need help with 2 issues that I am trying to resolve.

If I send the API command “Jump to specified step in current playlist” via URL GET it works as expected regardless of the length of the parameter string.

However, if I send the same command via web service request e.g “{Type:"command",Command:"Jump to specified step in current playlist",Parameters”First Snow”,Data:"0",Reference:""}” a JSON structure exception is returned if the parameter string is more than 10 characters. I am thinking my command structure is not correct.

The other issue is that I don’t see way to get artist or album data via the API. Other than %ARTIST% and %ALBUM% (which does not seem to work via the API) is there a way to query this data via the web Service?

3

Do You Need Help? Post it here / Re: xSchedule Output Processing

« on: November 23, 2018, 04:23:59 PM »

Thanks

4

Do You Need Help? Post it here / Re: xSchedule Output Processing

« on: November 23, 2018, 07:14:04 AM »

Should I enter this a a bug in the bug section?

5

Do You Need Help? Post it here / xSchedule Output Processing

« on: November 21, 2018, 05:47:57 AM »

Hi Guys,

I am using xSchedule64 build 2018.46 64bit and trying to add multiple (3) "Add Color Order" output in the Output Processing window. However only the first entry is saved after clicking the save icon or selecting "Save" from the main menu.

Is this a bug or by design?

6

Bugs in xLights/Nutcracker / Re: xSchedule "Back" (Prior step) Button function

« on: January 23, 2018, 08:14:15 AM »

You are correct, I tested it again with the 64 bit version and the "Back" button does correctly move to the last step if the current position is the first step when pressed, so I stand corrected.

However the "Next" button does stop the playlist if pressed while current position is last step, even with looping enabled.

Okay, if this is by design then so be it.

7

Bugs in xLights/Nutcracker / Re: xSchedule "Back" (Prior step) Button function

« on: January 22, 2018, 05:53:12 AM »

Yes, since it was designed to stop after the last step when looping is not enabled, then any button(s) using "Next step in current playlist" should be disabled. The same also for buttons(s) using the "Prior step in the current playlist" when the position is at the top or first step.

8

Bugs in xLights/Nutcracker / Re: xSchedule "Back" (Prior step) Button function

« on: January 21, 2018, 04:12:46 PM »

Perhaps, but remaining enabled creates options,  providing the ability to manually keep going (a step a time) if desired.  The scenario is that playing stops, but if the "Next" button is executed the next logical step in the last (played) playlist is executed.  I am mostly focused on my audience after my show ends, if they hit the button the next of previous step(not the entire playlist)  runs only once and stops.

9

Bugs in xLights/Nutcracker / Re: xSchedule "Back" (Prior step) Button function

« on: January 21, 2018, 03:15:07 PM »

Okay, that makes sense.

10

Bugs in xLights/Nutcracker / Re: xSchedule "Back" (Prior step) Button function

« on: January 21, 2018, 02:35:50 PM »

Correct, however I think it should jump to the last (since that was logically the previous step) but only if the status is playing (as it does when not at the first or the last step). It also stops playing if "Next" is executed while the last step is being played; in this case I think it should go the first step.

11

Bugs in xLights/Nutcracker / xSchedule "Back" (Prior step) Button function

« on: January 21, 2018, 11:26:18 AM »

Hi Guys,

I am not sure if this in a bug but whenever I trigger a xSchedule "Back" ("Prior step in the current playlist") button  function, the xSchedule stops playing the current step, if the current position is the first (top) step in the playlist. This occurs regardless of the method of trigger (manually in xSchedule or from a remote script).  Is there a simple fix or workaround that does not involve more coding on my end?

This was interrupting my show last Christmas when my audience were using the buttons during the first step.