Switch from Storyboard to Timeline causes a crash.

I’ve already submitted this to Tech Support, and awaiting a reply, but I’m wondering if anyone else has experienced this. Open a new file. See that it’s in Storyboard mode. Drag in some images. Drag in an audio track. Switch over to Timeline mode. Does FM 5.0b28 crash on you?

Everything was working fine on my system about a week ago under Yosemite, and all pre-existing slide shows worked perfectly under FM 4.6.3 – AND – FM 5.0b28. I updated to El Capitan and all hell as broken loose. All but one of my large slideshows made in FM 4.6.3 and earlier will no longer open without crashing the app (only one of them works as expected). I also have the above related crash from Storyboard > Timeline (in BOTH FM 4.6.3 and FM 5.0b28). Tech support said FM has been tested in El Capitan – but I only started having these problems after I performed the OS X update. Both 4.6.3 and 5.0b28 work fine on my wife’s MacBook Pro still running Yosemite.

One baby step at a time – I noticed that a 5.0b32 was released and I just installed and ran it. The switch from Storyboard to Timeline and back seems to be fixed. I dragged in an audio track and that seemed to work, too. Yeah!!

I still can’t open a pre-existing slide show without getting an immediate app crash, though – hope that’s still being looked into…

No, does not happen with my FM 5.0b30 (21391)

but at quit of FM app:

Process: FotoMagico 5 [266]
Path: /Applications/FotoMagico 5.app/Contents/MacOS/FotoMagico 5
Identifier: com.boinx.FotoMagico5
Version: 5.0b30 (21391)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: FotoMagico 5 [266]
User ID: 501

Date/Time: 2015-10-10 21:04:32.613 +0200
OS Version: Mac OS X 10.11 (15A284)
Report Version: 11
Anonymous UUID: D49F1CB2-78C9-9A49-0250-D7C64AF18E5A

Time Awake Since Boot: 530 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Codes: EXC_I386_GPFLT

Hi, willyman – First, I’d update your 5.0b30 version to 5.0b32, and then go from there. Your error message shows you’re using 5.0b30 – something’s been fixed in the b32 revision.