How To Make Your Own Internet TV Show – Part 3 – Adding Additional Cameras

Adding Additional Cameras
Part 3 – Installing Additional Cameras

In this video I show you how to add additional cameras to your Vidblaster setup in either Windows or Mac, and how easy it is to switch between them.

Note to Pros – These articles are aimed at beginners, who wish to spend little or no money until they have a grasp on the topic, and are hoping to learn how to get started quickly and easily, using equipment they most likely already have.

httpvh://youtu.be/VTpJ5ZkTShQ

You can also use your iPhone, Android and Nokia smart phones as cameras by using Epoccam as shown in this tutorial.

httpvh://youtu.be/Z5E-vEalubM

You can download a free unrestricted trial copy of Vidblaster from vidblaster.com

vidblasterbuynow234x60
Part 1 – Selecting Video Switcher Production Software – The Heart of Vidcasting – VIEW HERE
Part 2 – Installing Vidblaster, Connecting Your Webcam, Switching and Interface Basics – VIEW HERE Part 3 – Adding Additional Cameras – VIEW HERE
Part 4 – Mixing Audio, Mics, and Avoiding Looping in Software – VIEW HERE
Part 5 – Desktop and Browser Capture – VIEW HERE
Part 6 – Connecting Guests Via Skype – VIEW HERE
Part 7 – How To Make A Lower Third Overlay – VIEW HERE
Part 8 – Adding flair with Effects, Soundboards and Chat Streams – COMING SOON!
Part 9 – Green Screen/Chroma Keying and Virtual Sets with iClone – COMING SOON!
Part 10 – Recording and Streaming – COMING SOON!

Make a Mac OSX Lion Virtual Machine in Mac OSX Lion

A OSX Lion Virtual Machine running on OSX Lion I hear you cry? Why?

Much like Windows (but not quiet so bad) Mac OSX creates support files for most program you install. Even though a lot of programs you download seem like a self contained package, and if you don’t like it, you just trash it and its gone, that isn’t really the case. Like Windows, your mac has a large amount of hidden files, and new ones are created with most programs you run. Things like preferences files, registration data, and a swag of other stuff that hangs around after the main app file has been deleted.

(If you are interested in viewing this sort of stuff, and easy way to get started is to Download Tinker Tool, set it to “Show Hidden Files and Folders”, click “Relaunch Finder” and open up hard drive/library folder. BE WARNED! – You can do a LOT of damage in there, tinker with care!)

If you are like me, and feel uncomfortable with the possibility that clutter and orphaned files may be affecting your systems performance, a great way to test out new programs to see if you want to commit to them long term is to try them in a Mac Virtual Machine. This way, all of the files stay in the Virtual Machine, and you can roll back to a previous snapshot, or even delete it when your done, and your live system hasn’t been modified at all.

It’s pretty easy to install a Mac OSX Lion Virtual Machine in VMWare Fusion………as long as you managed to intercept/save your “Install Mac OS X Lion” Installer app from your Applications folder before you installed OSX Lion on your computer.

The problem here, is that a lot of us didn’t. I certainly didn’t. And for some reason it seems to be automatically deleted once you have installed it. I tried lots of methods that claimed to be able to reclaim the installer app, but none of them really worked. I ended up wiping my hard drive completely, re-installing Snow Leopard, then going back into the App Store and re-downloading the Lion Installer App, and saving it out before I ran it. As I had already purchased it, there was no cost, but it was still a lengthy process.

Once you have the Lion Installer app, open VMWare Fusion and click “Create New” in your virtual machine library to create your new Virtual Machine.

The next Window will ask you for your installation file. As you most likely don’t have OSX Lion on a disc, you will need to point it to your Lion Installer App. Click “Continue Without Disc”

Next, select your installer app’s location from the drop down menu and click continue.

The installer is pretty clever at picking what operating system you want to install, so in most cases you can just click “Continue” once it has correctly identified the installer.

The next window allows you to customize aspects of the new virtual machine. You can assign more memory, more hard drive space, and a lots of other variables by clicking “customize settings”. Again, VMWare is pretty clever about choosing the best settings for you, so feel free to accept them and click “Finish”. You can always change them later if you need to by right clicking your virtual machine in the virtual machine library and selecting “Settings”.

The final step is to name your virtual machine. VMWare Fusion selects a default name based on your operating system, but you will probably want to change it to something a little more meaningful. In my case, I changed it to “Lion Test Area”, as this is where I will be testing software.

And now it begins!

And before too long, your in business! You now have a sand-boxed version of OSX Lion running inside of OSX Lion!

Now, again, if your like me, your probably thinking “Can I use the same technique to run Leopard or Snow Leopard in Lion so I can use my old PPC apps?” At this stage, I am not aware of any simple easy way to make Leopard or Snow Leopard run. I am looking into it though, and if you already know, please let us know!

Enjoy!

Easily Backup and Restore VMWare Virtual Machines

Recently, a Webernets reader (Yes, there is at least one person looking at this site) crashed their XP Pro virtual machine, and it made me think about a really quick and easy way to back up and restore a VMWare Virtual Machine in the unfortunate event of a terminal failure.

As VMWare Virtual Machines can grow in size pretty quickly, especially if they are not regularly “cleaned up“, in most cases you will need to use an external hard drive or a very large USB key to store your back up. Whilst it is convenient to keep your back up on the same computer, its also no help to you at all if that computer is the one that fails, so keeping a back up some where else is a pretty good idea. I actually would recommend doing BOTH. You can never have too many back ups in multiple locations – ask any one who has ever had a catastrophic failure!

