Tried loading some tiffs into MF5's slide creator and it crashes. Tried rebooting and still same result. Batch converting the files to jpeg and it
imports just fine.
Anyone else had similar results with tiffs not importing into MF5?
Tiffs causing MF5 to crash
Hi,
I just tried importing some TIFFs with MF5+ (5.30.0107.0) without crashing.
I chose random TIFFs with 24bit and 32bit color, with/without alpha channel (transparency), and resolutions from very small 170x390 (260K) up to 3072x2304 pixels (17MB).
Possibilities, just guessing as usual
...
1. Maybe it was fixed in the update and you don't have the SP1.
2. Your TEMP area has no room for the (large) temporary files MF creates. Check your system environment variables where TEMP is defined.
3. Maybe your TIFF uses a feature that MF doesn't understand. TIFF files can use compression levels, various color depths, and other options. If so, report it so they can fix it.
4. MF decodes TIF files with these modules, which are all taken from PhotoImpact 11.0.0.0 (if I'm wrong maybe H.T. can correct me!):
MF5_Program_Folder\fio\u32Tif.fio
MF5_Program_Folder\ulibtif.dll
TIFF LZW compression is handled with these:
MF5_Program_Folder\fio\u32lzw.dll
MF5_Program_Folder\uliblzw.dll
So if any of these files (same name) are located somewhere else in your search path, then that would cause undefined behavior.
1., 2. or 3. is much more likely than 4.
Or it's something completely different.
I just tried importing some TIFFs with MF5+ (5.30.0107.0) without crashing.
I chose random TIFFs with 24bit and 32bit color, with/without alpha channel (transparency), and resolutions from very small 170x390 (260K) up to 3072x2304 pixels (17MB).
Possibilities, just guessing as usual
...1. Maybe it was fixed in the update and you don't have the SP1.
2. Your TEMP area has no room for the (large) temporary files MF creates. Check your system environment variables where TEMP is defined.
3. Maybe your TIFF uses a feature that MF doesn't understand. TIFF files can use compression levels, various color depths, and other options. If so, report it so they can fix it.
4. MF decodes TIF files with these modules, which are all taken from PhotoImpact 11.0.0.0 (if I'm wrong maybe H.T. can correct me!):
MF5_Program_Folder\fio\u32Tif.fio
MF5_Program_Folder\ulibtif.dll
TIFF LZW compression is handled with these:
MF5_Program_Folder\fio\u32lzw.dll
MF5_Program_Folder\uliblzw.dll
So if any of these files (same name) are located somewhere else in your search path, then that would cause undefined behavior.
1., 2. or 3. is much more likely than 4.
Or it's something completely different.
Henry
-
Scooterspal
- Posts: 48
- Joined: Thu May 25, 2006 1:14 pm
Henry:
Hum? You know I never did install that PhotoImpact program since I had others for doing the same thing. Silly that MF5 would rely on another program for importing a file format. There must be others who do not use PhotoImpact.
I guess I can try installing it to see if this does the trick. I wonder if there is a workaround to get Tiff file importation without a whole program install I really don't need? Perhaps install it and then move the specific files out and then back again after uninstalling PI??
Thanks!
Hum? You know I never did install that PhotoImpact program since I had others for doing the same thing. Silly that MF5 would rely on another program for importing a file format. There must be others who do not use PhotoImpact.
I guess I can try installing it to see if this does the trick. I wonder if there is a workaround to get Tiff file importation without a whole program install I really don't need? Perhaps install it and then move the specific files out and then back again after uninstalling PI??
Thanks!
-
htchien
- Advisor
- Posts: 2013
- Joined: Sat Dec 11, 2004 12:10 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- Location: Taipei, Taiwan
- Contact:
I think you have mis-understood what Henry said. He did not say DVDMF would rely on PI to run, he said DVDMF uses some components that are been ported from PI. PI is not necessary to be installed to make DVDMF to run.
Those FIO / DLL files Henry listed are shared components in Ulead products. Every Ulead product will have a copy of them.
About the TIF file you use, can they be opened successfully in other image editors? Are you sure they are not corrupted? Please add the TIFF files one by one to make sure.
If those TIF files are not corrupted, please contact Ulead Tech Support in the following link and provide them the files so they can help to check why those TIFF files cause DVDMF to crash.
Ulead Tech Support:
http://www.ulead.com/tech/techsupport.htm
Hope this helps.
H.T.
Those FIO / DLL files Henry listed are shared components in Ulead products. Every Ulead product will have a copy of them.
About the TIF file you use, can they be opened successfully in other image editors? Are you sure they are not corrupted? Please add the TIFF files one by one to make sure.
If those TIF files are not corrupted, please contact Ulead Tech Support in the following link and provide them the files so they can help to check why those TIFF files cause DVDMF to crash.
Ulead Tech Support:
http://www.ulead.com/tech/techsupport.htm
Hope this helps.
H.T.
Last edited by htchien on Sat Dec 23, 2006 3:30 pm, edited 2 times in total.
Ted (H.T.)
[color=red]The message is provided AS IS with no warranties and confers no rights. For official tech support please contact Corel Tech Support.[/color]
[url=http://www.youtube.com/htchien]My YouTube channel[/url]
[color=red]The message is provided AS IS with no warranties and confers no rights. For official tech support please contact Corel Tech Support.[/color]
[url=http://www.youtube.com/htchien]My YouTube channel[/url]
Hi H.T.,
Sorry, I just meant to say that MF includes these modules. I only mentioned their origin in case someone looks at their properties.
Yes, thank you for clarifying. My statement was written poorly and could easily be misunderstood to think you would need to install PI.Those FIO / DLL files Henry listed are shared components in Ulead products.
Sorry, I just meant to say that MF includes these modules. I only mentioned their origin in case someone looks at their properties.
Henry