Mac OS X Lion Discussion


Recommended Posts

I was actually thinking we might have had a new build by now. I'm hoping for another one in early April.

Interestingly enough, though, I just last night finally got an e-mail response regarding the bug reports I submitted at least three weeks ago.

Apparently we may be seeing a GM release of some kind soon ...

http://techcrunch.com/2011/03/25/os-x-lion-gm/

Specifically, Apple is gearing up to deploy an OS X Lion update to developers that they may be classifying as the ?GM1? release, we?ve heard. ?GM? or ?Golden Master? is a title reserved for software that is complete. But from what we?ve heard, this is only the initial Golden Master candidate. In other words, don?t get too excited just yet.

They actually answer you if you submit bugs? That never happened to me :p

I, for one, am not surprised we haven?t seen any build yet. After the first public build, they got a lot of feed-back, thus have a lot to fix. I?m hoping for a new build in April...

It was just a generic canned response. They said all the bugs I submitted had been submitted before so they already knew about them. But that's a good thing, it seems to imply the next build made public should take care of them.

Apparently we may be seeing a GM release of some kind soon ...

http://techcrunch.com/2011/03/25/os-x-lion-gm/

You know, I don't recall Leopard or Snow Leopard having anything other than the GM called a GM#. Interesting, I'd imagine it's Apple's terminology for a RC.

What do you mean, you don?t what? You don?t have an account in the Mac App Store? You don?t have a credit card? You don?t link your credit card number to your account? You don?t download anything from the store?

Same. This is the first build that got in the hands of thousands of people. They will get a bunch of comments, bug reports, complaints, and everything.

On one side, they need to stick to their roadmap, and on another side they need to sort out all the feed-back, then they need to address the major problems reported. Finally, they need to compile and test everything that has been added to see if it actually works better.

Lion?s developer build was released like yesterday. They need to breathe for a bit and maybe in April we?ll get another build.

Accounts at the MAS/iTunes/ADC are *identical* - you can use the same credentials for all three. And you don't need a credit card (for the simple reason that there are items in all three places that are free) - I have an account - with no credit card - that I use for all three.

NovaBench (benchmarking utility) is among the free Leo/SL/Lion-ready MAS apps.

After using my iPad 2 for a day I'm completely blown away by the iOS version of iTunes. It's so incredibly smooth: Scrolling without so much as a hiccup, advanced animations everywhere and overall the interface is just amazing. The biggest issues we have with the application are non-existent there, it's iTunes done right.

If anything Apple should rewrite iTunes for Mac OS X in its image.

After using my iPad 2 for a day I'm completely blown away by the iOS version of iTunes. It's so incredibly smooth: Scrolling without so much as a hiccup, advanced animations everywhere and overall the interface is just amazing. The biggest issues we have with the application are non-existent there, it's iTunes done right.

If anything Apple should rewrite iTunes for Mac OS X in its image.

Yeah iTunes is pretty amazing on my iPad 2 as well, the iPad 2 is by far the best tablet out there.

Is the developer preview stable enough to use as a primary operating system? I'm just a user; I browse the web, listen to itunes, chat via adium.

I didn't have any major issues with it, but I still wouldn't recommend using it day-to-day. Although if you like using beta software, I'd certainly suggest you try it out.

Well Adium for one didn't really work that well for me on Mac OS X Lion.

Because it worked well on Snow Leopard? :laugh:

I get a few crashes here and there and a buuuuuuunch of bugs.

About iTunes 11, it WILL happen in September, and I?m ready to bet my right hand that it?ll be rewritten completely in Cocoa/Objective-C/64-bit support, feature a new optimized Windows 7 interface that fits Aero as much as Safari does, remember what song you were playing last and where you where in your library after closing it (well this last one isn?t hard to predict, it?s one of Lion?s key features after all)

Otherwise they?re getting really annoying with their useless iTunes features that add bloat everywhere.

What exactly is it people expect to gain from iTunes re-written in Cocoa?

Here's the current list of stuff iTunes links against:

