Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
22nd March 2007, 03:12 | #521 | Link | |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
Quote:
This map only can confuse and isn't correct. Please forget the old BeSweetGUI, can't work with Aften. With BeLight you don't need any remap. |
|
22nd March 2007, 03:14 | #522 | Link |
Registered User
Join Date: Feb 2005
Posts: 585
|
Aha, yeah, I use the BeSweet gui and found I have to configure it this way when I transcode from ac3 to ac3. That's why, in the other thread, I was testing with BeHappy instead. But this channel mapping does work in BeSweet. I'll take a snapshot and put it up in a little while.
[EDIT] BeSweet azid settings: The only thing I use different is the dynamic compression. In the snapshot it's set to normal, but I use none normally which is in the pulldown list.
__________________
Chumbo Last edited by Chumbo; 22nd March 2007 at 03:31. Reason: added snapshot |
22nd March 2007, 03:33 | #523 | Link | |||
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
Quote:
Quote:
Quote:
-d3/2 -L0 -l1 -ol,r,c,lfe,sl,sr The correct wav order is FL, FR, C, LFE, SL, SR. |
|||
22nd March 2007, 03:43 | #524 | Link | ||
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
Quote:
- The channel remapping is wrong. - Use OTA for timestretch is obsolete. - ac3enc is also obsolete Quote:
|
||
22nd March 2007, 03:50 | #525 | Link |
Registered User
Join Date: Feb 2005
Posts: 585
|
That's fine, but if it ain't broke and it works... The channel mapping is not wrong. How can you say that? I've listened to the output tracks and they're absolutely correct. I've done this on many files. I wouldn't post bad or incorrect info if I hadn't used it successfully. Regardless of what's obsolete, it works. With that said, I'm trying to move to new tools as you know.
__________________
Chumbo Last edited by Chumbo; 22nd March 2007 at 03:50. Reason: fixed typo |
22nd March 2007, 03:51 | #526 | Link |
Registered User
Join Date: Dec 2006
Location: Heidelberg (DE), Kraków (PL)
Posts: 519
|
I'm very grateful for all the help, explanations, and suggestions!
1) I've finally understood the channel order (AC3's internal, and that of 5.1 WAVE). 2) Since I'm not familiar with foorbar2000, and the AviSynth-based applications have NET.framework dependency (or am I wrong? then plz correct me), I'm gonna try the standalone azid version. Yet my nose tells me I might hit the 4GB boarder again, since I did already twice while trying to transcode my AC3 file using BeLight/BeSweet or just the BeSweet's CMDL. Both azid's versions are the same (the standalone one and the one included with BeSweet package). 3) When I find some time to test, I'm gonna report back. again and good night
__________________
"Only two things are infinite: the universe and human stupidity, and I'm not sure about the former."
|
22nd March 2007, 03:54 | #527 | Link | |
Registered User
Join Date: Feb 2005
Posts: 585
|
Quote:
__________________
Chumbo |
|
22nd March 2007, 04:25 | #528 | Link | ||
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
Quote:
Quote:
|
||
22nd March 2007, 12:58 | #529 | Link | |
Registered User
Join Date: Dec 2006
Location: Heidelberg (DE), Kraków (PL)
Posts: 519
|
Quote:
I had some problems: first of all I have an AC3 source, so how do I load this kind of audio source in AviSynth? Or should I rip the VOBs again, so that they contain the audio track and call multiple "mpeg2source"s? Finally I went for DirectShowSource, and AC3 filter popped out then, decompressing the AC3 to 6 channel WAV, and sending it to the plugin (of course I had to reconfigure the AC3 Filter to not process anything on the way). The results are rather poor: 1) The first 16-bit 5.1 WAV seems to be 4.60 GB, and so much it occupies on my HDD, Media Info indicates proper length and size, while Audio Identifier says it's only 622.63 MB and 18min 53sec long! And so see it both AftenGUI and SoundOut, when I load the file via WAVSource(). 2) The same happened with my next trials (16-bit, and 24-bit WAVEs) - they occupy whole lot of space on my HDD, yet all audio processing applications see the above mentioned size and length, and so is the resulting Aften AC3 encode, when I try to process those files. 3) Could it be the fault of DirectShowSource() and AC3 Filter? Btw. the latter decodes the sound to WAV, with WAV channel order - hope SoundOut takes this into account? The rest in a separate post. If any moderator sees this, could he split this discussion form here? Thanks in advance! PS. Got it thanks to NicAC3soource(), and SoundOut shows 6 channles (I have always though NicAudio was limited to 3?) - gonna encode now. Nic's forces 32-bit float, but I specified 24-bit integer in the SoundOut itself - hope this time I finally get the damned WAVE. PS. NicAudio went on and created a huge 32-bit floating point WAV file. Wrrrr!
__________________
"Only two things are infinite: the universe and human stupidity, and I'm not sure about the former."
Last edited by HeadBangeR77; 22nd March 2007 at 13:48. |
|
22nd March 2007, 13:49 | #530 | Link | |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
Quote:
- the -ol,r,sl,sr,c,lfe parameter is ignored (like I say before and fortunately) in BeSweet-azid section. The order l,r,sl,sr,c,lfe is wrong, I don't know any soft than use this order. - the channel mapping order in BeSweet is controlled by bsn.dll. - Old bsn.dll generate wav's in ac3 order l,c,r,sl,sr,lfe (the same order necessary for ac3enc.dll, headac3he,... and supported by aften with the parameter -chmap 1) - New bsn.dll (by Kurtnoise) generate wav's in standard wav order l,r,c,lfe,sl,sr and send this order to aften, but when send data to ac3enc is remapped to l,c,r,sl,sr,lfe like is needed. This kind of mapping problems don't exist with BeLight, the new GUI for BeSweet, also support the last free encoders Aften, NeroAacEnc or CT enc_AacPlus, -soundtouch for timestretch and so on. |
|
22nd March 2007, 13:51 | #531 | Link | |
Registered User
Join Date: Dec 2006
Location: Heidelberg (DE), Kraków (PL)
Posts: 519
|
Quote:
Code:
(-f wav24 -d3/2 -L0 -l1 -ol,r,c,lfe,sl,sr) And Chumbo, thanks a lot for good intentions and your quick answers! @ tebasuna51: I'm constantly getting the same results with SondOut, no matter if I use DirectShowSource or NicAC3source - the file is huge, yet reported by most applications as much smaller, just 18 minute long, and so Aften sees it too.
__________________
"Only two things are infinite: the universe and human stupidity, and I'm not sure about the former."
Last edited by HeadBangeR77; 22nd March 2007 at 13:56. |
|
22nd March 2007, 14:36 | #532 | Link | ||
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
Quote:
Code:
azid.exe -F wav24 -d3/2 -L0 -l1 -ol,r,c,lfe,sl,sr <ac3> <wav> Quote:
Time_length = Size_in_bytes / (SampleRate x Num_channels x Bit_depth / 8) For instance for a wav 48 KHz, 6 channels, 24 bit and 4.87 GB you have: Time_length = 5229122682 / (48000 x 6 x 24 / 8) = 6052 sec = 1h. 40m. 52s. To encode with aften (rev449 and next) you need the parameter: -readtoeof 1 This parameter are not yet implemented in AftenGUI or SoundOut GUI, you need execute something like: Code:
NicAc3Source("G:\yourpath\input.ac3", DRC=0) (process if any) SoundOut(output="cmd", filename="G:\yourpath\output.ac3", autoclose=true, type=0, executable="G:\yourpath\aften.exe", prefilename="-v 0 -b 384 -readtoeof 1 -") |
||
24th March 2007, 14:07 | #533 | Link | ||||
Registered User
Join Date: Dec 2006
Location: Heidelberg (DE), Kraków (PL)
Posts: 519
|
Quote:
Thanks very much for the correction of my command line - it worked then, yet I think I'm gonna stick to the SoundOut plug-in, since then I can spare myself the step of creating a bloated WAV, and transcode AC3 => AC3 directly. Great plug-in, btw., must dig in the thread some time. Quote:
Btw. all the applications that read just the header have reported the file size and duration of the "overflow" above 4 GB, interesting... I mean for instance: I had a 4.6GB WAV (as above, yet only 16 bit) with total duration of 2 hours and 23 minutes; it was reported as 6XX MB file with a total playing time of about 18 minutes, instead of e.g. 4GB file, 2 hours 4-5 minutes. Do you happen know why is it so? Quote:
Quote:
Code:
NicAC3Source("I:\DVD\Black Pearl\AC3\Original AC3 Track.ac3") SoundOut(output="cmd", filename="I:\DVD\Black Pearl\AC3\New AC3 Track.ac3", autoclose=true, type=0, executable="I:\DVD\Black Pearl\AftenGUI-1.3\aften.exe", prefilename="-v 0 -b 384 -dnorm 31 -dynrng 5 -readtoeof 1 -") As to some tweaking: - -bwfilter 1 I can't notice any difference in audio, - dynrng 0 (which is "Film Light") is indeed very, very subtle. It might be not up to the specs, yet I think I'm gonna stick to it, since I really like the end effect [i]"The full dynamic range audio is still encoded, but a code is given for each block which tells the decoder to adjust the output volume for that block."[i](Aften HELP file) Does that mean the changes could be reverted? And really the last of my questions: I remember reading somewhere Aften adds some extra frames while transcoding /encoding. In my case the difference is: 02:23:10.944 original AC3 vs. 02:23:10.976 Aften Does it take place somewhere at the beginning of the file? If so, I could just add a "-32ms" delay while muxing with video, and the slight asynchronisation should be gone, shouldn't it? Thank you very much for all the help - really appreciated! cheers, HDBR77
__________________
"Only two things are infinite: the universe and human stupidity, and I'm not sure about the former."
|
||||
25th March 2007, 03:22 | #534 | Link | |||
Registered User
Join Date: Jul 2006
Posts: 276
|
Quote:
Quote:
Quote:
|
|||
25th March 2007, 04:08 | #535 | Link | |||||
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
Quote:
Quote:
Quote:
Quote:
Quote:
|
|||||
26th March 2007, 11:19 | #536 | Link |
Registered User
Join Date: Dec 2006
Location: Heidelberg (DE), Kraków (PL)
Posts: 519
|
@ jruggle:
Thank you very much for clarifying. @ tebasuna51: I've got to thank you one more time for all the explanations. I used to have some older (most probably the last official/stable) version of NicAudio plug-in, dated July 2005, and it didn't accept the DRC parameter - thanks for linking to a newer version. Everything seems now very clear to me, and I hope my endless questions and your explanations can be of any use for other people. cheers, HDBR77
__________________
"Only two things are infinite: the universe and human stupidity, and I'm not sure about the former."
|
5th April 2007, 10:00 | #537 | Link | |
Registered User
Join Date: Mar 2002
Posts: 2,323
|
Quote:
|
|
5th April 2007, 10:10 | #538 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Some theoretical questions to the (E-)AC3 gurus:
(1) Which bitdepth are studios encoding (E-)AC3 in? 16bit? 20bit? 24bit? 32bit integer? 32bit float? (2) Does the bitdepth make a difference for the final (E-)AC3 file size? Does the (E-)AC3 file size get bigger with more input bitdepth? (3) Is there a way to find out which bitdepth a given (E-)AC3 track was encoded with? (4) If a (E-)AC3 file was encoded with 16bit, does decoding to more than 16bit still have any advantage whatsoever? |
5th April 2007, 11:24 | #539 | Link | |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
Quote:
|
|
6th April 2007, 23:31 | #540 | Link | ||||
Registered User
Join Date: Jul 2006
Posts: 276
|
Quote:
Quote:
Quote:
Quote:
|
||||
Thread Tools | Search this Thread |
Display Modes | |
|
|