The work behind the screen.

A personal account by Jack Cali November 1 2026

The work behind Drivesoft

When someone spends serious money on a Drivesoft system, I want them to understand the work behind that purchase. The hardware and software have to earn their place. So do the people standing behind them. Our history matters because it explains the decisions we make, the problems we know, and the direction we intend to keep building.

This is my account of that road: the garage and competition years, the Orion relationships, the work before and during ADS and ADST, the independent development of Drivesoft, and the industries that helped shape it. It also explains why I am bringing more of that experience into consumer audio and the home.

Original literature, software, photographs and engineering records give this history its context. Documented dates sit alongside personal recollections. More material from the archive will be added here.

We have new tools now. Faster connectivity, modern devices and AI can make development and presentation easier. They help us carry years of work forward. To understand what we are offering today, you need to know where that work began.

The garage years and the thirty dollar trophy

Long before ADS, I was tinkering in the garage, like a lot of us were. I was trying things, competing, traveling and pushing the equipment. I remember breaking records, but the reward was often the experience, the people and a thirty-dollar trophy. Plenty of that work was done for no paycheck at all.

Some of the people providing those trophies are the same people still involved today. That continuity means something to me. We were building our lives around a shared interest, learning from what worked and finding out very quickly what did not.

My relationship with Orion goes back to 1988. The guys in Arizona could go down to the shop. I was across the country, but I remember Orion supporting me too. That support helped create a loyalty that lasted beyond a particular product or ownership period.

Competition taught me to question limits. I remember experimenting with ports and single-subwoofer systems, chasing results that surprised people, and watching the rules become more specific as competitors pushed harder. Score sheets, classes and dates help put those achievements in context. More competition records will be added to the archive.

Later, the same instinct took me into software for the organizations around the events. I saw recurring problems and wanted to help solve them. VSOMS belongs in that part of the history: the work behind keeping an operation organized, alongside the vehicles and systems people came to see.

Those years explain a lot about Drivesoft. Curiosity came first. We learned by building, showing up, listening and trying again. A small trophy can represent a very large amount of unpaid engineering.

By 1998 the music was already in the vehicle

By 1998, I was playing MP3s in my vehicle system. That is an important milestone in my own account. I wanted access to my music and the capabilities of a computer in a form that made sense inside a vehicle.

The idea extended beyond a music player. There was an opportunity to bring media, information and equipment control together, with software that could continue to grow. A computer offered room to add capabilities without treating the whole system as a disposable model-year purchase.

Cars had touchscreens before this. My point is the combination of functions, the software environment, and what users could actually run and control. Drivesoft supplied its interface and integration around a wider computer platform. That distinction is more useful than arguing over who first put a touch-sensitive display in a dashboard.

The archive includes a 2004 brochure describing a first assembled unit in November 1998. The original 2001 DVAS brochure documents the system and functions presented at that time. Earlier prototype material forms another part of the development history.

The original screens and period literature show how the system evolved. They give readers a direct view of the capabilities and controls from each era.

Enrique and the road to Arizona

Enrique, my partner today, knew what I had working in Louisiana. When an opportunity came up around a European car computer that mainly played MP3s, he made the connection. His point was simple: his friend already had a system operating and had been developing it for some time.

The unit sent to me did not power up on the bench in the way it needed to. My own system could demonstrate the direction, including software and media functions, but its power and ignition arrangement still needed refinement. It worked well enough to show people; making it a dependable automotive product required more engineering.

I drove to Arizona to present what I had and try to move the technology forward. I place that company-development period around 2001. By then, Mark had already left. I did not understand that at the time. His departure belongs in the history before my arrival, rather than being attributed to something that happened after I got there.

Sourcing the right components was work in itself. I spent time cold calling and following leads, using the early web much like a large directory. I found people working with automotive power supplies and suppliers with suitable LCDs. Existing equipment could solve one problem while still needing adaptation for the fuller system I wanted to operate.

The power supply and ignition behavior were essential. A demonstration had to become something that could cope with life in a vehicle. That meant working with specialist knowledge as well as developing the interface and software. The retained boards, software and period documents are part of the explanation, including the 2001 floppy-disk material in the archive.

