I just upgraded to Firmware 2.0.1 and what;s happening:
- during upgrade a short while I get chinese (or pixelated?) letters on screen of the wolfmix
after upgrade:
- all projects are erased on my Wolfmix.
- restore projects from my pc to the wolfmix does not work and gives error message unless I save a project on my wolfmix.
- after saving an empty project on my wolfmix, I can succesfully restore my projects to the wolfmix.
Looks like whole new system! Love the extra options. Now go and try this beast firmware! Here come's trouble LoL
Upgrade to Firmware 2.0.1 behaviour
Re: Upgrade to Firmware 2.0.1 behaviour
Also new behaviour: I had project called "Project A" loaded in the Wolfmix. Choose in the WTOOLS to restore another project called "project B" and that project B is immediately loaded and set as active project?
I was used to restore projects with WTOOLS, but they never replaced my already loaded project immediately?
I think it would be better to have the old way back? I want to choose myself when I load a project.
Example: I have the wrong project loaded, but there is already some lighting in the venue going on. I want to restore the correct project, but want to choose the right moment to switch to my other project. That way I can choose when I have time to restore the correct project and choose the moment it's the least interrupting in the venue.
But hey, that's my personal opinion.
I was used to restore projects with WTOOLS, but they never replaced my already loaded project immediately?
I think it would be better to have the old way back? I want to choose myself when I load a project.
Example: I have the wrong project loaded, but there is already some lighting in the venue going on. I want to restore the correct project, but want to choose the right moment to switch to my other project. That way I can choose when I have time to restore the correct project and choose the moment it's the least interrupting in the venue.
But hey, that's my personal opinion.
Re: Upgrade to Firmware 2.0.1 behaviour
Hello!
Thanks for the report- I'll address each point below...
Kind regards,
Will
Thanks for the report- I'll address each point below...
- This is expected! During the update all the text symbol data needs to be rewritten, so there is a brief moment where there are no loaded letter symbols."during upgrade a short while I get chinese (or pixelated?) letters on screen of the wolfmix"
- Again, this is expected- however we are going to push an update to WTOOLS that encourages users to backup their project files before proceeding (generally speaking, this should be done anyway- but it can be an overlooked which could cause problems!)."all projects are erased"
- The problem here appears to be actually linked to your second message about projects opening once synced from WTOOLS! If a project has unsaved changes, then you sync a project from WTOOLS- it shows an error. I've logged this with the devs to look into!"restore projects from my pc to the wolfmix does not work and gives error message unless I save a project on my wolfmix"
Kind regards,
Will
Re: Upgrade to Firmware 2.0.1 behaviour
THX for the reply and explanation!
Also all my restored projects display on the Wolfmix as "project name"-v2
So all my projects have -v2 added at the end of the projectname.
Is this because of other settings in firmware 2.0? And I can imagine this is done so you know it's not downwards compatible to the older firmware which possible does not understand all the extra's in the project?
Also all my restored projects display on the Wolfmix as "project name"-v2
So all my projects have -v2 added at the end of the projectname.
Is this because of other settings in firmware 2.0? And I can imagine this is done so you know it's not downwards compatible to the older firmware which possible does not understand all the extra's in the project?
Re: Upgrade to Firmware 2.0.1 behaviour
In fact, when syncing a new project file from WTOOLs- there should be a message that appears asking if you want to 'convert this old project file' (or something along those lines). It looks like this message is missing in 2.0.1 - so that likely causes (or is linked to) the issue described in the initial message.
Converting old projects into 2.0 does, as you mentioned, add a v2 suffix to the project name. This reason is two fold- firstly (again, as you mentioned) so that you can track which projects are '2.0' native, therefore no longer compatible with v 1.x. The second reason is that it prevents accidental overwrites when backing up your project files, so if you have a version of a project that is 1.x compatible- then you want to try out 2.x - you will end up with 2 different project files backed up rather than one project that is no longer backwards compatible!
Kind regards,
Will
Converting old projects into 2.0 does, as you mentioned, add a v2 suffix to the project name. This reason is two fold- firstly (again, as you mentioned) so that you can track which projects are '2.0' native, therefore no longer compatible with v 1.x. The second reason is that it prevents accidental overwrites when backing up your project files, so if you have a version of a project that is 1.x compatible- then you want to try out 2.x - you will end up with 2 different project files backed up rather than one project that is no longer backwards compatible!
Kind regards,
Will
-
- Posts: 3
- Joined: Fri Jul 26, 2024 8:31 am
Re: Upgrade to Firmware 2.0.1 behaviour
When setting fixture limits, Wolfmix reboots...
Re: Upgrade to Firmware 2.0.1 behaviour
Update (devs are well caffeinated today!), the problem has been located and fixed. This will be available in the next update very soon.
Kind regards,
Will
Kind regards,
Will
Re: Upgrade to Firmware 2.0.1 behaviour
Hmm, I'm not able to reproduce. What exact fixture name/brand are you using? Are you setting limitations on multiple fixtures, or just one? Is there any specific limitation that you are setting that causes the crash?
Kind regards,
Will
-
- Posts: 3
- Joined: Fri Jul 26, 2024 8:31 am
Re: Upgrade to Firmware 2.0.1 behaviour
It's a Shehds LED Beam 8x12W RGBW bar with Tilt function. I use 2 of these fixtures. Only trying to set the tilt limitation.
Also, when scrolling through the fixture list, after fixture 8 it jumps back to 1 in stead off scrolling through.
I'm working in a old project file, maybe that's the problem and I need to start from scratch?
Re: Upgrade to Firmware 2.0.1 behaviour
Thanks for the report! I can reproduce with this specific fixture. It's been reported for the devs to look into!
Kind regards,
Will
Kind regards,
Will