I found, the learning curve is significant for the Pro Titler. Also, I discovered my video card was not to par. Upgrading my video card stopped the crash/lag problems. Spend some time just playing with the Titler, inside Vegas, without needing a specific project completed. This helped me the most.

Thank you both.

I suggest you watch some tutorials on how to use the software. If you used the standalone, did you set the timeline settings to match your video? As for the created MOV file, Vegas imports them just fine. A screenshot of the error message you receive would be more helpful...

@Reyfox

I suggest you watch some tutorials on how to use the software. If you used the standalone, did you set the timeline settings to match your video? As for the created MOV file, Vegas imports them just fine. A screenshot of the error message you receive would be more helpful...

The error message I got was "Warning: An error occurred while opening one or more files. The file is in an unsupported format." I think the reason for this was I have to turn it on in deprecated features like @jetdv said. Still seems strange though because I have Vegas 365 and often use the stock footage included, some of which is in .mov format, and I can't recall having problems when using that. I couldn't seem to find any settings at all in the standalone beyond rendering quality and a couple others. Nothing that seemed to address the timeline anyway.

I think my problem was I was trying to use it through the video fx tab rather than the media generator tab, which launched the stand alone. When I tried again via the generated media tab I was able output directly to the vegas timeline. Here's a screenshot of the importing .mov file error.

@Ardat, it all depends on what's "inside" the MOV file. MOV is like a paper sack, you can put many different things in it. But what it contains determines what is needed read the file. In the case of PNG Sequence files, Quicktime is required and, to use Quicktime, it must be turned on in the deprecated features.

To read a ProRes MOV file, VEGAS will read that natively so nothing else needs to be turned on. The stock footage you are using must be using a format that VEGAS can read natively without needing Quicktime.

The same is true with other file formats. AVI, MP4, etc... can contain many different formats of files. That's why if someone says a file can't be read, the next question is - what's in the file? And if they answer "It's an MP4 file", that doesn't answer the question.

Here's the difference between the Media Generator and VideoFX and Standalone:

1. The Media Generator version gets added as a new event on the timeline allowing you to easily adjust the length of the event and place it over one or more media events.
2. The VideoFX version gets added as an EFFECT. This will limit it to the scope of the effect. If you add it on an event on the timeline, it is limited to that event. It DOES have the advantage of being able to show the underlying video in the Titler Pro timelilne. However, if you were to drag the VideoFX to a track like you would the generated media, it will apply as an EFFECT to that TRACK - probably not what you want.
3. Both Media Generator and VideoFX will automatically open the Titler Pro 7 interface. This is NOT the "standalone" version although the interface will look the same as the standalone version. Once the changes to the title are made, you simply need to close the Titler Pro interface and confirm you want to keep the changes.
4. To open the "standalone version", you simply need to run Titler Pro outside of your NLE. You can do that by using the Titler Pro 7 icon or open the App Manager and clicking on Titler Pro or TotalFX there. When Titler Pro is open in standalone mode, you can still create titles but will need to save them as a .nbtitle file. Once back in your NLE, add Titler Pro to the timeline and you can then open that .nbtitle file to add it to your timeline. You cannot open a .nbtitle file direct on the timeline.

@Ardat thanks for the screenshot. To see what the file is (maybe give the information of what created it), you can use MediaInfo. It's free. Run it, click on View>Tree, drag the problematic clip on top of it, screenshot and add it to your post.

Or, if you can supply a sample of a problem file to the cloud to be downloaded, I'll give it a shot.

Thank you, that's a lot of good info.

@Ardat I see you marked @jetdv as the Solution. Glad you got it sorted out.

@Ardat thanks for the screenshot. To see what the file is (maybe give the information of what created it), you can use MediaInfo. It's free. Run it, click on View>Tree, drag the problematic clip on top of it, screenshot and add it to your post.

Or, if you can supply a sample of a problem file to the cloud to be downloaded, I'll give it a shot.

Looks like a PNG sequence, but also says it is MP4? Screenshot attached.

@Ardat, it all depends on what's "inside" the MOV file. MOV is like a paper sack, you can put many different things in it. But what it contains determines what is needed read the file. In the case of PNG Sequence files, Quicktime is required and, to use Quicktime, it must be turned on in the deprecated features.

To read a ProRes MOV file, VEGAS will read that natively so nothing else needs to be turned on. The stock footage you are using must be using a format that VEGAS can read natively without needing Quicktime.

The same is true with other file formats. AVI, MP4, etc... can contain many different formats of files. That's why if someone says a file can't be read, the next question is - what's in the file? And if they answer "It's an MP4 file", that doesn't answer the question.

This is interesting to me because I was always told that .mkv worked in a similar way, and was why it was often referred to as a "container" as opposed to what .mp4 was considered. But I guess they are more similar in this way than I thought.

Thank you both again, I am learning a lot.