2. cables
  3. 124327-158

Has anyone tried these stunning new CPT power cord?

   Considering the many, many brands of power cords I've tried in my very well accomplished high-end system, I have never been so impacted by these Core Power Technology power cords. Within a very short period(15-20) minutes my system literally came alive. Soundstage opened wider and deeper. The background became dead silent, space between instruments and stage members were more focused and everything sounded cleaner and musical than ever. My highs had a glorious crispness and symbols shimmered. Midrange through my 2" horn became more dynamic and punchy. My 15" bass driver tightened and dug low with great control. My Rel G1 which is a fabulous sub on its own but with a CPT 150 on it is another story. Running high pass from my sub to my Audiozen Noah amplifier, music depth is just stunning. Lower end bass is authoritative and clean with solid grip and impact. 
   My experience with these power cords is truly magical. The scary part of the above is I only have one 150 on my sub and one 300 from my wall to my 6 outlet bar. I still need 3 more to complete my system. I could just imagine the level after that...In closing, I cannot emphasize enough to try one of these in your system. I CANNOT and WIIL NOT take these out as they are that good. But hold your jaw, cuz what you've been listening to will just become real after Core Power Technologies. 

Cheers....and let the tapping begin.......



128x128bacardi
calloway
874 posts
 
Mark has been saying they are going to be ready 'next week' for 2 months.He needs to be brutally honest with customers and those who have already sent him money and stop making excuses for the DCs NOT be delivered long before this. Honesty is appreciated...excuses are not..
jay23
210 posts
 
klh007:
I got in touch with Mark and have a Deep Core update, DCs are being made right now, because it's the first production run they are going slowly and carefully to avoid any mistakes, every unit will be tested before leaving, CPT appreciates the enormous patience DC buyers have shown, Mark expects shipments of DCs by the last week in October. Your long wait and understanding of Mark's health and location situations will be rewarded soon. 

Did a real Alpha or Beta process ever happen?

calloway:
Mark has been saying they are going to be ready 'next week' for 2 months.He needs to be brutally honest with customers and those who have already sent him money and stop making excuses for the DCs NOT be delivered long before this. Honesty is appreciated...excuses are not..

I would say take this as a lesson. DO NOT send money for unreleased products, if you're not willing to accept delays. Sh*t happens with preproduction products. I would rather wait to have a working product, rather than a broken or buggy product on the earliest announced release date.
klh007
621 posts
 
Mark will have time tomorrow to post news, and updates on E=Q and Deep Core production. Once again your patience is greatly appreciated, let's wait and see what news Mark has, I think it's good.
lak's avatar
Ag insider logo xs@2x
lak
4,655 posts
 
IMO: Alpha testing took place the first week of May 2017.

Alpha Tests Beta Tests Test Goals Evaluate the quality of the product and ensure Beta readiness. These tests focus on finding bugs, and answer the question: Does the product work? Evaluate customer satisfaction and ensure release readiness. These tests take users on a guided tour of the product to answer the question: Do customers like the product? When they happen After initial QA testing but before Beta Testing, in the stage of the development process when the product is 60%-80% complete (it’s stable enough for technical users, but not yet feature complete). After Alpha Testing but before Field Testing, in the stage of the development process when the product is 80%-90% complete (it’s stable enough for mainstream users, and mostly feature-complete). Test length Typically 1-2 weeks per test cycle with numerous cycles based on how many issues are discovered and how many new features are released. It’s not uncommon for the total Alpha phase to be 3-5x the length of the following Beta phase. Usually 3-6 weeks per test cycle with only 1-2 cycles. Additional cycles are added if significant new features are introduced or if a core component is changed. Primary stakeholders Engineering, Quality Assurance (QA), and Product Management teams. User Experience (UX), Quality Management, and Product Management teams. Participants (testers) Strangers from a variety of targeted technical environments, who can handle giving technical feedback during the test. Involving employees in this stage of testing (a.k.a. dogfooding) helps improve internal alignment and prepare your teams for live-support after launch. Strangers (not friends and family) from your product’s target market. They’ll provide objective insights on the product experience that are relevant to the product’s success and help you better understand your true customers. What testers should expect A product with plenty of bugs and crashes, as well as some missing documents and features. A near feature-complete product with some bugs, fewer crashes, and mostly complete documentation. How feedback is addressed Most known critical and severe issues are fixed, and some features may change or be added as a result of early feedback. Critical or important issues are fixed, and simple user experience improvements are made before product launch. Future versions of the product are heavily influenced by the results. What they achieve Identification of critical issues that cannot be tested in the lab, and insurance of your Betas by addressing show-stopping bugs that would otherwise cripple those tests. They also improve internal alignment and launch-readiness of customer-facing teams. Improvement of launch success by providing evidence-based recommendations for product improvements and a complete view of your customers’ experience with your product. When are they over? A product is Beta-ready when it meets design criteria, all of its primary features work, and Alpha testers are no longer finding critical or blocking issues. A product is Field-ready when mainstream users from your target market are comfortable with the user interface, and are satisfied with their experiences with the product and its features. What happens next? Beta Testing! Field Testing!
t_ramey
632 posts
 
@lak 

Were you and ozzy supposed to be the beta testers for the Deep Core?
More to discover