View Full Version : BeHappy and DTS-MA 7.1?
djloewen
20th November 2009, 05:37
I've used eac3to to grab a blu-ray audio track, which is listed as follows:
DTS Master Audio, English, 7.1 channels, 24 bits, 48khz, -8ms
(core: DTS, 5.1 channels, 24 bits, 1509kbps, 48khz)
I demuxed it twice, once as .dts and once as .wav. I didn't use any switches in either case.
I then tried encoding each with BeHappy. For the DTS file I used NicDtsSource, for the WAV I used "RaWav IgnoreLength Always". In both cases, I used the filters "Downmix - DPL II" and "Normalize to 100%", then encoded with "Lame MP3, CBR @ 128 kbit/s".
The mp3 created from the WAV file plays fine. The mp3 created from the DTS file appears to be silent from start to finish. Is this a limitation of NicAudio.dll? Am I doing something wrong?
tebasuna51
20th November 2009, 13:54
1) Please put the log file when you extract the .dts file.
2) The .dts file play ok with Foobar or MPC or ...?
3) Please upload a fragment of your .dts file using the same command line than 1) and the parameter -9mb
This stop the demux after the first 9 MB of input file with a .dts file small.
Mtz
22nd November 2009, 21:50
How can be avoided that forever error "Bass 2.2 required"? I put all dlls from "plugins" from latest version of BeHappy in C:\Program Files\AviSynth 2.5\plugins
Can you upload somewhere your BeHappy folder with all needed and updated files which is working so I don't need to navigate on hundred sites to get a simple audio conversion working?
I just broke my old 1.xx version of BeHappy with the new release because of stupid dlls and I am mad because of this.
I have the latest nero aac so you can skip it to not break some stupid nero rules. (The link from behappy aac window for neroaac is not good).
Thank you!
Mtz
Later edit: and now because of that bass 2.2 needed other programs are not working for me. I hope you can provide me at least bass 2.2 to get other programs back to work which are using avisynth.
tebasuna51
23rd November 2009, 01:00
How can be avoided that forever error "Bass 2.2 required"?
Don't install other versions than 2.4.
Use the components in last BeHappy version and, if you need other bass decoder go to http://www.un4seen.com/
Later edit: and now because of that bass 2.2 needed other programs are not working for me. I hope you can provide me at least bass 2.2 to get other programs back to work which are using avisynth.
I can't supply old and buggy versions, is more easy supply the last and working version (from 2008-03-14).
Ask to the 'other programs'
If all of your bass*.dll in AviSynth pluguins folder are older than BassAudio.dll also the 'other programs' must work.
djloewen
24th November 2009, 23:43
Sorry for the late reply. I installed foobar2000 and the DTS decoder, and when I play the DTS file I can hear the audio, but it's somewhat static-y and garbled.
Here's a 9mb sample:
http://www.megaupload.com/?d=V2VU6WER
As a note, using the -9mb switch only grabbed 900kb. So I tried -90mb, and it grabbed 9mb. *shrug*
tebasuna51
26th November 2009, 01:45
The mp3 created from the DTS file appears to be silent from start to finish. Is this a limitation of NicAudio.dll?
...
Here's a 9mb sample:
http://www.megaupload.com/?d=V2VU6WER
Sorry but I can't reproduce your problem the sample is decoded, donwmix and normalize without problems.
Check if you have the correct NicAudio.dll in ...\AviSynth 2.5\plugins folder. The DTS-HD (core) support was included with version 2.0.2:
24/09/2008 v2.0.2
25/06/2009 v2.0.3
12/08/2009 v2.0.4
djloewen
26th November 2009, 23:15
My NicAudio.dll is 12/08/2009, so it is the latest version. I tested the same 9mb clip myself and it encodes perfectly. I tried the full file again (2.11Gb) and it still produces a silent output. Both the 9mb clip and the full file play in foobar2000 (although with static-y sound as I mentioned earlier).
tebasuna51
29th November 2009, 00:46
The encoded mp3 files from wav(correct) and dtshd(silent) have the same size?
djloewen
29th November 2009, 17:13
Yes, they both have a length of 01:27:44 and a filesize of 82,256 KB.
tebasuna51
29th November 2009, 19:03
Then the first step (read the whole file and know the number of dts-core frames, samplerate and numchannels) seems work ok.
I don't know what can be the problem.
If you want make one more test for me, please try the same encode but now extracting the core from the DTS:
eac3to source_dtshd dtscore.dts -core
and after the BeHappy encode with NicDtsSource.
djloewen
29th November 2009, 20:09
I exctracted the core, and it encoded perfectly.
I did notice some very big differences between the two encodes though:
The dtscore file is 946MB. When I started the encoding job it took about half a second for the first 6 log lines to appear (from "Starting job" to "Writing PCM data to encoder's StdIn"). Then the green bar started moving, and it was done in 15 minutes (I'm running a Core i7).
The dtshd file is 2.11GB. When I started the encoding job it just said "Starting job xxx.dts->xxx.mp3" for the first 75 seconds. Then it printed the next 5 lines (up to "Writing PCM data to encoder's StdIn"). The job took just over 2 hours, and the green bar wasn't moving for most of that (it probably only started moving for the last 15 mins - I don't know, I wasn't watching the whole time).
b66pak
29th November 2009, 20:20
The dtscore file is 946MB. When I started the encoding job it took about half a second for the first 6 log lines to appear (from "Starting job" to "Writing PCM data to encoder's StdIn"). Then the green bar started moving, and it was done in 15 minutes (I'm running a Core i7).
i think you forgot to "normalize to 100%"...
_
djloewen
29th November 2009, 20:39
I just redid the dtscore, to be sure. I checked "Downmix - DPL II" and "Normalize to 100%". The first 6 log lines appeared almost instantly, then it took 8 minutes and 19 seconds for the green bar to start moving (I forgot to mention that in my last post). The entire thing from start to finish took 14 minutes 8 seconds.
b66pak
29th November 2009, 20:44
it took 8 minutes and 19 seconds for the green bar to start moving
this is normal...normalizing is done in two steps (1st to acquire data, 2nd to do the job)...
_
djloewen
29th November 2009, 20:51
Right, I have no problem with the 8minute wait for the green bar, or the 15min encode time. That's for the dtscore file, which produces a perfect working mp3. The problem is when I try to do the dtshd file. It takes 75 seconds to get to "Writing PCM data...", over two hours to do the entire encode, and the end result is an mp3 with no audible sound in it.
I wouldn't even mind if it took 2 hours as long as it worked, the thing is it doesn't. The only reason I mention the length is that there's such a big difference between the length of the dtscore and the dtshd, I thought it might be a clue as to why the dtshd doesn't work.
tebasuna51
30th November 2009, 00:38
With the dtshd the first 75 seconds before print "Write PCM data..." is the time to check the whole file to know the dts core frames, with the dts-core this is know instantly because is CBR (constant bitrate)
The time before the green bar begin to move is the pass to decode and know the max audio volume.
The problem is the very long time (2 hours) for decode and recode the dtshd, and of course the silent result. Maybe there are a problem inside the dtshd not well managed by NicDtsSource. Because the first 10MB work fine. I don't know.
Is the first report about this problem. Thanks.
BTW don't exist any reason to downmix the dtshd, instead the dts-core, and convert to mp3.
djloewen
2nd December 2009, 04:49
I agree that extracting the core is a good workaround.
In the interest of trying to identify and solve this problem though, I made smaller and smaller samples of the audio to see where it stops working. The answer is, a 10mb sample encodes in 5 seconds and works fine, a 15mb sample encodes in 5 seconds and doesn't work. So I have uploaded a 15mb sample for you to poke at:
http://www.megaupload.com/?d=B0ZP9B2C
I also should mention that the 2.11gb file took over two hours to encode, but a 1gb sample of the same file took only 14 minutes (and also didn't work, of course). So the long encode time is a totally separate problem.
tebasuna51
2nd December 2009, 14:04
Thanks for your sample, you are right the output is silence.
Seems a problem with the second pass, without the Normalize work fine (please confirm).
I will try to locate the problem.
Thanks.
djloewen
2nd December 2009, 15:08
Yes, it works fine without the normalize. Even the full track took 7.5 minutes and works fine.
Chetwood
19th December 2009, 12:54
I've got a similar problem with a DTS stream I've extracted with TSMuxer. Converting to MP3 does not even start, I'm getting:
Error: BeHappy.AviSynthException: Script error: there is no function named "NicDtsSource"
at BeHappy.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace, AviSynthScriptEnvironment env)
at BeHappy.Encoder.encode()
This is my first time playing around with BD media so I'm not sure what to check. nicaudio.dll is in both behappy\plugins and avisynth\plugins. What am I missing? Thx.
tebasuna51
19th December 2009, 16:22
...
Error: BeHappy.AviSynthException: Script error: there is no function named "NicDtsSource"
...
nicaudio.dll is in both behappy\plugins and avisynth\plugins. What am I missing?
Try reinstall AviSynth, if you have nicaudio.dll in the ...\AviSynth 2.5\plugins folder this error don't make sense.
Seems you have corrupt the AviSynth install, maybe installing Super or other.
Chetwood
20th December 2009, 07:59
That did the trick. After uninstalling Avisynth that came with AutoGK, I installed 2.58 and the file was processed. However, since I had selected "LAME MP3, VBR4" as output I had to copy over the missing lame.exe to make it start encoding which then was stopped with this error message:
Found Audio Stream
Channels=6, BitsPerSample=32 int, SampleRate=48000Hz
encoder\lame.exe -v -V 4 --nohist --vbr-new -h -S --silent - "D:\test.mp3"
Writing RIFF header to encoder's StdIn
Writing PCM data to encoder's StdIn
Any output was kept for you to inspect.
Error: System.IO.IOException: Die Pipe wurde beendet.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.FileStream.Write(Byte[] array, Int32 offset, Int32 count)
at BeHappy.Encoder.encode()
Any idea what's this about? I'm just playing around a bit so it's no biggy. However, I thought that ripping a BD with AnyDVD and demuxing DTS with TSmuxer should result in a proper file ready to be converted. Playback however is a bit garbled.
tebasuna51
20th December 2009, 12:26
...
Channels=6, BitsPerSample=32 int, SampleRate=48000Hz
encoder\lame.exe -v -V 4 --nohist --vbr-new -h -S --silent - "D:\test.mp3"
...
Any idea what's this about?
Yes, you can't encode 6 channels with Lame (only support mono or stereo).
You need apply before a Downmix 5.1 -> 2.0
However, I thought that ripping a BD with AnyDVD and demuxing DTS with TSmuxer should result in a proper file ready to be converted. Playback however is a bit garbled.
Use always eac3to to demux BD.
Chetwood
21st December 2009, 06:52
Right, thanks. Checking "downmix" helped, I got my MP3 so TSMuxer apparently was okay for this one. Gonna check out eac3to anyway.
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.