Views
No views yet


coremltools; the packages are stateless, so all sequencing and buffering lives in your Swift code.| Task | text to image |
| Upstream | ByteDance/Hyper-SD |
| Packages | 4 |
| Download size | 905 MB |
| Minimum iOS | 17.0 |
| Peak RAM | ~1000 MB |
| File | Size | Compute units | SHA-256 |
|---|---|---|---|
HyperSDTextEncoder.mlpackage.zip | 216 MB | cpuAndNeuralEngine | 201b0fcc3573811a… |
HyperSDUnetChunk1.mlpackage.zip | 310 MB | cpuAndNeuralEngine | 279da11b8231aeeb… |
HyperSDUnetChunk2.mlpackage.zip | 290 MB | cpuAndNeuralEngine | 0a700d11a105da58… |
HyperSDVAEDecoder.mlpackage.zip | 87 MB | cpuAndGPU | 1260371542d845a2… |
vocab.json | 1 MB | - | e089ad92ba36837a… |
merges.txt | 512 KB | - | 9fd691f7c8039210… |
| Total | 905 MB |
compute_units is not a suggestion -- it is the configuration the conversion was verified against. Moving a package to a different compute unit can silently change the numerics (FP16 attention overflow) or crash on the GPU.1hf download mlboydaisuke/coreml-zoo --include "hypersd/*" --local-dir ./hypersd
2unzip './hypersd/hypersd/*.zip' -d ./hypersd1import CoreML
2
3let config = MLModelConfiguration()
4config.computeUnits = .cpuAndNeuralEngine // as converted — see the table above
5
6// Unzip the .mlpackage, drop it into your Xcode target and Xcode compiles it
7// at build time:
8let model = try HyperSDTextEncoder(configuration: config)
9
10// ...or compile a downloaded .mlpackage at runtime:
11let compiled = try await MLModel.compileModel(at: mlpackageURL)
12let model = try MLModel(contentsOf: compiled, configuration: config)This model is split into 4 Core ML packages that are driven in sequence from Swift. Load them one at a time, copy the outputs out of theMLMultiArraybuffers and release each model before loading the next — two large Core ML models resident at once will OOM on an iPhone.
sample_apps/HyperSDDemo, a standalone SwiftUI project.convert_hypersd.pydocs/coreml_conversion_notes.md