[John Welsh]

Well, I haven’t tried it in Vista yet… your point is well taken. But it’s really great under XP Pro x64. Cheers, and thanks again for unlocking this mystery!

[John Welsh]

Frederick – I meant to add that I do have the latest version of Audition at work (v2.0) and actually prefer Audition v1.5 because it’s powerful, clean, hiccup free, very stable and DOES work with XP Pro x64 OS so far without any weirdness. I thought PPro (which I use at work and can vouch for its significant buginess compared to Vegas Pro) was the cat’s meow when it came to round-trip editing, because it’s a real time-saver. I had assumed that Audition could not round-trip, or that Vegas would not work with Audition to do this, but thanks to you I’ve cracked that nut and am thrilled.

Sound Forge is a fine program from what I’ve heard… nevertheless, if you have reason to go back to Audition, suggest trying to find 1.5 on Craigslist or eBay. Well worth it.

Final thought: Adobe’s Soundbooth (at least vCS3) can’t hold a candle to Audition v1.5. SB is less powerful, takes longer to process waveforms, has audibly inferior noise reduction, and for guys like myself who have been doing audio for many years and understand the inner soul of compression, expansion, EQ, limiting, etc., it’s one of the most frustrating pieces of software I’ve ever used. My fear is that Adobe, who IMHO has become the Microsoft of the creative software community, will do away with Audition altogether. A sad day if/when they do.

[John Welsh]

BINGO!

Thanks so much. I used the Edit / Adjust Sample Rate… command instead… and it worked like a charm. After saving in Audition, it round-tripped seamlessly and successfully back into Vegas, I played it therein, and it’s flawless. Having been in the Audition realm for so many years, and being able to do just about anything audio-wise in it, this is a HUGE big deal for me. Thanks again for your willingness to help. It’s what makes The Cow such a great resource!

[John Welsh]

Hey Peter, I have an HDR-SR12 and love it. While I haven’t worked with Blu-ray output, I can till you this: I’ve ingested my cam’s .m2ts files into Vegas without a hitch (all shot at the highest quality setting the cam is capable of), edited them (yes, they play back a bit jerkily, even on a quad processor system!), and encoded/rendered to .avi files at the highest quality settings to NTSC DV widescreen. The quality was very good indeed.

When I encoded to 1920x1080i in .avi format and played them back on my puter, they were very good as well.

[John Welsh]

Thanks, Frederick.

In Vegas, I right-clicked on the audio file, selected “Open copy in Audio Editor” (which is Audition 1.5) and the file is indeed 44.1K. Then, in Audition, I selected Edit / Convert sample type… and did just that, to 48K (and confirmed same in View / Wave Properties…).

When played back, the audio file still has the lower pitch, and when saved and round-tripped back into Vegas as a “take”, and then playing the video/audio clip, the audio is still the lower pitch and out of sync because of the pitch change (as before).

Did I miss your meaning as to how or in which application to change the sample rate of the waveform?

[John Welsh]

Thanks, Steve. The inside of the case is well-cooled, but the memory sticks are fairly close to each other, because they have integral heat sinks. I’ll put a fan on them and see what happens…

[John Welsh]

Appreciate your response!

Timing – RAM timing is these Patriot chips (PC2-6400 / 800mhz), is 5-5-5-12 but on my particular mobo (the S985Xbx2, which is the server version of the more-common Intel D985Sbx2), there is limited BIOS accesss to changing settings; you can’t overclock, and on the memory, you can only change the “-12” parameter, as I recall. However, the BIOS did read the timing correctly.

Memory voltage – Memory voltage is not adjustable in BIOS in the “S-” version of this mobo that I have. However, even though the four Patriot memory sticks bear the same model #, some time separates the two in manufacture (approx a year). Interestingly, all four are marked identically EXCEPT that one pair says “1.8-2.0V” and the other pair says simply, “2.0v”. According to the Patriot tech support guy, this makes no difference (I have no way to know if this is the case).

Possible defective memory sockets – There are two sets of sockets you can use for the RAM (blue set, black set). With a 4GB configuration (using 2GB sticks, which is all I’ve ever run in this machine), it doesn’t matter which sockets I put the two sticks in, they work fine, even when intentionally “mis-pair” the “1.8-2.0V” and “2.0V” sticks in the same color socket. (i.e. computer operation is solid as the Rock of Gilbralter).

You can see why this is such a pain in the donkey!

–John

[John Welsh]

Thanks John for taking the time to respond so quickly! I’ll check out BR and your website, assuming much of the excellence I’ll see was done with that. If you have any examples you show on your site where BR played a significant role, plz let me know…

–John

[John Welsh]

Gotta weigh in here due to some similarities… and differences that may help us solve this. I suspect the problem has to do with how Vegas handles AVCHD from non-Sony cams (though I couldn’t give you a technical explanation as to why).

Here’s my story: I have a Sony HDR-SR12 AVCHD cam that I got for a trip to Kenya last August (FANTASTIC piece of equipment, small and unobtrusive, dependable, stable, performed flawlessly in the Kenyan outback despite lots of rough-and-tumble). Came back and edited 1,000+ files on an Intel high-end mobo (S975Xbx2), Q6600 Quad core (not overclocked), 4GB RAM, ATI Radeon dual-DVI-I board, running XP Pro x64 (the 64-bit version of XP). All current drivers.

Ingested footage, no problem. Sony’s Picture Motion Browser has been egged by some, but it was flawless. Edited all this mostly on Vegas Pro 8.1 (their 64-bit version) but also on 8c. No probs with crashing to speak of UNTIL I tried to add 4 additional gigs of memory (to total 8GB), so I could take full advantage of XP Pro x64’s ability to actually use 8GB, which also gives me more RAM for the “dynamic RAM preview” feature, etc. Then the problems started!

My system would crash anywhere from just after I logged in, to several minutes after logging in. The crashes didn’t coincide consistently with any action, mouse movement,keyboard stroke, or which version of VPro I was using. Every crash was the same: Both screens go black (never a BSOD), can only full reboot (CNTL-ALT-DEL does nothing). The memory added is the same part # as the original 4GB of Patriot memory. I even tried 8GB of Kingston RAM, same problem. And I never even got around to increasing the dynamic preview RAM setting, either. Go back to 4GB RAM, everything’s stable as a rock.

Perhaps this clouds the issue, but I’m hoping there are some clues here that someone smarter and more experienced than myself may be able to discern. Short of that, apologies for the long post.

–John

[John Welsh]

Dom, I’m hearing you on the slow loading issue.

The “bloating” of Adobe software is something I’ve noticed too. NO, I don’t expect powerful software to load instantly, but this is ridiculous.

On my Quad (Q6600 Pentium) system, which has 4GB, and is optimized for PP CS3 (i.e., a purpose-built machine with a lean installation that has no non-production crap software on it), the load is exactly as you’ve described–I sometimes wonder if I’ve clicked the icon correctly. In fact, there have been a handful of times when I’ve double-clicked the icon at the right speed (click-click not too slow or fast, just as with any other double-click action for other software), and it doesn’t respond at all, ever, even if I leave the machine and come back. So I finally double-click it again, and it responds.

Perhaps Adobe and Microsoft should merge. Or not.