View Full Version : delaycut - ac3/eac3/dts/mpa/wav delay+cut tool: v1.4.3.7
Selur
20th April 2012, 12:30
delaycut -fixcrc fix -inputtype milliseconds -startdelay -1190 -o "D:\Encoding Output\fixDelay_ger_aid_6122__13_26_48_111_06.ac3" -i "D:\Encoding Output\fixDelay DELAY -1190ms_ger_aid_6122__13_26_48_111_05.ac3"
triggers an unwanted 'milliseconds' Popup-Window, would be nice if this would NOT happen when called through the command line (better output something to std::cerr or std::out)
+ delayac3.cpp misses:
#include "math.h"
+ some thing it wrong with delaycut.pro, using:
QT += core gui
CONFIG += qt \
console
TARGET = delaycut
!win32 {
target.path = /usr/bin
INSTALLS += target
}
TEMPLATE = app
SOURCES += main.cpp\
delaycut.cpp \
delayac3.cpp \
dragdroplineedit.cpp
HEADERS += delaycut.h \
sil48.h \
delayac3.h \
types.h \
dragdroplineedit.h
FORMS += \
delaycut.ui
RESOURCES += \
delaycut.qrc
RC_FILE = delaycut.rc
works fine on Linux&Mac
Cu Selur
hlmasterchief93
24th June 2012, 11:12
sorry, but how to compile delaycut in ubuntu ?
i check the README but i cant see the instruction
i use
git clone git://github.com/athomasm/delaycut.git
cd delaycut
qmake
make
and it's returned error
g++ -m64 -Wl,-O1 -o delaycut -L/usr/lib/x86_64-linux-gnu -lQtGui -lQtCore -lpthread
/usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/crt1.o: In function `_start':
(.text+0x20): undefined reference to `main'
collect2: ld returned 1 exit status
make: *** [delaycut] Error 1
Selur
24th June 2012, 11:20
Did you try the changes I posted above? (adjusting delaycut3.cpp and delaycut.pro)
Compiling works fine for me with these changes (on ubuntu 32/64 and mac osx x)
Snakekick
12th July 2012, 15:52
@Selur
sorry for my question but how do i make this changes?
i did not have the file delaycut3.cpp
qmake give not response and make give me the same error @hlmasterchief93
**Edit***
delaycut3.cpp== delayac3.cpp
Selur
12th July 2012, 15:57
i did not have the file delaycut3.cpp and delaycut.pro
That is strange since, qmake generates the MakeFiles by looking into the delaycut.pro file and they are both listed over at: https://github.com/athomasm/delaycut
I see I made a typo delaycut3.cpp should be delayac3.cpp ;)
Overdrive80
12th February 2013, 00:48
Hi guys, I want remove a segment of ac3 file. I put a example:
First part: 0ms-5000ms
Secong part: 6000ms-end
Of this way, I would remove 999ms intermediate. ¿How I should configure delaycut for it?
Sparktank
16th February 2013, 00:50
Hi guys, I want remove a segment of ac3 file. I put a example:
First part: 0ms-5000ms
Secong part: 6000ms-end
Of this way, I would remove 999ms intermediate. ¿How I should configure delaycut for it?
MKVtoolnix has a function (newly implemented) to trim given specific time lengths.
Which is perfect for trimming the beginning and/or the end of a compliant Matroska file.
Mux the AC3 into an MKA (Matroska Audio) using mmg (http://www.videohelp.com/tools/mkvtoolnix) and apply the splits you want.
Documentation on the -split function here.
http://www.bunkus.org/videotools/mkvtoolnix/doc/mkvmerge.html#mkvmerge.description.split
You can later demux the AC3 using MKVtoolnix (http://www.videohelp.com/tools/mkvtoolnix) with MKVExtractGUI (http://www.videohelp.com/tools/MKVExtractGUI-2) or other tool.
tebasuna51
16th February 2013, 12:40
@Sparktank
The easy way is use, like a say to Overdrive80 in other post, eac3to:
eac3to input.ac3 output.ac3 -edit=0:00:05.000,-1000ms
(remove 992ms without recode)
With DelayCut we can Cut first part 0 to 5000ms, obtain the second part with a -6000ms Delay and after join the 2 parts.
mariner
16th February 2013, 16:24
@Sparktank
The easy way is use, like a say to Overdrive80 in other post, eac3to:
eac3to input.ac3 output.ac3 -edit=0:00:05.000,-1000ms
(remove 992ms without recode)
With DelayCut we can Cut first part 0 to 5000ms, obtain the second part with a -6000ms Delay and after join the 2 parts.
Greetings tebasuna51.
How about inserting silence? Would a + sign work for both cases?
Can multiple edits be performed by a single command line?
Many thanks and best regards.
tebasuna51
16th February 2013, 17:15
To insert 1000ms of silence:
eac3to input.ac3 output.ac3 -edit=0:00:05.000,1000ms -silence
(with values less than 1000ms the default for eac3to is loop the previous frames)
mariner
16th February 2013, 20:20
Many thanks, tebasuna51.
1. eac3to doesn't like -edit=0:00:00.000,12750ms -silence. Minimum start time accepted is 13s. What could be wrong? It's a 6-channel 448kbps AC3 stream.
2. One command for each edit point?
tebasuna51
16th February 2013, 21:04
If you want a initial delay is enough:
eac3to input.ac3 output.ac3 +12750ms
mariner
17th February 2013, 12:30
@Sparktank
The easy way is use, like a say to Overdrive80 in other post, eac3to:
eac3to input.ac3 output.ac3 -edit=0:00:05.000,-1000ms
(remove 992ms without recode)
With DelayCut we can Cut first part 0 to 5000ms, obtain the second part with a -6000ms Delay and after join the 2 parts.
To insert 1000ms of silence:
eac3to input.ac3 output.ac3 -edit=0:00:05.000,1000ms -silence
(with values less than 1000ms the default for eac3to is loop the previous frames)
If you want a initial delay is enough:
eac3to input.ac3 output.ac3 +12750ms
Many thanks for these excellent beginner's guides.
Would you be kind enough to also look at a related problem posted here?
http://forum.doom9.org/showthread.php?p=1615955#post1615955
Best regards.
tebasuna51
18th February 2013, 13:15
Would you be kind enough to also look at a related problem posted here?
http://forum.doom9.org/showthread.php?p=1615955#post1615955
Seems a tsMuxeR problem not related with Delaycut or eac3to.
But you can use Delaycut or eac3to to avoid the problem.
When you add a delay here to a ac3 track, silent phisycal frames are added to the ac3 and you don't need add timeshift in audio/video containers.
If you need a delay >4935ms for a ac3 track in m2ts container, first use:
eac3to track.ac3 new_track.ac3 +4960ms
and you can now add the new_track to tsMuxeR without timeshift.
mariner
19th February 2013, 16:22
You're right. Will post reply at tsMuxeR thread.
Once again, many thanks and best regards.
djmasturbeat
25th February 2013, 16:47
delaycut v1.4.3.7 hangs on "crc errors - silence" mode for some files
it just makes zero progress
fixed file remains at zero kb even after an hour
also delaycut becomes unresponsive and won't respond to abort
(but it will close out with the X at upper rt)
esaxple log :
[Input info]
Bitrate=448
Actual rate=448
Sampling Frec=48000
TotalFrames=193208
Bytesperframe=1792.0000
Filesize=346228957
FrameDuration= 32.0000
Framespersecond= 31.2500
Duration=01:43:02.659
Channels mode=3/2: L+C+R+SL+SR
LFE=LFE: Present
[Target info]
StartFrame=0
EndFrame=193207
NotFixedDelay= 0.0000
Duration=01:43:02.624
1.3.0.0 performs quickly on same files, a matter of seconds.
if you need a sample please feel free to pm me.
GCRaistlin
2nd November 2013, 16:35
Is delaycut still being developed? There's some bugs there, has it any sense to report them here?
Selur
2nd November 2013, 16:37
no clue, but even if it's not developed any more atm. development might start again, so reporting to the bug tracker always is a good idea.
GCRaistlin
2nd November 2013, 16:42
Selur, you mean reporting here, or there's a special bugtracker for delaycut?
Selur
2nd November 2013, 16:46
Best report to the bug tracker on the project home page: https://github.com/athomasm/delaycut/issues
XMEN3
4th April 2015, 15:39
Hi, i know that eac3to fixes delay in both dts and dtshd tracks when extracting, is possible implement this frame fix on this software?
Sparktank
4th April 2015, 19:46
https://github.com/athomasm/delaycut/issues
I get 404 on that.
Even if I reduce to just athomasm, it's 404.
Someone mirrored it here:
https://github.com/darealshinji/delaycut
tebasuna51
17th November 2016, 02:23
I get 404 on that.
Even if I reduce to just athomasm, it's 404.
Someone mirrored it here:
https://github.com/darealshinji/delaycut
Where there are a new v1.4.3.8, but seems buggy.
Only loading a test ac3 file we can see differences between DelayCut versions:
= INPUT FILE INFO =================
v1.3.0 CORRECT v1.4.3.7 v1.4.3.8
---------------- ---------------- ------------------
File is ac3 ac3 ac3
Bitrate (kbit/s) 192 192 448 (?)
Act rate (kbit/s) 192.000 192.000 448.000 (?)
File size (bytes) 480000 480000 480000
Channels mode 2/0: L+R 2/0: L+R 2/2: L+R+SL+SR (?)
Sampling Frec 48000 48000 48000
Low Frec Effects LFE: Not present LFE: Not present LFE: Present (?)
Duration 00:00:20.000 00:00:20.000 00:00:08.571 (?)
Frame length (ms) 32.000000 32.000000 32.000000
Frames/second 31.250000 31.250000 31.250000
Num of frames 625 625 267 (?)
Bytes per Frame 768.0000 768.0000 1792.0000 (?)
Size % Framesize 0 0 201 (?)
CRC present: YES YES YES
= TARGET FILE INFO ================ ============= ==============
Start Frame 0 0 0
End Frame 624 624 266 (?)
Num of Frames 625 625 267 (?)
Duration 00:00:20.000 00:00:19.968 (?) 00:00:08.512 (?)
v1.4.3.7 is buggy because do a wrong calculation of target file duration.
Then always than I want a cut output one more frame than needed, if I want 3200 ms (100 frames) output 101 frames (3032 ms).
But v1.4.3.8 detect wrong Bitrate, Channels, LFE, etc. (reported here (https://github.com/darealshinji/delaycut/issues/4))
EDIT:
After some changes here is a build than work better than v1.4.3.7: delaycut_testbuild (https://github.com/darealshinji/delaycut/files/602290/delaycut_testbuild.zip)
tebasuna51
27th February 2017, 17:02
New release v1.4.3.9 here https://github.com/darealshinji/delaycut/releases
manolito
27th February 2017, 21:48
@tebasuna
Too bad but for v1.4.3.9 there is no qt4 build which means that it won't run under my WinXP...
Question:
In this post:
https://forum.doom9.org/showthread.php?p=1797824#post1797824
there is a link to a beta version which also contains a qt4 build. This build runs fine, so I'd like to know if the bugs from v1.4.3.8 are fixed in this beta version?
Thanks and Cheers
manolito
tebasuna51
27th February 2017, 22:59
... This build runs fine, so I'd like to know if the bugs from v1.4.3.8 are fixed in this beta version?
I'm not tested all the options but seems OK for me.
manolito
27th February 2017, 23:18
:thanks:
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.