Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
107 user(s) are online (58 user(s) are browsing Forums)

Members: 1
Guests: 106

daveyw, more...

Headlines

 
  Register To Post  

(1) 2 »
Pixy new pixel editor for amigaos4
Just can't stay away
Just can't stay away


See User information
I would like to let you know that there is a new graphic program for amiga os4 that,imho, is worth to try!

http://www.os4depot.net/modules/comme ... le=graphics/edit/pixy.lha

Go to top
Re: Pixy new pixel editor for amigaos4
Just popping in
Just popping in


See User information
I agree! It is a fantastic Hollywood app. Calling it a pixel editor does a dis-service to the breath of the program. Not only does have it have great pixel tools it also has a full animation suite. You can load up a gif anim, change it, and save it back out.

Just a great app!

Bill "tekmage" Borsari


Go to top
Re: Pixy new pixel editor for amigaos4
Site Builder
Site Builder


See User information
I agree that it looks great, but unfortunately, the latest demo also crashes on start on my system.

Follow me on
Ko-fi, Twitter, YouTube, Twitch
Go to top
Re: Pixy new pixel editor for amigaos4
Home away from home
Home away from home


See User information
@George
Same for me. All versions i tried crashes on start.

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Pixy new pixel editor for amigaos4
Just popping in
Just popping in


See User information
@All

Thank you for the complements

I'm sorry for the crash I haven't yet found the problem ...

Go to top
Re: Pixy new pixel editor for amigaos4
Just popping in
Just popping in


See User information
Tried the latest Version. I got it working one time but most of the time it crashes on startup. Looks promising. I like the quick browsing/applying of Filters in the Filter Manager.

Go to top
Re: Pixy new pixel editor for amigaos4
Just popping in
Just popping in


See User information
@All

For people who have a crash when starting I would like to know:

- Which language English or ?
- What machine ?
- Os4 or Morphos ?
- Pixy test on HD or RAM Disk?

Go to top
Re: Pixy new pixel editor for amigaos4
Just popping in
Just popping in


See User information
@sinisrus

- Which language English or ?
English Version of Pixy

- What machine ?
X5000 (P5020)

- Os4 or Morphos ?
OS4

- Pixy test on HD or RAM Disk?
Tried both. Launching from an SFS2 Partition lead more often to success than launching from an NGFS Partition or from RAM Disk. But this might just be a coincidence.

Go to top
Re: Pixy new pixel editor for amigaos4
Just popping in
Just popping in


See User information
@IamSONIC

Thank you

Is it possible for you to test with french localization ?

Go to top
Re: Pixy new pixel editor for amigaos4
Just popping in
Just popping in


See User information
Hi All,

I've been looking in to this for a while now. What I've found is a problem between HollyWood, MUI, and codesets library. There are two apps which reliably trigger this problem, SQLman and Pixy. Run either of those apps on a X5000 running OS 4 and you'll see a similar stack trace:

Stack trace:
native kernel module newlib.library.kmod+0x00034bd0
LIBS:codesets.library:LIB_CodesetsConvertStrA()+0x178 (section 1 @ 0x85FC)
module SYS:Storage/Hollywood/hollywood.IAVPXD/MUIRoyale.hwp at 0x7DC9CF74 (section 0 @ 0x9F50)
module SYS:Storage/Hollywood/hollywood.IAVPXD/MUIRoyale.hwp at 0x7DCB2280 (section 0 @ 0x1F25C)

At AmiWest and on IRC I've been asking people to test Pixy and the results are very consistent.

Personally I have tried different versions of OS 4 kernels and MUI builds with no change in results. Hope we can get this fixed, I'd like to use both those apps on my X5000.

Bill "tekmage" Borsari

Go to top
Re: Pixy new pixel editor for amigaos4
Just popping in
Just popping in


See User information
@sinisrus

Quote:
Is it possible for you to test with french localization ?


Switched the language to french. No difference.

I get the same stack trace like the one tekmage posted.

Go to top
Re: Pixy new pixel editor for amigaos4
Home away from home
Home away from home


See User information
@sinisrus

What version of codeset.library does it work with?
What version of MUIRoyale.hwp do you have?

Can you put in a check, for version number in Hollywood?

(NutsAboutAmiga)

