anyone compiled and tried dcaenc ?

[amtm]

As I said it was only a "probably", but it's highly unlikely the output will be very different especially at the bitrate you specified since you are at the level of what is pretty much transparent with lossy DTS. You might notice it more if your bitrate was at 756kbit or below. As to the file size difference, I can't see any reason why they'd be different. When I get home in a couple of hours, I can do some test encodes with Surcode and Master Audio Suite and see if both consistently do it and compare bitstreams against what dcaenc does. Would it at all be possible for you to post the streams you got from Surcode and dcaenc on multiupload or something so I could also check them? There may be some hints in the bitstream for the discrepancy.

[geminigod]

Would it at all be possible for you to post the streams you got from Surcode and dcaenc on multiupload or something so I could also check them? There may be some hints in the bitstream for the discrepancy.

Sorry, just reading this. I already deleted the surcode version that I decided not to use. I'm sure you could rip the audio from a long movie that you own though and attempt to repeat the experiment.

[madhatter300871]

Has anybody compiled Mulders dtsenc ? If so, could they upload a copy ?

I have tried to compile it but to be totally honest my compiling skills are limited !! I have compiled with mingw before using ./configure ./make and make install but anything further than that and I am just way out of my comfort zone. I have no idea at all how to install autoconf and M4 and whatever else I am being asked for, Linux really isn't my bag and in all honesty I haven't got a bloody clue what I'm doing !!

Would love to have a play with this if anyone can help.

Thanks.

[madhatter300871]

Done it !!!! How happy am I !!!!

I had to install autoreconf, automake and libtool then i just compiled as per the instructions .....

[LoRd_MuldeR]

Has anybody compiled Mulders dtsenc ? If so, could they upload a copy ?

I provided pre-compiled binaries all the time. So if you just need a "working" binary, you can simply grab (http://forum.doom9.org/showthread.php?p=1551512#post1551512) the one I provided ;)

If you want to compile yourself and if you use my branch, you can use the provided VS2010 project file. Should compile through "out of the box".

(You would only need to deal with "autoreconf" or "automake", if you use the MinGW/MSYS tool chain)

[madhatter300871]

Lord_Mulder

Thanks for the reply, I didn't see your pre-compiled version ! If only I had looked properly.

As it happens I did eventually compile your branch using Mingw/Msys. If nothing else it was a process in educating myself more regarding mingw compiling so not a total waste of time.

On a side note, and I know the real answer to this is rtfm, but would you be so kind as to tell me if there are any command line switches available that are not printed to console with command dcaenc -h ?

Thanks.

[LoRd_MuldeR]

On a side note, and I know the real answer to this is rtfm, but would you be so kind as to tell me if there are any command line switches available that are not printed to console with command dcaenc -h ?

Look at "main.c" ;)

t = xgetopt(argc, argv, "i:o:b:c:fhlev", &opt)

If anything was missing in the help, that would be unintentionally.

[madhatter300871]

Thanks for that pointer, unfortunately I am totally unfamiliar with C code and have to confess to being nothing more than a VB programmer, making my own GUIs for all these wonderful command line tools. I know, I know, I know ..... the world hates VB !

I actually don't think anything is missing, I was just wondering.

I have made my first encode, piping an avisynth script into dcaenc with bepipe and I must say the DTS soundtrack sounds fantastic when passed through to my amp.

One more question, I think I have missed the point about setting the bitrate as when I set anything between 650 and 764 (this is the only range I have played with so far) my final DTS track is always 755Kb/s, am I doing something wrong ?

[LoRd_MuldeR]

The bitrate that is sent to the "dcaenc" library internally is an approximate bitrate.

Although, as far as I know, dcaenc currently only uses a constant bitrate, it seems there is no function to query the actual bitrate...

[madhatter300871]

Ahh, ok. Dont understand why it is an approximation but, as I have confessed, I am not an expert in these things.

