Softpedia >Windows >Science / CAD >Nebulosity >  Changelog

Nebulosity Changelog

What's new in Nebulosity 4.4.4

Jan 19, 2021
  • Updated to LibRaw 0.20.2 for CR3 support
  • Use LibRAW preference applies at capture as well as loading for better Canon support

New in Nebulosity 4.1.8e (Sep 18, 2018)

  • New percentile-based stacking modes to reject noise, planes, hot pixels, etc.
  • New synthetic flat tool to remove gradients and vignetting
  • Ability to link to FocusMax v4 for auto-focusing (Windows)
  • Ability to use Nebulosity as it were an ASCOM Camera, so other programs can script and control Nebulosity’s captures.
  • Can now name filters for both on-camera and external filter wheels and have multiple saved sets. Can even have “short names” used in filenames.
  • Can use these filter names, series index number, and capture time in any combination you like when capturing a series (Preferences).
  • Complete rewrite of the dialogs / GUI to work well with variable system font sizes and Retina / High DPI screens
  • Simplified camera TEC / filter control into a single control
  • Optionally have the image capture routines run in a separate “thread” so that USB or camera issues won’t lock up Nebulosity
  • Support for Atik cameras greatly enhanced with the One’s filter wheel supported on both Mac and Windows and with most all Atik cameras now supported on the Mac (thanks Nick!).
  • For Mac users, I can no longer say 10.6 is fully-supported. Too many libraries Nebulosity depends on just can’t run on 10.6 anymore. 10.7 is the new official minimum version.
  • For Windows users, 32-bit versions of the OS (e.g., XP) are still supported but this has been now called “deprecated” meaning it is slated to go away down the road. You’re fine for now, though.

New in Nebulosity 3.1.0 (May 14, 2013)

  • The ability to run more than one instance of Nebulosity via a new Launch another instance entry in the File menu. This will launch another instance of Nebulosity to let you run more than one camera or to let you work on several images or projects at once.
  • Creating scripts was not very user-friendly in previous versions. These are very powerful ways to automate image capture and now there is a new script creation tool that lets you write scripts far more easily (and even chose from several pre-made scripts). Just select commands from the list and double-click to add them to the script. If you change the parameter values before double-clicking, the command and parameter will go in there. If not, just edit the script being formed to fill in the desired values. No more having to remember all the commands! Also, if you leave this window with a script in place that you're working on, it will remember it for next time (so long as you don't quit Neb).
  • In addition to the new tool, we have some new script commands and revisions to existing commands to make them easier to use.
  • Times (like exposure durations) are now in seconds with fractions allowed. So, if you want 10.5 seconds you can say "SetDuration 10.5". You should not say the old "SetDuration 10500" (the old msec format). This parallels the main UI. You can also use an "m" in here to denote minutes. For example 'SetDuration
  • 2.5m' would be 2 minutes, 30 seconds. '2m30' would also be this.
  • SetTEC command added to set the TEC regulation temperature (e.g., "SetTEC -10.0")
  • SetPHDDither command added to control the dither level on the PHD link. 0=none, …, 5=extreme
  • Ever want to apply the same processing to another image or set of images? There is now a new Macro tool in place to do just this. Copy/paste from your history (or triple-click, Append to Macro in History or just write it manually) and build up a processing sequence to run on other images.
  • Numerous image adjustment tools and internal bits significantly sped up through use of all available processors on your machine and more efficient code. You should notice that pre-processing and image adjustment is a more responsive, especially on big images and if your computer has several processing cores. In addition, the memory load for color images has been reduced considerably.
  • Extensive support for internationalization and foreign language support. Virtually the entire user interface is now setup for other languages. Currently, we have Dutch, French, German, and Italian!
  • New debayer / demosaic algorithms have been added (a setting in Preferences controls which one is used). Two simple ones (color binning and bilinear), PPG (patterned pixel grouping by Alain Desboilles), and AHD (Adaptive Homogeneity-Directed by Keigo Hirakawa, Thomas Parks, and Paul Lee) are now added to the VNG (variable number of gradients by Ting Chen) previously available.
  • Sliders work most of the time for setting values while manipulating images, but sometimes you want to specify the value exactly. Now, simply double-click on the value and you can specify the image manipulation parameters directly.
  • Ever want to force an image to be “color” even if it’s mono (e.g., to use in pre-processing color images)? We now have a convert to color tool to do just this.
  • What’s an update without updates to the supported camera list?
  • "Atik 3xx,4000,10000" entry changed to "Atik Universal" (Windows).
  • The original "ASCOM Camera" has been removed (early-bound interface that is no longer used in ASCOM as of v5 and v6) and the previous "ASCOMLate
  • Camera" renamed "ASCOM Camera" (Windows).
  • Canon 600D support and updates for T3 and T3i
  • The QSI 500 cameras on the Mac shifted to open-source based libftdi for better stability with the new 600 series cameras. Both have been renamed “QSI 500/600”
  • SBIG has been updated to 4r73B7-based driver for STF-8300 support
  • The main window’s user-interface has gotten a facelift and a number of the colors are now customizable (see Preferences). In addition, a 10% zoom option is in place and zooming in and out is faster and more predictable.
  • For Mac users, one change is that the PPC processors are no longer supported and neither is OS X 10.4 (Tiger). You must be on an Intel, 64-bit capable processor running 10.5 (Leopard) or later. 32-bit Intel processors (e.g., the original Core Duos) will work for most, but not all features (e.g., auto-align non-stellar).