failure to save with trimmed clips

Serena wrote on 10/30/2010, 10:28 PM
At present not having a lot of fun. Experiencing blackouts (video, not mine!) during rendering, sometimes nicely done with fast fade-out/fade-in. This is probably related to the issue of NeoHD encoded clips randomly turning black on the time line (see my thread on muting of video), but that's just me guessing. I've been getting good interactions with the Sony support interface people, but actually getting the problem presented to the software guys seems to be more difficult. Anyway, the problem now is maybe different: can't save a project with trimmed media. Get a message "an error occurred while creating the media file. The reason for the error could not be determined". Not with all clips in my tests (same for Vegas9e and 10a), but no pattern emerges when adding and subtracting clips. Sometimes an older clip causes the error, but so far all recent clips (of those tested) do. But saving a project with all media works in both 9e and 10a.
Any ideas? I've fed this into the support system.

Comments

xberk wrote on 10/31/2010, 12:28 PM
By this do you mean you have a crash in Vegas when ""create trimmed copies of source media" is used in a save -- both in 9.0e and 10.0a --- with some particular projects but not with others?

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

Serena wrote on 10/31/2010, 6:05 PM
The problem came to notice in a current project. To investigate I generated a project with just 3 or 4 clips and played around with those. Can't determine any systematic behaviour (e.g. clips older than....); have put that aside for the moment. Giving most attention to the problem of clips going black during render (likely related to similar problem during editing). There might be progress on the latter.
Serena wrote on 11/2/2010, 4:04 PM
Just in case others find a similar difficulty, Support have replied: "I have obtained confirmation from our Development team that saving a Vegas Project file with Cineform clips present and using the Trimmed Copies option error is a known issue. They anticipate a fix for this problem in a future version of the software."
Serena wrote on 11/2/2010, 10:59 PM
Another problem I'm suffering is Vegas crashing when I trim a clip. I can split and delete, but not adjust with the cursor. Presently Vegas 10a and Cineform appear to be largely incompatible. But I transcoded all the clips with NeoHD and going back and recutting the project isn't possible within time (or desirable!).
SuperG wrote on 11/3/2010, 12:41 PM
I seem to be experiencing a problem saving with trimmed copies also. In my case, I'm simply using HDV (m2t) files.
rs170a wrote on 11/3/2010, 1:24 PM
In the Pro 8, 9 and 10 manuals, it says that you can trim DV-AVI, uncompressed AVI, Sony YUV AVI and CineForm AVI files.
Any other format will not be trimmed but simply copied as is.

Mike
Guy S. wrote on 11/9/2010, 11:49 AM
Vegas 10 crashes every time I Save As and select the option to COPY all media. The first crash came after Vegas had copied over all 167 media files. The only file missing from the folder was the Veg file. So close...

All other times Vegas crashed after copying 164 or 165 of the files.

The original project was shot on HDV and V9.0c had no trouble copying all the media files.

The updated project has the original HDV clips plus several new AVCHD clips. Also, I used the Stabilize function on perhaps three of the clips.

Any ideas?
Opampman wrote on 11/9/2010, 7:35 PM
Guy - This is the Sony response to my bug report when using trimmed media and the 10a stabilizer:

Our Development team has informed me that this issue has been logged as a bug with the current build of the Vegas Pro 10 application. They anticipate a fix for this functionality in a future version of the software. I do not have access to future product release details,
Guy S. wrote on 11/10/2010, 3:33 PM
<This is the Sony response to my bug report >

Thanks!