Can't convert to MP3.Error message"no codecs found" I DL Lame and installed it, I think but still no MP3. This is a new computer. RB converts fine on the other one. I just forgot what needs to be done.
Thanks

John,

I can't find any answer for you in the RealBand user or update manual. You need to ask PG Music support or see if you can contact Jeff.

Did you install the 32 or 64 bit codec? If you installed the 64 bit RealBand is still 32 bit so you'll need to also install the 32 bit version.

The unknown is what location does RealBand look at to find the encoder. Every program seems to have a different location preference. The Windows default for the 32 bit version is C:\Windows\System32\. You may find +++ THIS +++ Microsoft forum message useful. If that doesn't help you may need to ask PG Music support or see if you can contact Jeff.

Assuming it's not an issue with RB2019 itself, if you didn't already, try installing the LAME ACM version, which writes the information into the registry and that's where RealBand looks for the CODECS. Just follow the instructions in the text file you get with the download. Just installing the regular LAME gives you the stand-alone version, which does not integrate with Windows/BIAB.

Ok thanks guys.
John do you have a link?
Thanks

Interesting that all my other programs can convert to mp3.

Some programs come with their own codecs.

Just go back to the lame site and look for the ACM version.

To much command line stuff for this day and age. Shouldn't be.

Here's a safe source for the LAME ACM.

http://m.majorgeeks.com/files/details/lame_acm_codec.html

Another source (the original)
http://www.rarewares.org/mp3-lame-dshow-acm.php

Back when I did it I just extracted the zip file, right-clicked the INF file and installed.
Rebooted (registry entry added), and it was available in RB/PT.

Hope it still works the same.

64bit computer?
I did that but forgot to reboot. Have to try that RHARV but it appears that command line entry is the only way for 64bit machines.

Yes, 64 bit machine but I think I installed the basic 32 bit codec.

No luck at all. even did the command prompt thing. Copy and pasted the commands but got "installation failure" Not a big deal as I can use other progs to convert but it bugs me.

John are you sure you even need MP3? RB defaults to Windows Audio which is the WDM format. I've read in several places that WDM actually sounds a bit better than MP3 and plays well on lots of different players.

Bob

Hey Bob,
Doing a CD for someone,bass tracks, that's 1500 miles away.Once the track is in the mix you can't tell it's MP3. Can't email big *wav files.

He's using a Mac with Cubase.

You can use www.wetransfer.com to send up to 2 gigs for free. Rog and I do that all the time.

Thanks I'll check it out.

If you got a failure message, then it didn't install properly to the registry. You need to open your command line window as administrator for it to work properly.

I thought I did. Right clicked the icon and chose run as admin. Ill try again. I even copy pasted the command lines.
thanks

Another vote for wetransfer.com

No one I record for would accept an MP3. You can send very large files, and many files, by wetransfer.com

Sending mp3 tracks was an experiment.Neither of us would accept it either. Google Drive does the same. I can send full wav files.
It just struck me odd that I can't create mp3 on this machine with RB 2019 and I can my other. Both with RB 2019. I must of somehow got mp3 Codec to install on the other.

Maybe k-lite or something (?)

jford,
Thanks for your tip about using LAME ACM version. It partially worked.

BIAB 64-bit was immediately able to save to MP3 right after being installed after I downloaded it. Nothing else needed.
And I've had Reaper 64-bit previously able to render MP3's. A year or so ago, Reaper started bundling in LAME during the Reaper install. Works solid.

But the 2 32-bit programs were not able to save MP3 --- RB 2019 and BIAB 32-bit. So, I tried your suggestion here to install LAME ACM. Then, BIAB 32-bit was able to save them, exactly the way BIAB 64 worked. Great, it seems to me the 32-bit version is a little bit faster, but things are working.

