for Cakewalk Sonar users and Pulsar 2

claudioD · Post by **claudioD** » Thu Nov 18, 2004 3:42 am

I would like to know if you have my same problems with MiDi recording .

often when I send a Midi signal to Sonar (for example from an Alesis DM5 drum machine) it crashes . Not immediately , sometimes I can wait some minutes, but in the end it crashes . I guess it could be a problem with Pulsar Midi in because I asked it in Sonar Forum and the other (Non Pulsar) users haven't this problem

thanks,
regards

Post by **garyb** » Thu Nov 18, 2004 4:10 am

do you have a loop with more than one device transmitting midi clock? midi and sonar3 work here...

claudioD · Post by **claudioD** » Thu Nov 18, 2004 5:08 am

On 2004-11-18 04:10, garyb wrote:
do you have a loop with more than one device transmitting midi clock? midi and sonar3 work here...

No I haven't . The only device that trasmit clock is my A16 ultra. I forgot to say that Sonar crashes only when I enable a track for recording and I record the incoming midi signal

at0m · Post by **at0m** » Thu Nov 18, 2004 5:28 am

The clock Garyb refers to is MIDI clock, A16 transmit word(audio) clock.

What track do you enable for recording, MIDI right?
To enable a MIDI track can cause a feedback loop, which may not be audible if it is a MIDI clock or so. MIDI clock or Active Sensing are streaming data, unlike note on/off or CC# which are more momentary. This streaming stuff should be avoided when possible. So if a hardware synth is transmitting MIDI Clock or Active Sensing, try switching that off.

Also, check if there is no loop made when you activate recording. I suspect activating recording enables MIDI Thru causing a loop. Check your IO in SFP, maybe you can solve the problem by adjusting your MIDI routing slightly.

claudioD · Post by **claudioD** » Thu Nov 18, 2004 7:55 am

On 2004-11-18 05:28, at0m|c wrote:
The clock Garyb refers to is MIDI clock, A16 transmit word(audio) clock.

What track do you enable for recording, MIDI right?
To enable a MIDI track can cause a feedback loop, which may not be audible if it is a MIDI clock or so. MIDI clock or Active Sensing are streaming data, unlike note on/off or CC# which are more momentary. This streaming stuff should be avoided when possible. So if a hardware synth is transmitting MIDI Clock or Active Sensing, try switching that off.

Also, check if there is no loop made when you activate recording. I suspect activating recording enables MIDI Thru causing a loop. Check your IO in SFP, maybe you can solve the problem by adjusting your MIDI routing slightly.

Yes I enable a midi track for recording. Echo is off, I don't have a device that transmit a midi clock .How can avoid this midi loop? I use an Alesis DM5 Midi out connected with Pulsar midi in . Then I record the Midi signals sent by the Alesis . What I do is to convert audio signals to midi signals through Alesis drum trigger . I connect the Midi out device of Pulsar to the Midi in device of the sequencer (Sonar) . That's what I do.

[ This Message was edited by: claudioD on 2004-11-18 07:58 ]

bosone · Post by **bosone** » Thu Nov 18, 2004 11:29 am

i once had a dm5 (always been a pulsar user) and never experienced crash with sonar 2.2 XL.
try to disconnect the midi IN of DM5, and to disable midi clock from dm5

claudioD · Post by **claudioD** » Thu Nov 18, 2004 1:04 pm

On 2004-11-18 11:29, bosone wrote:
i once had a dm5 (always been a pulsar user) and never experienced crash with sonar 2.2 XL.
try to disconnect the midi IN of DM5, and to disable midi clock from dm5

thanks for the tip ,

midi in is disconnected , but how can I disable the midi clock in DM5?

I use asio drivers

EDIT : ah ma sei italiano ! Diciamo che non sono espertissimo ad usare la DM5, la uso solo per triggherare e poi per trasformare in MIDI il segnale. Com'è che si fa a disabilitare sto midi clock? Grazie , ciao!

[ This Message was edited by: claudioD on 2004-11-18 13:08 ]

bosone · Post by **bosone** » Fri Nov 19, 2004 3:00 am

di preciso non ricordo...
comunque puoi sempre provare a caricare il midi-filter in pulsar (tra i midi device) e togliere tutti i messaggi midi che non ti servono.
ma comunque il problema potrebbe essere da un altra parte.....

claudioD · Post by **claudioD** » Sat Nov 20, 2004 8:43 am

other suggestions?

Post by **garyb** » Sat Nov 20, 2004 1:43 pm

there's no reason why this shouldn't work. midi clock transmitted in this way should be fine. i doubt that active sensing is transmitted by the alesis, but you can check the midi menu and turn it off if it is. what happens with another midi interface?

turn off clock transmission on the alesis since the alesis is not the master sequencer.

[ This Message was edited by: garyb on 2004-11-20 13:46 ]

claudioD · Post by **claudioD** » Sun Nov 21, 2004 8:59 am

On 2004-11-20 13:43, garyb wrote:
there's no reason why this shouldn't work. midi clock transmitted in this way should be fine. i doubt that active sensing is transmitted by the alesis, but you can check the midi menu and turn it off if it is. what happens with another midi interface?

turn off clock transmission on the alesis since the alesis is not the master sequencer.

[ This Message was edited by: garyb on 2004-11-20 13:46 ]

I'll try to use the Midi filter to stop unwanted signal. I don't know how to turn off the clock from Alesis.
thanks all

claudioD · Post by **claudioD** » Wed Dec 01, 2004 12:20 pm

the Midi filter seems to work! Finally !
Thanks