Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Proxy Module...

Only trouble with Wifi is it's not multi-cast. So there will be limits to how many people can view the stream at once before nobody can.

There's nothing inherent about wi-fi that makes multicast impossible. True, a lot of wi-fi base stations don't implement IP multi-cast, but they certainly could -- something a quick Google search would reveal.
 
There's nothing inherent about wi-fi that makes multicast impossible. True, a lot of wi-fi base stations don't implement IP multi-cast, but they certainly could -- something a quick Google search would reveal.

I concur. You could also, in theory, just skip the whole multi-cast packets, and just broadcast it encrypted, so anyone who can decrypt it will be able to view it. So no bandwidth limitations.
 
Will this be H.264 in a QT wrapper?
 
Hey Jim,
is it possible to put a custom "bug" or superimposition as you record to this module?
I would like to make sure any possible H.264 "broadcast" would be controlled as much as possible.
 
Hey Jim,
is it possible to put a custom "bug" or superimposition as you record to this module?
I would like to make sure any possible H.264 "broadcast" would be controlled as much as possible.

That's a great idea for protecting against the misuse of reasonable quality footage that is being passed around to clients right after shooting. Burn- in of filename and metadata would also be great.
 
I love the idea of an H.264 proxy for one reason alone:

Web dailies.

Sometimes people off-site need to see what happened. They don't want drives posted, they want stuff online.

With an H.264 module, it's one step at the end of the day: upload the H.264's.

Brilliant!
 
Rod,

A friend of mine called Teradek and asked about the Cube and was told he would bee all kinds of extra hardware and servers to do anything with it. The website makes it sound like you can easily stream from the camera with nothing but something to receive the signal.

Can I use the Cube to multicast h.264 to multiple devices on a local network on set?


Dusty
 
Dusty,

Weird, someone 86ed my first post. Thanks admins for the welcoming party.

Cube works with ad-hoc networking (meaning point to point) or infrastructure (meaning with WiFi router in between). We've done a bunch of testing with a RED ONE on a steadicam rig, to a router, to a Macbook Pro, and that's all that is needed. You can record the stream using VLC.

For multicast we recommend a layer 2 managed switch. Multicast and streaming to the Web both require some networking savvy on the part of the user, but that's true with any network device.

rC
 
Dusty,

Weird, someone 86ed my first post. Thanks admins for the welcoming party.

Not weird. It was in violation of the advertising policy here. And no, it wasn't me who deleted it, but I would have if I had seen it first. Sorry for the misunderstanding though. Please shoot a PM to Jason Ramsey. He can fill you in on advertiser / sponsor details.

Other than that, welcome aboard. :)
 
We've done a bunch of testing with a RED ONE on a steadicam rig, to a router, to a Macbook Pro, and that's all that is needed. You can record the stream using VLC.

How is the delay on the Teradeks?

I'd prefer to go with the RED but if that one is not available...
 
I love the idea of an H.264 proxy for one reason alone:

Web dailies.

Sometimes people off-site need to see what happened. They don't want drives posted, they want stuff online.

With an H.264 module, it's one step at the end of the day: upload the H.264's.

Brilliant!

Excellent! Yes I really think that is very useful.
 
There's nothing inherent about wi-fi that makes multicast impossible. True, a lot of wi-fi base stations don't implement IP multi-cast, but they certainly could -- something a quick Google search would reveal.

Care to point to a commercialized multicast wi-fi solution which can reliably stream h264 and doesn't require the NICs to be custom configured with non-standard 802.11x?

Wifi is notoriously poorly designed for multicast streaming. For example: the low power mode catch. Care to track down who on set has their NIC configured sub-optimally?

"Who here has low power mode enabled?"
 
Care to point to a commercialized multicast wi-fi solution which can reliably stream h264 and doesn't require the NICs to be custom configured with non-standard 802.11x?

Wifi is notoriously poorly designed for multicast streaming. For example: the low power mode catch. Care to track down who on set has their NIC configured sub-optimally?

"Who here has low power mode enabled?"

Well it can be done, but only with investment, Cisco WiSM through LWAPP radios can do it. I have successfully done it with a 1mb H264 stream to very large number of clients. But its not cheap and very very technically challenging to achieve.
 
Jeff, thanks for welcoming me onboard. I told my boss yesterday that I was participating in the forum and he replied - Confucius say "Enter Jacuzzi slowly so you do not get your balls cooked."

To be clear on my position: I've been working with H.264 for the last two years, and there's a ton of talk about the Proxy Module. So I figured I could add value to the forum by addressing questions that pop-up regarding streaming, compression, etc. By definition, if I mention the product we make it sounds like a cheesy sales pitch, but to be honest I'm a RED camera fanboy, we've got one in-house, and I'm more interested in participating in the forum on behalf of my own self interest as a shooter than the company's.

To answer Sander's question: How is the delay on the Teradeks?
The latency is variable and user configurable. Cube performs a massive amount of compression (something like 200 to 1) before streaming. So that crunching process takes about 100 milliseconds, then the transmission, and then the decoding. Decoding using a Macbook running VLC takes anywhere between 100 milliseconds to up to 2 seconds based on the settings you choose. We’ve found that in practice, between 300-400 milliseconds end-to-end is the sweet spot.

Today, Cube works best with a laptop (Macbook Pro is my favorite, I'm an Apple fanboy too) by streaming RTP (encapsulation) to VLC. iPad streams HTTP Live Streaming, which is extremely stable and provides excellent video quality, but the latency is HUGE (10 seconds!!). It’s native to the iPod & iPad platform. We’re currently developing an iPad/iPod app that uses RTP to circumvent the latency. The app should be completed in 6-8 weeks. A Cube streaming to an iPad with less than a half second of latency is going to knock the gray haired fellow right out of his director’s chair.

And Jay: You're absolutely correct. If you want to multicast, you're going to spend some dough on a layer 2 managed switch, that'll set you back a few bucks. If anyone of you guys is willing to buy the switch and test it (I mean really giver' a go) I'll see if I can loan you a Cube.

rC
 
Does anyone know if the proxy module is close to production or not? My guess is that it is behind Epic/Scarlet production, but having this thing around sooner rather than later would be music to my ears.
 
I think they're kind of preoccupied with getting the cameras out.
And with the entire HDRx and MagicMotion thing, they've got their hands full I guess.

This should follow pretty soon though. It's basicly a hardware compressor with wifi and ip streaming built-in.
I wouldn't be surprised if they had a finished prototype in the labs, and the only thing left is to place an order with the manufacturer.
But, like I said, image makers first, then compressors. :-)
 
Back
Top