Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - james7

Pages: 1 2 3 [4]
46
The subject pretty much says it all. Under Mac OS X the realtime preview for the ATrousWaveletTransform is VERY slow under Ripley RC7 (and earlier, this is not isolated to just the RC7 release).

There appear to be two new behaviors with the preview process under Ripley when using the ATrousWaveletTransform. First, you see a dialog for several seconds that says a cache is being computed (this only happens on the first attempt at showing a preview). Then, after the cache dialog disappears there is a very long delay (twenty seconds is not unusual) during which the progress indicator on the preview window spins after which the preview finally appears. This latter delay happens each time you click the preview button in the ATrousWaveletTransform panel. It even happens when you've selected a small preview area within a larger image. Under PixInsight v1.7 I never has such long delays when using the preview function on the ATrousWaveletTransform. It almost seems as if the realtime preview is actually running the full ATrousWaveletTransform process (i.e. the preview isn't any faster than running the entire ATrousWaveletTransform process on the original image).

Mac OS X 10.6.8 (but also happens under Mac OS X 10.7)
Mac Pro (2 x 2.66GHz Xeon)
10GB DRAM

Ripley RC6 and RC7 (and possibly other Ripley releases)

47
Announcements / Re: PI 1.8.0 RC6 Preview
« on: 2013 April 22 15:24:29 »
RC6 still crashes on launch on Mac OS X Snow Leopard (100% of the time). This is a problem that extends back over several releases of Ripley (well documented, the Webkit incompatibility).

Should I just assume that you aren't going to support Mac OS X 10.6 from this time forward? If so, it should be removed from your list of compatible OS versions.


 http://www.pixinsight.com/sysreq/index.html

System Requirements

 Mac OS X

Mac OS X 10.8 (Mountain Lion).
Mac OS X 10.7 (Lion).
Mac OS X 10.6 (Snow Leopard).

48
Bug Reports / Re: 1.8RC5 and Mac OS X 10.6.8 (Snow Leopard)?
« on: 2013 April 01 02:19:09 »
Juan, thanks for the update. It's no burden at the moment for me to go back to v1.7, I've kept a copy in case things didn't work out with v1.8.

Frankly, if you can't build a universal version that will work on 10.6 and 10.7/10.8 then maybe it is time to document that and end support for Snow Leopard. My first generation Mac Pro can run 10.7/Lion, it's just that I've kept on 10.6 because it works well with the remainder of my installed software (as the saying goes, "If it ain't broke, don't try to fix it.")

49
Bug Reports / Re: 1.8RC5 and Mac OS X 10.6.8 (Snow Leopard)?
« on: 2013 March 30 15:33:40 »
Hi,

strange! RC5 really runs fast on my mac? Although I have a MacBook Pro 2.8GHz Intel Core 2 Duo, 8GB 1067 MHz DDR3, OS X 10.8.3.
I do not see why RC5 wouldn't run on your machine? On of the Guru's will surely know what's the problem...

Best
It's a question about the Mac OS X operating system and what versions RC5 will run under. Unfortunately, Apple has seen fit to end support for the first generation, Intel Mac Pro machines and I can't run 10.8 (Mountain Lion). So, here I sit with a machine that should be notably faster than what you have and yet I can't run the latest operating system from Apple. I hope the same is not true with PixInsight 1.8.

50
Bug Reports / 1.8RC5 and Mac OS X 10.6.8 (Snow Leopard)?
« on: 2013 March 29 19:46:10 »
RC5 doesn't seem to run on Mac OS 10.6.8 (crash on launch, first generation Mac Pro with twin 2.66GHz Xeon processors and 10GB DRAM). Here is the relevant section from the  Mac OS X crash report:

Dyld Error Message:
  Symbol not found: __dispatch_source_type_vm
  Referenced from: /Applications/PixInsight.app/Contents/MacOS/../Frameworks/QtWebKit.framework/Versions/4/QtWebKit
  Expected in: /usr/lib/libSystem.B.dylib
 in /Applications/PixInsight.app/Contents/MacOS/../Frameworks/QtWebKit.framework/Versions/4/QtWebKit

This looks like it may be the same problem that was documented in the RC4 release and here is what you announced with that candidate (on March 12):

"This version is not compatible with Mac OS X 10.6 (Snow Leopard). This is due to a problem with the WebKit library, which PI uses to implement its document browsers. We'll release a special version for OS X 10.6 as soon as possible."

Should I assume that this is still a problem with RC5?

51
Bug Reports / Re: osx 10.8.2: PI 1.8 RC1 very slow operations
« on: 2012 December 23 20:39:22 »
I've seen the same thing on my Mac OS X 10.6.8 installation of Ripley. Debayer takes forever, several minutes for each image. Under PI v1.7.X it takes all of two seconds for each image. I'm still looking at what may be causing this, I'm going to move everything from my earlier installation out of the Application directory and try another installation.

One other issue (so far), the update for the new documentation fails unless PI 1.8 is at the root of the Application directory. As a first trial I had placed v1.8 in its own directory below Applications but that didn't work when the update tried to run (reported error, can't find necessary files/resources). I then moved v1.8 to the root of the Application directory and the update seemed to work.

Here is an update, it took 425 seconds for PI 1.8 to debayer ONE image. I'm running on a Mac Pro (2x2 2.66GHz Xeon, "Woodcrest" the first processor to support SSSE3) with 10GB DRAM.

Another update, it seems that it is the Debayer process/icon itself that is slow. If I attempt to open a RAW file directly the speed seems reasonable (a few seconds, with the DSLR_RAW format preference set to VNG). However, if you attempt to debayer a file using the process icon it can takes minutes for the debayer to complete. This means that any workflow that requires the debayer process is effectively unusable under Mac OS X.

52
Bug Reports / Re: File Open Dialog Position
« on: 2012 February 20 15:37:00 »
I've seen something similar. It appears that both the File > Open and File > Save As dialogs (and others?) follow the screen on which the last active window is displayed. Thus, if the Process Console is on your secondary display and is frontmost when you select the "Save As" menu item under the File menu the dialog appears on the secondary display even though your workspace is entirely within your main display bounds. Furthermore, if you have the Screen Transfer Function (process) open on the secondary display and it is the frontmost window the same happens (even when the Process Console is on the main display). However, this seems to happen for only the first activation of the File menu items after a window has been made frontmost on the secondary display. If you invoke the same File menu item a second time it stays on the main display (unless you've made the window that is on the secondary display active again between the two invocations of the dialog.

I'm running a fully updated version of Mac OS X 10.6.8 on a Mac Pro with 6GB DRAM. PixInsight Core 01.07.05.0779 Starbuck (x86_64)

53
Bug Reports / Re: Mac OS X 64 bit updater no-install loop
« on: 2012 February 20 15:15:27 »
Not that it really helps, but I have been using the trial of the 64-bit version of PixInsight for the last month and have gone through at least 3 update sequences (including the core a few weeks ago) and I have had no problems with the update process. I'm running Mac OS X 10.6.8 on a Mac Pro computer with 6GB DRAM. I think I've always updated immediately, as soon as I get the message at launch time (i.e. I click to install the updates, wait until they've finished download, and then quit PixInsight).

Pages: 1 2 3 [4]