Help - Search - Members - Calendar
Full Version: CD DATA MP3
Hydrogenaudio Forums > Lossy Audio Compression > MP3 > MP3 - General
Metallo
Hi,

I managed to put 894 MB of music on a CD-R 99 Min.

Playing it this morning in my new Ford (DENSO Navigation System) car player, which supports mp3, I noticed two problems:

1) Bass is too rich, often it brings to extreme distortion
2) Often, music skips

I had the same behaviour while I was testing on CD-RW, but I wanted to try a CD-R before reporting it.

The recording source were original CDs, I used EAC and Lame 3.97b1 to convert into mp3.

Command line:
-V 2 --vbr-new --add-id3v2 --pad-id3v2 --ta "%a" --tt "%t" --tl "%g" --ty "%y" --tn "%n" %s %d

I passed everyting into mp3Gain, 90db album track gain.

I'm gonna try my standalone DVD Player and see whether the issue might just be a low quality of my car player.
Maybe an issue in reading VBR encoding??

In the meantime, should you have any other suggestion, it is very welcome.

Cheers
Alex
ezra2323
I find that stripping out all tag info (make a copy of your songs before you do this) makes them play much better in my Ford car audio system. For whatever reason, tags really mess up play.
Metallo
QUOTE(ezra2323 @ Oct 13 2005, 05:19 AM)
I find that stripping out all tag info (make a copy of your songs before you do this) makes them play much better in my Ford car audio system. For whatever reason, tags really mess up play.
*



You mean that you just use -V 2 --vbr-new and get better sound?

Alex
Metallo
Hi,

To follow up my previous post, the CD Data mp3 doesn't skip when played into my home standalone DVD Player, it's a good player and in a way I did expect this.

However, something is wrong with the encoding because the high frequencies definitely tend to hiss.

In the car player, I have the same problem but more marked and in addition when there's a peak in the track, it skips.

This is a mistery to me, unless what ezra2323 states is true, but I would be even more perplexed crying.gif

Thanks
Alex
kornchild2002
Try seeing if you get the same results when encoding at the CBR 224kbps and ABR 224kbps. Some car CD decks have hard times playing VBR mp3's eventhough they are compatible with the mp3 format. Try doing a CBR mp3 then try doing a ABR mp3 and see if you get the same results.

I have used --alt-preset standard for Lame 3.90.3 and now have switched to -V 2 --vbr-new for Lame 3.97b1. I have not had any problems with the newer or older mp3's that I encode.

I would also try tacking off the tagging commands and just let EAC do the tagging. I have always done this and have yet to run across a problematic track in my car CD deck.

Just some things for you to think about.

Edit: changed --vbr-nre to --vbr-new, bad spelling.
Metallo
QUOTE
-V 2 --vbr-nre


I guess you meant -V 2 --vbr-new, did you?

Thanks for your suggestions, I'll prepare a test disc now and try tomorrow morning.

I'll come back with results.

Cheers
Alex
dreamliner77
I think your deck may just not like the 99 min cdr.
M
QUOTE(dreamliner77 @ Oct 13 2005, 06:51 PM)
I think your deck may just not like the 99 min cdr.
*


While that could possibly explain skipping (smaller and tighter pits/lands) it shouldn't have any effect on the bass response....

- M.
Metallo
QUOTE(Metallo @ Oct 13 2005, 12:13 PM)
QUOTE
-V 2 --vbr-nre


I guess you meant -V 2 --vbr-new, did you?

Thanks for your suggestions, I'll prepare a test disc now and try tomorrow morning.

I'll come back with results.

Cheers
Alex
*



I followed the suggestions of kornchild2002 and as promised, here's the outcome:

I encoded in VBR -V 2 --vbr-new, tacking off the tagging commands and just let EAC do the tagging.

Result: Perfect CD, no skips, no hiss, no bass problems anymore.

I also, tested ABR and CBR 224, no problem at all, it sounds good.

So, my conclusion is that when letting LAME do the tagging, somewhere it messes it up.

This was also the expereince of ezra2323 in his post above.

Is anybody able to provide a logical explanation to this or is it a bug in 3.97b1?

