-
Videoon 2/6/2020
New to Vegas 17 Pro. Why can't I write 22 min movie to reg DVD at 1920
Simply burning a file on a DVD (not compliant with the DVD standard but may run on some players) is no option?
-
Videoon 2/4/2020
Can Magix Vegas make strobes look normal? [video contains strobing]
Requesting longer (/softer??) strobe flashes could be a solution. But many CMOS cameras are simply annoying in this respect.😒 (...by the way: with a thread title containing the word "strobes" and an embedded video with a preview frame of brightly lit faces - isn't it pretty obvious that the video may contain strobing?)
-
Videoon 2/2/2020
Can Magix Vegas make strobes look normal? [video contains strobing]
What we're seeing here are the effects of the rolling shutter of the camera (combined with the asynchronous strobe starting always at a different segment of the frame beeing read out by the CMOS sensor). And there's an additional variation of strobe intensity throughout one strobe flash as can be seen in some flashes by the horizontal stripes/waves. But that's probably not meant by lenard-p. The problem is - as stated before - not called "flicker" and is not necessarily related to an "asynchronous" strobe, as those are almost always not synced to the camera. Maybe there's a plugin to fix this. But it can be almost avoided by using a camera that tends to have less of a visible rolling shutter (the "normal" camera?). It can only be completely avoided by using a camera with a CMOS sensor with global shutter (those are hardly available(?)) or with a CCD sensor (almost not available anymore). I wouldt try to cover it up with white frames (maybe not 70% opacity).
-
Videoon 11/5/2019
Wavy Lines When Downscaling from HD to SD (Vegas Pro 17, build 321)
[...]even when deinterlacing is not used, like rendering from interlaced to interlaced as Alderny did. If scaling is involved, the interlaced source has to be deinterlaced, then scaled, then again interlaced. Otherwise you get those "big wavy lines" @alderny mentioned. That effect is called aliasing and is the sign that no deinterlacing was applied prior to scaling like @EricLNZ noticed. (Maybe a bit too picky, but perhaps this helps understanding...)
-
Videoon 9/6/2019
Apply mask to only one FX
Thanks again! I oversaw the indicating "(2/2)".
-
Videoon 9/6/2019
Apply mask to only one FX
Thanks alot! 2. seems to be working fine for me. If I encounter another problem with this workflow, I will ask again. (You create the subclip only to avoid that the FX affects the whole (original) media, right? Is there a way to switch back to the original event, like with takes?)
-
Videoon 9/6/2019
Apply mask to only one FX
Sadly not what I'm looking for...
-
Videoon 9/6/2019
Apply mask to only one FX
But then it would be media-based, wouldn't it? Is there any advantage over the track FX that i also want to avoid? I need something that is like an event FX.
-
Videoon 8/28/2019
DNxHD Footage
@Musicvid Thanks for the informations. Your suggestions would probably be the reasonable way. But I doubt that such a decision by Magix would influence manufacturers... Adobe or Avid would have much more impact. And because of this lack of format support there may be users for which Vegas isn't usable despite its otherwise ingenious features and workflows.
-
Videoon 8/27/2019
DNxHD Footage
Ah, I see. Since both file types exist I would like them to be compatible with Vegas (regardless of the differences). By "native" I meant that also the mov wrapper should be able to be read without Quicktime libraries - just like ProRes. I would accept an increased price. (but at least for ProRes this was not the case...) I think if a codec is the most efficient or has some technical advantages is not the only point to consider. Ironically for Vegas (a Windows app) ProRes (as an Apple codec) is the only way to be compatible (without reencoding/intermediates) with a large part of professional (broadcast) video equipment. And those manufacturers won't always implement a codec that's technically the most advanced but what is accepted widely in professional workflows ("professional" in the sense of "profession" - it's not less professional to have a understanding of what (UT) codec would be better in a certain workflow - if it's possible). And as the major two NLEs support DNxHD it would be nice if Vegas would do that also.
-
Videoon 8/26/2019
DNxHD Footage
max, DNxHD MOV and DNxHD MXF are as different as night and day. I didn't mean to state anything different (if you understood it like that). But as Kinvermark summarised it, DNxHD isn't really well supported at all by Vegas. I think Marco stated somewhere that ProRes / Magix Intermediate really supports 10 bit and this is also what my tests indicated (undoing "intense" color correction of a rendered file - only 10 bit files survived that). To me my ProRes files looked always great on windows and Mac. ;-) Converting a few TBs of DNxHD files(for a single project) isn't really an option just to be able to edit the footage so I stick with ProRes.
-
Videoon 8/26/2019
DNxHD Footage
I assume that someone recording 4:2:2 video with an Atomos recorder isn't keen on generating h.264 "intermediates" with Handbrake... As far as I know Vegas doesn't support 10 bit (import/export) with DNxHD. Since it worked with VP 16 it "should" also work with VP 17, but maybe the mov wrapper can't be opened because Quicktime components are deactivated in VP 17 per default. (and DNxHD needs those) But rather than having to avoid DNxHD because of its non-efficient/deactivated support/performance (via Quicktime components) there should be added "native" support (mov and mxf wrappers) for this codec. It's widely used and besides ProRes (Magix Intermediate) there is no professional way in and out of Vegas.
-
Videoon 7/5/2019
Graide Color Curves
You explained that a lot better than I did - thanks! But would it be possible to add this feature? I can't really get used to the way the Y'-control affects the image. Or is there a different approach? Mainly I have to match different (or poorly matched) cameras. When I'm trying to correct the "exposure" I don't want to change the perceived saturation or get a washed-out look because that also wouldn't happen when closing or opening the camera's iris.
-
Videoon 6/26/2019
Graide Color Curves
Hello, I just tested the trial version: great handling of the curves - things the "original" Vegas version lacks are finally very easy to do. And the added curves (Y-->S,...)! But there are two things I stumbled upon (V15, build 321): 1. In 32 bit mode everything looks fine in the WFM - like it should. In 8 bit mode even slight changes of the Y curve generate comparatively obvious banding while the "same" curve done with the normal color curves plugin generates only a "normal" amount of banding so that you could use its result for a quick color correction with decent quality - if you wanted to. I can imagine that maybe a curve that looks the same in both plugins is not really the same. But I find it strange that so much banding happens. Best compared with the preset "studio RGB to computer RGB", the "same" preset ("PC") of the SeMW extensions seems to perform the same in the WFM - only with less banding (OK - it uses the levels plugins, but...). The "solution" to this comes with: 2. (independent of 32/8 bit - except the WFM/banding of course) The visual result of the "same" curve (again only Y/brightness) differs alot in the video preview, although the WFM seems very similar to the one with the Vegas color curves (assuming almost the same curve...). I am simply not able to get the effects/results I am used to when handling the Graide Y curve. In comparison the picture seems too bright/less saturated. I am comparing the "RGB" mode of the Vegas plugin with the Y curve. To my understanding that should technically be the same (Y = brightness = same changes to R, G and B). Am I wrong? Results got much more like I expected them to be as I copied both nodes i changed (great that this is possible!) from the Y curve and pasted them to the R, G and B curves. I then deactivated the original Y curve and finally got as close to the Vegas plugin as it is possible by approximating the curves visually. And the banding was also gone! But shouldn't be RGB=Y? The Vectorscope shows that the Vegas plugin changes also the saturation when manipulating the RGB curve while the Graide color curves almost don't change it. That was probably the cause of the impression of a less saturated image. So do I understand this plugin and its concept totally wrong? I always thought that raising the brightness means amplification of Y, which means amplification of RGB to equal parts and thus generates a higher "absolut" (measured) saturation, but staying the same visually and relatively to the Y component. Could someone explain that further, please? Thanks! ;-)
-
Videoon 4/7/2019
Color Processing and Bit Depth in Vegas
I did some testing: I imported ProRes 10 bit footage (containing a slight brightness gradient) into a 32 bit float project, applied a levels filter, set the gamma to 5 and rendered it to ProRes HQ. Then I reimported that and did the same. When I imported this clip (2 render generations) and applied 4 levels filters with gamma 0,45 (almost the opposite effect of 2 times 5,0) there was almost no banding visible (slightly rough histogram). (With XAVC-I slightly more banding/artifacts and with DNxHD (set to 10bit) clearly visible banding) When I did the same (again, ProRes) with project settings set to 8 bit (only for rendering) there was considerable banding visible. Doesn't that indicate that ProRes is being rendered with 10 bit? (and DNxHD behaved like it "should")
-
Videoon 4/7/2019
Color Processing and Bit Depth in Vegas
OK, thanks. But the imported ProRes is decoded as 10 bit (with 32 bit float project settings) and an XAVC-I export will contain the "real" 10 bit?
-
Videoon 4/7/2019
Color Processing and Bit Depth in Vegas
And rendering is different from project's internal video processing. If the renderer doesn't support more than 8 bit, you're done, which is the case when using Magix Intermediate. All of the Magix renderer versions of ProRes are 8 bit only. You need to use a 10 bit video codec instead (or a 10 bit or higher (or a float point) image sequence codec). Hello, I almost started a ProRes "10 bit" render process before reading this. I made a mistake during recording a ProRes 422 HQ file. I created a Vegas project to correct that (process creates heavy cpu load) and want to rerender it so I can use the corrected version as if nothing happened. Now I learned that a ProRes-->ProRes rendering with 10 bit isn't possible. Which intermediate codec will be rendered in 10 bit? (uncompressed, etc. is not an option because of the file size) I've read about a problem with Sony XAVC-I (or was it Sony AVC). I'm using Vegas Pro 15 (build 321, since later ones displayed green frames with P2 footage). If I understood correctly it's that simple: import ProRes file in 32 float project and rerender using an 10 bit capable codec. (?)
-
Videoon 2/6/2019
Docking a new window in the docking area next to other windows
OMG, I don't know why that didn't occur to me. Many thanks!
-
Videoon 11/8/2018
Video Clip Keeps Flickering Black on Sony Vegas Pro
Hi, is upgrading the hardware the (almost) only suggestion? I've seen similar flickering (in the timeline preview but also in the rendered file) that's getting darker and darker because of crushed blacks and an increasing contrast through the use of the smart GPU deinterlacer (VP 14/15).
-
Videoon 7/2/2018
Wie wird eine Blueray oder DVD erstellt.
Authoring bezeichnet quasi alle Arbeitsschritte, die im DVD A druchgeführt werden. Die Arbeitsschritte vor DVD A sind hier nicht relevant (Neat Video, etc.) Wichtig ist nur, dass deine fertig gerenderte Datei den Anforderungen einer DVD/Blu-ray entspricht. Im ungünstigsten Fall wird DVD A aber auch eine Neukodierung vornehmen. Nicht optimal, aber für dieses "Play"-Problem irrelevant. Wenn du im DVD A ein neues Projekt erstellst (gerne auch mit Menü, nicht unbedingt "einzelner Film"), dann kannst du in die zentrale Menü-Vorschau einfach eine Videodatei per Drag and Drop aus dem Explorer hereinziehen (testweise). Es entsteht eine Schaltfläche zum Video starten (sollte in der Vorschau auch so funktionieren). Wenn die Blu-ray dann vorbereitet und gebrannt wurde, sollte auch im Stand Alone-Player die Schaltfläche funktionieren und es sollte alles getan sein, damit nicht mehr "Play" in dessen Display steht.
-
Videoon 7/2/2018
Wie wird eine Blueray oder DVD erstellt.
Könnte es sein, dass du das Video beim Authoring nicht als Videoelement einfügst/abspielst, sondern dass der Player den Film als Menü abspielt? Dann steht bei Playern öfter mal nur "Play" im Display.
-
Videoon 6/30/2018
Preview is in slow motion
As problems with the audio hardware can sometimes lead to a stuck cursor (no playback at all until restarting Vegas), maybe this could also be caused by your soundcard/interface/driver settings?
-
Videoon 6/29/2018
Preview is in slow motion
What impresses me is that the timecode display of the timeline is counting at half speed. No matter how hard I try to do this to my timeline or project settings (timecode display), it doesn't happen. As far as I know, seconds of the timecode display should always be real seconds. In this video that is not the case (playback for 8 of 11 seconds in the video, TC advances ~4s). Only (other) solution could be that this captured video is also palyed back at half speed (can't find any real time reference).
-
Audioon 6/15/2018
Not recognizing SMPTE/EBU timecode
Hi, if you manage to know the timecode before import, you can set the ruler start time in the project properties (Properties --> Ruler). That avoids the negative timecode in the timeline (and empty space). And you preserve the original timecode in the timeline if you need that for your workflow. To delete the empty space you can select a region of the timeline and enable auto-ripple (Ctrl+L) and press delete. Don't forget to disable this option afterwards.
max8
Offline, Last login 11/20/2020, Member since 9/23/2016