It seems to me what people want is an overhaul of the UI and possibly the compartmentalization of some features. I don't think we're going to get them for purely business reasons: having the iTunes store (etc) built into iTunes forces it in your face much better than having it as a separate application does. And it's not like Apple couldn't build a complete UI-abortion with Cocoa alone.

	@executable_path/../Frameworks/iPodUpdater.framework/Versions/A/iPodUpdater (compatibility version 1.0.0, current version 1.0.0)
	/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3)
	/System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook (compatibility version 1.0.0, current version 883.0.0)
	/System/Library/Frameworks/AGL.framework/Versions/A/AGL (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 38.0.0)
	/System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 152.0.0)
	/System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 44.0.0)
	/System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration (compatibility version 1.0.0, current version 293.5.0)
	/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
	/System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime (compatibility version 1.0.0, current version 1742.0.0)
	/System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 37594.0.0)
	/System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore (compatibility version 1.2.0, current version 1.6.2)
	/System/Library/PrivateFrameworks/iPod.framework/Versions/A/iPod (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate (compatibility version 1.0.0, current version 4.0.0)
	/System/Library/Frameworks/QTKit.framework/Versions/A/QTKit (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 751.29.0)
	/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 15.0.0)
	/System/Library/Frameworks/WebKit.framework/Versions/A/WebKit (compatibility version 1.0.0, current version 533.16.0)
	/System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore (compatibility version 1.0.0, current version 533.13.0)
	/usr/lib/libicucore.A.dylib (compatibility version 1.0.0, current version 40.0.0)
	/System/Library/Frameworks/Quartz.framework/Versions/A/Quartz (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit (compatibility version 1.0.0, current version 1.0.0)
	@loader_path/libgnsdk_musicid.1.8.2.dylib (compatibility version 1.8.2, current version 1.8.2)
	@loader_path/libgnsdk_sdkmanager.1.8.2.dylib (compatibility version 1.8.2, current version 1.8.2)
	@loader_path/libgnsdk_submit.1.8.2.dylib (compatibility version 1.8.2, current version 1.8.2)
	@loader_path/libgnsdk_dsp.1.8.2.dylib (compatibility version 1.8.2, current version 1.8.2)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
	/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 103.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0)
	/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 227.0.0)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 550.29.0)
	/System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo (compatibility version 1.2.0, current version 1.6.1)
	/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1038.35.0)

Note that iTunes is already using Cocoa (and CoreAudio/video, appkit, webkit, etc) and that everyone's favorite examples of Cocoa applications link against similar libraries (ie: safari links against Carbon, libgcc/libogjc/etc, securityframework, etc) -- Why the concerns about the framework when what really matters is the user interface and performance? For all I care they could write the damn thing with QT and Java if it'd worked better than what we have now.

What exactly is it people expect to gain from iTunes re-written in Cocoa?

Here's the current list of stuff iTunes links against:

It seems to me what people want is an overhaul of the UI and possibly the compartmentalization of some features. I don't think we're going to get them for purely business reasons: having the iTunes store (etc) built into iTunes forces it in your face much better than having it as a separate application does. And it's not like Apple couldn't build a complete UI-abortion with Cocoa alone.

Note that iTunes is already using Cocoa (and CoreAudio/video, appkit, webkit, etc) and that everyone's favorite examples of Cocoa applications link against similar libraries (ie: safari links against Carbon, libgcc/libogjc/etc, securityframework, etc) -- Why the concerns about the framework when what really matters is the user interface and performance? For all I care they could write the damn thing with QT and Java if it'd worked better than what we have now.

There is more to the 'move to Cocoa than the obvious; I'd say there will be a move to possibly AV Foundation or at least QtKit will be sit ontop of AV Foundation which will be a bare bones basic framework. Cocoa allows 64bitness which includes better ASLR support, access to more registers, gaining benefits of GDC, compiler better optimisations etc.

I'd love to see changes happen but it all comes back to Apple and whether they consider its worth their while in the long run.

What exactly is it people expect to gain from iTunes re-written in Cocoa?

