A stage lighting automatic programming control method and system

Abstract

The present application relates to the technical field of stage performance equipment control, and particularly relates to a stage lighting automatic programming control method and system. The method comprises the following steps: obtaining GDTF format stage lamp data, stage building data and performance site data of a target stage scene, associating and encapsulating to generate a stage site data file; analyzing lamp capacity constraints, lamp position space constraints and site coverage constraints to generate a lighting material file and a lamp position layout diagram; writing material screening results and lighting parameter adjustment records to generate target lighting materials; combining target audio files to extract audio features, performing audio segmentation and lighting action segment matching, lamp control parameter mapping and time axis generation to obtain a lighting show execution file; checking DMX addresses, lamp channel fields and lamp parameter boundaries, converting into DMX execution control data and returning to generate a cloud-generated sample. The present application forms a continuous corresponding relationship among lighting materials, audio segments and stage lamp control data.

Description

Technical Field

[0001] This invention relates to the field of stage performance equipment control technology, and in particular to an automatic programming control method and system for stage lighting. Background Technology

[0002] In the field of stage performance equipment control technology, existing solutions for stage lighting programming typically rely on the coordinated control of lighting consoles, lighting library files, preset light shows, audio playback devices, and DMX protocol stage lights. Common approaches include having lighting technicians pre-edit lighting scenes based on lighting channels, light placement, stage zoning, and music rhythm, or adjusting illumination brightness, angle, and color changes during the performance based on preset light show control parameters. While these solutions can achieve basic lighting control with a fixed stage, fixed lighting setup, and fixed program flow, they are prone to limitations when stage setup data, lighting capacity data, venue coverage, and audio content all change simultaneously. These limitations include inconsistencies between lighting control parameters and on-site light placement, disconnects between audio segmentation and lighting actions, and difficulties in directly adapting lighting output data to DMX channels.

[0003] Existing solutions often rely on manually set lighting scenes, pre-set lighting materials, or single musical features for processing. When the stage light model, installation location, performance venue area, or target audio file changes, the lighting channel fields, lighting parameter boundaries, stage zones, and venue coverage are often scattered across different data sources, making it difficult to maintain continuous reference during the generation of lighting materials and the creation of light show execution files. Especially when it is necessary to map lighting action segments to audio segments, the lack of synchronous constraints on lighting fixture numbers, DMX addresses, channel fields, and parameter boundaries can easily cause transition breakpoints between the lighting action timeline and subsequent execution control data.

[0004] For the joint processing of stage live data, target lighting materials, and target audio files, existing technologies still suffer from insufficient coordination between material generation, audio matching, lighting control parameter mapping, and execution control conversion. Therefore, it is necessary to address the issue of how to generate a light show execution file and convert it into stage lighting execution control data based on stage live data files, target lighting materials, and target audio files, specifically within the context of stage lighting programming scenarios. Summary of the Invention

[0005] To address the aforementioned technical problems, this invention provides an automatic programming control method for stage lighting, comprising: S100: Obtain GDTF format stage lighting data, stage setup data, and performance venue data for the target stage scene; associate and encapsulate the lighting channel field, lighting parameter boundaries, lighting installation location, stage partition, and venue coverage area to generate a stage scene data file. S200. Based on the stage site data file, analyze the lighting fixture capacity constraints, lighting position space constraints, and site coverage constraints, and generate lighting material files and lighting position layout diagrams according to the lighting fixture capacity constraints, lighting position space constraints, and site coverage constraints. S300: Based on the aforementioned lighting material file and lighting layout diagram, write the material selection results and lighting parameter adjustment records to generate the target lighting material; S400: Based on the target lighting material, the stage data file, and the target audio file, extract audio features, perform audio segmentation and matching with lighting action segments, map lighting control parameters, and generate a timeline to obtain a light show execution file; S500: Based on the light show execution file, verify the DMX address, lamp channel field and lamp parameter boundary, convert the light show execution file into DMX execution control data, and send the target light material, light show execution file and light parameter adjustment record back to the cloud platform to generate a cloud-generated sample.

[0006] Furthermore, the stage site data file includes GDTF format stage lighting data, stage setup data, and performance venue data; the GDTF format stage lighting data includes the geometric model of the lighting fixtures, DMX channel allocation, physical properties, and functional parameters; the stage setup data includes CAD drawings, 3D models, lighting fixture installation positions, and lighting fixture installation postures; the performance venue data includes audience area data, the distance to the nearest audience member, the distance to the farthest audience member, and the target coverage area.

[0007] Furthermore, the analysis of the lighting fixture capability constraints, lighting position space constraints, and site coverage constraints includes: extracting the brightness range, color channel, pattern channel, pan-tilt angle range, and DMX channel occupancy length from the GDTF format stage lighting data to generate the lighting fixture capability constraints; extracting the lighting fixture coordinates, installation height, installation posture, and illuminated area from the stage setup data to generate the lighting position space constraints; and extracting the stage partitions, audience area, and illumination coverage boundaries from the performance venue data to generate the site coverage constraints.

[0008] Furthermore, the generation of lighting material files and lighting layout diagrams includes: grouping multiple stage lights according to the lighting space constraints; mapping the lighting groupings to candidate illumination areas in the site coverage constraints; and writing basic lighting action segments, basic lighting effect parameters, and material style identifiers based on the lighting capability constraints to generate the lighting material files and lighting layout diagrams.

[0009] Furthermore, the step of writing the material screening results and lighting parameter adjustment records includes: generating preview data based on the light position layout diagram and the lighting material file; receiving the screening results of the lighting material file and receiving the parameter adjustment records corresponding to brightness parameters, color parameters, pattern parameters, gimbal angle parameters or motion speed parameters; writing the screening results and the parameter adjustment records into the material version to generate the target lighting material.

