Why Media Selection Needs a Space Between Finder and the Timeline

There is a step before editing

Before I start editing, there is almost no time to look through asset media. Without a rough edit already in place, I cannot even begin to explore what I need.

Still images. Audio files. LUTs. Overlays.

Some of them need to be played. Some need to be compared. Audio needs to be listened to. A LUT does not tell me much until I see it applied to an image. An overlay is difficult to judge without seeing it against actual footage.

None of this is editing yet.

But it is more than file management.

After years of working with media, I began to notice that this part of the workflow did not really have a place of its own.

Finder manages files

Finder is where my files belong.

I use folders to define the structure of a project, and I want the original media to remain there. I do not want to move files into another library simply because I need to look at them.

Finder is very good at this job.

It tells me where something is. It lets me organize, rename, move and copy files. Quick Look can also give me a fast look at many formats.

But there is a difference between seeing a file and evaluating it.

When I am deciding whether a clip, sound, LUT or overlay belongs in an edit, the question is no longer:

Where is this file?

The question becomes:

Is this the one I want to use?

That is a different task.

The editing application comes later

An editing application can answer that question, of course.

I can import the files, create bins, put clips on a timeline, apply LUTs, stack overlays and start testing combinations.

But that always felt slightly backwards to me.

I was putting material into the editing environment in order to decide whether I wanted to put it into the editing environment.

For a few files, this does not matter.

For a folder containing hundreds or thousands of assets collected over years of production, it does.

The project starts accumulating material before I have decided that the material belongs there.

I wanted to make some of those decisions earlier.

The missing step is selection

I eventually started thinking of this as a separate layer in the workflow.

There is file management.

There is editing.

And between them, there is selection.

Selection is not just choosing a filename from a list.

It means understanding enough about an asset to make a decision about it.

For footage I shot myself, that may mean playing the clip and checking its duration, frame rate, codec or resolution.

For audio, it may mean seeing the waveform and listening to it.

For two similar assets, it may mean putting them side by side.

For a LUT, it may mean applying it to a known reference image.

For an overlay, it may mean seeing how it interacts with an actual image rather than looking at the overlay in isolation.

These are small actions individually.

Together, they form a distinct stage of work.

Some media cannot be judged alone

This became particularly obvious with LUTs and overlays.

A .cube file has almost no useful visual meaning by itself.

Its filename may give me a clue, but the thing I actually care about is what it does to an image.

The same is true of many overlays.

A light leak, film burn or texture viewed against black is not necessarily what I will see when it is composited over footage.

The asset needs context.

This changed how I thought about previewing.

A preview does not always mean showing the contents of one file.

Sometimes previewing means showing the relationship between two things.

A LUT and an image.

An overlay and a shot.

One clip and another clip.

Once I saw the problem that way, simple file thumbnails were no longer enough.

I did not want another library

The obvious solution would have been to build a media library.

Import files, generate a catalog, add tags, organize collections and manage everything inside the application.

I deliberately did not do that.

The folders already exist.

They are already part of the production workflow. They may live on an internal drive, an external SSD or a project archive. Other applications already depend on those locations.

Creating another organizational layer would mean maintaining two representations of the same material.

I wanted the filesystem to remain the source of truth.

So GyoKan Select reads media directly from local folders.

The files stay where they are.

When I find something I want, I can drag the original file from GyoKan into the application where I actually intend to use it.

GyoKan does not need to become the owner of the media.

It only needs to help me make the decision.

The space between Finder and the timeline

That became the basic idea behind GyoKan Select.

Finder manages the files.

The editing application edits them.

GyoKan occupies the space between those two jobs.

It is a place where I can browse local folders, inspect different kinds of media, compare assets and test media that only makes sense in context before committing anything to an edit.

This distinction also shaped how I think about the product.

I do not want GyoKan to become a replacement for Finder.

I do not want it to become a DAM.

I do not want it to become a lightweight editing application.

Each of those would pull it away from the problem I originally wanted to solve.

The useful boundary is narrower:

understand the material, make a decision, and move on.

Why I built GyoKan Select

For a long time, I treated this part of the workflow as a collection of small inconveniences.

Open this file in Quick Look.

Play that clip somewhere else.

Import a LUT to see what it does.

Drop an overlay onto a timeline just to test it.

Switch back to Finder.

Find the next file.

None of those steps is particularly difficult.

The friction comes from repeating them and from constantly moving between tools designed for different stages of the workflow.

Eventually I stopped seeing that friction as a collection of missing features.

I saw a missing place.

I did not want to replace Finder, and I did not want to build another media library.

I wanted a place to understand media before committing it to an edit.

GyoKan Select grew out of that missing space.