delaycut - ac3/eac3/dts/mpa/wav delay+cut tool: v1.4.3.7

I have ported delaycut from MFC to Qt and am at a point to release it as a beta to get others to test it.

Source code is at: https://github.com/athomasm/delaycut

Any feedback, bug reports, requests are welcome.

Version 1.4.1.0
- Added back CLI support.

Version 1.4.2.0
-Fix crash for opening file names with Unicode characters.

Version 1.4.3.0
- Add option to select input type between milliseconds, seconds, frames. Can add both rational values (24000/1001) or decimal (23.976) values in FPS field.
- Removed debug info being displayed in message box that was accidently left in.
- Added CLI switches to support new input value types.

Version 1.4.3.1
- Fix so that delay fields properly accept negative values.
- Fix for math when using frames as input type.

Version 1.4.3.2
- Fix autodelay detection so that it converts ms value in fileName to the selected input type.
- Fixed bugs in converting values between different input types.
- Fixed math errors when specifying delay in frames.
- Fixed bug where output file path wasn't updated when using Save As dialog.

Version 1.4.3.4.
-Fix rounding when converting between input types to a round half up scheme. Also changed the calculations for start and end frame to use the same.
-Fixed check for enabling the CRC group edit so it enables properly.
-Fix bug that where a pathological file caused the processing to never finish and UI hang.
-Calculated end frame is capped to the total frames in cases where end split value specified exceeds length of file.
-Renamed "original length" field to "preserve length".
-End cut value of 0 is treated as end of file when calculating end frame.
-End cut and start cut values no longer cause the other field to be overwritten. All checks to make sure that end cut is not smaller than start cut, except for the case of 0, happens when process button is clicked.

Version 1.4.3.5
-Logging of progress and error messages when using the CLI have been added back.
- "-console" switch has been removed. Switches to specify cut points have been renamed to "-startcut" and "-endcut" respectively. Switches to specify delay values have been renmaed to "-startdelay" and "-enddelay" respectively. "-i" switch introduced to allow the specifying of the input file path anywhere in the CLI arguments. "-version" switches introduced to get the current version of the software.

Version 1.4.3.6
-Added support to specify delay/cut values in audio frames.
-Added "-help" switch to display the options available from CLI.
-Fixed so that delay field in GUI worked properly.
-Fixed CLI parser for to detect new switches.

Version 1.4.3.7
-Fixed logic bug when checking valid input types.
-Fixed output of -help and the README to the proper names of the new switches.

Usage:

Command Line Instructions
Output and log files will be in the same path than the input file.

Options:
-help:                 List options.
-version:              Get current version.
-info:                 Outputs info about input file in log file
-inputtype <string>:   Input type of delay/cut values. (default millseconds 
                       when not specified) [milliseconds, seconds, videoframes]
-fps <float|rational>: Specify frame rate.
                       Needed when inputtype is set to frames. 
-fixcrc <string>:      Specify action to take in the case of crc errors
                       [ignore, skip, fix, silence]
-startdelay <integer>: Specify the needed frames added at the beginning of the file
-enddelay<integer>:   Specify the needed frames added at the end of the file
-same:                 file length will be the same after adding delay
-auto:                 detect start delay in filename (assuming DVD2AVI style)
-startcut <integer>:   Specify cut start point
-endcut <integer>:     Specify cut end point
-o <string>:           specify output file
-i <string>:           specify inputfile

Return values
0: Success
1: Something went wrong.

Examples:
Get info: Log file will be myfile_log.txt
    delaycut -info -i myfile.ac3

Adds 100 msec of silence at the begining. File lenght will be the same
    delaycut -startdelay 100 -same -i myfile.ac3

Adds 100 msec of silence at the begining. File lenght will be 100 msecs more
    delaycut -startdelay 100 -i myfile.ac3

Cuts start at 10.32 sec and ends at 15.20 sec.
    delaycut -inputtype seconds -startcut 10.32 -endcut 15.20 -i myfile.ac3

Cuts start at 10320 msec and ends at 15200 msec. Delay correction of 100 msec.
    delaycut -startdelay 100 -startcut 10320 -endcut 15200 -i myfile.ac3

[b66pak]

thanks a lot...
_

You're welcome. I'm not sure how many people still use it, but it was a simple enough app that I've been working on to learn Qt and get back into C++. After I get the CLI part reimplemented and some refactoring done tonight (since the old delaycut code was just a quick and dirty import and get it compiling job) and no one mentions any major bugs I'll push it out as a real release.

As far as I can tell from my so far limited testing file output is identical to the last delaycut release (verified with sha-1 hashes).

[Thunderbolt8]

not sure whether I understand, but version 1.3.0.0 does already exist, madshi made that one.

so whats the difference here?

I didn't know he had I just diverged from the last version from jsoto's site. This is different in that it's written in Qt so it's cross-platform. And I'll change the version number. Can you link his version? I'd love to incorporate any changes he made

Never mind I found madshi's version. When I get home I'll incorporate his changes and change the version number.

[Thunderbolt8]

so what exactly are your changes? (in case you stated them above, I cant understand that, sorry )

Its rewritten in Qt to be cross-platform, for those who care, and when I'm done tonight a significantly cleaned up codebase. At that point more functionality, etc can be added per any requests, etc.

As I said above this is mostly for me learning Qt and getting back into c++ programming. I thought I'd share in case anyone else was interested.

Plus I know there are other tools that do the same thing but none are as simple to use as this, IMO, so I thought I'd try to revive it. It's just one of a number of older mfc-based tools I've been working on porting.

[shh]

Win7x64: I click "Browse" for an input file, then break (don't select anything) -> crash

Ok, I see the issue. Fixing now. Fix will be in the newest version with the eac3 support. Removing the download link till I get the new version up.

New version renamed to 1.4 beta is ready to grab here.

This has the file dialog fix, adds eac3 support from madshi's 1.3.0.0 and adds support to autofill delay values set in the file that Chumbo added in 1.3.1.0.

Working on getting LiveCDs for Debian and Ubuntu to get generate deb packages for Debian 6, and Ubuntu 11.04 and 11.10. Will update when they are created.

[Sparktank]

Neat!

Any chance of adding more file support?
Like the lossless streams: DTSHD-MA, Dolby TrueHD, FLAC, w64?

Would come in handy when editing isolated scores from Blu-Ray.

Sure, I'll add it into the TODO list.

[Sparktank]

Originally Posted by amtm

Sure, I'll add it into the TODO list.

There's no rep or thanks buttons in doom9

For anyone who cares I have binaries here for Linux. Builds include Debian 5 & 6, Ubuntu 9.10 - 11.10, OpenSuSE 11.3-4, 12.1, Factory and Tumbleweed, and Fedora 15/16.

[pandv2]

It's the cli part implemented? I tried -info and the gui appears.

Thank's.

I've got it implemented locally just not pushed yet. I'll have it in tonight and new binaries.

Version with CLI support back in: https://github.com/downloads/athomas...ycut1.4.1.0.7z

Additional items still on the TODO list will be worked on but I will be busy the next couple of days so it probably won't be a new version until next week.

A question for users. On videohelp forums someone wanted to have the delay and cut fields support input values in seconds. I was thinking of having the user type s at the end to let the program know that the value isn't milliseconds and without that it just defaults to the normal behavior. Does that sound okay?