Yeah I already had increased it to 500 because of problems using R-Mix, so it wasn't that unfortunately. 

It might be worth trying values up to 1000 if you haven't already. Some systems/projects need higher values.


Also, I suggest splitting Simple Instrument tracks to separate MIDI and Synth tracks, which might help you troubleshoot the problem further, and could conceivably resolve it, as there have been many undesirable behaviors associated specifically with Simple Instrument tracks in the past.

brundlefly

fwiw, imo the correct answer here is in Jonesey's post above... it is simply good practice to start any midi based song at measure 2.. there is simply no way you can ever guarantee correct operation of a midi song by doing otherwise... regards.

I have to disagree with that. The vast majority of projects on the vast majority of systems should play back correctly from time zero.  In my experience, specific problems with this can (and should) be resolved with system or project tweaks, rather than making it SOP to start all projects later in the timeline. If there is a widespread issue with this, sample projects should be sent to Cakewalk for them to troubleshoot and resolve with code changes if necessary.

of course its ok to disagree.. it doesnt bother me..lol.. however fwiw my post did say *guarantee* and there is zero chance whatsoever of a set of hardware synths sync'ing to clock and having channel, patch and control data being setup while simultaneously playing a set of midi notes... :) .. and that is the reason why it has been a convention to start midi songs at measure 2

there is zero chance whatsoever of a set of hardware synths sync'ing to clock and having channel, patch and control data being setup while simultaneously playing a set of midi notes... :) .. and that is the reason why it has been a convention to start midi songs at measure 2

I was going to mention that the one area in which this is a persistent problem is with hardware synths. But there are fewer and fewer of us still using them, and this issue in particular does not seem to involve them.


My solution to hardware synth issues is to get them set up in advance and disable the widgets that send patch changes and other messages that can cause delayed - usually not completely dropped - notes. And then I get the hardware synth part rendered to audio as early as possible so it's not an ongoing problem.

Standard practice my ass. Never in 8 years have I inconvenience myself with starting at anything other than 0, but if I had had to I would have put in a feature request for negative time. As Brundle says there are simple system tweaks to avoid the workaround (which would be further compounded when bringing in external sequencers; like maschine).

Lets move from member opinion to straight FACT.

Access Virus setup guide page 17 "Inserting one or two empty bars at the beginning of the song helps the Virus TI settle into the tempo"

It takes no time at all to validate the reasoning for this statement by Access GmbH... start at 1:01:000 and you get dropped notes and hanging arpeggiator.. go further.. record and freeze the synth.. audio is bounced and oops.. first measure is all corrupted...

So, there is no "system tweak" that fixes this issue.. its real, well known and well documented in this forum several times as Jonesey indicated... a simple search is suggested to any casual reader of this thread.

A famous Abraham Lincoln quote seems appropriate in this instance ;)

So its standard practice for everyone...who has a virus, which is not exactly a staple in every users setup. Have you used Pro Tools at all with the virus? Does using negative time eliminate the issue? Anyway, OP mentions using softsynths only so his problem has nothing to do with page 17. I have had a similar issue in the past on a new build and made some preference adjustments and have never had the problem again. Like I said before, making an adjustment such as starting at bar 2 can be a huge inconvenience. Working with Maschine, client video projects, return to zero becoming defunct are a few immediate examples that come to mind.................................. Your Abe quote is not appropriate. Discussing this issue may reveal something that Cake could provide as a solution to everyone. If you are not familiar with negative bars: http://www.youtube.com/watch?v=HkLzZ5W5Z-Y Implementing it as nonrecordable, buffering space could be a useful option for some.

Sigh.. The Virus was nothing more than an example. This can happen on any of my current synths...

Look, this has been a well known and well documented issue with sequencers and midi devices for 20 years...namely you cannot send significant control, setup and timing information while simultaneously expecting notes to sound from a hardware synth...

The fact that you are unaware of this issue and I am does not make you right and me wrong, nor does it make the issue disappear, nor does it invalidate my statement and nor does it give just cause for you to throw redicule at my statement with references to your rear end... it is standard practice ..to anyone who knows about it

My view here is neither rogue nor unique... it is in alignment with a sizeable number of members with long experience in midi or hardware synths.. any simple search of the forum will validate this...or post a thread with a question on the topic... I am not the one who needs any sort of convincing :)

fyi, yes indeed, along with many others i have made a request for a custom offset to the display ruler... though it is far more important to video folks than midi.. at least with midi its simple math not seconds or parts thereof..tho still tiresome at times.

p.s. I have no issues in integrating Maschine with a music start at (say) measure 2, i simply have a scene with a blank pattern run at song start of 1:01:000 and use PC msgs to change to an active scene/pattern upon music start...be that at measure 2 or elsewhere... if you are not familiar with this mode i will be happy to help, but i am done with this thread.

peace out.

Its not just hardware synths: fx processors, lighting equipment, video equipment, etc. Anything that is triggered by timecode or needs to be synchronized need a bit of preroll to get them up to speed. Also, it is easier to add stuff to the beginning of a project if you start with an offset. Especially with large projects. Yes you can select all and move, but it is all too easy to mess something up that way. And what if the artist decides that he/she wants a pick up measure RIGHT NOW.. and cannot wait for you twiddle with the project to make space. :)

I HAVE THIS PROBLEM! Sorry to shout, but it's a doozy. It CAN'T be me. I started another thread on this a followed all the steps people asked, NOPE.!!!!

This happens to me in X1, has since I got it. No response from Cakewalk at all on this. In fact, the Matrix is unusable for me if I use midi patches because it won't play the 1st note of ANY midi patch. Same problem. Adjusted buffers, even tried outputting to a hardware synth, and in every event, the 1st note send to a soft or hard synth simply isn't played. In my case I know it's not a "did I play it before 0:00" problem because I do my midi work the hard way, staff drags. I generally do the start at measure 2 and slip a note early in the 1st.