Quantize MFX Broken - Cakewalk Please Fix !!!

RE: Quantize MFX Broken (in response to Ron Kuper) (planist)

Sun, 18 Jul 2004 08:11:41 GMT

The fix for the envelope bug is coming very soon, probably this week. It'll be a patch to the VST Adapter, which is actually at fault for this bug.

when? " />

RE: Quantize MFX Broken (in response to Ron Kuper) (cmusicmaker)

Sat, 17 Jul 2004 19:02:01 GMT

ORIGINAL: raja

Hey Ron,

So . . . if we're using Dxi plug-ins, or you are using DirectiXer, there are no envelope automation problems?

Roger Windsor

That is an interesting point...Console is another DXi > VST wrapper (an loads more) but I don't think it solves the problem either.

RE: Quantize MFX Broken (in response to Ron Kuper) (raja)

Tue, 13 Jul 2004 10:04:17 GMT

Hey Ron,

So . . . if we're using Dxi plug-ins, or you are using DirectiXer, there are no envelope automation problems?

Roger Windsor

RE: Quantize MFX Broken (in response to Ron Kuper) (JamminFool)

Mon, 12 Jul 2004 22:06:04 GMT

thank you, ron!

that is perfectly acceptable (and much appreciated).

RE: Quantize MFX Broken (in response to Ron Kuper) (planist)

Mon, 12 Jul 2004 10:15:23 GMT

(This is true even of the VST Adapter patch, but thankfully the adapter is a separate DLL component so have an opportunity to get an update out now.)

yes, please keep the adapter seperate from sonar - i had so mnany problems with the combined things in cubase sx (sometimes the main program wouldnt start because of one plugin!!)

jeff

RE: Quantize MFX Broken (in response to Ron Kuper) (Bill OConnell)

Mon, 12 Jul 2004 10:13:58 GMT

ORIGINAL: As much as I would be disappointed to be forced to pay to fix features that Cakewalk broke, I think I would also be surprised. There are a couple of other MIDI and audio hardware and software companies that I am definitely unimpressed with (no need to name names), and from whom I would just expect, and probably accept, a lack of support. I use some of their products anyhow because I already own them and I've learned to work out the glitches for myself, but my intention of purchasing future products from those companies has dropped to near zero. Until now, my experience with Cakewalk and SONAR has been just the opposite. While I understand that version 4 must be a priority and that there are industry goals and timelines and deadlines, I hope that these pressures won't make Cakewalk lose their character as good supporters of their customers. I'm really waiting for Cakewalk to show us that they are continuing their tradition of quality and support.

So far such companies have appeared to have gotten away with it. If Cakewalk follows suit and adopts such an "expedient" business model, they will have lost a large part of what made them so unique. That being said, the Cakewalk management has been quite visible and responsive in comparison to most other companies.

Sometimes you have to make at least a partial deal with the devil just to stay in business. I just hope Cakewalk can continue to walk that fine line that separates them from the competition. For example, if they decided to add C/R, a dongle, or some other intrusive type of copy protection, the last Sonar song may well be "Goodnight, Irene."

RE: Quantize MFX Broken (in response to Ron Kuper) (RTGraham)

Mon, 12 Jul 2004 09:59:04 GMT

Thanks, Ron - the info is greatly appreciated, as is your direct involvement in issues on this forum.

