+
About
+ +This is the about page.
+ +diff --git a/content/user_docs/Watching Clips/watch.md b/content/user_docs/Watching Clips/watch.md index 8270704..ddf4cc2 100644 --- a/content/user_docs/Watching Clips/watch.md +++ b/content/user_docs/Watching Clips/watch.md @@ -28,6 +28,9 @@ And there is a timecode box in the top left: This timecode box can be moved anywhere in the player window by dragging it to where you'd like it to be. You can reset the position of the timecode or disable the timecode box using the [user settings menu.](/user_docs/user_settings) +It is possible to navigate to a specific timecode by simply entering it whilst the page is active. + +If the timecode you want to go to is `10:03:05:00` pressing the 1 key will bring up the timecode navigation window. From there enter the rest of the timecode with no spaces or other punctuation. So you would enter: `10030500` and press enter. This will navigate to that timecode in the file. #### Audio Selection For clips that have more than one track of audio, you can select the track to play back by clicking on the headphone icon on the playbar and selecting the audio track. Glympse by default creates a full mix of all the audio channels and plays this by default. diff --git a/content/user_docs/review/_index.md b/content/user_docs/review/_index.md new file mode 100644 index 0000000..00976c1 --- /dev/null +++ b/content/user_docs/review/_index.md @@ -0,0 +1,8 @@ +--- +title: Review +next: /user_docs/review/upload_and_manage_files +--- + +Glympse has the ability to upload files for review and approval. Once you upload a file to Glympse, you can add markers and send the file to people within your team using and internal link or to anyone using the create link function. + + diff --git a/content/user_docs/review/folders.md b/content/user_docs/review/folders.md new file mode 100644 index 0000000..28b1c5b --- /dev/null +++ b/content/user_docs/review/folders.md @@ -0,0 +1,27 @@ +--- +title: Folders +type: docs +next: /user_docs/review +--- +By default when you upload a file, they will be in the root of the review table. This may be preferable when there are one or two files uploaded, but once you start to get more and more files uploaded, you may want to organise the files into subdirectories or folders. + +To add a folder click the New Folder button and enter a name for the folder. + + + +This will be added to the Home page, you can drag files into this folder, alternatively, if you enter a folder and then click upload, it will upload the file directly to this folder. + + +When you drag a file into a folder, the row of the folder you have selected will be highlighted green, release the file and it wil be added to this folder. + +Alternatively you can use the menu for each folder or item to move files. + +Click the dropdown menu button for the file or menu you wish to move and select Move. + +This will bring a folder tree where you can click on the folder you wish to move the files to. + + + +Click save changes and the file(s) will be moved. + +From the dropdown menu you can also rename files/folders as well as move them to the bin. Files in the bin will permanently deleted after 30 days. \ No newline at end of file diff --git a/content/user_docs/review/share_file.md b/content/user_docs/review/share_file.md new file mode 100644 index 0000000..41a2c63 --- /dev/null +++ b/content/user_docs/review/share_file.md @@ -0,0 +1,24 @@ +--- +title: Share File +type: docs +next: /user_docs/review +--- +It is posible to share the review file to anyone who is in the production group by simply copying the link from the browser. + +If you want to share a link with someone who doesn't have access or is not a Glympse user, you will need to create a link using the share dialogue. + +From the video review page, click share in the menu bar, then `generate share link` + +This will show you all the links for this file as well as the internal link that can be shared with Glympse users. + + +To create a new link, click Generate link. This will allow you to set some options for the link. + + +You can add a password, an expiry date and select whether the file should be downloadable from this link. + + +Click generate and a new link will be created with the selected options. + + +You can copy or delete any created links for the file. \ No newline at end of file diff --git a/content/user_docs/review/upload_and_manage_files.md b/content/user_docs/review/upload_and_manage_files.md new file mode 100644 index 0000000..91bcead --- /dev/null +++ b/content/user_docs/review/upload_and_manage_files.md @@ -0,0 +1,44 @@ +--- +title: Upload Files +type: docs +next: /user_docs/review +--- +## Upload +To upload a file, navigate to the review section of Glympse and click upload in the top right. + + +This will take you to the upload form. + +Every file you upload must belong to a production. + +### Existing Production +To upload to an existing production simply select it from the drop down menu. + +Next either select the file to upload or give it a title. If you leave the File Name field blank, by default it will use the filename of your selected file. + +Select the file you'd like to upload by either dragging and dropping it into the upload box or clicking inside the box to bring the file select dialogue. + + + + + +Once you have selected your file click upload and it will start uploading. + +### New Production +To upload a file to a new production, you will first need to create the Production. From the review upload page, click the blue + button. + + +This will open the Add Production Modal. This is similar to adding a normal production, only here you don't need to select a directory to scan for rushes or add a priority. + + +Once you click submit, the production will be created and automatically selected on the upload form. + + +Select or drag and drop your file and click upload. + +## Cancel upload +If you need to cancel an upload, you can stop and remove it by pressing the red X icon that shows when you hover your mouse over the progress bar. + + +## Resume upload +If for whatever reason the upload fails, you can resume the upload by submitting the same file with the same information and it will continue the upload from where it left off. \ No newline at end of file diff --git a/content/user_docs/review/watch_review.md b/content/user_docs/review/watch_review.md new file mode 100644 index 0000000..47812ba --- /dev/null +++ b/content/user_docs/review/watch_review.md @@ -0,0 +1,47 @@ +--- +title: Watch and Review Files +type: docs +next: /user_docs/review +--- +When you click on a file title from the review page, you will be taken the file viewing page. The viewing experience is similar to that of watching rushes, however with review files, multiple qualities are created. This allows for higher resolution viewing of a file. + +It is also possible for anyone with download access to download the original file. Download access is given to all users in the production group or is specifically given when creating a download link. + + + +You can play the video file and add markers as you watch. + +## Add Markers +Whilst the video is playing, you can add a marker by clicking in the box that says "Enter your notes here". This will pause the video whilst you add your text. + +You can change the type of marker by pressing the change marker button: + + +This will bring up a menu with the available marker types. Select the type you want to add and the marker button will change colour. + + + +When you have entered your text in the box, click the save button or press `enter` + + +The marker will be added to the right hand side of the video player. + + +Any markers added by you or others will appear here. MArkers will be added live if there are others reviewing the file at the same time. + +Clicking on the timecode of the marker will navigate the player to that timecode. + +It is also possible to change the marker type after it has been added. The process is the same, click the change marker type button on the marker itself and select a new marker type. + + + +If you added the marker, it's also possible to change the marker text. It is also only possible for the person who added a marker to delete it. + +Hover over the marker and the delete button will appear. + + +You can reply to any marker by pressing the reply button on a marker. This will allow you to add a reply to the markers. + + +Again, only the person who adds the note can delete it. Unless the marker it's applied to is deleted by someone else. + diff --git a/create share.png b/create share.png new file mode 100644 index 0000000..e9394f5 Binary files /dev/null and b/create share.png differ diff --git a/isableFastRender/404.html b/isableFastRender/404.html new file mode 100644 index 0000000..12e77eb --- /dev/null +++ b/isableFastRender/404.html @@ -0,0 +1,27 @@ +
This is the about page.
+ +To install you will first need the database and queue manager running. Every instance of Glympse you run will need to connect to these containers.
+First create your docker network. docker network create glympse_net
Then create a a directory and compose file:
+mkdir /opt/glympse_database
+
+cd /opt/glympse_database
+
+nano /opt/glympse_database/compose.ymlPaste the following, be sure to change the passwords and any other personal details before saving.
+services:
+ redis:
+ image: redis:alpine
+ container_name: redis
+ restart: always
+ ports:
+ - 6379:6379
+ volumes:
+ - /opt/glympse_database/redis_data:/data
+ healthcheck:
+ test:
+ - CMD
+ - redis-cli
+ - ping
+ interval: 30s
+ timeout: 10s
+ retries: 3
+ networks:
+ glympse_net: null
+ rabbitmq:
+ image: rabbitmq:3.13.4-management
+ container_name: rabbitmq
+ volumes:
+ - type: bind
+ source: /opt/glympse_database/rabbitmq.conf
+ target: /etc/rabbitmq/conf.d/10-defaults.conf
+ ports:
+ - 15672:15672
+ - 5672:5672
+ networks:
+ glympse_net: null
+ mysql:
+ image: mysql:8.0
+ container_name: mysql
+ environment:
+ MYSQL_ROOT_PASSWORD: <root password>
+ MYSQL_DATABASE: glympse
+ MYSQL_USER: glympse
+ MYSQL_PASSWORD: <glympse password>
+ volumes:
+ - /opt/glympse/mysql:/var/lib/mysql
+ - type: bind
+ source: /opt/glympse_database/my.cnf
+ target: /etc/my.cnf
+ ports:
+ - 6033:6033
+ - 3306:3306
+ networks:
+ glympse_net: null
+networks:
+ glympse_net:
+ external: trueThere are two more files that you need to create and save before running the compose file.
+First is the mysql config file.
+Create a file called my.cnf in the glympse_database directory: nano my.cnf and paste the following:
# For advice on how to change settings please see
+# http://dev.mysql.com/doc/refman/8.0/en/server-configuration-defaults.html
+
+[mysqld]
+#
+# Remove leading # and set to the amount of RAM for the most important data
+# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
+# innodb_buffer_pool_size = 128M
+#
+# Remove leading # to turn on a very important data integrity option: logging
+# changes to the binary log between backups.
+# log_bin
+#
+# Remove leading # to set options mainly useful for reporting servers.
+# The server defaults are faster for transactions and fast SELECTs.
+# Adjust sizes as needed, experiment to find the optimal values.
+# join_buffer_size = 128M
+# sort_buffer_size = 2M
+# read_rnd_buffer_size = 2M
+
+# Remove leading # to revert to previous value for default_authentication_plugin,
+# this will increase compatibility with older clients. For background, see:
+# https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_default_authentication_plugin
+# default-authentication-plugin=mysql_native_password
+skip-host-cache
+skip-name-resolve
+datadir=/var/lib/mysql
+socket=/var/run/mysqld/mysqld.sock
+secure-file-priv=/var/lib/mysql-files
+user=mysql
+connect_timeout = 600
+net_read_timeout = 30
+wait_timeout = 28800
+interactive_timeout = 28800
+
+pid-file=/var/run/mysqld/mysqld.pid
+[client]
+socket=/var/run/mysqld/mysqld.sock
+
+!includedir /etc/mysql/conf.d/Finally create a config file for rabbitmq: nano rabbitmq.conf and paste the following:
be sure to change the password for something secure and keep note of it as you will need it for your compose env files.
+default_vhost = glympse
+default_user = glympse
+default_pass = <enter password>
+default_permissions.configure = .*
+default_permissions.read = .*
+default_permissions.write = .*
+default_user_tags.administrator = true
+default_user_tags.management = true
+default_user_tags.glympse = true
+consumer_timeout = 31622400000To install Glympse, you will need a database, a redis cache and a rabbitmq queue all of which must be accessible by all of the Glympse containers you deploy. For that reason it is recommended to keep this as a separate compose file.
+ + + +To install glympse we first need to create a docker compose file and then an env file. These two files will allow you to configure most out of the box settings. Once you’re set these up, you will be able to change more setting from the webui.
+Services default to enabled, to disable a service, change yes to no in the environment section of the compose file. To enable a service, either change the environment variable to yes or delete/comment the line.
+UWSGI and NGINX are required for the webui service
+The following compose file will enable all services in a single container. This will work but it is possible that the transcoding and transcribing tasks can slow down the webui if you’re running on a slower machine.
+If you are going to be running the transcoder or the transcription engine, you will need an Nvidia GPU. To find the device ID run nvidia_smi on the system you will be installing the container.
+This will give you an output that looks like this:
+-----------------------------------------------------------------------------------------+
+| NVIDIA-SMI 565.57.02 Driver Version: 566.03 CUDA Version: 12.7 |
+|-----------------------------------------+------------------------+----------------------+
+| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
+| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
+| | | MIG M. |
+|=========================================+========================+======================|
+| 0 NVIDIA GeForce GTX 1080 On | 00000000:01:00.0 On | N/A |
+| 27% 38C P8 8W / 180W | 893MiB / 8192MiB | 1% Default |
+| | | N/A |
++-----------------------------------------+------------------------+----------------------+
+
++-----------------------------------------------------------------------------------------+
+| Processes: |
+| GPU GI CI PID Type Process name GPU Memory |
+| ID ID Usage |
+|=========================================================================================|
+| 0 N/A N/A 26 G /Xwayland N/A |
++-----------------------------------------------------------------------------------------+The device id is in the third row, just above the memory:
++========================+
+| 00000000:01:00.0 On |
+| 893MiB / 8192MiB |
+| |
++------------------------+In this case the device id is: 00000000:01:00.0
Add this to your compose file. A file that runs all services with a gpu looks like:
+services:
+ Glympse_net:
+ image: git.themainframe.co.uk/josh/glympse
+ container_name: Glympse
+ restart: unless-stopped
+ ports:
+ - 8080:80
+ environment:
+ TZ: Europe/London
+ ENABLE_UWSGI: yes
+ ENABLE_NGINX: yes
+ ENABLE_CELERY_BEAT: yes
+ ENABLE_PROCESSING: yes
+ ENABLE_MIGRATIONS: yes
+ ENABLE_TRANSCRIBER: yes
+ ENABLE_TRANSCODER: yes
+ DJANGO_SETTINGS_MODULE: Glympse.settings.production
+ SECRET_KEY: "super_secret_key"
+ SECRET_ADMIN_URL: random_string
+ CSRF_TRUSTED_ORIGINS: http://127.0.0.1
+ ALLOWED_HOSTS: 127.0.0.1
+ ADMINS: admin@glympsevideo.com
+ DOMAIN: glympse.glympsevideo.com
+ SQL_ENGINE: django.db.backends.mysql
+ SQL_DATABASE: glympse
+ SQL_USER: glympse
+ SQL_PASSWORD: insecure_password
+ SQL_HOST: mysql
+ SQL_PORT: 3306
+ EMAIL_HOST: mail.themainframe.co.uk
+ EMAIL_PORT: 587
+ EMAIL_USE_TLS: true
+ EMAIL_HOST_USER: noreply@glympsevideo.com
+ EMAIL_HOST_PASSWORD: insecure_password
+ DEFAULT_FROM_EMAIL: Glympse<glympse@glympsevideo.com>
+ ALLOWED_EMAIL_DOMAINS: glympsevideo.com
+ REDIS_HOST: redis://redis:6379
+ RABBITMQ_URL: amqp://glympse:insecure_password@rabbitmq:5672/glympse
+ ADMIN_USERNAME: hub
+ ADMIN_EMAIL: admin@glympsevideo.com
+ ADMIN_PASSWORD: insecure_password
+ LOG_LEVEL: DEBUG
+ TIMEZONE: Europe/London
+ MICROSOFT_AUTH_CLIENT_ID: None
+ MICROSOFT_AUTH_CLIENT_SECRET: None
+ MICROSOFT_AUTH_TENANT_ID: None
+ MEMCACHED: memcached:11211
+ CUDA_DEVICE: cuda:0
+ DEBUG: "True"
+ REMOTE_WORKER: "False"
+ REMOTE_PRODUCTION: None
+ volumes:
+ - /opt/glympse/logs:/Glympse/logs
+ - /media:/media
+ - /rushes:/rushes:ro
+ deploy:
+ resources:
+ reservations:
+ devices:
+ - driver: nvidia
+ device_ids:
+ - 00000000:01:00.0
+ capabilities:
+ - gpu
+ networks:
+ glympse_net: null
+ memcached:
+ image: memcached:latest
+ container_name: memcached
+ entrypoint: memcached -m 256
+ restart: unless-stopped
+ networks:
+ glympse_net: null
+networks:
+ glympse_net:
+ external: trueIf you are install Glympse on a second system or a system other than where the raw camera files are stored you can use the following to mount the volumes as smb shares:
+volumes:
+ rushes:
+ driver: local
+ driver_opts:
+ type: cifs
+ o: username=<sbm_username>,password=<smb_password>,ro,domain=localhost
+ device: \\smb\share\pathAlternatively you can use a nfs share:
+volumes:
+ rushes:
+ driver_opts:
+ type: nfs
+ o: "addr=<nfs-server-ip>,nolock,soft,rw"
+ device: ":/full/share/path"You will need to make sure that if you are mounting the raw rushes volume that you mount this as ro or read only so Glympse can not make any changes to the raw rushes.
If you are mounting the glympse mediafiles or logs, you will need to mount this as rw or read write so Glympse can create the files.
Glympse is split into multiple services so you can split the workload between multiple machines.
+The available services are as follows:
+Celery Beat
+You should only have one of these running across all your containers. This is responsible for managing the scheduled tasks. Without this, the scheduled tasks will not run. For ease, I usually run this in the same container as the webui.
WebUI
+This is the webui front end. The reverse proxy needs to point to the machine that is running this service. It is possible to run more than one frontend for load balancing purposes.
Processing
+This service is responsible for scanning the rushes drives and inserting the rushes into the Glympse database. It is also responsible for other background tasks such as sending emails etc. This worker will run 16 simultaneous tasks.
Transcoding - Prefers Nvidia GPU
+This is the transcoding engine. It takes the raw rushes and transcodes them to lower resolution proxy files that can be streamed. The transcoder will try use cuda hardware acceleration but will fall back to software if it is unavailable. This worker will run 4 simultaneous tasks.
Long Transcoding
+This was set up to create the thumbnail preview for the video player when you hover over the video play bar to allow for scrubbing. This worker will run 16 simultaneous tasks.
Transcribing - Requires Nvidia GPU
+This is responsible for transcribing clips. A modern Nvidia GPU is required for this to work. It is possible to select a different model that may better suit the available hardware. A GPU with more VRAM can support a larger model. This worker will run a single task at a time.
It is possible to run one or more services in a single docker container. the running services are managed through the environment settings in the compose file.
+ +You can manage most of the admin settings from the front end. When a user is assigned admin permissions or is joined to the “hub” group they will have access to the admin menu on the webUI.
+Access the dashboard page. This give you an overview of the system. It will show some figures like how many clips are waiting to be transcoded or how many clips have been transcribed. It also shows you all running tasks and will also show who is currently online.
+You can also trigger the periodic tasks from the bottom of this page.
+View the system logs.
+This brings up the add production modal where you can add a production. This is the same interface as pressing the add production button on the home page.
+Here you can edit productions.
+This is who is responsible for the production. It’s likely that this should be the edit assistant assigned to the production. You can change this here, this person will receive the emails after the production has been scanned.
+Click the image to upload a new thumbnail image for the production. Or reset it.
+An active production will be scanned for new rushes. A deactivated production will still be available to users.
+This will remove the production from being able to be viewed. All files will remain, they will just be hidden.
+This will export a json file containing the database entries for this production that can be archived to another system along with the media files. The media files will have to be manually backed up from your server. Once you have backed up the json file and the media, you can delete the production.
+This will delete the production and all the clips associated with it.
+Select a user from the dropdown menu and you can assign the user to a group. You can also deactivate the user which will keep the account but not allow the user to log in. Or you can delete the user which will delete their account completely.
+If the user was created by logging in via SSO, they will still be able to log in once they have been deleted. But they will have no permissions and won’t be assigned to a group so will not have access to any productions.
+You can enable the ability for users to scan or start a production transcoder. They will only be able to scan or transcode the productions they have access to.
+Clicking on the number beside their name at the top will enter the impersonation for this user. This is useful if you need to check a user has the correct permissions.
+You can add a local user by clicking the blue + button at the top.
+When a base production is added, a new group of the same name will be created.
+From this page you can select a group and assign productions to it. Users assigned to this group will then be able to access these productions.
+You can add a new group by clicking the blue + button at the top right.
+From this page you can
+This will open the django admin setting page.
+Here you can send an email to registered users. +Either select an existing email draft or click new to create a new one.
+This will take you to the editor page. Set the Subject at the top, then select a date and time to send the email. Not setting this will send immediately.
+Select the recipients of the email and draft the email below.
+The editor is a WYSIWYG editor so the email body will appear exactly as it does in this editor. You can add images and graphics to the email body should you wish.
+Click save and preview. This will show you a copy of what the email will look like when sent. You will be able to either schedule the send or edit the email again after this point.
+Click Delete to delete the email draft.
+This clears the cache of the system. Useful if there have been large database changes. By default the system caches data for around 10 minutes.
+Users may have to force refresh their browser to clear their local cache if the changes aren’t appearing for them.
+ +The admin settings page is where you can change almost everything. If it’s in the database, it’s likely you can make changes here.
+See here for more information
+Default: small
| Size | +Parameters | +English-only model | +Multilingual model | +Required VRAM | +Relative speed | +
|---|---|---|---|---|---|
| tiny | +39 M | +tiny.en | +tiny | +~1 GB | +~10x | +
| base | +74 M | +base.en | +base | +~1 GB | +~7x | +
| small | +244 M | +small.en | +small | +~2 GB | +~4x | +
| medium | +769 M | +medium.en | +medium | +~5 GB | +~2x | +
| large | +1550 M | +N/A | +large | +~10 GB | +1x | +
| turbo | +809 M | +N/A | +turbo | +~6 GB | +~8x | +
Here you can manage the advanced settings of the users and Groups. Most of these settings can be changed from the front end without coming into the Django Admin page.
+Here you can view the logs for the impersonation.
+These are created when installed. Should you wish to change the time the tasks run, you would do so in the Periodic Tasks section.
+These run once at a specific date and time.
+This is where you can set advanced schedules using cron. See here for more information about Cron
+These will allow you to let a task run at specific intervals, e.g. run once every hour.
+This is where you register or change the tasks, To change the schedule, you will need to create the schedule using one of the above options and then select it in this page.
+You can also enable and disable tasks here as well as override the priority of the task.
+This is where you can see all the files that have been uploaded for review. You can retranscode or delete the files from here.
+Add, edit or delete the share links for files here.
+You can make changes to the metadata of the clips or add or remove the productions here. But most of these tasks can and should be done in the front end.
+Add or edit the base productions. You can also change the group that the Base Production is assigned to.
+Here you can make changes to the production such as the name, friendly name, filepath etc. You can also trigger some tasks from this page such as the file scan or the transcoder.
+Here you can see and edit all the metadata for the clips in the Glympse database.
+Here you can see all of the clips that have been sent to the transcription engine. You can trigger tasks such as re-transcribe or delete the files from here.
+ +There are two main ways to change settings for Glympse. The first is the env file, the second is to change some settings from within the application. This can be done whilst the server is up and running from a central point, whereas changes to the env file will need to be replicated on each docker container.
+ +When you click Edit on the metadata page you will be taken to the edit page. This shows a table with all the clips for that production. You can see whether a clip has been transcoded, is marked as hidden or edit the metadata of the clip(s)
+
There are limited options for editing the metadata. You can edit only the roll, the date and the shooter aswell as hide or unhide a clip.
+To edit a clip select it by checking the checkbox of the clip row. At the bottom of the table you can enter a new roll/date/shooter then click save to save the edits.
+Whatever you entered in all three boxes will be applied to the selected clips. Leave the box empty to leave the current details unchanged.
+You can also hide/unhide clips by checking the hide checkbox. As soon as you click the checkbox it will be immediately hidden. It is possible that the clips may still appear until the cache has ben flushed. This process can take 10-15 minutes.
+From this page you can also send multiple clips to the transcription engine.
+Select the clips by checking the checkbox and click transcribe. This w3ill send the selected clips to be transcribed.
+You can also delete clips from the Glympse database.
+Glympse has read only access to the raw camera files, by deleting clips from Glympse, the original camera files will be unaffected.
+ +It is possible to edit some of the metadata for the clips within Glympse.
+Any metadata changes apply only to the Glympse database and are not carried over to the clips themselves.
+To edit the metadata of the clips, click “Edit Clips” in the top right. This will look like the home page where you can select your production. +Click the Edit button to edit the clip metadata.
+
Welcome to the user documentation of Glympse.
+Glympse is designed to be as intuitive as possible, so hopefully you won’t need to read this but its here if you need.
+ +By default when you upload a file, they will be in the root of the review table. This may be preferable when there are one or two files uploaded, but once you start to get more and more files uploaded, you may want to organise the files into subdirectories or folders.
+To add a folder click the New Folder button and enter a name for the folder.
+
+
This will be added to the Home page, you can drag files into this folder, alternatively, if you enter a folder and then click upload, it will upload the file directly to this folder.
+
When you drag a file into a folder, the row of the folder you have selected will be highlighted green, release the file and it wil be added to this folder.
+Alternatively you can use the menu for each folder or item to move files.
+Click the dropdown menu button for the file or menu you wish to move and select Move.
+
+This will bring a folder tree where you can click on the folder you wish to move the files to.