To transmit DTS over SPDIF doesn't it have to match the PCM bitrate, which for a 48Khz track is 1536mb/s. Do I need to worry about this or does the audio renderer (or decoder) take care of this by padding it automatically ?

[Midzuki]

...
One more question, I think I have missed the point about setting the bitrate as when I set anything between 650 and 764 (this is the only range I have played with so far) my final DTS track is always 755Kb/s, am I doing something wrong ?

MediaInfo and other tools / players display only the "target bitrate" according to what is written in the frame headers. The *actual* bitrate is a different story:

...

Exact bitrate must be calculated with Samplerate, Number of PCM Sample Blocks and Primary Frame Byte Size. Here:

Bitrate = 8 x 2012 x 48000 / 512 = 1509000 bits/s = 1509 Kb/s

This is the bitrate when commercial encoders output compact DTS (.cpt), when output padded DTS (.dts) the frames are incremented with bytes '0' until reach Transmission Bit Rate.
Here add 36 '0' at the end of the 2012 frame to reach 1536 Kb/s.

[madhatter300871]

Do you know why the specified target bitrate isn't used, why it is only an approximation (just for my own understanding and interest).

When I playback, does the decoder/renderer take care of padding it as needed ?

[LoRd_MuldeR]

Do you know why the specified target bitrate isn't used, why it is only an approximation (just for my own understanding and interest).

I'm not an expert on DTS bitstream, but if the situation is somewhat similar to MP3, then the encoder can choose between several pre-defined frame sizes. So if you do constant bitrate encoding, i.e. always pick the same frame size, then each of the pre-defined frame sizes results in a specific bitrate. In MP3, for example, there is one pre-defined frame size for 128 kbps, one pre-defined frame size for 192 kbps and so on. You can't get any other "constant" bitrates than those. If, instead, you do variable bitrate encoding, i.e. mix different frame sizes in the same file, you can get any average(!) bitrate that you like - simply by varying the frame sizes accordingly. But as said before, I think dcaenc does not offer variable bitrate encoding yet. Is that possible with DTS at all?

[amtm]

Do you know why the specified target bitrate isn't used, why it is only an approximation (just for my own understanding and interest).

When I playback, does the decoder/renderer take care of padding it as needed ?

Because the DTS spec only allows certain bitrate values. dcaenc allows you to pass it an arbitrary value but then based off of that it selects one of the allowed values.

[madhatter300871]

Ahh, OK. So what are those bitrates that the DTS spec allows ? I thought 768 and 1536 where allowed values (for example). They are the most common ones I see on my movies with a DTS soundtrack.

Yet when I select 768 as a bitrate, mediainfo shows it as 755. Eac3to, on the other hand, shows 768 as the bitrate if i set anything between 670 up to about 780.

I'm just playing at the moment and have included DTS encoding in my app, just curious why the bitrates are off seeing as (we think) dcaenc only allows for CBR encoding.

[Midzuki]

^ Yet when I select 768 as a bitrate, mediainfo shows it as 755. Eac3to, on the other hand, shows 768 as the bitrate if i set anything between 670 up to about 780.

Are you encoding 5.1 sources only ??? :confused:

In case of doubt, (re-)read this thread (http://forum.doom9.org/showthread.php?t=163526) again and again. :)

[madhatter300871]

I am encoding 5.1 sources only. Do you know the DTS bitrates that the spec allows ?

[madhatter300871]

I re-read the post and found the answer, in fact I found the answer many times over ..... perhaps in future I should be more patient in trying to find an answer before posting a question !

Thanks.

[madhatter300871]

I am only interested in 754.5 and 1509 at the moment, I have a question. Is 1509 correct or should i specify 1509.75 ?

[Midzuki]

I am only interested in 754.5 and 1509 at the moment, I have a question. Is 1509 correct or should i specify 1509.75 ?

According to http://aepatrakov.narod.ru/dcaenc/command_line_encoder/ :

dcaenc input.wav output.dts 1509000

However you really should try both 1509 and 1509.75 kbps, then run LeeAudBi and check whether dcaenc outputs the same bitrate in both cases, or not. Also, IF the goal is DVD-authoring, test both streams in the authoring program.
Otherwise, you might also verify if lower bitrates such as 1344 or 1152 kbps are acceptable to your ears --- today disk space is cheap, but hey :)