(I feel so special now. " />)

Seriously, I think I can safely say that it gives many of us peace of mind to know that support will continue at least one version back, and we won't be forced to shell out additional capital for bug fixes. Thanks again.

RE: Quantize MFX Broken (in response to Ron Kuper) (Master Chief [Cakewalk])

Mon, 12 Jul 2004 09:22:30 GMT

The fix for the envelope bug is coming very soon, probably this week. It'll be a patch to the VST Adapter, which is actually at fault for this bug.

Right now all of our resources are focused on SONAR 4. In fact any of the 3.1.1 bugs that are getting fixed internally are being fixed within the SONAR 4 development effort. This means that all the testing of these bug fixes is happening in the scope of SONAR 4, too. (This is true even of the VST Adapter patch, but thankfully the adapter is a separate DLL component so have an opportunity to get an update out now.)

That said, we recognize that some of you won't be interested in whatever features are coming in SONAR 4, and will just want to keep working with 3.1.1 with some bugs fixed. So after SONAR 4 is shipped, and only after these bug fixes have been tested and verified as fixed in SONAR 4, can we consider issuing another patch to 3.x.

RE: Quantize MFX Broken (in response to Ron Kuper) (RTGraham)

Mon, 12 Jul 2004 02:05:23 GMT

ORIGINAL: JamminFool

I agree. Serious regressions in the code should be fixed in a maintenance release. NOT PASSED ON TO THE NEXT PAID UPGRADE!

... ...

Paying for fixes to serious regressions is unacceptable! Such a policy is bad, and regardless of whether the competition is doing business that way, it will only lead to an undermining of the confidence which is at the heart of the relationship with the customer.

... ...

Please continue a long history of impressing me by revisiting the release schedule.

Well said. As much as I would be disappointed to be forced to pay to fix features that Cakewalk broke, I think I would also be surprised. There are a couple of other MIDI and audio hardware and software companies that I am definitely unimpressed with (no need to name names), and from whom I would just expect, and probably accept, a lack of support. I use some of their products anyhow because I already own them and I've learned to work out the glitches for myself, but my intention of purchasing future products from those companies has dropped to near zero. Until now, my experience with Cakewalk and SONAR has been just the opposite. While I understand that version 4 must be a priority and that there are industry goals and timelines and deadlines, I hope that these pressures won't make Cakewalk lose their character as good supporters of their customers. I'm really waiting for Cakewalk to show us that they are continuing their tradition of quality and support.

RE: Quantize MFX Broken (in response to Ron Kuper) (WireRage)

Sun, 11 Jul 2004 15:11:20 GMT

Bump!

RE: Quantize MFX Broken (in response to Ron Kuper) (JamminFool)

Sun, 11 Jul 2004 11:17:06 GMT

ORIGINAL: RTGraham

I would love to see this thread stay on top until we get a satisfactory resolution. Ron Kuper appears to be promising that the problem will be fixed in version 4, but that means I have to spend money to fix something somebody else broke. I cannot begin to emphasize how frustrating that is!. Fortunately Marc's MfxScript fix works for me, but I just discovered how much more time and effort it is to insert an extra plugin onto all the tracks I want to soft-quantize and set their times back by 960 clicks. Don't get me wrong, Marc - I'm very grateful to be able to handle the problem at all. But Cakewalk still isn't handling their business properly in this case. The thread about SONAR's audio engine versus Nuendo's gets 9 pages worth of hits and posts, as well as direct involvement from Cakewalk's vice president of engineering. In the meantime, this thread, which deals with an issue that actually directly affects my productivity, constantly gets knocked down the list, and the only response I ever received to my technical support email was "we have forwarded your message to our customer service department."

So Ron, I'm afraid I'm not satisfied with the suggestion to use MfxScript until version 4 comes out. I'm not someone who has to have the absolute latest version of something everytime an upgrade is available. I spend my money when I see that the purchase price of the upgrade is warranted for my needs, and that the improvement in productivity will justify the expense. In this case, the investment in version 3 REMOVED features that I use, and now you're telling me to wait until I can spend more money to fix it, and in the meantime use a solution that had to come from a third party, and which, although I am grateful for its existence, takes extra time - time that I would not have to spend on the issue if the product worked properly in the first place! " />

I think it's time for me to call Tech Support again this coming week, and send another direct tech support email. This is getting frustrating in light of the issues that get significant attention.

I agree. Serious regressions in the code should be fixed in a maintenance release. NOT PASSED ON TO THE NEXT PAID UPGRADE!

The Envelope Bug, this bug, another bug involving broken multiple control surfaces, etc....there are features broken in the current release which users have built habits around using, and then have to interrupt work flow with work-arounds...

Look, it happens. We all understand that. But it's what happens next that I am concerned with:

Paying for fixes to serious regressions is unacceptable! Such a policy is bad, and regardless of whether the competition is doing business that way, it will only lead to an undermining of the confidence which is at the heart of the relationship with the customer.

Come on, Cakewalk! Some regressions are unavoidable. But others are just egg on the face, and how you handle these define the company.

Please continue a long history of impressing me by revisiting the release schedule.

RE: Quantize MFX Broken (in response to Ron Kuper) (ebinary)

Sun, 11 Jul 2004 10:11:04 GMT

I agree. Between 2.2 and 3, I had a dozen projects including my primary template that simply didn't play half the notes unless the MIDI prepare buffer was at maximum. It essentially made me give up on a lot of 3rd party tools I had purchased for 2.2, through no fault of those tool makers.

Sequencers have handled MIDI properly for 20 years, and its pretty poor when a top-of-the-line package can't handle quantization properly. C'mon, we're talking quantization for gods sake - its the feature launched 1000 80s synth pop bands. Where would synth music be if HoJo, T. Dolby or Tears For Fears had dropouts at random intervals?

Eric

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (jlgrimes)

Sun, 11 Jul 2004 09:19:41 GMT

As others have already noted, this is a known issue in SONAR 3.1.1. Specifically it effects only soft synths, hardware MIDI is immune.

I did have a problem with my yamaha motif rack never able to start on time with the Quantize mfx. I was using usb instead of midi though.

RE: Quantize MFX Broken (in response to Ron Kuper) (WireRage)

Sun, 11 Jul 2004 03:09:14 GMT

I'm going to have to agree here and hope Cakewalk changes their decision. I don't think CW should delay Sonar 4 however they should provide a patch for the known issues with Sonar 3.1.1 after the release of Sonar 4.

I would purchase a upgrade because it might offer a new products, conveniences, or services for my trade that I can afford. On the same hand I rather switch software companies if I was forced to purchase a new upgrade just to fix a bug from a previous software version. The only reason not to offer a patch for 3.1.1 after the release of Sonar 4 is because you want want more money from us or you don't care what happens.

I hope enough people become aware of this situation and perhaps maybe CW will comply to offering a update patch for 3.1.1 users after the release of Sonar 4.

RE: Quantize MFX Broken (in response to Ron Kuper) (RTGraham)

Sun, 11 Jul 2004 02:28:47 GMT

I would love to see this thread stay on top until we get a satisfactory resolution. Ron Kuper appears to be promising that the problem will be fixed in version 4, but that means I have to spend money to fix something somebody else broke. I cannot begin to emphasize how frustrating that is!. Fortunately Marc's MfxScript fix works for me, but I just discovered how much more time and effort it is to insert an extra plugin onto all the tracks I want to soft-quantize and set their times back by 960 clicks. Don't get me wrong, Marc - I'm very grateful to be able to handle the problem at all. But Cakewalk still isn't handling their business properly in this case. The thread about SONAR's audio engine versus Nuendo's gets 9 pages worth of hits and posts, as well as direct involvement from Cakewalk's vice president of engineering. In the meantime, this thread, which deals with an issue that actually directly affects my productivity, constantly gets knocked down the list, and the only response I ever received to my technical support email was "we have forwarded your message to our customer service department."

So Ron, I'm afraid I'm not satisfied with the suggestion to use MfxScript until version 4 comes out. I'm not someone who has to have the absolute latest version of something everytime an upgrade is available. I spend my money when I see that the purchase price of the upgrade is warranted for my needs, and that the improvement in productivity will justify the expense. In this case, the investment in version 3 REMOVED features that I use, and now you're telling me to wait until I can spend more money to fix it, and in the meantime use a solution that had to come from a third party, and which, although I am grateful for its existence, takes extra time - time that I would not have to spend on the issue if the product worked properly in the first place! " />

I think it's time for me to call Tech Support again this coming week, and send another direct tech support email. This is getting frustrating in light of the issues that get significant attention.

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (mbncp)

Wed, 07 Jul 2004 18:11:21 GMT

Wrong answer.

Well they are two issues.

1) Mfx plugs that create Live events (real-time input) with future timestamps (arpeggiators, echo plug..).
When used with a VSTi, the events get fired at the same time (like setting the echo delay to 0 msec)
And it's ok with midiout or dxi synth
Only workaround here is to use a virtual midi driver.

