PLEASE HELP !! - FM8 64 bit does not play starting note in arpeggiator

Now this is annoying

FM8 64 bit does not play first note in arpeggiator when playing a MIDI note in the sequencer. I use Sonar X1 Prod 64 bit and I really don't think the problem is with Sonar. And I am facing this only since I moved to FM8 64 bit. The yellow bar running above the notes seems to visibly skip the first note most times, but it plays it at times too, just cant figure out what the problem pattern is.
Does anyone have the fix for this ?

Or is NI going to release an FM8 64 bit update to fix this please, really so important to have this fix as the arpeggiator is the cream function of FM8.

Any feedback of similar experience or any successful fix will be very helpful and appreciated. Thanks in advance.

 

I have the same problem. I described it in this video (in German).
http://www.youtube.com/watch?v=ZMK59KO6RHc
I noticed that the problem does not occur when you hit the key of the virtual keyboard of the GUI with your mouse. The first step is only skipped if I use an external keyboard. So maybe it's a latency problem? I don't know - probably not.

 

And here in English: http://www.youtube.com/watch?v=vfh9L-YpVMs&feature=em-upload_owner

Also described here: http://www.native-instruments.com/forum/showthread.php?194274-Really-bad-Arpeggiator-bug

And I found out that it does not happen when using the JBridged 32bit version of the plugin. Does anyone have an explanation?

 

Thanks Michael.

Seems I am not the only one having this problem in FM8. I also checked different possibilities. Its OK when I hit the virtual keyboard in the synth and also OK when I hit the computer keyboard letter mapped to notes. Its only when I play the note with my MIDI controller (Korg Nanokey), I don't get the first note in the arpeggiator. And the problem is in the standalone version also, not just the VST, which confirms that the problem is NOT inside the DAW (Sonar in my case). In fact, interesting thing is that the problem is also there when the DAW plays a MIDI track routed to FM8 arp. So, doesn't seem like a latency problem as well. I think it just seems to be a bug in FM8 64 bit version (even in the latest update 1.3.0). This problem was never there in the FM8 32 bit version.

I hope someone technical from NI are looking at this and hopefully working on a fix which could come as part of the next FM8 update. Is there any way to find out ? Can someone from NI reply please ! I've got many previously saved projects running FM8 arp and they all miss the first note of the arp at every MIDI note and its so disappointing

 

I reinstalled version 1.0.4 now. The bug was not there in that one which is from 2009. But probably many other bugs will pop up now...

 

Same here. Standalone 64 bit version on Win-7.

 

Michael,

Is the version 1.0.4 that you reinstalled 32-bit or 64-bit. I presume it is 32-bit. Or did FM8 have 64-bit from that time ? Are you using Win or Mac ? I see that in 1.1.1 update of FM8, 64-bit support for Mac OS X was introduced. No update specifically states 64-bit intro for Windows. Do you know when 64-bit support was introduced for FM8 under Windows, in which update ?

Also I see that in update 1.2.0 for FM8, new preset format and sound browser was introduced.

 

Hi Ramscapri,

sorry, I don't know the details about the FM8 version history. I am quite sure that the standalone version 1.0.4 already had a 64-bit architecture. At least there was a 64-bit version of the VST-plugin at that time. I am using Windows.

It would be great to have the option of loading at least the last version of FM8 which did not have the problem, but the NI download section only offers the latest patch.

And you are right, there was an update of the preset format which made me go back to the buggy 1.3.0 now, because I use several presets which could not be loaded in the older version. I hope NI won't wait too long with an update for the standalone instrument. Meanwhile I will only use the 32-bit version with a VST Host for live performances.

 

hi Michael,

In fact, the NI updates download section offers all the previous update patches of FM8 in case you want to try. I can see them available for download in the web site updates section, probably wont be available directly from service centre which I think you are referring to. Service centre offers only the latest version. For FM8, 1.1.1, 1.2.0, 1.2.1 and 1.3.0 are available. The preset format update was made in 1.2.0.

I am not sure if I will go right away for a full uninstall and re-install exercise but in case you do, please keep us posted on results.

Thanks and cheers...

 

Actually I wasn't referring to the Service Center, but I did not pay attention to the little check-box on the website that only the updates should be displayed which I had not installed yet. So thanks for that one! Now I have downloaded the 1.2.1 version, but I don't think I will go back immediately. By the way, can we be sure that the bug was "introduced" by the lastest update or could it come from an older one as well?

I haven't been using FM8 in the live context for a long time so there was no need for using the standalone version. And even now it is not absolutely necessary because in a hosting software I can still fall back on the 32-bit VST-plugin.

 

Really no idea which update brought about the first-note-missing-bug !
I have got into the 64-bit environment only now and directly to the FM8 1.3.0 64-bit version. Never had the problem in 32-bit. Of course, couldnt install the 1.3.0 32-bit update in my previous laptop possibly because it was a Win Vista SP2 32-bit. I guess some of the latest updates need a minimum of Windows 7 to get installed.

And by the way, 1.2.0 could also do unless you need the AAX plugin format (for avid) which was the main purpose of the 1.2.1 update.

True that we can have the 32-bit version in hosting environment, but one major drawback seems to be that in 32-bit plugin under 64-bit host, no automation / ACT, etc icons appear on the top right corner as it operates under bitbridge. Or am I missing something somewhere ? Can we still do everything in the 32-bit version as we can in the 64-bit OR as we could do when we use the 32-bit plugin under 32-bit host ?

 

Did somebody report this Bug already to NI?
They now seem to have some practise in fixing 64 bit bugs.

 

I had put in a report to technical support few days ago. No reply yet...

 

I wrote a report about a week ago. Haven't heard from NI since then.

 

Soooo.......

I am running 1.2.0 now and the arpeggiator does not work either. Seems we have been living with this bug for quite a while without any notice. Maybe this is the reason for NI not being too hasty anwering our requests.

 

I finally got a reply from NI support after 12 days. Part of the reply is : "If possible, please try to reproduce this issue by using an other DAW (Logic,
Cubase, Ableton Live) and let me know, if you experience the same."

Michael and others, can you help on this. Please msg back which DAWs you use and if you experience the same problem with FM8 64 bit.
I do not use any other DAW so I can reply back to NI saying that there are others with other DAWs having the same issue.

Thanks.

 

Hi,
as I wrote: I can reproduce this issues in standalone-FM8 without any DAW.
Chris

 

Me too. The bug occurs in the standalone application and in the 64-bit-VSTi (using Cubase 6, VST Host and Cantabile Lite). I am running Windows 7 64 bit.

 

NI confirmed the bug today and announced that they are going to fix with an update it in the near future.

 

Experiencing this also. Need a fix asap. Would it help in any way for me to lodge a ticket or feedback?