autocue : need a little improvement (but so obvious to code)

[Michael REMY]

hi,

i just used the autocue feature for the first time (in more than 6 years of golwave uses).

why didn't you add this 2 columns (track length and silence length) in the windows result after we use the autocue feature ?

these 2 columns are so useful to determine if we got a good cut or not (detect short tracks or long ones, bad cuts..)

http://www.pix-host.com/allimages/55177798.jpg

i hope you will add this in the next goldwave release !

have a good day

[DewDude420]

Probably because the program isn't generating a track length or silence length while doing the process. It's just looking for silence, marking the cue, and going on.

CUE files don't have a provision for either of those two options, so it's a waste to generate them.

You can look at your overall file and see cue flags at cue points; this should be enough to tell you if there's a proper cut.

[Michael REMY]

i don't speak about the information in the cue file,
i speak about the information detected after the first pass who "guessed" the cue information.