Chroma Blur -- abandon the Gaussian function, replace it with Box.
Where "Radius=1" means the chroma of the immediately neighboring pixels is mixed 1:1. With no influence of the distant pixels farther away.
Where "Radius<1" would mean a "portion of chroma, less then full value" is taken from the immediately neighboring pixel to be mixed into the pixel which is currently being processed.
FX Mark -- add FX Mark overlay on the Media thumbnails in Project Media browser. In the very same manner as it is overlaid on the Events.
The practical idea of Chroma Blur seems to be the compensation of the quirks of the chroma subsampling. So, straightforward masking/suppression of 4:2:0 chromatic upsampling errors does essentially require the chroma of adjacent pixels to be mixed 1:1. With no effect from other distant pixels. To the task, Box/Linear blur is relevant, Gaussian blur is not. Gaussian function/distribution, which is now used within "Chroma Blur" filter (according to my "investigations"), involves the influence of the distant pixels, which effectively forces the use of radius <1 and makes the operation non-intuitive. I, personally, do not use Sony/MAGIX Chroma Blur at all. I use Boris FX's 'BCC Gaussian Blur' filter with "Quality" set to "Gaussian Low" which mimics the Box algorithm most closely/almost precisely, to my mind.
Will this time there be exports in 8K on Vegas 15? Or wait until Vegas 16 for the 8K? And what will this time be customized the resolution for export on all video formats? Thank you for answering my question.
Awesome news, props to the magix team. Can we optimize the audio engine when multi tracking with many tracks and effects applied without audio droputs, glitches, stutters, buffering problems etc. That would kill the need to export to another DAW for mixing.
Taking this opportunity, I would like to ask MAGIX to provide us with a model system spec or two (NOT a minimum system requirement) in order to indicate what sort of systems would allow to achieve the intended features they implement (whether QSV, VCE or whatever). I know, as a software developer, MAGIX might feel awkward to recommend specific computer models or devices (e.g. exactly which model of GPU's) obviously for commercial reasons, but I still believe they could state what "test-bed" (computer model, CPU, RAM, GPU, software driver versions etc) they used in order to achieve the intended features without a crash or hang. I feel it unfair that MAGIX continues to let users test and decide what devices should be used or not used to achieve those intended features. I have been seeing a number of crash/hang reports in the forum over the past years, a part of which even from the Sony Vegas days, and feel MAGIX held responsible at least for a part of it (i.e. the failure to indicate what devices/drivers to use to properly achieve what's intended).
Hopefully you guys have done something about one of the most annoying things in the latest Vegas versions (It was way better in early versions) , which is that it is terribly hard to find the sweet spot in the corners of the footage clips to drag a fade in/ fade out into it.... This is hardly impossible to do sometimes and drives me mad.
So glad to see this - although I run FCPX on an iMac right next to my HP Workstation with Vegas Pro 13, I always find myself coming to the same conclusion. Nothing compares to Vegas Pro for speed, ease of use and a a common sense approach to editing video and audio. Can't wait for VP 15!!!!
This is always good news....but I can only cross my fingers that the dreaded 'black screen' issues have been resolved. I've been struggling with them since version 11 and hope that version 15 will nip it in the bud. For anyone that has had this issue, or has solved this issue, here is the post I have been trying to get answers to.....thanks to all that take the time to reply.
I know many of you have experienced the black preview screen, which leads to the blank rendered screen. I've tried all the fixes I can find online, including switching off hardware acceleration on my video card and switching 'close media files when not the active application'.....etc. None of these fixes work. In my case, the project seems to be moving along very well, the on a dime, just stop previewing properly. Ironically, some clips will continue to work while most will not. But the condition can worsen and include 70-90% of my clips. No issues with audio when this happens. This started in Sony Vegas Platinum 12 for me. I upgraded to version 13, and then Magix Movie Studio Premium 14. I've experienced this problem in each version. Can anyone offer some shreds of hope as to how this problem can be overcome? I found nothing on the Sony site back in the day and I see nothing about it on the Magix site now.
Any help will be greatly appreciated. Thank you so much!
Magix, thank you for the support. Please make a new benchmark file available to us so we all can benchmark our systems on the new software, and determine the best possible configurations for using Vegas 15. Something that utilizes all of the new features and gives us a nice stress test.
To all of those who plan on upgrading, please remember to backup your current system BEFORE you do the upgrade! And make sure the backup actually works! I have used backup software in the past that said the backup was successful and it turned out to be unusable garbage. Thank goodness I had another good backup or else I would have been in BIG trouble!
Also, do not upgrade while working on an important project. Do not even think about it.
I cannot count how many times someone had upgraded and was trying all kinds of hacks and workarounds in an effort to get things working again when the upgrade has failed to work for them. They did not have a verified backup.