Maker Pro
Maker Pro

OT: Burned JPGs sometimes not displayed on DVD player

M

Mark Jones

Frank said:
You should try saving them in a low resolution, just good enough for
TV viewing. Not bigger than VGA or 640x480. You won't notice on
the TV.

I have a feeling that your DVD player gets upset decoding larger jpg's,
requiring more memory that it has available, and quits loading more
complicated pictures, as it runs out of memory while decoding and scaling
them to normal video resolution. Of course it doesn't show any error
message,
because if it did, customers would run to the shop, complaining etc.

I had similar problems using a card reader with video output. Some of the
jpg's wouldn't display.


What is the optimal image size for JPG on DVD then?
 
I

Ian Stirling

Rich Grise said:
Do any of your jpg files have a file size that's not an exact integral
multiple of 2048 bytes?

I suspect your file system software simply puts the files wherever
they land, and the player software expects them to start at certain
specific points.

One possible fix is to create a new directory, write your first .jpg,
look at how many bytes, divide by 2048, get the remainder, R, and write
a dummy file 2048 - R bytes long. Then write the next jpg, pad it the
same way, and so on.

Very unlikely.
The right way to test this would be to use some other burner software.
 
T

Terry Pinnell

Ian Stirling said:
Have you considered excorsism?

I would be suspect of something like photoshop to create files, and would
use a really basic tool to ensure that photoshop wasn't doing anything
clever.
Where are the files coming from, all from one source?

Where did PhotoShop come into the discussion?

Files = JPG, source = identical, all described earlier.
 
T

Terry Pinnell

Frank Bemelman said:
You should try saving them in a low resolution, just good enough for
TV viewing. Not bigger than VGA or 640x480. You won't notice on
the TV.

I have a feeling that your DVD player gets upset decoding larger jpg's,
requiring more memory that it has available, and quits loading more
complicated pictures, as it runs out of memory while decoding and scaling
them to normal video resolution. Of course it doesn't show any error
message,
because if it did, customers would run to the shop, complaining etc.

I had similar problems using a card reader with video output. Some of the
jpg's wouldn't display.

That sounds a likely cause. Despite fact that they are all same type
and size, presumably some are more 'complex' than others. And/or the
DVD player can't quite keep up.

Although that simple burning approach in Nero is attractive because of
its simplicity, I'm now going to try the alternative of writing VCD
files.
 
I

Ian Stirling

Terry Pinnell said:
Where did PhotoShop come into the discussion?

Files = JPG, source = identical, all described earlier.

Oops.
I'd somehow misremembered your earlier mention of thumbsplus.
What might be illuminating also is to try to rename some files that don't work,
or copy different arrangements of files onto the disk.
This would guarantee that it's not some strange filesystem problem.
 
C

Chaos Master

Terry said:
Where did PhotoShop come into the discussion?

Files = JPG, source = identical, all described earlier.

Do those files have image information such as EXIF or IPTC?
(Use a image viewer like XnView to check)

[]s
--
Chaos Master®, posting from Canoas, Brazil - 29.55° S / 51.11° W

"Now: the 3-bit processor, with instructions:
1. NOP - does nothing, increase PC.
2. HLT - does nothing, doesn't increase PC
3. MMX - enter Pentium(r) emulation mode; increase PC
4. LCK - before MMX: NOP ; after MMX: executes F0 0F C7 C8
5. HCF - Halt and Catch Fire"
 
K

Keith Williams

"Now: the 3-bit processor, with instructions:
1. NOP - does nothing, increase PC.
2. HLT - does nothing, doesn't increase PC
3. MMX - enter Pentium(r) emulation mode; increase PC
4. LCK - before MMX: NOP ; after MMX: executes F0 0F C7 C8
5. HCF - Halt and Catch Fire"
6. EPI - Execute Programmer Immediate
 
T

Terry Pinnell

Chaos Master said:
Terry said:
Where did PhotoShop come into the discussion?

Files = JPG, source = identical, all described earlier.

