Wayne Waag
2
COW Coins
Forum Replies Created
-
My approach is probably the same as yours in terms of having a single folder (usually with a number of sub-folders) that encompass all of the projects assets. To avoid the problems you describe, here’s what I do. Rather than simply copying the original folder to my “Archive” drive, I create a new folder in the archive drive, open my finished project in Vegas and then do a “save as” to the new folder, making sure the “copy media with project” box is ticked. In this way, all of the assets are copied into that folder. Another advantage is that sometimes I will use assets on another drive, e.g. music, and forget to first copy them into the original project folder. Using this approach guarantees that all of your project’s assets are in the same folder and thus you avoid the problems you describe.
One thing to be aware of. If you copy multiple projects into the same “archive” folder which use the same assets, Vegas will make make a copy of those assets, in essence duplicating those media files. To avoid this, I first copy the additional projects into a new “temp” folder. Then using a file utility program that searches for duplicates, I simply copy the “different” files into my “archive” folder.
And finally, just to make sure everything is working correctly, I will rename the original project folder and then open each project in the archive folder. It’s a bit tedious, but it insures that each project will open without having to search or locate missing media files.
wwaag
-
Dave,
Once again, you need to be a lot more specific. You have provided very little usable information except that it did render, but it took a long time. The basics–detailed media information (4K, 1080 60P ??), project settings, and render settings. Again, the easiest and most comprehensive is a screen shot. Since it takes a long time to render, also system information. If you’re using an old Core 2 duo, that render time might be reasonable. If you have a fairly new I7, your render time shouldn’t be more than double your project length, unless you have lots of effects. Again, without such specifics, no one can provide any definitive help unless their crystal ball is working especially well.
wwaag
-
It sounds like you’ve selected “Ignore Event Grouping” on the bottom taskbar (assuming V13). You can enter “Ctrl-Shift-U” to toggle that switch. If you want the audio to always move with the video, then make sure it is disabled.
wwaag
-
Sounds like it’s locked. Right-click on the event, select Switches and see whether “Lock” is checked. If so, un-check and delete.
wwaag
-
Dave,
You need to be a lot more specific. Exactly, when you do you get this message? When you drag the files onto the timeline or when you attempt to render? Sounds like when you attempt to render. Screen shots of your raw Panasonic file info from MediaInfo, your project settings, and render settings would be most helpful. I’ve gotten similar errors when attempting certain renders–e.g. when trying to render MPEG-2 at 1080 60P or attempting to render Sony AVC 1080 60P using Quick sync. Again, you need to provide more detailed information.
wwaag
-
Most likely, your problem is that Action is using variable frame rate recording, rather than constant frame rate which is necessary for Vegas and other editors to work properly. I did a couple of Action recordings on my system using Intel Quick Sync at 60 fps. Both files imported OK onto the timeline. However, the frame rate for one file was 60.022 fps and the other was 59.631 fps. Even though MediaInfo reported the frame rate to be constant, it seems most likely that the frame rate is indeed variable. To “fix” the problem, you will probably need to transcode to ensure that the frame rate is truly constant. In a quick search, I’ve seen that some recommend using Handbrake. I did a quick re-render of one of the test files making sure the encoding was set to a constant frame rate. That file imported OK into Vegas indicating that it was a true 60 fps. It would be a shame to have to re-render all of your files and lose some quality. However, that may be the only solution, unless you try other editors. In any case, good luck.
wwaag
-
You’re correct. I was looking at the thread view, although the edit button used to be there in the past. The suggestion of using the Reply button works. Of interest, it permits me to edit previous posts of mine, even if they have already been replied to. In any case, thanks for the reply.
wwaag
-
How can I fix this issue?
Upgrade to Vegas V13. Unless I’m mistaken, you’re using a fairly recent high-end camera that shoots UHD at 60P and then attempting to use a Vegas Pro edition that was released almost 9 years ago. Uploading files to YouTube and then downloading them to use in Vegas 8 seems an almost unforgivable waste of your camera’s capability. Download a trial of V13 and see if it works on your system. If not, you may also need some computer upgrades. Regardless, you will need to provide more info on your current system and the types of footage you are capturing.
wwaag
-
Can you upload a short clip to something like Dropbox? I’d be happy to try it on my system.
wwaag
-
[Tim Wilson]
we’ve gone back to our first implementation, that a post is editable until it has been replied to.
No. That’s not correct. Just tried it on another thread. I posted and immediately tried to edit before a reply. I still cannot edit that post.
wwaag