Click save changes and the file(s) will be moved.
+From the dropdown menu you can also rename files/folders as well as move them to the bin. Files in the bin will permanently deleted after 30 days.
+ +Glympse has the ability to upload files for review and approval. Once you upload a file to Glympse, you can add markers and send the file to people within your team using and internal link or to anyone using the create link function.
+ +It is posible to share the review file to anyone who is in the production group by simply copying the link from the browser.
+If you want to share a link with someone who doesn’t have access or is not a Glympse user, you will need to create a link using the share dialogue.
+From the video review page, click share in the menu bar, then generate share link
This will show you all the links for this file as well as the internal link that can be shared with Glympse users.
+
To create a new link, click Generate link. This will allow you to set some options for the link.
+
You can add a password, an expiry date and select whether the file should be downloadable from this link.
+
Click generate and a new link will be created with the selected options.
+
You can copy or delete any created links for the file.
+ +To upload a file, navigate to the review section of Glympse and click upload in the top right.
+
This will take you to the upload form.
+Every file you upload must belong to a production.
+To upload to an existing production simply select it from the drop down menu.
+Next either select the file to upload or give it a title. If you leave the File Name field blank, by default it will use the filename of your selected file.
+Select the file you’d like to upload by either dragging and dropping it into the upload box or clicking inside the box to bring the file select dialogue.
+

