[Mordy Gilden]

“I’m gonna guess that your on-camera mic would probably not make a good boom mic. What make and model is it?”

Most mics, sure. I’m using the Rode Video Mic Pro (original model, it’s been updated since). It’s an adorable mini shotgun that does a pretty incredible job at isolating who I’m point it to, even at a bit of distance. Aimed at the subject’s mouth just out of frame, it seems pretty on par with my Rode NTG2 and Azden shotgun setups, and avoids background noise admirably. I saw it used on a short film shot upstate from where I live once and remember thinking, gosh that’s a weird use for an on-camera mic. But then I tried it once and was blown away. It’s pretty versatile. I used it with other wireless setups before to make it work, and it had no business working as well as it did. 🙂

It appears to have a TRS plug (hardwired) which gives dual mono. I don’t think it is balanced. The cord is too short and designed for DSLRs. I’d think it is unbalanced + unbalanced, but clearly something isn’t what I expect here. Maybe I should just make myself a mono adapter for this.

[Mordy Gilden]

Thank you for making me feel like I’m not the only one! LOL

So bottom line, what should I do? Fork over more money for the XLR “butt plug” adapter? That still won’t allow me to use mics like my Rode VMP. I don’t use it wirelessly often as its really an on-camera mic, but I like knowing that I CAN, since it always worked on my old G2 setup when I tried it. Should I get a TRS to TS cable? Or does that defeat the purpose of balancing audio? Or does the ew-100 not even support balanced audio anyway?

Not really sure how to proceed here.

[Mordy Gilden]

Thanks Ty! Yeah, I was thinking something along those lines. I did have the issue once with an adapter that I *thought* was recording in dual mono, but turned out it was recording inverse channel on the other side (results of a balanced connection). After editing together and putting up on google drive for the client to review, we found that anyone watching on a phone found the audio muted in those scenes. I blamed their phones because it CLEARLY worked fine on my computer, until I tried it on my phone and noticed in low bitrates it did the same thing. Apparently, Google was combining everything into one mono channel in the low bitrate preview compression, and the inverse audio channels were cancelling each other out!
That was a real head scratcher, took me a while to figure that one out!

So I was thinking this might be something similar, however why does the dynamic mic on the same adapter not have the hissing issue? And as far as I know, the Rode VMP with it’s DSLR-friendly 3.5mm jack isn’t a balanced connection either, so why does that not work yet mono connection lavs do? I’d say maybe the G3 doesn’t like TRS plugs, but again… it worked with the dynamic mic. Does that make sense? Do some mics balance and others not? I thought it was a cable thing?

[Mordy Gilden]

But what if I have different amounts of pictures vs what they have place holders for? And if pictures are different sizes/orientations?

[Mordy Gilden]

Douglas Spotted Eagle, I know this is a very old thread, but I love mentioning this story when people bad mouth Vegas as being “too consumery”.

Can I get more details on this? I’ve been trying to read between the lines and search for more references to it, but I can’t find anything. Thanks!

[Mordy Gilden]

Actually, I just found out the last two versions of Premiere starting supporting background capture due to popular demand… however, this is only true when ACTUALLY RECORDING- rewinding and ff stop as soon as the focus changes. I didn’t realize because when I’m actually recording, I’m usually watching as well, however when rewinding to tape to put away, or ff to a certain time location, I click away for a moment very often because it takes a couple of minutes, and I noticed that it would always stop when I did that (so I assumed the same would happen when capturing as well). So, thankfully they’ve “fixed” that part for people who capture a whole tape at a time. But for me, the biggest greif comes from rewinding. Why does it stop rewinding when the focus is moved?
This completely goes against the theory posted above, as rew and ff are completely camera-hardware based and take miminal amounts of RAM and CPU power from the workstation, if any at all, whereas capturing works just fine in the background!!

Anyway, it still doesn’t address the phenomenon when actually editing the timeline and the focus is changed… Sometimes I’m listening to a recorded interview play, while flipping through my clips of B-roll. But as soon as I click anywhere else, even if I switch to my email for a moment, it stops playing! This doesn’t make any sense. I also don’t believe that Sony’s Vegas is so “revolutionary” in being the only one that supports this… it seems like common sense to be able to edit like that, and I’d think a program with as much prestige as Premiere would allow such behavior. I was sorta hoping there was an option somewhere like “continue in background” or something.

[Mordy Gilden]

Oh. I see. Well, maybe they’re an idiot AND incapable of using message boards? 🙂

[Mordy Gilden]

If you don’t know what a crossfade is, you really shouldn’t be doing anything until you learn more about video editing. The folks here are nice and helpful, but you can’t expect them to spend their time walking you through the basics.
This stuff is Editing 101, buddy.

[Mordy Gilden]

Ok, I installed Vegas 6 and it did perform much better (roughly twice the speed, which would make sense to those who speculated Vegas 5 only used one of the dual cores).

These are my findings:
Vegas 5 on Athlon XP 3200+
11m 40s

Vegas 5 on Core 2 Duo E6400
12m 15s

-> VEGAS 6 ON CORE 2 DUO E6400
6m 4s

Much better!

Conclusion:
I’m impressed with the speed using Vegas 6, however a little bit appalled that Vegas 5 is so poor at CPU utilization. This seems more like a bug that was fixed in Vegas 6.
I say this because I run plenty of software that predated the dual core chips and they still perform well. For example, Caligari Truespace 5 (released back in 2001) does not have any “dual core optimized code”, however the resource manager reports 100% CPU usage when rendering. Vegas 5 reportedly only used 50% during rendering on a Dual Core. This should not be so.

[Mordy Gilden]

Honestly… I’m sure 7 is great, but it costs too much for me right now if I don’t need it. You have to keep in mind that it wasn’t so long ago that I bought 5, not to mention I just bought a new computer, and additionally just bought the Adobe Production Studio because certain projects I’m working on require it.
I wasn’t planning on buying a new version of Vegas as well, but if 5 is “incompatible” with my new hardware, I may have to purchase at least 6 (which I can get for substantially less than 7). So basically, if 6 works that much better than 5, I might have to purchase it. But 7 is out of the question for me right now, so why try it?

As far as HD goes… the stuff I use vegas for generally stays standard Def. Anything HD I’d probably end up doing in Premiere Pro.