View Profile
View Forum Posts
Hi, i have problems with using tooLame as the audio encoder for TMPGEnc
it keeps on freezing and gives me some error Cant open somethingsomething.mpa
+ Reply to Thread
Results 1 to 16 of 16
-
-
never mind about this one i think i found the anwer. tooLame doesnt work with plus version of TMP
-
On the contrary toolame works just fine with the plus version of TMPEGnc. I'm encoding a file as I'm typing this using toolame and no problems here. What version of toolame and TMPEGnc are you using? I'm using TMPEGnc version 2.57.41.146 with toolame-02i. From what I understand toolame is basically a command line utility. Try simplifying the pathway your using as the temp file for tmpegnc such as C:\Temp or D:\temp whatever your preference. This has something to do with the limited number of characters that can be included in a command line pathway. Someone else here that may be a little more up on how to use the command line might be able to go into more detail, but I'm afraid I'm a little rusty.
-
no how would i do that with windows xp
sry for the late reply on vacation and i am using the lateset tmpenc -
The Old One
- Aug 2000
- Hellas (Greece), E.U.
I can confirm that there are problems with the latest TMPGenc Plus and TooLAME
The latest version is very buggy, there are also probs with the DVD2AVI frameserver...
This week we expect a new version. Hope will eliminate those bugs... -
SatStorm,
First of all I'm not trying to start a flame session here so bear with me. I've been using the above mentioned set-up for the last month and done about 20 movies without a hitch with the exception of 2 where I encountered that stupid read error at the end of the encoding session. As we both know this is a well-known and documented error in TMPEGnc v.2.57 and in the end has no impact at all on the final result. As for DVD2AVI, yes some people have had problems using v1.77.3 so my suggestion would be to revert back to v1.76 if it's an issue. From my understanding v1.77.3 was written to take advantage of the P4 processor and it's set of extended operations and to be honest I don't know if this would have any negative impact on anyone running a PIII or lower/ AMD Athlon or lower processor, but I suspect it might. Now to get to the topic at hand, I've been using toolame without a hitch and not doing anything special. I unzipped it, placed it in a separate directory inside the TMPEGnc folder and opened up TMPEGnc and pointed it to the exe file. As I pointed out in my previous post toolame is basically a command line utility and as such invokes the command prompt during encoding with TMPEGnc. That’s why I suggested keeping the pathways as simple as possible. Now if I've missed something please point it out to me. I mean the whole purpose here is to help other people out and I'd be interested in any comments that you might have as to specific issues concerning any of these utilities. -
Tmpgenc, toolame, and ssrc--all the latest versions--have been working fine in converting audio from VOBs and MJPEG AVIs.
However, I did notice a repetitive crash when encoding the audio of a downloaded AVI file.
After separating the audio to a separate WAV file, I am still unable to up convert the audio from 22 kHz to 48 kHz without toolame crashing at audio frame 10010. I encoded this multiple times using 2 versions of Tmpgenc and even with an older version of toolam and ssrc. But it would always crash with toolame quitting at the exact audio frame 10010. This happens even after rebooting, creating a new project in Tmpgenc, and shortening the temp directory path to the C drive.
What's odd is when I tried converting the audio from 22 kHz to 44 kHz, toolame was able to complete the conversion. Prior to this incident, I've always been able to upconvert files, mainly from 44 kHz to 48 kHz.
So, are we all talking about the same toolame error, the upconversion from 22 kHz to 48 kHz error? -
bbb,
Did you load up that avi in VirtualDub and scan for junk frames first? Also I'd use VDub to do the conversion for the wave file. Just load up your file in VDub and go to the audio tab and select full processing mode. Then go to compression and make sure "no compression (PCM)" is selected. Then go back and select conversion and check either 44100Hz or 48000Hz whatever your preference, then go to the file tab and select save wav. It's been my experience ssrc will down-sample it back to 44100Hz if your trying to make a VCD/SVCD so I'd leave it at 44100Hz unless of course your trying to make a DVD in which case it won't matter. Then I'd load up that avi in TMPEGnc and make sure you select the wave file as your input source for your audio, but I'm sure you already knew that. Give that a try and see if it helps. -
Nice solution kayfam.
Hopefully when my video is finished all will be in sync. Thanks. -
yes I have stopped using toolame to do frequency conversions, I was having tons of problems. Guess this is a bug-I too have been using VDub to change the sampling frequency of my WAVs...
End of Line. -
I'm having big time problems with tooLame 0.2 i too. On one box, with W2k Pro, tooLame errors out after ca 50 MB output. Another (identical hardware, besides the processor, as the first) with W2k Server has no problems at all. A third with XP Pro, errors out about every second try. 2 first boxes runs PIV 2GHz, the 2nd PIV1.8 GHz, the third PIV 1.7 GHz. It's a pain transfering huge wavs over the network to the server box every time I want to make an MPEG from a wav...
/Mats -
The Old One
- Aug 2000
- Hellas (Greece), E.U.
-
I have many errors when I encode direct AVI files (huffyuv & PicVideo) with tmpgenc plus 2.57. and toolame. I don't have those probs with 2.56.
There is always a message at the end of any avi2mpeg2 encoding: "stream reading error" or something. This has no impact to the file, but for better, remux your files again as SVCD or VCD with BBmpeg....
If you use mpeg2vcr to cut files with this error and without that later remuxing , you experience many lipsync problems. -
@mats.hogberg- I have started using BSweet. I would recommend you try that app. It does a good frequency conversion and will do mp2 at any bitrate. what I don't understand is that it uses toolame for its mp2 encoding...is this bug on the TMPEGEnc side of things or the toolame side of things?...hmmmm
End of Line. -
That's what struck me too! But my problem isn't TMPGenc related - I run tooLame from the command line. I tried BSweet, but then TMPGEnc refused to accept the resulting MP2 when muxing. I really hope there's a new version of tooLame on its way!what I don't understand is that it (BSweet) uses toolame for its mp2 encoding
/Mats -
I never, ever, ever mux with TMPEGEnc...try BBMPEG and I'll bet it takes that .mp2...it is the muxer par excellance...
End of Line. -
Thanks for the tip - I'll give it a go!
/Mats
Quote
Visit Homepage