[0010] Furthermore, the audio features include beat points, audio energy segments, paragraph transition points, melody segments, and style identifiers; the extraction of audio features includes time segmentation of the target audio file, and writing the beat points, audio energy segments, paragraph transition points, melody segments, and style identifiers into the audio segmentation index.

[0011] Furthermore, the process of matching audio segments with lighting motion clips, mapping lighting control parameters, and generating a timeline includes: reading lighting motion clips from the target lighting material; matching the start and end times of the audio segments with the duration of the lighting motion clips; compressing, extending, or repeating the lighting motion clips when the duration does not match the start and end times; and mapping the processed lighting motion clips with the lighting fixture number, DMX address, and channel field to generate a lighting motion timeline.

[0012] Furthermore, the light show execution file includes time nodes, lamp numbers, DMX addresses, channel fields, target parameter values, duration, transition parameters, and execution order; obtaining the light show execution file includes binding the light action timeline with the lamp numbers, DMX addresses, channel fields, and target parameter values, and writing the duration, transition parameters, and execution order.

[0013] Furthermore, the verification includes: when there is a conflict in the DMX address, reassigning candidate addresses according to the DMX channel occupancy length; when the lighting channel field is missing, supplementing the lighting channel field and generating an execution verification result; when the lighting control parameters exceed the lighting parameter boundaries, limiting the amplitude according to the lighting parameter boundaries and generating a verified lighting channel control sequence; the cloud-generated sample includes the target lighting material, the light show execution file, the lighting parameter adjustment record, and the execution verification result.

[0014] Furthermore, an automatic programming control system for stage lighting, applied to any of the methods described above, includes: a stage site data construction module, a lighting material generation module, a material preview and adjustment module, a light show file generation module, a DMX execution and conversion module, and a cloud feedback module.

[0015] The key innovations of this invention include: (1) Associate the GDTF format stage lighting data, stage construction data and performance venue data into a stage site data file, and parse the lighting capacity constraints, lighting position space constraints and site coverage constraints from the stage site data file to form site constraint data for generating lighting material files.

[0016] (2) Based on the luminaire capability constraints, luminaire position space constraints and site coverage constraints, generate a lighting material file and a luminaire position layout diagram, and write the material selection results and lighting parameter adjustment records into the lighting material file to form the target lighting material.

[0017] (3) The target lighting material, the stage data file and the target audio file are used together to generate the light show execution file. The light show execution file can be converted into DMX execution control data by matching audio segments with light action segments, mapping lighting control parameters and generating a timeline.

[0018] The following are its main beneficial effects: (1) To address the problem of discontinuous data generation basis caused by the scattered storage of lighting capability data, stage construction data and site coverage, the lighting channel field, lighting parameter boundary, lighting installation location, stage partition and site coverage are uniformly associated through the stage site data file, so that the subsequent lighting material file generation process can continuously call the site constraint data under the same target stage scene.

[0019] (2) To address the problem of insufficient connection between pre-set lighting materials and actual lighting layout and site coverage, lighting material files and lighting layout diagrams are used to carry lighting fixture groups, candidate illumination areas and basic lighting action segments, and to write material screening results and lighting parameter adjustment records, so that the target lighting material has a material version corresponding to the current stage site before entering the light show execution file generation.

[0020] (3) To address the issue of potential breakpoints in the transition between audio segments and lighting action segments, lighting control parameters, and DMX execution control data, a light show execution file is generated by combining the target lighting material, stage data file, and target audio file. This ensures that time nodes, lighting numbers, DMX addresses, channel fields, target parameter values, and execution order form a continuous correspondence in the light show execution file. Attached Figure Description

[0021] Figure 1 A flowchart illustrating an automatic programming control method for stage lighting provided in an embodiment of this application; Figure 2 This is a structural block diagram of an automatic programming control system for stage lighting provided in an embodiment of this application. Detailed Implementation

[0022] Example 1: Refer to Figure 1 This is a flowchart illustrating an automatic programming control method for stage lighting provided in an embodiment of the present invention. The process may include at least steps S100-S500: S100: Obtain GDTF format stage lighting data, stage setup data, and performance venue data for the target stage scene; associate and encapsulate the lighting channel field, lighting parameter boundaries, lighting installation location, stage partition, and venue coverage area to generate a stage scene data file. S200. Based on the stage site data file, analyze the lighting fixture capacity constraints, lighting position space constraints, and site coverage constraints, and generate lighting material files and lighting position layout diagrams according to the lighting fixture capacity constraints, lighting position space constraints, and site coverage constraints. S300: Based on the aforementioned lighting material file and lighting layout diagram, write the material selection results and lighting parameter adjustment records to generate the target lighting material; S400: Based on the target lighting material, the stage data file, and the target audio file, extract audio features, perform audio segmentation and matching with lighting action segments, map lighting control parameters, and generate a timeline to obtain a light show execution file; S500: Based on the light show execution file, verify the DMX address, lamp channel field and lamp parameter boundary, convert the light show execution file into DMX execution control data, and send the target light material, light show execution file and light parameter adjustment record back to the cloud platform to generate a cloud-generated sample.

[0023] S100: Obtain GDTF format stage lighting data, stage setup data, and performance venue data for the target stage scene; associate and encapsulate the lighting channel field, lighting parameter boundaries, lighting installation location, stage partition, and venue coverage area to generate a stage scene data file. After receiving a new stage scene creation command or a stage data import command from the console, the stage site data construction module establishes a scene number for this lighting programming and links the GDTF format stage lighting data, stage setup data, and performance venue data under the same scene number. This scene number serves as the index for subsequent cloud platform parsing, material generation, and execution feedback, preventing data from different performances, different lighting batches, or different stage setup versions from being mixed in the same processing link. The GDTF format stage lighting data refers to stage lighting equipment description data recorded using the General Device Type Format (GDTF), which includes the lighting fixture geometric model, DMX channel allocation, physical attributes, and functional parameters. DMX is short for Digital Multiplex, used to represent the address and channel transmission method used for stage lighting channel control. The stage setup data comes from the computer-aided design (CAD) drawings and 3D model of the target stage scene; the performance venue data comes from the venue configuration file or the console input interface.