DVAS and the independent direction

The 2001 a/d/s/ literature introduced DVAS, the Digital Video Audio System. Its advertised functions included touchscreen and infrared control, GPS, FM and television, DVD and CD playback, MP3 storage and transfer, and a cellular Internet connection. That brochure lets people see what was being presented at the time.

The development did not start from nothing when I entered that building. Work preceded the ADS and ADST period, continued through it, and carried on as Drivesoft after the relationship ended. That sequence matters to understanding the company.

It was a difficult period, and it affected how I approached business relationships afterward. I wanted to keep developing the system and retain control of its direction. Some experiences taught me to be more careful about trust, responsibilities and the way technical work was shared. Those lessons can be told without turning the company history into a list of grievances.

I did not follow the corporate transition to Vista, California with the people who relocated. I was already pursuing my own path. But that did not mean the technical connections stopped. Orion equipment was still being provided to me, and Drivesoft continued to appear in show vehicles even without the official arrangement people might assume existed.

I still went to the DEI facility in Vista to install Drivesoft in vehicles headed for SEMA and CES. Those installations continued our technical connections while I pursued an independent path. More photographs from that work will be added here.

The people and the opportunities

Enrique is part of this story because he understood what was already working and helped make an introduction. Other people influenced the direction in ways that do not fit neatly into a product specification.

I remember sitting in neighboring cubicles with Shawn Dougherty and working through possible names. She helped me think about how to describe the software and what it did. That process brought us to Drivesoft. Her willingness to build something of her own, including her later work as a co-founder of mophie, is something I respect. Her place in this story deserves recognition.

I also remember trying to get ADS to take Shawn Fanning and the possibilities around digital music seriously. My suggestion was practical: help him get his car sorted out and put a proper audio system in it. I wanted leadership to engage with the people changing how music was used. I could not get the support I was looking for. That was a proposal I advocated, rather than a completed partnership.

Other relationships include Jeff Kukowski in the Destinator connection and Tim Coomer in the Escort and Cedar work. Each represents a different part of the development story. More from those projects will be added to the archive.

Much of my core circle goes back twenty or thirty years. Some projects began with an unpaid test or a decision to help someone see whether an idea could work. The knowledge and relationships from those decisions are still useful. New employees and collaborators can contribute alongside that experience; the history should give them something solid to build on.

Behind the show and on television

Some of the Drivesoft work people saw in the early 2000s was almost invisible. Around 2003 through 2006, I remember systems tucked under seats in vehicles being prepared for SEMA and CES. They helped run timing sequences, lighting and automation. People could watch the effect without knowing what was controlling it.

The visible dashboard tells only part of the story. A system could be controlling a demonstration or coordinating equipment elsewhere in the vehicle. Installation photographs help reveal the work behind the display.

I place the Pimp My Ride chapter around 2004. The work reached people who would never have visited our shop or attended a technical demonstration. Contemporary coverage also connects Drivesoft with West Coast Customs and appearances on the programme.

Television brought the work to a much larger audience, including viewers who had never visited our shop. Some contributions were visible on screen; others operated behind the scenes. More television and vehicle material will be added here.

Over the years, familiar functions and layouts appeared across the industry. The original screens, dates and product literature provide a useful way to compare how vehicle interfaces developed.

The industries told us what they needed

The limousine industry called me in 2004. I did not arrive with a declaration that everyone needed the same thing. I asked them to tell me what they needed, and then I went to work adapting the technology around how they operated.

I stayed close to the companies installing and using the products. Watching those systems in real use helped reveal the next requirement. One customer needed particular controls; another needed a different display arrangement or a way to manage information. The applications developed through that process.

Some industries made extensive use of what we had. Others had little need for it at that point, or needed capabilities I was not ready to provide. RVs are an example where I remember not yet having everything I needed. That is part of the development story too. Readiness is different for every application.

The limousine work connected entertainment with vehicle functions, displays and the people operating them. Other work moved through casino transportation, commercial vehicles, public information systems and specialized control. I recall casino field testing leading to the Bell Transportation work in Las Vegas, involving a contract covering more than four hundred cars.

