Why can't I open a *.ts file in Vegas Pro?

Christian de Godzinsky wrote on 4/7/2011, 11:01 AM
Hi,

It's a while ago - but in my opinion I have done this before:

I have .ts file (PAL SD) that at least Windows Media Player, VLC player and Badaboom happily opens. In my opinion I have before imported *,ts files to the Vegas Pro timeline...

All Vegas versions VP9 and VP10 (32 and 64 bit) refuses to open this file. They just bluntly give the error "..the file could not be opened"... not very much informative...

The file resides on one of my internal SATA HD's and the file is not write protected... Again, the other programs opens it without a hinch.

Why is this a problem for Vegas - come on -the import file list types include .ts files !!!??? Shouldn't it be able to do this?

What am I doing wrong? Or is it Vegas to blame?

Cheers,

Christian

PS: Running on WIN7 Ultimate 64 bit with all latest Vegas updates...

EDIT: Any news from NAB about VP10d ????

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

Comments

Former user wrote on 4/7/2011, 11:11 AM
Is it a video.ts folder or a transport stream file?

Normaly a video.ts folder is on a DVD and contains VOB files.

Dave T2
Christian de Godzinsky wrote on 4/7/2011, 11:15 AM
Hi,

Its a transport stream file with the name "xxxxxx.ts"

I'm totally confused... This file was captured from a DVBT television transmission in a recording digital receiver box... The size of the file is 1.8Gbyte...

Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

Former user wrote on 4/7/2011, 11:16 AM
try changing the extension to .mpg and see what Vegas does.

Dave T2
musicvid10 wrote on 4/7/2011, 11:41 AM
Christian,
PVR files of any type usually contain indexing errors due to transmission.
Just renaming or remuxing the files to ps will not re-index the GOPs.
Use the trial version of VideoRedo (run "Quick Stream Fix") on your files and see if that makes them work in Vegas.
ritsmer wrote on 4/7/2011, 12:41 PM
Tried to drop a .ts file onto an 10.0c 64bit timeline and it worked well.

According to Mediainfo it is a: MPEG HDV 1280x720p at 18.3 Mbps constant rate and 29.970 Fps file - but .ts files can be many things ...
Christian de Godzinsky wrote on 4/7/2011, 12:55 PM
Hi,

This .ts file is a plain vanilla MPEG-2 TS Video having a frame size of 720 x 576, 25 frames sec (PAL - interlaced). Video data rate is 8400kbps and total bit rate 8624 kbps. Funny, no Vegas version (9, 10 can open it. Still the same file works like charm in other applications. And plays just fine without any dropouts in Windows media player and VLC.

I was able to convert the file with handbrake to a mp4 video file, that Vegas opens and plays gladly.

I didn't know that Vegas is this picky... This is in my opining just an example of bad or sloppy coding. There might be something wrong with the file (taking in consideration it was recorded over air), but at the same time other applications opens, converts and plays it just fine. My finger points in the Vegas direction... Sad that a professional tool is this "flimsy"...

Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

john_dennis wrote on 4/7/2011, 3:03 PM
Look at this thread

musicvid has given you the correct answer.

Though it would be nice if Vegas had the ability to open files from ATSC and DBS transport streams, I disagree that not doing so represents "bad or sloppy" coding. I don't see that as a necessary part of a professional workflow where most acquisition is from cameras. VideoReDo corrects the indexing errors that musicvid described and it also allows you to select the correct stream if the source was multicasting multiple video and/or audio streams.
I do this every day with ATSC files and I've never had a capture that I couldn't edit in Vegas after preparing the source video files with the tools described in the thread above. I have had files with so many errors that I didn't think it worth the trouble. Never had the pleasure of capturing DVB-T.

P.S.
If you search my posts back far enough you might find a rant of mine that sounds just like yours.
Good luck.
jabloomf1230 wrote on 4/8/2011, 1:34 PM
Usually, most software will read a ts file, if you just change the file qualifier. If not, there's always HDTVtoMPEG2:

http://www.videohelp.com/tools/HDTVtoMPEG2
Christian de Godzinsky wrote on 4/8/2011, 11:35 PM
Thanks to you all for good ideas and advice. If I want to use this .ts file in Vegas I need to use some of the "tricks"...

I still wonder my I have to convert a .ts file to open it in Vegas - that should work with .ts files directly. Especially if this same file opens fine in all other applications....

Everyone brags about Vegas being the Swiss army knife (you can do most things within), but in reality you need lots of support applications (handbrake, hdtvtompeg, cineform, hdv capture etc etc) just to support the basic functionality in Vegas...

I don´t think that I´m completely wrong claiming that there is something more fragile in the Vegas .ts file decoder - than in other application´s decoders...

Take this as constructive criticism, I would like to see such annoyances getting fixed...

Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

PeterDuke wrote on 4/9/2011, 1:30 AM
"Usually, most software will read a ts file, if you just change the file qualifier. If not, there's always HDTVtoMPEG2:"

Quote from
http://www.avsforum.com/avs-vb/showthread.php?s=&threadid=395744

"I think the transport stream to program stream conversion was broken with newer versions of HDTVtoMPEG2. There are probably better programs to use for that. (X-Muxer or VideoReDo?)"
PeterDuke wrote on 4/9/2011, 1:39 AM
AVS Video Remaker will convert .ts to mpeg. The trial version works for short clips without watermarks, etc. It probably won't repair any transmission errors, but I am only guessing. VideoReDo is the one to use in that case.
Christian de Godzinsky wrote on 4/9/2011, 1:51 AM
Peter,

Yes, I changed the qualifier to many different - but no luck in Vegas (other applications still opened it OK).

And, Vegas IS supposedly to open .ts files - or not? If there are variations in .ts files that Vegas cannot accept, where do I find info about such?

Thanks again for you encourage :)

Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

PeterDuke wrote on 4/9/2011, 2:20 AM
"And, Vegas IS supposedly to open .ts files - or not?"

I don't recall seeing any such claim. Have you? The web specifications and the manual seem silent on the matter.

EDIT

I was able to import a .ts file into Vegas 9. I can only think that since .ts is only a container specification, the problem is the video format. See if Mediainfo tells you anything amiss.
JJKizak wrote on 4/9/2011, 5:09 AM
I have imported them by changing the file ending to mpg. These were files from the My HD Tuner card.
JJK
john_dennis wrote on 4/9/2011, 10:06 AM
I still wonder my I have to convert a .ts file to open it in Vegas - that should work with .ts files directly.

Learn more about transport streams and you'll be less inclned to expect Vegas to handle all the variations. This paper covers many of the points though it was written to sell a product. I suspect the characteristic of your stream that causes you the hangup is multiple streams and/or data types. Try tsMuxer, select the video and audio stream that you want to edit and remux to m2ts. If there are no transmission errors you may get a good editable file without VideoReDo.
PeterDuke wrote on 4/9/2011, 4:42 PM
Do you have Quicktime installed? It is necessary for .MOV and ,MP4. Perhaps your .ts file does not have MPEG2 encoding. Mediainfo will tell you.
richard-courtney wrote on 4/9/2011, 8:00 PM
Your saves transport stream most likely has 2 or more programs multiplexed
into one. I use tsreader to split the streams into separate files.

http://www.tsreader.com/legacy/

Download the free version to see if this is the case.
Then make your decision on the pay versions.
jabloomf1230 wrote on 4/10/2011, 9:02 AM
In any case, these conversions are quite fast, since you are only changing the wrapper and there is no transcoding.