A few questions for the developers

Former user wrote on 8/6/2019, 9:49 PM

1. The Slow Motion effect. When the effect is analyzing the footage, is it using all frames within that event as reference frames simultaneously to determine the motion data? If so, does that have a chance of grabbing incorrect data from frames that are not similar to the ones being interpolated at a different section of the event? If the analysis does not use all frames at once for reference, why was this approach used instead of a frame-by-frame calculation like Twixtor, s_ReTime, or even linear interpolators built into AviSynth and Vapoursynth?

2. Motion tracking data. Are there any plans to be able to take the X and Y coordinates generated from the Bézier Masking tool and be able to apply them to the center point of an effect, instead of only a PiP motion track? Also, would there be a limitation to doing this with 3rd party plugins because some of them may use different units of measurement, making the scale of coordinates inconsistent?

3. Does Vegas 17 handle project boot-up differently? When opening a project with a large number of files in it, Vegas 16 would load the entire timeline at once, with a chance of some playback performance loss until everything loaded in. Vegas 17 appears to load the timeline in increments, and the timeline cannot be interacted with between those increments. It's been causes freezing and sometimes crashing in situations like this. This is not an issue with projects that only have a few files, though I haven't determined the threshold for how many files start to cause this issue, or whether it's a different variable than quantity like file size, or maybe even media events (such as whether having a lot of splits on a normal amount of clips would cause the same issue).

It doesn't seem like a RAM issue or a matter of decoding performance, since I've allocated 2GB for both Vegas 16 and 17 to use, and also tried different combinations of settings such as GPU acceleration of video processing, Enable Open CL/GL Interop for Intel GPU, and using the Game Ready vs Studio NVidia driver, but they all yield the same result.

4. Are there plans to add more customization to the screen capture utility? The main things that come to mind are being able to save the original recordings (not the .cap exports) to somewhere other than C:\Users\Username\Captures, ability to change the resolution/frame rate, and the codec of the file.

5. What aspects of Vegas Post were influenced/developed by Magix, and which parts by FXhome? If you can't answer that now, could you follow up with this question after Vegas Post releases?

Thanks again for all of your hard work, Magix has been taking Vegas in a great direction.

Comments

fr0sty wrote on 8/6/2019, 11:00 PM

I can answer 3, there's a bug that slows things down when Vegas has to draw a bunch of thumbnails on the timeline, which is why the complex projects slow down but not the simple ones, and why it slows down every time you do something that makes Vegas have to draw thumbs again. To fix it (until it gets fixed internally), go into preferences and either lower the number of thumbnails (I think the options are beginning of the clip, end of the clip, all through the clip, or none) or disable them. This will improve performance. I completely disabled mine to know I was getting max performance, I don't need them anyway.

Former user wrote on 8/6/2019, 11:53 PM

Thank you, disabling thumbnails solved the incremental buffering entirely, though I do need them.

fr0sty wrote on 8/6/2019, 11:59 PM

I contacted Magix about it when the issue happened to me, so you can rest assured they are aware of the limitation and are working on it.

alifftudm95 wrote on 8/7/2019, 1:21 AM

1. The Slow Motion effect. When the effect is analyzing the footage, is it using all frames within that event as reference frames simultaneously to determine the motion data? If so, does that have a chance of grabbing incorrect data from frames that are not similar to the ones being interpolated at a different section of the event? If the analysis does not use all frames at once for reference, why was this approach used instead of a frame-by-frame calculation like Twixtor, s_ReTime, or even linear interpolators built into AviSynth and Vapoursynth?

2. Motion tracking data. Are there any plans to be able to take the X and Y coordinates generated from the Bézier Masking tool and be able to apply them to the center point of an effect, instead of only a PiP motion track? Also, would there be a limitation to doing this with 3rd party plugins because some of them may use different units of measurement, making the scale of coordinates inconsistent?

3. Does Vegas 17 handle project boot-up differently? When opening a project with a large number of files in it, Vegas 16 would load the entire timeline at once, with a chance of some playback performance loss until everything loaded in. Vegas 17 appears to load the timeline in increments, and the timeline cannot be interacted with between those increments. It's been causes freezing and sometimes crashing in situations like this. This is not an issue with projects that only have a few files, though I haven't determined the threshold for how many files start to cause this issue, or whether it's a different variable than quantity like file size, or maybe even media events (such as whether having a lot of splits on a normal amount of clips would cause the same issue).

It doesn't seem like a RAM issue or a matter of decoding performance, since I've allocated 2GB for both Vegas 16 and 17 to use, and also tried different combinations of settings such as GPU acceleration of video processing, Enable Open CL/GL Interop for Intel GPU, and using the Game Ready vs Studio NVidia driver, but they all yield the same result.

4. Are there plans to add more customization to the screen capture utility? The main things that come to mind are being able to save the original recordings (not the .cap exports) to somewhere other than C:\Users\Username\Captures, ability to change the resolution/frame rate, and the codec of the file.

5. What aspects of Vegas Post were influenced/developed by Magix, and which parts by FXhome? If you can't answer that now, could you follow up with this question after Vegas Post releases?

Thanks again for all of your hard work, Magix has been taking Vegas in a great direction.

I hope with new update I can use the Bézier Masking Motion tracking data on other FX too like the Lens Flares plugins. For now its limited to PiP