[0024] When importing GDTF format stage lighting data, the stage data construction module first reads the lighting fixture model, fixture number, fixture geometric model, DMX channel allocation, and functional parameters. Then, it establishes a correspondence between the lighting fixture channel fields and brightness, color, pattern, pan / tilt horizontal angle, pan / tilt tilt angle, and flicker-related functions. This correspondence is used to subsequently identify the types of lighting actions each stage light can participate in. For lighting fixture parameter boundaries, the module extracts the value range, channel length, and parameter conversion relationship for each channel, and binds the channel fields, parameter boundaries, and fixture number of the same stage light to the same lighting fixture record. If there are missing channel fields in the imported GDTF format stage lighting data, the module first calls the local lighting fixture channel template to complete the fields based on the lighting fixture model and channel length. Channels that cannot be completed are marked as missing fields and participate in the generation of verification results in the subsequent S500 process.

[0025] The processing of stage setup data focuses on the installation positions and postures of lighting fixtures. The control console reads the stage boundaries, lighting rig positions, and lighting fixture installation points from the CAD drawings, and the installation height, posture, and illumination direction of the lighting fixtures from the 3D model. When the coordinate references in the CAD drawings and the 3D model are inconsistent, the module establishes a unified coordinate system using the stage center point, the stage front edge line, and the lighting rig reference point, and then converts the 2D installation points and 3D installation postures to the same scene coordinates. If the installation posture of a certain stage light is missing in the 3D model, but the lighting rig and orientation of the stage light can be determined in the CAD drawings, the module retains the lighting fixture coordinates and sets the installation posture to a pending confirmation state. This state does not prevent the generation of stage scene data files, but it will limit the stage light from participating in the generation of lighting materials with large pan-tilt movements in S200.

[0026] The performance venue data is used to define the coverage area of ​​lighting actions. The control console reads audience area data, the nearest audience distance, the farthest audience distance, and the target coverage area, and converts this into stage zones and venue coverage areas. Stage zones can be divided into front, middle, rear, and side zones, or they can be divided according to the performance area boundaries in the 3D model. In one implementation, when the venue configuration file only provides the nearest and farthest audience distances, the stage site data construction module generates audience area boundaries based on the stage front edge line, and then combines this with the stage width to form the target coverage area. This target coverage area is not directly used as lighting control commands, but rather participates in the formation of venue coverage constraints in S200.

[0027] After completing the above processing, the stage scene data construction module associates and encapsulates the lighting channel field, lighting parameter boundaries, lighting installation positions, stage zones, and site coverage to form a stage scene data file. This association and encapsulation means that the lighting fixture number of the same stage light simultaneously points to its GDTF functional parameters, DMX address or candidate address, lighting fixture coordinates, installation posture, and illuminated area, rather than simply compressing various files into the same directory. The stage scene data file retains the index of the original input file and saves the scene coordinates after unified coordinate processing and the lighting parameter boundaries after channel parsing. This stage scene data file serves as input to S200 and is further parsed by the scene constraint parsing module into lighting fixture capability constraints, lighting position space constraints, and site coverage constraints.

[0028] S200. Based on the stage site data file, analyze the lighting fixture capacity constraints, lighting position space constraints, and site coverage constraints, and generate lighting material files and lighting position layout diagrams according to the lighting fixture capacity constraints, lighting position space constraints, and site coverage constraints. After the console uploads the stage data file generated by S100 to the cloud platform, the cloud platform first verifies the continuity of the scene number, file version, and lighting fixture number. Once verified, the on-site constraint parsing module reads the GDTF format stage lighting data, stage setup data, and performance venue data from the stage data file, and breaks down the content affecting lighting motion generation into lighting fixture capability constraints, lighting position space constraints, and venue coverage constraints. This breakdown does not change the source of the original input file; instead, it converts the content scattered throughout the lighting fixture descriptions, stage setup, and venue scope into constraint objects that the lighting material generation module can call. If the file version is inconsistent with the current scene number on the console, the cloud platform retains the stage data file but does not proceed with the lighting material generation process.

[0029] The lighting fixture capability constraints are obtained by parsing GDTF format stage light data. The on-site constraint parsing module reads the brightness range, color channels, pattern channels, pan / tilt angle range, and DMX channel occupancy length from the lighting fixture function parameters and binds these parameters to the lighting fixture number. For stage lights without pan / tilt channels, the module retains the brightness, color, and pattern control ranges in the lighting fixture capability constraints but does not assign lighting action segments that require changing the illumination direction to that stage light. For stage lights with multiple color channels, the module groups the color channels into the same color control group and saves the output order between the channels. When the lighting material generation module writes the basic lighting effect parameters later, it calls the corresponding channel fields according to the color control group.

[0030] The spatial constraints of the lighting positions are obtained by parsing the stage setup data. The on-site constraint parsing module reads the coordinates, installation height, installation posture, and illuminated area of ​​the lighting fixtures, and divides multiple stage lights into front lighting group, side lighting group, rear lighting group, and coverage compensation group according to the stage zoning location. The grouping process considers the physical position of the lighting fixtures, the direction of illumination, and the illuminated area simultaneously. For example, a stage light installed at the rear of the stage but which can be rotated by a pan-tilt head to cover the central area can be assigned to the central area candidate group. If the installation posture of a certain stage light is marked as pending confirmation in S100, the on-site constraint parsing module only includes it in brightness or color-related materials, and does not include it in follow spot action segments that require precise positioning.

