Chase Goldman

Yeah. That is the way to go if you find the speaker has too much delay using its own built in BT receiver.

Unfortunately, you appear to be mixing apples and oranges. Not surprising since the Bluetooth standard is generally a just a confusing jumble of technical jargon for the average consumer/end user to interpret, manufacturers of BT hardware provide woefully inadequate, ambiguous, imprecise, or incomplete descriptions of equipment features and the BT "standard" itself even presents technical challenges and incompatibilities for the manufacturer trying to incorporate the BT compliant technology into their equipment. BT 5 does not affect latency it is just the latest standard that supports the family of latest BT features, control protocols, codecs, and hardware that could be used. It is up to the audio equipment manufacturer to decide what subset of the BT 5 supported features (such as low latency codecs like APTX LL) to include in their BT 5 compliant equipment. It is the codec (hardware/soft combo that encodes/compresses/transmits/decodes the wireless audio) that affects latency. So BT 5 is not "faster" than 4.2 and BT 5 does not determine latency, but it is true that it theoretically can incorporate lower latency codecs that may not be compatible with the BT 4.2 standard. BT 5 is not a codec like APTX LL it just supports APTX LL, but the fact is BT 4.2 also supported APTX LL. The device itself has to have the proprietary hardware (APTX enabling chipset) to support the low latency codes. If you do a deep dive into the reviews you'll see folks complaining about high latency that in this case manifests in video being out of sync with the wirelessly transmitted audio to the speaker. This latency issue is not just an android issue BTW. Surprised you took the leap on the purchase despite asking for feedback ostensibly before purchase. Some folks find the latency of even APTX low latency wireless (40 ms) to be intolerable others have no problem with delays up to 1/4 second (250 ms) which is likely where this speaker falls out. Anyway, good luck, hope it works out...maybe you will be able to deal with it and it will be a non issue for you as the price is right at $20.

The Avantree Torus neck speaker discussed below and in other threads (just search the forum on Avantree Torus) is a popular choice for GPX 6000 users as, unlike yours, it supports APTX low latency AND you have the option to use the built in earbuds for specific situations. However, unlike yours, it is not waterproof but being wireless, it can be worn on the inside of a hooded rain jacket. Yours is a lot less expensive, but I think you will find the lack of APTX Low Latency compatibility (which is the standard Minelab relies on for the 6000 and also Equinox to remove excessive audio delay present in most non-low-latency bluetooth speakers and headphones/earbuds) to present an intolerable delay that will affect your ability to center on and pinpoint targets.

Looking forward to the finished product, Steve. Meanwhile, nice homebrew rig, Dave, can't wait to hear how it does on your next trip down south.

Set Salt sensitivity as high as you can for stability (less chatter). If you set it lower to gain stability the trade off is loss of sensitivity to small gold (or mid-conductive targets at TID 30 that now look like salt as far as the detector salt sensitvity filter is concerned).

Same here. Supposed to long press the pinpoint button, but could never get Fd to show up. Must be missing something. Love the added features/functions but the obscure icon driven/multi-function menu system is getting a little unwieldy (non-intuitive) with all these "secret" key press combinations to activate/adjust these features. The seldom used ones are hard to recall in the field. Getting to the point where I need to keep notes on my phone or at least a laminated cheat sheet.

We are not XP so not much we can do about it, so yeah, you’re effectively just complaining. But that’s ok. Maybe Gary Black or someone from XP will read your disappointment and bring it back to XP. I am not personally seeing a groundswell of dissatisfaction with D2 other than coil ear wear , so if XP is only hearing a few people complain about pinpointer issues and lack of coils or a future update schedule and it is not hurting sales, not likely to see a change in behavior. I have both Legend and Deus 2 (and Equinox) they are all 3 excellent overall machines and each have unique strengths that I exploit for different situations. So if you want to vote with your wallet and get a Legend and you highly value customer focus, I think you will like Legend. I’m personally happy with 0.71 - it seems like they were responding quickly to issues with ver 0.6 and features requested in the wake of the initial launch of the D2 (e.g, big TID digits), a 95+% solution missing only Mono gold field, small elliptical (I have no use for the 11x13) and finally releasing their companion app. The PP connectivity comes and goes without rhyme or reason.

To be clear, never said it was an excuse, I wanted to make sure people knew "them" was a one guy operation to put order fulfillment times in perspective. I stated clearly in my post that even one person operations need to at least communicate early and often what is going on or lose sales, totally agree on that point. That means when you hang up a shingle as a business run by one person or with 1000 employees you had better at least be answering customer emails quickly whether you are on vacation, sick, or whatever. Especially true for one person ops when quick turnarounds are difficult if product demand surges or when you're sick, on vacation etc. All the more reason to, if anything, communicate MORE frequently than bigger businesses because you will more likely be in a situation where your ability to supply product doesn't meet the expectations of those used to dealing with bigger operations. We have a few one guy business that regularly advertise and post in this forum and who have excellent customer focus and comms. It can be done by one person, provided you are committed to the customer and, thereby, commited to the success of your business.

"Them" is a one-guy operation, not Kellyco, so folks should set their expectations accordingly oturnaround time. On the flip side, if you do decide to embark on a single-handed business model, this thread is a good case study of how you can quickly lose sales simply because you are not communicating well with existing and potential customers.

Providing and uploading a video of the behavior, if possible, would also be helpful.

