News:

Server migration complete, Welcome to version 2.1.1

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 15532
Latest: travispauley
New This Month: 40
New This Week: 28
New Today: 6
Stats
Total Posts: 127446
Total Topics: 15647
Most Online Today: 74
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 4
Guests: 66
Total: 70

Vixen Events and FPP

Started by lrhorer, November 07, 2021, 02:43:24 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

lrhorer

OK, I am using GPIO pins to trigger events in FPP.  This seems to be working, but not quite the way I would like.  I am not certain if perhaps it can work the way I want if I did something a little differently.

First, the steps I am following:

I create main sequences and save them as fseq files.  Then I create brief event sequences and save them as fseq files under the same profile.  I load the sequences onto the Raspberry Pi.  I set the main sequences to play at the desired times.  I also set up the FPP GPIO routine to run the desired fseq file on the leading edge trigger and to stop on the trailing edge.

This causes the event to send out its data when the pin is asserted and to stop when the pin is reset or the sequence ends.  So far, so good.  The problem is, the event blanks the rest of the lights.  This is not what I want.  What I really want is to have the event sequence override only the lights in the channels with active effects in them and continue to play all the other data from the main sequence.  I do know that Vixen can purportedly produce eseq files instead of fseq files, but I am unsure of how the results will be handled by Vixen and then subsequently by FPP.  Can anyone lend some insight?

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod