Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't change Boblight priority #1269

Closed
1 task done
SunnyMoo opened this issue Jul 8, 2021 · 0 comments · Fixed by #1298
Closed
1 task done

Can't change Boblight priority #1269

SunnyMoo opened this issue Jul 8, 2021 · 0 comments · Fixed by #1298
Assignees

Comments

@SunnyMoo
Copy link

SunnyMoo commented Jul 8, 2021

  • I confirm that this is an issue rather than a question.

Bug report

2021-07-08T17:22:38.710Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:270:PriorityMuxer::clearInput()) Removed source priority 128
2021-07-08T17:22:38.710Z [hyperiond BOBLIGHT] (DEBUG) (BoblightServer.cpp:110:BoblightServer::closedConnection()) connection closed
2021-07-08T17:22:38.710Z [hyperiond BOBLIGHT] (INFO) Stopped
2021-07-08T17:22:38.710Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:ComponentRegister::setNewComponentState()) Boblight server: disabled
2021-07-08T17:22:38.710Z [hyperiond BOBLIGHT] (INFO) Started on port 19333
2021-07-08T17:22:38.710Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:ComponentRegister::setNewComponentState()) Boblight server: enabled
2021-07-08T17:22:39.481Z [hyperiond BOBLIGHT] (INFO) new connection
2021-07-08T17:22:39.481Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:161:PriorityMuxer::registerInput()) Register new input 'Boblight@::ffff:192.168.1.10/BOBLIGHTSERVER' with priority 100 as inactive
2021-07-08T17:22:39.482Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:270:PriorityMuxer::clearInput()) Removed source priority 100
2021-07-08T17:22:39.482Z [hyperiond BOBLIGHT] (WARNING) The priority 255 is not in the priority range between 128 and 253. Priority 128 is used instead.
2021-07-08T17:22:39.482Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:161:PriorityMuxer::registerInput()) Register new input 'Boblight@::ffff:192.168.1.10/BOBLIGHTSERVER' with priority 128 as inactive
2021-07-08T17:22:43.584Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:JsonAPI::handleLoggingCommand()) log streaming activated for client ::ffff:127.0.0.1

Steps to reproduce

Go to network services on web config and change boblight server priority value below 128

What is expected?

Priority to be set as wanted. It already worked once before clean reinstalling hyperionNG
I want boblight to be higher priority than flatbuffer (which can't change priority ?)

What is actually happening?

Boblight priority keeps on resetting to 128

System

Hyperion Server:

Hyperion Server OS:

  • Distribution: Windows 10 Version 2009
  • Architecture: x86_64
  • Kernel: winnt (10.0.19043 (WS: 64))
  • Qt Version: 5.15.0
  • Python Version: 3.9.0
  • Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
@Lord-Grey Lord-Grey self-assigned this Aug 3, 2021
@Lord-Grey Lord-Grey added the Bug label Aug 3, 2021
Lord-Grey added a commit to Lord-Grey/hyperion.ng that referenced this issue Aug 3, 2021
Lord-Grey added a commit that referenced this issue Sep 15, 2021
* Do not limit priorities for Boblight (#1269)

* Boblight - Allow to exclude component from build

* Fix merge

* Amlogic - Correct Pixelformat reference

* Remove "wrong" Amlogic ifdef, which was not working before
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants