-
Videoon 7/18/2018
VEGAS Pro 15 Update 6 (build 384) - General Discussion
Feature / inconvenience fix request. Dear Sirs!Looking close at the audio files you obtain from iTunes you can clearly see they are a lot like the AAC files rendered from Vegas Pro.The most noticeable difference being their extension. iTunes gives us .m4a.Vegas delivers .mp4. Some software have got troubles reading audio-only AAC with .mp4 extension. My request is:Please, change the default extension for the audio-only AAC files rendered by Vegas to .m4a, taking iTunes as the reference. Sincere thanks to you in advance!
-
Vegas Movie Studio (up to ver. 17)on 7/4/2018
Widescreen Encoding
And I did not think NTSC DV Widescreen was supported by .AVI???? 1) All DV is "in AVI". (Except for "HDV", which is neither AVI, nor... uh... DV.) 2) You may have heared "AVI does not support widescreen", and it is right. In some sense. AVI -- as the container -- has got no ability to store/declare aspect ratios (as well as interlacing). But DV -- as the codec (which is comressor-decompressor) -- has got it.If you happen to output an uncomressed AVI you will have no aspect/interlace information in your file; but if you wrap some compressed format inside then the codec may carry the information in it. 3) 854x480 is "16:9 photo", that's right. 4) If you see "Square pixels" words in codec's settings -- it basically means the proportions of the image were/are never chancged/going to be changed during encoding/decoding. If you see words about "non-square pixels" -- this basically means the proportions were/are going to be changed during encoding/decoding.This may require, as they say, "keeping your eyes open" sometimes.If you squeese photos into DV or any other "non-square" format you should ultimately select "non-square" encoding presets. 5) HD / FHD / UHD formats nowadays are "square" (except for HDV) and can be treated like normal photos when it comes to geometry (they do still differ from photos in regard of color).
-
Audioon 5/4/2018
How to render with 24 bit depth audio? (Vegas Pro 14 Build 270 64-bit)
So YouTube's playback bit depth is restricted to 16? May I ask where you found this out? Does any 24bit streaming audio format exist nowadays?
-
Videoon 4/27/2018
Script Menu folder & VegasPro 13 (453)
~ 1) ~ "C:\Program Files\Sony\Vegas Pro 13.0\Script Menu"or"C:\Program Files\VEGAS\Vegas Pro 13.0\Script Menu"-- ???-- Make sure!!! ~ 2) ~ ; @echo off if exist "C:\Users\*yourusername*\AppData\Local\VEGAS Pro\13.0\" ( del /f /s /q "C:\Users\*yourusername*\AppData\Local\VEGAS Pro\13.0\" ) Or ; @echo off if exist "C:\Documents and Settings\*yourusername*\Local Settings\Sony\Vegas Pro\13.0\" ( del /f /s /q "C:\Documents and Settings\*yourusername*\Local Settings\Sony\Vegas Pro\13.0\" ) depending on the situation. ~ 3) ~ Rename the "Script Menu" folder to something else. Like "Script Menu Compromised".Create new empty folder "Script Menu".Start copying your scripts to this new folder (begin with well-known and "native Vegas'es" ones) until you encounter the "corrupted" script which "breaks the Script Portal".Damn it's creators and delete it....If this is the case... ~~~ YOU WILL NEED NO PASSWORDS for the operations aforementioned.
-
Videoon 4/22/2018
VP15 Opacity Handle?
Oh, well, this one is tough!... My today's bet goes...today it goes to...my bet is on...is on... ...an incompatible Extension / Plugin / Script.
-
Videoon 4/7/2018
Mask effect
...Was it that hard or blasphemous to make transparent text on the black background in the first place... to save yourself from lots of "PITA&Rocket science"...BTW, scaling can be made with text controls either, in order to reduce aliasing, since font is a vector object.BTW, adding slight blur is desirable to avoid residual aliasing.No, I am not going to make a video about this.
-
Videoon 4/3/2018
Importing ProRes results in washed out video
MJPEG should not crash Vegas, so I would suggest you to shoot a special short file to send to MAGIX with a bug report. DaVinci Resolve accommodates totally to each & every type of content unless it is stopped by user. So, it is not a reference.
-
Videoon 4/3/2018
Importing ProRes results in washed out video
"Scope Original.PNG" = Correct range of levels."Scope Converted.PNG" = Reduced contrast / abnormal range of levels. ...I tend to believe "other programs" do apply some sort of transform to the preview/screen render... *'Cause my experience tells me that Vegas is on the list of rare programs that do NOT "care about user's feelings" and do NOT DO many conversions behind user's back.** Thus forcing the user to care more about what s/he sees and does. You may wish to look at some external tools/scripts that convert the Vegas's range of levels for preview. This all makes me suppose, your MJPEG is of TV range of levels, in accordance with broadcasting standards, and Vegas shows it right; while third-party applications handle it as "childish" (consumer camera) PC / full range, converting it to even narrower range. __________ * -- Lots of fun happens with interpretation of MJPEG since it never was a broadcast format and there was no "sole standard" about how its levels should be encoded/decoded. One does ultimately need to know his/hers codec/camera/workflow when it comes to MJPEG.** -- As far as I remember, it converts MPEG2 levels.
-
Videoon 4/3/2018
Importing ProRes results in washed out video
They show up as dull and low contrast clips in Vegas... Or, maybe, Vegas displays the video exactly the way it should be. ...however they look fine in any other program. Or, maybe, any other program displays those files erroneously. The screenshot of "scopes", namely Vectoroscope and Waveform Monitor* would have allowed for telling where is the error. ____________ * -- Composite mode, not "Luminance". There is Histogram for Luminance, while the most use of Waveform comes in shape of Composite signal.
-
Videoon 3/26/2018
Please, add NEW RULER TIME FORMATs
All Vegas family have the same ruler formats. ...Maybe for a reason? ... ruler format for PAL 50fps ...How's that supposed to look like? 😲😵😲 NTSC requires specific counter formats because -- at least -- there are two different "stories" the counter tells you.One "story" being the How Many Frames Are There in the video you are looking at (before the play-head).Another -- What Is The Number of the given exact frame in the video in Accordance With The NTSC Regulations. (Everybody knows there goes 'Frame #1002' after the 'Frame #1000' in NTSC.)(Hence the "Non-Drop Frame" & "Drop Frame" counter modes.) ...But... When it comes to ...errr... "full frame"-per-second formats, what goals can not be achieved without the things going beyond the "Hr.:Min.:Sec.:Fr.#" & "pure Time". Including WHATEVER 50 or 100 or 120 or 1256 fps. It seems to be beyond my clear understanding at the present moment.
-
Videoon 3/25/2018
Scene Auto Detection
Hello, Pandorama ! I believe you may wish to look at the Pinnacle Studio. It used to do for me in the past this very job you need now. ...Though, I haven't being working with Pinnacle products for some years. However, page 48 of Pinnacle Studio User Guide says that scene detection is still in there today...http://help.pinnaclesys.com/pinnacle/v21/main/en/user-guide/pinnaclestudio.pdf
-
Videoon 3/22/2018
Instagram video
This looks to me as the original source of "laws of engagement": https://www.facebook.com/business/m/one-sheeters/video-requirements Where "Instagram Feed" & "Instagram Stories" are the items of interest. Guiding steps to the world domination are also outlined here:https://www.facebook.com/business/ads-guide/video/instagram-feedTo obtain the sacred knowledge about Instagram Stories be advised to select the "Instagram Stories" in drop-down menu right underneath the "Choose your ad placement" line.
-
Videoon 2/13/2018
Trouble sorting out codecs in VP15
rmack350 -- Have you tried to rename the file's extension to .AVI ? Could you try that?... Out of pure curiosity. Since it's essentially YUY2 in a MOV container.
-
Videoon 1/19/2018
Color Curves Issue
Stop it. What you are doing effectively is cutting yourself with scissors and then blaming the scissors and the manufacturer. 'Color Curves' is one of those FX that work just fine, as they are supposed to! Go fix your brains and your hands! _______________________________________________ Notes: i....In fact, I do not like "bezier handles" philosophy much. I would prefer the same spline behavior which was in use in Photoshop's curves (and I would like to have export-import from-to Photoshop & Corel Draw). But, sigh.. It's totally operational right now. ii.What are the FX which "do not work just fine"? One of the examples is the 'HSL Adjust' (Hue - Saturation - Luminance). Where the 'saturation' uses an unknown to me "matrix"/idea of color /channel proportions. What do I mean by that? -- I mean, the desaturated image is wrong, it is not the pure Luma Signal (in other words, the pure black-and-white video with color data stripped off)(it's "Y" without "CbCr") it should be.Well, Sony/Sonic Foundry were not alone here. Boris FX also exhibits this incorrect behavior. They had even implemented some "P" mode (HSP) in an attempt to get closer to the correct Luma signal representation, but this "P" is also wrong. I don't know what the problem was/is, it just takes a walk to the International Telecommunications Union's site and reading the "Recommendation BT 709" document to get your hands on the proper matrix coefficients for Full HD pure-luma signal. While "Recommendation BT 601" will provide you with matrix coefficients to SD video. ...OK, for those who has trouble reading the Recommendations, here it is: Luminance Pure Signal of HD (bt.709): Luminance Pure Signal of SD (bt.601): iii.Wonder, is there anybody out there, who managed to implement the correct Desaturation operation for HD video?Yes, there is one company, one FX (actually, the sole one I'm aware of, doing it right) -- 'FilmConvert Pro'.
-
Videoon 1/3/2018
I can't Edit My "Media Generated Text"
...Don't you, by any funny chance, have your "desktop" configured in GPU to use two monitors?... 😁
-
Videoon 1/3/2018
VP14 crashed frequently on pro tools 12 file "CFnd.dll"
1. Find out which VST plugins does the "ProTools" bring with itself / installs. 2. Change the extension of CFnd.dll from "dll" to something else. 3. Launch Vegas. 4. Go to the "Options -> Preferences -> VST Effects" 5. Locate and uncheck the ProTools-inherent plugins. 6. Rename the CFnd.dll back to its normal name. ~~~~~~~~~~ One of the reasons behind the mentioned crash:Vegas calls VST plugins at startup. Some of the plugins do respond in an "uncompatible" manner, thus preventing Vegas from starting. One of MDA plugins I used to know did this. Some of the plugins, in their turn, do activate their host/engine. An example of separated "plugin-engine architecture" being the Waves plugin system. I suppose, what we see here is an example of "uncompatible action" from the host of some VST plugin. ======================= ⚠️ The troubleshooting measures listed above are purely my theoretical supposition/assumption. I have never had any practice with "ProTools". ⚠️
-
Videoon 1/2/2018
Select everything either left or right of point in timeline or cursor
I have Vegasaur installed.The mentioned functionality (Ctrl+Shift+ Home/End) is kept when the Vegasaur's DLL is removed from "Extensions" folder. I don't know what else to say.My PC is compromised by some force? 👽(...I see Russian words in UI, I've got key-commands that do not work for others... 👽👻)
-
Videoon 1/2/2018
Select everything either left or right of point in timeline or cursor
*edited* I have this combination acting in the very same manner in VP10, VP11, VP14, VP15 😵 Ctrl + Shift + End or Ctrl + Shift + Home
-
Messageson 8/31/2017
[Release] VEGAS Pro 15 – Inspiration Meets Productivity
Dear MAGIX Creative Team! Have a good day, and please stop "localizations" from polluting your program's UI ! "Размытие уровней цветности" -- ?...It's an utterly sad bullshit.Something like "Blurring of the levels of colorization" - how would you like that?And that's just one example. Please, dear Sirs!Had a user chosen "English" -- let him/her see English, and so on. Thank you very much in advance!
-
Videoon 8/31/2017
VEGAS Pro 15 build 177 General Discussion
Any suggestions? Remove everything "SeMV" from C:\Program Files\Common Files\OFX\Plugins
-
Videoon 8/30/2017
Vegas Pro 15 - NVIDIA(CUDA) not an option for me on MAGIX AVC/AAC MP4
GeForce GTX 760 here. No NVENC either.
-
Videoon 8/29/2017
VEGAS Pro 15 build 177 General Discussion
Bug Report №__ The Toolbar Buttons do change unsolicited if you make changes to the "Script Menu" folder (add/remove files).
-
Videoon 8/29/2017
SeMW Extensions for VEGAS Pro 15
Well, "no plugin - no message". With this plugin in the OFX\Plugins folder the Vegas would not start. Saying bad things about my .NET Framework installation. Which is v.4.7.
-
Videoon 8/29/2017
VEGAS Pro 15 build 177 General Discussion
... and also tell us what you like about the changes we already made ... Gladly, Sir! The "Spica Resize" aka "Smart Upscale" is a fantastic piece of an overwhelming code, and the idea of incorporating it into the Vegas was/is brilliant & genius! I love it's image enhancement that creates a "sharpening effect" unachievable by other means! Because of this, I can't go back to versions prior to 14. I adore it! * * * Speaking exactly about VP15, the first change I'd like to seriously praise is the absence of "those little thingies" at the docked windows' upper-left corners that made windows close or un-dock if you accidentally hit 'em with your mouse. Now I'm very much pleased to know I have to apply a whole lot more forces and efforts to "massacre the UI layout" :))"Say No to Parkinson!" 😁
Jam_One
Offline, Last login 7/22/2018, Member since 10/28/2016