[0031] The venue coverage constraint is formed by the performance venue data and stage partitions. The on-site constraint parsing module generates multiple candidate illumination areas based on the audience area, target coverage area, and stage partitions. Each candidate illumination area records its respective stage partition, audience viewing direction, lighting fixture coverage relationship, and illumination boundary. If the target coverage area exceeds the illumination range of the imported stage lights, the module does not expand the lighting fixture parameters but generates a coverage gap mark in the venue coverage constraint. After receiving the coverage gap mark, the lighting material generation module avoids generating motion clips that rely on the strong illumination of a single stage light for that area and prioritizes the overlapping illumination method of multiple lighting fixture groups.

[0032] The lighting material generation module generates lighting material files according to the three types of constraints mentioned above. First, the module groups multiple stage lights based on the lighting position space constraints, then maps these groups to candidate illumination areas within the site coverage constraints. After mapping, the module writes basic lighting action clips, basic lighting effect parameters, and material style identifiers based on the lighting fixture capability constraints. Basic lighting action clips include zoned brightening, grouped sweeping, color switching, pattern switching, and fixed-point illumination. Each action clip is bound to its callable lighting fixture group, channel fields, and parameter boundaries. Therefore, the lighting material file is not the final execution instruction, but rather an editable collection of materials constrained by the stage environment.

[0033] The lighting layout diagram is generated synchronously with the lighting material files. The lighting layout diagram records the correspondence between lighting fixture groups and candidate illumination areas, and saves the fixture positions, main illumination directions, and coverage boundaries based on stage coordinates and fixture numbers. In one implementation, the lighting layout diagram can be rendered as a two-dimensional lighting layout diagram by the console, or it can be combined with a three-dimensional model to form a preview view. This lighting layout diagram participates in material preview and material selection in S300. The console reads the lighting fixture group and its corresponding illumination area called by a certain lighting material through the lighting layout diagram.

[0034] S300: Based on the aforementioned lighting material file and lighting layout diagram, write the material selection results and lighting parameter adjustment records to generate the target lighting material; After the console receives the lighting material files and light position layout diagram generated by the S200 from the cloud platform, the material preview and adjustment module first checks whether the scene number in the lighting material file matches the stage live data file currently loaded by the console. If the scene number does not match, the console does not enter the material preview process, but instead re-acquires the lighting material file corresponding to the current target stage scene. If the scene number matches, the material preview and adjustment module reads the light fixture groups and candidate illumination areas from the light position layout diagram, and then combines them with the basic lighting motion clips in the lighting material file to generate preview data.

[0035] The preview data is not directly sent to the stage lighting control data, but is a simulation result generated on the control panel based on the lighting layout diagram, basic lighting effect parameters, and lighting fixture parameter boundaries. When displaying the preview screen, the control panel shows the lighting fixture grouping, main illumination area, and action segment duration for each material in correspondence with the lighting layout diagram. For areas with coverage gap marks in the lighting layout diagram, the preview screen retains these marks, allowing the material selection process to identify the coverage boundaries of the material. If a lighting material uses a stage light whose installation posture is yet to be confirmed in S100, the material preview adjustment module locks the pan / tilt head movement of that stage light in the preview data, only displaying its brightness and color changes.

[0036] The material selection results are received by the console and written into the material version of the lighting material file. The user can choose to keep a certain lighting material or discard materials that are not suitable for the current stage. In one implementation, the console also filters and sorts the lighting material files based on overlay gap markers, missing channel field markers, and abnormal lighting grouping markers that appear during the preview process, but the final material selection results still correspond to specific lighting material files and material versions. The material selection results are subsequently used as the source of target lighting materials in S400, and lighting materials that are not selected are not involved in the generation of the light show execution file.

[0037] The lighting parameter adjustment record is used to save partial modifications made to the footage by the user or the console. Adjustable parameters include one of the following: brightness, color, pattern, pan / tilt angle, and motion speed parameters, or a combination of multiple parameters. When writing parameter adjustment records, the footage preview adjustment module first checks whether the adjusted parameter belongs to the corresponding lighting channel field and verifies whether the adjusted value is within the lighting parameter boundaries. If the adjusted value exceeds the lighting parameter boundaries, the console does not delete the adjustment record but marks it as pending limiting. Subsequently, the S500 limits the lighting according to the lighting parameter boundaries before generating DMX execution control data.

[0038] The target lighting material is formed by the material selection results, lighting parameter adjustment records, and selected lighting material files. This target lighting material retains basic lighting motion clips, material style identifiers, lighting fixture groupings, and lighting position layout indexes, while also including the material version and adjustment records. Compared to the lighting material files generated by S200, the target lighting material already corresponds to the current target stage scene and the confirmed material selections. When S400 performs audio segmentation and lighting motion clip matching, it reads the lighting motion clips and adjusted parameters from the target lighting material, rather than reading all candidate lighting material files.

[0039] S400: Based on the target lighting material, the stage data file, and the target audio file, extract audio features, perform audio segmentation and matching with lighting action segments, map lighting control parameters, and generate a timeline to obtain a light show execution file; After receiving the target lighting material generated by S300, the light show file generation module simultaneously calls the stage live data file generated by S100 and receives the target audio file uploaded by the console or selected locally. The target audio file can be in MP3 format or any audio file format that the console can parse. Before starting processing, the light show file generation module checks the version of the stage live data file referenced by the target lighting material. If the versions are inconsistent, the module pauses the generation of the light show executable file and re-executes the material filtering or re-downloads the lighting material file to avoid inconsistencies between the lighting fixture grouping in the material and the lighting fixture installation positions in the current stage live data file.

[0040] Audio feature extraction begins with the timeline of the target audio file. After reading the target audio file, the light show file generation module divides it into multiple audio segments and extracts beat points, audio energy segments, paragraph transition points, melody segments, and style identifiers from each segment. Beat points are used to mark candidate time positions for light action transitions; audio energy segments are used to distinguish areas with significant changes in brightness or action speed; paragraph transition points are used to separate the intro, main section, sub-section, and ending section. Melody segments and style identifiers do not directly generate color values ​​but participate in the selection of light action segments, allowing different action segments from the same target light material to be called in different segments of the target audio file.

