IPhone OS4 Fix Date????

[Better2LightACandle]

Painless temporary fix:

Create new folder on desktop, e.g. "TEMP iTUNEZ PLAYLIST"
In MM, use Send to...>Folder (Copy) to create your playlist du jour
In iTUNEZ File>Add Folder to Library
Drag/Drop/Sync in iTUNEZ, while not messing with your whole MM library

Total additional time....negligible
When MM is updated, delete "TEMP iTUNEZ PLAYLIST" folder
Go back to ignoring iTUNEZ

[FixNowPlz]

yea, but if you dont have your artwork embedded... bye bye cover art.


FIX PLZ

[frankz]

Better temporary fix: This plugin:
http://www.mediamonkey.com/forum/viewto ... =2&t=45713

[Fix-U]

FIX !!! FIX!!! FIX!!! FIX!!!

[wdpaynter]

According to the mantis site, this has been solved and added to release 1298 (yesterday AM). Any ideas when this will be released as beta or actual release?

http://www.ventismedia.com/mantis/view.php?id=6398

Thanks
BP

[njkode]

According to the mantis site, this has been solved and added to release 1298 (yesterday AM). Any ideas when this will be released as beta or actual release?

http://www.ventismedia.com/mantis/view.php?id=6398

Thanks
BP

It will prob be a few days for the beta at least. RC will be some time after that

[Furthur420]

I'm really sad about all of this. Most of my music is FLAC and MM would auto convert for my itouch. I HATE itunes. so i guess i'll have to wait this one out..

[dkstott]

has it been"at most a few days before a release will be issued " yet??




Dave

[refs_unperson]

Having just got back from holiday, I've been scouring the net to see if a fix for this issue exists yet and found this thread. After reading through it, I felt I needed to register and post my comments.

My thoughts on MediaMonkey - Its quite easily the best audio organizer out there for my purposes. Its a shame that this issue with iOS 4 has come about, but as a developer myself I understand the difficulties in maintaining compatibility with an ever growing number of 3rd party libraries / OS's etc. Quite clearly, if the issue was easily fixed, it probably would have been by now. The fact that its taken as long as it has should give some indication of the complexity and effort required to resolve the problem. I trust people and I doubt that the MediaMonkey development team have been sitting around idlely.

I bought MM because I didn't want to install or use iTunes on my media center computer. AFAIK, I can't get a refund after a few years of using this product...although I certainly would if I could. We're moving into the third week of release. Obviously the inability to sync *at all* is a show-stopper. This length of time for a critical update to MM is unacceptable by any reasonable standard I've known to exist.

I bought my license approx 5 years ago. Do I feel that I have got my moneys worth - hell yes. The current situation is clearly a pita for all of us, but considering the cost of the software, its more than acceptable in my opinion and I feel I got my moneys worth within the first 6 months of using the software. If you feel that this software should maintain compatibility with all 3rd party software/hardware, you would have to expect to fork out alot more money. For me - the balance is right. Possibly for you it isn't so therefore maybe MM isn't the ideal fit for you. Or... maybe the iPhone isn't the best phone to use due to Apples development/marketing strategy. I have the iPhone 3Gs and have updated to iOS4 but all my music is still accessible however I suspect that next year, I won't be buying an iPhone 4G or whatever it is they have out at the time. Whilst it may not be obvious to the average consumer yet, Google's approach with Android is better for everyone.

One note to the MM team - in our team, we provide daily updates on progress for critical issues and whilst my client base is likely 100s of times larger in terms of revenue, I feel the practice is a very good one as it builds trust between the development team and the customer. Perhaps if this isn't feasible, maybe you could set some expectations regarding frequency of updates so everyone knows where they stand.

Speaking as an IT lead in a major company, I can testify that we have had trouble tickets open for far longer than this for far smaller issues.

Speaking as an IT lead in a major company, I would be fired by now if I had trouble tickets open for this long on issues of this size.

Cmon guys, comments like this don't add value to the thread because you don't know all the facts and no one has an understanding of your job, client base, code base, product, strategy etc.

[rovingcowboy]

