TONEFOLD / physical hardware concept
Procurement questions
Concrete questions for defining the physical sample, nominated system and supplier responsibility.
01 / Does a controller produce sound by itself?
No built-in sound engine is included by claim. A real controller sends messages to a nominated host or instrument; sound generation and its software/license responsibility are separate.
02 / Is a DAW or instrument library bundled?
No. No real software product, sound library, subscription, song, artist or endorsement is represented. Ask the actual supplier to confirm any licensed bundle outside this demo.
03 / Do MIDI connectors prove host integration?
No. Nominate message behavior, driver/editor ownership, actual host and application. Connector shape and a message target do not establish a complete working map.
04 / How should presets be reviewed?
Keep one firmware and map revision, then observe changes, reconnect and any persistence behavior using the actual supplier protocol. The site itself stores no presets.
05 / Are faders motorized or calibrated?
No motorization or calibrated control accuracy is claimed. Travel, reach and command-range behavior remain physical and host sample questions.
06 / Can this brief confirm production?
No. The local summary is NOT SENT. Actual feel, map, sample costs, firmware/editor scope, markings, MOQ, dates and shipment terms need supplier confirmation.
Prepare the real supplier discussion
Separate the gesture from the message and the sound source.
The demonstration has no supplier inbox, quote engine or order workflow. Its preset summary simply makes the sample responsibilities reviewable.
MIDI-map worksheet ↗