# Snapmark feature
**URL:** https://community.openglow.org/t/snapmark-feature/323
**Category:** General Discussions
**Created:** [September 5, 2018, 6:28pm UTC](https://community.openglow.org/t/snapmark-feature/323 "2018-09-05T18:28:07Z")
**Posts on this page:** 12
**Page:** 2
### Author:  [@tim1724](https://community.openglow.org/u/tim1724)
#### Post date: [September 10, 2018, 10:48pm UTC](https://community.openglow.org/t/snapmark-feature/323/21 "2018-09-10T22:48:07Z")
> [@ScottW514](#):
>
> It may just be what they are promising, since many people have reported it being much more accurate than that. Under-promising and over-delivering is a departure for them.
Maybe they’re actually starting to learn?
---
### Author:  [@pingemi](https://community.openglow.org/u/pingemi)
#### Post date: [September 11, 2018, 11:53pm UTC](https://community.openglow.org/t/snapmark-feature/323/22 "2018-09-11T23:53:02Z")
> [@ScottW514](#):
>
> Given that they claim .001" accuracy on the focus, which is achieved with a blurry looking laser spot, they should certainly be able to get that with a sharp image of their fiducial mark.
My guess is you want blurry to get sub-pixel accuracy, similar to how star-trackers work.
---
### Author:  [@ScottW514](https://community.openglow.org/u/ScottW514)
#### Post date: [September 12, 2018, 12:39am UTC](https://community.openglow.org/t/snapmark-feature/323/23 "2018-09-12T00:39:24Z")
I shouldn’t have used ‘blurry’ to describe the height images.
The head pictures used for the height measurement look like this:
While the image itself is in focus and not blurry, the edges of the laser spots are not very well defined, given the nature of the material surface. They claim to get ~.001" accuracy in their measurements from these images.
---
### Author:  [@palmercr](https://community.openglow.org/u/palmercr)
#### Post date: [September 12, 2018, 5:08pm UTC](https://community.openglow.org/t/snapmark-feature/323/24 "2018-09-12T17:08:42Z")
And to be able to track curved surfaces in real time, although I think they removed that from the specs a long time ago.
---
### Author:  [@ScottW514](https://community.openglow.org/u/ScottW514)
#### Post date: [September 13, 2018, 12:56pm UTC](https://community.openglow.org/t/snapmark-feature/323/25 "2018-09-13T12:56:14Z")
They changed it to multi-point.
Another WAG - they may have been hoping to leverage the built in image processing capabilities of the iMX6 SOC. It is a pretty capable device in that regard, and probably explains why they opted for that particular device family instead of much cheaper options. Since the heavy lifting for motion planning is done in the cloud, they could have went with a much less expensive processor.
Sadly, it seems that this major selling point, like many of the other lofty claims, has been walked back.
I’ve been holding out hope that the team over there is just busy with developing GFv2, and that is why there is little progress on the promised features (continuous autofocus, highly accurate visual alignment, auto-alignment for flipped over material, passthrough alignment, auto detection of phones/tablets, etc.).
The low hanging fruit is ignored, and only updates of very little utility seem to creep out. This would lead one to think they are sandbagging, and planning to include all these wonderful enhancements in a new product.
Then, they go and do something like the autofocus speed up. I don’t seem to recall any torch bearing mobs storming GF HQ because the autofocus wasn’t fast enough. So, why expend developer time on it? And why roll it out in such a haphazard way that it ends up taxing your already overworked support staff, and further damaging your shaky QA reputation?
To be a fly on the wall in that organization.
BTW - it looks like shortly after [we chatted about their mixed Glassdoor reviews](https://community.openglow.org/t/openglow-prototype-2-schematics/255/7), there are two new reviews up there ([this one](https://www.glassdoor.com/Reviews/Employee-Review-Glowforge-RVW22064583.htm) and [this one](https://www.glassdoor.com/Reviews/Employee-Review-Glowforge-RVW22063549.htm), both dated Aug 30) that look suspiciously like they were written by a marketing person.
---
### Author:  [@motocoder](https://community.openglow.org/u/motocoder)
#### Post date: [September 13, 2018, 1:34pm UTC](https://community.openglow.org/t/snapmark-feature/323/26 "2018-09-13T13:34:02Z")
> [@ScottW514](#):
>
> BTW - it looks like shortly after [we chatted about their mixed Glassdoor reviews](https://community.openglow.org/t/openglow-prototype-2-schematics/255/7), there are two new reviews up there ([this one](https://www.glassdoor.com/Reviews/Employee-Review-Glowforge-RVW22064583.htm) and [this one](https://www.glassdoor.com/Reviews/Employee-Review-Glowforge-RVW22063549.htm), both dated Aug 30) that look suspiciously like they were written by a marketing person.
No doubt in my mind that someone there is reading this site.
---
### Author:  [@pdobrien](https://community.openglow.org/u/pdobrien)
#### Post date: [September 14, 2018, 3:26pm UTC](https://community.openglow.org/t/snapmark-feature/323/27 "2018-09-14T15:26:16Z")
> I’ve been holding out hope that the team over there is just busy with developing GFv2, and that is why there is little progress on the promised features (continuous autofocus, highly accurate visual alignment, auto-alignment for flipped over material, passthrough alignment, auto detection of phones/tablets, etc.).
I would think it’s premature to start developing new hardware when they haven’t even gotten the first one right (or even released, in the case of the air filter.) But that seems to be their standard procedure, so who knows?
> The low hanging fruit is ignored, and only updates of very little utility seem to creep out. This would lead one to think they are sandbagging, and planning to include all these wonderful enhancements in a new product.
They’ll have a riot on their hands if they do this. But then again, pissed off customers don’t seem to bother them.
> Then, they go and do something like the autofocus speed up. I don’t seem to recall any torch bearing mobs storming GF HQ because the autofocus wasn’t fast enough.
They weren’t. I imagine this was some employee’s big idea for the month, and when you have no big improvements to report, you blow small improvements out of proportion. This enhancement would have taken an experienced coder all of a few hours to implement and test.
> So, why expend developer time on it? And why roll it out in such a haphazard way that it ends up taxing your already overworked support staff, and further damaging your shaky QA reputation?
Here’s my take on it: they have an incredibly inexperienced team trying to do some very hard things. Dan has prioritized hiring a young and diverse (and presumably inexpensive) workforce over hiring an experienced one, and it shows. Look how long it’s taken to get to this point (minimally functional product, no real enhancements since launch, long list of unfulfilled promises.) Compare that to what one guy has been able to do with a few months of spare time here. Imagine where they’d be if Glowforge had just hired a half dozen @ScottW514’s to start with.
> BTW - it looks like shortly after [we chatted about their mixed Glassdoor reviews](https://community.openglow.org/t/openglow-prototype-2-schematics/255/7), there are two new reviews up there ([this one](https://www.glassdoor.com/Reviews/Employee-Review-Glowforge-RVW22064583.htm) and [this one](https://www.glassdoor.com/Reviews/Employee-Review-Glowforge-RVW22063549.htm), both dated Aug 30) that look suspiciously like they were written by a marketing person.
Glassdoor is notorious for looking the other way in exchange for cash when HR posts shill reviews.
And the reports of a strong top-down management culture are more evidence of the inexperience of the team - it’s a common mistake made with young, inexperienced managers.
---
### Author:  [@bdm](https://community.openglow.org/u/bdm)
#### Post date: [September 14, 2018, 10:59pm UTC](https://community.openglow.org/t/snapmark-feature/323/28 "2018-09-14T22:59:41Z")
> [@pdobrien](#):
>
> But then again, pissed off customers don’t seem to bother them.
IIRC they picked up a bunch more venture capital so it would seem they don’t need to care… and if anyone was worried about how the users feel about the ‘Forge they would only have to visit the Joy-filled(\*) forums to see how glowing the praise is
(\*) Joy-filled as in Compulsion Games’ ‘We Happy Few’
---
### Author:  [@ScottW514](https://community.openglow.org/u/ScottW514)
#### Post date: [September 15, 2018, 3:21am UTC](https://community.openglow.org/t/snapmark-feature/323/29 "2018-09-15T03:21:09Z")
> [@bdm](#):
>
> IIRC they picked up a bunch more venture capital so it would seem they don’t need to care
I find it unlikely that an investor would be interested in giving more money just to keep them afloat while they try and finish the product they already sold, which lends weight to the “GFv2” theory.
The other interesting development is the claim that they are now [sold out](https://community.glowforge.com/t/basic-pro-sold-out-right-now/29311) due to demand.
This is fishy.
Either they shut down the US factory too soon and are having problems getting their new [Guadalajara factory](https://community.glowforge.com/t/international-shipping-update-september-2018/28913) up and running, or they stopped production on the old ones in preparation for a launch of the new ones.
The former would be a classic Glowforge planning fiasco. The latter would be a refreshing change if the new product launches without a hitch. Sadly, I fully expect it to be the former.
Whatever it is, it will be interesting to see how long they are without inventory (and sales revenue), especially with the Dremel launch coming up.
---
### Author:  [@palmercr](https://community.openglow.org/u/palmercr)
#### Post date: [September 15, 2018, 8:37am UTC](https://community.openglow.org/t/snapmark-feature/323/30 "2018-09-15T08:37:15Z")
They are still selling the plus model, so they do have some revenue.
---
### Author:  [@MH1944](https://community.openglow.org/u/MH1944)
#### Post date: [September 16, 2018, 6:46pm UTC](https://community.openglow.org/t/snapmark-feature/323/31 "2018-09-16T18:46:07Z")
> [@ScottW514](#):
>
> The low hanging fruit is ignored, and only updates of very little utility seem to creep out. This would lead one to think they are sandbagging, and planning to include all these wonderful enhancements in a new product.
> Blockquote
I use Onshape (CAD cloud) and LightBurn (laser software) and follow both forums. It’s interesting to see how many features both companies have implemented and how responsive they are to their forum communities. Onshape introduces a handful of new features every 3-4 weeks and will often push minor fixes within a few hours of 1st report. They maintain an user-driven list of feature requests and prioritize implementation partly in response to user votes. Anyone can see the requests, how many votes it has, and make comments. When bugs are mentioned one of the developers will usually pop into the thread and give some explanation as to the cause and when a fix might be expected. Very open and above board and a _huge_ contrast to GF’s reputed “hopper”.
Lightburn was started by one guy to improve on the RDWorks software that folks like Russ Sadler use on their Ruida-controlled lasers as well as a bunch of the DIY lasers. By my count he has had 13 software updates since January this year. He seems to have no problem acknowledging bugs, often explains what caused them, and usually has them fixed with in anywhere from a day to a week.
Glowforge could learn a lot from either company.
---
### Author:  [@ScottW514](https://community.openglow.org/u/ScottW514)
#### Post date: [September 18, 2018, 8:28pm UTC](https://community.openglow.org/t/snapmark-feature/323/32 "2018-09-18T20:28:58Z")
So, I finally received the Snapmark® feature in the GFUI.
Obviously, without the cameras working, it isn’t functional with the OpenGlow.
Did notice, when you scan for the fiduciary marks, it sends a new option with the command:
```auto
{"id":27052616,"action_type":"lid_image","machine_serial":"DMQ-793","status":"ready","settings":{"IMjq":80}}
```
I haven’t seen the `IMjq` setting before. I wonder if it is specifying the JPEG compression quality.
I’ll see if I can fool it into thinking there are marks on there, and then find out if there is anything new in the commands it sends to take the up-close picture with the head camera (at least, I assume it takes a closeup with the head cam…).
[Previous page](https://community.openglow.org/t/snapmark-feature/323.md?page=1)