Privacy Model licenses

Home › Guide

A short guide

SeasonStudio is meant to be learned by using it, not by reading about it. This page exists for the handful of things worth knowing before you start, and the handful more worth knowing when something surprises you.

Nothing here takes longer to read than the model you are waiting on takes to load.

Your first ten minutes

The app opens with a small language model already inside, so there is something to do immediately. A suggested order:

  • Open Text and ask it something. No download, no setup. This tells you how the window works and roughly how fast your machine is.
  • Open Translate and paste a paragraph. The most immediately dependable tool in the app, and a good sanity check that inference is using the backend you expect.
  • Open Image and type one sentence. The panel will tell you which model file it needs. Start with a light model at 512×512 to see the whole loop end to end before committing to a large download.
  • Look at the results panel. Everything from every tool lands in the same place, and it is the fastest route to "save that one".

Resist the temptation to download the biggest model first. A fast model teaches you the app; a slow one teaches you to wait.

Finding your way around

One window, three regions, and they never move. The tool list runs down the left, the controls for the current tool sit in the middle, and results collect on the right.

The tool list

Eight entries — Text, Translate, Image, Video, Music, STT, TTS and Vision. Switching tools does not throw away what you had; you can go back to a panel and find your settings where you left them.

Premium

Bottom left. One screen, one price, a Restore action for a purchase you already made. It unlocks all models and the hardware acceleration backends; there is no subscription and nothing recurring.

The controls

Model, prompt, and the two or three numbers that matter for this tool. Panels deliberately expose less than a node-graph app would — the aim is a decision you can make in seconds.

The results panel

Every output from every tool, newest first, with a full-size view a click away. Save what you want; the rest costs you nothing but a little disk cache.

Adding models

This is the one piece of housekeeping the studio asks of you, and it works in the least demanding way we could find: a run tells you what it is missing, and nothing else.

Two ways in

  • Let the run fetch it. Choose a model, press go, and if the file is not on disk the app names it and offers to download it. Only that file — the studio never pre-provisions a model zoo you did not ask for.
  • Import what you already have. If you have a folder of GGUF or ONNX files from other local tools, point the studio at it. Nothing is copied or converted behind your back and nothing touches the network.

Building a shelf that suits you

Two image models beat five: one fast one for exploring, one heavy one for finishing. The same logic applies everywhere — a small transcription model for voice memos and a large one for interviews will serve you better than one compromise in the middle.

A note on file sizes

Image models run from a couple of gigabytes to twenty; video models are larger still. Check hardware expectations before starting a download you will not be able to run.

Writing prompts

There is no secret syntax and no magic word list. Prompting well is mostly about being specific in the right places and quiet in the others.

Name the subject, then the light, then the medium. Everything else is decoration. — the shortest useful prompting advice we know

Four habits that pay for themselves

  • Lead with the subject, not the style. "A wizard reading under a mushroom" first; "watercolour storybook illustration" after. Models weight the front of a prompt more heavily.
  • Describe light explicitly. Soft rim light, overcast noon, single candle. It changes an image more than any adjective about quality.
  • Change one thing at a time. When a result is nearly right, edit one clause and keep the seed. Rewriting the whole prompt throws away what worked.
  • Use the negative field sparingly. Two or three genuine problems — text, watermark, harsh contrast — beat a paragraph of borrowed boilerplate.

Let one tool write for another

The Text panel is a good prompt editor. Describe the picture you want in ordinary sentences, ask for it as a compact image prompt, and paste the result into Image. This is also the direction the app itself is heading — see the roadmap.

Results, and where they go

Output is ordinary files in ordinary formats — PNG for images, MP4 for video, WAV for audio, plain text for text. There is no project format and no library database that has to be exported from.

Watch and abandon

Image generation draws a live preview while it samples. If the composition is wrong at step five it will still be wrong at step thirty — stop it, change one clause, run again. This single habit will save you more time than any hardware upgrade.

Keep the settings with the result

When something works, note the model, seed and steps somewhere before you move on. Persisting that automatically, so a run can be reopened and re-run later, is the first thing on the roadmap — until then, a text file beside the image does the job.

Content safety

Two gates sit around every run, and both of them run on your machine like everything else in the app.

Prompt → Prompt gate → Generation → Output gate → Shown and saved
  • The prompt gate reads what you typed before any model is loaded and before anything is downloaded. A refusal here costs you nothing but the sentence.
  • The output gate classifies every generated image, live preview frame and video frame before it can be displayed or written to disk. Anything over the threshold is replaced with a neutral placeholder — the frame never reaches the screen and never reaches your folder.

Both gates use a small classifier bundled with the app. Like the rest of the studio, they work with the network switched off, and they report nothing anywhere.

Privacy, stated plainly

There is no account, no server component, and no analytics or crash-reporting SDK. Your prompts, imported files and generated results never leave your machine.

What the app does over the network

Downloading a model file you explicitly asked for, asking the store which purchases you own, and — only when you press Report — opening the report page in your browser. That is the entire list. Import your models from disk instead and the app has no reason to open a connection of its own at all — you can verify this by running it offline, which is a perfectly normal way to use it.

What is stored, and where

Models sit where you put them. Results and cached previews sit in the app's own folder on your disk. Settings are a local file. Deleting the app takes all of it with you.

Store purchases

The Premium unlock is handled entirely by the Microsoft Store, the Mac App Store or Google Play, which means we never see a payment detail. Restoring a purchase on a new device goes through the same store mechanism: the app asks the store what it owns.

Reporting content

Results carry a Report button. It opens this site's report page with the record placed after the # in the address, a part browsers never send to a server; that page has no analytics and no third-party scripts. Nothing reaches us until you send the email or open the GitHub issue yourself, and a GitHub issue is public.

When something goes wrong

What you see What it usually means
Generation is far slower than you expected The run has fallen back to CPU. Check the backend selection, confirm the Premium unlock if you are relying on an accelerated backend, and try a smaller model or a smaller output size.
A run stops or the app runs out of memory The model does not fit. Drop the resolution, use a more heavily quantised model, close other applications, or move down one tier in hardware expectations.
A model will not load Usually an incomplete download or a missing companion file — image models need a matching VAE, video models need their text encoder. Re-fetch the file and check the pair.
Your prompt was refused The prompt gate declined it before any work started. Rephrase and run again; nothing was downloaded and nothing was recorded.
A result came back as a grey placeholder The output gate replaced a frame that scored over the safety threshold. Adjusting the prompt is usually enough.
Images are blurry or washed out Steps too low, guidance too high, or a size the model was not trained for. Return to the model's native resolution first, then adjust one number at a time.
A transcription is full of mistakes Audio quality dominates here. Try a larger Whisper-family model, and if the recording has overlapping speakers expect to edit.