[madhatter300871]

Disk space is cheap so space usage is not an issue for me really. I am not authoring DVDs but it would be nice to know that if I chose to, the bitrate would be accepted (I'll check it is accepted by the authoring program).

My main concern is that it is an acceptable bitrate for my amp. I know .. encode and check ! ... but it's good to throw these questions out.

I'll use LeeAudBi to check the output using different bitrates with dcaenc, never used that tool before but I have just downloaded it and will check it out, thanks for the pointer.

On a side note .... is MediaInfo not that accurate when checking audio bitrate ?

[Selur]

Is 1509 correct or should i specify 1509.75 ?
I normally use 1510 and it worked fine so far,.. :)
If anyone does some additional testing please share your findings!

Cu Selur

[madhatter300871]

Made a quick test.

Input was a 1536kbs, 5.1, 48KHz, DTS track.

Encoded with dcaenc at bitrates of 1141, 1411.2, 1509, 1509.75, 1510.

1141 is a random value just to see what happens.

@1141kbps LeeAudBi shows as 1152, mediainfo shows as 1152
@1411kbps LeeAudBi shows as 1411.2, mediainfo shows as 1411.2
@1509kbps LeeAudBi shows as 1536, mediainfo shows as 1510
@1509.75kbps LeeAudBi shows as 1536, mediainfo shows as 1510
@1510kbps LeeAudBi shows as 1536, mediainfo shows as 1510

Checking the source file, LeeAudBi shows as 1536, mediainfo shows as 1510.

[Midzuki]

Made a quick test.

Input was a 1536kbs, 5.1, 48KHz, DTS track.

Encoded with dcaenc at bitrates of 1141, 1411.2, 1509, 1509.75, 1510.

1141 is a random value just to see what happens.

@1141kbps LeeAudBi shows as 1152, mediainfo shows as 1152
@1411kbps LeeAudBi shows as 1411.2, mediainfo shows as 1411.2
@1509kbps LeeAudBi shows as 1536, mediainfo shows as 1510
@1509.75kbps LeeAudBi shows as 1536, mediainfo shows as 1510
@1510kbps LeeAudBi shows as 1536, mediainfo shows as 1510

Checking the source file, LeeAudBi shows as 1536, mediainfo shows as 1510.

Sadly I forgot to mention, LeeAudBi MUST be used together with a calculator :)

As tebasuna51 said:

Exact bitrate must be calculated with Samplerate, Number of PCM Sample Blocks and Primary Frame Byte Size.

Next time please buy some bottles of ATTENTION @ the drugstore next-corner :D

P.S.: eac3to would be a better option. ;)

[tebasuna51]

...
Checking the source file, LeeAudBi shows as 1536, mediainfo shows as 1510.

Yes, LeeAudBi only read the fields in DTS header and Transmission Bit Rate show always 1536 for 1509 or 1509.75 exact bitrate.

[madhatter300871]

OK, so mediainfo is correct ?

Is the 1510kbps (or whatever) stream padded to 1536 when it is decoded ?

[tebasuna51]

Not when is decoded, but when is sended through SPDIF.
Read http://ac3filter.net/forum/index.php?topic=10.0

[madhatter300871]

Ahh, yes. I remember now. Its the sending of DTS audio over SPDIF that means audio stream needs to be padded to meet the exact bitrate if PCM. Thanks for jogging my memory.

So, just for my own clarity, DTS audio can be any legal bitrate we want, it will automatically be padded (if needed) when sending over SPDIF.

I must say in all sincerity, aren't forums just great. I have no idea how I would self teach myself without them and the ability to tap into the knowledge of all you guys.

[geminigod]

Nice link Tebasuna.

