 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I bought a Samsung Q2 player. It says it can play MP4 videos.
I got one or two MP4's off of http://www.publicdomaintorrents.com/.
I transferred them to the device. The Q2 gives it a question mark icon and says
no codec.
Q: Anyone found a workaround for problems like this? Could the problem be with
the device or the file? I tried some conversions with avidemux or some other
software, but haven't tested it yet.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
gregjohn wrote:
> I bought a Samsung Q2 player. It says it can play MP4 videos.
>
> I got one or two MP4's off of http://www.publicdomaintorrents.com/.
>
> I transferred them to the device. The Q2 gives it a question mark icon and says
> no codec.
>
> Q: Anyone found a workaround for problems like this? Could the problem be with
> the device or the file? I tried some conversions with avidemux or some other
> software, but haven't tested it yet.
Problem more likely with the file...non-computer devices are usually a
bit picky as to wanting specific settings for files they'll play, look
those up for the Q2 and convert to those parameters.
--
Tim Cook
http://empyrean.freesitespace.net
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I bought a Samsung Q2 player. It says it can play MP4 videos.
>
> I got one or two MP4's off of http://www.publicdomaintorrents.com/.
>
> I transferred them to the device. The Q2 gives it a question mark icon
> and says
> no codec.
>
> Q: Anyone found a workaround for problems like this? Could the problem be
> with
> the device or the file? I tried some conversions with avidemux or some
> other
> software, but haven't tested it yet.
Similar problems with PSP and PS3, they're *really* fussy about what they'll
play.
After spending days with command line parameters, I finally found a program
called XviD4PSP which is GUI based and has profiles for common media players
that are known to work. I don't have it here on this computer, but maybe
using the PSP or similar profile would make it work on the Q2?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Great advice all.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tim Cook wrote:
> Problem more likely with the file...non-computer devices are usually a
> bit picky as to wanting specific settings for files they'll play, look
> those up for the Q2 and convert to those parameters.
My dad had a player which accepts Ogg Vorbis... but only at specific
bitrates. And Vorbis is an inherantly variable bitrate system, so the
sound would randomly drop out during playing.
I have a set of MP3 files which WinAmp will play. However, by player
(powered by RockBox) refuses to play track 1. It will play all the other
tracks, just not track one...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
> I have a set of MP3 files which WinAmp will play. However, by player
> (powered by RockBox) refuses to play track 1. It will play all the other
> tracks, just not track one...
Heh. My Civic has a built-in MP3 player. I've been buying and
downloading music lately, and every once in a while I'd get an album
where every song would start with a burst of LOUD static. Very annoying
when driving down the road. The files played just fine in Winamp and
Windows Media player. Eventually figured out that I had to untag and
retag every single file that would give static. No idea why this worked,
unless the site selling the music put the tag at the font of the file
instead of the end of the file (If that's even possible)
The other bit of weirdness is if the file is tagged in unicode, you can
only see the first screenful of text, it never gives you the option to
scroll to see the rest of the text, but works fine with ASCII.
Consumer electronics are sometimes weird ;)
--
~Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Raiford wrote:
> Heh. My Civic has a built-in MP3 player. I've been buying and
> downloading music lately, and every once in a while I'd get an album
> where every song would start with a burst of LOUD static. Very annoying
> when driving down the road. The files played just fine in Winamp and
> Windows Media player. Eventually figured out that I had to untag and
> retag every single file that would give static. No idea why this worked,
> unless the site selling the music put the tag at the font of the file
> instead of the end of the file (If that's even possible)
I would suggest that the MP3 player is expecting the ID3 tag to be in
one specific place, when the standard actually permits it to be placed
anywhere.
> The other bit of weirdness is if the file is tagged in unicode, you can
> only see the first screenful of text, it never gives you the option to
> scroll to see the rest of the text, but works fine with ASCII.
>
> Consumer electronics are sometimes weird ;)
Weird, no. Substandard, sure.
Unfortunately people seem to think that it's "OK" to make products that
don't work correctly. It's extremely annoying, really...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
>
> Weird, no. Substandard, sure.
>
> Unfortunately people seem to think that it's "OK" to make products that
> don't work correctly. It's extremely annoying, really...
Well, when you consider in consumer electronics you're trying to cram
functionality seen on a general computer into a device that's small,
designed so the average person can use it w/o detailed knowledge of
computers, and cheap enough that the average consumer will buy it, you
have to make all sorts of compromises.
The unicode thing to me is strange, though. Why is it capable of only
displaying part of the string?
--
~Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> Unfortunately people seem to think that it's "OK" to make products
>> that don't work correctly. It's extremely annoying, really...
>
> Well, when you consider in consumer electronics you're trying to cram
> functionality seen on a general computer into a device that's small,
> designed so the average person can use it w/o detailed knowledge of
> computers, and cheap enough that the average consumer will buy it, you
> have to make all sorts of compromises.
Faulty software is unecessary. It's quite possible to write software
that works well, and it needn't even be particularly expensive.
(Depending on what it's supposed to do, obviously.) But people can't be
bothered, it seems...
You know why my player uses RockBox? Because the manufacturer's own
firmware crashes constantly. That wouldn't be so bad, but when it
crashes it sandblasts your ears with very loud sound. One could almost
argue it's HARMFUL TO HEALTH beyond being merely defective... And yet, a
bunch of bored hackers on the Internet who don't even have access to the
design spec for the player managed to do a better job than paid
programmers. I ask you...
> The unicode thing to me is strange, though. Why is it capable of only
> displaying part of the string?
Indeed. There's no reason for it, other than they didn't plan what they
were doing properly. If they'd done the job right, it would work.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Raiford <"m[raiford]!at"@gmail.com> wrote:
> The unicode thing to me is strange, though. Why is it capable of only
> displaying part of the string?
Possibly using UTF-8 to store the string, giving you a non-constant number of
bytes per character, which makes handling such strings (like, say, displaying
the substring starting from the 42th character) non-trivial.
Add limitations of the software design chosen before they decided to add Unicode
support at all, and pressure to finish the product on time, and you're there.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
