Possible V13 bug - Renaming files

Comments

NickHope wrote on 11/13/2014, 12:17 PM
I got the following reply back from SCS. I can't test anything as I'm away from my machine for a few days.

Thank you for writing back. Viewing your system information we noticed a commonality between the errors from our application as well as other applications on your system failing from the same source. Here is our information we have on troubleshooting this particular issue as the commonality is the KERNBASE module on your system.

Now I would really like to know if anyone on VP13/Windows 8.1 does NOT get a crash when renaming in-use files. Please test! It would be a shame if this got conveniently blamed on Microsoft or individual machine configuration if everyone on Win 8.1 is getting the same crash.
ddm wrote on 11/13/2014, 12:44 PM
I just tried this with no problem. W8.1, latest update (yesterday) latest Vegas 13. Hmm. Let me see if I got the test right. I dragged an mov file from the vegas explorer to the timeline, went back to explorer, renamed the file, clicked off it, to finalize it... no crash. file name change seemed to stick. Tried it again, same way, no crash.
xberk wrote on 11/13/2014, 1:58 PM
DDM Are you sure you are renaming the file within "Vegas Explorer" and not the Project Media Bin? ..

You don't need to drag anything to the timeline. Just open Vegas 13. Navigate using Vegas Explorer to some files. Attempt to rename a file in Vegas Explorer.

I think I'm on the latest W8.1 and the latest V13 .. still getting a crash when renaming files in Vegas Explorer.

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

ddm wrote on 11/13/2014, 2:42 PM
I was in the Explorer and not the Media bin, just tried it again, two different times, no crash.
NickHope wrote on 11/17/2014, 1:56 PM
xberk, I'm also finding that the file doesn't have to be in use. Just renaming a file in the Vegas Explorer window causes the crash, even if it's not in use by Vegas.

Also, the file does actually get renamed despite the crash.
NickHope wrote on 11/17/2014, 2:08 PM
Also I've just noticed that if I execute the filename change by clicking on another file in the Vegas Explorer window, instead of pressing <ENTER>, it doesn't crash.

But it still crashes sometimes if I click in empty space in the Explorer window to execute the change.

Pressing <ENTER> always makes it crash.
xberk wrote on 11/17/2014, 2:45 PM
Nick .. I see the same behavior. That's a good work around to execute the filename change by clicking on another file in Vegas Explorer. Terrific.

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

ddm wrote on 11/17/2014, 3:07 PM
>>>Also I've just noticed that if I execute the filename change by clicking on another file in the Vegas Explorer window, instead of pressing <ENTER>, it doesn't crash.

So I guess that's why my tests weren't crashing. I also tried right clicking and choosing "rename" and then renamed the file followed by the enter key and that didn't crash either.
ddm wrote on 11/17/2014, 3:10 PM
I just tried it again and it seems to only crash if you click on some blank space in the explorer window, if I click on the timeline after renaming it's fine. Odd.
NickHope wrote on 11/26/2014, 12:12 AM
VP13 build 428 still has this problem.
NickHope wrote on 12/12/2014, 10:51 PM
I had a reply back from SCS that includes this...

"Because this incident involves very detailed technical aspects of the programming and design of our software, I will be consulting with our Development and QA team to try and resolve this issue.
john_dennis wrote on 12/14/2014, 9:58 AM
I just tested this on two separate machines running Windows 7 Professional 64 bit and Vegas Pro 13-428. I was able to rename the files without incident multiple times. I hit the Enter key and I clicked in an open space in the Explorer window.

I have the Problem Step Recorder output files if anyone wants to see a successful outcome.
NickHope wrote on 12/14/2014, 11:52 AM
Thank you John. I will suggest that to SCS.

So far, we have 4 crashers, all on Windows 8.1, and 3 non-crashers, all on Windows 7.
NickHope wrote on 12/22/2014, 9:20 PM
I has a reply from SCS support that included this:

"Our developers and QA team were able to reproduce the issue and will be working to resolve this issue in a future update of the application."
hollyviewvideo wrote on 2/11/2015, 9:16 PM
Same issue here. I started reporting this to Sony right after I noticed they had used a completely different Windows explorer UI control in V12.

In V11, the UI control is completely different and renaming files in V11 works flawlessly.

I also got a response from Sony that they had no interest in fixing this bug that I encounter 30 times a day.
NickHope wrote on 2/11/2015, 9:33 PM
I had a thought yesterday that perhaps this bug is related to the routine that automatically renames the .sfk etc. files after the media file has been renamed. I wouldn't be surprised if that got overlooked when the updates were being coded.

Unfortunately I can't easily report this hypothesis to SCS as the support ticket is closed and marked as solved.
NickHope wrote on 4/7/2015, 2:12 AM
This bug still exists in VP13.0 build 444
NickHope wrote on 8/6/2015, 5:54 AM
Bug still exists with Windows 10, in case anyone wondered.
NickHope wrote on 9/20/2016, 2:44 AM

This bug is fixed in VEGAS Pro 14.0 (Build 161). Thanks!