Thanks for confirming that. If possible please file a ticket. I'll try the minimizing work around but usually the way I work is back forth between photoshop and Vegas. I'm also experiencing strange issues with Sound Forge 9 and Vegas 12. I usually have to close SF after returning to Vegas in order for Vegas to recognize the audio changes.

this is a pain... i have to close vegas completely..no problem in vegas 10..just with 12 and cs5

I'm not in front of Vegas at the moment, but isn't there a setting in Options / Preferences about Vegas releasing files? I don't remember what it's called or what to look for, but I seem to recall there's a setting like this. Maybe it's set differently in 12 than in your other versions?

Or it could be a bug, there's always that....

It is your own choice:

Preferences, General : ( ) Close media files when not the active application.

Something is wrong with Vegas 12 not letting go of files properly.

I have this working fine in Corel>PSD File import to VP12 and then alter in Corel then Save. I am using the Open in Graphics Editor script by Rosebud. Holding together here.

Could it be a PS thingie?

Cheers

G

...........Preferences, General : ( ) Close media files when not the active application.


no working here...works in 10 not 12

Sorry to be no help, but V12 & photoshop work on my system. I use the open in image editor script with V12 & PS & it just works. Hopefully, that gives you hope in fixing this problem.

It works for me in Pro 12 too. I find that sometimes I have to switch back to Vegas and take focus off of the event that I opened in Photoshop (click anywhere else) but otherwise it's fine.

Mike

I'll throw in my 2 cents---I don't usually select the "Close Media Files" option because (if the files within Vegas aren't changing) it can dramatically slow down the time Vegas gets ready to work when you click off and back to it. But when I do, and if I'm using Photoshop to fiddle with a graphic, quite often during the switch between Vegas & Photoshop the file becomes marked as busy elsewhere and unable to be saved. Once the file becomes marked this way, I usually quit Vegas, then open Task Manager.

In Task Manager I can see whether or not Vegas is still running and exerting control over the file. Vegas can appear in the Processes tab for a long time (45 seconds) after I close it, which can cause confusion in "ownership" of files. This behavior seems to compound when I open multiple instances of Vegas---usually one of them crashes, which doesn't help matters either.

I thought this was fixed in the latest version but it's not. Sometimes it works but most of the time it does not. Please file a bug report with Sony if you're having this issue.

OK . . . I've got an anomaly that I don't remember happening before: I can now no longer treat the separate "layers" now Event on its own Tracks with any movement like Rotation in either Pan/Crop or Track Motion. I defintiely could before. Also changing the "layer" in Vegas breaks the link back into Corel.

Yup, I got it now.

Here's a (yes, badly rendered from me, from my WMP file) multi-layered PSD (PSP<>Vegas) I did in previous version of VP. And this worked.......

That's great Grazie - sorry it's not yet working in V12.

I hadn't realised how effective this is as a way of animating the layers of a still and finishing with the still Logo - a multi level transition.

Thank you Peter.

It's a great Creative way to utilize Vegas. This plus using the Compositing Layers. When this came avaible for Vegas I really saw an opportunity to treat Vector layer in VP as I would in Corel<>PSD.

I hope the engineers can reclaim the territory around this.

Grazie

@ Grazie

Love the music.
What is it?

Ah man, my brain hurtz . . . one of my Royalty Free vendors? OR it could have been a Cinescore slap?

G

I sent my results on this issue to SCS. I hope that helps them.

Cheers

Grazie

Ok Grazie :-D. No title on the track eh?

No title on the track eh?

Let me "investigate".

G

Thanks :-D.

Just had another round with tech support and they have confirmed the issue.

Hi Marc,

Thank you for writing back. The developer I have been working with has responded saying that this is a known issue and that it has been submitted to be fixed in a future release of the application. Apologies for the inconvenience and be sure to keep an eye out for future updates.