Ok, thanks both.

The make and model is a Samsung 707SCII from SoftBank, but I don't think
it is available in NZ.  It will not play MP3 files, but what I want to do
is encapsulate an MP3 file in an MP4 container and try that.

Of course, Nick is right- I should know the phone's capabilities and make
an MP4 file which can be expected to work, but I don't, so it's trial and
error for now.  And I am full of hope, because I really don't want to have
to re-encode music I want to listen to.

I have to say, it's been fun playing with BlueTooth.  KDE pops up the
BlueTooth device (my phone) as a file icon in Konqueror.  Clicking it
opens the filesystem *on the phone* and I can drag and drop files between
the local and phone filesystems, which is as it should be.

I also have to say that I despise the phone companies and their insistence
on crippling the hardware so that it only does things they can charge for.
 I am sure this phone is capable of many things, such as MP3 playback, but
that's probably neutered so that DRM can be included (or so you can't
easily use MP3 as a ringtone and have to buy your favourite music yet
again in an MP4 container).  Also the address book in the phone is 'hidden
away' and doesn't appear as a file in the filesystem.  There may be an API
to query the address book- I will try Kmobiletools later (but my phone
isn't listed, and when I tried it with USB it didn't work).

Anyway, rant over, I want my MP4 (with apologies to Dire Straits).

A

On Mon, October 1, 2007 09:58, Douglas Royds wrote:
> What make and model is the phone? We can probably find out from there.
>
>
> Nick Rout wrote:
>
>> you need to know what codec you want to encode to.Know your phone wants
>>  "mp4" is unhelpful unless you know the audio codec to put inside the
>> mp4 container.
>>
>> So find that out and then we will be able to get somewhere.Its possibly
>>  aac. If you have a sample file that perhaps came with the phone
>> software (did you throw out that windows disk?) you can fun ffmpeg -i
>> filename.mp4 to see what is inside.
>>
>> Nick.
>>
>>
>>
>>> Some possibles. The web pages infer it's possible, but I havn't
>>> tried.
>>>
>>> http://mirror.greaterscope.net/cmus/
>>>
>>>
>>> http://www.mplayerhq.hu/design7/info.html
>>>
>>>
>>> http://www.oddsock.org/tools/streamTranscoderV3/
>>>
>>>
>>> Best of luck. HTH. Let us know how you get on.
>>>
>>>
>>> Thanks for the info about the BlueTooth whodackey.
>>> It's exactly what we need to transfer images from a
>>> camera-phone to the 'puter. I'll see what I can find locally before
>>> bothering your good services.
>>>
>>>
>>> On 9/30/07, Andrew Errington <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>>> On Sunday 30 September 2007 05:43, Robert Fisher wrote:
>>>>
>>>>
>>>>> Andrew Errington wrote:
>>>>>
>>>>>
>>>>>> PS The bluetooth adaptor I got here is tiny- it is a USB plug
>>>>>>
>>>>>>
>> with a 5mm
>>
>>>>>> long blob on it.  It barely sticks out from the side of the
>>>>>>
>> laptop.  Oh,
>>
>>>>>> and it's a brand-new product, but is properly detected with
>>>>>>
>> Mepis, so
>>
>>
>>>>>> must be an established chipset, just shrunk.
>>>>>>
>>>>> Can you please tell us what model the dongle is Andrew?
>>>>>
>>>>>
>>>> Ok, I have started a new thread about that, but in the meantime, I
>>>>
>>>>
>> want my,
>>
>>>> I
>>>> want my, I want my MP4.  Anyone?
>>>>
>>>> A
>>>>
>>>>
>>>>
>>> --
>>> Sincerely etc.
>>> Christopher Sawtell
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
> =======================================================================
> This email, including any attachments, is only for the intended
> addressee.  It is subject to copyright, is confidential and may be the
> subject of legal or other privilege, none of which is waived or lost by
> reason of this transmission. If the receiver is not the intended
> addressee, please accept our apologies, notify us by return, delete all
> copies and perform no other act on the email. Unfortunately, we cannot
> warrant that the email has not been altered or corrupted during
> transmission.
> =======================================================================
>
>
>


Reply via email to