I wonder if anyone here can help shed some light on a problem I've been having for a while now. Nero's tech support blame Microsoft's DirectShow MP3 import filter, Microsoft tech support blame the MP3 files (but there are a whole load I've got that cause this problem, and they all work fine in most other software, even Windows Media Player).
I'm creating a DVD-based picture slideshow disc using Nero NeroVision Express, which allows you to place multiple picture files onto its video timeline, and it can fade/cut/etc between them at various intervals as required. It also has an accompanying audio timeline, onto which you can place one or more songs to play in the background while you are viewing the slideshow on a DVD player.
It is importing MP3 tracks onto the audio timeline that causes the problems.
When I import an MP3 file, the duration shown in NeroVision often shows as somewhat longer than the actual audio file. Not all MP3 files cause this problem, but it is always repeatable for any given file (most of my own are LAME 3.9x VBR files which generally seem to fail). The total duration for the slideshow is calculated based on the displayed audio durations, not the real running time of the MP3 tracks, so when you play the slideshow (either via on-screen preview or from the final disc) there is a corresponding silent period after each piece of music has finished before the next audio track starts. This silence can last several minutes with longer tracks.
I have sent two short sample MP3 files to Nero and they found the same problem when they tried them. When they looked into it, they blamed a bug in Microsoft's DirectShow import filter for the issue and they won't look into it further. Given that these files all work fine in other programs (both Microsoft and third-party) I find their attitude to their registered customers a bit offhand, but until I can prove categorically that the bug isn't in DirectShow I've got to accept what they're saying.
Hope someone here can help - I'd settle for finding a batch utility that will correct whatever headers NeroVision is having trouble with. I've tried several, including foobar2000's Fix Headers option, which actually made the problem worse - a 5'46" MP3 file which NeroVision originally reported as being 8'13" loaded in as 16'24" after foobar "fixed" it! :-)
If this isn't a known problem (which I'm guessing it might be?) I can upload/email a few short sample files (1Mb or so) if anyone in the know about these things might be able to check them out for me?
TIA!
Regards,
Andre
