NoteWorthy Composer Forum

Forums => General Discussion => Topic started by: Arne Tredal on 2017-08-29 06:29 pm

Title: Fail to export to NWC 1.75 File after upgrade to 2.75a today
Post by: Arne Tredal on 2017-08-29 06:29 pm
After installing the 2.75a upgrade (nwcupd_from_v2.75.exe) the program crash every time I try to export to the NWC 1.75 format.
Export to MIDI works fine.
OS: Windows 10
Tried with and without Admin priviliges.
Same error every time:
"nwc2.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available"

Has anyone else tried to export to the 1.75 file format and experienced the same problems after upgrading to version 2.75a?

Kind regards,
Arne Trædal
Title: Re: Fail to export to NWC 1.75 File after upgrade to 2.75a today
Post by: Lloyd on 2017-08-29 06:55 pm
Has anyone else tried to export to the 1.75 file format and experienced the same problems after upgrading to version 2.75a?

I tested it when I read this thread and, in my system, NWC 2.75a crashed too.
I'm running NWC under WinXP Pro (32-bit). I have another session running Win7 Ultimate (64-bit) but I've not tested it yet...

Anyone more?
Title: Re: Fail to export to NWC 1.75 File after upgrade to 2.75a today
Post by: NoteWorthy Online on 2017-08-29 06:56 pm
Yes, I can confirm this. We are getting pretty far away from version 1 compatibility, but I will give this a look.
Title: Re: Fail to export to NWC 1.75 File after upgrade to 2.75a today
Post by: chripete on 2017-08-30 11:36 am
Same with my 2,75a
Title: Re: Fail to export to NWC 1.75 File after upgrade to 2.75a today
Post by: NoteWorthy Online on 2017-09-01 03:28 pm
This mechanism is fixed in 2.75a.2.
Title: Re: Fail to export to NWC 1.75 File after upgrade to 2.75a today
Post by: MusicJohn on 2017-09-01 05:42 pm

   Thanks.

   Some of us - me, for one - are still using 1.75 ... and W2k !

   MusicJohn, 1/Sep/17

Title: Re: Fail to export to NWC 1.75 File after upgrade to 2.75a today
Post by: Arne Tredal on 2017-09-05 08:28 pm
This mechanism is fixed in 2.75a.2.


Thank you.
It was truly promptly delivered.
-Arne