Do those files have image information such as EXIF or IPTC?
(Use a image viewer like XnView to check)

[]s

Yes, all of them.
 
K

keith

OK, what does F0 0F C7 C8 do?

On PowerPC? Dunno, I'll look it up if you're interested.

On Pentia it's a LOCK Exchange Register (with an exception and
re-execute), or some such, which locks the processor up tighter than a...
 
J

John Woodgate

On PowerPC? Dunno, I'll look it up if you're interested.

The context is Pentium, so thank you for your offer, but there is no
need.
On Pentia it's a LOCK Exchange Register (with an exception and re-
execute), or some such, which locks the processor up tighter than a...

... wallaby's sphincter? I believe that's the classic expression.(;-)
 
K

Ken Taylor

John Woodgate said:
The context is Pentium, so thank you for your offer, but there is no
need.

.. wallaby's sphincter? I believe that's the classic expression.(;-)

Struth, Bruce, I haven't heard that one before! Now 'tighter than a dead
dingo's donger' is a known quantity.....

Ken
 
D

Don Lancaster

John said:
OK, what does F0 0F C7 C8 do?

--
Regards, John Woodgate, OOO - Own Opinions Only.
The good news is that nothing is compulsory.
The bad news is that everything is prohibited.
http://www.jmwa.demon.co.uk Also see http://www.isce.org.uk

There's also RPI for Reconfigure Programmer Immediate.

--
Many thanks,

Don Lancaster
Synergetics 3860 West First Street Box 809 Thatcher, AZ 85552
voice: (928)428-4073 email: [email protected]

Please visit my GURU's LAIR web site at http://www.tinaja.com
 
I

Ian Stirling

keith said:
On PowerPC? Dunno, I'll look it up if you're interested.

On Pentia it's a LOCK Exchange Register (with an exception and
re-execute), or some such, which locks the processor up tighter than a...

Unless the OS is appropriately patched.
 
R

Rich Grise

Struth, Bruce, I haven't heard that one before! Now 'tighter than a dead
dingo's donger' is a known quantity.....

I once met a guy who said, "tighter than a nun's pussy."

But he also said stuff like "happier than a sissy in boy's-town."

Cheers!
Rich
 
C

Chaos Master

I wish I had keith's angel tonight:
On PowerPC? Dunno, I'll look it up if you're interested.

On Pentia it's a LOCK Exchange Register (with an exception and
re-execute), or some such, which locks the processor up tighter than a...

Exact... if you have a Pentium MMX machine lying around with Windows or
MS-DOS, try typing F0 0F C7 C8 in an hex editor, save the file as a .COM
file and run this.

I found that there's a fix for this bug, if you're running Windows... -
involves a configuration in the MSCONFIG program.

[]s
--
Chaos Master®, posting from Canoas, Brazil - 29.55° S / 51.11° W / GMT-
2h / 15m


"Now: the 3-bit processor, with instructions:
1. NOP - does nothing, increase PC. / 2. HLT - does nothing, doesn't
increase PC
3. MMX - enter Pentium(r) emulation mode; increase PC / 4. LCK - before
MMX: NOP ; after MMX: executes F0 0F C7 C8
5. HCF - Halt and Catch Fire / 6. EPI - Execute Programmer
7. DPC - Decrease PC"
 
C

Chaos Master

Ian Stirling stated:

[F00FC7C8]
Unless the OS is appropriately patched.

I know this - and I have found a way to make Windows 98/ME safe against
this bug. Involves using MSCONFIG.

[]s
--
Chaos Master®, posting from Canoas, Brazil - 29.55° S / 51.11° W / GMT-
2h / 15m


"Now: the 3-bit processor, with instructions:
1. NOP - does nothing, increase PC. / 2. HLT - does nothing, doesn't
increase PC
3. MMX - enter Pentium(r) emulation mode; increase PC / 4. LCK - before
MMX: NOP ; after MMX: executes F0 0F C7 C8
5. HCF - Halt and Catch Fire / 6. EPI - Execute Programmer
7. DPC - Decrease PC"
 
Top