QS v1 triggers not working with iTunes anymore, need help

[Will Fiveash]

I'm now finding with QS v1 on my MacBook Pro running 10.7.5 that the triggers I use to control iTunes have stopped working.  I can't say for sure that QS has a bug but something has definitely changed as I've used these triggers for a long time.  For example I've used shift+command+spacebar to pause/play the current track in iTunes for several years.  Now it has no effect.  This is true for all my defined iTunes triggers which all start with shift+command.  I've looked at the Console log viewer but haven't seen anything that looks like a debug message relating to this.  Anyone have an idea as to what is up?

[Rob McBroom]

On Mar 31, 2013, at 8:23 PM, Will Fiveash <will.f...@gmail.com> wrote:

I'm now finding with QS v1 on my MacBook Pro running 10.7.5 that the triggers I use to control iTunes have stopped working.  I can't say for sure that QS has a bug but something has definitely changed as I've used these triggers for a long time.  For example I've used shift+command+spacebar to pause/play the current track in iTunes for several years.  Now it has no effect.  This is true for all my defined iTunes triggers which all start with shift+command.

I haven’t used them in years, since there are dedicated keys on “newer” keyboards, but I still have those triggers set up. In fact, I have ⇧⌘Space set to Play/Pause too. And of course, it’s working for me. :-)

What if you select iTunes in the first pane, then select the “Play - Pause” action? Or, if you have the iTunes Controls catalog entry enabled, you could select “Play/Pause” directly in the first pane and try running that. These should be alternate ways of running more or less the same code that the trigger calls.

Maybe also try (temporarily) enabling “Show Window” for one of the triggers. That should make a small window with the trigger’s icon appear and zoom away whenever you run it. That will tell us if Quicksilver is even getting the keystrokes and trying to run the code.

-- 
Rob McBroom
<http://www.skurfer.com/>

[Will Fiveash]

On Monday, April 1, 2013 8:54:43 AM UTC-5, Rob McBroom wrote:

On Mar 31, 2013, at 8:23 PM, Will Fiveash <will.f...@gmail.com> wrote:

I'm now finding with QS v1 on my MacBook Pro running 10.7.5 that the triggers I use to control iTunes have stopped working.  I can't say for sure that QS has a bug but something has definitely changed as I've used these triggers for a long time.  For example I've used shift+command+spacebar to pause/play the current track in iTunes for several years.  Now it has no effect.  This is true for all my defined iTunes triggers which all start with shift+command.

I haven’t used them in years, since there are dedicated keys on “newer” keyboards, but I still have those triggers set up. In fact, I have ⇧⌘Space set to Play/Pause too. And of course, it’s working for me. :-)

What if you select iTunes in the first pane, then select the “Play - Pause” action? Or, if you have the iTunes Controls catalog entry enabled, you could select “Play/Pause” directly in the first pane and try running that. These should be alternate ways of running more or less the same code that the trigger calls.

I figured out my problem. I'm running iTunes v10.7 and the iTunes QS plugin that is installed is 2.3.1 which indicates it is only compatible with iTunes v11.  That is unfortunate because iTunes v11 removed a number of features that I use all the time and so I reinstalled v10.7.  Is there a way for me to install a version of the QS iTunes plugin that is compatible with iTunes v10.7?

[Raymon]

I have pretty much the exact same problem and am looking for the older iTunes plug-in for Quicksilver.

Can someone possibly share that? My previous iTunes plug-in has gone with the old Quicksilver after the update to v1.

[Rob McBroom]

On Apr 1, 2013, at 2:20 PM, Will Fiveash <will.f...@gmail.com> wrote:

I figured out my problem. I'm running iTunes v10.7 and the iTunes QS plugin that is installed is 2.3.1 which indicates it is only compatible with iTunes v11.  That is unfortunate because iTunes v11 removed a number of features that I use all the time and so I reinstalled v10.7.  Is there a way for me to install a version of the QS iTunes plugin that is compatible with iTunes v10.7?

I don’t remember how I worded the changes, but there seems to be some confusion. The plug-in was updated so it would work with iTunes 11 in addition to all of the versions it already worked with. And those changes predated the release of QS 1.0.0 by months, so if it was working a month ago, it should still work now.

Having said that, the current plug-in is set to require iTunes 11. Not because it really “requires” it, but because the plug-in loses features that should still be there for users of 10 and older. Did you install 11, update the plug-in, then go back to 10? If you delete the iTunes plug-in, then install it again from Quicksilver’s preferences, it should give you version 2.2.0 instead (since you don’t have iTunes 11 installed).

But I suspect you’ll still have the trigger problem, because nothing was changed in that area.

[Raymon]

Hi Rob,

I tried what you just said: Select iTunes Plugin 2.3.1, deleted it.