Question 1: I am still confused though as to what the exact differences are between the "wrapped & padded" DTS vs. the just "padded" DTS.

Question 2: Why do so many places say spec for DTS is 1509 even though it just pads it up to 1536 anyway? Why not just encode at 1536? There must be a reason for undershooting this number a little bit??

Question 3: Tesabuna, you mentioned a while back that it wouldn't be too hard to add w64 support to this? I think that would be a nice feature for many who might be too intimidated by the work-around of piping split wav channels through SoX.

[Selur]

@geminigod: better open another thread for that, since it's not really dcaenc related,...

[b66pak]

Question 3: Tesabuna, you mentioned a while back that it wouldn't be too hard to add w64 support to this? I think that would be a nice feature for many who might be too intimidated by the work-around of piping split wav channels through SoX.

use this:

eac3to audio.w64 stdout.wav -down16 | dcaenc -i - -o audio.dts -l -b 1509

_

[geminigod]

@ Selur: What I wrote is most definitely dcaenc related. Not sure why you would say otherwise.

@b66pak: Thanks for taking the time to suggest SoX command line advice, but also doesn't really answer my questions. I am pretty familiar with SoX, so let me respond to that code quickly for the benefit of others. First, it is pointless to down-sample it to 16 when you can upsample to 32 bit and still be compatible with dcaenc. 2nd, up until the latest release, SoX didn't work properly with w64. I provided developer Uklauer feedback regarding getting this issue resolved. Since the latest release, there is a good chance that code will work, but I can just as easily mix and pipe 6 mono wav files. Long story short, I wasn't really inquiring about w64 for my sake but more for the sake of other less tech savvy film editors.

[Selur]

for me your posts are more related to the general format specifications of dts and the usage of sox than to dcaenc itself

[Midzuki]

I was bored :) , so I decided to compile dcaenc-2

( not sure if it was worth the effort though... :o :p )

[LoRd_MuldeR]

Just for the notes: Ported back the latest changes in 'dcaenc' to my branch and bumped version to 2.
http://gitorious.org/~mulder/dtsenc/mulders-dtsenc/commit/f7c5f87a2419dde43bacd595861b5de17a8677f6

(Only relevant change seems to be "Fixed buffer overflow on attempts to encode a 7.1 file" though)

[Midzuki]

While it would be good to support this feature, we cannot rely on it.

Not all multi-channle Wave files have a WAVE_FORMAT_EXTENSIBLE header...

Even though they should. :-/

