Hidden Line Removal Makes Your 3D Model Sound Better
Hidden line removal draws a 3D model as a solid object instead of a see-through wire cage, and on an oscilloscope that changes the sound as well as the picture: the beam's path is the waveform. In BeamTracer's OSC-1 oscilloscope the control is HIDE HIDDEN LINES, it sits in the 3D IMPORT panel, and it is on by default.
Hi, I'm Trina with BeamTracer.com — this one's about the 3D setting that changes your sound as much as your picture.
Hidden line removal sounds like a purely cosmetic setting. Draw the model as a solid object instead of a see-through wire cage, tidy up the picture, move on.
On an oscilloscope it's not cosmetic at all. The path the beam takes through your model is also the waveform you are listening to. Change which edges get drawn and you've changed the audio — not as a side effect, but by definition. That makes hidden line removal one of the few settings that's simultaneously a visual control and a sound-design control.
What does hidden line removal change on an oscilloscope?
- An oscilloscope draws with one moving point, and that point's position is the stereo signal. The drawing and the sound are the same object.
- A wire-frame draws every edge, including the ones on the far side of the model. Those edges are in the audio too.
- Removing them means the same drawing time is spent on fewer lines: each surviving line gets more of the beam, so the figure is brighter and cleaner and the tone is simpler.
- It also gives back a large slice of your scan budget — in the on/off comparison below, about a third of the points.
- In OSC-1 the control is HIDE HIDDEN LINES, and it's on by default.
No model loaded yet? The import workflow is covered start to finish in how to convert a 3D model to oscilloscope or laser art — this post picks up where that one leaves off.
An imported 3D model traced as a single beam path, with the live point count and what real hardware can draw sitting right beside it.
How does a 3D model turn into sound?
The mechanism is simpler than it looks.
The model is projected to a flat view, exactly like a shadow. That gives every edge a 2D start and end. Those edges are then ordered into one continuous route that a beam can physically travel — because a beam cannot be lifted off the screen the way a pen can be lifted off paper. The horizontal position of that route becomes the left channel and the vertical position becomes the right one.
Two consequences fall straight out of that:
- Every edge you draw costs time, and the time available per redraw is fixed. Draw more, and each line gets less of it.
- Every move between separate strokes is still drawn. Those are the faint diagonals you can see crossing the figure — the beam travelling. They are also the harshest thing in the signal, because an abrupt jump is the audio equivalent of a hard edge.
So the question "which edges should exist?" is not a rendering question. It is a question about what the thing sounds like.
What does the same model look like with and without the lines you can't see?
The same model, same framing, one toggle. Left: HIDE HIDDEN LINES on — the object reads as solid and the lines are bright. Right: off — the far side of the model is drawn through the near side, the figure is busier, and every line is dimmer.
The dimming on the right is the part people don't expect, and it's the clearest evidence that this is an audio setting.
Nothing about the beam's brightness was changed. The beam spends a fixed amount of time per redraw, so drawing more lines with it means less time on each line — and on a scope, time spent is brightness. The see-through version is paying for edges you cannot see with the visibility of the edges you can.
A single frame can't quite settle the argument, because occlusion only really announces itself when the model turns:
The same model rotating with HIDE HIDDEN LINES on. Edges stay hidden as they swing to the far side and reappear as they come round, which is what makes the trace read as a solid object — and the point count and the scan-limit readout move with the pose, because the drawing does.
How much scan budget does hidden line removal give back?
The panel shows the cost of the current trace against what real hardware can actually draw, computed from your live settings.
The same model with the toggle on (left) and off (right). Points fall from 3,745 to 2,439, and the oscilloscope readout goes from 2.3× over its limit to 1.5×.
That is roughly a third of the drawing gone — and the third that was contributing nothing you could see. What you do with the space you got back is the interesting part:
- Spend it on detail. Lower EDGE THRESHOLD to let finer creases through, now that there is room for them.
- Spend it on tone. Raise TRACE SPEED so the same path is spread across more refreshes. A slower redraw is a lower drawing frequency — a lower pitch — and it also gives the beam more time to make each corner properly, so corners come out sharper.
- Spend it on nothing. Staying under the limit is worth something on its own. Go over it and a real scope or projector redraws more slowly and the image visibly flickers.
For the pose and settings in that comparison:
| HIDE HIDDEN LINES on | HIDE HIDDEN LINES off | |
|---|---|---|
| How it reads | A solid object | A see-through wire cage |
| Points per redraw | 2,439 | 3,745 |
| Against a 48 kHz scope | 1.5× over | 2.3× over |
| Against a 30 kpps projector | 2.4× over | 3.7× over |
| Brightness per line | Higher — fewer lines share the beam | Lower — the same beam covers more path |
| Sound | Simpler; fewer jumps and fewer strokes in the waveform | Busier and harsher, with more travel between strokes |
| Costs anything on a single convex shape | No — identical either way | No |
The scope's ceiling is set by your sound card, because one drawn point costs one audio sample. A 96 kHz interface doubles the budget of a 48 kHz one. The laser ceiling is separate and mechanical — a projector is rated in points per second and its mirrors have mass.
How do you hear the difference in OSC-1?
Load a model, rotate it until one part sits behind another, then toggle HIDE HIDDEN LINES with the audio up. The figure goes solid, the point count drops, and the tone simplifies in the same instant — that is the whole argument in one click. Then spend the budget you got back and export.
- Open OSC-1 in Chrome or Edge and switch to PERFORMANCE mode
- Open IMPORT SHAPES → 3D IMPORT and load a preset model or a built-in shape such as BLOCKS
- Toggle 3D PREVIEW OFF so you are looking at the traced output rather than a shaded preview render
- Rotate the model a little with ROTATION X / Y / Z so one part sits behind another
- Toggle HIDE HIDDEN LINES and watch the figure and the point count change together
- Spend the budget back: lower EDGE THRESHOLD for finer creases, or raise TRACE SPEED and listen to the pitch drop
- Open EXPORT and save the result — 3D→XY writes a 192 kHz 16-bit stereo WAV, ILDA writes an ILDA V5 frame, SVG writes a vector path
Every control on that panel is documented in 3D Import Settings.
How does path order change the sound?
HIDE HIDDEN LINES decides which edges exist. The path stage decides what order they get drawn in, and that changes the sound too.
| Control | What it changes visually | What it changes sonically |
|---|---|---|
| HIDE HIDDEN LINES | Solid object versus see-through cage | Removes the occluded edges from the waveform entirely |
| PATH OPTIMIZATION | Shortens the travel between strokes | Less time spent on jumps, more on artwork |
| BLANKING POINTS | How long the beam takes to cross a gap | More points make the crossing gentler; fewer save budget but sharpen the step |
| JUMP THRESHOLD | How far apart two points must be to count as a jump | Decides how much of the figure is treated as travel rather than line |
| TRACE SPEED | How many refreshes one full redraw is spread over | Sets the drawing frequency — the pitch you hear |
The sound is the path, not the shape
If you take one thing from this table: two traces of the same model, ordered differently, look identical and sound different. The waveform comes from the specific route the beam takes, not from what the object looks like.
When does hidden line removal make no difference?
Being straight about the limits:
- On a single convex shape — a sphere, a cone, a cube seen head-on — there is nothing to hide, and the drawing is identical either way.
- Head-on symmetrical models can hide edges without looking any different, because the far edges land on top of the near ones. The picture won't change; the point count and the sound will. Rotate the model a little and the visual difference appears.
Traced as a bare outline with nothing inside?
That's the crease threshold, not the hidden-line setting, and it's not a failed import. Very smooth models have surfaces meeting at gentle angles, so nothing qualifies as a crease. Drop EDGE THRESHOLD from 30° to 15° or 10° and the interior detail comes back.
What should you read next?
The import workflow this article builds on is covered end to end in how to convert a 3D model to oscilloscope or laser art. If your file already contains a walk cycle or other motion, see converting an animated GLTF to XY audio.
For the wider principle — that every audio decision is also a visual one — what audio effects look like on an oscilloscope runs the same dictionary in the other direction.
Before sending any of this to a real projector, read the laser safety guide.
Trace a 3D model and hear the difference — free, no account required
OPEN OSC-1 OSCILLOSCOPE →Flip the setting and listen. beamtracer.com — see you in the next one.