[0041] After extracting audio features, the light show file generation module writes beat points, audio energy segments, segment transition points, melody segments, and style identifiers into the audio segment index. This index records the start and end times, segment type, and matchable action conditions for each audio segment. Subsequently, the module reads light action clips from the target light source material and maps the start and end times of the audio segments to the duration of the light action clips. For action clips with durations matching the start and end times, the module directly establishes a matching relationship. For action clips with durations shorter than the audio segments, the module repeatedly calls them according to the transition parameters. For action clips with durations longer than the audio segments, the module compresses them according to the cuttable nodes in the action clips. If an action clip has no cuttable nodes, the module calls an action clip with a closer duration from the target light source material.

[0042] The mapping of lighting control parameters is performed after the audio segments and lighting motion clips are matched. The light show file generation module reads the lighting fixture number, DMX address, and channel fields from the stage data file based on the lighting fixture grouping in the target lighting material, and then binds the processed lighting motion clips with the corresponding stage light's channel fields. For clips involving pan-tilt-zoom (PTZ) motion, the module reads the lighting fixture coordinates, installation posture, and illuminated area from the lighting position spatial constraints to avoid calling PTG angles that do not match the installation status of the stage light on the lighting motion timeline. For clips involving only brightness or color changes, the module uses the brightness range and color channel in the lighting fixture capability constraints as the mapping basis.

[0043] The timeline generation is based on the audio segment index. The light show file generation module arranges the light action segments corresponding to each audio segment into a light action timeline according to the playback time order of the target audio file. Each time node records the lamp number, DMX address, channel field, target parameter value, duration, transition parameters, and execution order. If adjacent audio segments call the same lamp group, but the target parameter value changes significantly, the module writes transition parameters between the two time nodes, enabling the subsequent DMX execution conversion module to form a continuous lamp channel control sequence. If adjacent audio segments call different lamp groups, the module switches the lamp groups according to the execution order and retains the exit time node of the previous lamp group.

[0044] The light show execution file consists of a light action timeline and corresponding lighting control parameters. This file is not directly equivalent to DMX execution control data because it still retains material versions, audio segment indexes, lighting groupings, and transition parameters for subsequent verification and feedback. After receiving the light show execution file, S500 continues to verify the DMX address, lighting channel field, and lighting parameter boundaries, and converts the parts that can be executed by the stage lights into DMX execution control data.

[0045] S500: Based on the light show execution file, verify the DMX address, lamp channel field and lamp parameter boundary, convert the light show execution file into DMX execution control data, and send the target light material, light show execution file and light parameter adjustment record back to the cloud platform to generate a cloud-generated sample. S500 is executed by the DMX execution conversion module and the cloud feedback module in the console. After receiving the light show execution file output by S400, the DMX execution conversion module first reads the time nodes, lamp numbers, DMX addresses, channel fields, parameter target values, durations, transition parameters, and execution order from the file. The read results maintain the same data source as the lamp parameter boundaries in S100 and the lamp capability constraints in S200, and are used to verify whether the lamp control fields in the light show execution file still fall within the control range defined by the stage data file. If the lamp number in the light show execution file cannot be found in the stage data file, the DMX execution conversion module does not generate a lamp channel control sequence for that lamp number and writes that lamp number into the execution verification result.

[0046] DMX address verification proceeds according to the lamp number and time node. The module first checks the DMX addresses used by each stage light within the same time period, and then determines whether the address ranges overlap based on the corresponding DMX channel occupancy length. If two stage lights use the same DMX address within the same time period and their DMX channel occupancy lengths overlap, the DMX execution conversion module marks this state as a DMX address conflict. For stage lights with conflicts, the module reallocates candidate addresses based on the DMX channel occupancy length and the current available address range on the console, and writes the reallocation result into the execution verification result. If the available address range is insufficient, the module retains the original light show execution file, does not generate the lamp channel control sequence for the corresponding conflicting stage light, and outputs an address anomaly flag. This address anomaly flag can be displayed on the console or sent back to the cloud platform along with the execution verification result.

[0047] The lighting channel field verification checks whether the channel fields in the light show execution file exist in the corresponding stage light's GDTF format stage light data. If a lighting channel field has been completed using a channel template in S100, the DMX execution conversion module uses the completed channel field for conversion and records the source of completion in the execution verification result. If the channel field is still missing, the module skips the target value of the parameter corresponding to that channel field, without affecting the conversion of other channel fields in the same stage light. For cases where lighting control parameters exceed the lighting parameter boundaries, the module limits the amplitude according to the lighting parameter boundaries and writes the target values ​​of the parameters before and after the limiting into the execution verification result. Lighting parameter adjustment records marked as pending limiting in S300 are processed into executable lighting channel control sequences in this step.

[0048] After completing the DMX address, lighting channel field, and lighting parameter boundary verification, the DMX execution conversion module converts the target parameter values ​​into DMX execution control data according to the time nodes and execution order in the light show execution file. The DMX execution control data includes the lighting fixture number, DMX address, channel field, channel value, output time, and duration. For time nodes containing transition parameters, the module calculates an intermediate output sequence based on the starting channel value, target channel value, and duration, and writes the intermediate output sequence into the lighting fixture channel control sequence. For time nodes without transition parameters, the module directly writes the target channel value according to the execution order. After connecting the DMX protocol stage lights, the control console outputs control data to the corresponding stage lights according to the lighting fixture channel control sequence.

