didn't convert and didn't yell an error

[Jad Madi]

I just tried it on .rm file and it didn't work, it didn't convert the file nor yelled an error, just an exclamation mark.

sorry for the non-descriptive bug report but I don't know how to debug java apps.

[cutout (cutout33)]

humm.
is your .rm file path valid for lame (ie. don't have spaces and don't contain non english characters)
I know that this is not very efficient but it is due to lame not me!!!
also is your .rm file path valid for rmc (ie. it is on a place that doesn't need a root to write on).

[cutout (cutout33)]

humm.
is your .rm file path valid for lame (ie. don't have spaces and don't contain non english characters(arabic))
I know that this is not very efficient but it is due to lame not me!!!
also is your .rm file path valid for rmc (ie. it is on a place that doesn't need a root to write on).

[Jad Madi (jad)]

Yes, it is valid.

  File: `kids77.rm'
  Size: 840336 Blocks: 1656 IO Block: 4096 regular file
Device: 803h/2051d Inode: 4123662 Links: 1
Access: (0775/-rwxrwxr-x) Uid: ( 1000/ jad) Gid: ( 1000/ jad)
Access: 2008-05-26 21:18:06.000000000 +0300
Modify: 2008-05-26 21:18:02.000000000 +0300
Change: 2008-05-26 21:18:02.000000000 +0300

[cutout (cutout33)]

OK.
I was talking about the path
(ie. "/home/user/file.rm" is good but "/home/user name/file.rm" is not)
also Arabic characters will not work in the path.
please confirm on that.

Am assuming that you are using Ubuntu as you are my team leader :)
please try to run it from the terminal using the command "rmconverter"
and copy paste the console output for the error please.

thanks for your help.

P.S do you know any command line tricks to access such files from the terminal besides putting a quotes "" around the path cause this one doesn't helpp in this case.

[Jad Madi (jad)]

the file stat shows it all, it's in English, no spaces, permission is ok.

again, as I mentioned before, it doesn't output any error :-)

I uploaded a screen shot hopefully it will help
http://temp.syntux.net/rmconverter/

again I'm sorry for my disability in debugging java apps.

[cutout (cutout33)]

I found why it didn't print the error
now lets found what is the error.
please use the attached jar file
you can run it in terminal using
java -jar rmconverter.jar

[Jad Madi (jad)]

now you're talking :-)

########
jad@syntux:~/Desktop$ java -jar rmconverter.jar
lame -V 4

mplayer: could not connect to socket

mplayer: No such file or directory

Failed to open LIRC support. You will not be able to use your remote control.

demux_real: invalid chunksize! (-93182618)

No stream found.
############

but mplayer is there and it works fine
jad@syntux:~/Desktop$ which mplayer
/usr/bin/mplayer

[cutout (cutout33)]

OK.
I think I've a theory about that...
1. did you upgrade your gutsy to become a hardy???
2. did you had your w32codecs, mplayer from the era of gutsy???
will if the above is true I have faced the same problem you need to updated the medibuntu repositories in you software sources to become a hardy ones
if they don't yell to update these two packages then you will need to do it manually

# sudo apt-get autoremove w32codecs mplayer
# sudo apt-get install w32codecs mplayer

I don't know the cause of that but that what happened with me :-/

for medibuntu try:
https://help.ubuntu.com/community/Medibuntu

don't forget to remove the old one.
please keep me updated.

[Jad Madi (jad)]

1. did you upgrade your gutsy to become a hardy???
No, it's fresh Hardy install
2. did you had your w32codecs, mplayer from the era of gutsy???
No

w32codecs and mplayer were installed by your deb package dependency request; they were not installed before and I got them from Medibuntu as you just advised.

:d

[Jad Madi (jad)]

attaching the .rm file as per requested.

[cutout (cutout33)]

Please try this command at your terminal.

mplayer /your/file/path.rm -ao pcm:file=/your/file/path.wav

[cutout (cutout33)]

This bug is due to mplayers encoder not real media converter.