Plugin (FX, Tran. and Gen.) Bugs and Ideas

toineenzo wrote on 12/17/2016, 9:49 AM

UPDATE: I changed the subject of this topic to Plugin (FX, Tran. and Gen.) Bugs and Ideas. You can now also talk about your ideas and bug report surrounding the Plugin Video FX Chooser, and the Media FX, Transitions and Media Generator Browser.

=====================================================================

UPDATE:

The project leader of vegas Gary Rebholz wrote:

gary-rebholz wrote on 12/20/2016, 06:34 PM

We've already got this bug in our system, but this extra discussion and detail helps. I've linked to this discussion in our notes for the issue. I hope we can get to it sooner rather than later.

So that's why I tagged that as a solution. It is being worked on...

=====================================================================

verytime I want to change the name of a Plugin in the Plugin Chooser - Video Event FX, Vegas 14.0 build 201 crashes.

I tried to change the name of 'proDAD Mercalli V4' to 'proDAD Mercalli V4 STABILIZER'

Computer specs:

CPU/Processor: Intel i5 4690k (Boxed Edition, 1150 socket @ 3.5GHz) 
CPU Watercooler: Corsair Hydro H80i 
RAM: Kingston HyperX DDR3, 16GB 2133-11 XMP-Beast 
GPU/Videocard: MSI GTX970 (NVIDIA GeForce, 3,5+0,5GB) 
Motherboard: GIGABYTE Z97x-GAMING3 (G1 Series) 
SSD: Samsung 840 EVOBasic (250GB, OS and Frequent used programs VEGAS IS INSTALLED HERE AND ALL OTHER VIDEO PLUGINS) 
HDD: Seagate Barracuda Desktop HDD ST2000DM001 (2TB)
PSU/Power Supply: Corsair CX550M 
Case: Sharkoon T28 (Blue edition) 
OS: Windows 10 Home (Genuine version :P) 
Disk Drive: ASUS DRW-24F1ST 
Wireless (WiFi) Networkcard: TP-Link TL-WN951N (300Mbit/sec) 

======================================

Vegas has stopped working:....

Extra Information
   File:                C:\Users\user\AppData\Local\VEGAS Pro\14.0\dx_video_grovel_x64.log
   File:                C:\Users\user\AppData\Local\VEGAS Pro\14.0\svfx_video_grovel_x64.log
   File:                C:\Users\user\AppData\Local\VEGAS Pro\14.0\svfx_Ofx1_1_plugin_x64-'com.NewBlue.Titler2.0' (0, Multiple Contexts).log
   File:                C:\Users\user\AppData\Local\VEGAS Pro\14.0\ocio_x64.log
   File:                C:\Users\user\AppData\Local\VEGAS Pro\14.0\dx_grovel_x64.log
   File:                C:\Users\user\AppData\Local\VEGAS Pro\14.0\gpu_video_x64.log
   File:                C:\Users\user\Desktop\Untitled.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 14.0 (Build 201) 64-bit
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 14.0\sfvstwrap.dll
   Fault Address:       0x00007FFD9B60FAE1
   Fault Offset:        0x000000000005FAE1

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 14.0\vegas140.exe
   Process Version:     Version 14.0 (Build 201) 64-bit
   Process Description: VEGAS Pro
   Process Image Date:  2016-12-07 (Wed Dec 07) 06:38:21

 

Comments

ushere wrote on 12/18/2016, 12:50 AM

why do you want to change the name in the first place?

Grazie wrote on 12/18/2016, 1:02 AM

Everytime I want to change the name of a Plugin in the Plugin Chooser - Video Event FX, Vegas 14.0 build 201 crashes.

I tried to change the name of 'proDAD Mercalli V4' to 'proDAD Mercalli V4 STABILIZER'.....

So, what's your question?

Red Prince wrote on 12/18/2016, 8:47 AM

Come on guys! If you right-click on a plug-in name in the Chooser, it pops up a small menu, one of whose options is to rename the plug-in. It makes no difference why he wants to change it, if it crashes (I did not try it, but I believe him). The point is it should not be crashing, and if it does, there is either something wrong with his system or there is a bug in Vegas. If there is a bug, I’m sure the programmers appreciate his bringing it to their attention.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

Kinvermark wrote on 12/18/2016, 4:38 PM

Wow.  It really does crash it.   It does seem  like a slightly unusual thing to do, but in principal one should not be able to force crash the program this way. 

For the OP: you should file a bug report so Magix knows about this.   As a workaround I guess you could do your naming in presets or plug-in chains. Maybe not ideal for you, but not too inconvenient.

 

NickHope wrote on 12/18/2016, 9:45 PM

Doesn't crash for me (VP14.201). It just doesn't rename it to what I type, and keeps the original name.

Quitter wrote on 12/19/2016, 6:20 AM

I've tried it, but can't also rename it.
The option appears, but nothing happens

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 11 , i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
            Vegas Pro 14.0 Build 270
            Vegas Pro 21.0 Build 300

 

Red Prince wrote on 12/19/2016, 7:43 PM

For the record, I have just tried it, attempting to change the name of a filter package, using non-English characters, running as an administrator. It worked just fine.

I then quit Vegas, waited for it to exit, then ran it again, this time as a regular user. I renamed the filter package just fine.

I quit Vegas and restarted it, then tried to rename a plug-in. Big Crash!