If you have taken a limousine in Las Vegas, you may already have encountered Drivesoft without knowing our name. The work often operated behind the passenger experience, connecting media, displays and vehicle controls. More fleet and installation history will be added here.

The different branches of Drivesoft grew through those requirements and installations. They were not all conceived on a whiteboard last night. Today the whiteboard helps us explain a long history of connecting systems and adapting them to the work.

The work beyond car audio

My background includes technical and workplace-language training, office systems, point-of-sale work and software supporting events. Some people may have been at shows using my management tools without ever knowing it. The work was often behind the operation rather than at the center of attention.

That experience affects how I think about interfaces. A control has to make sense to the person using it, in the situation where they need it. An installer, a driver, an office worker and a student do not necessarily need the same screen, even when some of the underlying functions are shared.

I have kept the development of our audio software and interfaces in-house. The work comes from our own hands and decisions. That does not mean we invented every operating system or manufactured every component; specialist hardware, suppliers and outside platforms have always had their proper roles.

AI is now one of the tools we use to develop and communicate. It can help us work through new interfaces, organize material and present the history. The experience directing that work comes from the years of projects behind it.

Commercial and specialty-vehicle experience informs our consumer-audio and home products. Modern devices and faster connections give us new ways to carry that work forward. Product pages identify available features, compatible equipment and upcoming releases.

What a customer should get for the money

When I talk about someone putting roughly two thousand dollars into a system, I am talking about the scale of the commitment. That person deserves a clear explanation of the equipment, software, compatibility, support and continuing costs. The history helps explain the engineering, but the product still has to deliver useful value.

The consumer range brings together supported media, audio control, displays, lighting and other equipment through the appropriate interfaces. Our Pro audio hardware includes balanced connections. Tuning, demonstrations, legacy integration and display choices are covered in the individual product descriptions.

Useful comparisons start with the complete system: connections, functions, required extras, recurring costs and the equipment in the installation. Those details help customers choose the right fit.

Explore the launch and product-detail pages for configurations and purchase information. This history page provides the people, projects and original records behind them.

Version, license and support information belongs alongside the product. The archive provides the wider context: projects, revisions and the people behind the work.

Ownership and useful services

I have never liked the idea of charging someone indefinitely simply to keep using something they already bought. It makes me feel like a property-tax collector. Our direction is that purchased local software functions remain usable when an optional membership ends. Equipment compatibility and outside services still have practical limits, but we should not create an artificial shutoff to collect another payment.

I want someone to be able to keep a useful package for years if it continues to meet their needs. Other customers may want active support, new services or deeper involvement. Those are choices we can explain honestly. Continued use of a purchased version is a different promise from unlimited future development or unlimited personal support.

My own music collection makes the issue personal. I have tapes and CDs in the closet that I paid good money for. Now I pay services to hear much of the same music. I enjoy the convenience. I also think we should stop occasionally and ask what we are paying for. I am part of this too.

I want users to be able to manage their own media on supported equipment without us adding unnecessary obstacles. That is what I mean by flexibility and control. It does not mean our proprietary source code is public, and it does not erase the rights of the people who make the music.

The same principle applies to personal files. For some people, a few terabytes could hold a very substantial collection of photographs, music, favourite videos and documents. Four to six terabytes is an example, not a universal lifetime allowance. Video formats, collection size and future growth make a difference, and a separate backup still matters.

I value storage, backup and the convenience of help protecting information. Customers deserve to know where their files are, how to retain or export them and what an ongoing service provides.

Grandma could manage a household with a pen and a pad. We now have extraordinary tools, but an ordinary kitchen table should not inherit every complication of an enterprise office. Technology ought to reduce that burden. Again: me too. This is a question I ask myself as much as anyone else.

Real people and sustainable growth

We need to earn a profit. Useful online services cost money, and skilled support takes time. I am comfortable charging for something that provides continuing value, provided the customer understands it and can reach the people responsible.

Having one company help coordinate several things can be useful when you know who that company is, understand the arrangement and can get a real person on the phone. That relationship has to be backed by clear boundaries and practical control over your information.

