Isadora v2.5 - Final Candidate (v2.4.5b09) is available
-
finally, without accents, all is working properly
Jacques -
can you please enter a bug report outlining the elements that are not working with utf8 text.Once in the system, I can confirm the issues, and move them towards a fix.thank you for the great feedback. -
I entered two bug automatically after the crashes with some log, do you think it's not suffisant?I can also send you the patch with the accents who provoke the crashes.All the best,Jacques -
You should have received a support reply from me earlier. I added to your crash report the details you listed above.If you could reply to the support ticket with the izzy file attached it would be great. -
Hi,v245b09I am having irregular results from the node connection wires using the 'command 3' shortcut. When disconnecting from an input the wire displays at obtuse angles and at times with some distance away from the mouse pointer and node input.Using the patch provided yesterday "VIdeoGrid", for example disconnecting wires from the router using the 'command 3' shortcut appear to produce the irregular result on my system.Regards,bonemap -
Hi mark and all,
I'm seeing one unusual issue in 245b09 :
I'm having a frame rate drop from normal to just a few frames/s for any patch when any actors are moved BUT only when MS Excel for Mac (v15.16 (current version)) is open (even a blank worksheet). Closing excel causes izzy to revert to normal. It appears tied to the process "fontd" which is spiking to as much as 60% CPU usage when an actor is moved. The behavior appears ONLY when both Isadora and MSexcel are open. rebuilding the font database does not appear to help...
Thanks,
Ian
-
-
Thanks, I am using OSX 10.11.5\. It doesn't appear to start happen on the first move, but on the second or third?Cheersbonemap -
Just tried it again, before I only tried it on straight lines but you are right, if you disconnect a line with edges once its fine if you disconnect another one it is kind of wonky.I will file a bug report for this.Best Michel -
Dear Everyone,
First, @bonemap's crash was recreated and I will work on that later today.@jhoepffner I think I know what your crash is. I had a crash yesterday too, and it had to do with opening an old (v2.2.2) file with "foreign" characters like é, ç, etc. I am also working on this. But if you have a version of the file that _consistently_ crashed because of this, please send it to me via email.I will get these bugs sorted before the final release.Best Wishes,Mark -
Here is the file who crashes consistently, foreign characters in:– stage name– Trigger Text actors to feed Edit text controls– Radio Button actorWhen i suppress all the faulty letters, it works without problems.Thanks for your attention for the disappearing langages…Best wishes,Jacques -
In this version I opened the sound frequency watcher and made the frequency width very broad, just for testing. I don´t get any triggers...the frequencies I am whistling should be all in the frequency spectrum
I also increased the gain +12dB to get more input -
Ok forgot to turn on sound frequency analysis in the live capture settings...
-
Works great here so far no crashes at all! The one thing i found is the new "zoom feature" on my macbook & trackpad. it is the option (then scrolling with 2 fingers) and not the command key (like mentioned in the knowledgebase.) i hardly use a mouse.
-
I really love the new features, the zoom feature is great (for my eyes)!
With the "trigger text" actor I have some problems: When I open a V2.2.2 izzy file with v.2.4.5b09, all text inputs of trigger text actors get blank. It does not crash but the text information is lost. I hope that this can be corrected, because it will keep older patches "alive" and useable with V2.5
Best wishes, gunther
-
Thank-you all for the feedback.
It is great to have so many people actively testing the latest release.As you find issues, it would be very helpful if you could enter them as bug reports.Our support system / bug tracker, is our go to location for working thru issues.It helps us remain organized, and saves time.http://troikatronix.com/support/isadora/ -
Hi all,
Tried downloading the most recent beta and a Mac OS warning that 'the image is not recognized' as if it was corrupted or something. Tried with both Safari and Chrome. I'm on most recent updates on the mac platform.Thanks,Barry -
Hey everybody,
Just tried to install the beta, having the same problem as Barry.- daniel. -
Dear @brightboy and @danieljackson,
I've just updated to v2.4.5b10\. Please try again.Best Wishes,Mark -
Dear @bonemap + @jhoepffner,
I've just uploaded v2.4.5b10\. Both of your problems should be solved.We were able to reliably recreate @bonemap's problem, and I feel confident this is solved.Jacques, your problem was a bit more subtle. What was happening was that Isadora would only accept UTF8 strings in v2.4.5, but did not allow for the conversion of strings in the old format. I need to make a couple of further changes to ensure no one else runs into trouble with this, but please try opening one of the old files. You should discover that you will not encounter the errors you discovered before.Best Wishes,Mark