Arpeggios - why don't they playback from 1st beat of 1st bar ?!

Have you tried to move the start point in BAR 3.1.1.1 or 5.1.1.1

this is a known rule for all daws: never start a song at Bar 1.1.1.1

Try to drag the objects forward...
let me know...

Logic requir to load buffer size... so you cant start at 1.1.1.1 without losing somthing...

Always start to play before the regions starting point...

Cheers

G

Florence wrote:
thx for replying.....

if i shift the regions to bar 2 and then start playback about half a bar before the start then it plays fine - but this is SO lame!! Is there not an option anywhere to deal with this - maybe something that makes the playback head start just before 1.1.1.1 ?

in the pro studios 1.1.1.1 is never used..
Professionals requires a lot of SMPTE sync... for movies or for make MTV Music video of your song... or for Jingles...
h

have never see the number 5.... 4.... 3.... 2.... 1.... before starting a jingle???

usually the correct workflow is to start at 5.1.1.1... or later...

do you know somthing about SMPTE sincronization?

It's too annoying having to manually place the cursor at a point where it will actually play the arpeggio back! (also in cycle mode this is impossible - so even more hassle!)

I'm sorry but i think that it is not so annoyning...

in any case you can use Garage Band or other not Professional software.

hope this helps.

G

Agreed, I never start on the first bar either.

I know it technically makes more sense if you're producing or building loops out, but just create a template with loop enabled and your start point on either bar 2 or 4 depending on what you want.

It's really not that big of a hassle.

You might check to see that the note is actually beginning right on 1.1.1.1 If you anticipated, it might be starting at 0.4.239 or something, in which case it won't trigger..

Most of the time, I start my songs on 1.1.1.1 but if you're doing stuff that's going to another studio, or outside project, I'd make a couple of bars of silence.. You can always highlight all tracks and move them to bar 5 etc. .at any time.

Are you talking about Logic arpeggiator?

which is the Virtual instrument that we are talking about?

Sotty is NI plugin
have you tried to ask to Native instrument support?

Maybe the problem is not related with Logic!

G

Florence you have an attitude problem.

Switch DAW's for all we care, this is my last time trying to help you.

angelonyc wrote:
You might check to see that the note is actually beginning right on 1.1.1.1 If you anticipated, it might be starting at 0.4.239 or something, in which case it won't trigger..

It definitely sounds like the MIDI information isn't quantized exactly at the beginning of the bar and this is causing the problem as angelonyc has mentioned above. Could you upload a screenshot to look at? This may help more.

When you record enable the software instrument track and hold down any MIDI key on your keyboard does the synth patch work? If yes then it really does sound like the note is not exactly on the bar. Give this a bash and let us know how you get on.

fermusic wrote:
Have you tried to move the start point in BAR 3.1.1.1 or 5.1.1.1

this is a known rule for all daws: never start a song at Bar 1.1.1.1

This is NOT a known rule for all DAWS but it is a general rule for Logic.

Because of it's buffering scheme Logic often fails to pick up first notes.
On this board alone there's dozens of threads relating to the missing first note syndrome.
This first appeared in version 4.xx and was not present before.

Some DAWS even have a setting of how much look ahead data you wish to buffer so no matter where you stop, the next bit of data is picked up and buffered.

pancenter-

p.s. interesting side note... Garage Band which is based on Logic does not have this problem, the internal rewrites of the basic Logic MIDI/Audio engine have yet to make it into Logic, but I'm sure they will.