Need to stream video over a network using iOS devices? Transmitting video over wifi or Cat5e using an Apple tablet or phone can be really easy. This is how to do it.
A recent gig required live video and audio streamed from one building to a projection screen in another building some distance away. The gig came as a last minute request (the night before a morning event). I had little time to prepare. They were in a bind and didn’t have anyone else they could count on. Though I did not own very much video equipment, I knew I had to help. I had to be creative in order to accomplish the task. Here is what I did.
First, I broke the problem into 2 parts: audio and video. Figuring out an audio solution was easy, since I’m primarily experienced in audio and had all the gear for that portion. So the tough part was figuring out video. Another factor to consider was that the signals needed to be fairly secure (to prevent easy hacking), so wired was preferred over wireless options. My plan was to send audio over balanced audio cables and video over ethernet/Cat5e cable to reassemble on them together on the other end.
Second, I scoped out the location. The buildings were two small structures set on opposite sides of a small parking lot. A quick reading with my super handy laser distance measurer revealed the buildings sat about 100 feet apart. This measurement was helpful for figuring out how much cabling I need to run between the two locations. In addition to the distance between the two, there was also a height factor (the receiving location was on the second floor), plus there were interior distances that needed to be run. Altogether the total distance from the source to the destination required enough cable to reach somewhere in the ballpark of 200 feet.
Third, I needed to inventory my equipment list to figure what I needed to buy, if anything. Luckily, I found a nice iOS app that streams video quite reliably.
Video Signal Flow
This is the basic routing I came up with:
iOS Device with Video Source App > Wifi Router > Ethernet Cable > Computer with Video Destination App > HDMI Cable > Output Device (Display or Projector)
And here are the specific details of my setup:
- a newer iOS Device (iPad/iPhone/iPod touch) with good camera (I used an iPad Mini 2.)
- a video streaming iOS app (I used AirBeam by Appologics UG with its companion desktop app AirBeam Pro.)
- a wifi router (I used an older AirPort Extreme Base Station A1354. For increased security, I also made sure the SSID was not broadcast, the network required a WPA2 password, and the password was fairly long and complicated. Not a perfect solution, but much better than an open wide, password-free network.)
- Cat5e cable (I used cable rated for outdoor use since it was kind of rainy and wet outside.)
- an Apple computer with ethernet jack (I used an aged Mid-2010 MacBook Pro.)
- a video adapter for connection to video cable (I used one of these AmazonBasics Mini DisplayPort (Thunderbolt) to HDMI adapters.)
- a video cable (I used an HDMI to HDMI cable.)
- an output device (I used a projector.)
Here is a sketch of my set up:
Not shown: MiniDisplay Port to HDMI adapter
I didn’t describe or diagram my audio setup as it was a little more traditional in approach. I may or may not write about that in another article.
No Comments >
Here is how I fix this Pro Tools error.
Really? A typo in the error? Grrrrr…
Ever get this error? Can’t open your session, right? Not only is it a major workflow stopper, but the double punctuation typo at the end is annoying as well.
Luckily, the solution is quite simple.
This is the quick fix that works for me and my particular setup of hardware/software. Your mileage may vary.
- Quit Pro Tools
- Restart Pro Tools
- Open the session that wouldn’t open before
- Get back to work
The IT mantra “Have you tried turning if off and on again?” waves the problem away like a magic wand, but why is this problem happening in the first place?
The last time this error occurred for me, I noticed that it was after I had ejected my audio hard drive, removed my iLok, and left Pro Tools open, but put my machine to sleep before Pro Tools could issue the panic message: “Hey! Where’s your iLok, buddy?! That’s it! We’re shutting this whole thing down.” Then when I went to reopen the last session I was working on, boom, the error in question occured.
I’m guessing that between the time I ejected everything and the time I plugged it all back in and tried to fire it up again, Pro Tools had switched its default sample rate from whatever my Mbox 2 Pro says it was to whatever my MacBook Pro thinks it should be. Then when I try to open a session with a particular sample rate that doesn’t jive with what the current rate is, Pro Tools freaks out because it thought it knew what was right, but doesn’t even know anymore, man.
Disclaimer: I don’t actually know how or why the error is occurring. These are just my slightly educated stabs in the dark. If you know anything more about this error, why it happens, and, most importantly, why there’s a typo in it, please leave your thoughts in the comments section below.
No Comments >
Pro Tools hardware is either not installed or used by another program. If you thought that having Pro Tools 9 installed meant no more “Hey, Mr. Engineer Genius, where’s your fancy hardware?” errors, then this nagging error probably came as a surprise. It did for me. Since installing Pro Tools 9, my workflow has allowed […]
Pro Tools hardware is either not installed or used by another program.
If you thought that having Pro Tools 9 installed meant no more “Hey, Mr. Engineer Genius, where’s your fancy hardware?” errors, then this nagging error probably came as a surprise. It did for me. Since installing Pro Tools 9, my workflow has allowed me to jump around from my Mbox 2 Pro, Mbox 2 Micro, and MacBook Pro’s built-in sound card. This has been really handy while trying to finish up my album on the road. But, apparently, all that hardware hopping can cause the playback engine to get stuck in some funky states that don’t so work –if at all. See my previous post “FIX: Pro Tools could not set sample rate to specified value” for a similar issue.
Obviously, the problem has something to do with the playback engine. Since the error dialog only offers an ‘OK’ button, which closes Pro Tools, there doesn’t seem to be a way to work around the problem. There is not even a way to know what hardware Pro Tools is expecting.
I found a simple solution via this Sweetwater forum. The answer given there details how to get Pro Tools running on a PC, but I found that it worked for Macs too and without having to install any drivers. The fix is kind of like booting Pro Tools in safe mode. Simply hold the ‘N’ key while starting up Pro Tools. This will bypass the normal start up sequence and open up the Playback Engine window. Now you can select the correct playback engine and continue using Pro Tools.
In my situation, Pro Tools was looking for the last connected device (my Mbox 2 Pro), but since it wasn’t available it opted for the next available option: my MacBook Pro’s line input, which doesn’t make a very good playback engine.
Let me know if this fix worked for you.
10 Comments >
This problem may have been fixed in the Pro Tools 9.0.2 update that came out yesterday, though I’ve not been able look through the 9.0.2 Readme file in detail or to test this out on the updated software. I’ll update this page when I find out more.
After upgrading to the newly released Pro Tools 9, I couldn’t open sessions or create new ones. I got this error: “Could not complete the Open Session… command because Pro Tools could not set sample rate to specified value..” I hunted around on the web and various forums, but couldn’t find a solution that fit. […]
After upgrading to the newly released Pro Tools 9, I couldn’t open sessions or create new ones. I got this error: “Could not complete the Open Session… command because Pro Tools could not set sample rate to specified value..” I hunted around on the web and various forums, but couldn’t find a solution that fit. I found several items relating to Windows and Pro Tools 8, but nothing for a Mac running Pro Tools 9. After messing around a bit I figured out the problem was with my playback engine. Here’s how I solved it. Let me know if it works for you too.
Open the Playback Engine dialog under the Setup menu item.
From the menu bar select Setup > Playback Engine… to open the Playback Engine dialog window.
The problem is with the Pro Tools Aggregate I/O.
By default, my current engine was set to “Pro Tools Aggregate I/O.” It’s odd that this Pro Tools would leave it that way after an installation since AVID states that it is not supported in OS X.
Select your current playback engine.
The fix is easy. Simply select the right playback engine. Your options may differ based on your setup.
In my case, I usually would edit with my Mbox 2 Micro, but since Pro Tools 9 gives us so many more options for hardware compatibility, I selected Built-in Output. I was able to edit some vocal takes using my Macbook Pro’s speakers instead of pulling out my headphones. Nice!
30 Comments >
The Problem Today, I had a problem emptying the trash on my MacBook Pro. The trash would begin to empty, but would hang shortly after starting the deletion process. I made several attempts to empty the trash (all ending in a force quit of the Finder) before deciding to pull all the files out and […]
Today, I had a problem emptying the trash on my MacBook Pro. The trash would begin to empty, but would hang shortly after starting the deletion process. I made several attempts to empty the trash (all ending in a force quit of the Finder) before deciding to pull all the files out and move them back into the trash one by one to delete them. After several rounds of trashing, I was able to eliminate all but the single offending file, a partial dmg from a failed download of Adobe’s CS5 Design Premium. Holding ‘Option’ while clicking Empty Trash didn’t work. Renaming the file and then deleting didn’t work either. No matter what I did, just I couldn’t trash the file. So I began an online search.
After scouring a bunch of forums with various non-helpful solutions and scary Terminal command line code that “might ruin everything if you’re not careful,” I finally found the safe and easy solution in a free trial download of Cocktail, a shareware maintenance utility for Mac OS 10.4 and above.
Cocktail is an award winning general purpose utility for Mac OS X. It is a smooth and powerful digital toolset with a variety of practical features that simplifies the use of advanced UNIX functions and helps Mac users around the world to get the most out of their computers. Cocktail is installed at more than 200,000 computers world wide. The largest part being private individuals, but Cocktail can also be found at large international companies (Puma, Sony), educational institutions (Harvard University, University of Texas) or newspapers (The New York Times, Business Week).
Cocktail can empty the trash!
Fixing the problem was as easy as clicking the ‘Empty’ button found under the ‘Misc’ subgroup in the ‘System’ tab. Trash empty. Computer nice and tidy again.
2 Comments >