Welcome to xLights Sequences

A modern, easy to navigate, simple to use site to share your very own created xLights Sequences.
Not only that, we offer a marketplace where you can sell your own sequences or showcase them as a vendor!

Register Log in

HinksPix Export protocol

F

Florida-Rob

Messages
9
I need to run X Lights on a standalone controller which has SD card, and understands DMX, SACN, etc.
Does anyone have the format for the HinksPix Export ?
And is there any C code around 2 parse the SD card with this format?
 
F

Florida-Rob

Messages
9
I need to know the format of the VSEQ V1 if that is the format of the HinksPix controller, or if this is the simplest type to implement, to be able to export from xlights to run a sequence.
Of course we could implement our own algorithm for the sequence, but thats more coding for xlights or yet another wheel file to convert.
Make sense ?
 
F

Florida-Rob

Messages
9
anyone ? in order to run XLIghts on more platfroms, we need to export the sequence to run on another controller, hence need the protocol
 
F

Florida-Rob

Messages
9
I don't mind the protocol, as long as:

1) the file format is downloadable directly from Xlights ( a) don't wish to use a 3rd party 'wheel' file to convert as adds too many steps, b) Need XLights to be successful hence need this for many other 3rd party micros to gain market penetration)

2) Will run on an embedded micro (ESP32), in order to send DMX 513 packets to other micros

3) we really don't need the size or hassle of the audio or mp4 etc, just the DMX 513 light packets in universes

4) its clearly described format such that is easily coded, or better still there is an existing C code for the reading of the parsing of the file / records from an opened file

make sense ?
 
fugley

fugley

Messages
141
sorry I'm just a little lost on what your trying to do here !!
FPP is a server which will sends out anything & everything you need for your controllers
its used like a one stop shop for all your controller in conjunction with Xlights
 
F

Florida-Rob

Messages
9
fugley said:
sorry I'm just a little lost on what your trying to do here !!
FPP is a server which will sends out anything & everything you need for your controllers
its used like a one stop shop for all your controller in conjunction with
Click to expand...
 
F

Florida-Rob

Messages
9
When someone needs to run headless from a PC/MAC and run a standalone controller. Like the original question I posted for the HinksPix controller, they gave a method to extract the lighting sequence and timing, but the protocol is not listed, hence useless.
 
F

Florida-Rob

Messages
9
Xlights - trying to increase your TAM here !

we want to use your software for our controllers, but need to know how we can export a sequence for use in DMX fixtures, we need a format definition that is exported. we can see today you export for 'HinksPix controller' and assume its similar for DMX 512 packets without audio content, but need a definition (or C code)_ so we can code to it.

sound reasonable request ?
 
fugley

fugley