2) Mfx plugs that move Track events timestamps in the 'past' or in the 'future' (Quantize plugs).
If these events are outside of the current processing buffers they will be lost.
MfxScript can buffer future events, but not early ones, so the trick is to move the events back (using the time field of the track settings), and push them back at the correct position n the script.

To avoid the the 'Time' trick when using the quantize script we could keep the events within the start of the buffer. That means that some of the events (some of the ones you don't hear) would be less quantized or not at all, but a least you would hear them.
If someone can understand what I try to say and is interested in such a plug(script), just let me know.

And be sure that when S4 is coming out and these two bugs are not fixed, it is not â€˜yodelâ€™ that you will hear in the Swiss alps " />

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (mbncp)

Wed, 07 Jul 2004 17:15:49 GMT

Hi Russell,
Glad it works for you.

If you are doing some simple quantizing you may check this script.
It's very basic quantizing with an option for random offset (after quantizing).
Note that it would be very easy to add some extra parameters, so let me know if you need something special, even something that's not on the default quantize plug.

Currently I should be working on the GUI part of MfxScript, so the plugs would have controls to enter the parameters, but instead of working on this, I'm just playing around with an 'arpeggiator-live midi groove sampler' that I created using mfxscript.
In the meantime, you can just save the script with different settings under different names in a given folder, so they will show in the preset page of mfxscript, and you are then just a double-click away.

Note that a right-click on a 'folder' in the preset tree control will open this folder using window explorer.

Now the link:
http://mypage.bluewin.ch/ncplus/download/Quantizing.txt

PS: Off course, if you use this script don't use the previous one and don't use the default Quantize plug. this is an ALL-IN-ONE " />

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (jeffn1)

Wed, 07 Jul 2004 16:03:02 GMT

quote:

This post should stay on top until someone from Cakewalk responds.As others have already noted, this is a known issue in SONAR 3.1.1. Specifically it effects only soft synths, hardware MIDI is immune. The general statement of the problem is if an MFX processor is present which produces MIDI event times that are in the future, then these events will get lost.

If the MFX doesn't move events into the future, or if the MFX is feeding hardware MIDI, then the problem won't manifest itself.

This will be fixed in SONAR 4. In the meantime we suggest we use Marc's MfxScript workaround.

Wrong answer.

JeffN

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (Master Chief [Cakewalk])

Wed, 07 Jul 2004 14:32:24 GMT

This post should stay on top until someone from Cakewalk responds.

As others have already noted, this is a known issue in SONAR 3.1.1. Specifically it effects only soft synths, hardware MIDI is immune. The general statement of the problem is if an MFX processor is present which produces MIDI event times that are in the future, then these events will get lost.

If the MFX doesn't move events into the future, or if the MFX is feeding hardware MIDI, then the problem won't manifest itself.

This will be fixed in SONAR 4. In the meantime we suggest we use Marc's MfxScript workaround.

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (jeffn1)

Wed, 07 Jul 2004 14:03:00 GMT

It seems clear to me that Cakewalk has an obligation to provide its Sonar 3.xx customers with a free update to fix this bug and the envelope bug. I just bought Sonar 3 thinking it was solid. This post should stay on top until someone from Cakewalk responds.

I think Cakewalk has a pretty good reputation among its user base. I hope it does not behave in a short sighted fashion here.

JeffN

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (RTGraham)

Wed, 07 Jul 2004 12:50:39 GMT

Alright - time to bring this thread back up. " />

Marc - if you're still out there watching the forum (and this thread), thank you very much for your posts regarding MfxScript. I did finally get a chance to try the quantize fix, and I no longer have missing notes. Of course, if I have an event right at the very beginning of the track it gets lost, but I almost always have a click-in at the top of a song anyhow. I really appreciate the work that must have gone into MfxScript and also into investigating the cause of the quantization plugin problem.

Again, this raises the issue of why it isn't important enough to Cakewalk to fix a problem like this themselves. I'm still not satisfied with waiting until version 4 to see them fix the MIDI implementation that they broke. I repeat again, the quantize plugin used to work. Other MIDI implementation issues used to work (there have been numerous threads on a handful of issues). They have only been "broken" since the latest updates. And again, I have a real problem shelling out money for the next version when I have already lost confidence in the company's support for their product. I'm going to call customer service and complain again, and I'm going to send another email to technical support later this week.

Again, many thanks to Marc for addressing the issue that Cakewalk should have addressed themselves.

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (LionSound)

Mon, 31 May 2004 06:32:36 GMT

Its good to see diehard Cakewalk users stay loyal, but I for one am on the fence. The reason I use Sonar over Pro Tools, Cubase, etc. is the way it handles MIDI. Its simple, elegent, yet powerful. For me, using MFX is an important pat of every project. I dunno guys, but if it aint fixed in version 4 ... well, I'll have to regretfully go in another direction.
Oh, and have you guys seen that Guitar Tracks Pro 3 has a built in metronome? It makes me wonder why Sonar 3 does not ... S

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (rjt)

Fri, 28 May 2004 19:11:35 GMT

I also will not switch from Sonar in the forseeable future... like probably years. But regarding the short/long term bugginess.... I continue to find it odd that Sonar's "improvements" not only effect other developers, but also cause their own plug ins not to work properly. I'm sorry, but I can't see how that is a thoughtful improvment. Maybe I'm missing something. It certainly isn't the first time I don't get the big picture.

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (RTGraham)

Fri, 28 May 2004 18:13:49 GMT

ORIGINAL: GC San Diego Seth

RT, your explanation certainly makes sense. It is unfortunate that there is no true fix for the problm right now. Seems like it could be taken care of so easily. Do you have any desire to switch to another sequencer?

It looks like Marc's MfxScript plugin might fix the quantize issue. I haven't had a chance yet to try it, but I've read his explanations a couple of times to make sure I understand the concept, and it makes sense.

Despite the issues with MFX (and if Marc is correct about where the problem lies, with MIDI implementation in general), I have no plans to switch from SONAR to another platform. I'm quite happy with the program in general. I've used Pro Tools quite a lot when I have to transfer my material to other studios, and I've used Cubase and Logic on a limited basis. They all have their strong points, but I've been a Cakewalk user since version 2 or 3, and I'm very accustomed to the workflow.

At the same time, I won't be shelling out money for version 4 until I see stability and support for existing versions improve. This quantize situation reminds me of an ordeal I went through with Finale several years ago (back in version 3.5 or 3.7). The quantize algorithm for their automatic transcription feature went haywire on me, creating all sorts of gibberish notes, dropping notes from the staff, etc. Despite numerous calls to tech support, and despite the fact that they could recreate my problem immediately, and despite numerous assurances that it was being fixed, it took THREE more versions before HyperScribe's quantize algorithm was actually usable. Three versions of the same bug. I think it's part of the reason that I now refuse to purchase every upgrade Finale comes out with - I've been happily using Finale 2002 for professional products even though 2003 and 2004 have been released, and I definitely won't upgrade until 2005 or 2006. Finale has grown into a great, stable program, but for me the limited improvements don't justify the annual expense.

I'm hoping I don't have to fall into the same pattern with SONAR. I think unlimited, name-able groups with a group view where you could manage group attributes for tracks, controls, etc. might be the killer feature for me.

RE: <span class="high">Quantize</span> MFX Broken - Cakewalk Please Fix !!! (Bill OConnell)

Thu, 27 May 2004 20:39:13 GMT

ORIGINAL: axe

Bottom line, bug fixes need to continue one release back. So, Sonar 3 gets fixes till Sonar 5 is out. That provides a much more workable solution to those that use this software to make a living. Given the loyalty that I see from Cakewalk users they are going to pony up their money for the next release regardless. This just provides much more peace of mind to a working person.

Good Luck!

AXE

Your whole post was very well put, axe.

While I have been supportive until now about Cakewalk's decision about no more planned updates for S3, I am now becoming quite worried that they are becoming sucked into the buggy whirlwind of yearly production cycles. (Although this may be viewed as a special case, because surround didn't make it into this version for those who need it--and for that "pro" aura.)

