Aaron Star
Forum Replies Created
-
So the intern has Vegas Pro 13 build 453, and you have tried FILE > Export > Final Cut Pro X (.fcpxml) and found it does not work for you?
When I tested a simple 2 track timeline just now and Exported and Re-Imported to a new project. I got some odd sound sync placement of the audio files on track 3. The final cut format seems to break out the audio channels. But the edits and track 2 audio was correct.
EDL Export worked well exporting and re-importing. I think EDL has limited tracks.
-
These are cool if your DSLR will provide a clean HDMI feed that is pre-encoder, and 10-bit 422 color.
They could also help your workflow also by being able to record directly to ProRes or DNxHD. No conversions or intermediate formats, you are basically starting at the intermediate stage.
There is the new BM Video Assist that looks like a good deal as well.
https://www.blackmagicdesign.com/products/blackmagicvideoassist
However, whenever I see these things, I always think the person should have bought a better camera that operates at a higher level. Like a C300, Blackmagic, Arri, or Sony F-5 series. The higher level cameras will have better electronics, image sensors, and in some cases higher end codecs than some low cost DSLR body.
-
That ACES RRT SRGB is only available in 32-bit Full Level mode. Unless you are editing RED, ARRI, Blackmagic Cinema, Sony F-series, you would need to apply the 2.22 gamma as well to your setting. Otherwise shift to 8-bit mode or 32-bit video levels will keep you from screwing up your source levels. 32-bit video levels stays inside the rec709 color space, but processes with 32-bit FP accuracy.
Pretty much the only reason to edit in 32-bit mode is if your source footage was shot in a 10-bit or better codec. If you are shooting with a standard AVCHD camera or DSLR then stay in 8-bit mode. AVCHD is pretty basic 8-bit video and processing in 32-bit mode is pretty much adding extra math for very minor returns. Even the newer low cost 4K camcorders and DSLRs are shooting 8-bit 4K.
You only really need to work in 32-bit Full levels when you are working with footage that has been encoded with a linear gamma, or you are attempting to Color correct in the ACES color space. Hence the ACES RTT sRGB transform setting.
-
I would get an H1 or H4, the H4 gives more options down the road for corded mics or mixer input.
Also get the troll hair wind screen in a neutral color, black preferably.
Then get a shock mount adapter that will allow for connecting to a Boom Pole. Have someone Boom your shots or interview just out of frame with the H1 mounted as the boom mic. Put a safety strap on your H1 or H4 in this mode, to keep your Boom Op from dropping your recorder out of the shock mount. You also will not have LAV mics in your frame. With the H1 or H4 mics in 90 degree mode, your sound will be rich and in stereo. If you really need a Lav for noise issues, the H4N will allow XLR grounded cabling, and connection to an Sony ECM-44B Lav. ECM-44B has great sound and much less than wireless lavs.
-
You could determine what the hold up is when deleting clips with Promon, but this might be to in depth for average user.
There is another post on SV forum on a process to allows Vegas to edit the HEVC files directly in the Vegas timeline. I thought this is what you were doing when I first read this. If you are converting your HEVC files with some camera sidekick app, I would try the solution below. Then when Vegas can read the HEVC files, convert them to XAVC-i.MXF. It could be that your camera app is not creating compliant MP4 renders.
https://www.sonycreativesoftware.com/forums/showmessage.asp?messageid=931639
.MTS HD is not a good edit format, converting to HDCAM-SR-lite.mfx, or XDCAM-ex/422.mxf, would edit smoother and take better advantage of system hardware.
HEVC ironically needs to be converted to XAVC, even though HDCAM SStP is 4K capable just not included in Vegas. I say convert the HEVC to XAVC because even though Vegas will read the HEVC format, editing with it slow and chunky.
Word to the wise. Steer clear of Lacie drives. Lacie has attractive designs with crap hardware interface chips, and their designs do not deal with heat well. The heat kills the drives prematurely, or the chips fry from the HDD heat build up. After loosing 2 LaCie external drives, and one during a production, they made the S-List. Luckily the drive that failed during production was the adapter chip that blew, and HHD internal was ok when connected directly as an internal PC drive.
-
The Media info you posted says your source file is 1920×1080 @47.9 FPS. This is not a standard video format. Then you are trying to render to 60i profile. Please verify that the media info posted is the rendered file or source file.
Who created the 47FPS file? I would get a new file of the source in 1920×1080-30p or 60p if the source was shot that way. Vegas maybe having a hard time with MP4 in AVI, but my guess the conversion from 47FPS to 60i at such a low bitrate (1.9Mbs) is creating the picture issues you see.
One thing I would try is using the match media button in the upper right corner of the prject settings. Then choose one of your source files. Then when in Render As, choose a profile under Sony AVC that has an = sign next to it. If an = does not exist, choose an Internet profile of 1920×1080-30p.
2Mbs for 1080p is really low for posting to YouTube. I would see if you can get the source material above 12Mbs, and render to at least the same bitrate.
If your source material is coming from some other NLE, like final cut, get an export to ProRes, DNxHD.mov, or XDCAM-EX.mxf, and not .AVI. If it is something like Resolve, export to MXF OP1A, Sony MPEG4 422(225Mbs) profile, or the XDCAM MPEG2 profile. Then bring that file into Vegas for editing.
-
I personally happen to like abstracted backgrounds for talking head shots. Let the b-roll show more details and camera movement. Three camera with varied angles. Wide or MS, CU and one long lens for ECU if your material needs. If I had to do another doc, I would do more Steadicam and walk more with people. Driving and Bus tour shots are is nice too for those traveling though life sort of vibe.
For a blind musician, I would think sound would play greatly into an opening or some aspect of the story. Some attempt of what it must be like to play in front of people and see only blurry images, or nothing, and only hear sounds of the location and hearing peoples reactions.
Fog of War is a good example, with the way the DP varied camera shots with framing and tilt in a very nice way. I think they shot that 4K or 35mm and cropped to HD allowing reframing and more shot choices. If not, the editing and interviewing was amazing for single subject.
All this really depends on your story teller position.
-
Those kind of issues are hard to trouble shoot and could be due to a number of things.
You seem to be using some free video converter. Why when you have access to Vegas Pro?
You were saying your system has 1280MB of RAM? Does this refer to the RAM preview setting or amount of system RAM? If this is Preview Ram, set it to the default 200MB.
You need to give us an idea of what camera source media is from, or media types on the timeline.
I would try the following to attempt to clean up your system:
Uninstall any and all freeware image editing applications, codec packs, or video converters.
Uninstall all old software or trails you are not using.
Uninstall AV software that is different from MS essentials or the integrated Win8-Win10 AV software.
Apply all windows updates. reboot
Download an ISO of MEMTEST86+ from https://www.memtest.org/ and create a CD/DVD or USB drive, boot to it and verify your memory.
Check your windows system event logs for physical Disk Errors and resolve if any are found. Run windows check disk on boot and media drives and look for errors. Also check for “Found000” type of folders on your Boot and media drives. Disk errors and Found000 folders indicate failing controllers or media.
Run Malwarebytes, Scan and cleanup. Reboot and rescan if anything is found and cleaned.
CCleaner – run the core cleaner, then reg clean, disable any startup processes you do not need or were not uninstalled from other apps. Reboot.
Right click on your windows boot drive > Properties > Windows Disk Sweeper – enable the “clean Windows System Files” clear all the windows update restore files. Reboot and check for Windows Updates, reboot after any updates.
If after all that disk, memory verification and cleanup, Vegas still fails at the same place, you need to start removing media from the timeline until you can find the offending corruption.
-
I am not sure anyone understands what you mean by “Fix.” Hitting F1 can solve several issues, and offer guidance on the use of View > Windows Layouts usage. If that is what you mean.
-
SSD and external media are all good ideas for different reasons. The lagging of the system sounds more software related than disk hardware related.
I would try encoding a couple clips from the camera master mp4/H265 format to Sony XAVC-intra. Then create a new Vegas project with only the XAVC-I converted files on the timeline. Then see if Vegas still hangs when attempting your edit. Vegas does not support mp4 with H265 natively, and so the add-on that is allowing you to work that way maybe cause the glitch.
When you attempt the edit and the system hangs, do you see little … building next to the frame counter below the preview window?