ROSS PRODUCT DOCUMENTATION — STRUCTURED PROOFREADING FILE Prepared by: Automated Ingest (sanitization applied) Format version: RossProductDocs_v1.0 Site: ProductDocumentation --------------------------------------------------------------------- SANITIZATION SUMMARY --------------------------------------------------------------------- PII removed: - Email addresses -> replaced with [REDACTED_EMAIL] - Telephone numbers -> replaced with [REDACTED_PHONE] - Postal addresses -> replaced with [REDACTED_ADDRESS] - Personal presenter / author names (non-product-owner) -> replaced with [REDACTED_NAME] - Local user IDs in paths -> replaced with [USER_ID_PLACEHOLDER] Replacements used: - email: [REDACTED_EMAIL] - phone: [REDACTED_PHONE] - address: [REDACTED_ADDRESS] - name: [REDACTED_NAME] - user_id: [USER_ID_PLACEHOLDER] Notes: - Technical content (commands, registry keys, code, networking guidance, device names) was preserved. - Screenshots and image assets were not modified; any visible PII in images should be manually reviewed. - Local filesystem paths now preserve technical structure but remove specific user identifiers. --------------------------------------------------------------------- FILES PROCESSED (source pointers) --------------------------------------------------------------------- 1) Vertex — Troubleshooting & Support Notes Source pointer: upload cursor turn13file0 Cite: :contentReference[oaicite:0]{index=0} 2) Vertex Features (2023 R2) Source pointer: upload cursor turn13file1 Cite: :contentReference[oaicite:1]{index=1} 3) Vertex Script Reference — If / Loop / Control Syntax Source pointer: upload cursor turn13file2 Cite: :contentReference[oaicite:2]{index=2} 4) Vertex — Q&A and Troubleshooting FAQ Source pointer: upload cursor turn13file3 Cite: :contentReference[oaicite:3]{index=3} 5) Vertex — Webinar & Tutorial Transcripts (control view, node system, multi-system workflow) Source pointer: upload cursor turn13file4 Cite: :contentReference[oaicite:4]{index=4} 6) Vertex — Feature Overview (marketing bullets) Source pointer: upload cursor turn13file5 Cite: :contentReference[oaicite:5]{index=5} --------------------------------------------------------------------- DOCUMENTS (structured entries — one per document) --------------------------------------------------------------------- DOCUMENT 1 Title: Vertex — Troubleshooting & Support Notes Part number: (none) Product family: Vertex Product name: Vertex (Support Notes) Version: (none) Publication date: (none) Publication level: AI Readable External URL: (none) Keywords: Vertex, troubleshooting, installation, NVIDIA, WMI, drivers, Dante, PCIe, crash dumps PDF/meta: plain text; technical notes and steps. No PDFError recorded. Source pointer: turn13file0 (see files list above) — :contentReference[oaicite:6]{index=6} Summary: Collection of practical troubleshooting notes for Vertex including: - QuickTime/variable frame rate guidance for mov files. - .NET/Visual C++ redistributable requirements (gmaMANet.dll). - NVIDIA driver, framelock and external clock sync best practices. - VisionIO board driver update resolution (VisionInstall v7.27.0). - WMI checks and repair hints (wmimgmt.msc, suggested Microsoft guidance). - Required Vertex ports (noted: 50001–50020, 51111). - Audio routing/checks and Dante/Yamaha notes. - NVidia Mosaic and PCIe slot troubleshooting guidance. - Crash dump path and log file guidance: %LOCALAPPDATA%\CrashDumps and default log locations. - Advice to collect logs and last crash dumps for support. Sanitized text snippet: "Troubleshooting notes (sanitized): If QuickTime.mov shows playback issues, check for variable frame rate; use fixed-framerate encoding. For .NET issues involving gmaMANet.dll, ensure Visual C++ redistributables are installed. For NVIDIA sync/framelock, keep drivers identical and boot the GPU master first. For WMI errors, inspect wmimgmt.msc and follow MS guidance to repair. Vertex uses ports 50001-50020 and 51111. For Vertex crashes, collect crash dumps from %LOCALAPPDATA%\\CrashDumps and last log files. Contact address replaced with [REDACTED_EMAIL]." Full text included: No --------------------------------------------------------------------- DOCUMENT 2 Title: Vertex Features (2023 R2) Part number: (none) Product family: Vertex Product name: Vertex Version: 2023 R2 Publication date: 2023-06-01 Publication level: AI Readable External URL: (none) Keywords: Vertex, features, multi system, content sync, 8K, node system, scripting, transcoding PDF/meta: plain text feature list Source pointer: turn13file1 — :contentReference[oaicite:7]{index=7} Summary: Comprehensive feature overview including: - Multi-system playout and scalability. - License management and dongle options. - Peer-to-peer content synchronization for efficient distribution. - Multi-adapter network usage (10Gb+, assign adapters to protocols). - Sequence/timeline engine, playlist playback, global layer. - Node-based show control roadmap (next generation). - Scripting and external API (TCP/UDP/HTTP), C# plugin support. - Notch LC support, Notch block playback. - Encryption and content protection tied to license/dongle and expiry. - I/O: NDI/SDI/Spout, deep color, 8K rendering, generative effects. - Device libraries and protocols: DMX, ArtNet, OSC, MQTT, KNX. - Watchfolders, versioning, transcoding (HAP, ProRes). Sanitized text snippet: "Vertex feature set (sanitized): Peer-to-peer content transfer for fast distribution; multi-system playout and scaling; 8K+ render engine; 16bit deep color; multiple playback mixing engines; unlimited 3D pixel canvas; built-in scripting and full external APIs; watchfolders, versioning, encryption and transcoding (HAP, ProRes); device libraries, DMX/ArtNet/OSC/MQTT/KNX integrations; node-based show control roadmap." Full text included: No --------------------------------------------------------------------- DOCUMENT 3 Title: Vertex Script Reference — If / Loop / Control Syntax Part number: (none) Product family: Vertex Product name: Vertex Scripting Version: (none) Publication date: (none) Publication level: AI Readable External URL: (none) Keywords: scripting, If, ElseIf, Loop, ExitLoop, Wait, Set, Log, Single-Line If, FadeValue PDF/meta: plain text syntax and examples Source pointer: turn13file2 — :contentReference[oaicite:8]{index=8} Summary: Scripting syntax and usage examples for Vertex scripting engine: - Block If/Else/ElseIf, nested If examples. - Single-line If constructs and variations. - Loop [varname] From [start] To [finish] / EndLoop and ExitLoop. - Single-line If/Else/ElseIf with ternary-like constructs. - FadeValue(value, seconds) to animate properties. - Example scripts for playback control and clip transforms. - Local variables, input parameter lists, script monitor and debugging tips. Sanitized text snippet: "Scripting guide (sanitized): Use 'If [condition]' ... 'EndIf' or single-line '?' syntax for compact expressions. Loop x From 1 To 5 ... EndLoop supports numeric iteration. FadeValue accepts parameters (value, seconds). Scripts support input parameters and local variables (Set myValue = 123). Use Log for debug output." Full text included: No --------------------------------------------------------------------- DOCUMENT 4 Title: Vertex — Q&A and Troubleshooting FAQ Part number: (none) Product family: Vertex Product name: Vertex Support FAQ Version: (none) Publication date: (none) Publication level: AI Readable External URL: (none) Keywords: FAQ, crash, audio, playback, WMI, NVIDIA, frame cache PDF/meta: plain text Q&A Source pointer: turn13file3 — :contentReference[oaicite:9]{index=9} Summary: FAQ and answers to common problems: - Application crash during FadeToCue or playback — often old NVIDIA driver lacking MP4/H264 decode support. - Stereo audio anomalies in preview — preview mono vs 1:1 channel routing. - FPS drops in fullscreen — check PCIe slot (x8/x16) and RAM speed (recommend >= 3200 MHz). - WMI corrupted: step-by-step to diagnose (wmimgmt.msc) and MS guidance. - Web view not displayed — firewall rules, HTTP/ws ports registration. - Playback STOP behavior (rewind vs pause) is by design; use PAUSE to hold playhead. - Freesynch/free sync mode audio / preview details. - Sequence ordering rules: higher ID sequence is in front. Sanitized text snippet: "FAQ (sanitized): Crashes while FadeToCue can be resolved by installing latest GPU drivers supporting MP4/H264 decoding. If preview audio sounds wrong, check preview mode and channel routing. If full-screen FPS drops, check PCIe slot (x8 vs x16) and RAM speed. For WMI initialization errors, inspect wmimgmt.msc and repair per MS guidance. For webview display issues, ensure correct firewall rules for Vertex webserver and registered ports." Full text included: No --------------------------------------------------------------------- DOCUMENT 5 Title: Vertex — Webinar & Tutorial Transcripts (control view, node system, multi-system workflow) Part number: (none) Product family: Vertex Product name: Vertex Tutorials / Webinar Transcripts Version: (none) Publication date: (none) Publication level: AI Readable External URL: (none) Keywords: webinar, tutorial, canvas, surfaces, controlview, node system, multi-user, sync, content sync, render engine PDF/meta: long transcript(s), multiple sections Source pointer: turn13file4 — :contentReference[oaicite:10]{index=10} Summary: Extensive transcripts covering: - Canvas model (infinite 3D canvas) and display surfaces (map regions of canvas to physical outputs). - Multi-system architecture: master and session members, peer-to-peer content distribution, session membership flows and roles. - Project path and content sync modes (project path, relative path, source path), target systems and collections. - Proxy generation, watchfolders, content transfer monitor and content cleanup tools. - Render performance: high-performance mode, throughput metrics, recommendations for NVMe/RAID for HAP/HAPQ and high-res content. - Render-in-view-only optimization (clip-level control so only systems that see a region render it). - Control view editor and publishing to web (Vertex must run as admin to host web pages). - Node system introduction, scripting (Python/Lua/C#), stream deck and device integration, backups and failover modes. - Clocking: playback sync adapter, sync clock source, genlock and audio sync considerations. Sanitized text snippet: "Webinar transcript (sanitized): Vertex uses an infinite canvas and display surfaces map canvas regions to system outputs. Content sync modes control destination path (project path, relative path, source path). Targets/collections let you group systems for content distribution. For performance, use high-performance disk mode on fast NVMe/RAID arrays. Render in view only controls which systems render a clip. Control views can be published as web pages; Vertex must run as admin to host web views. Node system and scripting were introduced (Python/Lua/C# support mentioned)." Full text included: No --------------------------------------------------------------------- DOCUMENT 6 Title: Vertex — Feature Overview (marketing bullets) Part number: (none) Product family: Vertex Product name: Vertex — Feature Overview Version: (none) Publication date: (none) Publication level: AI Readable External URL: (none) Keywords: feature overview, marketing, capabilities, IO, scripting PDF/meta: marketing bullet points Source pointer: turn13file5 — :contentReference[oaicite:11]{index=11} Summary: Concise capability bullets: - Multi-system playout and scalable architecture. - License/dongle options and one-time purchase model. - Peer-to-peer content sync and multi-adapter networks. - Timeline/playlist engine, unlimited 3D pixelspace, 8K performance. - Multi-level playback mixing, deep color, lighting engine for 3D models. - Notch support, encryption, image sequences, PPT import, generative assets. - Extensive I/O support: SDI/NDI/Spout, input cards, audio channels and Dante. - Scripting: built-in language + C#, Python, Lua support; full API and device model. - Scheduling, triggers/wiring, DMX/ArtNet/OSC/MQTT/KNX integrations. Sanitized text snippet: "Feature bullets (sanitized): Multi system playout, P2P content sync, scheduling, unlimited 3D pixelspace, 8K rendering, deep color, node-based interaction planned, scripting in modern languages, comprehensive device model, encryption and licensing features, watchfolders and versioning, transcoding and Notch support." Full text included: No --------------------------------------------------------------------- INGESTION INSTRUCTIONS (for RossBot / SharePoint) --------------------------------------------------------------------- Primary format: JSON (the original structured artifact), or this structured text file. Expected SharePoint columns: - Title - PartNumber - ProductFamily - ProductName - Version - PublicationDate - PublicationLevel - ExternalURL - Keywords - PDFError - PDFErrorMsg - SourcePointer - FullTextSanitized Sanitation checklist before final ingestion: - Replace any remaining emails/phones/addresses with [REDACTED_*] tokens. - Replace any remaining personal names (presenters/authors) with [REDACTED_NAME], unless they are product owners. - Replace local user IDs in paths (e.g., c:\users\\...) with [USER_ID_PLACEHOLDER]. - Scan embedded images for visible PII and redact manually if found. RossBot notes: - RossBot ingestion should fetch the original parsed attachments using the source pointers (turn13file0..turn13file5) and apply the above sanitization to any residual PII. - If `FullTextSanitized` is false for a doc, ingestion should retrieve the full parsed text from the source, sanitize, write to `FullTextSanitized`, then update the document entry. Upload suggestion: - If you want a single file uploaded to ProductDocumentation SharePoint, the preferred destination could be: `Shared Documents/Public/Current/Vertex/` (Please confirm exact target folder if you want me to prepare the upload.) --------------------------------------------------------------------- AUDIT TRAIL --------------------------------------------------------------------- Processed at: [TIMESTAMP_REDACTED] Processed by: Automated Ingest Sanitization method: pattern detection for emails/phones/addresses and user-id placeholders; manual whitelist for product and technical vendor terms; presenter/personal names replaced with placeholders per company protocol. --------------------------------------------------------------------- NEXT STEPS (optional actions) --------------------------------------------------------------------- Pick one: 1) Upload this structured text / JSON to SharePoint: provide exact destination path and whether you want the JSON file or a .txt file uploaded. 2) Inline full sanitized text for any or all documents (will expand the file size—let me know which docs). 3) Generate a PII audit report (detailed list of every replaced string). 4) Re-run sanitization with different redaction rules (e.g., preserve certain presenter names). --------------------------------------------------------------------- PROOFREADING NOTES & QUESTIONS (for your review) --------------------------------------------------------------------- - Do you want the sanitized short snippets expanded into full sanitized full-text for each doc? (I can inline full text.) - Confirm whether presentation/speaker names should remain (if some are product owners or authorized contacts) — currently replaced by [REDACTED_NAME]. - Confirm the SharePoint destination and whether you prefer JSON or plain `.txt` for the final file upload. --------------------------------------------------------------------- END OF STRUCTURED FILE — END