To get started, you need to locate your Virtual Machines, and this is REALLY easy! Open a finder window, click “Documents”, and you will see a folder called “Virtual Machines”

To back up your virtual machine, simply drag the virtual machine file to your back up destination. As you can see below, I have a virtual machine called “XP with Apps”, which is my main Windows computer, and I would be pretty lost if anything happened to it. I also have a FREENAS server, which is just basically a big hard drive that is attached to my home computer network, and shows up as a “Share”, so to back up my XP Machine, I just drag the virtual machine file onto the Freenas entry in the side bar menu, and let it do its work. As my Virtual Machine is quiet large, it does take some time for it to copy over.

Now that we have our Virtual Machine backed up, you are probably wondering how easy it is to restore it? Its just as easy! Check this out!

To restore a saved virtual machine, just locate it on your back up source (In my case, it is on my Freenas server), and drag it into your virtual machines folder. For this demonstration, I am going to restore my most FAVORITE Linux distro, PUPPY LINUX! I started by dragging the Puppy Linux Virtual Machine from my Freenas server to the desktop on my Mac.

Once the file had copied over, I moved it into the “Virtual Machines” folder in my “Documents” folder with my other virtual machines. Then to begin the restore, just double click the virtual machine file.

When you double click it, a window will pop up asking if you have copied or moved the virtual machine. In this case, we have performed both actions, we have moved, as well as copied the machine. Given the wording in the dialogue box, and the confusion that arises after being presented with a multiple choice question where both answers are applicable, I went with “If you don’t know, answer “I Copied It””, and I clicked “I Copied It”.

Almost instantly, my Puppy Linux virtual machine sprang into life, and before you can say “How the heck did I do that?” my Puppy Linux Virtual Machine was up and running!

Thanks to the folks at VMWare for making this so easy!

Clean Up And Shrink VMWare Fusion Virtual Machines With Ease

vmware-logoIts always bugged me how large and bloated my Virtual Machines become. I recently installed XP Pro and ran Windows Update to get it up to scratch, and the raw install Virtual Machine file was a little over 3Gb. I installed a few of my favorite video editing/converting apps (Including Premiere Pro – about 2Gb in size), converted a few files, and within days, the size was over 12Gb? It really doesn’t make sense to me why the virtual machine would blow out to that size so quickly. Its also a real annoyance when you want to backup/copy your virtual machine elsewhere for safe keeping, and your file is unmanageable.

Thankfully, the folks at VMWare have provided a solution to this bloat. Open VMWare Fusion, but don’t open any virtual machines. From the menu, select “Window” and then “Virtual Machine Library”. Right click on your obese machine and select “Get Info”.

clean-vmware-virtual-machineYou will now see a summary of your Virtual Machine.

clean-vmware-virtual-machine-2You can see from above, I can reclaim over 7Gb of size! Click the “Clean Up Virtual Machine” button.

clean-vmware-virtual-machine-3Now is one of those “Go get yourself a cup of coffee” moments. It does take a while, so be prepared for some down time.

clean-vmware-virtual-machine-4Presto! The 12Gb Virtual Machine is now a much more manageable 5.2Gb!

VMWare Fusion 4 Black Screen Workaround on OSX Lion

VMWare Fusion Black Screen in OSX LionIf your like me and run Windows on your Mac using VMWARE Fusion, you have probably been getting really frustrated lately at the blank black screen you see when you try to run your virtual machine. I haven’t found a permanent fix for this, and I hope the folks at VMWare are looking into it, but I have found a workaround, which has worked for me.

TRY THIS AT YOUR OWN RISK – I ACCEPT NO RESPONSIBILITY IF YOU BREAK SOMETHING – THIS IS MERELY A RECOUNT OF HOW I WAS ABLE TO RESOLVE THE ISSUE – YOUR RESULTS MAY BE VERY DIFFERENT!!!

I have performed this workaround not only on my Macbook Pro, but on my Mac Pro as well – it worked in both instances.

To begin, I went back to VMWare’s site HERE and re-downloaded VMWare Fusion 4 (I use the lite version without McAfee)

VMWare Download ScreenOnce the download was complete, I mounted the .dmg and tried to simply drop the app icon onto the Applications Folder……..FAIL!

VMWare Install Fail

I cant stress enough, I accept NO responsibility if you try this and it fails for you ok!

At this point I opened up my Applications folder and dragged the VMWare app to the trash – I had to type in my admin password before the system allowed this. Initially I was worried that my license would get deleted as well, but I had a hunch the license would be stored elsewhere deeper in the bowels of my Mac, so I pressed on.

Move To TrashAfter the app was successfully moved to the trash, I was able to drag the VMWare logo from the .dmg into the Applications folder. Again, I was asked to type in my Admin password.

Once it had completed copying, I unmounted the .dmg, and clicked the icon in my dock to boot my Windows XP Virtual Machine. An alert popped up telling me that VMWare had to update some resources, and again I had to type my Admin password……………..AND THEN…..

XP-Boot-Screen

LOOKIN GOOD……………….

Running AgainYES! Back in the game!

Since I discovered this workaround about 10 days ago, my Mac Pro hasn’t skipped a beat. I updated my Macbook Pro last night with new iCloud features, and my Virtual Machine Black Screened again this morning. So I re-tried the work around for the creation of this article and It worked again for the second time.

I know its a pain to perform, but it did work for me, and if I have to choose between not using my Virtual Machine at all, or spending three minutes performing the workaround to get going again, I know what I would prefer to do.

Lets hope the folks at VMWare sort this one out soon!