However, it's RealBand 2019 that still isn't working ---- I installed with the CMD line as Administrator, run the programs as Administrator, and the menu lets me choose "Save as MP3" ---- it loads the LAME interface, allows me to choose Attributes, and tries to render out, but gives the error message Cannot get Stream Size It does save WAV files just fine. Any ideas?

Jerry, I'm getting the same "Cannot get stream size" error. But strangely enough, I've found that if I rename the generated WAV file to.mp3 rather than .wav the file plays fine in an mp3 player. Strange.

Jeff

OK Jeff,
Thanks, just to clarify what I see happening, I get the error when I try to save the Song as MP3.
It does create a .mp3 file, but it's 0 bytes long.

If I save the Song as a WAV file, no such problem, it works fine.

I'll try to run it on my computer and see what happens.

Another option is to try something like K-Lite CODECS (I think you need the Mega Pak to get the MP3 CODECS).

Mountainside, most media players can playback both MP3 and WAV files. So as long as the actual file is a type that the media player can play, it don't care what the file suffix is as long as one is there.

LAME as a converter..... doesn't the name say it all?

I use Wavepad from NCH to do my conversions to MP3. It's free.

And yes.... wetransfer is a great site for the bigger files.

Renaming the file and having it work is a clue, thanks Jeff.
You can probably tell if it's an actual MP3 by the file size. Is it closer to 5 meg or 50?

As far as the LAME name, as an acronym it stands for Lame Ain't MP3 Encoder.
It was how they got around the patent that allowed them to exist. Thus the name.
It is actually quite a good codec.

OK rharv,

Apparently this MP3 rendering situation in RB has been around for a while! I found an old discussion from 2016, and you and Larry Kehl were going back and forth about it. Larry found a link to a Windows registry edit that enables the Fraunhofer codec!

Here is that previous thread ---- https://www.pgmusic.com/forums/ubbthreads.php?ubb=showflat&Number=352908&page=1

On page 2, he posted the link to a CMD file that you Run as Administrator ---- I just tried it, and it worked solidly! I'm on Windows 10 - 64bit, version 1809, and it worked like a charm, even though this patch was devised 5 years ago.

To recap my own situation, I had the LAME encoder installed a couple years ago, used with Audacity at first, then with Reaper. I installed BIAB just recently, and BIAB-64 worked fine, was able to save MP3. But not in BIAB-32 or RealBand 32. So I tried jford's suggestion of installing LAME ACM version, and then BIAB-32 worked fine(!) --- but still not in RealBand! I kept getting the error about the Stream Size. So I tried the CMD batch file, and now RealBand is also working fine for MP3. It allows me now to choose EITHER the LAME version, or the Layer-3 version (Fraunhofer which is already installed in Windows 10).

I didn't know about this being builtin, the 2 files are no doubt on every Windows 10 computer, they just need to have the registry settings enabled. Nice easy solution!

There was a time when you could purchase an activation of the Fraunhofer CODEC, but that disappeared many years ago when the newer owners of the CODEC basically abandoned it, but kept the patent active. I knew about that CODEC and that would have been my next suggestion. Still surprised that RealBand didn't let LAME ACM work, though. I recall having used it in the past; however, most of my MP3 ripping is done in a different program (just because that's part of my workflow).

John, thanks for your input (and humor!) on so many threads. If it's not the exact answer, it usually leads to the answer!

As a relative "newbie" to BIAB & RB, I'm sure there are a lot of folks who are just not sure yet, as to how these programs are "supposed" to act. As a veteran, you probably wonder..... hmm, what's going on here.... is it a newbie problem, or is it something more, and it's often hard to separate it all out. The key on this one was the Stream Size error, which has been noted by others going back several years, and only on RB. What caused it??? Don't know, but the registry edit fixed it.

Thanks for the update Jerry
Always good to learn more.
Like jford, the Lame ACM file has always worked for me, but I don't think that I've tried it on W10 yet.
Your post will likely become more and more relevant as more people go to W10.
Thanks again