Converting Songs Bought in iTunes to mp3

If you have bought songs in iTunes and want to play it in your Palm or other devices (in my case using PocketTunes for my Palm LifeDrive) and need a mp3 format to do it, here are some ways to do it.

Use Audacity, an OpenSource software to convert it

OR

Try this method:

1. From your iTunes, burn the CD of the songs you purchased using the iTunes preference Disc Format: Audio CD. Just go to Edit -> Preference -> Advanced -> Burning. Note: iTunes will not allow you to burn MP3 CD for songs you bought. To Burn CD, just click on the Burn Disc icon &#59;D

iTunesPreferences
Click to view original size

2. Use your mp3 ripping software, in my case, I used, Windows Media player. Click on the Rip tab. Right click the Rip tab and a pop up menu comes up. Choose Tools -> Options . From Options, click on Rip Music. Under Rip Settings, Format choose: mp3.

WindowsMediaPlayerPreferences
Click to view original size

3. Rip the songs you bought and burned to the Audio CD. The songs converted to mp3 format will be created in the directory as specified in your preferences directory in Windows Media Player. Media Player created a subdirectory under this called Unknown Artist\Unknown Album (Date TimeStamp), e.g. D:\myhomedirectory\My Music\Unknown Artist\Unknown Album (5-13-2006 10-58-55 AM)

4. Transfer your mp3 files to your non-iPod MP3 player, in my case the LifeDrive

Transfer to LifeDrive
Click to view original size


Enjoy!

Open Source and Offshore Development

Recently, my friend Todd McGrath has written about the symbiotic relationship of open source software and offshore development. He builds a case for the relationship between building trust in developers you might never meet (or mitigating risk in an offsourced project) with the use of open source software in the project.

In combining Open Source software and offshore development, high quality, cost effective software is more easily obtainable... Open Source provides a foundation of trust and confidence when using and/or providing offshore software development services.

In this article, my definition of Open Source is intended to mean complete products, tools, libraries, etc. with a vibrant community.

When implementing an outsource development strategy, choose developers that will use Open Source software in the overall solution. Using Open Source in the solution provides a shorter path to confidence and trust in outsourced software developers. Put another way, open source plays a positive part in the risk management of the decision to outsource. By choosing offshore software development partners that deliver based on community established Open Source with appropriate license for your needs, quality and the most competitive cost can be obtained.end quotation
-- Todd McGrath in Flat World Software Development ยป Open Source and Offshore Development

Those excerpts give his premise and conclusion, but you must read the whole article to see how he builds his case.

Todd focuses on outsourced, especially offshore, software development. There are, however, other things being offshored by businesses today. Business processes such as accounting and human resources, IT operations & maintenance, telecommunications management, design and development projects, and manufacturing are only a few examples. And there are many reasons for businesses to outsource. Some of these are reducing cost, enhancing skills, suplementing personnel, and taking advantage of economies of scale.

Having a common architecture or framework can be important in mitigating risk. But the assumption here is that if the first outsourced project fails, another team can pick it up because open source software provides common themes throughout software development, and you can find other developers with familiarity with the open source software that forms the basis of the project. I don't believe that this constitutes bulding trust in the original team, or even in the offsourcing tactic. So, I disagree with the premise that bulding trust is equivalent to mitigating risk. I would agree that using open source software in a software development project can help mitigate risk.

More importantly to building trust and to mitigating risk is assuring that the culture of the outsourcing partner matches your own culture. Can both partners truly communicate? Not just speak the same language, or a dialect of the same language, but truly understand each other's written and spoken dialogues, specifications, emails, messages and meeting notes. When offsourcing, societal, cultural and language barriers will complicate matters, and you may not have much control over these factors. [Excepting some artificial and unsustainable rules, such as a USA firm should only choose offsourcing partners in the Philippines because of the good blend of cultural match and economics.] You do have control over corporate culture aspects that affect the project, process, program or people being outsourced. For the type of software development projects of which Todd is speaking, you might want to consider:

  • decision making
  • documentation
  • specification
  • in-code comments
  • project management
  • QA
  • configuration control
  • version & release management
  • testing
  • bug fixes, enhancements and problem escalation/resolution
  • meeting protocol
  • team structure/team building
  • interfaces across and interactions among business untis/users, operations personnel and developers

I think these types of factors will be more important in building trust across distributed workgroups than the software architecture to be used.

Having said that, I do agree that there is a symbiotic relationship between offsourcing and open source development methodologies, in that both use the priciples of distributed workgroups, both are enhanced by the TeleInterActive Lifestyle™ and the two movements have feed off each other to a certain extent.