Once you have selected your file click upload and it will start uploading.
+To upload a file to a new production, you will first need to create the Production. From the review upload page, click the blue + button.
+
This will open the Add Production Modal. This is similar to adding a normal production, only here you don’t need to select a directory to scan for rushes or add a priority.
+
Once you click submit, the production will be created and automatically selected on the upload form.
+
Select or drag and drop your file and click upload.
+If you need to cancel an upload, you can stop and remove it by pressing the red X icon that shows when you hover your mouse over the progress bar.
+
If for whatever reason the upload fails, you can resume the upload by submitting the same file with the same information and it will continue the upload from where it left off.
+ +When you click on a file title from the review page, you will be taken the file viewing page. The viewing experience is similar to that of watching rushes, however with review files, multiple qualities are created. This allows for higher resolution viewing of a file.
+It is also possible for anyone with download access to download the original file. Download access is given to all users in the production group or is specifically given when creating a download link.
+
You can play the video file and add markers as you watch.
+Whilst the video is playing, you can add a marker by clicking in the box that says “Enter your notes here”. This will pause the video whilst you add your text.
+You can change the type of marker by pressing the change marker button:
+
This will bring up a menu with the available marker types. Select the type you want to add and the marker button will change colour.
+
When you have entered your text in the box, click the save button or press enter
+
The marker will be added to the right hand side of the video player.
+
Any markers added by you or others will appear here. MArkers will be added live if there are others reviewing the file at the same time.
+Clicking on the timecode of the marker will navigate the player to that timecode.
+It is also possible to change the marker type after it has been added. The process is the same, click the change marker type button on the marker itself and select a new marker type.
+
If you added the marker, it’s also possible to change the marker text. It is also only possible for the person who added a marker to delete it.
+Hover over the marker and the delete button will appear.
+
You can reply to any marker by pressing the reply button on a marker. This will allow you to add a reply to the markers.
+
Again, only the person who adds the note can delete it. Unless the marker it’s applied to is deleted by someone else.
+ +To add a production click the “Add Production” button in the top right of the home page.
+This will bring up the dialogue to add a new production.
+
+A production consists of two parts. The Base Production and the Production.
For example your Base Production may be “Game of Thrones” then the Production could be “Game of Thrones Series 1”
+Select the Base Production, if it doesn’t exist create it by clicking the button next to the select dropdown.
+Enter the new name of your production and click submit.
+
+The name you entered will be automatically selected.
Enter the series of the production you are adding. This must be an integer.
+Enter a short friendly name for the series. This is what will appear on the default thumbnail. In this example we will enter GOTS1
Click on a directory to open it and select it by clicking the radio check mark on the left.
+
Most productions can be left as the default of 20. But if you have a smaller production or one where the transcodes need to be run before others you can change the priority here. 0 = lowest priority 100 = highest priority.
+This is who will be responsible for the production. They will get the emails to say that the production has been scanned etc. This will usually be the edit assistant assigned to the project. The user must exist in the Glympse system.
+If left empty, this will default to the admin user.
+Click submit and the production will be added to Glympse and the Processing engine will start scanning for new clips.
+
+Once You have been added to a production(s). You will see all your available productions on your home page. Under the thumbnail for each production you will see a list of buttons. The fist will let you view all the rushes from every shooter.

