Any timeframe on next beta update?
- Thread starter DavidB
- Start date
- Status
The current build can mux MPEG2 elementary streams into a file VRD can edit. It does not yet support H.264, but that is something we do plan in a future release.
WMV is most likely never going to be supported as an input format. VRD is mainly designed to help people edit TV programs. All across the world the only two codecs used for actually broadcasting TV are MPEG2 and H.264, which is why those are the only input formats we support. We do however support a wide array of output codecs so that you can play your edited files on pretty much any device.
Dan
WMV is most likely never going to be supported as an input format. VRD is mainly designed to help people edit TV programs. All across the world the only two codecs used for actually broadcasting TV are MPEG2 and H.264, which is why those are the only input formats we support. We do however support a wide array of output codecs so that you can play your edited files on pretty much any device.
Dan
We have considered generic DS input, however there are a few problems with it....
1) We could not quick edit. So anything input via DS would have to be completely recoded on output. (quick edit requires specific knowledge of the source codec)
2) Seeking in DS is not always 100% accurate which could create problems for our editing routines.
3) We would be reliant on the codecs/filters installed on the users machine. DS uses it's own mechanism for connecting all the filters needed to render a specific file. Without specific knowledge of the input codec we would have no control over which filters are used to render a specific file. This could potentially create an issue where various users would get different results from the same file depending on which filters were installed on their PC. This creates a serious support issue for us and is the main reason we don't support DS input.
DanR is in charge of putting out release builds. I have no idea when he's planning to put out the next one.
Dan
1) We could not quick edit. So anything input via DS would have to be completely recoded on output. (quick edit requires specific knowledge of the source codec)
2) Seeking in DS is not always 100% accurate which could create problems for our editing routines.
3) We would be reliant on the codecs/filters installed on the users machine. DS uses it's own mechanism for connecting all the filters needed to render a specific file. Without specific knowledge of the input codec we would have no control over which filters are used to render a specific file. This could potentially create an issue where various users would get different results from the same file depending on which filters were installed on their PC. This creates a serious support issue for us and is the main reason we don't support DS input.
DanR is in charge of putting out release builds. I have no idea when he's planning to put out the next one.
Dan
You appear to be the only one that is having this issue. No one else has indicated that they too have these gaps.
I've never had an issue with audio at edited locations.
What is your source of these HD files?
Rats. H.264 is where we need it most. I could easily be wrong, but weren't most of the postings from H.264 users?
Will get it into H.264 after we finish testing it with MPEG2. Its just about done just doing some testing. Turned out to be a MUCH MUCH bigger job than anticipated, but the major plumbing is now complete so getting it into H264 should be much easier (he said optimistically).
Interesting. The few times I've opened a x264 file that I created I didn't have any issues opening them.
I wonder if it is related to the options used.
Can you upload a short sample file and VPRJ that duplicates the problem. In re-working the audio for multiple streams we've found a couple of subtle situations where the audio can get off a frame (32 msec for AC3) and maybe your files are triggering one of these cases.
I have ZERO files to test with it (MPEG-2). Oh wait, I can do a capture of a source with at least two AC3 audio streams as well as a MP2 audio stream.
I've heard nothing regarding the issues with ABC H.264 files. NBC H.264 isn't trouble free either, so that might be related. Was anything discovered with the files that I uploaded?
Lastly, any progress on the edit location error with 720p video (MPEG-2 or H.264)? As a reminder, in cut mode, the edit location that starts a location of video to be removed is off by one, always. If the location is to remove the frames starting at frame number 1000, the frame at 999 is also removed. I have to set the edit point at 1001. There is no error at the end selection of frames to be removed. Only the start location.
I can capture the complete mux, which also has a Dolby-E stream. VRD normally ignores that stream. I'll capture a couple of minutes worth tonight and send it your way.
:-(
Floobydust
Member
File uploading to the MrVideo directory. Still has about 300 minutes to go. No support e-mail as this isn't a support issue
Four audio streams: Dolby-E, AC3-2.0, AC3-5.1, MP2 stereo
- Status