CLI Encoding Issues

[afljr]

Hi, I'm using the Music Converter and CLI encoder along with an external Fraunhofer encoder and a VBR command line to convert FLAC files to mp3 in Fraunfofer VBR . This was working fine until I decided to migrate all of my music activity to a different machine. I loaded my registered install 14.0, codecs, etc., (Reference, family pack) on this other computer along with all of the same CLI settings used on the first machine.

For some reason, it won't complete the conversion process (FLAC to mp3/Fraunhofer VBR) on this second machine. When it starts to run the conversion, the window initially shows that the encoding process is running, starting out with encoding speed in the low 20X's (which is the encoding speed that the first computer usually runs this conversion at). However, on this second machine, shortly after the encoding process begins, the encoding speed begins to drop. It continues to gradually drop and then eventually grinds to a stall. It then locks up with the first track partially encoded. The converter seems to work properly with all other codecs.

I've tried reinstalling everything. I've checked the settings -- making sure the command line is correct, that the application is pointing to the Fraunhofer .exe file, etc. All of the settings are identical to those in the first computer (where it worked). Both computers are are running XP with similar specs. I would prefer to continue using Fraunhofer VBR via CLI since it's so much faster than lame.

Any suggestions?? Apologies for the lengthy the message.

[dbfan]

Re: CLI Encoding Issues

If you install the reference codec pack, it supplies a native Fraunhofer encoder.

[afljr]

Re: CLI Encoding Issues

Yes, but will it allow me to use VBR? The Fraunhofer reference pack only allows for CBR encoding, right?

Regardless, I'm still confused, since I had it working (Fraunhofer VBR encoding via CLI) on one computer and it wouldn't work on another.

[Spoon]

Re: CLI Encoding Issues

Enable the debug option in dBpoweramp configuration >> Music Converter

It will show the command line as sent to your encoder.

[afljr]

Re: CLI Encoding Issues

Ok, thanks. I'll try this for both computers and compare the results.

[afljr]

Re: CLI Encoding Issues

I attempted to use the debug function. But I wasn't able to pull any type of report because when the conversion app grinds to a stall, it just keeps running trying to complete the conversion of the first track without ever finishing. So I eventually have to cancel and shut it down ... which appears to eliminate the possibility of capturing the report, unless I'm missing something.

any other suggestions .... am I missing something .... could another app or something else on the PC be causing this to happen .... did I miss something in the installation on the second machine?

I'm using the same command line --
-if [infile] -of [outfile] -br 0 -m 2 -q 0 -ofl -vbri

and I have it pointing to the same Fraunhofer .exe encoder as as in the first computer where the CLI is functioning properly.

Your thoughts?

[Spoon]

Re: CLI Encoding Issues

I do not know what could be different.

[afljr]

Re: CLI Encoding Issues

Hi, I'm back to experimenting with Fraunhofer VBR using CLI. Apparently the problem was the .exe file (finally downloaded and installed another one and it worked).

I'm experienced a new issue -- the track time of the encoded file does not match up with the original file. It's sometimes varies to a large degree (as much as 30+ secs.). However, the files appear to be playing properly ... I still want to reconcile the issue if possible.

Still using the same command line --
-if [infile] -of [outfile] -br 0 -m 2 -q 0 -ofl -vbri

I thought that the "-ofl" (original file length) command would be taking care of file length/track time issue but apparently not .... it doesn't seem to be recognizing the ofl command. I found this info regarding ofl "-ofl Use Original File Length Feature (Not supported if piping to stdout is used)." I'm not that familiar with "if piping to stout", but could this be the issue or is it something else? Is there another way to set up the command line in CLI?

I'd like to try to get Fraunhofer VBR working properly in CLI. Method to my madness --- Lame is superior, but Fraunhofer in VBR mode produces reasonably acceptable results (in sound quality) with far greater speed. I like to have this as an alternative option to Lame. Played around with Helix MP3 ... great speed, not crazy about the sound.

Any help you can provide would be greatly appreciated. Thanks.

[Spoon]

Re: CLI Encoding Issues

It is just the player which is unable to work out the correct length of the VBR file. If you convert to WAVE, the wave file is the right length?

[afljr]

Re: CLI Encoding Issues

Correct you are, Sir.

I didn't even convert it to wave. I just opened up the album folder and checked the tag data (shadow) associated with the mp3 files. The track length/time associated with the respective files does appear to be correct. Looks like the JRiver/MediaCenter player front end isn't interpreting it correctly. I can't figure out why. It only seems to have a problem with Fraunhofer VBR. All of my music files are created in dBpoweramp, whether they're Flac, Lame, Fraunhofer CBR, etc. ... MC doesn't seem to have a problem with anything else.

Thanks for your quick reply