Sean Meighan
Hardware => Falcon Pi Player => Topic started by: bwinter on December 16, 2018, 03:18:49 PM
-
When using FPP Upload to load a new sequence to the FPP, you have the option of selecting multiple .xml files to upload.
When you select multiple files, do these all re-render prior to being uploaded? Or do they each need to be opened/rendered/saved, prior to batch-uploading using FPP Connect?
-
If I remember correctly you should be uploading the fseq file not the XML?
Sent from my iPhone using Tapatalk
-
Using FPP connect, you select the .xml files. Presumable, this uploads the .fseq file. I’m just confirming that it rerenders prior to uploading
-
I'm a bit out of it this year so I'm not quite certain. But I think the fseq is based on the last save. Best to do a batch render and make sure everything is up to date.
Sent from my iPhone using Tapatalk
-
Im asking specifically how the FPP Connect feature works when uploading in batch.
-
As far as I know and what I experience, when using FPP connect it will upload that latest fseq file for the sequence you select. It does not render it before it sends. You could do a batch render first then go to FPP connect to send fresh fseq files.
-
Thanks—I hadn’t used Batch Render yet (just started using FPP Connect).
Just wasn’t sure if rendering was automatically included in uploading—sounds like it’s not.
-
The batch render is super nice when you have made changes to your layout, like moving existing props around or when you plan to make changes to multiple sequences. Turn off render on save, do all your work, then before you go to bed start your batch render and all is good to go in the AM. :) Then go to FPP connect and upload.
Sent from my SM-N960U using Tapatalk
-
I've used both batch render and FPP connect without any issues. This is a great feature if you need to make changes to your models or layout. A real time saver!!
-
Agreed, they’re great features.
I was just asking for confirmation if batch-upload automatically re-renders prior to uploading. After all, you select the .xml to upload, not the .fseq—so that suggested (to me) that there might be some sort of pre-upload processing of the .xml prior to upload.
But it sounds like that is not that case. They need to be re-rendered separately prior to being uploaded.
-
Since the transfer starts relatively quickly and some of my renders take more time than the transfer it does not appear to me that it is doing any rendering before transfer. Beside I would not want it to do that. Sometimes I am just making a correction to a sequence and need to upload it quickly between plays so I would prefer that the upload do so as quickly as possible.
-
I think I’m the opposite. If I’m making quick tweaks to a song, I upload it directly (and solo) through FPP Connect once I make the tweak. The only time I’ve ever needed to batch-upload was when I need to tweak my show config (and thus re-render/re-upload everything).
-
I don't think you are the opposite. When I make a correction that only impacts one remote (I have 9) I use FPP Connect to upload just to that controller. I seldom upload to the master after I have the first copy of the sequence on it since I have no lights connected to my master and the sync pulses are based on where it is in the sequence / song and not on the sequence data (at least that is my understanding). Now if there was just a way to limit the file sync done by FPP to only selected files that would be great. I know that the sync compares the files and does not copy if they are the same, but it still takes time to go thru all the compares, especially when you have 9 remotes and over 10 sequences.
-
I have the same number of songs/sequences.
I would “batch-upload” the sequences/media from xlights to my Main FPP. From there, I would then multisync all the sequences (and unfortunately some mp4 files) from the Main to all the remotes (takes about an hour, even with compression).
That’s why I wanted to know when the rendering occurred (as I really didn’t have much time to spare, trying things out and testing various options).
I’m really looking forward to the .sseq (abbreviated file transfer that’s being developed). That will REALLY help this process with multiple remotes and sequences.