Honestly, I do not see the point of still supporting broken/non-compliant files :( IMNSHO, .WAVS with more than two channels but without the WFEXT-flag should be completely rejected (together with the weird mono and stereo .WAVs that have it). Of course, firstly Patrakov himself should have realized that it was a bad idea to repeat certain mistakes of the FLAC format in its DCA encoder. -.-

[LoRd_MuldeR]

Okay, enough is enough. I moved the off-topic discussion. Let's stay on topic again.

[Selur]

can't compile the latest version on MAC
calling:
git clone git://gitorious.org/dtsenc/dtsenc.git
cd dtsenc
aclocal
autoconf -f -i -v

I get the following output:
autoconf: running /opt/local/bin/autom4te -f --melt -v --language=autoconf --output=configure configure.ac
autom4te: the trace request object is:
autom4te: $VAR1 = bless( [
autom4te: '2',
autom4te: 0,
autom4te: [
autom4te: '/opt/local/share/autoconf'
autom4te: ],
autom4te: [
autom4te: '/opt/local/share/autoconf/m4sugar/m4sugar.m4',
autom4te: '/opt/local/share/autoconf/m4sugar/m4sh.m4',
autom4te: '/opt/local/share/autoconf/autoconf/autoconf.m4',
autom4te: 'aclocal.m4',
autom4te: 'configure.ac'
autom4te: ],
autom4te: {
autom4te: '_LT_AC_TAGCONFIG' => 1,
autom4te: 'AM_PROG_F77_C_O' => 1,
autom4te: 'AC_INIT' => 1,
autom4te: 'm4_pattern_forbid' => 1,
autom4te: '_AM_COND_IF' => 1,
autom4te: 'AC_CANONICAL_TARGET' => 1,
autom4te: 'AC_SUBST' => 1,
autom4te: 'AC_CONFIG_LIBOBJ_DIR' => 1,
autom4te: 'AC_FC_SRCEXT' => 1,
autom4te: 'AC_CANONICAL_HOST' => 1,
autom4te: 'AC_PROG_LIBTOOL' => 1,
autom4te: 'AM_INIT_AUTOMAKE' => 1,
autom4te: 'AM_PATH_GUILE' => 1,
autom4te: 'AC_CONFIG_SUBDIRS' => 1,
autom4te: 'AM_AUTOMAKE_VERSION' => 1,
autom4te: 'LT_CONFIG_LTDL_DIR' => 1,
autom4te: 'AC_REQUIRE_AUX_FILE' => 1,
autom4te: 'AC_CONFIG_LINKS' => 1,
autom4te: 'm4_sinclude' => 1,
autom4te: 'LT_SUPPORTED_TAG' => 1,
autom4te: 'AM_MAINTAINER_MODE' => 1,
autom4te: 'AM_NLS' => 1,
autom4te: 'AM_GNU_GETTEXT_INTL_SUBDIR' => 1,
autom4te: 'AM_MAKEFILE_INCLUDE' => 1,
autom4te: '_m4_warn' => 1,
autom4te: 'AM_PROG_CXX_C_O' => 1,
autom4te: '_AM_COND_ENDIF' => 1,
autom4te: '_AM_MAKEFILE_INCLUDE' => 1,
autom4te: 'AM_ENABLE_MULTILIB' => 1,
autom4te: 'AM_SILENT_RULES' => 1,
autom4te: 'AM_PROG_MOC' => 1,
autom4te: 'AC_CONFIG_FILES' => 1,
autom4te: 'include' => 1,
autom4te: 'LT_INIT' => 1,
autom4te: 'AM_PROG_AR' => 1,
autom4te: 'AM_GNU_GETTEXT' => 1,
autom4te: 'AC_LIBSOURCE' => 1,
autom4te: 'AM_PROG_FC_C_O' => 1,
autom4te: 'AC_CANONICAL_BUILD' => 1,
autom4te: 'AC_FC_FREEFORM' => 1,
autom4te: 'AH_OUTPUT' => 1,
autom4te: '_AM_SUBST_NOTMAKE' => 1,
autom4te: 'AC_CONFIG_AUX_DIR' => 1,
autom4te: 'sinclude' => 1,
autom4te: 'AM_PROG_CC_C_O' => 1,
autom4te: 'm4_pattern_allow' => 1,
autom4te: 'AM_XGETTEXT_OPTION' => 1,
autom4te: 'AC_CANONICAL_SYSTEM' => 1,
autom4te: 'AM_CONDITIONAL' => 1,
autom4te: 'AC_CONFIG_HEADERS' => 1,
autom4te: 'AC_DEFINE_TRACE_LITERAL' => 1,
autom4te: 'AM_POT_TOOLS' => 1,
autom4te: 'm4_include' => 1,
autom4te: '_AM_COND_ELSE' => 1,
autom4te: 'AC_SUBST_TRACE' => 1
autom4te: }
autom4te: ], 'Autom4te::Request' );
autom4te: running: /opt/local/bin/gm4 --nesting-limit=1024 --gnu --include=/opt/local/share/autoconf
--debug=aflq --fatal-warning --debugfile=autom4te.cache/traces.2t --trace=AC_CANONICAL_BUILD
--trace=AC_CANONICAL_HOST --trace=AC_CANONICAL_SYSTEM --trace=AC_CANONICAL_TARGET --trace=AC
CONFIG_AUX_DIR --trace=AC_CONFIG_FILES --trace=AC_CONFIG_HEADERS --trace=AC_CONFIG_LIBOBJ_DIR
--trace=AC_CONFIG_LINKS --trace=AC_CONFIG_SUBDIRS --trace=AC_DEFINE_TRACE_LITERAL
--trace=AC_FC_FREEFORM --trace=AC_FC_SRCEXT --trace=AC_INIT --trace=AC_LIBSOURCE
--trace=AC_PROG_LIBTOOL --trace=AC_REQUIRE_AUX_FILE --trace=AC_SUBST --trace=AC_SUBST_TRACE
--trace=AH_OUTPUT --trace=AM_AUTOMAKE_VERSION --trace=AM_CONDITIONAL --trace=AM_ENABLE_MULTILIB
--trace=AM_GNU_GETTEXT --trace=AM_GNU_GETTEXT_INTL_SUBDIR --trace=AM_INIT_AUTOMAKE
--trace=AM_MAINTAINER_MODE --trace=AM_MAKEFILE_INCLUDE --trace=AM_NLS --trace=AM_PATH_GUILE
--trace=AM_POT_TOOLS --trace=AM_PROG_AR --trace=AM_PROG_CC_C_O --trace=AM_PROG_CXX_C_O
--trace=AM_PROG_F77_C_O --trace=AM_PROG_FC_C_O --trace=AM_PROG_MOC --trace=AM_SILENT_RULES
--trace=AM_XGETTEXT_OPTION --trace=LT_CONFIG_LTDL_DIR --trace=LT_INIT --trace=LT_SUPPORTED_TAG
--trace=_AM_COND_ELSE --trace=_AM_COND_ENDIF --trace=_AM_COND_IF --trace=_AM_MAKEFILE_INCLUDE
--trace=_AM_SUBST_NOTMAKE --trace=_LT_AC_TAGCONFIG --trace=_m4_warn --trace=include
--trace=m4_include --trace=m4_pattern_allow --trace=m4_pattern_forbid --trace=m4_sinclude
--trace=sinclude /opt/local/share/autoconf/m4sugar/m4sugar.m4
/opt/local/share/autoconf/m4sugar/m4sh.m4 /opt/local/share/autoconf/autoconf/autoconf.m4 aclocal.m4
configure.ac > autom4te.cache/output.2t
autom4te: formatting traces for `/var/folders/KA/KA1QuiE6GRW0LBJLfWWhkU+++TI/-Tmp-//am4t1cP0fR/warnings': _m4_warn
autom4te: reading /var/folders/KA/KA1QuiE6GRW0LBJLfWWhkU+++TI/-Tmp-//am4t1cP0fR/warnings
autom4te: creating configure
autom4te: formatting traces for `/var/folders/KA/KA1QuiE6GRW0LBJLfWWhkU+++TI/-Tmp-//am4t1cP0fR/patterns': m4_pattern_allow, m4_pattern_forbid
autom4te: forbidden tokens: ^_?A[CHUM]_|_AC_|^LIBOBJS$|^_?m4_|^dnl$|^_?AS_|^_?LT_[A-Z_]+$|^_?PKG_[A-Z_]+$
autom4te: forbidden token : ^LIBOBJS$ => do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs LIBOBJS'
autom4te: allowed tokens: ^AS_FLAGS$|^SHELL$|^PATH_SEPARATOR$|^PACKAGE_NAME$|^PACKAGE_TARNAME$|^PACKAGE_VERSION$|^PACKAGE_STRING$|
^PACKAGE_BUGREPORT$|^PACKAGE_URL$|^exec_prefix$|^prefix$|^program_transform_name$|^bindir$|^sbindir$|^libexecdir$|^datarootdir$|
^datadir$|^sysconfdir$|^sharedstatedir$|^localstatedir$|^includedir$|^oldincludedir$|^docdir$|^infodir$|^htmldir$|^dvidir$|^pdfdir$|
^psdir$|^libdir$|^localedir$|^mandir$|^PACKAGE_NAME$|^PACKAGE_TARNAME$|^PACKAGE_VERSION$|^PACKAGE_STRING$|^PACKAGE_BUGREPORT$|^PACKAGE_URL$|
^DEFS$|^ECHO_C$|^ECHO_N$|^ECHO_T$|^LIBS$|^build_alias$|^host_alias$|^target_alias$|^AM_[A-Z]+FLAGS$|^INSTALL_PROGRAM$|^INSTALL_SCRIPT$|
^INSTALL_DATA$|^am__isrc$|^CYGPATH_W$|^PACKAGE$|^VERSION$|^PACKAGE$|^VERSION$|^ACLOCAL$|^AUTOCONF$|^AUTOMAKE$|^AUTOHEADER$|^MAKEINFO$|
^install_sh$|^STRIP$|^INSTALL_STRIP_PROGRAM$|^MKDIR_P$|^mkdir_p$|^AWK$|^SET_MAKE$|^am__leading_dot$|^AMTAR$|^am__tar$|^am__untar$|
^(_LT_EOF|LT_DLGLOBAL|LT_DLLAZY_OR_NOW|LT_MULTI_MODULE)$|^LIBTOOL$|^build$|^build_cpu$|^build_vendor$|^build_os$|^host$|^host_cpu$|
^host_vendor$|^host_os$|^CC$|^CFLAGS$|^LDFLAGS$|^LIBS$|^CPPFLAGS$|^CC$|^CC$|^CC$|^CC$|^ac_ct_CC$|^EXEEXT$|^OBJEXT$|^DEPDIR$|^am__include$|
^am__quote$|^AMDEP_TRUE$|^AMDEP_FALSE$|^AMDEPBACKSLASH$|^am__nodep$|^CCDEPMODE$|^am__fastdepCC_TRUE$|^am__fastdepCC_FALSE$|^SED$|^GREP$|
^EGREP$|^FGREP$|^GREP$|^LD$|^DUMPBIN$|^ac_ct_DUMPBIN$|^DUMPBIN$|^NM$|^LN_S$|^OBJDUMP$|^OBJDUMP$|^DLLTOOL$|^DLLTOOL$|^AR$|^ac_ct_AR$|^STRIP$|
^RANLIB$|LT_OBJDIR|^LT_OBJDIR$|^MANIFEST_TOOL$|^DSYMUTIL$|^NMEDIT$|^LIPO$|^OTOOL$|^OTOOL64$|^CPP$|^CPPFLAGS$|^CPP$|^STDC_HEADERS$|
^HAVE_DLFCN_H$|^CC$|^CFLAGS$|^LDFLAGS$|^LIBS$|^CPPFLAGS$|^CC$|^CC$|^CC$|^CC$|^ac_ct_CC$|^CCDEPMODE$|^am__fastdepCC_TRUE$|
^am__fastdepCC_FALSE$|^PKG_CONFIG(_(PATH|LIBDIR|SYSROOT_DIR|ALLOW_SYSTEM_(CFLAGS|LIBS)))?$|^PKG_CONFIG_(DISABLE_UNINSTALLED|TOP_BUILD_DIR|
DEBUG_SPEW)$|^PKG_CONFIG$|^PKG_CONFIG_PATH$|^PKG_CONFIG_LIBDIR$|^PKG_CONFIG$|^ALSA_CFLAGS$|^ALSA_LIBS$|^HAVE_LIBASOUND$|^HAVE_ALSA_TRUE$|
^HAVE_ALSA_FALSE$|^STDC_HEADERS$|^int32_t$|^int64_t$|^size_t$|^_UINT32_T$|^uint32_t$|^_UINT8_T$|^uint8_t$|^LIBM$|^LIBOBJS$|^LTLIBOBJS$|
^am__EXEEXT_TRUE$|^am__EXEEXT_FALSE$
when I than call:
./configure --prefix=/usr
I get:
configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.."

config.log shows this:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by dcaenc configure 2, which was
generated by GNU Autoconf 2.68. Invocation command line was

$ ./configure --prefix=/usr

## --------- ##
## Platform. ##
## --------- ##

hostname = macmini.local
uname -m = i386
uname -r = 10.8.0
uname -s = Darwin
uname -v = Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386

/usr/bin/uname -p = i386
/bin/uname -X = unknown

/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = Mach kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
Kernel configured for up to 2 processors.
2 processors are physically available.
2 processors are logically available.
Processor type: i486 (Intel 80486)
Processors active: 0 1
Primary memory available: 2.00 gigabytes
Default processor set: 52 tasks, 229 threads, 2 processors
Load average: 0.44, Mach factor: 1.56
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown

-> Does anyone know how to fix this?

Cu Selur

Ps.: Same happens on my linux systems,...

[Selur]

got it working!
The main problem was a conflict between autoconf <> automake <> m4 <> libtool versions,... ARGH,...

Cu Selur

[Midzuki]

To whom this may interest :) ,
here go the channel-orders required by the current version of dcaenc for the correct encoding of the channel layouts that "nobody uses" :rolleyes:

[2/1] ( dcaenc -c 7 )

FR, BC, FL

[2/0 + LFE] ( dcaenc -c 3 -f )

FR, LFE, FL

[2/1 + LFE] ( dcaenc -c 7 -f )

FL, FR, BC, LFE

[3/0] ( dcaenc -c 6 )

FL, FR, FC

[3/0 + LFE] ( dcaenc -c 6 -f )

FC, FL, FR, LFE

[3/1] ( dcaenc -c 8 )

FC, FL, FR, BC

[3/1 + LFE] ( dcaenc -c 8 -f )

FL, FR, FC, BC, LFE

[4/0 + LFE] ( dcaenc -c 9 -f )

FR, BL, FL, BR, LFE

[mariner]

Greetings. A few beginner's questions:

1. Can dcaenc encode 6-channel LPCM (>4GB) into dts-ma lossless? If yes, appreciate if some one can provide command line instruction starting with using eac3to to demux from m2ts file. Should W64 extension be used?

2. If not, is there any advantage using dts over 640kbps AC3? Again, command line instructions appreciated.

Many thanks and best regards.

[Selur]

Can dcaenc encode 6-channel LPCM (>4GB) into dts-ma lossless?
Nope, dcaenc 'only' creates dts and not dts-ma output.

If not, is there any advantage using dts over 640kbps AC3?
if you use the same bit rates probably not :)