their answer to daily updates on troubles was the ventis list they post a link to with every update. it is there in the update posts to go check out it is not just for that one update it is able to be checked at any time and see what is being taken care of.
they said the posting of updates in the forum's or news letter would be too much for them to do with all the fix'es they are doing and the upgrading that is being done. there are only a few programmers for the mediamonkey so they don't have time for all the nice little things that might be done, since they fix the errors as soon as they can.

some errors are made by third party app codes being changed to block other programs from working with them.
some are caused by hardware updates that thus cause driver updates which cause the need for third party programs to be updated to fix the errors.
more and more systems using the program cause a wider and wider range of issues on both those matters because not every system is the same. what fix's it for one might not fix it for another system?

[refs_unperson]

their answer to daily updates on troubles was the ventis list they post a link to with every update. it is there in the update posts to go check out it is not just for that one update it is able to be checked at any time and see what is being taken care of.
they said the posting of updates in the forum's or news letter would be too much for them to do with all the fix'es they are doing and the upgrading that is being done. there are only a few programmers for the mediamonkey so they don't have time for all the nice little things that might be done, since they fix the errors as soon as they can.

some errors are made by third party app codes being changed to block other programs from working with them.
some are caused by hardware updates that thus cause driver updates which cause the need for third party programs to be updated to fix the errors.
more and more systems using the program cause a wider and wider range of issues on both those matters because not every system is the same. what fix's it for one might not fix it for another system?

in our team when we have a critical incident (which isn't often thankfully), we have one person who every day spends 5 minutes putting together an update with progress until the said issue is resolved. I'm not suggesting that this process is followed for all defects (which would clearly be unsustainable), just for the ones that grab the headlines on an exceptional basis (I'm not really in a position to say whether this is the case here but if it warrants an update on the news page, that suggests a very serious problem with significant user impact). this was a lesson I learned v early in my days as a support manager and I found that the more frequent and detailed the updates, the less questions I got (in fact, when communicating updates for serious problems, we use the number of questions back as an indicator of how successful the communication was. we now v rarely get any questions at all). I'm also responsible for post resolution preventative actions and I know this detail is always well received by our user base as it shows a willingness to improve the development process and reduce the likelihood of future recurrences.

All that being said, whether such approaches is appropriate here is not for me to say, I just want to share my experience of development/support in the IT industry. I want to see MediaMonkey succeed because I strongly believe in their product (which is why I recommend this product to all my friends). I see a gap for improvement here and think it would be quite low effort to fill. That being said, I don't know the development process at Ventis and such a suggestion could be contrary to the development methodology of choice.

[Cactus Jack, Too]

I have an iPod Touch 3G that HAD OS3.1.3 on it. With the latest MM, syncing was perfect. I knew that iOS 4.x had numerous bugs and complaints, so I didn't upgrade. I knew that MM doesn't support iOS 4.x yet, so I didn't upgrade.

Then, the DB got hosed on the Touch. Launched iTunes to try to fix, which said it could not read the Touch and that I needed to reset to factory defaults. I initiated that reset, only to find out that Apple FORCES you to install iOS 4.x (which was NOT the factory-installed OS)! You cannot restore iOS 3.1.3, which was a PURCHASED OS, unless you try following one of the OS "hacks" found on the web. Tempted, but I don't trust them.

So, MM developers, yes hurry up and fix MM to support Apple's f'd up product! Why is nobody here trashing Apple for their stupid-ass practices?

By the way, it IS possible to sync your music files to the iPod through iTunes without adding the files to the iTunes library. From Windows Explorer, drag the music files and drop them on the iPod icon in iTunes.

[ClayM]

I suspect the reason that nobody is trashing Apple's practices here is because it's the only thing more useless than complaining about the lack of a MM update

[rovingcowboy]

I suspect the reason that nobody is trashing Apple's practices here is because it's the only thing more useless than complaining about the lack of a MM update

what version do you have useless?

oh you opened the door on that one.

but joke aside what version do you have mediamonkey updated a few weeks ago did you get that one?

you see your comment would be better if you had said complaing about lack of winamp update or wmp update. but mediamonkey is updating as fast as they can get the errors fixed and tested.

[jiri]

The first beta version of the OS4 support has been released - see the beta forum.

Thanks for your feedback,
Jiri