When will we see an update

It's been far too long for an update which fixes some of the more annoying bugs.

please!

K

 

it would be very cool to have multitimbral (8 part) with let say 8 stereo out !

 

most important bugs to fix

Yes, the OS 9 version did the multitimbral thing in standalone mode and that was a nice feature that was lost in OS X.

The bugs that I would like to see fixed are as follows:

1. (OS X) Sysex reception via MIDI works fine in standalone mode. No problems here! But as a VST plugin in Cubase SX 2 and SX 3, it does not work. Yet Cubase is sending the sysex to the plugin and even shows it in the activity bar. Please fix this.

2. (OS X) In standalone mode, open the preferences/audio setup. Check the MIDI tab. If another program establishes a virtual port (which is allowed to happen at any time in CoreMIDI and all programs are required to handle the change messages from CoreMIDI), the Audio Setup does correctly display that port. BUT, the FM7 (and also all other NI products) do not connect to that port correctly, and if you try clicking on any of the ports here, the FM7 will do a hard crash when you close this Audio Setup dialog. This is a serious crashing bug that affects the entire NI product line.

3. (OS X Tiger only) f you play the virtual keyboard using the QWERTY keyboard, all the keys you press stick! This also affects some other NI products as well but I forget offhand which ones.

Thanks.

 

another FM7 crasher

Found another serious bug in the FM7: In the OS X standalone version, if you Hide the application (press the yellow button on the menu bar), it immediately crashes, with the following report. It would be really good also if Native Instruments would set up some forums for reporting bugs.

OS Version: 10.4.2 (Build 8C46)

Command: FM7
Path: /Applications/FM7.app/Contents/MacOS/FM7
Parent: WindowServer [105]

Version: FM7 1.1.1.015 (1.1.1, Copyright © 2003 Native Instruments)

PID: 1331
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x68696475