[mariner]

Nope, dcaenc 'only' creates dts and not dts-ma output.


if you use the same bit rates probably not :)

Thanks for the kind reply, Selur.

What's the highest bit rate you'd recommend that's Blu-ray compatible?

[Selur]

1510 kBit/s probably gives the best hardware compatibility

[mariner]

Thanks.

1. What would be the files size for 90 min 6-channl track?
2. Is this lossless? It seems most DTS-HD MA lossless track has 1509 kbps rates.
3. Can eac3to do the same?

[Selur]

1 -> do the math yourself,.. 90min = 90*50 seconds with 1509 000 kBit per second you get 4527000000 bit
2 -> No, it's not lossless and not the DTS-MA extension is normally 1509 kBit/s the DTS core normally is.
3 -> no clue, I never use eac3to

[mariner]

Many thanks and best regards, Selur.

[tebasuna51]

...
3. Can eac3to do the same?

Some post about how use eac3to to encode with dcaenc moved to new thread dcaenc and eac3to (http://forum.doom9.org/showthread.php?p=1617506#post1617506) by Selur petition.

[Selur]

btw. did anyone compile a new version based on the latest updates with LorD_MuldeRs patch?

[SeeMoreDigital]

btw. did anyone compile a new version based on the latest updates with LorD_MuldeRs patch?I guess LoRd_MuldeR has compiled it himself for his own LameXP audio encoding application...

I wonder how far it's possible to go with DCAenc. Could say, support for DTS-ES and even DTS 96/24 be added?