I then clicked on 'Refresh list of plugins' and it still shows iTunes Plugin 2.3.1 as available for download, not the old version.

I'm using iTunes 10.6.1 (7).

Can you simply link us to an older version to download so we can manually install it?

[Raymon]

This is what I'm seeing after deleting and re-installing the iTunes plug-in. It's v 2.3.1 with an error status: Requires version 11.0 of iTunes.

On Monday, April 1, 2013 4:17:37 PM UTC-4, Rob McBroom wrote:

[Will Fiveash]

I'm seeing the same thing when looking at the QS iTunes plugin info.

[Will Fiveash]

I hacked the ~/Library/Application Support/Quicksilver/PlugIns/com.blacktree.Quicksilver.QSiTunesPlugIn.34D.qsplugin/Contents/Info.plist and changed:

    <key>QSRequirements</key>
    <dict>
        <key>bundles</key>
        <array>
            <dict>
                <key>id</key>
                <string>com.apple.iTunes</string>
                <key>name</key>
                <string>iTunes</string>
                <key>version</key>
                <string>11.0</string>
                             ^^^^
            </dict>
        </array>

to:

    <key>QSRequirements</key>
    <dict>
        <key>bundles</key>
        <array>
            <dict>
                <key>id</key>
                <string>com.apple.iTunes</string>
                <key>name</key>
                <string>iTunes</string>
                <key>version</key>
                <string>10.7</string>
                             ^^^^
            </dict>
        </array>

and now the QS iTunes plugin works properly.

[Raymon]

Brilliant, that worked!

[Rob McBroom]

On Apr 1, 2013, at 4:25 PM, Raymon <vurto...@gmail.com> wrote:

Can you simply link us to an older version to download so we can manually install it?

I could have, but if the in-app system is broken I want to know. It seems that it’s partially working in the worst possible way. It’ll let you download the plug-in, but then it will refuse to load it. This is probably why the triggers stopped working in the first place.

We’ll look into that, but the short-term fix is to just remove the iTunes 11 requirement. That would mean the iTunes DJ actions are gone for iTunes 10 users, but that’s better than no plug-in at all I suppose. The 4 people that use iTunes DJ would just have to manually go back to an older version of the iTunes plug-in.

[Will Fiveash]

On Tuesday, April 2, 2013 10:14:51 AM UTC-5, Rob McBroom wrote:

On Apr 1, 2013, at 4:25 PM, Raymon <vurto...@gmail.com> wrote:

Can you simply link us to an older version to download so we can manually install it?

I could have, but if the in-app system is broken I want to know. It seems that it’s partially working in the worst possible way. It’ll let you download the plug-in, but then it will refuse to load it. This is probably why the triggers stopped working in the first place.

That's how it appears to me (broken in-app system in QS).  After I updated QS to v1, my iTunes triggers stopped working and when I looked at the QS plugins it showed the iTunes plugin as disabled.  Once I modified the version in QSRequirements in Info.plist, QS showed the iTunes plugin as enabled.

[Raymon]

Same here.

I didn't think it was the triggers since hacking the plist fixed the issue. Looked more like the plug-in wouldn't accept an older version of iTunes.

[Will Fiveash]

I assumed the problem was QS disabling the iTunes plugin because it's requirement that iTunes v11.0 be installed.

--
You received this message because you are subscribed to a topic in the Google Groups "Quicksilver" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/blacktree-quicksilver/ajb5jcA-gUI/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to blacktree-quicks...@googlegroups.com.
To post to this group, send email to blacktree-...@googlegroups.com.
Visit this group at http://groups.google.com/group/blacktree-quicksilver?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Will

[Rob McBroom]

On Apr 2, 2013, at 12:33 PM, Will Fiveash <will.f...@gmail.com> wrote:

I assumed the problem was QS disabling the iTunes plugin because it's requirement that iTunes v11.0 be installed.

Right, it’s not that the plug-in wouldn’t accept iTunes. Quicksilver wouldn’t accept the plug-in. But only because it said it wants a certain version of iTunes… so I suppose you’re both right. :-)

In any case, I’ve created an issue so we won’t forget.

https://github.com/quicksilver/Quicksilver/issues/1457

[Will Fiveash]

Great, thanks.
 

[Rob McBroom]

A new version of the plug-in is available that doesn’t claim to require iTunes 11.

It also doesn’t have a 3 - 10 second delay every time you play an album under 10.8.3.

[Will Fiveash]

On Thursday, April 4, 2013 8:56:47 AM UTC-5, Rob McBroom wrote:

A new version of the plug-in is available that doesn’t claim to require iTunes 11.

It also doesn’t have a 3 - 10 second delay every time you play an album under 10.8.3.

Thanks, that's working for me now.