Here's the current list of stuff iTunes links against:

It seems to me what people want is an overhaul of the UI and possibly the compartmentalization of some features. I don't think we're going to get them for purely business reasons: having the iTunes store (etc) built into iTunes forces it in your face much better than having it as a separate application does. And it's not like Apple couldn't build a complete UI-abortion with Cocoa alone.

Note that iTunes is already using Cocoa (and CoreAudio/video, appkit, webkit, etc) and that everyone's favorite examples of Cocoa applications link against similar libraries (ie: safari links against Carbon, libgcc/libogjc/etc, securityframework, etc) -- Why the concerns about the framework when what really matters is the user interface and performance? For all I care they could write the damn thing with QT and Java if it'd worked better than what we have now.

iTunes just doesn't fit in with other Mac OS X applications. It performs poorly, during on-the-fly encoding to 128 kbps AAC to my iPod and iPad it doesn't utilize that fact I have a Quad-Core processor with HT, the entire application slows to a crawl during initial syncing with devices, Preferences have to be applied with a "OK" or "Cancel" button not standard for Mac OS X, scrolling is much much slower than in other applications, it doesn't utilize Core Animation, etc.

While I'm not saying it's all the fault of Carbon alone there does seem to be a trend going on where Carbon applications feel very different from their Cocoa counterparts. QuickTime used to be Carbon as well, we saw a huge improvement in interface performance and overall look-'n'-feel when Apple rewrote it in Cocoa during Mac OS X Tiger development.

For all I care they could write the damn thing with QT and Java if it'd worked better than what we have now.

Doubtful you'll end up with an application that has a native look-'n'-feel with proper OS service integration. Again, not saying it's impossible, it's just very unlikely looking at every single application for Mac OS X that has been written that way.

iTunes just doesn't fit in with other Mac OS X applications. It performs poorly, during on-the-fly encoding to 128 kbps AAC to my iPod and iPad it doesn't utilize that fact I have a Quad-Core processor with HT, the entire application slows to a crawl during initial syncing with devices, Preferences have to be applied with a "OK" or "Cancel" button not standard for Mac OS X, scrolling is much much slower than in other applications, it doesn't utilize Core Animation, etc.

Use of multiple processors has nothing to do with Cocoa, in fact I'd argue "best" (easiest) way to get access to a lot of cores in a cross platform application isn't to use cocoa. Core animation has nothing to do with scrolling of the nsscroll views, and the "okay/cancel" is also not a cocoa thing, it's a 'bad ui' thing.

All this hammering on "use cocoa" is misguided, it should be "fix the UI issues", "simplify the process <x,y,z>", "improve the handling of libraries of size xxx gb". Simply moving to cocoa won't fix any of those problems: there's nothing to stop Apple from building just as big a turd just because "[[their[code: looks]like]this];" instead of "looking(like(this)));"

I'd say there will be a move to possibly AV Foundation or at least QtKit will be sit ontop of AV Foundation which will be a bare bones basic framework.

iTunes is already using those libraries.

Cocoa allows 64bitness which includes better ASLR support, access to more registers, gaining benefits of GDC, compiler better optimisations etc.

iTunes isn't really the sort of Application which benefits from 64-bit guts. The only thing that iTunes does where it would be noticable is transcoding of audio. If you wanted to look at it as an "Apple is the devil" type of person you might say that transcoding isn't really part of Apple's business: their goals are for you to buy your music from them encoded and for you to buy larger ipods so you don't need to transcode. I'm not arguing that making audio encoding slow is part of some master plan to sell more ipods but it's understandable that this part of the applicaiton just isn't going to make it high on their list of priorities. Simply running more transcodes at once isn't something that is drastically easier in Cocoa than Carbon: it's a fairly easy problem to parallelize.

What sort of compiler optimizations do you think you'd get out using Cocoa that would be unavailable to Carbon? it's not like "gcc -o3" stops working just because you've chosen to link against some different set of libraries. It's already got access to GCD (I'm guessing that's what you mean by GDC) by nature of using CoreFoundation but it doesn't really matter. The majority of what iTunes does isn't CPU bound and it certain isn't going to perform drastically better just because you change the architecture it's targeting. The problems with iTunes aren't in the technology, they're in the design of the application.