Basilisk II for AmigaOS4
AmigaInputAnywhere
Excalibur
and other tools and apps.
Go to top
Re: Pixy new pixel editor for amigaos4
Not too shy to talk
Not too shy to talk


See User information
@tekmage

I can confirm it's something with MUIroyal/Mui,

On a cold/warm reboot Pixy works without a crash no matter how
many times I restart it.

As soon as I start another MUI app(have it open or closed) I get random Pixy crashes after that.

Edit: @sinisrus Thank you for this app!
It's a really nice app with our without bug,
keep up the good work.

1989-> A500, A600, A3000, A4000, A1200, CD32, µA1, PegII, A1XE, CDTV, Amy/416D79, A1X5000, Vampire 500 V2+, Vampire 600 V2, Amy-ITX, Denise ITX <-2024
Go to top
Re: Pixy new pixel editor for amigaos4
Quite a regular
Quite a regular


See User information
@sinisrus
Quote:
For people who have a crash when starting I would like to know:

- Which language English or ?
- What machine ?
- Os4 or Morphos ?
- Pixy test on HD or RAM Disk?


For me it crashes sometimes on start but not evey time.

- English - X1000 - OS4 - HD

Here is the start of the crash log:

Crash log for task "Pixy"
Generated by GrimReaper 53.19
Crash occured in module kernel at address 0x02007008
Type of crash: program exception
Alert number: 0x80000008

Register dump:
GPR (General Purpose Registers):
0: 0204B4B0 5B6D2D00 00000000 00000000 12C83000 0000000C 00000000 01D65E80
8: 194FF825 A7FC1280 00000000 02003030 00000000 00000000 5B780000 5B780A98
16: 5B6F0000 5B714B7C 5B6D32F8 5A7C6020 5B780000 5B714A98 5B780000 5A7DA3C0
24: 5A932020 FFFFFAFF 02A87274 00000005 DF725D50 00000000 000CA7FC 12C83000


FPR (Floating Point Registers, NaN = Not a Number):
0: nan 0 3.32193 1.35004e-08
4: -0.0909091 4.01381e-05 0.584962 0.00826446
8: 1 0.0140618 -0.118583 -9.34567e-09
12: 96 4.5036e+15 0 0
16: 0 0 0 0
20: 0 0 0 0
24: 0 0 0 0
28: 4.5036e+15 4.5036e+15 2.14748e+09 0

FPSCR (Floating Point Status and Control Register): 0x82002000


SPRs (Special Purpose Registers):
Machine State (msr) : 0x02043030
Condition (cr) : 0x4A730000
Instruction Pointer (ip) : 0x02007008
Xtended Exception (xer) : 0x4A5ED134
Count (ctr) : 0x00570001
Link (lr) : 0x00000000
DSI Status (dsisr) : 0x4A5ECDB0
Data Address (dar) : 0x39553933



680x0 emulated registers:
DATA: 61F541FE 00000003 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 6FFA4000 00000000 00000000 00000000 00000000 00000000 00000000 5B6D2560
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x02007008 belongs to module "kernel" (HUNK/Kickstart)

Stack trace:
native kernel module kernel+0x00007008
native kernel module kernel+0x0000d214
native kernel module kernel+0x00051624
native kernel module kernel+0x000329e0
native kernel module kernel+0x00033520
module Pixy at 0x7F8B0DB8 (section 0 @ 0x241D94)
module SYS:Storage/Hollywood/hollywood.TVGRZH/MUIRoyale.hwp at 0x7F630094 (section 0 @ 0x16070)
module SYS:Storage/Hollywood/hollywood.TVGRZH/MUIRoyale.hwp at 0x7F6337A8 (section 0 @ 0x19784)
module SYS:Storage/Hollywood/hollywood.TVGRZH/MUIRoyale.hwp at 0x7F623690 (section 0 @ 0x966C)
module SYS:Storage/Hollywood/hollywood.TVGRZH/MUIRoyale.hwp at 0x7F6299F8 (section 0 @ 0xF9D4)
module Pixy at 0x7F775830 (section 0 @ 0x10680C)
module Pixy at 0x7F77C838 (section 0 @ 0x10D814)
module Pixy at 0x7F775F20 (section 0 @ 0x106EFC)
module Pixy at 0x7F772C68 (section 0 @ 0x103C44)
module Pixy at 0x7F774E30 (section 0 @ 0x105E0C)
module Pixy at 0x7F774F1C (section 0 @ 0x105EF8)
module Pixy at 0x7F772958 (section 0 @ 0x103934)
module Pixy at 0x7F690E0C (section 0 @ 0x21DE8)
module Pixy at 0x7F7FEE3C (section 0 @ 0x18FE18)
module Pixy at 0x7F677C68 (section 0 @ 0x8C44)
module Pixy at 0x7F7F9008 (section 0 @ 0x189FE4)
module Pixy at 0x7F8B1174 (section 0 @ 0x242150)
module Pixy at 0x7F8B3CBC (section 0 @ 0x244C98)
0x61727400 symbol not available

