View Full Version : acid vs. besweet auto gain detection
mOE
21st January 2002, 19:03
Hi
I have a problem with the autodetection of gain offset in beSweet (the version from DVD2SVCD 1.0.6 b1 bundle). The found offset is too high. It finds an offset of 15.1 dB.
Azid from version 1.0.5 finds 14.7 dB...
When beSweet encodes the audiostream I get an overflow and in the result mp2 file is a click.
Why???
DSPguru
21st January 2002, 19:41
very interesting.
did BeSweet print an overflow error message while transcoding ?
mOE
22nd January 2002, 07:53
Yes, it printed "overflow +0dB" or something like that. but only once. And at this position in the encoded audio file the signal is amplified too much and beSweet produces a very loud click.
The rest is okay.
The movie was Pearl Harbor - German audio stream at position 00:05:31...
sandchar99
22nd January 2002, 18:29
Same thing as above.
Back-up: Final Fantasy NTSC, Region 1
Loud clicks in the beginning silence (movie banner, approximately 5 seconds) before there is any regular soundtrack audio.
Otherwise, DVD2SVCD 1.06b1 works great. I look forward to having gain settings readjusted because I love how DSPGuru's BeSweet eliminates the huge intermediate WAV files.
Sorry, I was not watching to see if there was an overflow message during transcoding.
mOE
23rd January 2002, 07:45
And for me in DVD2SVCD 1.0.6 it is not possible to disable the 2pass gain detection and choose the gain manually. If I do that beSweet still detects the gain itself...:eek:
And finds always the wrong one.
daxab
23rd January 2002, 18:31
I saw BeSweet complain about a CRC error once during the gain detection pass.
sandchar99
23rd January 2002, 21:21
Follow-up: Loud Clicks in Final Fantasy
Used older version of DVD2SVCD, 1.05b4, and started DVDSVCD using the VOBs that I had already ripped using internal routines in v1.06b1 with files going to a different folder.
Proceeded thru Audio encoding (the old way-AZID-->toolame)and stopped when mp2 file was completed. I renamed the new mp2 to be compliant with DVD2SVCD v1.06b1 and placed it back in the original directory. I erased the muxed files and CD image files and used crash recovery to start at Muxing and then CD Image creation.
The result was that the new sountrack did not have any clicks or pops.
Another back-up "Blow" (NTSC, Region 1) did not have any clicks or pops with DVD2SVCD 1.06b1.
So, BeSweet may have problems with gain when the soundtrack has only a narrow range, low (near subsonic) frequency.
markrb
23rd January 2002, 23:02
So this must have been the problem I was having on Gladiator. I thought that my bitrate was too high, even though I have encoded many movies at the same bitrate with no problems.
It must have just been coincidence that the clicks went away when I re-encoded. It also happened on Scary Movie 2 at lower bitrates.
Mark
DSPguru
24th January 2002, 07:39
thank you guys for all the info :)
i will look for the normalization issue.
one small request :
when you report bugs, please make sure you were using the latest stable release of BeSweet (v1.0 ATM).
10x.
mOE
24th January 2002, 07:47
It's pretty shitty that beSweet sometime does these clicks. The biggest problem for me is I realize that the audio isn't okay only after I burned the images and erased everything... :devil:
I hope DSPguru will resolve this prob because besweet is much more effective than the old audio procedure.
markrb
24th January 2002, 08:02
DSPguru I think most of us are in the same boat. We are tied to the releases of the DVD2SVCD bundle. We have been told NOT to upgrade unless told by DVD2SVCD to do so and so far this has never happened. Of course with a new release comes a new bundle and many times new versions of the software.
However I believe the only way to get the newest version is to get the beta bundle of DVD2SVCD unless I am mistaken.
Also I have noticed that Besweet doesn't seem to make a log file when running in DVD2SVCD. Without a log file it becomes difficult to track down problems. Does Besweet normally generate a log file?
Mark
DSPguru
24th January 2002, 08:18
in fact, dvd2svcd should have made a new bundle a week ago, when i released Stable v1.0.
BeSweet can create a logfile. "-core( -logfile file.txt)".
mayB dvd2svcd will use it on the next bundle..:confused:
dvd2svcd
24th January 2002, 08:47
I know, I know. BUt I ran into some more bugs I wanted to fix first, sorry. Anyway, it should be safe to use BeSweet 1.0 (not b1 or b2). In any event, there's a link to a pre release in the "CCE Crash, the quest continues" that you can download and install.
DDogg
24th January 2002, 17:03
Just to make it clear, when I upgraded to B1 or B2 I got a hard nasty crash than only a power down would unfreeze. To the best of my knowledge, the only release of besweet that works with dvd2svcd is the one that says simply v1.0. If it has a "b" after it, it will not work on my xp machine. Perhaps this is something only to do with my machine. Anyway, the old addage about not upgrading sofware versions of individual apps still seems wise. The link mentioned above has the right one in it and works well.
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.