Rode Wireless Go II

Can you imagine if a monitor corrupted your footage if you turned it on after your camera? My monitor wouldn't receive signal from GH5 if gh5 was already recording when I connected it. But my A7SIII will
 
Can you imagine if a monitor corrupted your footage if you turned it on after your camera? My monitor wouldn't receive signal from GH5 if gh5 was already recording when I connected it. But my A7SIII will

Yeah, this is unacceptable. I haven't put a lot of mileage on my units yet but this requires further testing...
 
My new Rode Go 2 does the same clicking sound. What did Rode do for you or did you get it to go away?
Thanks, Patrick Morrow
 
I went through this thread and skipped the patent infringement parts. What I did not read:

Has anyone tested the transmitter with a dpa or sanken which needs minimum 3 - 5V phantom power? How solid is the 3,5mm jack?

If the receiver in on and you switch on the transmitter - does it automatically start recording internally via the internal mic?

Thanks!
 
Last edited:
Answer #2 first. Yes if under preferences in the Rode Central app the "Always Record" button is checked. If it's unchecked you can use the TX units as just that, TX only units, without recording internally. With v1.6.0 software you can now use the TX units as stand-alone recorders. In other words, the RX unit doesn't have to be turned on.

Answer #1 I would suggest yes but you would have to double-check that for the Sanken and DPAs. I've wired a couple of Sennheiser MKE2s to work with the TX units and getting very satisfactory results. The MKE2s require 7.5 volts with an operating current consumption of 250 µA. These little rodents seem to be able to supply that without any difficulty.

Regards the 3.5mm jack sockets. They seem to have a pretty firm grip on the 3.5mm plug when inserted. No problems with pull-outs so far. Mine are tight enough that I would worry more about cable damage first if such tension was applied to pull the plugs out.

Post #129 shows you one of my solutions though I'm only using that when there is a lot of physical movement going on. Like I had with a Phys Ed teacher training a class of students

Chris Young
 
Last edited:
Hi guys. I just bought the Rode Go II and it's still unopened. I'm reading all of these issues and I'm wondering if I should send it back.

I'm a real estate photo / video guy and I was wanting the dual channel features. I already have a Sennheiser G3 and a Sanken Cos lapel mic. Should I send the rode back?
 
Hi guys. I just bought the Rode Go II and it's still unopened. I'm reading all of these issues and I'm wondering if I should send it back.

I'm a real estate photo / video guy and I was wanting the dual channel features. I already have a Sennheiser G3 and a Sanken Cos lapel mic. Should I send the rode back?

No. From what I can see as long as you make sure you turn on the receiver before the transmitters (until the patch arrives) all will be fine .
For real estate I assume these will be interviews at only a few metres so they will be exactly what you need unless you are in a space full of competing wifi?
 
No. From what I can see as long as you make sure you turn on the receiver before the transmitters (until the patch arrives) all will be fine .
For real estate I assume these will be interviews at only a few metres so they will be exactly what you need unless you are in a space full of competing wifi?

Does the high quality recording actually work, or is it buggy?
 
mine arrived today. I have a very strange issue. On the C300iii and the Zoom H1n the I hear an ugly interference from the receiver.
It's subtle on the C300iii and on the Zoom H1n I can hear it even when I hold the RX close to the recorder without plugin it in.
It happens also when both transmitter are off.

I don't hear it on the R5 and neither when I plug into the Tentacle Track E recorder and neither on the Roland R6.
The C300iii is my main purpose. If it doesn't work properly it's useless for me. Has anyone a similar experience or heard about it?

Zoom H1n
https://www.dropbox.com/s/7ez2avop749ibit/210625-214050.WAV?dl=0
C300iii
https://www.dropbox.com/s/097i9zv7hv3qpiz/C300iii.wav?dl=0

The internal recording seems okay.
 
Sounds suspiciously like hi-frequency RFI. Two things that can contribute to that are insufficient RF shielding on the recording device and using unshielded cables. With regards to the second point. As you would be aware the Wireless Go II cables are not 3 pin shielded cables. They are common or garden unshielded cables. Before you ditch the Go IIs I would strongly suggest trying out and testing the units with some clip-on ferrite ring core RFI EMI noise suppressor chokes. I have successfully eliminated RFI in the past on unbalanced RCA cables and I do know of people who have eliminated the problem on mic cables. The Rodes being wireless frequency devices running unshielded cables may well be the problem. A bit of a surprise to me that you are suffering the problem as I have now used Go II's on four different cameras and not suffered any RFI issues. Mind you none of them Canon cams. A last thought! Firstly can you try them through a decent quality ENG mixer as most of them have very good RFI shielding? If the problem disappears through a mixer then it is almost sure to be RFI in which case the ferrites might be worth go.

Chris Young

A bit of a primer here:

https://en.wikipedia.org/wiki/Ferrite_bead

available all over eBay and most decent electronic stores.

https://ebay.to/3dfphCR
 
update.
I forgot to turn phantom power off. Stupid me.
it works now on the C300iii. I don't care about the H1n
--

thanks Chris. I wrote to the Rode support. Maybe it's a faulty unit? If it's a general issue I will ditch it indeed. The clip on ferrit cores are not trustworthy for me. I would not feel safe. But thanks a lot for the enlightening. As I wrote if I hold the RX close to the Zoom H1n I can hear the interference without plugin a cable to the recorder
 
Last edited:
For those having issues with some backup files crashing the Rode Central app and refusing to export - like some others, I sent a file to Rode Support for conversion, but after waiting 7 weeks I gave up (they were "having trouble" with it). In the end I just played it in the Rode Central app, and recorded the output in real time with Windows Recorder. I could just as easily have used the headphone out on my laptop into my Zoom recorder. In 3 months of use, I have only had the one backup file which has refused to export, so this workaround shouldn't be needed too often hopefully.

This system remains a fantastic bit of kit for my documentary shooting.
 
For those having problems - and I haven't since the early days and initial flurry of firmware updates - has the newly released firmware (now version 1.6.5) helped at all? As usual, there are no details of what the firmware update has changed nor is anything obviously different (which suggests a bug fix). And, again, I've asked Rode to provide details of the firmware versions...

Cheers,

Roland
 
OK, I've now heard back from Rode about firmware v1.6.5, as follows:

Firmware 1.6.5 is essentially a bug fix, or rather, a bug prevention.
With any Wireless GO II kit which is on 1.0 firmware (brand new out of the box), not only will it update the firmware to 1.6.5, but it will also perform a factory reset on that unit. This is because performing a factory reset from the get-go will safeguard against having files which fail to export.
(In case this issue ever does occur though, if one sends the source files to us, we can convert the file(s) for them).
(Also, firmware 1.0 has internal TX recording disabled out of the box, so this firmware won't inadvertently delete any recordings).


And, also technical support volunteered the following in relation to the clicking that some have had problems with:

Something I'll let you know though, is a bug we'll be looking to fix hopefully in the next firmware update.
Essentially, if the TX unit(s) are turned on a minute or two before the receiver, this can cause 'clicks' in the outputted audio from the RX.
If this is occurring during recording, turning off and on again the TX units will fix this.
For now though, to prevent this issue, as long as the RX is turned on first, then everything will perform as expected.


Obviously, this is something that some of you have worked out already.

Cheers,

Roland
 
Back
Top