Gearslutz.com - View Single Post - Source connect in post production context
View Single Post
Old 24th April 2011   #23
toddschick
Gear interested
 
toddschick's Avatar
 
Joined: Apr 2011
Location: Toronto, Ontario, Canada
Posts: 1

Hi Guys,

Great thread! I consider myself lucky to have come across it. Hat's off to soundguydave who nailed it on the head about all the crappy audio out there from wannabe VO talent; I can happily say I'm not one of them.

I'm looking for some advice, guys. I've been mandated to research a Source Connect solution for my client and myself. There's been a few comments here about the (VO-to-picture) method working well if both users have their *stuff* together, which is the case here. Big pipe on the client side, I've got a meg up and 10 down from my ISP which I can upgrade if need be. Both sides would work together to make the solution work.

I'm all in as this will negate a daily 30 minute commute +parking fees....you name it. The costs to facilitate the contract are outta sight. Client is skeptical (as most corporations are) but have the gear and the right people in place to test it and roll it out.

I don't run PT - use AA3. All I've ever done is cold VO editing and the odd basic mix, so PT was overkill for my work flow. No worries, I will upgrade if need be and have a great resource client side to walk me through the basics. What I need to know is:

1) Can this be done using AA3? (No harm in asking...)
2) Thoughts on minimum bandwidth?
3) Common pitfalls during setup?
4) Has anyone tried the latency tweaking mentioned here?
5) Do I have to upgrade to SC Pro, or can I get away with the Standard version I have now?

My thinking is, the smoother I can make the testing go, the more likely the client will bite. This is why I'm doing my homework first.

Any help would be greatly appreciated.

Regards,

TS

Last edited by toddschick; 24th April 2011 at 04:58 PM.. Reason: Had to finish post
toddschick is offline   Reply With Quote