# Cinematic Style LoRA for MiniMax H3
A broad cinematic style LoRA for MiniMax H3, trained on roughly 1,200 carefully captioned cinematic stills.
The goal is not to force one specific movie look. The dataset was built to teach a wider cinematic language: realistic film photography, composition, framing, perspective, motivated lighting, lens character, depth of field, production design, realistic materials and skin, color relationships, atmosphere and organic film texture.
## Activation Tag
Use the original activation tag exactly as trained:
ASTROCINEMAV01K2TYes, the tag still contains K2T. That is intentional because it is the original learned activation tag from the dataset. This release itself is for MiniMax H3.
Place the tag near the beginning of style_and_tone.
Example:
style_and_tone: ASTROCINEMAV01K2T. Photorealistic neo-noir crime drama, motivated practical lighting, shallow depth of field, restrained color grading, realistic skin texture, subtle halation and organic fine film grain.## How I Recommend Prompting It in MiniMax H3
Do not rely only on the word "cinematic".
Tell H3 what kind of cinematography you actually want:
- time of day
- dominant and secondary light sources
- practical lights visible in the scene
- camera distance and framing
- camera movement
- lens feeling / depth of field
- realistic skin and material response
- environment and production design
- weather and atmosphere
- color relationship
- film grain, halation or highlight rolloff when useful
The LoRA works best as a broad cinematic foundation, while the rest of the prompt defines the specific genre and shot.
## MiniMax H3 Prompt Structure
I recommend separating the prompt into:
- style_and_tone = visual language and cinematography
- continuous_shot or multi_shot_sequence = action, acting, camera and timing
- audio_design = music, sound effects and ambience
- explicit dialogue lines whenever characters speak
H3 is very good at combining visual direction with audio, so do not forget the audio side when the scene needs it.
For example, a crime scene can include rain, passing traffic, a low score and dialogue. A fantasy battle can include orchestral music, weapon impacts, footsteps and creature sounds. An advertisement can use voice-over, product Foley and a clean commercial music bed.
## General Tips
For realistic cinematic results, avoid contradictory style language. If you want realism, do not mix the prompt with vector-art, cel-shading or illustration terminology.
Use physically coherent lighting. Instead of listing random light colors, describe which source is dominant and how secondary light affects the subject.
Keep skin and materials realistic. Describe pores, tonal variation, fabric response, wet surfaces, polished metal, glass or practical reflections only when they are relevant to the shot.
For fast action, keep the movement readable. One clear action per beat usually works better than trying to force too many unrelated events into a few seconds.
For trailers and advertisements, multi_shot_sequence is extremely useful because each cut can have a clear purpose.
For music-led videos, describe the music as the master timeline. Shot and camera cuts may use timecodes, but avoid forcing sung lyric lines into strict timed segments.
## What to Test
The LoRA is useful for a wide range of H3 projects:
- crime and neo-noir
- period drama
- romance
- action
- science fiction
- fantasy RPG cinematics
- realistic game trailers
- commercials
- beauty advertising
- product videos
- music videos
- atmospheric character scenes
- cinematic environments
The attached example videos were generated with MiniMax H3 using this LoRA. I also included a separate prompt pack containing 15 complete H3 Text-to-Video prompts across film, games, romance, action, trailers, advertising and music-video scenarios.
Feel free to modify the examples and push the LoRA into completely different genres. If you create something interesting, I would love to see the result.
Description
For Images use https://civitai.red/models/2831431/astro-cinema-v01-for-krea-2 .
FAQ
Comments (6)
Noise a little bit high after generate in my workflow.
Did you use a turbo LoRA? How many steps die you Set? Maybe i can h LP to improve the quality. xD
@Astroburner I use workflow of H3 Motion Context to connect with segments together with 20 steps under dual_clock_euler and native flow sampling method.
@yli6hz iI was using a Workflow from comfyui Templates with a single AdvancedSampler with res_multistep with 1 megapixel resolution. Do you have a Link to your Workflow I could test it.
@Astroburner I change another workflow and noise issue is solved, thanks!