Re: [Banshee-List] Extension delay with next track

[Gabriel Burt <gabriel burt gmail com>]

That might prevent your thread from getting blocked, but it shouldn't
speed up the actual Next() call.  The long Next () call has been
discussed (and likely solved) recently on bugzilla.  See:

https://bugzilla.gnome.org/show_bug.cgi?id=581103

Gabriel

On Wed, Dec 2, 2009 at 10:55 AM, Martin Eve <martin martineve com> wrote:
>
> I think I found the answer actually.
>
> This is running inside a different thread and, with the following code, the
> track change happens instantly:
>
> ThreadAssist.ProxyToMain (delegate {
>                                                        ServiceManager.PlaybackController.Next();
>                                                });
>
> Martin
>
>
> gabaug wrote:
>>
>> How many tracks are in your library?  And how many smart playlists do
>> you have?  The delay may be due to reloading smart playlists (since
>> the play count has changed, the contents of the Unheard playlist for
>> example might have changed).  But I wouldn't expect that kind of delay
>> without quite a large library.
>>
>> Gabriel
>>
>> On Wed, Dec 2, 2009 at 7:39 AM, Martin Eve <martin martineve com> wrote:
>>>
>>> Hi,
>>>
>>> I'm working on an extension and am encountering a strange problem
>>> relating
>>> to track skipping.
>>>
>>> In my extension I have the following code:
>>>
>>> Log.Information(command);
>>>                                        switch(command)
>>>                                        {
>>>                                        case "playPause":
>>>
>>>  ServiceManager.PlayerEngine.TogglePlaying();
>>>                                                break;
>>>                                        case "next":
>>>
>>>  Log.Information("Doing...");
>>>
>>>  ServiceManager.PlaybackController.Next();
>>>                                                Log.Information("it.");
>>>                                                break;
>>> }
>>>
>>> This produces the following output:
>>>
>>> [Info  15:33:58.182] next
>>> [Info  15:33:58.182] Doing...
>>> [Info  15:34:02.510] it.
>>>
>>> However, as can be seen from the time stamp, over 4 seconds elapsed
>>> between
>>> the request to move to the next track and the action being taken. Am I
>>> doing
>>> something wrong? This seems to sometimes take up to 7 seconds, which
>>> makes
>>> the extension extremely sluggish and unresponsive.
>>>
>>> Thanks,
>>>
>>> Martin
>>> --
>>> View this message in context:
>>> http://old.nabble.com/Extension-delay-with-next-track-tp26610966p26610966.html
>>> Sent from the Banshee mailing list archive at Nabble.com.
>>>
>>> _______________________________________________
>>> banshee-list mailing list
>>> banshee-list gnome org
>>> http://mail.gnome.org/mailman/listinfo/banshee-list
>>>
>> _______________________________________________
>> banshee-list mailing list
>> banshee-list gnome org
>> http://mail.gnome.org/mailman/listinfo/banshee-list
>>
>>
>
> --
> View this message in context: http://old.nabble.com/Extension-delay-with-next-track-tp26610966p26614299.html
> Sent from the Banshee mailing list archive at Nabble.com.
>
> _______________________________________________
> banshee-list mailing list
> banshee-list gnome org
> http://mail.gnome.org/mailman/listinfo/banshee-list
>