[0049] After the DMX execution control data is generated, the cloud feedback module reads the target lighting material, light show execution file, and lighting parameter adjustment records, and generates a cloud-generated sample based on the execution verification results. The cloud-generated sample retains the data items actually used in the generation process, including the lighting fixture grouping of the target stage scene, the lighting position layout index, the used lighting action clips, the audio segment index, the parameter adjustment records, and the verified lighting channel control sequence. In one implementation, after the console completes the live playback and generates an execution log, the cloud feedback module associates the execution log with the cloud-generated sample, allowing the cloud platform to call upon the used target lighting material and parameter adjustment records during the subsequent generation of lighting material files for similar stage scenes.

[0050] When the connection between the console and the cloud platform is interrupted, the cloud feedback module caches the target light source material, light show executable file, light parameter adjustment records, and execution verification results locally on the console, and writes the scene number and generation time to the cached data. After the cloud platform connection is restored, the module uploads the cached data according to the scene number. If there are multiple material versions under the same scene number, the cloud feedback module prioritizes uploading the material version that has actually been converted into DMX execution control data, and retains the screening results of the unused versions. When the cloud platform generates samples subsequently, it uses the actual converted version as the master sample record and the unused versions as the screening records.

[0051] Example 2: Figure 2 A structural block diagram of an automatic programming control system for stage lighting according to an embodiment of the present invention is shown. Figure 2 As shown, the structure may include: The stage scene data construction module 01 is used to acquire GDTF format stage lighting data, stage setup data, and performance venue data of the target stage scene. It associates and encapsulates lighting channel fields, lighting parameter boundaries, lighting installation locations, stage zones, and venue coverage areas to generate a stage scene data file. This module starts upon receiving a stage data import command from the console. It first establishes a scene number for the current target stage scene, and then links the GDTF format stage lighting data, stage setup data, and performance venue data to the same scene number. GDTF stands for General Device Type Format; the GDTF format stage lighting data records the lighting geometric model, DMX channel allocation, physical attributes, and functional parameters. DMX stands for Digital Multiplex, representing a digital multiplexing protocol.

[0052] The stage site data construction module reads the lamp number, lamp channel field, and lamp parameter boundaries from the GDTF format stage lighting data, and associates brightness, color, pattern, pan / tilt horizontal angle, pan / tilt tilt angle, and flicker-related functions with the corresponding channels. For missing lamp channel fields, the module first calls the local lamp channel template to fill in the missing fields based on the lamp model and DMX channel length. Fields that cannot be filled in are marked as missing fields and passed to the subsequent verification stage along with the stage site data file. The stage setup data is imported from CAD drawings and 3D models. The module establishes a unified coordinate relationship based on the stage boundaries, lighting rig positions, lamp installation points, installation height, and installation posture. When there are differences in coordinate references between the CAD drawings and the 3D model, the module performs coordinate conversion using the stage center point, stage front edge line, and lighting rig reference point, while retaining the original coordinate index.

[0053] After the performance venue data enters the stage live data construction module, the module generates stage zones and venue coverage areas based on audience area data, the nearest audience distance, the farthest audience distance, and the target coverage area. When the venue configuration file only provides distance data, the module uses the stage front edge as a reference to form the audience area boundary, and then combines it with the stage width to obtain the target coverage area. The generated stage live data file is not just a collection of multiple input files, but rather establishes a correspondence between the lighting fixture channel field, lighting fixture parameter boundaries, lighting fixture installation location, stage zones, and venue coverage areas, indexed by the lighting fixture number. This stage live data file is sent to the lighting material generation module as the data source for subsequent parsing of lighting fixture capability constraints, lighting position space constraints, and venue coverage constraints.

[0054] The lighting material generation module 02, connected to the stage site data construction module, is used to parse the lighting fixture capability constraints, lighting position space constraints, and site coverage constraints based on the stage site data file, and generate lighting material files and lighting position layout diagrams according to these constraints. Upon receiving the stage site data file, the lighting material generation module first checks the continuity of the scene number, file version, and lighting fixture number. If the scene number is inconsistent with the current processing task, the module retains the received file but does not proceed to the lighting material generation process. After successful verification, the module reads the GDTF format stage lighting data, stage setup data, and performance venue data from the stage site data file, and converts them into three types of constraints that can be used in the lighting material generation process.

[0055] The lighting fixture capability constraints are formed by the lighting fixture channel field and the lighting fixture parameter boundaries. The lighting material generation module reads the brightness range, color channel, pattern channel, pan / tilt angle range, and DMX channel occupancy length from these. For stage lights without a pan / tilt channel, the module does not assign lighting motion segments that require changes in illumination direction; instead, it retains brightness, color, and pattern-based motions. The lighting position space constraints are formed by the lighting fixture's installation location, installation height, installation posture, and illuminated area. The module divides multiple stage lights into front lighting group, side lighting group, rear lighting group, and overlay compensation group according to stage zoning. If the installation posture of a stage light is in an unconfirmed state, the module includes it in brightness or color-based materials but excludes it from follow spot motion segments that require precise positioning.

[0056] The site coverage constraints are formed by stage zones, audience areas, and illumination coverage boundaries. The lighting material generation module generates lighting material files based on the coverage relationship between candidate illumination areas and lighting fixture groups. When the target coverage area exceeds the illumination range of a single stage light, the module does not expand the lighting fixture parameters but instead uses an overlapping illumination method of multiple lighting fixture groups in the material. The generated lighting material files include lighting fixture groups, basic lighting motion clips, basic lighting effect parameters, and material style identifiers. The lighting layout diagram synchronously records the correspondence between lighting fixture groups and candidate illumination areas and provides the lighting fixture positions, main illumination directions, and coverage boundaries to the material preview and adjustment module for use.

[0057] The material preview and adjustment module 03, connected to the lighting material generation module, is used to write material selection results and lighting parameter adjustment records based on the lighting material file and lighting layout diagram to generate target lighting material. After the console receives the lighting material file and lighting layout diagram, the material preview and adjustment module first compares the scene number in the lighting material file with the currently loaded stage scene data file. If the two are inconsistent, the module stops the current material preview and re-requests the lighting material file corresponding to the target stage scene. If the scene number is consistent, the material preview and adjustment module reads the lighting fixture grouping and candidate illumination areas in the lighting layout diagram and combines them with the basic lighting action clips in the lighting material file to form preview data.

