QUINLED DIG-OCTA - several output types missing in device setup

[DaleTiger]

--------- Instructions -------- Please provide answers directly below each section. --------- Instructions ---------

ESPixelStick Firmware Version 4.0-beta5

Hardware Version QuinLED Dig-Octa

Binary release or compiled yourself? Binary release

Operating System (and version) Windows 11

Web Browser (and version) Mictosoft Edge Version 119.0.2151.97

Access Point Netgear AC1450

Describe the bug Several output types missing in device setup for DIG-OCTA firmware GECE, DMX, Renard, Serial (I need GECE for my setup).

[DaleTiger]

[MartinMueller2003]

What output types do you believe are missing? The current supported list was chosen by Quindor. If you really think something is missing, then do a factory reset. Thaat usually clears such things up.

[MartinMueller2003]

And if you want GECE (Quindor asked not to include that) I can give you a build that includes it.

[DaleTiger]

Thanks Martin.

It's strange they didn't want to include GECE on the OCTA since it's supported on the DIG-QUAD.

Sincerely,

Dale Smith

Get Outlook for Androidhttps://aka.ms/AAb9ysg

---

From: Martin Mueller @.> Sent: Wednesday, December 6, 2023 9:29:43 AM To: forkineye/ESPixelStick @.> Cc: DaleTiger @.>; Author @.> Subject: Re: [forkineye/ESPixelStick] QUINLED DIG-OCTA - several output types missing in device setup (Issue #698)

And if you want GECE (Quindor asked not to include that) I can give you a build that includes it.

— Reply to this email directly, view it on GitHubhttps://github.com/forkineye/ESPixelStick/issues/698#issuecomment-1843116623, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BC6OROYF5X7TLCAK7MTICYTYICFOPAVCNFSM6AAAAABAENXEB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBTGEYTMNRSGM. You are receiving this because you authored the thread.Message ID: @.***>

[MartinMueller2003]

Please download the latest dist in my google drive: https://drive.google.com/drive/folders/1bGrkXSMoGjWtX5iWspPFRogM2G6c1VXu?usp=sharing

[DaleTiger]

Martin,

I really appreciate this! I still have a lot of GECE wire frame props and pathway lights.

Is there a process to contact the folks at Quin-LED to talk about their pixel type support criteria? I would really like to get their thoughts on pixel type support. There are a couple of other pixel types I don’t use at this time but could see a future need for them (i.e. Renard, Serial) to name a few.

I would also like to offer any assistance you may need on program development (like beta testing) or whatever would help further the cause.

Again, thanks for the great work you do.

Sincerely,

Dale Smith

From: Martin Mueller @.> Sent: Friday, December 8, 2023 8:58 AM To: forkineye/ESPixelStick @.> Cc: DaleTiger @.>; Author @.> Subject: Re: [forkineye/ESPixelStick] QUINLED DIG-OCTA - several output types missing in device setup (Issue #698)

Please download the latest dist in my google drive: https://drive.google.com/drive/folders/1bGrkXSMoGjWtX5iWspPFRogM2G6c1VXu?usp=sharing

— Reply to this email directly, view it on GitHubhttps://github.com/forkineye/ESPixelStick/issues/698#issuecomment-1847328746, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BC6OROYMK6MNO65LBVK26W3YIMTINAVCNFSM6AAAAABAENXEB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXGMZDQNZUGY. You are receiving this because you authored the thread.Message ID: @.**@.>>

[MartinMueller2003]

I got my direction from Quindor. You can contact him on his discord server: Intermit.tech. I also do not think a lot of thought went into the decision. The focus for the octo was on specific pixel types so all serial protocols were left out.

[DaleTiger]

Good afternoon Martin,

I hope you don’t mind that I use e-mail to ask this question. I don’t think it’s a bug so I thought e-mail would be best.

Running 4.0-beta5

My question is this. What does this message from the serial output of a QuinLED-DIG-QUAD mean?

13:04:49: [InputMgr] ParseFseqFile:: Could not start: XmasEve12-24.fseq File does not contain enough data to meet the Stated Channel Count * Number of Frames value. Expected 11381832, Got: 2420736

Thanks for your help.

Sincerely,

Dale Smith

From: Martin Mueller @.> Sent: Friday, December 8, 2023 2:50 PM To: forkineye/ESPixelStick @.> Cc: DaleTiger @.>; Author @.> Subject: Re: [forkineye/ESPixelStick] QUINLED DIG-OCTA - several output types missing in device setup (Issue #698)

I got my direction from Quindor. You can contact him on his discord server: Intermit.tech. I also do not think a lot of thought went into the decision. The focus for the octo was on specific pixel types so all serial protocols were left out.

— Reply to this email directly, view it on GitHubhttps://github.com/forkineye/ESPixelStick/issues/698#issuecomment-1847827275, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BC6ORO2V3M5A47A5PMZOETTYIN4OBAVCNFSM6AAAAABAENXEB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXHAZDOMRXGU. You are receiving this because you authored the thread.Message ID: @.**@.>>

[MartinMueller2003]

I dont mind at all. 

It means the fseq file has been truncated in some way. The fseq header at the start of the file says there should be N bytes of data in the file but the file actually has less than that. This is an oft reported issue when using xLights FPP Connect to send files to the ESP. Martin On Saturday, December 16, 2023 at 02:18:39 PM EST, DaleTiger @.***> wrote:

Good afternoon Martin,

I hope you don’t mind that I use e-mail to ask this question. I don’t think it’s a bug so I thought e-mail would be best.

Running 4.0-beta5

My question is this. What does this message from the serial output of a QuinLED-DIG-QUAD mean?

13:04:49: [InputMgr] ParseFseqFile:: Could not start: XmasEve12-24.fseq File does not contain enough data to meet the Stated Channel Count * Number of Frames value. Expected 11381832, Got: 2420736

Thanks for your help.

Sincerely,

Dale Smith

From: Martin Mueller @.> Sent: Friday, December 8, 2023 2:50 PM To: forkineye/ESPixelStick @.> Cc: DaleTiger @.>; Author @.> Subject: Re: [forkineye/ESPixelStick] QUINLED DIG-OCTA - several output types missing in device setup (Issue #698)

I got my direction from Quindor. You can contact him on his discord server: Intermit.tech. I also do not think a lot of thought went into the decision. The focus for the octo was on specific pixel types so all serial protocols were left out.

— Reply to this email directly, view it on GitHubhttps://github.com/forkineye/ESPixelStick/issues/698#issuecomment-1847827275, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BC6ORO2V3M5A47A5PMZOETTYIN4OBAVCNFSM6AAAAABAENXEB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXHAZDOMRXGU. You are receiving this because you authored the thread.Message ID: @.**@.>>

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were assigned.Message ID: @.***>

[MartinMueller2003]

Output Types have been added.