Noise could be one of several sources - Ground noise (are you sure you are GB properly?), EMI (did you try frequency shift noise cancel), mineralization in the ground/ferrous fragments - so what are your filter settings (Discrimination, bottle cap, and silencer)? For us to help you, it's best for you to start with your custom program. What factory program did you use as your starting point? Then go through your custom settings. A little background on your experience with detectors and detecting would help us understand if there are any general/basic conceptual issues associated with detector setup you may be struggling with, as well. Standing by to help...

I've said it before...XP needs to provide a single (mono) frequency variant of Goldfield (like they did with the D2 discrimination Programs), and preferably a small, high frequency/FMF compatible elliptical coil. Of course, if they manage to pull that off, there really is not much reason for the D1 and Orx to exist (other than 0RX price point due to its limited features/settings). So there's that...

They will once they get to final release (except for any post 1.X version that contained a major bug). As explained in the previous post, any version less than 1.0 is not final release. We're still technically beta testers until 1.0. Not really ideal, but that's the way it is, XP needed the broader user base beyond their initial testers to really shake this out. SInce it's not final release yet, they are going to limit how far you can roll back at this time to ensure you get no further back than the last stable version without major known bugs (i.e., 0.6 version (3-11-22)). At least you can roll back to that version now from 0.71. I DO know that I was pretty upset when the "broken" 0.6 version was released in March (also upset they lost software configuration/version control and released no less than 3 "0.6" versions without using minor revision numbers to alert users but that's a separate story). Perhaps they are waiting for the Go Detect app to be released world wide before they go to Ver 1.0, who knows...

I had a very similar experience with this baby...

Happy. Now, waiting for that LG24 Coil...

I'd still be happy with silver any day regardless of the junk ice.

Interesting, because from what I have found (see below) Airpods are definitely not low latency - not even close. Just to confirm, I take it you do not get the "+" symbol next to the Bluetooth (BT) symbol on your Vanquish when your Airpods are paired to the Vanquish. Latency/delay as little as 15ms is noticeable by some detectorists-most proprietary, dedicated detector wireless audio systems (e.g., Minelab Wi-Max, Garrett Z-Lynk, Nokta Makro non-BT wireless, Quest Wireless, and probably the XP Deus/Orx/Deus 2 wireless audio system) have this small level of delay. Note that Bluetooth APTX LL latency tops out at about 40 ms and works well for detecting, though a small number of detectorists find even this level of latency bothersome. Non-LL APTX BT has a latency of 60 to 70 ms and I personally find that to be basically unusable. Most BT protocols (including AAC used for Airpods) can lag as much as 150 to 200 ms. I can't imagine this level of latency being usable for most detectorists. I found the following off the web regarding latency for 1st through 3rd gen airpods: The first-generation AirPods, which use Apple’s W1 chip, measure latency of 274 ms. Second-generation AirPods, released earlier this year [2019] and powered by Apple’s newer H1 chip, drop the latency to 178 ms. And AirPods Pro, which use the same H1 chip, are even better at 144 ms. The 130 ms improvement from the first-generation AirPods to the AirPods Pro might not seem like a lot on paper, Coyle acknowledges, but “the perceptual difference from this makes the AirPods Pro tantalizingly close to seamless.” https://9to5mac.com/2019/12/22/airpods-latency-test/ Well as far as metal detecting is concerened, I wouldn't consider 144 ms of delay "close to seamless". But I can imagine some small percentage of detectorists (including yourself, SwiftSword) can somehow deal or not be bothered with this higher level of delay. The good news for you is that if you can deal with >100ms delays, that opens a whole host of non-APTX-LL phones and true wireless buds that you can pair with your Vanquish. This topic has been discussed several times on the forum. So anyone who is interested in a deeper dive should do a search on APTX Low Latency and you can see the tech specs, facts and wide range of opinions of how wireless audio latency affects the detectorist. Regardless most prefer latency no greater than what is supported by APTX-LL (40ms). Neither here nor there as far as XP detectors are concerned so a bit off topic (unless you want to plug a BT transmitter into the audio output jack on your Deus 2 remote or WS6 Headphones so you can use your Airpods) but just thought I would walk through it again in the interest of anyone who might be considering marrying Airpods to their BT audio compatible detector (Vanquish, Equinox, Legend, and GPX 6000 among others). FWIW

...and the list just keeps getting longer. 😉 jk Looking good. Don't let "spanking" that pesky D2 detract you from more important work, Joe.

It took about four months for me to get over the bad taste with the Equinox release, from the slipping release dates, broken dealer promises on shipping, bad shaft fitup quality, lack of accessory coils. You get over it eventually...for me it was my first gold find w/ the Nox and then an amazing 1 day relic run. Yeah, I got over it.

With non low latency phones, as I would swing across a target it would look like two adjacent one way hit targets offset by the distance associated with my sweep speed and the delay of up to 1/4 sec (faster sweeps made the problem worse). It really wasn't about accurate pinpointing per se. As someone who uses coil motion and rotation vice the pinpoint function to line up targets, it literally drove me bonkers.

Not a button.

Cheeky. Just tells you not to begin practice there. Now that you've cleared the junk out with the Nox you can use Deus 2 to find the REAL treasure.🤣🤣🤣 BTW How goes it with the WS6 repair/replacement?

Good job, Erik! Much more interesting than my back yard. Cool saves.

Wouldn't think they would make things worse (that's not say it's bad now), but my point is the 1.07 fixed IF setting is apparently equivalent to the max IF setting of ver 1.08.

Didn't know Airpods were low latency, so would be interested know if they really are low latency because LL BT true wireless buds are a unicorn. Non-Low Latency BT phones are basically unusable. Anyway, as posted above, a simple adapter allows you to plug the WS4/6 puck into whatever audio headphones/buds/speaker you wish.