VSP Pro X2 file format

Moderator: Ken Berry

Post Reply
mcam
Posts: 7
Joined: Sat Dec 05, 2009 3:24 pm
operating_system: Windows 7 Professional
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: ASUSTeK P5KPL-SE
processor: Intel Core2 Quad Q8200
ram: 4GB
Video Card: NVidia GeForce 9600 GT
sound_card: external Z-10 USB speakers
Hard_Drive_Capacity: 2x4TB
Location: Malta

VSP Pro X2 file format

Post by mcam »

Does anyone have any information about the internal format of a VSP file? I have some Videostudio Pro X2 projects containing hundreds of MPG clips which I need to relink to MTS versions of the same clips. I can of course do this manually, but that's very laborious. What I would like to do instead is to write a program which scans a VSP file and changes all clip references. I have already tried doing this by scanning the project file and changing all extensions in the clip references from MPG to MTS, but this didn't work - evidently there is more to it. Any suggestions anyone?
User avatar
Ron P.
Advisor
Posts: 12002
Joined: Tue May 10, 2005 12:45 am
operating_system: Windows 10
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: Hewlett-Packard 2AF3 1.0
processor: 3.40 gigahertz Intel Core i7-4770
ram: 16GB
Video Card: NVIDIA GeForce GTX 645
sound_card: NVIDIA High Definition Audio
Hard_Drive_Capacity: 4TB
Monitor/Display Make & Model: 1-HP 27" IPS, 1-Sanyo 21" TV/Monitor
Corel programs: VS5,8.9,10-X5,PSP9-X8,CDGS-9,X4,Painter
Location: Kansas, USA

Post by Ron P. »

That's really unknown. VSP files are similar to text files, however they are compiled and contain whatever Corel uses for it's programming language. You can try looking at one, opening it with Notepad, to see if you can determine what is being used.
Ron Petersen, Web Board Administrator
mcam
Posts: 7
Joined: Sat Dec 05, 2009 3:24 pm
operating_system: Windows 7 Professional
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: ASUSTeK P5KPL-SE
processor: Intel Core2 Quad Q8200
ram: 4GB
Video Card: NVidia GeForce 9600 GT
sound_card: external Z-10 USB speakers
Hard_Drive_Capacity: 2x4TB
Location: Malta

Post by mcam »

Thanks. As you say, that's unknown, but not unknowable. I'm only interested in the parts of the VSP file which reference clips (I'm not interested in the project header or in how the transitions are coded etc.) What I have so far is that for each clip the absolute path to the file is stored as a pascal-style string (length byte first). This is then followed by a 32-bit field recording the length of the file, followed by another 32-bit field (or a pair of 16-bit fields) the function of which I haven't yet determined, but may be a checksum of the clip being referenced. These seem to be the only bits I need to change to relink my projects programmatically, if I can work out the function of the 32 bits of data following the filelength field.
Trevor Andrew

Post by Trevor Andrew »

Hi

If your original Mpeg files have the same names as the MTS files then they should re-link.
In addition they have to be the same length, if not longer. Shorter files will generate an error.

With the MTS files in a different folder to the Mpeg files. (I assume they are)
Re-name the Mpeg folder, simply add a suffix ¡¥a¡¦

Opening the project will force a re-link, navigate to the MTS file of the same name.
All files within that folder should re-link.

Best to make a copy of your project file before starting the process.
Post Reply