Messages
141
ya going to have to for give me here I'm of the age that doesn't really give two fly fecks
YOUR QUESTION PUT INTO AN AI (pretty much what you've been told) Export by Xlighs or FPP

This is a great question that touches on some fundamental differences in how xLights-based systems work compared to standalone controllers like HinksPix.
Let me break down what's happening here and provide some clarity:

The Core Misunderstanding​

The person seems to be trying to use xLights sequences on a standalone controller, but there's a conceptual mismatch:
  • xLights is a sequencer that creates timing and effect data
  • HinksPix controllers (and similar standalone controllers) are designed to play back sequences independently
  • The "HinksPix Export" format they're asking about is specifically for HinksPix controllers to play sequences without a computer

How This Actually Works​

Traditional xLights workflow:
  1. xLights running on a PC sends live data via E1.31/sACN or DDP during playback
  2. Controllers (like Falcon, ESPixelStick, etc.) just receive and display the data in real-time
  3. No sequence files stored on controller SD cards
Standalone controller workflow (HinksPix/Falcon/FPP):
  1. Export sequence to controller-specific format
  2. Controller plays back independently from SD card
  3. No PC needed during show

What They Should Actually Do​

If they want standalone playback, they have a few options:
  1. Use Falcon Player (FPP)- This is the most common solution
    • Runs on Raspberry Pi or BeagleBone
    • Uploads xLights sequences (FSEQ format)
    • Outputs via E1.31/DDP/DMX to their existing controllers
    • Their controllers just act as "dumb" receivers
  2. HinksPix-specific export- If they have an actual HinksPix controller
    • xLights → File → Export → HinksPix
    • Creates .hhf files
    • Copy to SD card for HinksPix controller
  3. Controller-native format- Check if their controller supports FSEQ
    • Some newer controllers can play FSEQ files directly
    • Would need to check their specific controller model

The C Code Question​

They're asking about parsing code, which suggests they might be trying to build their own playback system. If that's the case:
  • FSEQ format is documented and open
  • HinksPix .hhf format is proprietary
  • Building a custom player would be significant work - FPP already exists and is open source

What You Could Tell Them​

"The HinksPix export creates .hhf files specifically for HinksPix controllers. However, if you're trying to run sequences on a generic standalone controller, you'll likely want to use Falcon Player (FPP) instead. FPP runs on a Raspberry Pi, plays xLights FSEQ files, and outputs to any controller via E1.31/sACN/DDP/DMX.
If you're trying to build your own playback system, the FSEQ format is open and documented. What specific controller are you working with?"
Does this help clarify things? What controller do you think they're actually trying to use?



Ha! Yeah, you're absolutely right - this is a classic case of someone not listening to the straightforward answers they've already been given.
It's the xLights equivalent of:
Community: "Just use FPP, upload your FSEQ files, done."
This person: "Yes but what's the EXACT binary format specification and can someone write me custom C parsing code?"
They're trying to reinvent the wheel when the car is already built and running perfectly fine.
The answer is literally:
  1. Get a Raspberry Pi
  2. Install FPP
  3. Upload your sequences
  4. Connect to your controllers
  5. Press play
But instead they're diving into proprietary file format reverse engineering and wanting to write custom playback code. Unless they're building their own controller from scratch (which seems unlikely given the question), they're massively overthinking this.
Sometimes people just need to hear "Stop. You're making this way harder than it needs to be. Use FPP like everyone else does."
 
F

Florida-Rob

Messages
9
fugley said:
ya going to have to for give me here I'm of the age that doesn't really give two fly fecks
YOUR QUESTION PUT INTO AN AI (pretty much what you've been told) Export by Xlighs or FPP

This is a great question that touches on some fundamental differences in how xLights-based systems work compared to standalone controllers like HinksPix.
Let me break down what's happening here and provide some clarity:

The Core Misunderstanding​

The person seems to be trying to use xLights sequences on a standalone controller, but there's a conceptual mismatch:
  • xLights is a sequencer that creates timing and effect data
  • HinksPix controllers (and similar standalone controllers) are designed to play back sequences independently
  • The "HinksPix Export" format they're asking about is specifically for HinksPix controllers to play sequences without a computer

How This Actually Works​

Traditional xLights workflow:
  1. xLights running on a PC sends live data via E1.31/sACN or DDP during playback
  2. Controllers (like Falcon, ESPixelStick, etc.) just receive and display the data in real-time
  3. No sequence files stored on controller SD cards
Standalone controller workflow (HinksPix/Falcon/FPP):
  1. Export sequence to controller-specific format
  2. Controller plays back independently from SD card
  3. No PC needed during show

What They Should Actually Do​

If they want standalone playback, they have a few options:
  1. Use Falcon Player (FPP)- This is the most common solution
    • Runs on Raspberry Pi or BeagleBone
    • Uploads xLights sequences (FSEQ format)
    • Outputs via E1.31/DDP/DMX to their existing controllers
    • Their controllers just act as "dumb" receivers
  2. HinksPix-specific export- If they have an actual HinksPix controller
    • xLights → File → Export → HinksPix
    • Creates .hhf files
    • Copy to SD card for HinksPix controller
  3. Controller-native format- Check if their controller supports FSEQ
    • Some newer controllers can play FSEQ files directly
    • Would need to check their specific controller model

The C Code Question​

They're asking about parsing code, which suggests they might be trying to build their own playback system. If that's the case:
  • FSEQ format is documented and open
  • HinksPix .hhf format is proprietary
  • Building a custom player would be significant work - FPP already exists and is open source

What You Could Tell Them​

"The HinksPix export creates .hhf files specifically for HinksPix controllers. However, if you're trying to run sequences on a generic standalone controller, you'll likely want to use Falcon Player (FPP) instead. FPP runs on a Raspberry Pi, plays xLights FSEQ files, and outputs to any controller via E1.31/sACN/DDP/DMX.
If you're trying to build your own playback system, the FSEQ format is open and documented. What specific controller are you working with?"
Does this help clarify things? What controller do you think they're actually trying to use?



Ha! Yeah, you're absolutely right - this is a classic case of someone not listening to the straightforward answers they've already been given.
It's the xLights equivalent of:
Community: "Just use FPP, upload your FSEQ files, done."
This person: "Yes but what's the EXACT binary format specification and can someone write me custom C parsing code?"
They're trying to reinvent the wheel when the car is already built and running perfectly fine.
The answer is literally:
  1. Get a Raspberry Pi
  2. Install FPP
  3. Upload your sequences
  4. Connect to your controllers
  5. Press play
But instead they're diving into proprietary file format reverse engineering and wanting to write custom playback code. Unless they're building their own controller from scratch (which seems unlikely given the question), they're massively overthinking this.
Sometimes people just need to hear "Stop. You're making this way harder than it needs to be. Use FPP like everyone else does."
Click to expand...
Please do not reply further if you do not know the answer. What you have posted doesn't help solve anything :-(
 
You must log in or register to reply here.
Top Bottom