PPC disassembly:
02007000: 78840020 rldicl r4,r4,0,1
02007004: 7c642378 or r4,r3,r4
*02007008: 7c002264 tlbie r4
0200700c: 4e800020 blr
02007010: 7d6000a6 mfmsr r11

System information:

CPU
Model: P.A. Semi PWRficient PA6T-1682M VB1
CPU speed: 1800 MHz
FSB speed: 900 MHz
Extensions: altivec

Machine
Machine name: AmigaOne X1000
Memory: 2097152 KB
Extensions: bus.pci bus.pcie


AmigaOne X1000, uA1
Go to top
Re: Pixy new pixel editor for amigaos4
Not too shy to talk
Not too shy to talk


See User information
Suddenly, the initial crash has gone :-O I'm 100% sure it was with the new version, too.

But more important is, it consumes 100% CPU immediately after start and all the time. So smooth painting is no go on my SAM440 HD7750.

CD32/A500/A600/A600+Furia/A1200/A4000D+A2320+PiccoloSD64/Sam440 flex 800MHz RAM 1GB HD7750 128MB OS4.1 SBLive! ->
Go to top
Re: Pixy new pixel editor for amigaos4
Home away from home
Home away from home


See User information
@ktadd

I wonder...

Why is it picking up MUIRoyale.hwp from SYS:Storage/Hollywood in your crash log?

I can't find MUIRoyale.hwp in Pixy's install archive, so I guess it's hardcoded into the executable (?)

Try to rename, move or delete that Sys:Storage/Hollywood dir and try again.

@all

Why are Hollywood programs placing something into Sys: anyway?
I'd be concerned if I didn't know about this...

People are dying.
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
Go to top
Re: Pixy new pixel editor for amigaos4
Just popping in
Just popping in


See User information
@Raziel

Exactly MuiRoyal.hwp is include in pixy

Go to top
Re: Pixy new pixel editor for amigaos4
Just popping in
Just popping in


See User information
@all

Please test this add tooltype of the icon pixy :

SKIPPLUGINS=*

Go to top
Re: Pixy new pixel editor for amigaos4
Home away from home
Home away from home


See User information
@sinisrus
Quote:

Please test this add tooltype of the icon pixy :

SKIPPLUGINS=*


Same crash sadly

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Pixy new pixel editor for amigaos4
Just can't stay away
Just can't stay away


See User information
Here too I get a crash on my SAM460ex:

English, SAM460ex, OS4, RAM:


codesets.library V6.21


Crash log for task "Pixy"
Generated by GrimReaper 53.19
Crash occured in module newlib.library.kmod at address 0x01B59390
Type of crash: DSI (Data Storage Interrupt) exception
Alert number: 0x80000003

Register dump:
GPR (General Purpose Registers):
0: 6FFB4000 52A54870 00000000 50B2811D 00000021 00000010 FEFECAFE FEFECAFE
8: FEFECAFE FEFECAFE 5D29958C 00000008 00002EE3 00000000 511E9A14 511E9A10
16: 52A54B1C 00000000 511E9908 511E9A90 52A54A58 511E9A14 511E9A14 50B29C14
24: 50B2811D 5D2EF170 00000000 5F4E0000 50B2811D 5D475018 5F4E0000 52A549C8


