- Fixed occasional JIT error when pairing with device.
- Fixed random foobar crashes.
- Volume and seekbar sliders are quite smooth now.

Download: foo_touchremote 0.2.2.1

Requirements:

• .NET Framework 3.5 SP1 or higher;
• Bonjour;
• Remote app on your iPhone, iPod Touch or iPad.

Grab and try: foo_touchremote 0.2.1.2

Also I have a request to those of you who has a MacBook and a not-Touch iPod (i.e. Classic, Nano, etc.). Please post in the comments how does the player appear in the Mac OS X. Is it mounted to some directory (which exactly?) as a removable drive just like in Windows?

I wonder whether new library will completely supersede iTunesDB or will they continue coexisting for compatibility reasons. But anyway, linux guys would be happy since SQLite format is open and much more clear for understanding.

We need following functions (meta-language):

ERROR AMDObserveNotification(HANDLE proxy, CFSTR notification);
ERROR AMDListenForNotifications(HANDLE proxy, NOTIFY_CALLBACK cb, USERDATA data);

and callback delegate:

typedef void (*NOTIFY_CALLBACK)(CFSTR notification, USERDATA data);

First, we need AMDObserveNotification to subscribe notifications about “com.apple.itunes-client.syncCancelRequest”. Then we should start listening for notifications (second function) until we get “AMDNotificationFaceplant”.
That’s it. When notification got, you should unlock and close lock file handle (don’t sure if you need to post “syncDidFinish” to proxy, seems it doesn’t matter) and terminate sync gracefully.

P.S. The same notification is also got when you unplug your device, so you should always be ready for errors.

And today I’ve managed to create a fully cross-platform .NET library to deal with Apple devices. It even works without re-compiling for target platform. The trick is to use MobileDevice (dll on Windows and framework on Mac OS X) instead and apply some dll redirections for Mono.

However, it’s not just to change referenced library name. Unlike iTunesMobileDevice, MobileDevice framework doesn’t use native threads on both platforms. Also it is more strict about strings, so hand-made CFStrings most likely won’t do.

P.S. I really have no idea why both of these libraries are included in Windows distribution of Apple Mobile Device Support, ’cause they don’t even reference each other.

A few days ago I was trying to resolve a reported issue with “parameter is not valid” error.
At first I thought there were some changes in thumbnail formats (error was got on iTouch 2G, and I’ve never tested it on that device). Then I looked in ArtworkDB and noticed that it had invalid information inside, like overlapping offsets in cache files.
So I understood ArtDoctor must also be able to rewrite artwork database, not only cache. It still doesn’t affect main database and is safe for your player. Even if something goes wrong, you won’t lose your music.

Just to make it clear: that iPod was managed by MediaMonkey. I don’t blame it, but you should be careful when using unofficial managers. There is absolutely no warranty you’ll get your artwork (or whole media library) working after next sync.

I’ve already succeeded in complete rewriting artwork information and made a “lab” version of ArtDoctor 2.0 (it’s private, but you could contact me to get one for testing).
It definitely works, but there are some things to do before release:

1. It has neither GUI, nor settings – it is a console prototype. Eye-candy UI must be made before going to public.
2. It supports only iPhone and iTouch cache formats for now. I have no Classic/Nano/etc. models at the moment and don’t remember which formats do they use. If you have one, please send me your ArtworkDB file (it is located in hidden folder iPod_Control\Artwork). Anyway, there’s a trick with ticking “Display album artwork on device” option off and then on for these devices, so they are not a primary target.
3. I didn’t find a way to notify device about database changed yet. It somehow caches that database, so now you need to restart your device (completely off and then on) to reflect changes correctly. That should be resolved before release. [solved]

Stay tuned.

Go to product page.