Thread 0 Crashed:
0 com.native-instruments.fm7 0x000d2380 std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string[in-charge](std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 24
1 com.native-instruments.fm7 0x000e3670 std::basic_string<char, std::char_traits<char>, std::allocator<char> > std:perator+<char, std::char_traits<char>, std::allocator<char> >(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char) + 36
2 com.native-instruments.fm7 0x000a9e7c NI::GP::FileName::getSystemPath() const + 44
3 com.native-instruments.fm7 0x000acc64 NI::GP::FileManager::existsFile(NI::GP::FileName const&) + 28
4 com.native-instruments.fm7 0x000178b4 FM7Stream:penFile(NI::GP::FileName const&) + 48
5 com.native-instruments.fm7 0x00062ce8 FM7App:nEvent(unsigned, NI::UIA::EventData*) + 224
6 com.native-instruments.fm7 0x000b0c4c NI::UIA::Application:nWndEvent(unsigned, NI::UIA::EventData*, NI::UIA::Application::WndEventExtra const&) + 28
7 com.native-instruments.fm7 0x000b0bec NI::UIA::Application::sendEvent(unsigned, NI::UIA::EventData*) + 64
8 com.native-instruments.fm7 0x000b5fdc NI::UIA:ETAIL::WindowImpl::sendEvent(unsigned, NI::UIA::EventData*, bool) + 224
9 com.native-instruments.fm7 0x000b8a74 NI::UIA:ETAIL::WindowImplBaseMacOS::handleCommandEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*) + 408
10 com.native-instruments.fm7 0x000b7e04 NI::UIA:ETAIL::WindowImplBaseMacOS::handleEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*) + 584
11 com.native-instruments.fm7 0x000be88c NI::UIA:ETAIL::WindowImplMacOSStandAlone::handleEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*) + 32
12 com.native-instruments.fm7 0x000b7ac0 NI::UIA:ETAIL::WindowImplBaseMacOS::eventHandlerProc(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 84
13 com.apple.HIToolbox 0x931229f4 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 692
14 com.apple.HIToolbox 0x9312214c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372
15 com.apple.HIToolbox 0x93128ed0 SendEventToEventTarget + 40
16 com.apple.HIToolbox 0x931a1dd0 SendHICommandEvent(unsigned long, HICommand const*, unsigned long, unsigned long, unsigned char, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 380
17 com.apple.HIToolbox 0x931d1e14 SendMenuItemSelectedEvent + 136
18 com.apple.HIToolbox 0x931ed378 HandleKeyboardEvent(OpaqueEventRef*, unsigned char) + 340
19 com.apple.HIToolbox 0x931229f4 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 692
20 com.apple.HIToolbox 0x9312214c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372
21 com.apple.HIToolbox 0x93121fc8 SendEventToEventTargetWithOptions + 40
22 com.apple.HIToolbox 0x931ec688 HandleKeyboardEvent(OpaqueEventRef*, unsigned long) + 320
23 com.apple.HIToolbox 0x9312924c ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 512
24 com.apple.HIToolbox 0x93122c44 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1284
25 com.apple.HIToolbox 0x9312214c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372
26 com.apple.HIToolbox 0x93128ed0 SendEventToEventTarget + 40
27 com.apple.HIToolbox 0x93169e00 ToolboxEventDispatcher + 92
28 com.apple.HIToolbox 0x93169d8c HLTBEventDispatcher + 16
29 com.apple.HIToolbox 0x93168340 RunApplicationEventLoop + 148
30 com.native-instruments.fm7 0x000b608c NI::UIA::Application::run() + 32
31 com.native-instruments.fm7 0x000b16a0 NI::UIA:ETAIL::AppModuleStartup::messageLoop() + 60
32 com.native-instruments.fm7 0x000b1548 NI::UIA:ETAIL::AppModuleStartup::run() + 28
33 com.native-instruments.fm7 0x00064ed0 main + 16
34 com.native-instruments.fm7 0x000036dc _start + 380
35 com.native-instruments.fm7 0x0000355c start + 48

 

The idea of a bug-report forum/area is good.
Users out here in the real world are really the best beta-testers for any company.

Aside from fixing bugs, it would be great to see a few new simple features.
How about a small info field which tells you the name of the currently loaded bank?

There must be plenty more....

 

Re: most important bugs to fix

If you look on page 45 of the manual, it says that receiving sysex as a VST plugin IS NOT POSSIBLE because the VST standard doesn't support sysex...
ew

 

the sysex fix

Interesting, I see that in my manual too.

Unfortunately, that information is out of date. VST has supported sysex for several years now. In the VST specification, check for the kVstSysExType event type.

In software, it's supported as far back as Cubase VST 5.1. Cubase SX 1 did leave it out accidentaly, but it was supposed to be added back.

If the FM7 VST could check incoming packets for kVstSysExType and parse them like it does correctly in the standalone version, things would be great.

 

how to fix the sysex, with pointers to the code

OK, at least six years now: it's documented in the VST development kit's aeffectx.h header file for the 2.1 VST standard, dated 2000. If their code is like every other VST plugin, if NI will search the FM7 code base for where they check for kVstMidiType and kVstParameterType, they will be able to add a third case right there for kVstSysExType, handle the sysex with the code they already have and everything will be hunky dory.

I can also do the fix for them if they wish to contract with me to do so & also could find and fix all the other problems the FM7 has in OS X Tiger for them in case they are swamped with other projects at this time.

 

I agree that at least 8 part multitimbrality and 8 stereo outs would be a really helpfull feature. And the same thing applies to Pro-53 too

 

I'd like to see multitimbrality too. I'd also like to know if there will be an update. When I bought my FM7 I got it on sale, and the salesperson opined that this was because NI is discontinuing it. NI, say it isn't so!

 

No, we didn't discontinued the FM7.

Best regards,
Steffen (NI, Berlin)

 

Thanks, Steffen, that's good to know. I'd have considered it a good buy anyway, but it's nice to know that there will be more to come.

 

hi,
didn´t want to create a new topic, but i am very interested in the FM7, the only thing that makes me hesitate is one thing: if i´m not mistaken it´s copy protection asks for the original disc every now and then... call me lame, but i prefer to have it stored in the original box... or is there an update which enables online registration like the newer NI products do have?

and if there isn´t such an update... how frequently does it ask for the disc?

thx,
Jan

 

You'll need the CD for installation and when installing updates, other than that you won't be asked for the CD again...

 

cool, this sounds great - going to get the FM7 in the near future!

 

New features would be nice but fixing bugs is long overdue. In fact it was almost two years ago that I assured that the fixes were coming soon. oh well

K

ps thanks for the topic support my fellow fm7 users

 

Still waiting.....

This thread deserves a revival.
As an old faithful NI product customer, I feel very neglected. FM7 could certainly have a few repairs, and also a couple long-awaited new features.

How about it NI? Please don't dump your supportive customer base.

Regards - Colin

 

Would be nice. Somebody had a look at Octobus from Linplug - FM with 8 operators and 2 filters etc, lots of multistage envelopes, flexible mod-matrix, etc.

Lots of nice features. FM7II wih flexible mod-matrix, better and additional filters, perhaps more operators would be nice.
And of course the stepped pitchbend behavior, etc. etc.

 

I had a look at it...

 

>> I had a look at it...

Well, obviously a comment I do not fully understand. Any more comments on that thing and on Linplug (PM is also ok - uff at gmx.net)

Thanks,
Steff