FPR (Floating Point Registers, NaN = Not a Number):
0: nan 1 3.32193 1.35004e-08
4: -0.0909091 4.01381e-05 0.584962 0.00826446
8: 1 0.0140618 -0.118583 -9.34567e-09
12: 174 4.5036e+15 1.23719e+276 4.63652e+34
16: 1.82212e-24 3.77197e-05 7.70794e-169 3.05493e-82
20: 9.8214e-10 2.16435e-284 7.75565e+303 -1.0788e-81
24: 2.87896e-24 5.8666e-51 -0.00921478 -1.43682e+294
28: 4.5036e+15 4.5036e+15 2.14748e+09 0

FPSCR (Floating Point Status and Control Register): 0x82002000


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0002F030
Condition (cr) : 0x00000010
Instruction Pointer (ip) : 0x01B59390
Xtended Exception (xer) : 0x020F0000
Count (ctr) : 0x5FEF4AB0
Link (lr) : 0x02119BE4
DSI Status (dsisr) : 0x425C2DB0
Data Address (dar) : 0x01840188



680x0 emulated registers:
DATA: A5C5F100 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 6FFA6000 00000000 00000000 00000000 00000000 00000000 00000000 52A54680
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x01B59390 belongs to module "newlib.library.kmod" (HUNK/Kickstart)

Stack trace:
native kernel module newlib.library.kmod+0x00004010
LIBS:codesets.library:LIB_CodesetsConvertStrA()+0x178 (section 1 @ 0x85FC)
module SYS:Storage/Hollywood/hollywood.IBKTQW/MUIRoyale.hwp at 0x7B8BDF74 (section 0 @ 0x9F50)
module SYS:Storage/Hollywood/hollywood.IBKTQW/MUIRoyale.hwp at 0x7B8D3280 (section 0 @ 0x1F25C)
module SYS:Storage/Hollywood/hollywood.IBKTQW/MUIRoyale.hwp at 0x7B8D5244 (section 0 @ 0x21220)
module SYS:Storage/Hollywood/hollywood.IBKTQW/MUIRoyale.hwp at 0x7B8D61EC (section 0 @ 0x221C8)
module SYS:Storage/Hollywood/hollywood.IBKTQW/MUIRoyale.hwp at 0x7B8D8430 (section 0 @ 0x2440C)
module SYS:Storage/Hollywood/hollywood.IBKTQW/MUIRoyale.hwp at 0x7B8CD3D0 (section 0 @ 0x193AC)
module SYS:Storage/Hollywood/hollywood.IBKTQW/MUIRoyale.hwp at 0x7B8BD5B4 (section 0 @ 0x9590)
module SYS:Storage/Hollywood/hollywood.IBKTQW/MUIRoyale.hwp at 0x7B8C39F8 (section 0 @ 0xF9D4)
module Pixy at 0x7B9FB830 (section 0 @ 0x10680C)
module Pixy at 0x7BA02838 (section 0 @ 0x10D814)
module Pixy at 0x7B9FBF20 (section 0 @ 0x106EFC)
module Pixy at 0x7B9F8C68 (section 0 @ 0x103C44)
module Pixy at 0x7B9FAE30 (section 0 @ 0x105E0C)
module Pixy at 0x7B9FAF1C (section 0 @ 0x105EF8)
module Pixy at 0x7B9F8958 (section 0 @ 0x103934)
module Pixy at 0x7B916E0C (section 0 @ 0x21DE8)
module Pixy at 0x7BA84E3C (section 0 @ 0x18FE18)
module Pixy at 0x7B8FDC68 (section 0 @ 0x8C44)
module Pixy at 0x7BA7F008 (section 0 @ 0x189FE4)
module Pixy at 0x7BB37174 (section 0 @ 0x242150)
module Pixy at 0x7BB375F4 (section 0 @ 0x2425D0)
native kernel module dos.library.kmod+0x00029c78
native kernel module kernel.debug+0x000811c4
native kernel module kernel.debug+0x0008123c

PPC disassembly:
01b59388: 38a00010 li r5,16
01b5938c: 7ca103a6 mtxer r5
*01b59390: 7cc3642a lswx r6,r3,r12
01b59394: 7ccb389d .word 0x7CCB389D
01b59398: 7d8c5a14 add r12,r12,r11

System information:

CPU
Model: AMCC PPC460EX V1.2
CPU speed: 1155 MHz
FSB speed: 231 MHz
Extensions:

Machine
Machine name: Sam460ex
Memory: 2097152 KB
Extensions: bus.pci bus.pcie
...

Go to top

  Register To Post
(1) 2 »

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project