[0058] Preview data runs on the console and is not directly sent to the stage lights. The material preview adjustment module displays light fixture groups, main illumination areas, and motion clip durations based on the light position layout diagram, basic lighting effect parameters, and light fixture parameter boundaries. For areas with coverage gap marks, the module retains the corresponding marks in the preview data. For stage lights whose installation posture is yet to be confirmed, the module locks the pan-tilt head movement of that stage light, only displaying brightness and color changes. The material selection results are written to the light material file version by the console; unselected light materials do not enter the subsequent light show executable file generation process.

[0059] The lighting parameter adjustment record corresponds to the user's or console's partial modifications to the material, including adjustments to one or more parameters such as brightness, color, pattern, gimbal angle, and motion speed. Before writing the adjustment record, the material preview adjustment module checks whether the adjusted parameter belongs to the corresponding lighting channel field and whether the adjusted value is within the lighting parameter boundary. If the adjusted value exceeds the lighting parameter boundary, the module retains the adjustment record and adds a pending limiter mark, which is then processed by the DMX execution conversion module before generating DMX execution control data. The target lighting material is formed by the material selection results, the lighting parameter adjustment record, and the selected lighting material file, and is sent to the light show file generation module.

[0060] The light show file generation module 04, connected to the material preview and adjustment module, is used to extract audio features based on the target light material, the stage data file, and the target audio file. It then performs audio segmentation and matching with light action clips, maps lighting control parameters, and generates a timeline to obtain the light show execution file. After receiving the target light material, this module simultaneously calls the stage data file and reads the target audio file uploaded to the console or selected locally. The target light material stores the material version, lighting group, lighting position layout index, and light action clips; the stage data file stores the lighting fixture number, DMX address, channel fields, and lighting parameter boundaries. Before processing, the light show file generation module checks the version of the stage data file referenced by the target light material. If the versions are inconsistent, the module pauses the generation of the light show execution file and returns the version inconsistency status to the console.

[0061] After reading the target audio file, the light show file generation module divides the audio into multiple audio segments based on the audio timeline. Within each segment, it extracts beat points, audio energy segments, paragraph transition points, melody segments, and style identifiers. Beat points serve as candidate time locations for light action transitions, audio energy segments distinguish areas with significant changes in brightness or action speed, and paragraph transition points differentiate between different music segments. The module then reads light action clips from the target light material, mapping the start and end times of the audio segments to the duration of the light action clips. When the duration is shorter than the audio segment, the module repeatedly calls the clip based on its transition parameters; when the duration is longer than the audio segment, the module compresses the clip based on its scalable nodes.

[0062] After matching audio segments with lighting motion clips, the light show file generation module reads the corresponding lamp number, DMX address, and channel fields from the stage data file based on the lamp grouping in the target lighting material, and maps the processed lighting motion clips to the corresponding lamp control parameters. For clips involving pan-tilt-zoom (PTZ) motion, the module simultaneously reads the lamp coordinates, installation posture, and illuminated area from the lamp position spatial constraints to avoid generating PTU angles that do not match the stage lighting installation status; for clips involving only brightness or color changes, the module performs parameter mapping based on the brightness range and color channels in the lamp capability constraints. The final light show execution file includes time nodes, lamp numbers, DMX addresses, channel fields, target parameter values, duration, transition parameters, and execution order, and is sent to the DMX execution conversion module.

[0063] The DMX execution conversion module 05, connected to the light show file generation module, is used to verify the DMX address, lamp channel field, and lamp parameter boundaries based on the light show execution file, converting the light show execution file into DMX execution control data. Upon receiving the light show execution file, the DMX execution conversion module first reads the time node, lamp number, DMX address, channel field, parameter target value, duration, transition parameters, and execution order, and then checks these contents against the lamp parameter boundaries and lamp capability constraints in the stage data file. If the lamp number in the light show execution file cannot be found in the stage data file, the module does not generate a lamp channel control sequence for that lamp number and writes this status into the execution verification result.

[0064] DMX address verification is performed according to the lamp number and time node. The DMX execution conversion module first checks the DMX addresses used by each stage light within the same time period, and then determines whether the address ranges overlap based on the DMX channel occupancy length. If two stage lights use the same DMX address within the same time period and their DMX channel occupancy lengths overlap, the module marks this state as a DMX address conflict. For stage lights with conflicts, the module reallocates candidate addresses based on the DMX channel occupancy length and the current available address range on the control console. If the available address range is insufficient, the module retains the light show execution file, does not generate the lamp channel control sequence for the corresponding conflicting stage light, and outputs an address anomaly flag.

[0065] The lighting channel field validation verifies whether the channel fields in the light show execution file exist in the corresponding stage light's GDTF format stage light data. If a lighting channel field has been completed using a channel template, the module uses the completed channel field for conversion and records the source of the completion in the execution validation result. For lighting control parameters exceeding the lighting parameter boundaries, the module limits the amplitude according to the lighting parameter boundaries and writes the limited parameter target value into the lighting channel control sequence. Time nodes containing transition parameters form an intermediate output sequence based on the starting channel value, target channel value, and duration; time nodes without transition parameters are written to the target channel value according to the execution order. The generated DMX execution control data is sent to the console output interface and provided to the cloud feedback module for reading the corresponding execution validation results.

[0066] The cloud feedback module 06, connected to the DMX execution conversion module, receives the target light source material, the light show execution file, and the light parameter adjustment record, and sends these materials back to the cloud platform to generate a cloud-generated sample. After the DMX execution conversion module completes the generation of DMX execution control data, the cloud feedback module reads the target light source material, the light show execution file, the light parameter adjustment record, and the execution verification result, and extracts the data items actually involved in the generation process. These data items include light fixture grouping, light position layout index, adopted light action segments, audio segment index, parameter adjustment record, and verified light fixture channel control sequence. The cloud feedback module does not use unadopted candidate materials as the main sample record, but retains them as screening records to avoid mixing candidate materials with the actual execution process.