M

As I said in my first post, I had the same issue with a CD-RW 74 min., the CD 99 has nothing to do with the problem.

Thanks for your comments
Alex
M
QUOTE(Metallo @ Oct 14 2005, 06:22 AM)
M

As I said in my first post, I had the same issue with a CD-RW 74 min., the CD 99 has nothing to do with the problem.
*


Well, apologies if my comment seemed ignorant of what you had already stated. Here's what I read:
QUOTE(Metallo @ Oct 13 2005, 07:06 AM)
I had the same behaviour while I was testing on CD-RW, but I wanted to try a CD-R before reporting it.
*


Not sure where I was supposed to infer the capacity of your CD-RW, but not important enough to argue over.

- M.
robert
maybe the car player doesn't understand id3v2 in the version used by LAME?
Metallo
QUOTE(robert @ Oct 14 2005, 04:07 AM)
maybe the car player doesn't understand id3v2 in the version used by LAME?
*



Robert,

I woould exclude that because the sound is bad in the home standalone DVD Player, which is a Hi-End one.

I guess is something technical, that's why I wanted to hear the opinion of a developer wink.gif

Thanks
Alex
dreamliner77
Just to satisfy my morbid curiosity... Try a good band CDR and see what happens.
VCSkier
i'd try -V 2 --vbr-new --id3v1-only --ta "%a" --tt "%t" --tl "%g" --ty "%y" --tn "%n" %s %d

maybe they would do better with just id3v1.
robert
QUOTE(Metallo @ Oct 14 2005, 07:35 PM)
QUOTE(robert @ Oct 14 2005, 04:07 AM)
maybe the car player doesn't understand id3v2 in the version used by LAME?
*



Robert,

I woould exclude that because the sound is bad in the home standalone DVD Player, which is a Hi-End one.

I guess is something technical, that's why I wanted to hear the opinion of a developer wink.gif

Thanks
Alex
*


Well, my Pioneer DVD player doesn't understand id3v2 tags, id3v1 only.

Did you mp3gain in your successful test above too?
Metallo
Hi guys,

I started again my encoding and at this point I'm lost. crying.gif

Reading about the configuration of Compression Options, I had undestood that if you use a LAME command line, the bit rate windows doesn't really matter what you put in because it has no influence when the command line is there.


So, I set up -V 2 --vbr-new and in the Bit rate window, I choose 320 kBit/s.

http://img384.imageshack.us/my.php?image=co3208wh.jpg

Look what happens when compressing to mp3:

http://img384.imageshack.us/my.php?image=v2vbrnew3202aa.jpg

Then, I set up -V 2 --vbr-new and in the Bit rate window, I choose VBR 192 kBit/s

http://img384.imageshack.us/my.php?image=cobitrate1927nx.jpg

Look what happens when compressing to mp3:

http://img384.imageshack.us/my.php?image=v...ewvbr1920gj.jpg


At this point, I don't know what to say more, but the question is the following:

1) Either I have seriously misunderstood what I've read so far

2) Or there must be an important part that I've missed.

Whoever has an explanation, is very very welcomed!

Thank you!
Alex

VCSkier
my opinion is that we should stick with figuring out how to get lame's internal tagging routines working correctly w/ your player. from what i understand, eac's tagging routines are inconsistent. i still would be curious to see how things turned out if you stick to just lame's id3v1 tags (using -V 2 --vbr-new --id3v1-only --ta "%a" --tt "%t" --tl "%g" --ty "%y" --tn "%n" %s %d).
Metallo
QUOTE(VCSkier @ Oct 14 2005, 11:22 AM)
my opinion is that we should stick with figuring out how to get lame's internal tagging routines working correctly w/ your player.  from what i understand, eac's tagging routines are inconsistent.  i still would be curious to see how things turned out if you stick to just lame's id3v1 tags (using -V 2 --vbr-new --id3v1-only --ta "%a" --tt "%t" --tl "%g" --ty "%y" --tn "%n" %s %d).
*



I can try and let you know...tomorrow, I'm in Europe.

Cheers
Alex
Metallo
QUOTE(Metallo @ Oct 14 2005, 11:06 AM)
Hi guys,

