Missing magazines in Liveplay server

[Andrew clemson]

Bit of an odd one, running liveplay via teradek from an epic. All running fine as per usual but for some reason the server is refusing to register any new folders. I updated both my iPad client and the server but still no dice.

Still able to playback clips via airvideo, but as you can imagine it doesn't dazzle quite as much as liveplay.

Any ideas?

 

[Nick Pasquariello]

Is Teradek not CREATING new folders when you record? Or is LivePlay not SEEING the folders that Teradek is creating?

If it's the former, then I'm guessing some permissions are set incorrectly in your NFS share, and Teradek isn't being allowed to create new folders, even though you have asked it to do so. If it's the latter, you could try writing all clips to the main folder (rather than creating a new sub-folder per Mag) and see if that works. If it does, that would tell you that the problem is specifically with LivePlay recognizing clips in subfolders, which eliminates a LOT of other possibilities for the source of your issue.

But other than that, I'm about one step behind you. Just yesterday (and continuing today) I'm trying to get Red One --> Teradek --> NFS Share on an Apple Laptop --> LivePlay to work. Ran into a snag mounting the NFS share yesterday. Permissions on the Share are where I would expect the majority of the issues. The second largest source of issues in this setup is likely the particular wireless setup one has running.

 

[Scott Crawley]

Are you running OSX Lion? I have had many issues with permissions in Lion.

 

[Chris Peariso]

Hi Andrew,

I have some ideas that might help send me an email chris at lightiron dot com and we will see if can figure it out for you.

Thanks
Chris Peariso
CTO
Light Iron
www.lightiron.com

 

[Nick Pasquariello]

Andrew, if you figure it out, can you post your solution? Like I mentioned, I'm working through getting this exact thing up and running. I haven't run into your exact issue, but every bit of information on how this setup works, helps.

 

[Andrew clemson]

The teradek is A-OK. Clips being created as they should and playing back on laptop or via airvideo with no problems. Very odd.

 

[Nick Pasquariello]

Maybe you've already done this, but connecting to each TX and RX and individually and then updating to the latest firmware (downloaded from Teradek's site) helped make things go smoother.

We have Teradek working (though, if we try to record a clip while Teradek is still transcoding a previous clip, it skips the now-recording clip. At our rate of shooting, this will not work for us in terms of proxy creation). We have LivePlay working (log in, clips from Teradek or elsewhere show up and can have notes added). We can log in to ToDailies, but no clips show up.

Anyone have any thoughts on THAT one?

 

[Chris Peariso]

Hi Nick,

We have seen some weird permission problems with Lion that cause symptoms similar to what you are describing...
Try quitting Light Iron Server and changing the permissions on your root asset folder to be everyone = read/write (and then propagate those permissions to subfolders / files) then start a new Light Iron server project and try again.

If that does not work feel free to shoot me an email and I will continue to help you troubleshoot.


Thanks.
Chris Peariso
CTO
Light Iron
www.lightiron.com

 

[Nick Pasquariello]

I'll give that a shot. The folder that LightIron Server was watching was a folder that had been set up as an NFS share with open read/write permissions so that the Teradek Cube could write proxies to it.

When my boss first tried LIS with ToDailies, it worked instantly for him, but he was on Snow Leopard. I spent over a day tweaking Teradek and LIS to get as far as I did. LIS was the easy part; the Teradek has some slow response times (possibly because of an overly cluttered 2.4GHz and 5GHz spectrum in the area), but once I got that working with the NFS share, LivePlay saw the clips very soon thereafter. Which is why it was odd that ToDailies couldn't see them. But checking permissions (and even chmod'ing to 777) is certainly something I can try.