1) The new loopback plugin works great for me on the RPi, and loaded up fine running QLC on a PC, but I couldn't find the Loopback modules when loading the new version up on Mac OSX. Not sure what that's about, but it just wasn't available.
2) On the RPI Solo Frames aren't behaving properly - they aren't behaving has solo frames, but are just like ordinary frames (IE. buttons aren't be switched off when another is hit).
3) I'm also finding the RPi is freezing up sometimes on loading a new project via the web interface. Can't really get this to happen under specific circumstance, so I'll just keep watching it.
4) Lastly I can't get Artnet to receive on the Rpi from either my PC or Mac. Was working perfectly on 4.8.3
Few Bugs with 4.8.4
-
Massimo Callegari
For #1 and #4 see this:
https://sourceforge.net/p/qlcplus/discu ... #041d/d953
Please let me know if the OSX bundle is OK now.
As for #2, no idea. You should share your workspace so we can check.
Also, does it happen on the desktop version too ?
https://sourceforge.net/p/qlcplus/discu ... #041d/d953
Please let me know if the OSX bundle is OK now.
As for #2, no idea. You should share your workspace so we can check.
Also, does it happen on the desktop version too ?
-
FactorFilms
Yup the new OSX bundle has the loopback, and it works correctly.
The solo frame issue is only happening on the RPi, and it has happened on different files for me. Also, having just been testing it, the web interface has disconnected multiple times when trying to load new projects. Triggering a restart via terminal has been the only way to get it back. I'm also having random time outs on the web interface, where 'connection is lost' and I can't get it back.
And the ArtNet issue on the RPi doesn't work, even if I set it up manually without an autoload project, it still doesn't receive.
I have attached the workspace that I have been using otherwise successfully on the RPi. You'll see the loopback plugin is behaving as it should
The solo frame issue is only happening on the RPi, and it has happened on different files for me. Also, having just been testing it, the web interface has disconnected multiple times when trying to load new projects. Triggering a restart via terminal has been the only way to get it back. I'm also having random time outs on the web interface, where 'connection is lost' and I can't get it back.
And the ArtNet issue on the RPi doesn't work, even if I set it up manually without an autoload project, it still doesn't receive.
I have attached the workspace that I have been using otherwise successfully on the RPi. You'll see the loopback plugin is behaving as it should
- Attachments
-
SubMaster%20Control.qxw- (15.3 KiB) Downloaded 21 times
-
FactorFilms
All fixed on new 4.8.5 GIT except for the solo frame issue - solo frame still acting as ordinary simultaneous buttons on the RPi.
-
Massimo Callegari
This is strange cause the RPi code is the same of the desktop version.
You should experience the same on a PC.
Do you trigger the buttons inside the solo frame from the web interface ?
If so, can you do the same on your Mac and tell us if the behaviour is the same ?
You should experience the same on a PC.
Do you trigger the buttons inside the solo frame from the web interface ?
If so, can you do the same on your Mac and tell us if the behaviour is the same ?
-
FactorFilms
Argh good spot. Yes I just loaded up the project on QLC+ on my Mac and accessed the web interface from my PC, and yes, the Solo frame issue is there too.
Aaaand I've just opened up the same project on my PC, and accessed the web interface from my Mac, and the same problem exists.
So as you predicted, it is a problem inherent in the code on all platforms. Now I guess the question is whether this is a problem with this project file, or the new build?
Aaaand I've just opened up the same project on my PC, and accessed the web interface from my Mac, and the same problem exists.
So as you predicted, it is a problem inherent in the code on all platforms. Now I guess the question is whether this is a problem with this project file, or the new build?
-
dmxWolf
About #2... Did you happen to cut and paste the buttons into the solo frame from a regular frame? This doesn't work, because QLC+ still thinks the cut and pasted button is still in the frame it was cut from for some reason. Just a heads up... don't use cut/copy and paste. Delete it and re-create it where you want it.
-
Massimo Callegari
Just checked SubMaster Control.qxw via web interface on 4.8.4 / Linux.
Solo frames work as expected.
Which browser are you using ? It's suggested to use Chrome, since it has a good implementation of websockets
Solo frames work as expected.
Which browser are you using ? It's suggested to use Chrome, since it has a good implementation of websockets
-
FactorFilms
Using Chrome. Were you dialling into your Linux QLC+ with the web interface? That's the only one I haven't tried. Whereas I have tried accesssing a PC, Mac and RPi QLC+ project, all of which exhibit the solo frame issue.
-
FactorFilms
OK just to make sure it wasn't some inherent issue with the relative complexity of that submaster project, I just created a new document, simple as hell, with a few dimmer channels, two buttons in a solo frame. This project also exhibits the same problem with the solo frame acting as an ordinary frame, but again only in the web interface.
Tested again accessing QLC on Mac, PC and RPi, all of which have the problem. Project attached.
This really must be a bug - it isn't possible that it's only happening in my house on all these different platforms. Even tried accessing the virtual console via Internet Explorer to rule out a cross-platform Chrome issue.
Also BTW there does seem to be an issue with loading projects up on the RPi via the web interface in this new version. More than half the time when I try and load a new project it will freeze on the loading screen, and trying to reconnect to the web interface throws up a "Can't be found" browser error. Have to restart the Pi via ssh.
Tested again accessing QLC on Mac, PC and RPi, all of which have the problem. Project attached.
This really must be a bug - it isn't possible that it's only happening in my house on all these different platforms. Even tried accessing the virtual console via Internet Explorer to rule out a cross-platform Chrome issue.
Also BTW there does seem to be an issue with loading projects up on the RPi via the web interface in this new version. More than half the time when I try and load a new project it will freeze on the loading screen, and trying to reconnect to the web interface throws up a "Can't be found" browser error. Have to restart the Pi via ssh.
- Attachments
-
- Solo%20Frame%20Test.qxw
- (3.37 KiB) Downloaded 26 times
-
Massimo Callegari
OK, just tested on Linux+Chrome and works fine.
I'll try to make a test on the RPi as soon as I can
I'll try to make a test on the RPi as soon as I can
-
Massimo Callegari
Tested on the Pi.
What you see is confirmed.
There's a workaround though: switch to design mode and then to operate mode and the solo frame behaviour gets fixed.
On my PC I was switching to operate mode manually. That's why I've always seen it working.
What you see is confirmed.
There's a workaround though: switch to design mode and then to operate mode and the solo frame behaviour gets fixed.
On my PC I was switching to operate mode manually. That's why I've always seen it working.
-
FactorFilms
Interesting. Work around doesn't help for the RPi because it is running headerless in my setup. But I can wait till the next version.
Glad to know it actually was a bug, and not just going crazy!
Glad to know it actually was a bug, and not just going crazy!
-
Massimo Callegari
It works also if you set the project to autostart and reboot.
Once we find a fix I'll produce a new full image and send an email
Once we find a fix I'll produce a new full image and send an email