Aaron Star
Forum Replies Created
-
I think its best to use Adobe or Raw Therapee to process the raw images, then export to .EXR, .png, or even JPEG. Then import into Vegas as an image sequence.
-
I would add that you can use 44KHz with 48KHz just fine. If your project settings are 48KHz, vegas will auto convert the 44Khz media to the final output.
Audio KHz and bit depth (16-24) is much like video resolutions 720 vs 1080 or 4K. Issues can arise if you are doing highly technical work, but for general work most are doing on the forum there are no issues mixing audio rates in a project. If you are concerned about Vegas not handling this correctly, convert all your 44Khz media to 48Khz so that all project media conforms.
-
I think the reason people struggle to tell you some specific number is because compression varies due to motion and changes in the video work. Low motion will compress better, high motion will need more bit rate and increase the file size. Only testing will give you what you want to know.
Generally for 720p h264 distribution, you do not need more than 10Mbs. YouTube streams at 6Mbs. Create new profile from an internet profile, and adjust the bit rate to roughly match 6-10Mbs. Then do some testing on your own.
Here are Google’s settings for the various video sizes using h.264.
https://support.google.com/youtube/answer/1722171?hl=en -
Pretty sure Magix will help with this. Call them.
-
Forgot to add. If you go M2 NVME mode, the whole boot drive is sort of passe. The IO on the M2 drive is so high that the reasons for doing a stand alone boot drive are a thing of the past. It comes down to how much storage you want to spend money on, and how to separate slow media long term storage, from fast media working storage.
-
Depending on the motherboard you buy, look into M2 SSD for the Boot and 2x Hard Drives for the storage. M2 running in UEFI bios and NVME mode on Win10 is where you want to be IO wise. Then place the storage drives(HHD) into a Raid 1 OS mirror for project safety.
SDD Boot: M2 SDD 950 PRO is has superior everything to an 850 EVO.
Hard drives/storage drives: 2 x HGST Ultrastar of whatever size you want.
System Memory: 16-32 GB will give you plenty of Windows disk cache to operate multicam work the best. Disk Cache operates at system memory speeds which is 30-60GB/s, vs a HHD at 100MBs. Even if Vegas is only using 8GB of memory, you need to add the disk cache to that. Windows OS will be using all the extra memory in your system to assist with operation.
Remember storage is not the issue today that is was a long time ago. Everyone’s concerns on storage and video comes from the days when a HDD could not keep up with delivering the data rates. Most consumer video codecs are only running at 3-10MBs, when the drives today are capable of 200MBs. Uncompressed data rates are where you need to worry about data throughput. If you need to work uncompressed, then move your project to the SSD, or work your projects from the SSD and use the spinning media for long term storage.
Personally, i would not build a system today that is not all SSD. I would only use spinning media for long term storage.
-
So if you are only doing movie studio, why not just upgrade to the latest version? Instead of trying to figure out why some old software will not work on what you have going. The latest version is available for trial, you can at least do some testing. I mean its 50 bucks, hardly worth the forums time to try and figure it out. Buy the latest version and let Magix figure it out for you.
When OS version numbers climb they normally do not stop supporting what the last version did. So there must be something wrong with you load of Window 7, or your copy of Vegas is hacked / corrupted. Vegas 10 is nothing special, as its all CPU based. There is no GPU hardware issue to resolve. You only need a CPU and Video card fast enough to throw video to the screen. See the minimum requirements, an apply all updates to windows 7 and the GPU.
-
Did you do your own testing? Did you try the same clip in 2 different projects, and see which is better?
-
I would do some gradient tests when using vegas to process to DNxHR from a 10-bit source. I might be wrong, but I think there is a problem with quicktime not passing the 10bit info through the workflow. Regardless you need to do your processing in 32-bit video levels.
Resolve, or FFMPEG transcode might be better.
-
I would do a trial of XSplit Broadcaster, that app records game footage in Constant frame mode.