[SOLVED] Fan tastic

[fredvaillant]

Hi Mark, no problem for this first meeting with v2.2. We know that we upgrade when we're not on stage and v2.1 wasn't crap.

I'll dive in this new version and in few weeks I need for a next project to buy a new computer and it'll run with Capitan.

Tchüss.

[dbini]

to reiterate: i'm getting the problem on 10.9.5 but not on my machine with 10.11.3

i don't have my 10.9.5 machine with me this weekend, so can't test the fix at the moment. I'll report back next week.

John

[mark]

Dear @dbini,

Yes, the problem would not have appeared on 10.10 and later.

I feel confident enough that the problem is addressed that I'll release the v2.2.2 hotfix today.

Best,

Mark

[dbini]

@mark - that's great. I'm running a second laptop with 10.9 because of issues with El Capitan and NiMate.

[mark]

Dear All,

I post the links publicly later, but here is the new build with the fixed MoviePlayer64\. If you see this and can give it a quick try, that would be great.

http://troikatronix.com/files/isadoracore222f00-std.dmg (mac standard)

http://troikatronix.com/files/isadoracore222f00-usb.dmg (mac usb key version)

http://troikatronix.com/files/isadorawin-222f00-std.exe (win standard)

http://troikatronix.com/files/isadorawin-222f00-usb.exe (win usb key version)

Best,

Mark

[fifou]

Mark,

It seems to work ok.. No crash, no useless processsor activity, end loop trigger fired..
Tested on osx 10.9.5

Thanks for the quick fix.

best
Philippe

[mark]

Dear All,

 The issue with 10.9 identified by you all has been solved. Thanks for all the help.

 You can now download v2.2.2 at http://troikatronix.com/download/isadora-download/

 Best,

 Mark

[dbini]

all working for me on 10.9.5 as well, thanks Mark

John

[crystalhorizon]

Everything looks good now, thanx Mark

[dbini]

@Mark: I just started working on my 10.9 machine with 2.2.2, running a syphon feed out of NIMate, after about 10 minutes my laptop started to heat up. The activity monitor is showing suspect IzzyMoviePlayer 32s and 64s not responding, although there's no Report Crash. This time its NIMate that seems to be hogging the processor.

[mark]

Dear @dbini,

This is some kind of weird flaw Mac OS. The "not responding" indicator is not accurate. If the CPU % is off the charts, then let me know. But otherwise, ignore the "not responding" label.

Best,

Mark

[dbini]

Hi @Mark - I just upgraded to 10.10 and the offending processes are no longer showing up in the  monitor - as predicted. NIMate is still a bit angry, but only hogging up to 80% CPU, but its not an Izzy issue, she's only using 12%.

cheers,

John