Hi Marty,

Happy holidays.

I'm using a 120 gig drive with 512K memory, and granted, it is the system drive, however, everything else worked during the prerender before PTT. When I went back and looked at the timeline, the audio portion of the clip was hardly noticable. Do you think that may have something to do with it? I'm at a loss. I was thinking of capturing that part of the tape again.

BTW, I am capturing from svhs via canopus advc-100 if this helps.

Thanks,

Jim

Marty,

Another bit of info, I can see that that portion of the file prerenders at the point of the crossfade on both ends of the clip. But I do hear the audio when I play file from the timeline. I've tried normalizing the audio but that didn't help either in terms of the prerender.

Where would I find the settings to save the temporary files.

Thanks

Hi Jim,

You might set the folders for media files in Options>Preferences>General>Temporary files folder, and in you project properties panel: File>Properties>Video>Prerender files...File>Properties>Audio>Recordings.

When you see PTT skip a portion of the rendering, it is usually a "native" segment of tape, that will copy bit-for-bit from the original file. This is normal.

If the audio event plays back properly from the timeline, it should PTT similarly. If the audio event plays poorly from the timeline, you can check it in the trimmer and see if the clip captured poorly. If it's OK in the trimmer, you might right-click on the event to check if any switches were inadvertantly mis-set, or the event level-control could be dragged down.


HTH, MPH

I think we had this sometime ago and then VV3 was upgraded somethins to do with the markers /regions.

Here is a saved error report :
I tried to "print video to DV tape" from timeline after installing build 128 and hit a killer snag. After rendering the .w64 audio file, it popped up an error screen saying Vegas couldn't access that prerendered file, and to make sure I have proper access to read and write from the drive.

Sure enough, the file existed, and all the permissions were properly set for the drive and the file itself. I can access the file perfectly from Windows Explorer.

Uninstalling Vegas and Re-installing build 107 fixes the problem, and I was able to print to tape from timeline.

The video in question is 1 hour and 4 minutes long.

SF, please let me know whether you can repro this, and how I can help. Look forward to seeing it fixed.
Thanks--
Luxo

We have reproduced this error and will have a fix posted soon.

Short term workaround:

1) save your project to a new file name (EX: "myproject_FIX.veg") or name the markers

2) Right-click next to any timeline marker, choose "Markers/Regions"> delete all.

3) You should now be able to render to wave64 (.w64), and you will also be able to print to tape.

If anybody still has problems after following the steps above, please post here- we are watching this thread closely. We regret the error and will post a fix as soon as possible.

That bug was resolved in the release of 3.0c:
(From the 3.0c readme)

" Notable changes/fixes in 3.0c
• An a/v sychronization bug in MPEG encodes has been fixed.
• A bug has been fixed that caused print-to-tape operations to fail when markers with no text were present.
• In Vegas 3.0a and 3.0b, choosing None from the Time stretch / pitch shift Method drop-down list in the Audio Event Properties dialog had no effect on time-stretched audio events. This bug has been resolved.

Notable changes/fixes from 3.0b
• A Vegas project saved in version 3.0b will not open in any previous version of Vegas. Project structure had to be changed to address bugs and there was no way to avoid this project versioning incompatibility.
• Text command markers now embed captions in QuickTime streaming files for viewing in the QuickTime player.
• RealMedia 9 video codecs are now available on the Advanced Video tab in the Custom Settings dialog. Standard templates continue to use RealMedia version 8 video codecs.
• A bug that caused some color curves settings to display inaccurrate color values has been corrected.
• Autonamed CD extraction now correctly saves files to the Recorded Files folder.
• Regions and markers and regions created in .w64 files using Sound Forge 6 now correctly display in the Vegas trimmer window.
• PAL Widescreen DV renders now use correctly auto-switching format flag.
• A bug that prevented some resampled events from resampling when using the best render quality has been fixed.
• A bug that caused play/pause in the Trimmer to revert to timeline focus has been corrected.
• A bug that caused Vegas to crash during project loading when transitions were missing has been corrected.
• A bug that caused disk-at-once CDs to cause problems with some third-party verification software has been corrected.
• The Main Concept MPEG-2 DVD templates now have an average bitrate of 6,000,000.
• Numerous Video Capture changes have also been implemented. Please see your Video Capture readme.
• A bug that caused normalize to fail on looped clips has been corrected.
• Vegas will use SoundForge 6.0 as its default audio editor if SoundForge 6.0 is installed on the system.
• A bug that caused the Main Concept plug-in to crash when using K6 processors has been corrected."