[0067] When the console maintains a connection with the cloud platform, the cloud feedback module sends the target lighting materials, light show execution files, and lighting parameter adjustment records back to the cloud platform according to the scene number, and generates a cloud-generated sample. When the connection between the console and the cloud platform is interrupted, the module caches the above data locally on the console and writes the scene number and generation time. After the connection is restored, the cloud feedback module uploads the cached data according to the scene number. If multiple material versions exist under the same scene number, the module prioritizes uploading the material version that has been converted into DMX execution control data, and saves the unused version as a filter record. When the cloud platform subsequently generates lighting material files for similar stage scenes, it calls the target lighting materials, lighting parameter adjustment records, and execution verification results from the cloud-generated sample.

Claims

1. A method for automatic programming control of stage lighting, characterized in that, include: S100: Obtain GDTF format stage lighting data, stage setup data, and performance venue data for the target stage scene; associate and encapsulate the lighting channel field, lighting parameter boundaries, lighting installation location, stage partition, and venue coverage area to generate a stage scene data file. S200. Based on the stage site data file, analyze the lighting fixture capacity constraints, lighting position space constraints, and site coverage constraints, and generate lighting material files and lighting position layout diagrams according to the lighting fixture capacity constraints, lighting position space constraints, and site coverage constraints. S300: Based on the aforementioned lighting material file and lighting layout diagram, write the material selection results and lighting parameter adjustment records to generate the target lighting material; S400: Based on the target lighting material, the stage data file, and the target audio file, extract audio features, perform audio segmentation and matching with lighting action segments, map lighting control parameters, and generate a timeline to obtain a light show execution file; S500: Based on the light show execution file, verify the DMX address, lamp channel field and lamp parameter boundary, convert the light show execution file into DMX execution control data, and send the target light material, light show execution file and light parameter adjustment record back to the cloud platform to generate a cloud-generated sample.

2. The method according to claim 1, characterized in that, The stage site data file includes GDTF format stage lighting data, stage setup data, and performance venue data; the GDTF format stage lighting data includes the geometric model of the lighting fixtures, DMX channel allocation, physical properties, and functional parameters; the stage setup data includes CAD drawings, 3D models, lighting fixture installation positions, and lighting fixture installation postures; the performance venue data includes audience area data, the distance to the nearest audience member, the distance to the farthest audience member, and the target coverage area.

3. The method according to claim 1, characterized in that, The analysis of the lighting fixture capability constraints, lighting position space constraints, and site coverage constraints includes: extracting the brightness range, color channel, pattern channel, pan-tilt angle range, and DMX channel occupancy length from the GDTF format stage lighting data to generate the lighting fixture capability constraints; extracting the lighting fixture coordinates, installation height, installation posture, and illuminated area from the stage setup data to generate the lighting position space constraints; and extracting the stage partitions, audience area, and illumination coverage boundaries from the performance venue data to generate the site coverage constraints.

4. The method according to claim 1, characterized in that, The process of generating the lighting material file and lighting layout diagram includes: grouping multiple stage lights according to the lighting space constraints; mapping the lighting group to the candidate illumination areas in the site coverage constraints; and writing basic lighting action clips, basic lighting effect parameters, and material style identifiers based on the lighting capability constraints to generate the lighting material file and lighting layout diagram.

5. The method according to claim 1, characterized in that, The process of writing the material selection results and lighting parameter adjustment records includes: generating preview data based on the light position layout diagram and the lighting material file; receiving the selection results of the lighting material file and receiving the parameter adjustment records corresponding to brightness parameters, color parameters, pattern parameters, gimbal angle parameters or motion speed parameters; writing the selection results and the parameter adjustment records into the material version to generate the target lighting material.

6. The method according to claim 1, characterized in that, The audio features include beat points, audio energy segments, paragraph transition points, melody segments, and style identifiers; the extraction of audio features includes segmenting the target audio file into time segments and writing the beat points, audio energy segments, paragraph transition points, melody segments, and style identifiers into the audio segment index.

7. The method according to claim 1, characterized in that, The process of matching audio segments with lighting motion clips, mapping lighting control parameters, and generating a timeline includes: reading lighting motion clips from the target lighting material; matching the start and end times of the audio segments with the duration of the lighting motion clips; compressing, extending, or repeating the lighting motion clips when the duration does not match the start and end times; and mapping the processed lighting motion clips with the lighting fixture number, DMX address, and channel field to generate a lighting motion timeline.

8. The method according to claim 1, characterized in that, The light show execution file includes time nodes, lamp numbers, DMX addresses, channel fields, target parameter values, duration, transition parameters, and execution order; obtaining the light show execution file includes binding the light action timeline with the lamp numbers, DMX addresses, channel fields, and target parameter values, and writing the duration, transition parameters, and execution order.

9. The method according to claim 1, characterized in that, The verification includes: when there is a conflict in the DMX address, reassigning candidate addresses according to the DMX channel occupancy length; when the lighting channel field is missing, supplementing the lighting channel field and generating an execution verification result; when the lighting control parameters exceed the lighting parameter boundaries, limiting the amplitude according to the lighting parameter boundaries and generating a verified lighting channel control sequence; the cloud-generated sample includes the target lighting material, the light show execution file, the lighting parameter adjustment record, and the execution verification result.

10. An automatic programming control system for stage lighting, applied to the method described in any one of claims 1 to 9, characterized in that, include: The system includes a stage data construction module, a lighting material generation module, a material preview and adjustment module, a light show file generation module, a DMX execution and conversion module, and a cloud feedback module.

Images