68 lines
3.0 KiB
Markdown
68 lines
3.0 KiB
Markdown
# Joining the Visionary PacketAV Beta
|
|
|
|
Thank you for helping test pre-release builds. The beta plugins are the real
|
|
blocks that will ship — you're seeing them a cycle early. Setup is the same as
|
|
the normal plugins, just a different URL.
|
|
|
|
## Before you start — one rule that matters
|
|
|
|
**Do not have both the regular and the beta Visionary PacketAV packages
|
|
installed on the same computer.** The beta plugins share the same internal IDs
|
|
as the production plugins (that's what makes them a true test), so if Q-SYS
|
|
Designer finds both, it can silently load the wrong one. Pick one channel per
|
|
machine:
|
|
|
|
- Testing beta? Remove the regular **Visionary PacketAV** personal package
|
|
first (below), then add the beta one.
|
|
- Done testing? Do the reverse to go back to production.
|
|
|
|
A dedicated test computer is ideal if you have one.
|
|
|
|
## Add the beta package
|
|
|
|
1. Sign in at `https://library.qsys.com`, then **My Library → My Packages**.
|
|
2. If the regular **Visionary PacketAV** entry is present, select it and
|
|
**remove** it first (see "Leaving the beta" for why this is safe).
|
|
3. Click **Add Personal Package** and enter:
|
|
- **Asset name:** `Visionary PacketAV (Beta)`
|
|
- **Package URL:** `https://vsplug.in/packetav-beta`
|
|
4. Click **Add package**. You'll see the "Personal Package Added" confirmation.
|
|
|
|
## Install in Q-SYS Designer
|
|
|
|
1. Open **Q-SYS Designer** and sign in to the **same** Library account.
|
|
2. **Tools → Show Asset Installer**.
|
|
3. On **Available Assets**, find **Visionary-PacketAV-Suite-Beta** and click
|
|
**Install**. Wait for **Install Status = Complete**.
|
|
4. The plugins appear under **Visionary** in the schematic Plugins list, same
|
|
as always. (Tip: check the plugin's **Help** page — beta builds are marked
|
|
so you always know which channel you're on.)
|
|
|
|
## Getting new beta builds
|
|
|
|
When a new beta is published, the Asset Installer shows a higher **Latest
|
|
Version** than your **Local Version** — click **Install** to update. If it isn't
|
|
showing yet, click **Refresh**; if that's stale, remove and re-add the
|
|
`https://vsplug.in/packetav-beta` entry (that forces a fresh read).
|
|
|
|
The plugins also tell you in-product: the **Software Update** line on the Help
|
|
page checks the beta feed and reports when a newer beta is available.
|
|
|
|
## Reporting issues
|
|
|
|
Please include: plugin and version (from the Help page footer), Q-SYS Designer
|
|
version, Core model, and what you expected vs. what happened. Send to
|
|
`support@visionary-av.com` or use the links at `https://vsplug.in/resources`.
|
|
|
|
## Leaving the beta / going back to production
|
|
|
|
1. **My Packages** → remove the **Visionary PacketAV (Beta)** entry.
|
|
2. Add the production package back: **Add Personal Package** →
|
|
name `Visionary PacketAV`, URL `https://vsplug.in/packetav`.
|
|
3. In **Asset Installer**, install the production suite over the beta. Because
|
|
the plugin IDs match, your existing designs keep working — they just move
|
|
back to the released version.
|
|
|
|
Removing a personal package only detaches the feed; it doesn't touch designs
|
|
you've already built.
|