[Tyson Onaga]

Thank you John.

I always change the name, normally prefix with my initials. Since they’re saved in:
…AppDataRoamingSonyRender Templates

it is easy to find the ones I’ve mucked up.
I assume the VAAST templates were added when I installed Production Assistant. Very nice and handy (btw) …

[Tyson Onaga]

Click-drag on the five vertical dots to undock the window.

[Tyson Onaga]

OK, now I’m a little confused:

[James Dubendorf] “My understanding is that the computer to studio conversion must occur regardless of whether the file is destined for broadcast, DVD, bluray, or most web streaming. Even though computers work in 0-255, almost any way of streaming video requires the file to be in 16-235. The goal, therefore, is to have the colors you see in the Vegas preview window be essentially identical to what you see on youtube or vimeo. ”

[John Rofrano] […snip…] The problem is not so much Studio RGB vs Computer RGB. The problems is that video sites like YouTube and Vimeo boldy assume that your video is Studio RGB so they BLINDLY (and sometimes wrongly) convert all videos from Studio RGB to Computer RGB whether they need the conversion or not. In effect, what you need to do always make sure that you supply sites like YouTube and Vimeo with Studio RGB video even if your video is Computer RGB already because they will convert them whether you like it or not. That is different from using a streaming site that does not blindly convert, in which case you should deliver Computer RGB video.

and from this thread: https://forums.creativecow.net/thread/24/939771

[John Simmons] “Do I need to apply the Sony Levels Studio RGB to Computer RGB?”

[John Rofrano] The answer unfortunately, depends on what codec you are using. If you render to Sony AVC using one of the Internet HD … templates, then you don’t need to do anything. The Sony AVC codec assumes you are feeding it Studio RGB and it will convert it to Computer RGB for you. So you don’t have to do anything. I’m not sure about MainConcept AVC because I don’t use it much. The bottom line is to feed the codec what it expects.

And Glenn Chan’s article: https://www.glennchan.info/articles/vegas/v8color/vegas-9-levels.htm

From this, to create a video for YT/Vimeo, I would place the Sony Color Corrector on the Main Video Bus and set it to Computer RGB to Studio RGB.

1. So will the Sony AVC renderer convert it back to Computer RGB?
2. If it does, wouldn’t that contradict the objective above (to supply YT/Vimeo with a Studio RGB video)?

I’m relying on the wisdom of John and Glenn (and other like them) here …
Thanks.

[Tyson Onaga]

If you ever get the “unable to disconnect …” some drive but you don’t know who’s holding on to a file on that drive, use the tool Unlocker. CNET review is here:
https://download.cnet.com/Unlocker/3000-2248_4-10493998.html

Unlocker (say you pick drive H:) will show you all processes that have open handles to that drive. You can close the app(s) in question (eg, you forgot that you’ve got Excel open with an xls from that drive), or have Unlocker free the resource. I’ve seen Sony’s File I/O Surrogate hanging around (via Process Explorer) even though Vegas itself is not in memory. You can use Unlocker to unload and thus free the file handles that prevent Windows from allowing you to disconnect the drive.

As John said … NEVER EVER disconnect a drive that Windows thinks is “in use”. The only things that can happen are almost all BAD.

[Tyson Onaga]

If true, the second to last paragraph:

https://www.ripoffreport.com/video-film-production/videoblocks-com/videoblocks-com-footage-firm-d-8b6e3.htm

does not sound good for the customer …

[Tyson Onaga]

From your image, you have two instances of Vegas running. If you don’t see two copies of Vegas in your task bar, something’s wrong (i.e., one of them has crashed; you don’t have a UI to interact with but it is still resident in memory).

If you have had any applications shut down abnormally or if Windows blue-screen-ed on you, I’d run a HD scan. Open a command box and type:
chkdsk c: /v/f

Check each HD you have.

Reboot. Start a fresh copy of Vegas. Process Explorer should only show one instance of Vegas. Create a new project and insert one of your previously used avi or wmv files. Save the project. Close and reopen it. You shouldn’t have any problems.

Open one of the projects that you had a problem with. Any problems? If you do, open one of your backups (you did make backups, yes!?) to see if it is the file or some changes you made since your last “edit”.

BTW … I’ve also seen Vegas die where the splash screen is up and it is on the “File I/O …” initialization. In those cases, I’ve found “oprhaned” File I/O Surrogate.exe hanging around (using Process Explorer). When I kill them and Vegas, a restart of Vegas almost always succeeds.

[Tyson Onaga]

I’ve seen Vegas 8.x, 10.x have the same issues. Whenever FileIOSurrogate.exe (from Sony) has a problem it appears to be a HD issue which is the common cause.

First, I’d get Process Explorer from SysInternals.
https://technet.microsoft.com/en-us/sysinternals/bb896653

This can show you all the process, subordinate DLLs, threads, etc. … more detail than you can throw a stick at. You can easily see if Vegas or something spawned from Vegas is “dead”. You can then kill Vegas from here.

Second, I’d run a HD scan on your disks.
chkdsk [dr:] /v/f

should suffice.

[Tyson Onaga]

If you’re asking how to move the images, you can use Track Motion or Pan/Crop. If you use Track Motion, then you can still use Pan/Crop to zoom in/out of the image while it is rotating. Track 1 would have an image moving clockwise; track 2 counter-clockwise. Use Properties, Media, Alpha to enable the alpha channel.

Formats with alpha are .avi uncompressed, .mov animation, and .mov PNG.

But I’d take Matt’s suggestion and nest this project into your parent project(s). That way, any changes to the child project are reflected in the parent project immediately and it doesn’t require another intermediate render step and subsequent replacement in the parent project.

[Tyson Onaga]

As there is no API to the Sony Text objects, a “workaround” is the best you can do. I’d make a test .veg with 2 or 3 PTT objects. Run through the steps above and see if you find the 2 or 3 “span” statements with your text strings.

If so, then the next step would be to write a Word macro (in VB) that would start at step 6 and automate the rest. You would use Word to find the
<spans text=
statement, then
– copy the text string
– add it (eg) a second Word document
– find the next spans statement (or stop)

When the macro is executed, you’d have a document with just the text strings … which should be your PTT text strings.

[Tyson Onaga]

I know of no way to easily get the text out of Sony Text objects from within Vegas. However, if you have all ProType Titler objects, you can:

1. COPY the .veg file
2. Start Word
3. File Open
4. In File of Type, scroll down and select: Recover Text from Any File
5. Select the COPY of the .veg file

Word will then extract the text. Your PTT objects should show up as XML blocks.

6. Select All
7. Edit Replace (Ctrl H)
8. Replace ^p^p with ^p (double paragraph with single paragraph)

This should remove “blank lines”.

9. Select All
10. Copy
11. Run Notepad
12. Paste

I see this block
twice in Notepad. You probably need only one (ie, hand-editing).

13. In Notepad, search for: <spans text="

The value(s) within the double quotes should be your text strings.
Collect them and copy to your EM.