Lighting: Ray silent HDR if you grade; Veo if it talks
Audio off vs native. Pick.
Audio off vs native. Pick.
A lighting OEM clip is either a photometric plate or a talking SKU. Those are not the same generate. If the next session is a grade — throw, falloff, the wall that still has texture after you downmap — you need a silent file with headroom. If a host has to say 3000K, 90 CRI, or the catalogue name, you need native audio. Pick the soundtrack first. The row follows.
Empty audio is a field on the SKU
Luma Ray 2 720p is Luma Ray 2 video generation in 720p quality. Category: text-to-video. Durations: 5s and 9s. Resolution: 720p. Credits: 50. Audio: empty. No image required. That empty audio field is the product. Do not write a musical into the prompt and expect a bed. Do not write a presenter into the prompt and expect a mouth.
720p is the ceiling. Qualities listed: 720p. There is no 1080p switch on this row. Aspects run 1:1, 3:4, 4:3, 9:16, 16:9, 9:21, 21:9. Pick the shape the platform actually serves. A 21:9 "cinematic" take you later crop to 9:16 throws away the only sharpness you bought.
Fifty credits bills that unit. The 9-second take is the expensive sibling of the 5-second one, not four free seconds. The row, not the brand is the same warning in catalog form. Demos are not this SKU.
When the brief named HDR by name — 16-bit, 1080p, a master you will sit under Rec.2020 PQ or HLG — Ray 2 720p is the wrong original. Ray 3 is the HDR silent plate. Versely does not publish /models/luma-ray-3. Route by job anyway. Tagging a 720p SDR-looking file as PQ does not invent speculars. Grade HDR once, keep the SDR downmap.
Kelvin and CRI do not belong in the generate
A fixture housing is a physical SKU. If the crew already shot the lamp, that still is the contract. Ray 2 720p does not require an image; text-to-video will invent a cousin of your housing. Leave the T2V row. Animate the photo on an image-to-video model. A generated sconce that is "close" is a failed catalog page.
3000K, 4000K, 90 CRI, IP ratings, "not for wet locations" are strings. Burn them with a text overlay after picture lock. Prompted type on a bezel is a misspelled reference you cannot edit. Silence in the Ray file does not change that.
Native dialogue is a different row
Veo 3.1 is native audio, official 4K tier, 4 / 6 / 8 second clips. Use it when a line has to leave a mouth, or when always-on dialogue is the soundtrack you cannot rebuild later. It is the wrong row for a colour-volume plate of a beam.
Split the jobs. Silent wides of the throw on Ray (or Ray 3 if the master is HDR). The line on Veo. Cut them. TTS under a beam with no face is fine. TTS on a generated presenter is a lipsync problem neither Ray row signed up for.
The AI video generator is only the door. Name the row after the brief names audio. "Show the fixture" is silent. "The fixture has to speak" is Veo.
FAQ
Does Ray 2 720p generate native audio?
No. The audio field is empty. Description is "Luma Ray 2 video generation in 720p quality." Plan sound in the editor, or pick Veo 3.1 when a mouth is in the brief.
We need an HDR10 master plus an SDR downmap. Is Ray 2 720p enough?
No. Max output is 720p. The 16-bit HDR 1080p plate is Ray 3. A tagged 720p Rec.709 file is not that master.
The catalog page has a talking host. Which generate?
Veo 3.1 for the host — native audio, 4 / 6 / 8 seconds, 4K tier. Keep Ray for silent beam plates. Do not ask one file to be both.
Can I put "4000K" in the prompt so it appears on the housing?
Do not. Prompted type is a miss you cannot edit. Keep the housing clean. Overlay the Kelvin string after lock.