Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.



  • Content Count

  • Joined

  • Last visited

Community Reputation

22 Excellent

About perdrix

  • Rank

Profile Information

  • Gender
  • Location

Contact Methods

  • Skype
  1. I'll post to the DeepSkyStacker mailing list over at groups.io as soon as I know. David
  2. If you look at the dcraw webpage you will see that it supports: Canon EOS 5D Canon EOS 5D Mark II Canon EOS 5D Mark III Canon EOS 5DS Canon EOS 5DS R notably the Mark IV is not supported. So I'm afraid that until Luc finishes converting the code to use libraw, we won't be able to support the EOS 5D IV David
  3. Darn how embarassing - the problem is with the 32 bit assembler code in zlib inflate_fast(). I can fix it at the cost of some performance. Let me see how we can best get this drop shipped. David
  4. Without further information, I can't determine why that happened. What size of image were you trying to stack (i.e. what camera). Were you using Drizzle? If so the odds are you just ran out of memory. It's really very hard to handle that condition. On the subject of Drizzle - there is really very little point using Drizzle except on undersampled images - if you have well oversampled stars you are just wasting time and processing resources if you enable Drizzle. David
  5. Are you sure you've not accidentally changed the White Balance settings in the Raw/DDP settings? Is it possible you are now stacking with "Per Channel Background Calibration", when before you were using "RGB Channels Calibration"? Per Channel Calibration will give you a much redder image (typically) than will "Per Channel ..." Please can you let us know what camera you are using. Thanks, David
  6. Other AV packages reacted the same because they've never seen it before - AVG for one had it submitted and it was pronounced clean by them. If you are concerned, do feel free to submit it for evaluation, bit I'm pretty sure it is virus free. David
  7. I've logged this an issue - our next development goal is to migrate from dcraw to libraw for handling raw files, so there may be hope. If you can make a few subs available for testing that would be very useful. David
  8. I'm very pleased to announce that we've just released DSS 4.1.0. If you just want to grab zip files of the installers you can get them from: https://github.com/LucCoiffier/DSS/releases/download/4.1.0-Release/DeepSkyStacker64Installer.zip https://github.com/LucCoiffier/DSS/releases/download/4.1.0-Release/DeepSkyStackerInstaller.zip Otherwise here's some more information. This version of DeepskyStacker is supported on Windows 7, Windows 8, Windows 8.1 and Windows 10 and completely supersedes DeepSkyStacker 3.3.2, 3.3.4 and 3.3.6. We now provide DeepSkyStacker and the other programs as both 32-bit (x86) and 64-bit (x64) builds based upon the latest version of dcraw. There are separate installers for the 32-bit and 64-bit versions. Installing the 32-bit build will remove earlier versions of DeepSkyStacker (3.3.2 and upward). If you are running an earlier version than 3.3.2, please remove it manually. You can install both the 32-bit and the 64-bit versions on 64-bit versions of Windows without problems. PLEASE NOTE: If anyone who installs this gets: "This program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing" when they try to open the programs, the solution is to install: https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows for your specific version of Windows. This problem should only affect users of Vista / Win7 / Win 8.x who are behind on WindowsUpdates, or are running an offline system and opting out of WindowsUpdates. Enjoy, Luc Coiffier, Tony Cook, David C. Partridge We've fixed a number of problems since 4.1.0 beta 1: 1. Fixed a problem when using drizzle and Intersection mode which resulted in an output image that was 4x or 9x too large with the image in the upper left corner. 2. Worked around a problem with incorrect display of the left panel on high resolution monitors. (Set the DPI Aware flag in the application manifest to No). 3. Changed our build of libtiff so that we use Unix style rather than Win32 style I/O as the Win32 code is wrong in x64 mode (known problem with libtiff). 4. A number of other size_t/DWORD/long issues in the code were fixed for the 64 bit build (to ensure computed values were indeed 64 bit sized). 5. Small change to improve the responsiveness of the post-processing screen (faster display of the final image). If you wish to download the installers as .exe files or download the source code, you can go to: https://github.com/LucCoiffier/DSS/releases Clear Skies David Partridge
  9. I'm having to work it out as I go along myself with help from Luc C. Luc is really the only one who knows the code well enough to write descriptions for all the classes. I will say however that by and large it isn't that much effort to work your way round most of it especially now that I've added a trace capability (Class ZTrace in the ZLib folder). Quick summary: There are three main projects in the VS2017 sln file (which is in the root of the DSS tree). They are DeepSkyStacker, DeepSkyStackerCL and DeepSkyStackerLive whose project files are in the eponymously named folders. These build the three main components of the distribution. DeepSkyStackerCL and DeepSkyStackerLive (we generally refer to these as DSSCL and DSSLive) use a lot of code from the DSS folder. Help is in the Help folder, install scripts for NSIS in the Installer folder. All the remaining folders are for support libraries that the code uses - they are build internally as projects where necessary or expedient or imported from an external build into the libs folder (and their headers placed in an appropriate folder (e.g. the zlib folder). HtH David
  10. We now understand the bug with drizzle processing where (when using Intersection mode) the output bitmap was 4x or 9x too large with the actual image in the upper left corner. If you use either Standard mode or "Mosaic" mode you should not hit the problem. Keep watching this space. Clear skies, David
  11. Graeme If you could email me** the files and let me know the exact settings you used, I'll attempt to reproduce the problem (**Please use the pm facility on SGL - giving an email address on the open forum is likely to result in you receiving more SPAM than you may have bargained for!! SGL Mods). Cheers Dave
  12. If that's the case it would be useful to be able to have both 2.9 and 3.0+ installed at the same time. Is that doable? I probably will pay for the upgrade, I'm considering right now. Dave
  13. I think I understand why you've decided to charge for the full function version of Sharpcap, if nothing else it must be encroaching on the day job. Nonetheless I am disappointed that a function that was free (Polar Alignment) is now only available to those who are prepared to pay. Dave
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.