Extra Information
   File:                C:\Users\Adam\AppData\Local\VEGAS Pro\14.0\dx_video_grovel_x64.log
   File:                C:\Users\Adam\AppData\Local\VEGAS Pro\14.0\svfx_video_grovel_x64.log
   File:                C:\Users\Adam\AppData\Local\VEGAS Pro\14.0\ocio_x64.log
   File:                C:\Users\Adam\AppData\Local\VEGAS Pro\14.0\dx_grovel_x64.log
   File:                C:\Users\Adam\AppData\Local\VEGAS Pro\14.0\gpu_video_x64.log
   File:                D:\Adam\Documents\redhead-days.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 14.0 (Build 201) 64-bit
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 14.0\sfvstwrap.dll
   Fault Address:       0x00007FFB5686FAE1
   Fault Offset:        0x000000000005FAE1

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 14.0\vegas140.exe
   Process Version:     Version 14.0 (Build 201) 64-bit
   Process Description: VEGAS Pro
   Process Image Date:  2016-11-14 (Mon Nov 14) 20:09:00
 

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

toineenzo wrote on 12/20/2016, 10:44 AM
  • Grazie, it is not really a question but I don't know where to report bug reports, so I just post this on the forums.
  • Thank you Red Prince and Kinvermark for verifying that Vegas indeed crashes when you rename a PLUGIN. Filter packages DO work, I forgot to mention that but also thanks for verifying that Red Prince :)
  • When you change the name and Vegas does NOT crash, the name will stay the same. But that should not happen of course xD. Thanks to Nick Hope and Quitter for verifying.

 

Maybe you are probably thinking: why the hell does he want to change the display name of a plugin?!?!?!?!

Because for example: STABILIZER is easier to remember then proDad Mercalli V4 ;)

 

Maybe also a feature to add: FAVORITES! Would be really cool!!!!

 

Again, thanks everyone for replying. This was my first post so yeah.. idk k bye

set wrote on 12/20/2016, 11:21 AM

toineenzo, you can report your issue here:

https://support2.magix.com/customer/en/vegas/form

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

gary-rebholz wrote on 12/20/2016, 11:34 AM

We've already got this bug in our system, but this extra discussion and detail helps. I've linked to this discussion in our notes for the issue. I hope we can get to it sooner rather than later.

Red Prince wrote on 12/20/2016, 12:00 PM

Thanks, Gary!

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

Grazie wrote on 12/20/2016, 12:12 PM

Thanks, Gary!

Not to be churlish, but this is me 10 years ago: https://www.vegascreativesoftware.info/us/forum/is-there-a-way-to-change-the-names-of-the-fx--47427/#ca248594

Grazie wrote on 12/20/2016, 12:26 PM

Software development? Yah gotta luv it.

Red Prince wrote on 12/20/2016, 12:37 PM

Grazie, OFX plug-ins have two names, an internal name and a display name. The option to change the name of a plug-in only changes its display name. It does not affect its internal name. There should be no conflict if/when two plug-ins have the same display name. Indeed, it is quite possible for two independent developers to come up with the same display name (after all, how many unique display names people can come up with for something like a Chroma Keyer, and there are many Chroma Keyers out there). It is, however, highly unlikely for them to come up with the same internal name, at least not if they follow the convention of starting the name by the reverse of their Internet domain.

For example, one of my domains is www.pantarheon.org and if I were to write a plug-in, its internal name might be org.pantarheon.www.somethingorother (actually, I’d just use a uuid for that somethingorother part, so I wouldn’t have to keep track of the internal names of all my plug-ins).

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

Len Kaufman wrote on 12/23/2016, 11:27 PM

One good reason for changing the name of a plug-in is so that things will appear in some kind of alphabetical order that makes sense to us. I use a LOT of plug-ins, and I find it difficult to remember where they are located under their various names; names that don't necessarily tell me what I need to know, such as the example mentioned above (Prodad Mercalli/Stabilizer).

 

toineenzo wrote on 12/24/2016, 7:57 AM

That's exactly what I wanted to say Len Kaufman!

Maybe also a suggestion (@gary-rebholz) just like you can do in Windows File Explorer: show as list, icons or detailed list that you can sort.

Grazie wrote on 12/24/2016, 8:20 AM

Yes, I like that.

OK, this whole delving about, IMO, could do with some overhauling of the FX retrieval process.

There is the exsisting Searching facility that, although working, is very, v e r y slow, to the point I think it's gone to sleep. Maybe that's something else Gary can have the MAGIXies improve.

toineenzo wrote on 12/25/2016, 8:45 PM

Yes, I like that.

OK, this whole delving about, IMO, could do with some overhauling of the FX retrieval process.

There is the exsisting Searching facility that, although working, is very, v e r y slow, to the point I think it's gone to sleep. Maybe that's something else Gary can have the MAGIXies improve.

Yeah that's also a thing. I knew that you could search for video fx plugins in the explorer.

But always when I try to search, I have to pray that my vegas doesn't crash because it takes a lot of ram/cpu to search a plugin xD. Also my custom folders don't show up in that explorer. So maybe rework the search engine and add it to the Plugin Chooser just like this:..

 

I change the subject of this discussion to "Plugin (FX, Tran. and Gen.) Bugs and Ideas"

NickHope wrote on 3/29/2017, 9:48 AM

In VP14 build 244 the FX "Rename" option is now greyed out. From the release notes:

"A menu option to rename video plug-ins while in the Plug-In Chooser has been removed since the operation is not available and choosing it caused a crash"

The fact that it is greyed out and not removed implies to me that it might return to functionality at some point.