What do you need help with?

Open the app and tap Best Settings. Pick your printer, the slicer you use, and the material loaded in your machine. Printer Studio shows the slicer's out-of-the-box defaults next to known-good tuned values, side by side. Copy those numbers into your slicer, run a quick calibration, and print. Star any combo you print often so it's one tap away next time.

Workshop is the part of Printer Studio built for the business side of printing. It keeps your material profiles and filament inventory in one place, and a print log records the real cost-per-gram and success rate of your jobs over time — so you can see what a part actually costs and which jobs are worth quoting.

Printer Studio is a one-time purchase tied to your Apple ID. If you reinstall the app or move to a new device, open it and use Restore Purchases, then make sure you're signed in with the same Apple ID you bought it on. Billing and refunds are handled by Apple — use "Report a Problem" in your App Store purchase history.

No. Printer Studio works 100% offline. Every printer, filament, and slicer setting lives on your device, so you can look up values in the garage, at a market stall, or anywhere with no signal once the app is installed.

Yes. Printer Studio runs on both iPhone and iPad. The layout adapts to the larger screen, so settings tables and printer comparisons are comfortable to read on an iPad next to your machine.

The values are dialed-in starting points, not guaranteed final settings. Filament varies spool to spool, so always run a temp tower, flow, and pressure-advance calibration to fine-tune for your exact material and machine. The app's calibration walkthroughs cover each one step by step.

Yes, please ask. The database covers 78 printers across 23 brands and dozens of filament brands, and it grows between updates. Email the model or brand you'd like and we'll look at adding it.

The core reference app needs no account and works fully offline — no ads, no analytics, no tracking. Your favorites, exports, and selections stay on your device. See the privacy page for full details.

Yes — this is one of our specialties. When a device has no off-the-shelf driver, we develop a custom Control4 driver or Savant profile that exposes its controls to your system. Send us the device make and model, the control platform you're on, and what you want it to do (power, volume, inputs, status feedback, etc.) and we'll scope it.

The more the better, but at minimum: the device's make and model, its control method (IP, RS-232 serial, IR, or a published API), the manufacturer's protocol/API documentation if you have it, and the control platform it needs to live in. If there's no documentation, we can often capture the protocol from the device directly.

Where the device supports it, yes. Two-way drivers report real status back to the system — current input, volume, power state, lamp hours, and so on — so your interface always reflects what the device is actually doing instead of guessing. IP and serial devices generally support feedback; simple IR-only devices are one-way.

Often, yes. We can review an existing driver or profile, fix bugs, add missing commands, or adapt it to a new firmware version. If the original is locked or encrypted we may need to rebuild it, but we'll tell you that up front.

We deliver the finished driver/profile ready to load into your project, with notes on the commands and any setup properties. Licensing terms depend on the scope — a one-off for your own system versus something reusable across many projects — and we'll lay that out in writing before any work starts.

Most control issues trace back to network or power. Confirm the controller has power and a network link. Power-cycle in order: modem first, then router/switch, then the controller — wait for each to come fully back before the next. Check whether anything changed: a new router, a changed Wi-Fi password, or an ISP swap will break a system that worked yesterday. If it's still down, contact us with your platform and what changed.

Control systems rely on devices keeping the same IP addresses. A new router hands out different addresses and changes the network name, so the controller can no longer find your gear. The fix is to recreate the network settings (name, password, and reserved IPs) the system expects, or reconfigure the system for the new network. This is a common service call and usually a quick fix.

If one button or device fails but the rest work, the device itself is usually the issue: it lost power, dropped off the network, or its input changed (for example, a TV switched HDMI ports). Power-cycle just that device and confirm its connections. If a whole room is dead, suspect the room controller or its network drop. Tell us which button and which room and we can pinpoint it.

In most cases, yes. We regularly adopt existing Control4, Savant, Crestron, and URC systems — assess what's there, get you access, fix what's broken, and document it so it's serviceable going forward. Some platforms require dealer-level access to make certain changes; we'll tell you exactly what's possible with your specific system.

Adding a device usually means wiring it in, then adding and configuring it in the project so the system knows how to control it — which often needs the right driver or profile (see the Drivers & profiles tab). It's not typically a homeowner-facing change. Send us the device and your platform and we'll handle the integration.

There's no single best one. Control4 is broad and dealer-friendly; Savant leans premium with strong Apple-style UX; Crestron is the deepest for large/commercial jobs; URC is strong value for AV-centric setups. The right choice depends on your scope, budget, and how you want to interact with the system. We program all four and will recommend honestly. Ask us →

Intermittent automation is almost always a network or device-availability problem: weak Wi-Fi where the device lives, an overloaded consumer router, IP address conflicts, or a device that drops offline to save power. A properly segmented network with reserved IPs for control devices fixes the majority of these. We can audit your network and make it reliable.

For more than a handful of devices, yes — and it's the single biggest factor in whether a system feels solid or flaky. A managed network with proper Wi-Fi coverage, VLAN segmentation (keeping control gear, cameras, and guest traffic separate), and remote monitoring keeps everything responsive and secure. It's the foundation we build every integration on.

Dead spots usually mean too few access points, the wrong placement, or consumer mesh gear that can't keep up. The reliable fix is hard-wired access points placed for full coverage rather than range extenders, which cut throughput. We can survey the space and design coverage that actually reaches every room.

Usually, yes. Bringing mixed-brand gear under one system is exactly what integration is for — sometimes natively, sometimes through a custom driver or profile, and sometimes via an API or hub. Tell us what devices you have and what you want them to do together, and we'll map out what's possible.

Start with the network: change default passwords, keep firmware updated, put cameras and IoT devices on their own VLAN away from your personal devices, and disable remote access you don't use. For cameras and access control, proper segmentation and strong credentials matter more than any single product. We can review your setup and tighten it.

Yes. For systems we deploy (and many we adopt), we can set up remote monitoring so issues are often caught and fixed before you notice them, plus a clear path for service when something does need hands-on attention. Ask about a support plan →