what is better to use with EAC, exe or dll version of lame, since lame comes with both versions.
im asking this because i was suprised when my firewall asked me do I want to allow lame.exe to connect to the internet, and I really dont like when some unexpected applications suddenly wants to connect... why it needs to?
anyway, does it have any differences in speed, quality between encoding with exe or dll version?

the lame.exe will not connect to the internet.

maybe the connection was initiated by EAC, i erased the log but i remember that the ip where it was trying to connect was 224.0.0.***.

since you are the lame developer can you tell me is there any difference in quality and speed when i encode audio files to mp3 between lame.exe and lame_enc.dll in EAC.

i've experienced a firewall report saying lame.exe was trying to connect the net too. i was transcoding some flac files with foobar when it happened. (LAME 3.97b2)

Are you sure your firewall didn't just ask you if you want to allow
EAC to execute lame.exe?

http://en.wikipedia.org/wiki/Multicast_address

Maybe you are both using the same firewall, and this could be a bug from your firewall?
Anyway, the lame encoder that we programmed will not connect to the internet. Where did you get Lame from?

my lame is from rarewares, i'm using AVG's built-in firewall, i can't tell the IP adress it tryied to connect to (the log is already gone)

it happened only once, and my computer seemed to be heavily overloaded and instabile at the time. most probably it will be that multicast issue, although i'm not sure what it exactly is.

i personally don't think that this connection attempt is something serious, so my previous post is rather confusing

and orginally this topic should be about the dis/advanteges of .exe/.dll versions of lame, not ?

To answer the original question, with EAC you should use the .exe, not the .dll, if you want full control over the encoding parameters. And, as already stated above, lame does NOT at any time need, or request, an internet connection.

However, since version 3.97b, one no longer needs to wory about parameters, since the new version always uses highest quality settings. For example -V 5 --vbr-new is sufficient and this can be set for dll version too. So, if you want to encode on-the-fly (like I prefer to do), then the dll version is the one to chose.

no, it was asking to allow lame.exe to connect to internet.
i use Sygate personal firewall,
and Lame 3.98a2

but it is clear now, it is that multicast issue that Squeller has mentioned. i said before that i remembered the IP, was something with 224.0.0.xxx, so it must be that.

This seems to happen a lot with CLI tools and Sygate. I frequently get reports from x264, oggenc, etc. trying to send packets. Just a little annoying, bt nothing to worry about. Unfortunately Sygate has stopped support for this firewall.

Sorry if this is a little OT....
Sygate was bought by Norton, newer releases are know as Norton Personal firewall...

With the difference that the Norton Personal Firewall is far from free while the Sygate Personal Firewall was.

You can call me cheapo.

that is why im using Sygate ...for defiance to Norton (this maybe wasn't spelled good in sentence....i dont know what i exactly wrote, english is foreign language to me....)

I don't use a firewall. They tend to be more trouble than they're worth.

So long as you keep your computer otherwise secure, it's "good enough" to just be behind a router. Or nothing at all, even.