Vegas 21 Issues loading m2t (HDV files)

steve-medley wrote on 12/30/2023, 8:02 PM

Hi All

Have recently upgraded to Vegas 21 from 20 and the following problem has arisen. When I select an m2t file to drag onto the time line in VP21 it just freezes for a couple of minutes and then fails the drag request. Do the drag again it works fine.

When you close VP21 and restart the same failure happens and repeat the process and it works fine.

If i was a betting person I would hazard a guess that the first time I select the M2T file, it is registering the codec silently and subsequent drags work fine until you close VP21 and restart.

MP4 files work fine, have not tried MOV files yet.

I have never had this issue for VP 20 and Prior and any suggestions would be greatly appreciated.

Steve Medley

OS Win 11, 32 GB ram and all drives are SSD

Comments

mark-y wrote on 12/30/2023, 9:24 PM

Unusual, because I assumed the versions use the same decoder.

Look at the Vegas File properties, and compare the decoder versions like this:

NickHope wrote on 12/30/2023, 9:29 PM

m2t HDV files in my VP20 and VP21 are both using compoundplug.dll and files decode on the timeline pretty quickly.

steve-medley wrote on 12/30/2023, 10:02 PM

Thank you both for the comments

I feel there is an issue with the compoundplug.dll that was deployed with FP21

For my version of FP 18

and from FP21

Note the differences in the DLL

john_dennis wrote on 12/31/2023, 1:08 AM

@steve-medley said: "Note the differences in the DLL"

The only difference I see is the Version and Build. Even if the code doesn't change, I suspect Vegas 21 will show that the .dll belongs to that release.
I don't have an issue with the .M2T files that I have available to me.

General
  Name: MPEG-2 Source - 1.m2t
  Folder: C:\Users\John\Desktop\M2T
  Type: MPEG-2 Transport Stream
  Size: 70.02 MB (71,702,260 bytes)
  Created: Saturday, December 30, 2023, 10:21:18 PM
  Modified: Saturday, December 30, 2023, 10:21:54 PM
  Accessed: Saturday, December 30, 2023, 10:31:02 PM
  Attributes: Archive

Streams
  Video: 00:00:21.522, 29.970 fps interlaced, 1440x1080x12, MPEG-2
  Audio: 00:00:21.522, 48,000 Hz, Stereo, MPEG Layer 2

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: compoundplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 21.0\FileIO Plug-Ins\compoundplug
  Format: MPEG-2 Transport Stream
  Version: Version 21.0 (Build 208)
  Company: MAGIX Computer Products Intl. Co.

Please use this FAQ to post the Mediainfo report for your source file(s).

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

Tell us about your hardware.

jetdv wrote on 12/31/2023, 7:12 AM

When dragging files to the timeline, drag to the timeline and keep the mouse button pressed. You can move the mouse around in the timeline area but keep the button pressed UNTIL you see the outline of the event(s) appear. Once those appear, drag it to the desired area and then let go of the mouse button.

steve-medley wrote on 12/31/2023, 9:11 PM

When dragging files to the timeline, drag to the timeline and keep the mouse button pressed. You can move the mouse around in the timeline area but keep the button pressed UNTIL you see the outline of the event(s) appear. Once those appear, drag it to the desired area and then let go of the mouse button.

Thanks Edward, I have been using vegas for 10+ years and I do know how the Vegas Timeline works.

Happy New Year

steve-medley wrote on 2/10/2024, 7:00 AM

Hi All

Sorry for the long delay between my posts, holidays and a funeral has slowed me down.

After taking on comments from the forum I did a little testing for my self and have found that the problem that is the NTSC (29fps) format of m2t files loads really quickly but the PAL (25FPS) loads a lot slower. On a small m2t file is a noticeable delay. When you do the same exercise on a 20GB file the delay is extricating in the PAL format but fast with the NTSC format.

Clearly I live in Australia and only use the PAL format

I have left files in the following link

