UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
Hi,
I just installed v2.0.0-beta1 which I am testing with a dataset that works perfectly with version 1.083.4.
I have the following message:
I include the contents of the console
Seems to be a similar problem like I reported yesterday evening... Same error, unkown root cause. Strange thing is, the whole process went 100% fine from Calinbration through Integration, except the auto-save. Sadly there is no visible Integration in the imae viewer which one could attemt to save manually
Thanks for reporting, we've not seen this before and I'll inform Mabula about it.
@jochen-scharmann I see a question mark in the file name in the popup. This may indicate that there is a non-ascii character in the filename and given the location of the question mark I suspect a degrees symbol º. Can you rename the file(s) to not have that character and see if that works? If it does then we will know what to fix in APP. Thanks!
thanks Vincent,
what would be helpful for such type of error message is providing information to the user, what value exactly is wrong, so as a user I could take appropriate action. "Invalid" can mean anything, from special characters, naming, file size, numbers or other values
Jochen
True, however APP should be able to handle all filename characters, so in this case (if we can fix it) it should not happen again.
I confirm that the problem was the character °.
I renamed my files and everything works fine.
Good, that means it's the same issue. We're working on it, thanks for letting us know!
