You are viewing an archive of the old fxhome.com forums. The community has since moved to hitfilm.com.

Image stretching error (fix coming in 1.0.4)

Posted: Fri, 30th Apr 2004, 4:19am

Post 1 of 3

MarkB

Force: 220 | Joined: 7th Mar 2004 | Posts: 47

Gold Member

Downloaded the official copy today finally. I took two jpgs, stretched them out to 60 frames and went to the middle of the top frame and set its transparency to 100, then rendered. It crashed with error "integer expected 60.000". The textfile it generated is below.

Interestingly when I used task manager to kill it, in the dialog box it says, "You chose to end the nonresponsive program, Macromedia Projector", clicking on the "see data" gives:
szAppName : Chromanator.exe szAppVer : 10.0.0.188 szModName : dirapi.dll
szModVer : 10.0.0.188 offset : 00061125

I had not changed my render defaults from what it came with (format quicktime none, render high quality opengl)

Ive posted the project and graphics at http://markbutler.8m.com/ctest.zip Every time I load the project, go into the track 2 object and back to project view, it asks if I want to render, if I say yes it crashes.


Error textfile created:
<object>
[#object_type : #error]
[#os: "WinXP"]
[#director_os: "Windows,32"]
[#version: "5.1"]
[#directx: "9.0.0"]
[#quickTime: 6.5000]
[#color_depth: 32]
[#application_name: "chromanator"]
[#application_type: #standard]
[#application_version: 1000003]
[#total_memory: 1073000448]
[#free_memory: 1156047284]
[#error: "Script runtime error"]
[#Message: "Integer expected"]
[#function_list: [#o5, #cc3, #cc4, #cc4, #cc4, #o3, #cc1, #cc1, #cc1, #cc1, #v58, #v58, #e6, #h2, #a9, #a17, #aa2, #v58, #o5, #d11]]
</object>

Help!
Mark
Posted: Fri, 30th Apr 2004, 11:15am

Post 2 of 3

Cogz

Force: 16050 | Joined: 18th Jun 2002 | Posts: 674

VisionLab User VideoWrap User PhotoKey 5 Pro User MuzzlePlug User PowerPlug User FXpreset Maker Windows User MacOS User

FXhome Team Member

I've downloaded your project file, and indeed I also get error you have, however if i delete the image in track 2, then put it back, stretching it and adding the transparency the same as yours it works fine. We'll look into it for you, thank you for bringing it to our attention.
Posted: Fri, 30th Apr 2004, 11:37am

Post 3 of 3

Joshua Davies

Force: 25400 | Joined: 21st Mar 2001 | Posts: 3029

VisionLab User VideoWrap User PhotoKey 5 Pro User MuzzlePlug User PowerPlug User PhotoKey 3 Plug-in User FXpreset Maker Windows User MacOS User

FXhome Team Member

We've had one report of a similar bug, it has now been fixed in release 1.0.4 which should appear on the site on Monday - sorry for the trouble its caused you.