https://drive.google.com/drive/folders/1w6tvTc_oXpIHWWn5SYMha6B1W2eAA-Me?usp=drive_link

Thanks

Steve Medley

Former user wrote on 2/10/2024, 7:41 AM

@steve-medley Hi, I can't help but just to report I have no problem with the PAL file, loads quickly & @ Good (Full) it plays well. Windows 10 & a different PC tho 🤷‍♂️

Howard-Vigorita wrote on 2/10/2024, 10:42 AM

@steve-medley Tried both of your clips on my laptop with vp21 b208 and they both drop onto the timeline fine from the Vegas Explorer and play full rate. Wondering if the problem might be the project settings. I'm set to match the 1st clip of a new project and did not throw both clips into the same project. Also noticed some slight differences between the 2 clips in their metadata but don't know why it might be significant on your system and not matter on mine. I ran a diff and captured it:

General:
Complete name                            : C:\Users\hv\Downloads\Small File 1.25GB PAL.M2T
Duration                                 : 6 min 52 s
Start time                               : UTC 2024-01-01 17:04:08
End time                                 : UTC 2024-01-01 17:11:01
Overall bit rate mode                    : Variable
Overall bit rate                         : 26.1 Mb/s
Encoded date                             : UTC 2024-01-01 17:04:08

Video:
Format settings                          : CustomMatrix / BVOP
Format settings, Matrix                  : Custom
Format settings, GOP                     : M=3, N=12
Bit rate                                 : 24.4 Mb/s
Maximum bit rate                         : 25.0 Mb/s
Frame rate                               : 25.000 FPS
Bits/(Pixel*Frame)                       : 0.629
Stream size                              : 1.17 GiB (94%)

General:
Complete name                            : C:\Users\hv\Downloads\Small File 1.25GB NTSC.m2t
Duration                                 : 6 min 53 s
Start time                               : UTC 165-25-45 45:85:85
End time                                 : UTC 165-25-45 45:85:85
Overall bit rate mode                    : Constant
Overall bit rate                         : 26.2 Mb/s
Encoded date                             : UTC 165-25-45 45:85:85

Video:
Format settings                          : BVOP
Format settings, Matrix                  : Default
Format settings, GOP                     : M=3, N=15
Bit rate                                 : 24.5 Mb/s
Frame rate                               : 29.970 (30000/1001) FPS
Bits/(Pixel*Frame)                       : 0.525
Time code of first frame                 : 00:00:00:00
Time code source                         : Group of pictures header
GOP, Open/Closed                         : Open
GOP, Open/Closed of first frame          : Closed
Stream size                              : 1.18 GiB (93%)

Also, my project setting ended up looking like this... I avoid using Smart de-interlacing to preclude possible gpu issues:

Reyfox wrote on 2/10/2024, 11:40 AM

To add to the "it worked without an issue" group. Dragged and dropped the PAL file from the download folder on my computer directly to the timeline. My computer specs listed below. It was instant.

steve-medley wrote on 2/10/2024, 7:11 PM

Thanks all for the comments. I would appear that If I re-render my PAL MT2 footage to a new Pal file and import the re-rendered file it imports as I would expect. I suspect that the real cause of the problem the ay the footage is being recorded onto the CF card from the sony z5 camera and the extraction with the sony ru-util.exe utility.

Not and Ideal solution but will have to do for now.

Thanks again

Steve Medley

mark-y wrote on 2/10/2024, 8:04 PM

you can try importing your footage from the card using Device Explorer in Vegas, rather than the utility.

you can also still find copies of Sony Catalyst online, which might also do the trick.

steve-medley wrote on 2/10/2024, 8:52 PM

Thanks Mark-y

Your suggestion of using the device explorer worked perfectly. Still do not know why we had to resort to this as VP 20 back to VP15 worked fine.

Cheers

Steve Medley

mark-y wrote on 2/10/2024, 8:54 PM

You are welcome.