I don't want to stop the parade of progress. But I am going to stick with the DAW I have for least a couple of years. Having been in marketing for most of my life, I understand the bottom line realities. But this sloppy pattern of two steps forward and three steps back that some other companies perpetuate--well I just hope Cakewalk doesn't feel compelled to fall into that endless cycle of never-realized potential.

Before someone asks me the question, I have no big issues with Sonar 3.1.1. It's a fine program. In the spirit of axe's post, I would feel a lot better, though, if Sonar 3 had a couple more maintenance upgrades on the back burner. A few bugs here and there--why not fix them? For many people 3.1.1 is rock solid. For a not insignificant minority, problems have been reported. Maybe Cake should take another look.

I just see a fall season with Cakewalk and Steinberg racing each other down to the wire with their new versions. The design meetings for the new logos, glossy brochures and ads are probably already in full swing.

May the less buggy program win.

RE: <span class="high">Quantize</span> MFX Broken - Cakewalk Please Fix !!! (axe)

Thu, 27 May 2004 14:04:34 GMT

ORIGINAL: ba_midi

RT and rjt,

I just want to point out that sometimes Sonar actually makes "improvements" to their code which then causes problems in other plugins which are not updated.

ORIGINAL: RTGraham

This is so funny I work in the software industry and this is a universal problem. Who gets priority? Marketing with the new features or the installed base that needs stability? Note: marketing will always win as the company always has the money from the installed base - sad but true.

