595 Muscles-In on V10e Parent?

Grazie wrote on 3/8/2012, 5:05 AM

VP11 - 595 jumps into the Nest Operation when using VP10e Parent.

I've got a PAID-for job.

It was created in VP10e and I have Nests within a MAIN Parent Veg.

I Right Click on a Nest, and select "Open Veg XXXXXXX" and what I get instead is V11 595 opening it, and not VP10e.

Bizarre.

To recap:-

* V11 595 insists on opening a previously created, and functioning, nested V10e Project.

* This most definitely did not happen in previous V11 Builds.

* To get around this I am needing to open the Nest separately outside of the Parent VP10e project; do my editing within VP10e; save, and return and wait for the updating to happen.

Could somebody attempt to repro this?

Grazie

Comments

farss wrote on 3/8/2012, 5:24 AM

I think your problem lies inside Windows file associations.
If I associate .VEG with Vegas 11 not matter which version of Vegas I open a parent with when I try to edit the child from within the parent V11 opens.

Probably somewhere in the install of the upgrade you let the installer modify your Windows file associations.

Bob.

Grazie wrote on 3/8/2012, 5:46 AM

Bob, thanks for taking an interest, but read on . . . .

I think your problem lies inside Windows file associations.
How? Read on . . . .

If I associate .VEG with Vegas 11 not matter which version of Vegas I open a parent with when I try to edit the child from within the parent V11 opens.
Not had this with 521? 521 allowed me to work in VP10e from a nest from within VP10e. Any way, WOULDN'T a User want to associate Veg with Vegas? Stands to reason - no? But the CORRECT version of Vegas. Now, how Vegas discerns ONE edition form another edition of Vegas - in terms of Nesting - is well above my pay grade. I'm a User.

Probably somewhere in the install of the upgrade you let the installer modify your Windows file associations.
How would I "let" it do that? I don't see an option?

OK, I'd quizzed the Windows Associations menu and have SEEN that VP10 is bizarrely associated with VP11 and have then MANUALLY changed it and SAVED. However, the issue remains.

What next? Stronger Medication?

G

farss wrote on 3/8/2012, 6:29 AM

"How would I "let" it do that? I don't see an option?"

Everytime I open a version of Vegas that is not the one associated with the .VEG file extension it asks me if I'd like to change the file assocaiions. Click Yes once by mistake or just hit the Enter and that's it.

"OK, I'd quizzed the Windows Associations menu and have SEEN that VP10 is bizarrely associated with VP11 and have then MANUALLY changed it and SAVED. However, the issue remains."

Now I or you or both of us are confused.
Windows associates an application with a file type, the file type is determined by the file extension. WIndows knows nothing about which version of Vegas created the project file and I've never known Vegas to be savvy enough to work this out when it opens a .Veg file or open an external editor. It just asks windows to do it.

So what you should look for is which application is associated with the .VEG file extension. Because all version for Vegas have the same file names (Vegas.exe) you have to specify to Windows the full path to get this right.

Having said all that I think you've found a nasty problem and worse I cannot figure out how to fix it.

I have Windows file assoc set to .veg = Vegas 10 and that works, click any veg and V10 opens.Click any nested and it used to open V10.

However to help you out I opened V11 build 425 and clicked that Yes button.

Now (drum roll) clicking a veg from win explorer still fires up V10. Selecting the edit nested with Vegas menu option in BOTH V10 and V11 opens it with V11.

I've checked all the prefs and the internal ones I cannot find where Vegas is hiding this info, WIndows has the right links but V11 should have changed that and it didn't, wierd, really wierd.

Bob.

[edit]

I fixed it, on my system at least. I opened V10 and clicked Yes in the box as shown above and now from V10 the child is opened by V10, phew.

Just checked with V11, it too now opens with V11.

Try doing the above.

amendegw wrote on 3/8/2012, 7:00 AM

The Windows way....

...Jerry

Grazie wrote on 3/8/2012, 8:33 AM

Jerry, when I RightClick on Vegas100 (that's VP10) I don't get the "Open With " option at all.

G

Steve Mann wrote on 3/8/2012, 9:18 AM

Make sure that you aren't trying to right-click on the desktop shortcut.

Grazie wrote on 3/8/2012, 9:38 AM

Thanks Steve. No, I'm doing this in WinExpl.

G

Kimberly wrote on 3/8/2012, 9:55 AM

For what it is worth, I cannot replicate this error. Window 7 32-bit. Vegas Pro 10e Build 737. Vegas Pro 11 Build 594.

First I opened Vegas 10. I received the prompt about associating *.veg files with Vegas 10. I chose "Yes." I closed Vegas 10. Then I opened Vegas 11 and received a similar prompt about associating *.veg files with Vegas 11. I chose "No."

Next I created a new Vegas 11 project and nested a Vegas 10 project. I right-clicked the nested Vegas 10 project and chose "Edit in Vegas." The project opened in Vegas 10e Build 737.

Maybe the above issue affects only the 64-bit version?

Regards,

Kimberly

ForumAdmin wrote on 3/8/2012, 10:30 AM

Grazie et al: I have a repro on one machine, and we're looking into it. I'm not sure what's causing this just yet, since the Windows file associations are correct. I will let you know as soon as I learn more. Thanks,

Paddy
SCS

Grazie wrote on 3/8/2012, 1:01 PM

Paddy thanks for the update.

Cheers

G

amendegw wrote on 3/8/2012, 1:33 PM

"Jerry, when I RightClick on Vegas100 (that's VP10) I don't get the "Open With " option at all"Heh, that's 'cuz you right click on a .veg, not the .exe (I'll redo the above image with bolder text). In other words, you want to associate the extension with an executable - not the other way around.

Although, in reading thru the subsequent posts, I'm not sure I understand your problem. I read it as you want to switch the Vegas version associated with opening a .veg. If that's not correct, ignore me!

...Jerry

farss wrote on 3/8/2012, 1:34 PM

"when I RightClick on Vegas100 (that's VP10) I don't get the "Open With " option at all"

Why would you?
Vegas100.exe is an executable, it opens files, files don't open it.
You have the whole concept the wrong way around.

Right Click a xxxxx.veg file, then you get the Open With option.
You get that because it isn't an executable (program) file, you're telling Windows which program to open the file with.

Bob.

Grazie wrote on 3/8/2012, 2:25 PM

Thanks for the instruction Bob. Much appreciated.

G

amendegw wrote on 3/8/2012, 2:29 PM

"Thanks for the instruction Bob. Much appreciated."Ahhh, the guy that posts 32 seconds later gets all the praise [chuckle]

...Jerry

Grazie wrote on 3/8/2012, 2:41 PM

Just so you both know, my thoughts were along the same lines; I wanted to associate Vegas exe with veg files. Of course I did.

And Jerry, you are still correct, I wanted to associate Vegas exe with my veg made in VEGAS 10.

G

farss wrote on 3/8/2012, 3:08 PM

"Ahhh, the guy that posts 32 seconds later gets all the praise"

Don't worry, I gotta go to a real job now.
Grazie is all yours, I'm sure he's in good hands :)

All that said I think something is messed up in V11, I suspect it has been messed up before the current build too. I really don't have the time to get to the bottom of it though at the moment. I think from my very quick test that the Vegas method will get Grazie back to sanity unless there is something extra messed up in the latest build.

Bob.