Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Introducing Omni Encoder (Read 40415 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Introducing Omni Encoder

Omni Encoder is a multi-format audio conversion utility (front-end). This beta includes AAC and MP3 support, with Vorbis and FLAC support planned soon.

The beta download is temporarily offline while version 1.0 is completed internally.

It is released under the GPL, and sources (Visual Studio 2005 solution, written in C#) are available as well.

Key Features:
  • Modular design - new encoders and tagging engines can be added with ease. Currently includes modules for Lame MP3, Nero and Apple AAC, Ogg Vorbis, MPC, Apple Lossless and FLAC.
  • EAC integration - Use the best ripper out there, and have it intelligently pass track information to Omni Encoder.
  • WaveGain pre-processing - Automatically run an album or track gain analysis, then have the encoder adjust by that amount.
  • Tag preservation - Omni Encoder will automatically read and then re-write tags to the new format, if desired.
  • Automatic cover art downloading - Have Omni Encoder automatically retrieve cover art from the internet, in a single click or less!
Beta Information:

The beta is over, and the final version shall be released soon (read: before Christmas). I just have a few more things to iron out first. Read my post towards the end of this thread.

Introducing Omni Encoder

Reply #1 –
Just looked at it briefly, but you might consider a few of the things REACT, MAREO, etc. can do:
  • Multiple format encodings (e.g., to allow encodings to a lossless and lossy format at the same time)
  • The ability to save and load configurations
  • The ability to use both GUI and command line settings for the encoders (similar to foobar)
  • Custom field tagging (especially in id3v2)
  • Ability to integrate with other programs (e.g., foobar, etc. similar to MAREO)
  • Ability to either download album info from the web or to call up a tagging program that can do it.
  • Alternate configurations for Various artists albums.

IMO, A good encoding program should take out some of the multiple steps to get the audio files ripped securely, analyzed for replaygain, tagged (with albumart and Allmusic Guide level of album information), and placed in their correct file structure location.  I currently use EAC + REACT to automate pretty much the entire rip process.  It requires user input for initialization of ripping, selecting whether or not various artists, albumart confirmation, and lookup and tagging by a 3rd party tagger.  It would be nice to see all of this in one GUI.

Good luck.

Introducing Omni Encoder

Reply #2 –
Quote from: Gabes Dad on
Just looked at it briefly, but you might consider a few of the things REACT, MAREO, etc. can do:
  • Multiple format encodings (e.g., to allow encodings to a lossless and lossy format at the same time)
  • The ability to save and load configurations
  • The ability to use both GUI and command line settings for the encoders (similar to foobar)
  • Custom field tagging (especially in id3v2)
  • Ability to integrate with other programs (e.g., foobar, etc. similar to MAREO)
  • Ability to either download album info from the web or to call up a tagging program that can do it.
  • Alternate configurations for Various artists albums.
IMO, A good encoding program should take out some of the multiple steps to get the audio files ripped securely, analyzed for replaygain, tagged (with albumart and Allmusic Guide level of album information), and placed in their correct file structure location.  I currently use EAC + REACT to automate pretty much the entire rip process.  It requires user input for initialization of ripping, selecting whether or not various artists, albumart confirmation, and lookup and tagging by a 3rd party tagger.  It would be nice to see all of this in one GUI.

Good luck.
  • Multiple format ripping made the program dramatically more complex, and given that Omni Encoder preserves tags, you can for instance rip right to FLAC from EAC, then just change the encoder, hit "convert" again to create the other format (MP3 or whatever). Yeah, it's one extra step, but it sure shaved a lot of compexity out of the program!
  • Configurations are saved on a per-encoder basis, so I don't see the need just right now. Maybe once more features are added, profiles could become a requirement.
  • I might add an "override" option, but I haven't decided... I think it would just be better to include all sensible options in the GUI.
  • More tagging options (like custom fields in id3v2) are definitely planned.
  • Well, it already integrates with EAC. There are no plans to integrate with foobar, purely because I don't use foobar. If someone else wants to code something, then be my guest!
  • Since this integrates with EAC, usually tag info is grabbed there. I might add this feature to Omni Encoder natively, but I want to see what is going on with freedb2 et al. first.
  • Good idea.
Thanks for your feedback! The idea is very much to automate the entire process - in a sensible way. Right now it does this already, according to my expectations. Hopefully with some work, it will fill your expectations as well.

Introducing Omni Encoder

Reply #3 –
Quote
EAC integration - Use the best ripper out there, and have it intelligently pass track information to Omni Encoder.


Well that's entirely subjective  . Need we not forget about the dBPowerAmp and some other secure rippers.  Overall though I would say that your front-end is coming along quite nicely keep up the good work.
budding I.T professional

Introducing Omni Encoder

Reply #4 –
I like it...A suggestion: instead of having to copy the nero files to the install directory, have an option in the preferences to browse to the nero executables.

Edit: only .wav is supported as input?

Introducing Omni Encoder

Reply #5 –
Well, I know we're not supposed to complain... but I go to all this trouble for you guys, and I get rejected as a news item?

Quote from: =trott= on
I like it...A suggestion: instead of having to copy the nero files to the install directory, have an option in the preferences to browse to the nero executables.

Edit: only .wav is supported as input?


That's an idea. If you don't like having them in 2 places though you could always use shortcuts, or add them to PATH. I think that would work.

No, any module you add will allow for input AND output of that format.

Quote from: HotshotGG on
Quote
EAC integration - Use the best ripper out there, and have it intelligently pass track information to Omni Encoder.


Well that's entirely subjective  . Need we not forget about the dBPowerAmp and some other secure rippers.  Overall though I would say that your front-end is coming along quite nicely keep up the good work.


And it should be really easy to add support for those as well.

Introducing Omni Encoder

Reply #7 –
Quote from: Garf on
Quote from: Jebus on
Well, I know we're not supposed to complain... but I go to all this trouble for you guys, and I get rejected as a news item?


We go through all this trouble to make stickies and README's, and you keep ignoring them?

http://www.hydrogenaudio.org/forums/index....showtopic=20857


Well, i missed the one about the exclamation mark... but as far as the screenshot goes, I tried adding it as the second post, but the new board software just joins the posts together if they are from the same person! Would it be possible to resubmit this thread with edits? Seems clunky to create a new one just to change the title. Mods?

Introducing Omni Encoder

Reply #8 –
Quote from: Jebus on
I tried adding it as the second post, but the new board software just joins the posts together if they are from the same person! Would it be possible to resubmit this thread with edits? Seems clunky to create a new one just to change the title. Mods?


I'll edit your starting post to something which I feel would be fit for a news submission.

Good point about the automatic joining of posts. Perhaps that feature should be disabled again.

Introducing Omni Encoder

Reply #9 –
Quote from: Garf on
Quote from: Jebus on
I tried adding it as the second post, but the new board software just joins the posts together if they are from the same person! Would it be possible to resubmit this thread with edits? Seems clunky to create a new one just to change the title. Mods?


I'll edit your starting post to something which I feel would be fit for a news submission.

Good point about the automatic joining of posts. Perhaps that feature should be disabled again.


Thanks Garf!

Introducing Omni Encoder

Reply #10 –
Quote from: Garf on
Good point about the automatic joining of posts. Perhaps that feature should be disabled again.

it doesn't autojoins if you wait a certain (5? 10? 15?) mins.

Introducing Omni Encoder

Reply #11 –
Jebus

nice work. Like where it's heading. I have one request: could you please provide a non-installer version?  A zip version that can be unzipped and run would be great.

thanks

Introducing Omni Encoder

Reply #12 –
Quote from: kanak on
Jebus

nice work. Like where it's heading. I have one request: could you please provide a non-installer version?  A zip version that can be unzipped and run would be great.

thanks


Yeah, I guess so... it is just an xcopy application after all (no registry footprint beyond the EAC one it overwrites). Check the site in about 15 minutes.

quick update: Vorbis module has been added in Trunk... tagging is an issue though as I'm not sure the best way to handle multiple tag formats (what if someone wants to add APE2 and ID3v1 tags?). Gonna have to ponder that and make some API changes before beta 2.

Introducing Omni Encoder

Reply #13 –
Uploaded verison 0.1.1, which fixes a few bugs, and adds the option to specify whether you want a Folder.jpg generated when art is available.

I probably won't do another release until 0.2, which as mentioned will include Vorbis, FLAC, and more robust tagging options.

Introducing Omni Encoder

Reply #14 –
Request for comments: What tag types are do people use for the following formats:

MP3: I know ID3v1 and ID3v2, but also APE2, correct? Any need for APE1 and/or Lyrics3 tags?
Vorbis: I don't use vorbis, so my understanding is that they commonly use Vorbis comments, ID3v1, and APE2? Corrections, ommisions?

I need feedback because the tagging system needs an overhaul before i integrate any more codec modules.

Introducing Omni Encoder

Reply #15 –
I'm about to buy a new dual core CPU thanks to AMDs price reductions. I have about 100 GB of FLAC files that I want to encode to LAME MP3, is it possible to run two instances of this front end and encode with two instances of LAME set to each CPU core, without anything conflicting?

Introducing Omni Encoder

Reply #16 –
Quote from: ShowsOn on
I'm about to buy a new dual core CPU thanks to AMDs price reductions. I have about 100 GB of FLAC files that I want to encode to LAME MP3, is it possible to run two instances of this front end and encode with two instances of LAME set to each CPU core, without anything conflicting?


No, it won't start up more than once. This is a requirement due to how it sends messages between processes. I will add an option though for multiple concurrent encodes eventually, though. I'll want that feature myself once i upgrade to a dual-core.

Introducing Omni Encoder

Reply #17 –
Installer feedback: I wasn't expecting OmniEncoder to hijack--I mean overwrite--EAC's compression options. Should the 'Install and enable...' prompt include a warning to that effect? (It makes the encoder very easy to use. However, the people who can't cut and paste a command line option might not have their preferences saved as profiles either.) Your call, of course.

With respect to a FLAC module: I'd like to reiterate/clarify a request for 'metaflac --add-replay-gain [list of all FLAC files in the album]' after compression is complete.

It's looking very promising so far. Thanks much!

Introducing Omni Encoder

Reply #18 –
Quote from: windowshade on
Installer feedback: I wasn't expecting OmniEncoder to hijack--I mean overwrite--EAC's compression options. Should the 'Install and enable...' prompt include a warning to that effect? (It makes the encoder very easy to use. However, the people who can't cut and paste a command line option might not have their preferences saved as profiles either.) Your call, of course.

With respect to a FLAC module: I'd like to reiterate/clarify a request for 'metaflac --add-replay-gain [list of all FLAC files in the album]' after compression is complete.

It's looking very promising so far. Thanks much!


Well, i figure the "enable" part of "install and enable" would indicate that it was about to overwrite settings.

Regarding lossless files and ReplayGain: I'm thinking that i'll let wavegain do an analysis just like with other codecs, then (if gain adjustment is enabled) simply write those values to vorbis comments like metaflac would have. This will keep the interface uniform, and have the desired side-effect of disabling lossy gain processing on lossless files.

I've already added FLAC and Vorbis to trunk. Gotta make some tagging changes, then i'll add the above feature as well.

Introducing Omni Encoder

Reply #19 –
Quote from: Jebus on
Regarding lossless files and ReplayGain: I'm thinking that i'll let wavegain do an analysis just like with other codecs, then (if gain adjustment is enabled) simply write those values to vorbis comments like metaflac would have. This will keep the interface uniform, and have the desired side-effect of disabling lossy gain processing on lossless files.
If the output is (about) the same, I'll be one happy ripper.

Introducing Omni Encoder

Reply #20 –
Quote from: Jebus on
No, it won't start up more than once. This is a requirement due to how it sends messages between processes. I will add an option though for multiple concurrent encodes eventually, though. I'll want that feature myself once i upgrade to a dual-core.

Excellent, great to know it will be added eventually.

Introducing Omni Encoder

Reply #21 –
Just a quick note (sorry to bump my own thread):

Server will be offline while I move tomorrow for about 2 hours... the DNS record change may take up to 24 hours to propagate though.

Introducing Omni Encoder

Reply #22 –
Hi Jebus,

have you already heard about a new AC3 encoder called Aften? You cna find it announced here, but the discussion is taking place mainly at Doom9. I think some people would appreciate if you implemented support for it.

Introducing Omni Encoder

Reply #23 –
Quote from: Jebus on
Request for comments: What tag types are do people use for the following formats:

MP3: I know ID3v1 and ID3v2, but also APE2, correct? Any need for APE1 and/or Lyrics3 tags?
Vorbis: I don't use vorbis, so my understanding is that they commonly use Vorbis comments, ID3v1, and APE2? Corrections, ommisions?

I need feedback because the tagging system needs an overhaul before i integrate any more codec modules.
Vorbis use only Vorbis Comments... it don't use ID3v1, ID3v2, APE1, APE2, or any other just Vorbis Comments....

Note: You don't ask about FLAC, but FLAC files uses Vorbis Commenst too... ID3 are not longer used.
JorSol
aoTuVb5 -q4

Introducing Omni Encoder

Reply #24 –
Quote from: Jebus on
Request for comments: What tag types are do people use for the following formats:
MP3: I know ID3v1 and ID3v2, but also APE2, correct? Any need for APE1 and/or Lyrics3 tags?


I'd like to cast my vote against ape tags on mp3 files...foobar used to do this and everything was peachy as long as I only used foobar, but it caused me a lot of grief when I started using other applications with them...

Also, beware of mp4 tags...there seems to be a lot of confusion about the correct way to do it. (more precisely the interpretation of the word 'correct'  )