To adequately solve this you need to split the product into two lines one with a short life cycle that continues to add in new features and capabilities and you of course get the risk of being Production beta testers :-) The other long lifecycle puts in only bug fixes with the goal of stability.

Bottom line, bug fixes need to continue one release back. So, Sonar 3 gets fixes till Sonar 5 is out. That provides a much more workable solution to those that use this software to make a living. Given the loyalty that I see from Cakewalk users they are going to pony up their money for the next release regardless. This just provides much more peace of mind to a working person.

Good Luck!

AXE

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (mbncp)

Thu, 27 May 2004 13:26:26 GMT

1) RT, you are right about the IgnoreMidiInTimeStamps, this has nothing to do with the quantizing plug(s) bug.

2) The bug isn't currently in the mfx plugs.
The host is calling an mfx plug via OnEvents(timeFrom, timeThru) with buffers of events that have a timestamp between timeFrom and timeThru.
Note that timeThru-timeFrom is equal to the 'prepare using ...' setting.
Now it is logical for a plug that deals with timing to sometimes 'move these events either in the past or in the future. Unfortunately, sonar 3.1.1 will discard/ignore events that are outside this window, when sending events to a dxi/vsti.

As timeFrom is always delayed according to real time, it should be possible to move events back (normally about 1 measure).
For events past timeThru, it would be better for the plug to buffer them internally (this is what mfxscript is doing), but the host should keep these events anyway.

