Aaron Star
Forum Replies Created
-
Aaron Star
August 27, 2015 at 9:12 pm in reply to: AVCHD rendering @60p w/ Intel Quick Sync Video problem – Vegas Pro 13It is really odd that Sony does not do a better job on keeping up with these new technologies. You have to wonder who is in charge over there. I mean NV, AMD, and Intel all have hardware mp4 integrated, and there is list of cheese ball apps that support the functions, but Sony Vegas….has issues. I just find this really weird.
-
Lets see…hmm. There have not been any changes to Windows since 7, unless you consider these as changes:
Improved memory architecture:
•
Windows 7
•Starter: 8GB
•Home Basic: 8GB
•Home Premium: 16GB
•Professional: 192GB
•Enterprise: 192GB
•Ultimate: 192GBWindows 8 & 10
• Windows 8 – 128GB
• Windows 8 Professional – 512GB
• Windows 8 Enterprise – 512GBLighter weight OS overall that boots faster, much faster. On my configuration, once my system clears Bios checking, its only like 10 seconds to desktop. Basic OS load memory utilization actually went down on Win8.
Windows 8&10 include Hyper-V – win8,10,Server 2012 support dynamic memory support, OS like Unbuntu do not support dynamic memory.
Windows 10 supports DX12
Chrome, Firefox, and Edge all perform faster in 10.
Integrated AV
Improved device support, and improved OS update technology.
I will say that my printer from 2000 no longer auto recognized, and I needed to load an HP driver that was compatible manually. Not sure that is an HP or MS issue though. HP makes ****** products.
-
Aaron Star
August 26, 2015 at 9:50 pm in reply to: AVCHD rendering @60p w/ Intel Quick Sync Video problem – Vegas Pro 13This is interesting to me. Since your source footage is AVCHD2.0@60P, have you tried rendering a test clip to XAVC-I or SonyAVC in a 60p profile, then attempting the Quicksync render?
Have you made sure that you have the latest Intel video drivers for your chip, and chipset.INF?
Not saying that this sample of video is using Vegas to prepare, but there several examples on YouTube of 1080@60p quick sync.
https://www.youtube.com/watch?v=_qLl4VtRNXc
-
As long as DVD-A is not saying it is going to recompress your audio, it will just Mux the AV into vob files. Your audio channels should remain intact.
Have you run a test disc to see if there is a problem?
-
Aaron Star
August 26, 2015 at 9:35 pm in reply to: Mysterious lagging phenomenon on freshly-rendered fileWhy would you render the DV capture to MPEG2? DV is going to be as good as it gets from the ADVC-300.
If the project timeline is lagging when it hits the DV footage, I would check the project properties of the DV file. Make sure the dll being used is Sony’s, and not some other company.
-
The HD7970-ghz I recommend based on your budget, you would have to source one from EBay.
I compiled a list of cards from wiki, and other sources that sorts the cards I recommend by release date. I tend to look at cards that score high in Single Point GFLOP performance, since Vegas is looking to the GPU for OpenCL calculations.
As John said, and I believe read some time ago that the MC encoder stops GPU assist at the HD69xx series. Most export then use Handbrake for upload to something else. I personally just render to XDCAM-ex and upload that directly to YouTube, or use Sony AVC at various levels for something like MPEG-DASH. 32-bit modes, Sony AVC, XDCAM, HDCAM, and XAVC will all use the GPUs HD5700 thru R9-390x.
The 6970 may be a good choice too for the MC encoder reasons, however you also said you have a PCI3.0 board, and so the 7970-GHz would be a better with the upgraded interface. PCI3.0 is a significant upgrade in bandwidth and reduced overhead. This would be more in line with the class of system you have.
-
HD7970
290x / 390x pretty much the same minus the improvements you added.
My opinion is not that popular, but I believe in X or what AMD labels XT chipsets. These are what the likes of Apple choose, and represent what the engineers setout to achieve, more so than the non x series cards. They also offer better computational performance.
-
“Generally you want to be at double or quadruple the bitrate for editing.” – what does that mean?
Normally when you record your source material, you want to record at >10Mbs for HD .mp4 or in this case Windows Media. Like I said before WMV is just a Microsoft version of .mp4 with MS audio.
How you capturing your source media to edit?
“Is my footage not full hd?”
According to Media Info no:
Bit rate : 6 519 Kbps
Width : 1 440 pixels
Height : 1 080 pixels
Display aspect ratio : 4:3
Frame rate : 23.976 fps1440×1080 is considered HD but in a 4×3 aspect ratio matching older TV sets, the older square sets vs. typical HD 16×9 ratio. If all your footage looks stretched vertically, then changing the Pixel ratio can correct the footage to 16×9. The original HVD captured in 1440×1080 with a rectangular pixel, that later played back in a 16×9 ratio. True HD is 1920×1080 with a square pixel. Media Info is seeing the footage marked as 4×3.
i tried to render in the settings you gave me but it still crashed.
Does it crash in the same place? Have you tried muting tracks and test rendering, maybe bypassing the effects or uncheck or disable the effects on the footage? Trying to determine where in the footage or effects the error is happening. Could be a corrupt spot in the media stream that vegas is not doing well with.
You could try using “Sony AVC” and a profile that matches your project. Also maybe try rendering a test to .avi DV Profile, in attempt to rule out a WMV issue.
“if i upgrade to a new sony vegas will i still be able to open this project in it?”
The new Vegas will read the old file, but save to a new format that VP9 will not read. You can try the trial version of either Movie Studio , Vegas Pro, or Catalyst Edit. You will still be able to open the old version of VP9, just make sure to not save over your original file if you plan on going back.
-
Its been a long while since I have seen the VP9 render as panel. Most codecs will allow you to go in and create custom render size, and save that setting as a new preset. If I remember right the XDCAM support was not to .mxf, but stored it in a .mp4 container. Can you post some screen shots of the render as window? VP9 according to wiki was the 1st version to fully support xdcam. Are you on the last build?
Based on the footage info you posted, make your project settings 1440 x 1080 @ 23.97FPS, square pixel aspect ratio. Then create or use an equivalent WMV profile that matches 1440×1080@23.97FPS, square pixel, and bitrate of >10mbs. You can also enable the Quality VBR mode, and WMV will auto determine the bitrate.
Your source material is only 6Mbs for a 1080 material, that is less than what YouTube runs at for HD content. Generally you want to be at double or quadruple the bitrate for editing.