Trail camera footage of animals that do not exist.
I made a 30-second Halloween short in Adobe Firefly and wrote up every prompt, including the ones that failed.
Make your own: https://adobe.ly/SpookyFF
@AdobeFirefly #AdobeFireflyAmbassadors #Ad https://x.com/i/article/2107974157115801600
Trail camera footage of animals that do not exist
Trail cameras take bad pictures. The flash blows out the grass, the animal goes flat gray, and a timestamp sits in a black bar along the bottom. Everyone knows that look, which makes it a good place to hide something impossible.
So for Halloween I made a 30-second short called Trail Cam: October. It is trail camera footage of five animals that do not exist. The stills, the motion, the sound, the music and the edit all came out of Adobe Firefly.
This is the process in order, including the parts that failed. The failures taught me more than the keepers did.
Step 1: one prompt, three image models
Firefly Boards lets me run one prompt through several models and line the results up on one canvas. I started with the hardest creature, a buck with lit candles for antlers.
Firefly Image 5 gave me a normal buck with glowing antler tips. No candles. GPT Image 2.5 gave me the most detailed frame, with wax tines and visible wicks. Nano Banana 2 landed between them.
Then I zoomed in and the ranking flipped. The GPT Image 2.5 frame was too well exposed. It read as a clean black and white photo. In the Nano Banana 2 frame the flash died into black a few meters out and the flames blew into lens flare. It looked like a frame off a real trail cam, so it won.
The lesson: judge each result against the look you are after. The sharpest frame lost because trail cam footage is supposed to look bad.
Step 2: the info bar breaks in motion
The timestamp bar is part of every still. That made it the riskiest part of the project, because video models redraw text on every frame.
The first run was Luma Ray 3.14. The camera stayed locked and the head turn landed. The bar did not survive. "CAM 03" turned into 06, then 00, then 60, and the year ended as "202C".
I ran the same still and the same prompt on Kling 3.0. Every character in the bar held for the full five seconds. Kling 3.0 became the motion model for the rest of the film.
If your video model keeps scrambling on-screen text, crop it out of the still and add it back with the text tool in the Firefly Video Editor.
Step 3: fix a miss with one line
The second creature was a fox with a tail made of ground fog. The first result had two problems. The fox still had a full furry tail with mist streaming off it. There was also a second trail camera strapped to the tree, because my prompt said "camera strapped to a tree at knee height" and the model took that literally.
I did not regenerate. I selected the image, clicked Edit and typed this:
Both problems were gone in one pass and the rest of the frame stayed put. I also pulled that camera phrase out of every prompt that came after.
Step 4: describe the material
My first motion prompt for the fox said its "tail of fog streams behind it". Kling 3.0 moved it like a tail. It swung with the body as one stiff limb.
So I rewrote the prompt without the word tail.
This version piles up on the log and spills over the sides after the fox has left the frame. Same still, same model. If you name a body part, the model animates a body part. If you describe what the material does, you get the material.
Step 5: know when to swap the creature
The tortoise with a pumpkin for a shell worked on the first try, still and video. The motion prompt said the pumpkin was fused to the body, so it rocks as one piece with each step.
The bats did not work. I wanted wings made of dry maple leaves. Round one gave me normal bats with leaves stuck on leathery wings. Round two said there was no skin membrane at all and came back worse, with leaves hanging beside the bats.
Two misses was enough. Every keeper so far was one animal with one obvious swap. The bats needed the model to rebuild anatomy. I replaced them with an owl in a bedsheet ghost costume, and it landed on the first generation. In motion the head turns far past where a neck should stop, and the sheet stays cloth the whole way around.
The last creature is a crow built like a scarecrow, with a burlap body and a button eye. I kept a real beak and real feet in the prompt. Those two details are why it reads as a living bird. It also worked on the first try.
Step 6: one sound per prompt
For audio I used Generate Sound Effects. My first prompt for the tortoise asked for footsteps, a hollow pumpkin knock, a quiet forest and crickets. It came back as stomping. The model grabbed the loudest idea and dropped the rest.
The fix was one ambience bed under the whole film, then a single sound per shot, described by what is physically making it.
The same rule fixed the crow. One prompt with straw, wings and a tap on glass produced thuds against a microphone. Split into a straw rustle and a wing flap, both came out clean. The fox came back too loud and too fast because my prompt said "trotting quickly". I rewrote the pace and saved the volume for the edit.
Step 7: music from tags
Firefly's Soundtrack Generator builds its prompt from tags. I cleared the defaults and set the vibe to mysterious and eerie, the style to ambient and cinematic, and the purpose to "spooky short film". Energy went to low and tempo to slow. Four tracks came back, and I took the one with low stings.
Step 8: assemble in the Firefly Video Editor
The timeline is a title card, five creatures and an end card. Both cards are generated stills with every line of text spelled out in the prompt, and each one carries #AdobeFireflyAmbassadors on screen.
The creatures run in timestamp order, from 7:52 PM to 11:59 PM, so the night moves forward. I used hard cuts between them, the way a real trail cam jumps from one capture to the next. The crow lunges at the lens and the cut lands on a "no signal" card full of static.
What I would tell you before you try it
- Run your riskiest shot first. The buck told me which image model and which video model to use for everything else.
- Pick the model per job. Nano Banana 2 held the look and Kling 3.0 held the text.
- When a result misses, read your own prompt first. Two of my failures were single words I wrote.
- After two misses, change the idea.
Prompt share
Swap in your own animal and try it in Firefly Boards.
Made in Adobe Firefly with Nano Banana 2 and Kling 3.0. Try it yourself at adobe.ly/SpookyFF, then show me what your trail cam catches.
I hope you have a productive and creative day.