Under that you will see a list of the shooters from that project. Clicking on these will allow you to filter the production by that shooter.
+If we were to click on John Snow from either the home page or at the top of the rushes page. We will filter the rushes to show only those shot by John Snow.
+
At the top of the page, you can also click on the name of the shooter to filter the clips. Clicking on the shooter will only return results shot by the selected shooter. Clicking All or Reset will show all the rushes again.
+In the search bar, you can search for a card or date. The results will be filtered live as you type.
+Once you select a card, you’ll be taken to the video player screen.
+ +From the User Settings menu you can change some personal settings.
+
When checked, this will automatically add or remove tags on any related clips. When unchecked this, any tags you add or remove, will only be apply to the clips you have selected.
+This enables/disables the timecode box in the video player. Is is enabled by default, should you wish to disable it, you would do so here.
+Default: 16
+You can change the font size for the timecode box here. Increase to make the timecode larger, decrease to make it smaller.
+It is possible that the timecode box may disappear off the ege of the video player. Especially if you use multiple devices with different resolution screens. If that happens, you can reset it to the top left corner here.
+This will automatically expand the related clips accordion oin the right next to the player. If it is enabled, the related clips will be shown automatically. If disabled you would need to manually open the accordion to display them.
+Change the colour of your markers, this only really applies to the Review section.
+If you are set as a production owner, this enables/disables the email updates.
+ +
+This is where you will watch through the clips in Glympse.
When the page loads, it will automatically load the first clip into the player. To start playing you can press the big play button in the centre.
+Glympse uses the timecode from the media files. This is so that it matches the timecode that your editor sees within Avid or their NLE of choice.
+It is possible that the timecode in Glympse may be a frame off, this is because the timecodes must be calculated rather than read from the file. It will never be more that one frame off the timecode in the NLE.
+The timecode of the clip is displayed in two places. The seek bar:
+
And there is a timecode box in the top left:
+
This timecode box can be moved anywhere in the player window by dragging it to where you’d like it to be. You can reset the position of the timecode or disable the timecode box using the user settings menu.
+It is possible to navigate to a specific timecode by simply entering it whilst the page is active.
+If the timecode you want to go to is 10:03:05:00 pressing the 1 key will bring up the timecode navigation window. From there enter the rest of the timecode with no spaces or other punctuation. So you would enter: 10030500 and press enter. This will navigate to that timecode in the file.
For clips that have more than one track of audio, you can select the track to play back by clicking on the headphone icon on the playbar and selecting the audio track. Glympse by default creates a full mix of all the audio channels and plays this by default.
+
+Clicking the theatre mode button will expand the player to take 100% the width of the browser window. Clicking the theatre mode button again will return the player back to its normal size.
Click this button for full screen playback
+
Some clips like GoPro files can be the wrong orientation. Click the rotate button to rotate the clip by 180°
+
Click the restore rotate to return the clip to its original orientation.
+
When on this page there are a number of keyboard shortcuts you can use. +J, K, L are shuttle controls to speed up or change the direction of play. You may have to click in the player window to enable these controls. Holding the Shift Key will also increase the amount the play is sped up or slowed down.
+M will add a marker at the current time of the clip. Markers will appear for everyone who has access to the production.
+You can select the clip you’d like to view from the table at the bottom of the screen. Click the title of the clip to load it into the player.
+You can also navigate through the clips by pressing the Next/Prev buttons at the bottom of the player. This will load the next or previous clip.
+The title of the currently playing clip is shown at the bottom of the player and the middle of the menu bar at the top.
+When clips are loaded into Glympse, the system will scan for the start timecode and the end timecode of a clip. This allows it to show all the related clips of the clip you are playing. The related clips box onthe right of the player will update whenever the source of the video player changes. You can automatically hide or show the related clips dropdown using the user settings menu.
+In this example the clip being played belongs to the Main camera and there are two GoPro cameras that have clips with overlapping timecodes.
+
Clicking on the title of these related clips will play it in the current page, allowing you to quickly view clips from the other cameras. When you’re viewing a related clip, the title in the menu bar and below the player will change showing you that it’s playing a related clip then it will list the card followed by the clip title.
+
+As well as this, the prev/next buttons will disappear from below the player. You can select the next related clip by clicking on the clip title or you can return to the original clip by selecting it in the table at the bottom again. This will re-enable the next prev buttons and you can resume watching the camera clips as normal.
You can also navigate to any related cards from the related menu in the manu bar. This will show you camera cards from the same camera operator shot on the same day.
+You can add markers or tags to any clip within Glympse.
+Markers allow you to mark a specific place in a clip. They will be displayed in the marker window next to the player and clicking on them will take you to the correct position in the clip.
+Markers are shown to everyone who has access to the clip.
+Tags are to tag an entire clip. You can tag more than one clip at a time. There is also a setting in the user settings menu that will automatically add the tags to any related clips.
+Tags are available to everyone who has access to the clips.
+
+The menu bar may show different options depending on what permissions you have. For example, the Download button will only appear if you have been give download permission for your production.
From the file menu you can send a clip to be transcribed, edit the metadata of the card, submit the card for re-transcode or report issues with the card.
+Select the clip or clips you would like to transcribe by checking the box in the table and click file then transcribe. This will send the selected clip(s) to the transcription engine. You can learn more about how this works here.
+From this menu you can change some of the metadata for the card. Anything you change here will be applied to every clip in the card.
+You can change the date, the card name, or the shooter. You can also hide the card which will stop it from showing on the rushes page. Anyone with a link to the card would still be able to access the clips. This will only stop the card from appearing in the rushes page. Users with access to the production can also unhide any card from the metadata edit pages.
+This will send the entire card back through the transcode engine. It allows you to report any issues with the card and manually submit the clips to the transcoder. The transcode will only work if the original clips are still available.
+This allows you to report issues with the current card. But this option will not automatically retranscode the clips. They would need to be manually transcoded by the admin team.
+This will show any cards that were shot by the same camera operator on the same day as the current card. Clicking one of these will take you load that current card.
+If you have been given the download permissions for your production, you can download the original clip by selecting the clips from the table with the checkbox and clicking download. These files can be very large and may take a long time to download.
+This will open these help pages.
+This will open the user settings menu. Click here to learn more.
+In the centre of the menu bar, the title of the currently loaded clip will be displayed.
+ +