cpu overload when using midi sync

Learn about building and using Max for Live devices.
Post Reply
charlybeck
Posts: 114
Joined: Sat Sep 18, 2010 1:42 pm

cpu overload when using midi sync

Post by charlybeck » Sat Aug 03, 2013 10:53 pm

Hi there,

i wanted to make a live set with my device tonight so i synced traktor with live over midi sync.

But when i did this i got an heavy cpu overload. It's occuring only if i enable my device and midi sync.

I used a standard transport-patcher somewhere from the live libraries connected to this step sequencer object from live, took the current_step_index value and triggered some envelopes with it,
nothing special. There is no other midi processing in the device, its an audio plugin.

Anybody observed this behaviour too?

greetz,
charly


ps:
thanks so much for your help. hope some day i can help back.

charlybeck
Posts: 114
Joined: Sat Sep 18, 2010 1:42 pm

Re: cpu overload when using midi sync

Post by charlybeck » Sat Aug 03, 2013 10:58 pm

it's only occuring when the device runs natively. as soon as i open the max editor everything works fine..... this looks like a support issue to me...

charlybeck
Posts: 114
Joined: Sat Sep 18, 2010 1:42 pm

Re: cpu overload when using midi sync

Post by charlybeck » Sun Aug 04, 2013 1:22 am

ok fixed it.... i used a function, a line~ and a snapshot object to create a ramp.
i used no relative time values but never the less it was affected by midi sync.
don't know why.
however, there is a much better way to create the ramp using only a line object - now it works.

thanx for my help. ;-)

Post Reply