-
Audioon 3/3/2023
[bugs] Vegas 20 - summary (I hope) of the VST crashing issues
I already work with Sound Forge since 1997, but it's architecture blocks me from using it as a wordshaper (which is a normal definition in my workarea, btw). I also work as a geräuschemacher for international movie companies, but some of it call it foley-artist or sound-designer (-architect) (or just a soundwall-editor). Anyhow, Sound Forge works lineair and destructive, so it's not possible to use it - also because it's filecontainers are pretty obsolete and proprietor, software-wise. My native is not English, so forgive me my grammar. Since I use Vegas from 2003 until now, I (and Vegas) started out as a DAW, but I have moved on technically and Vegas didn't. Bottom line : Vegas 20 says it's supports VST2 / -3 and it doesn't, it's buggy as hell in real life production environments. I just want Vegas to work like they promise, not using other software to get the job done (which is not possible, since I am stuck to this workflow for the project I mentioned).
-
Audioon 3/3/2023
[bugs] Vegas 20 - summary (I hope) of the VST crashing issues
...is that no one from Vegas ever answers and support is not existing. Sure!Even us the users won't follow you, else you report the concrete issue that is reproducible under certain HW and project environment and so on. How much you did spend or how long you do your job does really interest nobody. I think meta-data is important, it's also shapes the problem and issue. It's not "just an issue", it's the death of Vegas for professional audioshapers in our industry. But don't worry : once the devvers do squash the bugs in their repo or dist. / I'll quit and you'll never hear from me again. Not sure what iteration / grunt-system they use, but since it's .git based, solution must be possible.
-
Audioon 3/3/2023
[bugs] Vegas 20 - summary (I hope) of the VST crashing issues
While I appreciate the summary, the fastest road to solving this issue is replication. If you could provide a few specific examples with steps that others with the same VSTs could attempt on our systems that would probably be more useful to the developers. What are these VSTs applied to. Tracks? Events? Does event type matter (wav, mp3?) Is the auto resizing of Fx windows feature enabled in preferences? Does it matter in your tests? A few of us have noted undo bugs with VSTs. I will upload a basic Vegas project with the settings. Thx! (main problem - besides the bugs - is that no one from Vegas ever answers and support is not existing)
-
Audioon 3/3/2023
[bugs] Vegas 20 - summary (I hope) of the VST crashing issues
You msut have bought a faked VEGAS. 😬😬 These days half the posts are from you, and we even don't know what HW you use, what a project you build and what parameters you did or didn't changed in the e.g. app preferences, etc...😌😌😌 I am a liable buyer of Vegas since 2003. And I am not an "average" user. I do use Vegas purely as a DAW. I am a word-shaper. So I do shape the sound of words, by adjusting the intelligibility of every sentence / start and end of a word. Sometimes I work eight hours to adjust ten words on a row. https://i.ibb.co/wWS1xRw/eq.gif Above capture is how it works by finetuning EQ dynamically. Vegas does say it supports VST, but Vegas 20 is extreme buggy when using professional hardware and software. My basic set-up is worth more than $ 15.000,- and it still not works. At the moment I am working at a project I started in 2019 and I work about 120 hours a week on this, 7 days a week. In 2025 it must be finished (it's not payed, I do it for fun) and I am stuck to Vegas, since I started with it in 2019 and can't switch DAW in between. If you are interested in the profession of word-shapers, take a look at this clip that explains; - edit - This forum mess up the embed deeplink, you have to skip to 284 seconds. I think Vegas should embrace people like us, because we fight against "the big three" (US based tech, like Adobe) and do power the base of there product.
-
Audioon 3/2/2023
[bug or feature] auto-ripple affects also unaffected events
Maybe even though it is the end of the event that is being edited, the whole event is judged to be the beginning of the edit, and the ripple proceeds from the front of the event. That is an inconvenient corner case that would need to be better tuned. Yeah, something like a toggle; Affect ALL events Affect only when the event is BEFORE* the edit Affect only events AFTER* the edit *) I mean "before" and "after" solely based on there placement on the timeline. Not before, or after doing some editing __A_B_x_C_D__ So "x" is the "edit", A / B are placed before, C / D are after and A / B / C / D are both. You can select whether A B (before) are affected when editing x, C D (after) that same edit or simple the complete range (A B C D). It looks difficult, but this way auto-ripple comes more predictable for many edits. 9 out of 10 I (audio-)edit "from left in the timeline to the right", so when I do an edit, almost never I want the events "before" (on the left) of that edit to be affected.
-
Audioon 3/2/2023
[bug or feature] auto-ripple affects also unaffected events
That help says " the contents of the timeline are rippled after the edit according to the option (etc.)". So it doesn't sound like the OP scenario is working according the the help. Like I said : I am holding it wrong. But in my opinion an envelope placed before a cut is never affected, thus should not move at all.
-
Audioon 3/2/2023
[bug or feature] auto-ripple affects also unaffected events
Well, it explicitly says affected. And a marker or event chronically placed before an edit, is never affected. I mean, you have a timeline / event like this; __mumble__mumble__SHOUT__mumble__mumble__ Than you do two things; Soften the shout by an envelope Cut of the last mumble (or is it "mumbling"?) __mumble__mumble__shout__mumble__ The envelope that changes the SHOUT to shout should not be affected by cutting the last __mumble__ but it is in my example (first post).
-
Audioon 3/2/2023
[bug or feature] auto-ripple affects also unaffected events
It may not be what you want, but according to the HELP file, it is the intended behaviour. Yes, but it states "affected". And every event chronological placed before an edit, is not affected by the edit. Graphical; - A - B - C - D - E - Let's say I cut out "C", this will become; - A - B - | - D - E - Timeline-wise only D and E are affected; - A - B - | - D - E - So in my opinion A and B should not be altered, when chancing something between B and D. Why would an envelope or marker placed at B be affected when you cut out C? That doesn't make sense, from a timeline-point-of-view...
-
Audioon 3/2/2023
[bug] Vegas 20 - RX10 crashes and freezes total GUI
VP 20 has a new audio VST engine. My initial testing of it showed issues with Izotope VST2s (which I reported) and I just continued with 19 / RX9 so I can complete projects in progress. I also bounce audio to RX9 and use multiple RX plugins there instead of in Vegas. For projects where I'm not doing much with audio I use 20. Thanks for confirming. Now I am not alone in cyberspace with all the issues Vegas gives me. The new VST2 / VST3 engine is, simply said, pure garbage. RX10 even refuses to render in Vegas 20 (crash) and freezes when adjusting parameters. Melda plugin do crash, because of an undo-stack-error in Vegas' side (I already did report it). Other VST3 plugins can't undo, freeze or crash. RX09 is "okayish" (yes, Vegas does crash) when you finetune them when not in plain sight (toggling the status, etc...). But RX09 in Vegas 19 is not workable, when used with envelope-events (adjusting a parameter from 5% tot 5.01% freezes / stutters the complete system). So now I am stuck with Vegas 20, RX09 and VST2.
-
Videoon 3/2/2023
[feature] Copy / paste specific bezier-point
I like the idea of being able to copy/paste volume-envelope break-points. But not for your reason. Sometimes points that look alike are not and if you try to drag them down in a pair to zero, they won't go all the way. A quick cut and paste would fix that. Presently I reset them both, then drag. Or to just equalize a pair: double-click on one, copy the value, double-click on the other, and paste the value. Most tedious. Instead of inserting break-points one at a time... try four-at a time. Obviates the need for most single inserts. Yeah, enveloppe points became rather buggy in Vegas 20, especially when "auto ripple" is turned on. But I can select four points at a time and copy them in concussive order; The point is (pun intended...) sometimes I want "exactly" a 100% copy of a point with all it's linked parameters (from the timeline to the plugin it triggers).
-
Videoon 3/1/2023
[bug] Explorer is breaking parent / child relationship
Thanks for the response. I am not sure what your movie show, but I encounter the bug since +/- 2010 in Vegas 13 ~ 20 on several machines / configurations. I can not upload a screen recording here, but please check : https://i.ibb.co/wWtxh6d/refresh.gif As you can see, after some tries the parentfolder (on the left) resets totally, while refreshing it's content (on the right). (I cropped some of the left explorer pane, but that's because of privacy). Literally the left pane traverses up to the root of that disk, resetting it's own state.
-
Videoon 3/1/2023
Forum access issue
Our system administrators are looking into the problems. It's a serverside problem. The queries to the main DB are routed wrong, so the ping is extreme low which results in unreachable / unusable interaction. Check the booleans inside the DB query, they are overflowing the system. Lol, this low end scripting platform becomes as buggy as Vegas does. Maybe the loadbalancer went nuts and is now resolving the wrong DNS, but the issue is 100% backend related. It's not only the forum, the homepage also went dead and showed a dead cat with sunglasses. ping www.vegascreativesoftware.info Pinging agw-gwc-vi-prd.germanywestcentral.cloudapp.azure.com [51.116.187.243] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 51.116.187.243: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
-
Audioon 3/1/2023
[bug] Vegas 20 - RX10 crashes and freezes total GUI
I'm not sure why you spent any money on hardware to address software issues. I've also seen functionality issues with Izotope RX9 so mainly stuck with VP 19 for audio which mostly works. RX10 is VST3 only, right, so you have to work in VP20? I haven't yet upgraded for that reason. In VP20 I see hangs as the window draws but if I wait it comes back. Hopefully you reported details of issues to both Vegas Creative Software and Izotope. Happy to attempt to replicate issues with RX9 for diagnosis purposes if you specific which plugins and what you are doing with them to trigger problems. Because some other mentioned it a hardware (videodriver) issue "or something else". Vegas 19 / RX09 is "okayish" : it does crash (what isn't?), but it works when don't leftclick on certain GUI items. Vegas 20 / RX10 is crap : nothing is reliable. On a more personal note : I quit my job and started working on a private project for about 5 to 10 years. I am halfway now. This project heavily relies on Vegas for the audio-part of the project, so I can not switch back and forth because of legacy reasons (yeah... Vegas 17 can't open Vegas 18, while the fileformat is exactly the same : I did heavenly filediff testing, XML investigation, etc... to see "why" it wasn't backwards compatible). Bottomline (from my developers point of view) is that all the crashes has something to do with "the state" and "the way" this (mainly visual) state is saved inside the parent Vegas container. The canvas, redraw of items, etc... are linked with all the freezes. Even when undoing a split or edit in the main timelime does totally redraw the complete GUI, even when the plugin itself is not altered at all by that undo. There is something fundamental wrong with the way Vegas handles the pluginchain / canvas and "state / memory" update.
-
Audioon 3/1/2023
[bug] Vegas 20 - RX10 crashes and freezes total GUI
Have you reported your issues to iZotope? What do they say? I also have (trials) of other NLE / DAW, even freeware solutions. They all work 100% fine and flawless. Even embedding a Melda plugin, combined with RX inside iZotope (the editor) works... Just adding one single Melda or RX DLL does crash complete Vegas since version 20. So I think, after weeks of debugging, crashlog investigation and testing in multipurpose environments the culprit is Vegas, not the messenger. _________________________________ Besides that : I am a devver myself and do know how ecosystems of DDL (dynamic link libaries) work. When Vegas says "it does support VST 2 / 3 extensions", all those extension (within the programming protocol) should work flawlessly, because when not Vegas can't say "it does support the protocol". I mean, even when my microwave says "we do support VST", it should be able to handle them, because otherwise it doesn't support them. Things would be different when Vegas should say "we don't support VST, but hey! You can always give it a try, maybe the system crashes, maybe the GUI freezes, but that's because we don't support them." _________________________________ FYI : Melda plugins are also crashing. I did contact Melda (and Vegas) about this. Vegas never answered, Melda did. Their answer? "Sorry, but we don't support Vegas because the devs from Vegas never answer our e-mails and are not willing to work with us."
-
Videoon 2/26/2023
How Did Vegas Pro Get So Good?
@Foo-Bar There is nothing obscure on my .vbs, as I write it myself, not taken from the net! Code inside "Kill Vegas.vbs" (pretty similar to .BAT): Set oShell = CreateObject("WScript.Shell") oShell.Run "taskkill /f /im vegas200.exe /t", 0, True Well, that's the same script I use in the .bat file :-) I like low-level programming, so using a plain text-file is (sometimes) more fun than wrapping it inside a scripting development. Glad to see it works for you!"pro" tip : create a shortcut for the .vbs / .bat and assign a nice name / icon to it. When a crash occurs, at least you have a funny icon to look at... (and the distinctive look will assure you won't accidentally click the "app" if you want to launch, and not kill it). SOUND FORGE VEGAS ICON ENVIROMENT Speaking of graphical assets, did you know how professional Vegas is upgraded from 17 to 18? Just kiddin'... found this asset inside the executable of Vegas while extracting the icons. But it's inside every ones copy, I guess... a hidden gem.
-
Videoon 2/25/2023
How Did Vegas Pro Get So Good?
I do have a "kill vegas process" .vbs handy at he desktop for when it will not start No need for obscure .VBS as one can do it by .BAT taskkill /F /im vegas200.exe I even made some special .bat files with icons for it and stored it in my app-menu for quick access (need it dozens of times when Forge is not starting due to a link-library-bug, when fired from Vegas).
-
Videoon 2/25/2023
How Did Vegas Pro Get So Good?
We've been working hard behind the scenes, and the developers have been working even harder. VEGAS has a very solid, exciting future ahead of it. Thanks for the heads-up. Personally I use Vegas 100% as an advanced audio-editor / DAW (since version 3) and do have three serious bugs in Vegas 20. Please don't only focus on video, also keep in mind audio is important. I've bought a brand new system for almost $ 3.500,- to get rid of those bugs and there are still there (i9 Intel, 12th generation, 128GB ram, Samsung 990 PRO ssd's, top notch audio connected). 1. Today I had to restore at least 10 times a single project because the order of the VST2 / 3 | 32 / 64 bits audio-plugins were corrupted; https://www.vegascreativesoftware.info/us/forum/bug-vegas-20-plugin-order-corrupted--139874/ 2. On top of that the timeline shows complete garbage / garble visual artefacts (did buy both NVIDA + AMD GPU cards to solve it (by driver) and the navite iGPU on my main systemboard : none of it did work). https://www.vegascreativesoftware.info/us/forum/bug-selection-cursor-artefacts-on-the-timeline--138798/ 3. And last, but not least for sure, is the 100% freeze / crash when altering some parameters from third party plugins like RX (iZotope) or Melda - due to a ridiculous "undo error" which is overflowing the internal buffers; https://www.vegascreativesoftware.info/us/forum/bugs-vegas-20-freezes-when-undoing-melda-plug-in-and-more--139751/ It takes me more time to buy / test new hardware and re-opening projects than I can work on them without any trouble.
-
Audioon 2/22/2023
Audio Keeps Going For 0.5 to 1 Second, after pausing
Like the title, whenever I pause my video, the audio keeps going for 1/2 a second. It's very annoying, anyone know how to fix this? Currently using Vegas Pro 20, and on Windows 11 Be sure in "preferences / audio device", the "buffer" en "latency" times are as short as possible. Of course, when audio is stuttering or "shows" anomalies, some higher values are better.
-
Videoon 2/22/2023
[bug] selection / cursor artefacts on the timeline
Bug is still there, I even bought a brand new dedicated videocard for this issue (NVIDA studio drivers), but it remains. Both Intel iGPU 770 and NVIDIA triggers the issue, which makes editing almost impossible. I did spend about $ 3.000,- for this bug (brand new system and brand new card) but it's still there.
-
Videoon 2/17/2023
after installing video saver, no picture from video recorder
Most users and moderators speak English, not Dutch / Belgian. Dat had je gedacht 😄😉 Ik kan het bevestigen.
-
Videoon 2/17/2023
after installing video saver, no picture from video recorder
(Title changed to a "lingua franca".) English isn't mine, that's why the typo :-)
-
Videoon 2/17/2023
Terminology
I was having trouble getting the fade in and out tools to work. They usually do, but not today. I came here for help. Someone suggested moving the Composite Envelope down and out of the way. It worked great... once I figured out what the Composite Envelope was. I'm a long-time user, but I don't always have the right terminology. I don't work with other users, nor do I communicate with them, so to me, it's that blue line at the top of the video track that moves the video between 0% and 100%... the fader or dimmer, in my mind.I'd like to respectfully suggest that when certain terms are used, they are defined as well. Thanks for the help, and for considering my suggestion. ms Composite is sort of an skeuomorphism (not sure if that helps...) and dates from the early beginning of photography (like 1880 or so). Lot's of stuff in modern editing is still referred to as analogue terms, even GUI-wise (with knobs and sliders and handles). https://www.wix.com/blog/photography/what-is-a-composite-photo-and-how-to-create-one#:~:text=When%20photographers%20say%20%E2%80%9Ccomposite%E2%80%9D%20%E2%80%93,unwanted%20pieces%20using%20different%20methods. Simply said "composite images" are two sources, blended together (hence the fade). Photoshop has it's composite engine, Vegas has and even in programming (low level machine language) you can create a composite when doing OOP (Object Orientated Programming). Today, it's kind of abstract but it's sure "more than opacity" (depends on the state of composite you want to achieve).
-
Videoon 2/17/2023
after installing video saver, no picture from video recorder
Het beeld vanaf de videorecorder krijg ik niet zichtbaar op de laptop. Hoe kan ik dit verhelpen? It's better to communicate in English here, since it's the language franca. Most users and moderators speak English, not Dutch / Belgian. And when doing so, do translate the title for better understanding!
-
Videoon 2/16/2023
Shortcut : fit track(width) into view?
Looked into the code...the fact the double click is not accurately resizing has to do with a remnant of the audio beginnings of VEGAS. Anyway, the extra buffer added to the timeline after a project is opened is actually a bug. The code being executed that added this buffer at the end of the timeline is actually supposed to be called when we are in the process of recording audio to an audio track. Anyway, I have this fixed and it will be remedied in the next update. The weird thing is that some projects behave like they should; Open the project Doubleclick scrollbar (x-axis) to fit in width 100% match in width But other project behave like; Open the project Doubleclick scrollbar (x-axis) to fit in width 65% to 75% match in width (or something like that) Can't figure out why this happens on some and not on other files.
Foo-Bar
Offline, Last login 3/3/2023, Member since 12/25/2022