3) The bakers are aware of the 'bug' and we can expect a fix in future version.
For now, the only workaround is to either:

a) Apply midi effect, and even in this case, make sure the clip size is big enough to handle eventual extra timing.

b) As I mentioned earlier, change the track time field to -960 and add the mfxscrip with the correct script after the quantizing plug (see my first post in this thread - mbncp).
Everything should work as expected.

c) I havenâ€™t try this, but another workaround would be to set ouput to a virtual midi device and get the events back on another track. (I try to avoid virtual midi drivers, but well, thatâ€™s me..)

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (LionSound)

Thu, 27 May 2004 01:46:20 GMT

RT, your explanation certainly makes sense. It is unfortunate that there is no true fix for the problm right now. Seems like it could be taken care of so easily. Do you have any desire to switch to another sequencer?

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (rjt)

Thu, 27 May 2004 00:49:42 GMT

While I would love to see Cake fix their own plug ins, there is still the question of other companies who offer MFX plug ins and don't seem to be able to get them to work in Sonar. It would be nice if Cake would help them get up and going again also.

RE: Quantize MFX Broken - Cakewalk Please Fix !!! (RTGraham)

Thu, 27 May 2004 00:39:50 GMT

I'm posting this information off the top of my head, without double checking it, so it may not be 100% accurate.
But...
If I remember correctly, the IgnoreMidiInTimeStamps parameter has to do with the way hardware MIDI interfaces, especially USB interfaces, handle MIDI timing. Back before there was such a thing as USB, MIDI interfaces connected to computers primarily through internal cards and through external serial cables. Serial ports (like COM ports) are synchronous devices, and the MIDI protocol, which is itself serial in nature, was happy as a clam.

But along came USB, an asynchronous protocol carrying data in packets where information could potentially get "out of order" (as opposed to the serial COM ports, where only one piece of information can travel at once and it's a nice neat single-file line). To get around this problem, various MIDI interface manufacturers devised systems of time-stamping the MIDI data, to be reinterpreted and re-ordered at the driver end. Some manufacturers have even advertised how accurate their time-stamping is when used with their own proprietary sequencing software (like MOTU interfaces with Digital Performer on a Mac).

That being said, I believe the IgnoreMidiInTimeStamps parameter applies specifically to this kind of USB hardware time-stamping, and as such has nothing to do with software synths. The MFX problems that I have encountered relate only to plugin synths, and I think this is true for many of the people who have posted messages about this problem. So the response you got from tech support sounds somewhat uninformed and generic. I'll certainly give it a try myself when I get a chance, but I don't have much hope of it solving the problem for me.

Hope that was more informative than it was confusing. " />