| DVDit Pro audio problem
• | | | |
 | DVDit Pro audio problem
by Daenris on Nov 17, 2005 at 3:11:04 am |
So I've just started using DVDit 6 Pro and am having some problems with audio tracks. I've got MPEG 1 video streams that are DVD compliant that I import. Then I import ac3 audio tracks for those videos (also DVD compliant). My video is at a very low bitrate (1000kbps) and the audio is around 128kbps. When I add the audio tracks to some movies, the project size jumps up by nearly 1gig, but for other files it's fine.
However, it's even weirder than that, because if I add the same audio track again to that movie or another it only goes up a little (about what it should). But if I add an audio track that originally only took a small space again to the same or another movie, it will jump up by nearly 1 gig again.
This is getting very frustrating and making me regret my decision to choose DVDit.
Any ideas why this is acting this way?
The same thing happens if I just use .mp2 audio and let DVDit do the transcoding.
| | | | |
• | | | |  | Re: DVDit Pro audio problem by SS Scott on Nov 17, 2005 at 11:32:32 pm |
I believe this behavior is addressed in the fortcoming 6.1 release. That should be available for download in the next week or so.
| | | | |
• | | | |  | Re: DVDit Pro audio problem by Alex Alexzander on Nov 18, 2005 at 11:45:25 pm |
I would use AC3, AKA Dolby Digital, at 192 or 224k for Stereo. This should be at the sample rate of 48k. Or for PCM, try .WAV also sampled at 48k. AC3 uses far less bandwidth however. PCM uses 1.54 Mbs, vs. AC3 which can be as low as 192k.
Stick to 48k as the sample rate.
-Alex
| | | | |
• | | | |  | Re: DVDit Pro audio problem by Daenris on Nov 19, 2005 at 12:24:45 am |
They ARE sampled at 48khz, and they ARE AC3 files (which I said in my first post). They're only 128kbps because I'm trying to fit quite a bit of video on a single DVD.
| | | | |
• | | | |  | Re: DVDit Pro audio problem by Alex Alexzander on Nov 19, 2005 at 3:22:23 am |
I've not tested working with half-D1 before. Sorry didn't catch those specifics. Perhaps the 6.1 update will indeed fix. I've not seen this.
-Alex
| | | | |
| |
|