Obsidian ONYX: Programming A Busking Showfile From Start To Finish On An NX1
HTML-код
- Опубликовано: 9 июн 2023
- In this video, Ben takes you through the process of programming a busking showfile from start to finish; from an unpatched Capture Visualizer show to a functioning busking file.
Ben uses an Obsidian NX1 with an NX-K as hardware, with Capture Visualizer running on a PC to visualize what he's doing.
This video is not meant to serve as a review or tutorial for any of the hardware or software elements, but merely as an over-the-shoulder look at creating a showfile from the bare beginning (hence we didn't set up a screen recording and other angles). Also, the autofocus (which should've really been manual focus in the first place, this was an oversight) didn't lock where we meant it to, so we apologize if there are important bits that are out of focus on the console. If there are specific topics/points that you'd like explained further, we are happy to explain them; simply comment the timestamp and/or topic, as well as any questions you have.
Fixtures used in the Capture file:
- 8x Chauvet Intimidator 375z
- 14x Chauvet PiX-ILS
- 16x Chauvet SlimPAR 64
- 4x Chauvet Wash FX 2
This video was recorded on a Sony A7iv with a GM 16-35mm lens, and a Rode Videomic for audio direct into camera (5:1 compression was added in post).
Make sure to stay up to date by subscribing to our channel and following us on Instagram and other socials @preampproductions.
For any inquiries regarding booking our services, feel free to reach out to us at info@preampproductions.com and we'll be in touch!
Please comment any questions you have regarding material covered in this video, and if you have any recommendations or requests for any tips or anything, drop that too and we'll cover it!
Hell yeah. Learning from the master
So good! Pleas do another from a top view!
NICEE🔥🔥
Nice!!!
🔥🔥🔥
can you go through how you got the individual pixel control again? i know im close but im not right there yet
Hey there - let me know if this answers that:
Individual pixel control comes from interacting with the fixture instances instead of the master fixture. Generally the instances will be notated by having decimal values after the fixture ID. So if I have a 12-pixel LED bar with fixture ID 301, the instances are going to be IDs 301.1 through 301.12. When I apply effects to the instances and apply delay/wave values, the pixel mapping effect shows as the instances will be doing different things relative to each other. I personally like to create a master instance group (so the 301, 302, 303... IDs) then a pixel instance group (the 301.1, 301.2, all that) so they're already separated when I go to apply anything to the groups. Keep in mind, for pixel effects to show, the master instances need their dimmer raised past 0 (as the master instance represents the fixture's overall intensity). You can also layer effects on both the master and pixel level to create some neat effects.
Could you show how to control the speed of the fx by bpm? Instead of hands on busking all night
In Onyx currently you can only run BPM if the fader is created as a chase, FX does not have BPM. At least it didn't in version 4.8, the 4.9 RC version might have it.
OMG Wha?? Hey Ben!
YOOOO
Saw tooth! Lol