Exactly what options in EAC are changed when installing Omni Encoder? I ask because I had saved my default (complete) profile in EAC, then saved (compression) only profiles for using either LAME, LAME+EAC id3 tagging, or Omni. I found that after installing Omni, if I tried to load one of my (compression) only LAME profiles, the wrong commandline was used regardless that the lame.exe path was correct in EAC's compression settings. It's impossible to see the entire commandline that is called, but it looks like EAC is still trying to call the EACEncoder.exe file in the Omni directory.
If I reload my default (complete) profile my LAME encodes once again work as they should. After reloading my default (complete) profile, if I try to load the Omni (compression) only profile, I get errors and it doesn't work. Once again, it passing the wrong commandline/path, but I cannot see exactly what it is trying to send. A little help please?
All I've been doing is overwriting the settings registry key. I've never tried saving profiles, to be honest, so i'm not sure how it works on a registry level. I'll play around with it tonight.
Just tried this for converting Flac 1.1.0 files (-5 and -8) to Flac 1.1.3 (-8) -- and I'm noticing
1) even though I have 'include Flac comments' checked, they aren't preserved in the reencoded flacs
2) the 'composer' tag isn't preserved (and I have lots of classical files to re-encode
Omni Encoder, by virtue of its multi-codec design, doesn't really "pass through" tags so much as read them out, and then retag the resulting files with those values. So what I mean is, the only fields that get used are the ones you see in the GUI... stuff like composer is going to get lost.
You raise a good point though with classical... I want to add custom tag fields as well, but "composer" might be a good one to add right to the current interface.
For now you might want to try that "FLAC Frontend" app for straight reencoding with FLAC.
Are you having problems with the standard fields though (artist, album etc?)