I started again my encoding and at this point I'm lost. crying.gif

Reading about the configuration of Compression Options, I had undestood that if you use a LAME command line, the bit rate windows doesn't really matter what you put in because it has no influence when the command line is there.


So, I set up -V 2 --vbr-new and in the Bit rate window, I choose 320 kBit/s.

http://img384.imageshack.us/my.php?image=co3208wh.jpg

Look what happens when compressing to mp3:

http://img384.imageshack.us/my.php?image=v2vbrnew3202aa.jpg

Then, I set up -V 2 --vbr-new and in the Bit rate window, I choose VBR 192 kBit/s

http://img384.imageshack.us/my.php?image=cobitrate1927nx.jpg

Look what happens when compressing to mp3:

http://img384.imageshack.us/my.php?image=v...ewvbr1920gj.jpg


At this point, I don't know what to say more, but the question is the following:

1) Either I have seriously misunderstood what I've read so far

2) Or there must be an important part that I've missed.

Whoever has an explanation, is very very welcomed!

Thank you!
Alex
*




Hi,

Can anybody confirm me if

-V 2 --vbr-new and VBR 192 kBit/s in the Bit rate window

is the right behaviour and

-V 2 --vbr-new and 320 kBit/s in the Bit rate window

is the wrong one?

Thank you
Alex



sh1leshk4
I think you should set 'User Defined Encoder' in the Parameter passing scheme setting rather than 'LAME MP3 Encoder'.
This way, the bitrate drop down list won't override whatever you fill in the 'Additional command line options'.

Read this Wiki entry.
It tells you how to set EAC to work w/ LAME properly.
Metallo
QUOTE(sh1leshk4 @ Oct 15 2005, 01:00 AM)
I think you should set 'User Defined Encoder' in the Parameter passing scheme setting rather than 'LAME MP3 Encoder'.
This way, the bitrate drop down list won't override whatever you fill in the 'Additional command line options'.

Read this Wiki entry.
It tells you how to set EAC to work w/ LAME properly.
*



If I set 'User Defined Encoder' , when i compress I get the following error:

The external compressor returned an error!
Options: -V2 --vbr-new
File: M: etc.


I don't know why. crying.gif

Any idea?

Alex
A_Man_Eating_Duck
QUOTE(Metallo @ Oct 16 2005, 07:58 AM)
QUOTE(sh1leshk4 @ Oct 15 2005, 01:00 AM)
I think you should set 'User Defined Encoder' in the Parameter passing scheme setting rather than 'LAME MP3 Encoder'.
This way, the bitrate drop down list won't override whatever you fill in the 'Additional command line options'.

Read this Wiki entry.
It tells you how to set EAC to work w/ LAME properly.
*



If I set 'User Defined Encoder' , when i compress I get the following error:

The external compressor returned an error!
Options: -V2 --vbr-new
File: M: etc.


I don't know why. crying.gif

Any idea?

Alex
*



it should be
CODE
-V2 --vbr-new %s %d


Take some time and read the guide properly
Metallo
[QUOTE]
*

[/quote]

it should be
CODE
-V2 --vbr-new %s %d


Take some time and read the guide properly
*

[/quote]


I took the time to read it, but could not find any explanation on the meaning of %s and %d, which I'm sure is evident to this community but not to me given that I cannot find an explanation of their meaning.

Thank you for pointing me to the solution.

Cheers
Alex

Acid8000
They define the source and output files.
Metallo
QUOTE(Acid8000 @ Oct 16 2005, 01:05 AM)
They define the source and output files.
*



Thank you Acid.

Regards
Alex
A_Man_Eating_Duck
QUOTE(Metallo @ Oct 16 2005, 08:57 AM)
QUOTE
*
it should be
CODE
-V2 --vbr-new %s %d
Take some time and read the guide properly
*
I took the time to read it, but could not find any explanation on the meaning of %s and %d, which I'm sure is evident to this community but not to me given that I cannot find an explanation of their meaning.

Thank you for pointing me to the solution.

Cheers
Alex
*
ok, i'll add something to the guide to explain %s %d
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.