Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Keith]

I'm new to this. My daughter is teaching an old dog new tricks.

My question is how long should it take to convert a WAV file to MP3. System is 1.4 GHz with 256 MB Ram. WAV file is 3:22 in length. I have the latest Beta and have registered the software. The last attempt had not completed in 20 minutes.

Converter is set for MP3 VBR Normal.

[gateley]

Hi Keith,

I'm not the expert on this, but no it shouldn't take 20 minutes.

Check your CPU usage and disk usage (watch the disk light, and there's a windows program to monitor your cpu usage) and you can tell if anything's going on.

So, tell the exact steps you went throught to convert, and what was displayed as you did, and we'll see if we can't help.

Thanks,

j

[Harry The Hipster]

Noticed some conversion problems in 8.0.336, converting .wav to mp3 VBR normal/high. Normalization at 90% selected. Nothing else of note going on in background. Long time to normalize (3-4 minutes), long time to convert (10-20 minutes for 10-minute file), frequently a crash with the following error message:

MEDIA JUKEBOX caused a general protection fault
in module GDI.EXE at 0001:00008bff.
Registers:
EAX=00000000 CS=046f EIP=00008bff EFLGS=00000282
EBX=00958ede SS=134f ESP=0000c7aa EBP=0000c7b4
ECX=00002fd2 DS=05df ESI=00008ede FS=6ad7
EDX=00010025 ES=05df EDI=0000c9aa GS=0000
Bytes at CS:EIP:
8e 65 0e 8b 3e 12 04 64 8b 05 8b d8 87 44 26 64
Stack dump:
072a8be6 8ede8ede c7d005df 046f88fd 2fd2293a 00000167 02076ad7 00000000 0000700b c7de6c42 18370193 2fd2072a 01672d26 0028c828 072a0197 5b4e2fd

System info:

Media Jukebox PLUS 8.0.336
Install Path: C:\Program Files\J River\Media Jukebox\

CPU: Intel Pentium II 450 MHz MMX
Memory: Total - 163 MB, Free - 26 MB
Resource Info: System - 52 %, GDI - 52 %, User - 56 %
OS: Microsoft Windows 98

Internet Explorer: 6.0.2600.0000
ComCtl32.dll: 5.50.4807.2300
Shlwapi.dll: 6.00.2600.0000
Shell32.dll: 4.72.3812.600
wnaspi32.dll: 2, 0, 0, 0 , ASPI for WIN32 DLL, Copyright © Adaptec 1995
Aspi32.sys: N/A

(memory usage was lower during conversion process)

I know that converting/encoding with mp3 VBR is slower, but don't recall it being that slow.

HTH

Listening to: 'Solar' from 'Art of the Trio 4 - Back At The Village Vanguard' by 'Brad Meldhau' on Media Jukebox

[Keith]

I did some more research this morning. Other formats convert just fine. I even went from MP3 to WAV. When going from WAV to MP3, it never decodes, just goes straight to encode and then no progress. The progress bar never changes. Let it go overnight. No conversion in 8 hours.

[JimH]

Try downloading the MP3 encoder plug-in again.  It's on our plug-ins page.

Also, if your trial period has expired, it won't encode to MP3 unless you purchase.

Disk space?

[Harry The Hipster]

Could be disc space - down to less than 1 Gig. Time to stop being so cheap.

HTH

[Rob Marques]

Greetings,

Not sure if this has much to do with it, but I noticed that Harry was a) running IE 6.0 and b) has very few available resources. On any machine I have ever installed IE 6.0 on, the system became so unstable as to render it practically unusable. I just had to perform a complete reinstall this morning because if it (I thought that maybe the issues would have been resolved from it by now...)
26mb free RAM is WAY too little and will make any encoding go much slower (due to massive memory swapping), let alone VBR encoding. I run a 1.2Ghz Thunderbird chip w/ 384mb RAM and it takes quite a while to encode a full CD at VBR HQ (average about 3x-7x encoding speed). If your GDI resources get too low, windows won't even draw anymore, pretty much forcing a reboot.

Just a few thoughts.

Rob

[Keith]

Well, I downloaded again the MP3 converter and now it seems to work. I must have thought I downloaded it again and did not.

thanks for the help

[Keith]

OK, I spoke to soon. It seems to convert some and not others. I can convert to another format and then to MP3, just not directly from WAV to MP3

I tried another jukebox program as comparison (musicmatch) and it converted just fine.

I have no idea of what is causing the problem. The file I am trying to convert was captured from LP record via soundcard into a WAV file.

thanks for any help

[Rob Marques]

ok, I am reaching here, so pardon if I am way off base..lol...

Maybe it is a problem with settings in the .wav file at record time? I don't know what encoder Music Match uses as it has been several years since i have used it, but maybe Media Jukebox's is puking on the .wav file itself where the other can convert it. As an example, I recorded a cassette tape into a .wav file once at 24 bit sound and couldn't play it as it had to be 16bit sound (I think it was something like that, it was several years ago, so pardon if the technical details are off...) So maybe MJ's mp3 encoder uses stricter input rules?

[Keith]

Rob,

You may have a point. Other encoders do find, but not the WAV to MP3. These WAV files I used musicmatch to record. I will try recording a WAV with media jukebox. If I convert MP3 to WAV with MMJ, then I can convert back to MP3 from the newly converted WAV.

[Keith]

If it will help, here is my system info

Media Jukebox PLUS 8.0.346
Install Path: C:\Program Files\J River\Media Jukebox\

CPU: Intel Pentium 4 1399 MHz MMX
Memory: Total - 261 MB, Free - 54 MB
OS: Microsoft Windows 2000  Workstation 5.0 Service Pack 2 (Build 2195)

Internet Explorer: 5.50.4807.2300
ComCtl32.dll: 5.50.4807.2300
Shlwapi.dll: 5.50.4807.2300
Shell32.dll: 5.00.3315.2902
wnaspi32.dll: Internal ASPI Layer

[Galley]

My 1.4GHz Athlon with 512MB RAM encodes to MP3 at 10-12x with 128Kbps.

[KingSparta]

the last time i looked at the encoding speeds in MJ

when you copy and encode at the same time the speeds are displayed correctly.

when copy and encode is turned off mj reports the copy speed but then does not report the encode speed. so the high encode speeds are reported incorectly.

last time i encoded was a few weeks ago so i am not sure if this has been corrected. it was not reported as being corected on the upgrade notes.