:Ben Metcalfe Blog Multiples

The idea that we would require multiple blogs per author and multiple authors per blog with the possibility of cross-posting is one of the deciding factors in our choice of b2evolution over Wordpress, plog or other blogware platforms.

Joking aside, Om's spot on. His instincts are right, and I can see this being a big theme of 2006 - people getting their second, third, forth blog. Blogs are cheap/free so why not? And for many of us it's already the case.

The question, therefore, is what can blogging platforms do to cater for this? Movable Type does multiple blogs and Blogger and TypePad also cater for it. So come on Matt, you gotta get WordPress multiblog working.end quotation
-- Ben Metcalfe in "Where do you put all that other stuff?"

We also couldn't agree more. There's only so much differentiation that can be done through categories. My partner and I each wanted a personal blog that could go in any direction that tickled our fancy at the time, as well as our focused blogs on the TeleInterActive Lifestyle and Open Source Solutions for BI.

The idea that folk would want to publish in multiple places also is one driver behind Marc Canter's philosophies, as he pointed out in "Cross Posting and the Future of having Multiple Blogs".

So, when looking at support from blogware, also look at support for micro-content, identity management, and OPML. Such is where the near future lies. The far future... who knows?

Trackback Response Etiquette

I was recently asked if that was a blogosphere etiquette for responding to trackbacks. I don't profess to be an expert on blog etiquette, but I'll answer anyway. It seems to me there are three ways to respond to a trackback:

  • do so in the comments to the original post on your own site, as my friend who asked the question did
  • do it in the comments of the trackback site
  • create a new post in your site with a trackback to the post that did a trackback to your original post

I actually like the last option. If every blog management software supported trackbacks, and everyone used them, the conversation could be held with minimum redundancy and full two-way traceability; after all, you can trackback to as many other sites from one post as you want. This builds a true "mini-web", "sub-blogosphere" or "pocket universe" [whatever] with all posts on the subject interacting thus creating a true conversation, with each person who participates in the conversation able to retain their "voice" as well as build search engine and meme tracker ranking due to the inter-linking. The disadvantage is that RSS 2 doesn't seem to include trackbacks in a feed, so the conversation is lost to someone who only reads feeds. I guess another disadvantage is that not everyone uses or allows trackbacks.

Tracking and consolidating a conversation is becoming a hot topic in Web2.0 circles, with some companies coming out with tools to do this. [See the techcrunch post on CoComment for an example.]

There is one point of etiquette that is somewhat related. Whenever one refers to, responds to or quotes something else on the web, one should provide full credit for the author/source and a link to that item.

Vonage IPO

Internet-phone company Vonage Holdings has filed to raise up to $250 million in an initial public offering. The company also named Mike Snyder, formerly president of security company ADT, as its new CEO. Founder Jeffrey Citron, who had served as CEO, remains chairman.end quotation
Wall Street Journal, 2006 February 8 Subscription Required

Having watched VoIP through Jeff Pulver's newsletter and, now, blog, since 1994 and through working with Nortel in the late '90's, it is very interesting to see VoIP finally coming of age. We've come a long way from Net2Phone.

The WSJ article points out that Vonage has been growing but not profitable, and that they've already raised 650 Million Dollars in funding. Yes, VoIP is coming of age, but still not taking off yet.

June 2019
Mon Tue Wed Thu Fri Sat Sun
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
 << <   > >>

The TeleInterActive Lifestyle is about the business processes, life choices, management challenges and technical issues facing organizations and individuals as individuals and organizations adopt the Internet of Things, Mixed Reality, wireless networks of all levels, mobile devices, long-distance collaboration, social networks, digital transformation, and adjust to growing urbanization.

Sensor Analytics Ecosystems for the Internet of Things (SAEIoT) brings value from emerging technologies through data management and analytics, advances in data science, as the IoT matures through the 5Cs: Connection, Communication, Contextualization, Collaboration and Cognition. The socialization of machines will allow for Privacy, Transparency, Security and Convenience to be flexibly provided with two-way accountability to build Trust among Humans and Machines.

AsDataArchon, we have evolved our consulting data scientist work from learning how to incorporate sensor analytics into data warehouses, business intelligence and analytics to focusing on IoT data management and forming sensor analytics ecosystems.

37.540686772871 -122.516149406889

Search

  XML Feeds

mindmaps

Our current thinking on sensor analytics ecosystems (SAE) bringing together critical solution spaces best addressed by Internet of Things (IoT) and advances in Data Management and Analytics (DMA) is here.

Recent Posts

Website engine