Re: Slow performance of adding MIDI Events to MusicTrack?
Re: Slow performance of adding MIDI Events to MusicTrack?
- Subject: Re: Slow performance of adding MIDI Events to MusicTrack?
- From: NickK <email@hidden>
- Date: Tue, 8 Dec 2009 15:40:24 +0000
Ok, I've submitted it as a performance bug to Apple. It's a quick win fix to be honest with a large effect on their MIDI users.
I should try a test using MIDIEndPoint attached to the MusicTrack to add the note events instead..
Nick
On 8 Dec 2009, at 14:59, Simone Tellini wrote:
> NickK ha scritto:
>> I've sampled the application running and it spends 100% of it's time within std::vector operations - iterator and copy. So I'm assuming it adds the event by iterating through the entire current set until it finds the correct timestamp location and then makes a gap my copying the data before inserting it.
>>
>> It seems a little barking mad for Apple to use a linear search routine and I would suspect a hashed based dense key storage system would have been better? This would slow down with more additions!
>>
>> Is this a known issue that others have experienced?
>>
> yes, I've noticed the same thing.
>
> Luckily, I've never had to add that many events/notes, so I could bear to wait for some seconds.
>
> --
> Simone Tellini
> http://www.tellini.org
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden