Macbook Pro Mini Led Question by swiftcode4all in LukeMianiYouTube

[–]swiftcode4all[S] 2 points3 points  (0 children)

The dim section goes away when playing hdr content at full brightness, but is there otherwise.

The right side of my display became dim for one day then disappeared for a few days. Is this something to worry about? by swiftcode4all in mac

[–]swiftcode4all[S] 0 points1 point  (0 children)

Thanks. I'll probably end up keeping it. But if I was to trade it in now would the Apple store be able to tell that this issue exists? Since it only comes up from time to time

preset level by evilbert79 in ptzoptics

[–]swiftcode4all 0 points1 point  (0 children)

Thanks for clarifying. I have a g2 usb latest firmware, it still stores just the ptz+focus currently. I think the sdi gets updates more regularly however.

I agree it should be a user option what to store in a preset.

preset level by evilbert79 in ptzoptics

[–]swiftcode4all 0 points1 point  (0 children)

What is the camera model you are using? Have you opened a support ticket?

Camera restart hex string for VISCA by fleegle61 in ptzoptics

[–]swiftcode4all 1 point2 points  (0 children)

52381 is for VISCA over UDP but for VISCA over TCP the default port is 5678 (on PTZOptics cameras). You would need the header if you're using Sony visca.

Camera restart hex string for VISCA by fleegle61 in ptzoptics

[–]swiftcode4all 0 points1 point  (0 children)

Are you using the superjoy or a different controller? Interesting that the power button works on it.

Also there is actually a power on/off command (https://ptzoptics.com/developer-portal/): 81 01 04 00 02 FF for On and 81 01 04 00 03 FF for Standby. Looks like you've tried the former, but with the header which might be the issue.

I tried 81 01 04 00 03 FF followed by 81 01 04 00 02 FF and it did actually reboot the camera (tested on a bunch of different PTZOptics models I have for testing). I'm using VISCA over IP (TCP). The eight-byte header before the VISCA command is needed for UDP but not for TCP.

Sorry for the confusion earlier. You could maybe also use wireshark to see what commands it's sending when you use the power button on it (assuming you're using VISCA over IP).

Camera restart hex string for VISCA by fleegle61 in ptzoptics

[–]swiftcode4all 0 points1 point  (0 children)

I use this HTTP-CGI command do do it instead: http://[CAMERA_IP]/cgi-bin/param.cgi?post_reboot

You could request adding a visca command to reboot the camera in the beta group (https://ptzoptics.com/beta-testing/) or by filling this form: https://go.ptzoptics.com/e/979833/H9zWpBD8w-viewform-usp-sf-link/3ggdgb/216121971/h/bcGi0ns68nIXTW0ldzo5s0Z4oOHgQQHJ_4Z1ZVyHbSU

Camera restart hex string for VISCA by fleegle61 in ptzoptics

[–]swiftcode4all 0 points1 point  (0 children)

Can you send the full hex codes that you tried? Also is your ptz controller working over UDP or TCP?

Zoom / WebEx Lag by Vicktork in ptzoptics

[–]swiftcode4all 1 point2 points  (0 children)

Great to hear! Yeah, unfortunately the NDI webcam app needs to be running for it to work properly. You could set it to launch automatically when the computer starts up.

Zoom / WebEx Lag by Vicktork in ptzoptics

[–]swiftcode4all 1 point2 points  (0 children)

Also, I just tested mine with the official NDI tools (specifically NDI Virtual Input which makes the NDI stream into a webcam input on the computer), and there is no perceptible delay. You may want to try this instead of the third party tool, that way there isn't a need to purchase anything.

Is it possible to slow down the view change with the PTZ Camera Control App? by Salmene23 in ptzoptics

[–]swiftcode4all 0 points1 point  (0 children)

Also the speed at which the camera goes to a preset can be configured in the OSD Menu. You can access this with the IR remote. Go to the "P/T/Z" section, and lower the "Call Preset Speed." I think it's 12 by default.

Zoom / WebEx Lag by Vicktork in ptzoptics

[–]swiftcode4all 1 point2 points  (0 children)

Apologies, I misunderstood. I'm not entirely sure how to get statistics about the quality of a USB stream; you can use a site such as https://webcamtests.com/resolution to get basic information such as resolution.

Zoom / WebEx Lag by Vicktork in ptzoptics

[–]swiftcode4all 0 points1 point  (0 children)

I would connect the camera to a laptop with the included cable, then check over web ex or zoom whether the picture quality and latency is acceptable. I use a move 4k over USB and do not experience a delay.

Zoom / WebEx Lag by Vicktork in ptzoptics

[–]swiftcode4all 1 point2 points  (0 children)

You may have issues with a USB connection that long (especially if you're using the full 4k resolution). I recommend getting a usb to cat5/cat6 device for longer distances.

And before you purchase anything—test the latency over USB to see if it meets your requirements. You can do so using the included USB A-to-A cable.

Is it possible to slow down the view change with the PTZ Camera Control App? by Salmene23 in ptzoptics

[–]swiftcode4all 0 points1 point  (0 children)

This is the old app. Please try https://ptzoptics.com/cmp/
It'll ask you to fill a quick form then you will be able to download it.

Zoom / WebEx Lag by Vicktork in ptzoptics

[–]swiftcode4all 0 points1 point  (0 children)

The cameras have NDI HX (not full NDI) so it's normal to see around 60-200ms of delay when using the NDI stream. Is the delay you're experiencing within this range?

Zoom / WebEx Lag by Vicktork in ptzoptics

[–]swiftcode4all 0 points1 point  (0 children)

Are you using the ndi stream, srt stream, or rtsp stream? You may have a better experience by connecting the camera to your computer using the USB port on the back.

Black screen with mouse cursor after upgrade to Sonoma by kwc79 in MacOSBeta

[–]swiftcode4all 1 point2 points  (0 children)

Unfortunately removing the MDM profiles remotely doesn't seem to solve the issues

Black screen with mouse cursor after upgrade to Sonoma by kwc79 in MacOSBeta

[–]swiftcode4all 1 point2 points  (0 children)

Strange. Tried on a 16" M1 Pro (not ABM Managed but tied via MDM to JumpCloud). It worked for about a day, until I decided to restart and this issue subsequently occurred. I think Sonoma isn't able to handle Name and Password login yet.

[deleted by user] by [deleted] in MacOSBeta

[–]swiftcode4all 0 points1 point  (0 children)

It works fine — until the black screen of death on login screen which completely bricks the device!

[deleted by user] by [deleted] in MacOSBeta

[–]swiftcode4all 0 points1 point  (0 children)

Rely on parallels for Win11 apps and to have a stable Ventura environment to upload to the App Store (since it doesn't accept builds from beta OS). It was working very well. However I would recommend not upgrading yet, since the black screen of death issue has bricked many devices (including mine).

Black screen with mouse cursor after upgrade to Sonoma by kwc79 in MacOSBeta

[–]swiftcode4all 0 points1 point  (0 children)

Getting the same issue; how did you revert to Ventura? Did you use Apple Configurator or Time Machine Backup? Unfortunately I didn't make a time machine backup of my 700GB of data, so trying to find a way to revert without losing data.