It's a good question - I didn't look for it as I use these cameras for streaming rather than ISO recording but I can imagine that would be useful to people. It's not on their VISCA spreadsheet (www.obsbot.com/explore/obsbot-tail-air/visca-over-ip) but you could email their tech support and request it to be added. You could however use OSC commands direct to the camera or via the Center App as that is supported: www.obsbot.com/explore/obsbot-center/osc

Thanks for the feedback, glad you found it useful!

It's meant to be, but some cables only work one way, so if it's not working, try flipping it 180

You'll need one module per camera so that you can connect with separate IP addresses, and then once you've built your first page you can mostly copy it to the new modules.

@@davidjoshuaford So you basically need a different page for each camera, buttons for up/down/left/right/etc can't be shared among multiple cams by selecting a camera button... gotcha. Thank you!!

@@jordanearth11 Canon CR-N300

@@BenjaminTemplar it’s a Canon PTZ camera, controlled by my DJF profile using Companion. The preset traces are built into my run of show

@@davidjoshuaford Spectacular! Have you done a tutorial about it? Id love to watch it if you already did and if not, I would love to watch it if you ever make it! Hollywood caliber my friend!

@@davidjoshuaford Spectacular! Have you done a tutorial about it? Id love to watch it if you already did and if not, I would love to watch it if you ever make it! Hollywood caliber my friend!

Thanks John!

Haha thanks…photorealistic top view! 😊

Thanks! I knew there must be a random setting somewhere. Maybe that was the problem with the Cut page source reel as well…

For the Stream Deck hardware, I just update via Elgato's native software. Then for Companion, export a back up of your configuration, then just boot up the new version. There's not usually a stream deck hardware update that makes it incompatible with Companion, but if there is then it's usually updated by the Companion team within two weeks.

It's an Otto bhpho.to/45qWNjb, though I'm interested to try the Shure SE215 Pros some day bhpho.to/3KF7pBL

I had a Sony TRV900 back in 02, and used a Z1 in 08 on some productions, but I've always been in the "detachable-lens" realm for production work since the 5DmkII days... These days it's a mix of C300's/C200s for live. You're right that camcorders are certainly a lot cheaper/ more for your money for live production, particularly given the inbuilt zoom range. But I've just personally invested a lot more in cinema cameras/lenses for production work that I carry over into live settings, and the PTZs are an incredible return on investment with reduced labor/crew. If I get the c400 I'll probably need to add a 24-105 2.8 for live/event work... (or 17-120 😅) and even then it won't have the full zoom range of a camcorder.

@@davidjoshuaford Definitely tradeoffs with camcorders vs. cine cameras! Looking forward to you getting a c400 + expensive glass (or REALLY expensive glass 😂) one of these days. BTW, thanks for your videos and streams! Your chennel's awesome.

I’ll have to experiment when I’m next in the studio

Good question - they've changed it now to "internal: Custom Variable: set with expression". Choose the variable you want to change, and then if you want to modify that same variable, add that same variable back into the "Expression" field and then modify it.. i.e. "$(internal:custom_value) + 1" would add 1 to the a variable called "value"

I wouldn't buy it again... cost me an additional $180 to have it repaired. Tech said there's a design flaw that makes it easy to blow a circuit if unplugging a phantom powered mic. Since the repair it has been working ok.

@@davidjoshuaford thanks for the answer. It’s good to know that at least they have pinpointed the flaw.

In that case do they suggest turning phantom power off on that line before unplugging to avoid that issue?

I thinkso, but in a fast paced production environment, and a hybrid photo/video workflow it’s easy to miss that

@@davidjoshuaford Thank you!

Hey! Glad you found it helpful. I have a livestream about that router in my feed, and I’ll do some more livestreams on the GL.iNet routers in the upcoming weeks/months. It’s essentially the same as any other router, and you’re connecting internet via the WAN port, just that these travel ones are very portable and have great features.

@@davidjoshuaford Wow that was fast! Thank you so much for your response. I’m watching your GL.iNet Slate AX Wifi6 Stream and I think I can set the travel router up. It looks like I will need to give each device a Static IP address with same subnet mask. I will let you know if I get everything configured. Thanks again

@@Casuallz You're welcome - the GL.iNet routers by default run on 192.168.8.1, so you'd set your ATEM and other devices to static addresses within that range 192.168.8.xxx

Thanks Eric!

I haven't tested it on Playoutbee but I would expect that it would work.

As far as I'm aware the HyperDeck arranges the files alphabetically. You could jump in over FTP using a tool like CyberDuck to rename the files. I usually add an 01, 02, 03 etc to the start of my filenames in preproduction for this reason.

If you're talking about my ATEM profiles, you'd do a full import of the ATEM profile first, then go back and do an individual page import to a blank/available page. When importing, you can choose to create a new connection with a new name, or to link the module to an existing ATEM or HyperDeck connection if you already have them installed.

Check out E69!

Thank you, appreciate the comment!

Yes, but Companion updates are very manual to process so will take me some time

Yes, that’s where the inspiration came from, thank you Niko!

no because all my cameras a Canon. I do like Sony's cable extension design though, and which Canon would make a first-party audio hotshoe

sure does!

what i really want to do is use the 1800 to bring in my camera signals and tehn use the yolobox to recognize them all as a separate video source based on the ip addresses assigned

The ATEM Mini can't send its Mulitview out via USB-C, so the best way would be to connect the HDMI Out to a UVC converter (HDMI-in, USBC out), and then the Multiview will show up as a video source in your computer apps. A common device is the CamLink4K, but there are cheaper ones out there on Amazon as well.

Glad it was helpful!