From: Milton Aupperle <milton@outcastsoft.com>

Date: October 26, 2009 11:06:54 AM MDT

To: Astro_IIDC@yahoogroups.com

Subject: Re: [Astro_IIDC] Re: Is anybody experiencing problems with snow leopard?


Antonio ;


In your "report"  (which didn't mention the 2x  issue) the thread that crashed has ridiculous offsets in the calling functions. My code isn't 1.9 million bytes in size, so the offsets that OS X was showing are impossible. That usually means OS X or QuickTime has trashed itself, which is why I suggested that you re-boot before getting back to me.


The other bug report similar to this from a fellow who re-started, the problem went away and was non repeatable. Maybe it's the same bug, how would I know because you provide no details in your report on what your were doing or how it got there.


When submitting bug reports, you need to tell me what you were doing and send the relevant Astro IIDC logs too (i.e. movie stacking in this situation) . A crash log usually tells me what crashed (it may not even be Astro IIDC), version info and Mac hardware used too. But it tells me nothing about what you were doing or how you got there. I need both to even begin to figure out what is happening.


The only defined bug I know of in 10.6.1 is it screws up any 8 bit monochrome movie that have a width that isn't a multiple of 4 (or possibly 16). I had a report to this saturday and the movies are diagonally offset when played back in QuickTime.That doesn't happen under QT 6.5.4 under 10.5.11 or 10.4.8, so it's a "new feature" of Apples.


The scaling code will rely on Apple to pass us the correct row bytes, and if they don't do that, then it will likely crash. Not much I can do about it if they lie about sizes as I can't know what sizes are real and which are due to Apples screw up.


And I do not consider 10.6.01 stable and likely it won't be stable until maybe 10.6.04 to 10.6.06, just like every other OS X version Apple has inflicted on people. Apple wouldn't be working around the clock to rush 10.6.2 out the door if it was stable (2 release in less than a month). On the Apple Developer and user lists, there are tonnes of reports from Mac developers and users about broken stuff in USB, FireWire, QuickTime and Quartz Composer list I frequent. If you check the Mac boards and news groups, you find all sorts of stuff that is broken. I have also seen bugs that were in Panther and Tiger suddenly show up in Snow Leper too for QuickTime problems, so they are screwing around with code all over the place. For a performance update, they sure broke a crap load of code with did minimal Q&A testing before shoving it out the door. Look at how many apps Apple wrecked on the MacinTouch lists, such that they set up a list for developers to indicate whether there apps was broken under 10.6 -that doesn't indicate stability.


Milton J. Aupperle

President

ASC - Aupperle Services and Contracting

Mac Software (Drivers, Components and Application) Specialist

#1106 - 428 Chaparral Ravine View SE.

Calgary Alberta T2X 0N2

1-(403)-453-1624

milton@outcastsoft.com

www.outcastsoft.com



On 26-Oct-09, at 5:57 AM, aa27100 wrote:

Well, it seems that the what is no longer working is the frame rescaling in the dialog box of "stack & align": setting at 2x crashes the program (I used to set it at 2x before upgrading to OSX 10.6.1). Everything else seems ok: disappointing, but I see it a minor bug which I can live with.


Antonio