HTH, MPH

Tips:
http://www.martyhedler.com/homepage/Vegas_Tutorials.html

Here is what I've been doing today:

I rerendered the file. The message I got is as follows. "An error occured while creating the media file Vegas Video Prerendered File 0000.w64. The reason for the error could not be determined." I clicked OK and received the Print dialog box. I thought I'd proceed and clicked OK. I received this message. "An error occured while creating the media file. A stream could not be opened because it was unrecognized or corrupt."

I tried to isolate the problem by rendering several different loops to .avi files and then to PTT. The files rendered perfectly to .avi and I can view them in Windows Media Player. I got the above error messages when I rendered then via PTT. I think I can rule out that a captured clip is bad.

I did set a separate directory and I can see all of the files that were rendered during the PTT. Is there a .w64 file that should have been generated. Is there another file I should look for to get this to tape some other way?

I am at a complete loss now, but at least I can see some of the files that were rendered. That is progress, I think.

Jim

I tried the instructions at the bottom of your message. I still got the same error message. I can see the files that were rendered but I do a search and can't find any .w64 file. Is there some setting that I have to change somewhere?

Thanks.

Hi Jim,

Could you post your project properties, including audio specs, and the properties of the template you are trying to PTT?

If you use the default NTSC or PAL DV template for PTT you *should* be fine:

Audio: 48 KHz, 16-bit, Stereo. PCM (uncompressed).
Video: 29.97 fps, 720x480, Lower field first.
Pixel Aspect Ratio: .909. OpenDML compatible.
NTSC DV video files compatible with Sonic Foundry Video Capture.

Audio: 48 KHz, 16-bit, Stereo. PCM (uncompressed).
Video: 25 fps, 720x576, Lower field first.
Pixel Aspect Ratio: 1.093. OpenDML compatible.
PAL DV video files compatible with Sonic Foundry Video Capture.


HTH, MPH

Marty,

Here are the properties from the template:

NTSC DV Template
Audio: 48 Khz, 16 bit stero, PCM uncompressed
Video: 29.97 fps, 720x480 lower field first
Pixel Aspect Ratio: .909 OpenDML compatible
NTSC DV Video files compatible with Sonic Foundry Video Capture

Here are the project properties:
Audio
Number of Stereo buses: 1
Sample Rate (Hz) 44,100
Bit Depth 16
Resample Oval: Good

Video
NTSC DV (720x480) 29.970 fps

I think I covered everything. Let me know if I left anything out.

Thanks

Hi Jim,

You might try changing the audio sample rate to 48k. It might help.

Everything else look straighforward.

HTH, MPH

What version of Vegas are you running?

Marty,

Changed the sample rate in the project properties. Same thing. I can see the files rendered but I still get the .w64 error message.

I did notice something though. Once I select the template and get thorough the leader/trailer dialog box, the device setup device comes up. Of course it has two choices.

Manual (device control) - Device must be manually cued and set to record. (This is the one I select because I am going through the Canopus ADVC-100 and dumping the tape to an svhs recorder.

The second choice is Use device control (device must support OHCI 1394 DV (device control). Start recording to the device at the specified device timecode location. I don't think it matters in my situation because I'm using the first choice, but the timecode is filled in and says 00:54:03;19. My project is just over an hour. That's why I'm including this.

Is there anything else that you think I could check for?

Thanks

Version 3.0c

Ok, well it seems the "common" hangups are sorta covered... let's look for the wierd stuff.

I might try PTT with the audio track muted. That might show if there is something in the audio track, or the render process itself is goofy.

Addendum: with the current audio muted, add another audio track with one event and try PTT.

Next thing to try is rendering one half of the project, then the other; to also see if it might be a bad file or event.

Another thing to try is to create another audio track and copy the audio events to the new track and render ; to see if the track might be corrupt.

This one's unusual...


MPH

Hi Marty,

I think it may have been a corrupt install. I uninstalled the software. Since I'm using XP home, it left some remnants. I reinstalled and wrote over those remnants and guess what, I printed directly to tape. No Problem.

Thanks so much to you and the others for pitching in to solve my problem. I learned a lot from this process but I guess that's what its all about.

Thanks,

Jim

We are ALL lucky to have this wonderful forum. It has been and continued to be one of the best I have ever seen.