Software can reach people around the world. Personal service cannot grow without limits just because a download can. We need to pace Pro participation and support around the people and capacity we actually have, beginning with the industry and community we know here at home.

If wider demand develops, that is an opportunity to build responsibly. My goal is a company that can remain involved with its customers and continue doing useful work. A large download number is not a substitute for keeping the commitments we make.

Interfaces that fit the person

The Drivesoft layout and a car-audio layout do not have to be identical. Some people want straightforward controls they can discover without a manual. Others love familiar equipment faces, classic player buttons and the shortcuts they already know. I understand both preferences.

We can carry shared capabilities into different skins and screen sizes. A larger workspace may have a dedicated area for extra information. A compact audio display may bring that information forward only when it is needed. The layout should suit the job and the person.

Planned for future releases: a privacy view that responds to supported door or presence signals. The design keeps selected content covered until the user deliberately restores it.

Privacy triggers depend on the signals available in the installation. A standard OBD connection does not provide every door or body signal. Essential controls and private spoken feedback are part of the design considerations.

Future device-awareness features include recognizing enrolled devices and helping identify a phone that may have been left behind. Device detection and occupant sensing are different functions; occupant sensing requires its own hardware.

More information about privacy and device-awareness features will accompany their release.

Learning through the work people already do

My experience with workplace-language education is part of this direction. People often have an immediate reason to learn the words they use with colleagues, customers and equipment. That can become an approachable beginning for broader language learning.

Planned language features include optional spoken control labels, useful verbal feedback and translations suited to the industry and task. Supported language packages will be listed with each release.

A person might start by hearing the name of a control, then choose to explore the vocabulary for a task. Someone who wants more could move into guided practice and deeper AI-assisted learning. Someone who simply wants to operate the system should be able to do that without a lesson interrupting them.

Language and guided-learning tools are planned for future releases. Their purpose is practical: help people communicate in the work they already do and explore more when they choose.

A place for the next generation

Imagine someone of eighteen, nineteen or twenty who knows very little about our equipment but can make a video, organize people online or find their way around almost any app. They may already have useful skills without knowing where those skills fit in this community.

Now imagine a familiar screen making something happen in front of them: a configured vehicle system responds, a demonstration runs, or they help prepare an entry for an event. That connection between the digital tools they know and a physical activity can open a door.

They do not have to write the app or build every component to take part. There are installers, fabricators, competitors, event hosts, business operators, media creators and people who help a show run well. Each role has things to learn, and there are many ways to begin.

The person who can bring a crowd together may be exactly who a local event needs. Someone who documents a build well can help the builder explain it. A newcomer operating a system may become curious about installation or engineering. We do not know where that interest will lead until we make room for it.

Those of us who have been here a long time need to recognize that potential. We can share the knowledge earned through years of building and competition while listening to what newer people bring. There is a place for you here. You just might not have found it yet.

Back at the shows together

Part of the ambition is to have our own presence at the events that brought this community together: booths, vehicles, demonstrations and Team N-Tense representing the people who kept the work going. That includes the kinds of major shows and competitions where enthusiasts can see the equipment and meet the people behind it.

dB Drag Racing, Import Face-Off and local competitions connect people through vehicles, music and shared experience. Local organizers are an essential part of that community.

I would like to make the show experience easier to enjoy as we get older. Set up the vehicles, run supervised demonstration sequences, pull up a chair and actually finish a conversation with an old friend. After all those years of unpaid work, that sounds like a reasonable ambition.

Online coverage can help an event reach people beyond the people standing beside a vehicle. In-person activity and online participation can support one another. The invitation to younger builders is part of keeping that connection alive.

Our event presence will grow alongside the company. Participation supports useful products, continued development and the community behind them.

Keep the record open

This archive connects the software, hardware, original documents and people who helped us get here. More records and images will be added over time.

That includes recognizing people properly, recording the important departures and losses, and showing how one project led to another. It also means separating a remembered date from a documented one and correcting the record when better information appears.

This history brings together surviving records and my own recollections. If you took part or have photographs, documents or details to contribute, please get in touch. Every contribution helps preserve the shared record.