-
Notifications
You must be signed in to change notification settings - Fork 11
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
Videohub Preset Instances being reset when Companion is restarted #6
Comments
@theColourSpace I'm trying to follow. Do you mean the IP of your instance is getting reset to the default on restart or other settings in the instance? |
No sorry, I mean the "instance feedback" settings for the individual buttons. |
By that do you mean that the feedback itself is gone or simply that the dropdowns have reset to input 1 and output 1? |
That the "instance feedback" field is now empty. |
Could you take a screenshot of this and post it here? |
Before restart. Buttons set with "Select Destination" and "Route Source"
presets.
https://www.dropbox.com/s/c2c5oxw6q89ez4l/b4_buttons.png?dl=1
You can see the instance feedback is present:
https://www.dropbox.com/s/4gy0ijfpuvrck1r/b4_button.png?dl=0
After quitting and restarting companion in headless mode:
https://www.dropbox.com/s/mppya7ay87m5e38/aftr_buttonpage.png?dl=1
Instance feedback highlight no longer appearing. And the instance feedback
actions are missing.
https://www.dropbox.com/s/qszkc05lagh36rm/after_buttons.png?dl=1
|
Is this the only module you use feedback for? I've definitely not seen that before. |
Yes, this is the only module I use feedback for. |
Have you tried using the standard routing presets? I'm curious if the 'Change background by route' will have the same issue. |
These are the standard routing presets. EDIT: Just tested it with the "output X" presets. Same behaviour. |
@willosof or @haakonnessjoen any reason you can think of for this behavior? |
Possibly related. I have error on launch: "24. 00:07:38 CORE(cb): db.tmp->db failed: Error: ENOENT: no such file or directory, rename '/home/pi/companion//db.tmp' -> '/home/pi/companion//db'" |
I to am having same problem but with using atem |
@jkfosler are you also using a pi? |
sorry no windows 10
…On Tue, Apr 30, 2019 at 4:50 PM Keith Rocheck ***@***.***> wrote:
@jkfosler <https://github.com/jkfosler> are you also using a pi?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/bitfocus/companion/issues/626#issuecomment-488127990>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AL6VA5W25DQVU5VIKIR22B3PTC5KTANCNFSM4HHMFBIA>
.
|
Is this the same aissue as the one I'm having? |
Sure sounds like it is.
…On Sat, May 11, 2019, 7:08 AM DrumDrummy ***@***.***> wrote:
Is this the same aissue as the one I'm having?
Click here... bitfocus/companion-module-bmd-atem#23 <https://github.com/bitfocus/companion/issues/639>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/bitfocus/companion/issues/626#issuecomment-491501816>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFZGIKUEYVUSRB2PB5WR4LLPU2SJZANCNFSM4HHMFBIA>
.
|
Still present in companion 2.0. Verified on pi build as well as x64 linux build. |
@haakonnessjoen @willosof looking at the screen shots it seems like there's a condition here where the feedback is disappearing on a restart. I have never seen feedbacks in a bank disappear on a restart, but I only use Windows and this is being flagged for PI and Linux. But I'm not seeing anything the module can do different to prevent this at this point? |
I suspect it's not the module.
…On Thu, Jun 13, 2019, 11:41 AM Keith Rocheck ***@***.***> wrote:
@haakonnessjoen <https://github.com/haakonnessjoen> @willosof
<https://github.com/willosof> looking at the screen shots it seems like
there's a condition here where the feedback is disappearing on a restart. I
have never seen feedbacks in a bank disappear on a restart, but I only use
Windows and this is being flagged for PI and Linux. But I'm not seeing
anything the module can do different to prevent this at this point?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/bitfocus/companion/issues/626?email_source=notifications&email_token=AFZGIKWBBYABXONGZWJGDSTP2JTAXA5CNFSM4HHMFBIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXUDQFQ#issuecomment-501757974>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFZGIKSOWYBWMVYHFQVSO33P2JTAXANCNFSM4HHMFBIA>
.
|
Does this happen if you put the computer to sleep and bring back up again? |
I don't know about sleep. Both the rpi and x64 copies of companion that I run are on server configs, that never sleep. That said, in the latest builds of 2.0 this issue seems to have been fixed! |
@theColourSpace did we ever determine that this is no longer an issue in the recent v2.0 builds? |
Indeed, works a charm now! |
Thanks! |
I don't know if this applies only to videohub instances or others, but the button instance setting is getting erased between restarts of companion.
I have dragged over the presets for my sources, assigned them to buttons for both destination and source. The instance indication for this works spectacularly.
But if I restart the companion (running headless on a pi) it will retain the source and destination routing aspects of the button settings but reset the instance config. So that I need to reconfigure the instance after every restart.
Running 1.3.0 (596e7f6-1412).
The text was updated successfully, but these errors were encountered: