Rodecaster Pro II Primary Channel Audio Connection Failure - Reported to Rode - Case No: 393265 скачать в хорошем качестве

Rodecaster Pro II Primary Channel Audio Connection Failure - Reported to Rode - Case No: 393265

Bug Issue. This video documents a bug currently reported to the Rode Development Team that documents a persistent bug that disconnects the RCP II Primary Channel Audio connection between the RCPII and an Apple M1 Mac Studio Max. Connection Description: RodeCaster Pro II USB Type C Port 1 connected to an Apple M1 Mac Studio Max USB Port (Rear Port via a USB Type A to Type C Cable adapter). Test results in this video were initially based on connecting the M1 Mac Studio Max front USB Type C ports to the RCP II Primary/Secondary USB Type C ports. The Apple M1 Mac Studio Max USB Type C ports cable connections were subsequently moved to the USB TYPE A ports on rear of the M1 Mac Studio Max using a Type A to Type C cable adapters. Once done, the test was rerun. Same failure occurred using the USB Type A rear ports. Observations: 1. RCP II Primary Channel (USB Type C - USB 3.0) audio connection to Apple M1 Mac Studio Max disconnects are persistent. Audio connection can only be re-established via a Power ON Reset of the RCP II or by pulling the RCP II Primary Channel Cable. 2. RCP II Secondary Channel (USB Type C - USB 2.0) Channel is typically not affected by this bug and can be used as a circumvention when the primary channel audio connection fails. However, it does drop occasionally when this bug occurs. 3. Pulling the USB Type C cable connected to RCP II Primary Channel Port will allow the RCP II Secondary channel to re-establish a connection to the Apple M1 Mac Studio if the RCP II primary audio channel fails as described in observation item 2. 4. When the cable to the RCP II Primary Channel (USB Type C) is reconnected the Apple M1 Mac Studio Max after the audio connection failure, the connection will occasionally re-establish itself (not always) but will then disconnect again after 2-5 minutes. The RCP II Secondary Channel (USB Type C) connection to the Apple M1 Mac Studio remains intact and maintains the audio connection between the RCP II and the M1 Mac Studio Max. Conclusion: This bug was first reported to the Rode Development Team back on June 23rd by myself. Other RCP II users have reported the same problem on social media (YouTube, Reddit, Discord, etc.) so it is a real problem. I have this problem documented with Rode (Case #: 393265) and support from the Rode Development team has been marginal. They cannot recreated the problem. However, the problem is well documented in this video. My workflow is typical of most streamers in that it includes the RCP II, an Apple Mac Studio M1 Max, a Blackmagic ATEM Mini Extreme Pro ISO, Blackmagic Design HyperDeck Pro Plus, an iPhone XII connected to the RCP II via Bluetooth, RCP II Line Connection to the ATEM Mini Extreme Pro ISO and a Sonnet Echo Express PCIe III which provides a 20GB aggregate network connection via a MikroTik CRS309 Cloud Switch. All networking equipment is Ubiquiti (EdgeRouter 12 and EdgeSwitch 24 devices are used). Verizon FIOS is the network carrier. Nothing out of the ordinary is used in this workflow and I would say that most advanced streamers out there have similar workflows. So, what could it be? We even thought static electricity might be the cause, but I grounded the RCP II via a grounded outlet adapter. No joy. Problem still occurs. "SuprUsr Stan" has reported this issue in a video on YT, so there are other RCP II users experiencing the same problem. I have been working with the Rode Development Team to help them diagnose, isolate and resolve this problem since I reported it back on 6/23. My thoughts are that the problem lies in the RCP II Primary Channel Port (USB Type C port - USB 3.0) as the root cause of the problem. I have eliminated the Apple M1 Mac Studio Max as the source of the problem via various testing scenarios. The RCPII Secondary Channel (USB Type C port - USB 2.0) that is connected to the M1 Mac Studio Max continues to work (most times after a failure) and is the circumvention that I have been using until the Rode Development Team can re-create, diagnose, isolate and fix this nasty bug. One last note is that I was using the Rode USB Type C cable (provided by Rode) to connect the RCPII to the M1 Mac Studio Max. Thinking that the cable provided by Rode might be source of the problem. So, I replaced it with an Apple USB Type C cable. No joy. Problem still occurs so it is not a cable issue. My best guess is that the problem lies in the RCPII primary channel USB Type C port which runs USB 3.0. Call to action: If anyone viewing this video has experienced the same problem, please report it to the Rode Development team and shoot me a note ([email protected]) to let me know that you are having the same issue. It would be extremely helpful if you can share similar experiences and what you done to attempt to either fix or circumvent this problem. Also, please like and share this video to other potential RCP II users in hopes that they too are experiencing the same or a similar problem. Thanks a bunch...