I'm not doubting that iTunes will eventually use more Cocoa than it does now, one day, but I am doubtful that any issues people have it it are going to be addressed by a gradual change in technology. If iTunes does get better it'll have to do with revisiting their design decisions and not just because they checked a different box in xcode.

Use of multiple processors has nothing to do with Cocoa, in fact I'd argue "best" (easiest) way to get access to a lot of cores in a cross platform application isn't to use cocoa. Core animation has nothing to do with scrolling of the nsscroll views, and the "okay/cancel" is also not a cocoa thing, it's a 'bad ui' thing.

All this hammering on "use cocoa" is misguided, it should be "fix the UI issues", "simplify the process <x,y,z>", "improve the handling of libraries of size xxx gb". Simply moving to cocoa won't fix any of those problems: there's nothing to stop Apple from building just as big a turd just because "[[their[code: looks]like]this];" instead of "looking(like(this)));"

Hence the reason why I said:

While I'm not saying it's all the fault of Carbon alone there does seem to be a trend going on where Carbon applications feel very different from their Cocoa counterparts.

It's just something you see: Practically all Carbon applications integrate poorly with the OS, suffer from odd non-standard interface quirks and have worse performance than their Cocoa counterparts. As such I think it's fairly logical that people who don't have advanced coding knowledge draw the conclusion that all the issues are directly Carbon related.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • ...but you're Johnny, from Australia?    
    • Glow 26.9 by Razvan Serea Glow provides detailed reporting on every hardware component in your computer, saving you valuable time typically spent searching for CPU, motherboard, RAM, graphics card, and other stats. With Glow, all the information is conveniently presented in one clean interface, allowing you to easily access and review the comprehensive hardware details of your system. Glow provides detailed information on various system aspects, including OS, motherboard, processor, memory, graphics card, storage, network, battery, drivers, and services. The well-organized format ensures easy access to the required information. You can export all the gathered data to a plain text file, facilitating sharing with others for troubleshooting purposes. No installation needed. Just decompress the archive, launch the executable, and access computer-related information. Glow runs on Windows 11 and Windows 10 64-bit versions. Glow 26.9 changelog: New Features The processor hardware detection engine has been significantly enhanced beyond traditional Intel and AMD architectures. Native support is now available for modern platforms such as Apple Silicon (M-Series) and the newly introduced NVIDIA Spark. In addition, all ARM-based processors can now be accurately distinguished between ARM32 and ARM64 architectures, providing precise hardware reporting. This marks a major milestone for Glow's hardware detection capabilities. The RAM manufacturer identification algorithm has been expanded. JEDEC vendor codes for popular brands such as Patriot, PNY, Team Group, GeIL, Lexar (Longsys), and Asgard/Gloway have been integrated into the database. This significantly reduces the likelihood of incorrect or "Unknown Manufacturer" results and improves overall hardware detection accuracy. New Public IP Address and Internet Service Provider (ISP) features have been added to the Network section. To ensure reliability, this information is retrieved from the trusted service ipwho.is. When Hiding Mode is enabled, no requests are sent and these features remain hidden, as they may expose sensitive information. The search engine used in the Installed Drivers, Installed Services, and Installed Applications sections has been enhanced. You can now perform more flexible and accurate searches using initials, partial matches, and loosely arranged character sequences. The TS Preloader loading bar has been rebuilt using our modern TS Custom Controls graphics library, developed entirely in-house. As a result of this infrastructure upgrade, the loading bar now features smooth rendering and rounded corners that align with the visual style of Windows 11. [TS Updater] A new validation algorithm has been added to check whether the target application is currently running before the update process begins. Bug Fixes Resolved a condition that could prevent TS Preloader from shutting down safely during rare application crash scenarios. Fixed a text alignment issue in the Network section affecting the display of DNS addresses. Alignment is now rendered correctly. [TS Updater] Fixed an issue that could prevent the updated application's executable "*.exe" file from being located after the update process. [TS Updater] Fixed a bug that could leave outdated "*.sha256" files in the application directory after an update. [TS Updater] Fixed a rare issue that could cause subfolders to be moved into the root directory after an update. [TS Updater] Fixed an issue during the first launch that could cause flickering and a temporary white window appearance due to Windows Defender interactions. Changes A small improvement has been made to the internet connectivity detection algorithm. Connectivity checks are now performed in the background with minimal impact on the user interface thread. The keyboard shortcuts in the top menu have been reorganized and simplified to provide a consistent experience across all Türkaysoft applications and to avoid potential conflicts with standard Windows shortcuts. The TS Preloader splash image has been updated with a Türkiye-themed stadium design to celebrate Türkiye's qualification for the 2026 FIFA World Cup—its first appearance in 24 years. Congratulations, Türkiye! The TS Custom Controls module has been updated to version 26.6, delivering improved stability and a more polished visual appearance. [TS Updater] The application icon has been redesigned to provide a more modern and refined look. Note: Always unzip the program before using it. Otherwise you may get an error. Download: Glow 26.9 | 1.8 MB (Open Source) Links: Glow Homepage | Screenshot | Github Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • DWARF mini review: the world's smallest smart telescope for night and day sky captures by Steven Parker DWARFLAB reached out to me asking if I was interested in checking out the DWARF mini, which is a portable astronomy telescope designed for amateur astronomers. Why do I say it's for amateurs? Well, for starters, it's not what you'd call "high end"; it's more of a professional-grade starting point for amateurs serious about capturing what's up there in our night and day skies. A typical amateur astronomer is most likely thousands of dollars deep into the hobby, and I will make no claims that this DWARF mini (at a fraction of the cost) could replace it all, okay? Well, if you read on, it will be clearer what I am trying to convey. Disclosure: DWARFLAB provided a free sample without any editorial input or review pre-approval. I have always been interested in looking up and observing the night sky. I see satellites crossing the sky above my garden most nights, and I am always looking at the moon. Yeah, I have a 200MP camera on my phone, but at 200X zoom, AI takes over and makes the pretty moon pictures that I snap, the DWARF mini does not, you get an actual true picture of what you can barely see with the naked eye. Before we start, let's share the highlights of the DWARF mini in bite-sized format: Pocket-Sized & Ultra-Lightweight Weighing just 1.85 lbs (840g), the DWARF mini easily fits into a backpack or large pocket. Its all-in-one, compact design makes it the ultimate grab-and-go digital telescope for hiking, camping, or traveling to dark-sky locations. Intuitive App Control & Built-in Sky Atlas Go from unboxing to your first shot in just 3 minutes! The DWARFLAB App provides a seamless experience with an interactive star map. Simply select your target and start exploring without the steep learning curve of traditional setups. Auto GOTO & 360° Pivot Freedom Enjoy pinpoint automated tracking with full 360° rotation. Powered by a high-sensitivity Sony IMX662 sensor (1/2.8-inch, 2.9μm pixels), it captures amazing, low-noise astro details, bringing faint nebulas and star clusters to life with stunning clarity. Pro-Level EQ Mode & Long Exposure Unlock advanced deep-space imaging with Equatorial (EQ) Mode. Supporting impressive single-frame exposures up to 90 seconds and featuring built-in light pollution filters, it easily cuts through city glow to reveal intricate celestial structures. Smart Cloud Processing & All-Ages Fun Effortlessly enhance your raw data with integrated cloud processing for professional-grade results. Perfect for beginners, kids, and adults, this telescope makes exploring and sharing the wonders of the universe an exciting, family-friendly adventure. The packaging is a pretty minimal affair with the outer box opening like a flap to reveal the plastic mould of the DWARF mini sitting in it. Below, the Sun filter, charging cable, cleaning cloth, and documentation can be found. DWARFLAB also provided a Mini Hydraulic Tripod ($89.99), and I highly recommend getting it if you plan on purchasing the DWARF mini, as it fully supports the motorized tracking feature of the telescope; plus, at 840g, the weight of the telescope, you will need a tripod that supports more than the weight of a smartphone anyway. What's in the box DWARF Mini Smart Telescope × 1 Sun Filter x 1 Type-C to Type-C Cord x 1 Cleaning Cloth x 1 User Guide With that out of the way, here are the full specs: DWARF mini Dimensions (DWH): 60.70 mm x 100.38 × 183.61 (2.39" x 3.95" x 7.23") Weight: 840g (1.85lbs) Aperture diameter: 30 mm (telephoto), 3.4 mm (wide angle) Image Sensor: SONY IMX662 1/2.8" (Telephoto) OmniVision OS02K10 1/2.8" (Wide-angle) Focal length: 150 mm (telephoto), 6.7 mm (wide-angle) Equivalent focal length: 1016 mm (telephoto), 45 mm (wide-angle) Shutter Speed: Tele - 1/10000-90s, Wide - 1/10000-30s Maximum exposure time: 90s (telephoto & wide-angle), Both in EQ mode Rotation range: Lens: 225°, Base: 360° Effective Pixels: 2.07M Maximum Resolution: 1920 × 1080 (Telephoto & Wide-angle) Built-in filters: Astro, Dark, Duo-Band (Telephoto), Astro (Wide-angle) Output: JPG, FITS, TIFF, MP4 Shooting Mode: Photos, Videos, Astronomy, Burst Shooting, Time-lapse Photography Storage: 64 GB Battery: Built-in 7000 mAh, supports external USB charging Charging Port: Type-C NPU: 1 TOPS Features: WiFi, NFC NFC One-Touch Connection Astronomy Post-Processing/Appointment Shooting/Astronomy Mosaic Wi-Fi Transmission Range: 15m (open environment) Color: Black Compatibility: iOS & Android smartphones/tablets Warranty: 2-years (24-months) MSRP: $399 Design Charge port On/off button Lens On the DWARF mini itself, it is a pretty minimal affair. On one side, there is a Type-C USB port to charge the non-removable 7000 mAh battery, and on the other side, a large button to power on or off the telescope. The button is flanked by an LED that is green when connected via the DWARFLAB app, or lights up red when being powered off. Below the button, there are four LEDs that indicate battery power. The DWARF mini does not have any sharp edges as all sides are rounded off; it has a good heft to it, but the weight of it feels quite balanced in the hand, so it isn't top or bottom-heavy. On the front there is the DWARFLAB logo which is quite small and there are no other markings on it. The tripod offers full 360° rotation of the motorized base, which allows for tracking for the time-lapse mode, but also for the 90-second captures of nearer objects in the sky, such as the Sun or the moon. Usage To get started, simply power on the DWARF mini and open the DWARFLAB app, tap on Connect, and it will scan for the DWARF mini over the Wi-Fi network. The device supports both 2.4 GHz and 5 GHz Wi-Fi, as well as Bluetooth for discovery, so connection issues were minimal in my experience with it. As previously noted in the specs, the DWARF mini will stay connected with a phone or tablet up to 15 meters in an open environment, such as a backyard. Lighting status Powering on: The green circular light will rotate and breathe in turn Powering off: The red circular light is gradually extinguished Connecting: Green light strip rotating Connected: Green light strip solid/always on 4 lights 1= 0-25%, 2= 25-50%, 3= 50-75%, 4= 75-100% battery power To view the full lighting status, such as tracking mode and connection failure, you can check the user guide on the official DWARFLAB page. DWARFLAB app Above, you can see the steps undertaken to connect the DWARFLAB app to my Galaxy S26 Ultra. Weirdly, I got an alert that a firmware update failed to get uploaded to the DWARF mini the first time, but upon retrying, it worked. Then place the DWARF mini outside, make sure your smartphone or tablet is connected to it, and then head back inside, because you can manage it from the comfort of your home. Simply enter the Atlas tab in the app and search for what you want to capture, and then tap on the camera icon; the DWARF mini will then attempt to track the object and give you a live view right on your connected device. Results I've had the DWARF mini since April, but even though my garden is south-facing, I had a lot of trouble trying to capture a good image of the moon. In the end, it was possible after I took it with me on a trip to my parents in Southend, UK, at the end of May. Here is a capture of the moon, resulting from 20 stacked images over a 90-second exposure. What you are seeing here is not AI-assisted. A good example of what I mean is the latest flagships with their 200MP cameras claiming to capture things like closeups of the moon, and while they are not as good as the above example on the DWARF mini, the resulting image on smartphones is actually AI-assisted above 30X zoom. Here is an example of a similar shot at the moon at 200X zoom using an HONOR Magic8 Pro. The difference is clear. Next, here we have a shot of the daytime moon. Here is a shot of Arcturus, the red giant star, which is the fourth brightest in the night sky. As previously mentioned, it could be a bit clearer, but clouds passing in front of it muddied the shot a bit. The Sun The DWARF mini also ships with a sun filter, meaning you can take great shots of the sun as well. Tracking Sun Resulting (stacked) shot Live zoom The pictures themselves are limited to Full HD, and some of the examples actually came out in HD (1280x720), but this is because the standard telescopic result is in 720p while "Wide" is in 1080p. Above you can see how in the app the Sun is tracked, the resulting capture, and Live zoom. I have only scratched the surface of what is possible with this telescope; I found several examples online of shots of the Milky Way, among others, such as nebulae and galaxies. All of this requires patience and knowledge, although if you know what you are looking for, simply enter it in the Atlas tab in the DWARFLAB app, tap the camera icon, and the telescope will attempt to track it. Conclusion The good The DWARF mini definitely places itself in a price point that makes astrology accessible to anyone looking to get started in the hobby. Say you want to have a closer look at the moon, simply enter it in the Atlas, and the Live view also lets you zoom in and snap pictures. The bad Some issues I came across while operating the DWARF mini were that it sometimes failed to connect unless I held my smartphone right next to it, and finding and tracking sometimes took several attempts to get it calibrated. I discovered that it helped if I sort of positioned and pointed the telescope in the general area it was supposed to detect, but this obviously wouldn't work with objects you can't see with the naked eye; more testing is required for that. Another bit of advice is to ensure that the lens is clean. While making the examples of live zooming on the sun, I discovered that the telescope lens and sun filter were not completely clean, and only after cleaning with a microfiber cloth was I able to get a decent shot of the sun. Where to buy and a coupon Okay, $399 is not cheap for a side hobby, but nor is a $1,500 smartphone flagship that you'll most likely have for a couple of years. This is a one-time entrance into astrology, and it won't become obsolete in one year like a smartphone. It's a thumbs up from me. The DWARF mini is available to buy right now in the U.S. and U.K. at the links below. DWARF mini for $399 on the official site DWARF mini for $399 on Amazon U.S. Use the NEOWIN5OFF coupon code for an additional 5% off at checkout (expires June 21) As an Amazon Associate, I earn from qualifying purchases.
    • Adobe Acrobat Reader Dis Continued
    • The name, you mean? If so, it's actually the objects common name. There's another one called NGC 7293 which is also known as Helix Nebula (because we're looking at a helix structure top down) but other times also known as the Eye of God. You'll understand when you see it
  • Recent Achievements

    • One Month Later
      lamborghiniv10 earned a badge
      One Month Later
    • Week One Done
      lamborghiniv10 earned a badge
      Week One Done
    • Reacting Well
      X-No-file earned a badge
      Reacting Well
    • One Month Later
      pestcontrol46 earned a badge
      One Month Later
    • Week One Done
      pestcontrol46 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      504
    2. 2
      PsYcHoKiLLa
      270
    3. 3
      Skyfrog
      75
    4. 4
      +Edouard
      71
    5. 5
      FloatingFatMan
      69
  • Tell a friend

    Love Neowin? Tell a friend!