BIG crash problems with HDVsplit for capture

blink3times wrote on 5/13/2007, 4:16 PM
I'm using HDVsplit to capture because the scene detect on the internal capture is just plain out to lunch. But I'm having SERIOUS crash problems during renders. It seems that just about every new scene detection causes a render crash (when rendering as HDV m2v)

Is anybody else that uses HDVsplit seeing this?

Comments

riredale wrote on 5/13/2007, 4:43 PM
Using HDVsplit here with no problems.

With my newish HC3 camcorder I would have dropped frames issues until I upgraded to the latest version, .77beta.

The other thing I would mention is that when I first began using HDVsplit last spring, I would get a hard crash if the tape went from an m2t file (HDV) to a DV file. Could your tape be a re-used one with pieces of DV material still on it?

EDIT:
Wait a minute, that's not what is happening in your case, is it?
blink3times wrote on 5/13/2007, 5:40 PM
No... I haven't done DV in a long while now.

Strange though... I'm using HDVsplit with my HC3 and the odd scene is just plain unusable even on the timeline. Yet when I capture that same footage with internal capture (less the scene splits of course) there are no problems.... so it's obviously something that HDVsplit is doing (or not doing as the case may be).

Furthermore, I can't get the HDVsplit scene detect to work at all with my new canon HV20... it generates a new scene every 75kbytes or so, regardless of an actual scene change!?

Oh well... guess I'll head back to internal capture and manual scene detect :(

I wish they would do something with the damned internal scene detect!!!
riredale wrote on 5/13/2007, 6:44 PM
You're running the .77 version, right? I understand that the whole reason for the .77 version is because of the HV20.
Illusioneer wrote on 5/13/2007, 7:16 PM
Yes, I saw this as soon as I upgraded (7.0e) :-(. Anyone have any suggestions how to resolve or is using the internal capture the only solution?

P.S. not sure which version of HDVSpilt I used for the original capture
blink3times wrote on 5/13/2007, 9:23 PM
Mmmmm.... Nice to see I'm not alone... not that I wish this bad luck on others. I may roll back to 7d and see if that clears the problem. I'm not into AVCHD so the 7e update is of no real use to me anyway.

Of course, I'm back in the dark ages with version .75 HDVsplit anyway.... maybe that's part of the problem as well.

The whole thing is quite the piss-off though.... Being backed into a corner and having to use a third party capture program because the one that came with my $600 Vegas editor, splits scenes like crap.

****Madison.... You REALLY NEED to get serious about fixing the HD scene detect!!!!****
Christian de Godzinsky wrote on 5/14/2007, 1:19 AM
Hi,

****Madison.... You REALLY NEED to get serious about fixing the HD scene detect!!!!****

I could not agree more :) How does this error take so long to fix? Or is it going to be fixed at all ???

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