# GUI Overview

In this section, we are going to look at the differences and similarities between the graphics user interface of Disguise and LightAct software.

<figure><img src="/files/IoYI3x3oyxvPekk5CtMr" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Good to know:** unlike Disguise, LightAct uses dockable windows, that you can save into Workspaces. This allows you to modify the GUI and save it for future use.
{% endhint %}

## Dashboard

The closest thing to Disguise's Dashboard is LightAct's [Top Bar](/quick-start/user-interface/top-bar.md) where you can see all the Windows in LightAct software.

## Track Editor

Using the Track Editor in Disguise, you could play and edit all Tracks within a single project. Here is where you placed the desired Content Layers on the Timeline.

In LightAct, the term Track refers to a lane along which you can place layers in the [Timeline](broken://pages/gVo5IggqA2Ti6LFoq45y). Consequently, a Timeline can have lots of tracks, populated with different [Layers](broken://pages/uGObavuxs9guD7Ph8k4i), such as video, notch, image layers, or others.

{% hint style="info" %}
**Good to know:** Unlike Disguise, layers in LightAct are not strictly defined and are completely customizable.
{% endhint %}

LightAct also fosters the term Timeline, although a Timeline in LightAct typically contains one or more Timeline tracks. You can have multiple Timelines in a single project, which you can add and manage in the [Timelines window](broken://pages/s5uC9iAZKeosFNoPuwDQ).

## Stage

All your objects in Disguise could be visualized on the Stage. Similarly, in LightAct, all Viewport Objects can be seen in the [Viewport window](/quick-start/user-interface/viewport-navigation.md).

## Feed

The equivalent to the Feed level in Disguise, would be the [Output Maps Window ](broken://pages/lG8qiETTr6xQ57Jc5mWO)in LightAct.

## Devices

In Disguise you used to add devices in the form of a list displayed in the Devices Editor. In LightAct, devices are inserted in the form of nodes, in the Devices window.

Here, you can both receive or output from and to different [Network devices](/integrations/network.md), [Trackers](broken://pages/ZYGqSdzGrDzYelwMoooh), [MIDI](/osc-and-midi/midi.md), [Content I/O](/integrations/content-io.md), or [Audio devices](/integrations/audio.md).

{% hint style="info" %}
**Good to know:** In Disguise, you could create a DmxDevice, just like you created any other device type. In LightAct, you can receive or send DMX data by using the dedicated DMX In and DMX Out windows, instead of the generic Devices Window.
{% endhint %}

## Transport

In Disguise, Timecode configuration happened in the Transport Editor of the Dashboard. In LightAct, you can receive timecode data, such as LTC or MIDI in the Devices Window.

To find out more about syncing a Timeline to a Timecode, please read [this section](https://app.gitbook.com/o/jm10Bq9qF0zSG9DcWnyq/s/9sVaJpWJhPbmscipukhh/~/changes/232/understanding-the-basics/lightact-for-operators/lightact-for-disguise-operators/sequencing#multitransport-manager).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lightact.com/transitioning-to-lightact-from-other-media-servers/lightact-for-disguise-operators/gui-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.