Broken iTunes User Interface

When I use iTunes, all I can see are the section headings and track names. There is no background, so it makes it incredibly difficult to do anything in it. The problem first occurred in iTunes 7, and carried on to 8 despite working origonally. . I've tried reinstalling iTunes several times, but this did not work. Any help is appreciated.
Thanks in advance.

Are you suffering from transparent iTunes? If so you may find this thread helpful:
http://discussions.apple.com/message.jspa?messageID=7427113#7427113
If you are using any plug-ins, iTunes now has a safe mode to check if they are causing trouble:
Open iTunes in "safe mode" (without external plug-ins) Control-Shift (while opening iTunes)

Similar Messages

Why has itunes user interface been ruined?

Why has the itunes user interface been ruined? It used to be easy to use. Basic functions dont work any more. Editing a Play List requires extra steps. I cant restore the useful side navigation bar where I could easily add a song to one or more play list...
Incredibly frustrating.

When I plug the iPhone in the sync options comes up once, but once you leave you cant get it back. There is phone icon in the top icon nave bar - but clicking on it does nothing. What is the point of the icon if it does nothing?
How do you get back to the sync options screen where you can select the music you want without having to disconnect and plug it back in again?
It used to be easy... More frustration...

I have problems with my itunes user interface

i can't see all the options & checkbox int the prefernences window
what should i do to solve it ?

Hello gustavolopez,
Thanks for using Apple Support Communities.
To reinstall iTunes, please download and install from the following website:
Apple - iTunes - Download iTunes Now
http://www.apple.com/itunes/download/
Take care,
Alex H.

Why oh why was it fixed when it wasn't broken..the user interface

This is a serious error on Apples part to alter the way this critical program operates
its like taking away critical controls from an automobile...like the steering wheel
Its that bad its at the level like Microsoft would have done.
It may operate with all the same features...but where are they...not on the iTunes desktop
where one could surf iTunes to look at, get, explore
big mistake & an even bigger one not to listen to customers...
Bruce L. Farrar

Steve
Sorry I just cant see how you can compare iTunes 10.7 & iTunes 11 - yuo are in the minority !!
Everyone I speak to has the same view on this:
That 11 hasnt the same user interface & controlability.For me this is fundamental in the way I used iTunes to "surf" what was available from what I already had.I find the way I have to go through things in a list poor to unusable. OK Apple may want to have the same interface accrooss the whole product platform - but why the capability of a Mac with a omplete keyboard & larger screen allows for more possibilities than say an iPhone which I reackong any user will realise & accept...basically the iTunes on mac platform has been dumbed down & is now far less capable
The search "engine" that hasnt got fields to select to narrow down or focus a search is just riduculous & it doesnt work that well as whats comes back has to be searched through again.
Using iTunes 10.7 & before was an "adventure" into music or material you knew & you found things you didnt know about & to do this was easy & enjoyable. Ifound previosly I could find a single track out there quickly & also explore.
Whats happened is fundamentally bad - lets give a comparison - say if the whole user interface of the MacOS or write was altered, made significantly different...everyday tasks that you could do before had to be re learnt or just couldnt be done.
Even Microsoft are carefull about making changes to the way things work & the way that a user interfaces with this...one carefull step at a time OK Microsoft "things" have to recieve this type of carefull scrutiny & adjustment - but Microsoft onthe whole take thier customers with them. Learning point that Apple have yet to realise & learn from
Previous to this from Lion to Mountain Lion there was Frontrow a simple little program that gave a feature that me for one used (& enjoyed) regularly.....on the Mac doing something important...take a break, relax & enjoy some music...one press of the remote & you had all you music & videos there to be used...like a big iPod...really ver good. Finished relaxing or taking a break get back to work just where you left off, an impressive feature that was taken awy & replaced with NOTHING.
So for me at least the usability & functionallity of the Apple experience has deteriorated...for no appreciable gain....for just a commonality of controls accross the products.
Its called "change for changes sake" & in this case the customers werent consulted they were totally ignored in being left with something that is retrograde.
The very fact that I am here with others making comment is proof postive that the situation is a definate backwards step. I just hope that for Apple its a "blip" i.e. an error that will realised & corrected...
I have been using Apple products from 1989...I am not a Microsoft refugeee or reluctant convert who is throwing mud..just the opposite in my family we have:
4 Macbook Pros,
an iMac,
4 iPods,
4 iPhones
Apple TV
all backed up ona time capsule.
We have lived through the bad times & good...I realise that Steve Jobs cant come back...but I am sure he would have listed & then gone back to the teams & forced the change backs through.

ITunes 11.1.1 User Interface corrupted

After I updated to 11.1.1 the user interface of iTunes is messed up.
The icons and the tabs do not correspond to the proper actions.
see images below. Any help would be muchly appreciated.

Issue Solved !
If you have the same issue follow these steps:
0. back up your itunes collection (not neccesary)
1. Re-download iTunes from here http://www.apple.com/itunes/download/
(approx. 226 MB for Mac)
2. Ensure that the iTunes app is not running
3. Double Click the downloaded file (iTunes11.1.1.dmg)
4. Follow the screens to Install it (on top of the one you already have installed).
5. Run the app
Now the user interface should be back to normal.
Hope this helps

Time Machine user interface broken after PowerMac G5 replacement

My PowerMac G5 tower recently experienced a disaster. I was able to replace the unit with a very similar unit, and moved in my hard drive. It's working great.
I've been using an external hard drive for Time Machine backups.
I decided after moving in to the "new" G5 to hook up my external drive and do another incremental backup.
I received the error messages that are associated with a different motherboard - the backups are associated with the old logic board's MAC address.
Apparently there is a relatively easy way to fix this with Snow Leopard and later - a terminal command called tmutil.
Not so in Leopard.
I found the following thread at Mac OS X Hints, and spent quite some time reading it: http://hints.macworld.com/article.php?story=20080128003716101
I felt somewhat intimidated by all the tinkering with extended attributes, and opted to use a link from the thread which lead me to a script that would automate the process.: http://hints.macworld.com/article.php?story=20081216145458979
I ran the script, it gave no error messages, and reported that the previous backups had been succesfully inherited to the new computer and Time Machine.
I can now run Time Machine, it does incremental backups, and if I boot the computer from my Leopard DVD, I can do a full restore to various points in time.
However, the Time Machine GUI application is "broken". There is no past. The only time available is NOW, even though there have been 2 or 3 recent backups, and many before then. There is no way to roll back in time, choose a file or folder and restore it.
Summary: Time Machine is creating backups, and the Leopard DVD believes it could restore the whole hard drive with them. But the handy user interface is useless - for all users.
I am very close to doing a complete scorched earth reset and simply begin doing Time Machine all over again, just to get the user interface to work.
Any suggestions?

Gordon Henderson wrote:
Apparently there is a relatively easy way to fix this with Snow Leopard and later - a terminal command called tmutil.
Actually, not Snow Leopard. It's on Lion and later.
However, the Time Machine GUI application is "broken". There is no past. The only time available is NOW, even though there have been 2 or 3 recent backups, and many before then. There is no way to roll back in time, choose a file or folder and restore it.
Sounds like the hack is, well, like most, a faulty one.
It's barely possible it's somehow confused Time Machine into treating each backup as being on a separate drive, and only the most recent is connected. You might be able to see the old ones via the procedure in #E3 of Time Machine - Troubleshooting, but that's not going to have the result you want.
I am very close to doing a complete scorched earth reset and simply begin doing Time Machine all over again, just to get the user interface to work.
That's probably best.

Why do I get -18001 Errors using Customised TestStand User Interface

Hi all
I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
If anyone
has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
Thanks
Dave

David,
I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
LabVIEW : VI is not executable.
An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
2) The same error will occur when
a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
Building The Operator Interface
The following are steps if you are using a LabVIEW operator interface.
1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
Creating a LabVIEW Run-time Server
If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
Assembling the Test VIs for Run-Time Distribution
This distribution process uses one of the shipping TS examples that calls LV VIs.
1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
3) Confirm that the sequence runs without problem.
4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
6) Set the target directory to be something distinct like C:\temp\AssblVIs.
7) If you are using TestStand 2.0 skip adding Dynamic VIs
8) Save with or without diagrams. Its your choice.
Change Search Directories
Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
1) In the sequence editor select Configure>>Search Directories.
2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
3) Close the Edit Search Directories dialog box.
4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
1) In the sequence editor select Configure>>Adpaters.
2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
Distributing Components
-To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
-To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
-You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
Hope this helps.
Regards,
Kitt
=========================================
Title:
Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
Components that need to be distributed:
TS engine
Operator interface
LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
LabVIEW run-time engine
LabVIEW test VIs
Test sequence files
Actions before distributing:
It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
Assemble the test VIs for distribution.
Update the TestStand search directories so that the sequences reference the assembled VIs.
Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
Test the distribution components on the development machine.
Enter section headings, separating each section with a line break:
TS Engine Component
Operator Interface Component
LabVIEW ActiveX Server
Configuring the LabVIEW Standard Prototype Adapter
LabVIEW Run-time Engine Component
Assembling your Test VIs for Distribution
Note
TS Engine Component
With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
Operator Interface Component
You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
LabVIEW ActiveX Server
You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
Configuring the LabVIEW Standard Prototype Adapter
When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
LabVIEW Run-time Engine Component
If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
Assembling your Test VIs for Distribution
After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
Links: See Distributing LabVIEW Test VIs below
Note
Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
==============================================

User interface effects even though it's deselected?

So I have "user interface sound effects" deselected in System Preferences, but whenever I'm using iTunes or other apps I still get SOME of them? Particularly if I go to delete something or get some type if "denial" interface effect, one that users the 'Basso' sound.
Even more odd is the fact that right now I am streaming music to a Jambox via bluetooth and when I hear an effect it only plays thru my Macbook speakers and not the bluetooth speaker.
Any ideas on how to make this stop?

I reset the Test Tool.
Although I know how to access and change my Preferences...not sure about how
to go about trashing them. You mean delete them?
Seems they're all in some default settings. How would I remember all the
box checks?
I did uncheck all 5 'Type' boxes with no change.
I also know that any other program with text (e-mail, facebook, Word etc)
all work fine, but just in case I unplugged the keyboard to a different USB
port...no fix.
I'm trashed still...
Thanks for the reply Hunt!
--Thomas

Weather not displaying in notification center after iOS 5 update not to mention the entire user interface is much more sluggish.

Weather not displaying in notification center after iOS 5 update not to mention the entire user interface is much more sluggish.

Okay, mine now works here is what I did.
plug in the iPhone, iPad etc
in iTunes select the phone or iPad
Under Summary uncheck "Sync with this....."
Under "Music" uncheck the "Sync Music"
Let it remove all the songs, dont worry it will come back no problems.
Once that is all done all the music on the phone or ipad should be gone.
Now check them both back on and everything should copy back onto it.
Working now !!!!!

Inconsistent User Interface in ITMS

I just looked at the free items for this week on ITMS, and was reminded that the user interfaces for songs, albums, audio books and movies are different. Movies and audio books use one style (with a big circular "Preview" button and a small "Add Book" or "Add Movie" button to put the item in your cart) while songs use a very different style. With the "Single of the Week," the big circular button is "Get Free Download" and the small "Add Song" button is at the bottom and does the same thing as the "Get" button.
I think a more consistent layout would be much more appropriate. Letting the user click a "Preview" button on ALL ITMS items would be more useful than having this feature with only some items, and an obvious preview button would be easier for new users to catch on to than the iTunes master Play button. Likewise, using the same button for selecting all items would be more appropriate than having different buttons for different kinds of items.
(I'd also like to see a better "suggestion box" for ITMS than having to start a discussion forum topic, but I spent a lot of time looking and couldn't find anything better for this suggestion.)

Here's the link to iTunes feedback:
http://www.apple.com/feedback/itunesapp.html
It's also available directly in iTunes from menu iTunes>Provide iTunes Feedback
Best of luck.

HT4208 App store user interface language

Recently, the user interface language of the App Store turned from German to Japanese. How can I set it back to German?

The iTunes and App store will usually only display the language of the country you made the subscription I can only down load from Japan iTunes and sometimes they do not have Apps or what ever but someties it depends on you language prefferences too ,it is quite annoying and confusing I use Finnish and English Swedish.
Apple is not altogether internatonal because of international agreements and local protectionism that is why there is no Finnish dictionary and spell checker
we are bound by the laws of the country we live in at the present and Apple and any other company does not want us to mixit up ,but they the internationalists Capitalists can do this like make Apple pruducts in China cheap labour.
yet it took years for Chinese to get Apple products ! Apple Japan is not very popular beause Japanese do not like the translations of Japanese by Nissei Japanese who live in the US!
Look at all the language preferences in Apple OSX they do nothing I use about 5 languages and find a total mix up my keyboard does not know what I am using better to have different computers install different language.

User interface documentation

I am looking for some user documentation for iTunes (Mac) that is more comprehensive than the Apple tutorials. In particular, the user interface isn't always intuitive, and I keep coming across things that take a while to figure out.
For example, I am trying to put the movements of a classical work in order in the main window so that they will play in the right order; in spite of numbering the tracks in the Info window, it still doesn't happen, and I can't find a way to do this.
A previous discussion
https://discussions.apple.com/message/7234401#7234401
(now archived) gave a reference to an article
http://docs.info.apple.com/article.html?artnum=93078
which is now not available.
Does anybody know of anything current which could help?
Thanks.

I find the iTunes Help accessed from the iTunes > Help menu to be really useful. You can browse the contents, or use the search bar at the top right to go right to what you want. For example, I searched for Edit song and CD information and found this:
To edit song or CD information:
Select the song or CD you want to edit, and choose File > Get Info (or press Command-I).
Click Info and make your changes.
Tip: If you’re changing the same information for multiple items (genre, for example), you can select all the items and change the information for all of them at the same time
Here are other ways to customize song and CD info:
You can edit information in the Info window to make it easier to find and sort items in your library. For example, you can:
Group individual movements on a classical CD into one work by indicating the movement (for example, “Piano concerto in A Minor, Op. 54”) in the Grouping field.
Group songs that are part of a compilation together in your library by clicking the Info button and selecting the “Part of a compilation” checkbox.
Identify the individual artists on a tribute album in the Artist field, and type “various” in the Album Artist field.
Create your own genre category by choosing Custom from the Genre pop-up menu.
Change the order in which tracks on a CD play by changing the numbers in the Track Number fields.
Try it. You'll find a lot of good tips.
There is also an excellent archive of 3rd party tutorials here: http://www.ilounge.com/index.php/articles/archives/tutorials

3rd gen User Interface

[This is a slightly toned down and otherwise amended version of a review I posted elsewhere earlier today.]
The new iPod was my first specialised MP3 player purchase, last night. Considering the allegedly superior User Interface design of Mac products, I’m not really that impressed.
Most of the music I listen to is classical, and the whole MP3 industry needs to sort out some fundamental naming problems for classical tracks. For a 2CD-box containing one Mahler symphony, I have two “Albums”, one for “GustavMahler; Symphonie No. 2; Abbado, Chicago SO”, the other for “Mah; Sym 2; Abbado, Chicago SO”.
First requirement: a relational database with a single ID for each composer, work, conductor, orchestra, etc. etc. Preferably with each work categorised as Symphony, String Quartet, Opera, etc. and the ability to have a number and/or name for each - so that “Manfred Symphony”, “Symphony No. 6″, and “Symphony No. 6 (’Pathetique’)” are all possible. Major benefit: only one person has to know how to spell “Shostakovich”. Ideally, each language gets its own versions of names for both people and works. I can amend the album titles in iTunes, but I have to do so once for each track (why, I have no idea - all tracks started with the same album title - what sort of lunatic would want to set different album titles per track?). Later loading up of a 4-disk boxed set of Beethoven quartets and a 2-CD of Verdi's Otello produced similar stupid title differences.
Second requirement: recognition of CDs 1 and 2 (and up...) as part of the same 'album'. I’m really looking forward to putting the Ring cycle on there.
Third requirement: a Work/Disc/track hierarchy, that deals with more than one work on the same CD and more than one CD for the same work. Then we can stop having those idiotic track titles like “Strauss (R), 4 Last Songs, Op. posth. - Im Abendrot” where everything except the song title is the same on 4 different tracks and there isn’t enough screen width to see the parts that are different. Oh, and then the addition of “Work” to the categories like “Album”, “Playlist” and so on.
The same kind of tripe is served up in Windows Media Player, but as I had to download a whole new 50 Mb app just to put CD tracks onto my iPod, Apple seem to have had the opportunity to do that “right thing” that you’re supposed to be experts at. Guys, you missed it!
Back in the user interface of the player itself, if I’m playing an album in that old fashioned “track 1, then track 2, then track 3″ way, I sometimes wonder what track’s coming up next. Finding out means MENU click, move down to Music, and select it, move to and select Albums. Now find the album that’s currently playing (for which you have to remember what it’s called - there’s nothing else to tell you which album is currently playing). Select it, find the little icon that shows which track is playing, and then read the line below. Then repeat most of this tedious operation backwards to return to where you were. Back in the stone age, you just picked up the record sleeve and looked. Even worse, someone at Apple decided to use a huge chunk of screen space for the album cover pic that I don’t bother downloading. “Next track: Ruhe, Meine Seele” - that’s all we need. Far more useful than a pic of a couple of quavers/eighth-notes.
The there's the joyous discovery that having not spotted the opportunity at some point in initial set-up, I'm stuck with that boring name "Owner's iPod" for the rest of the products life.

I apologise for that. Your conviction sounded so strong I thought it a shame to try to correct you.
To be a bit more helpful, you can select multiple tracks and set their album (along with various other properties) all at once. In the same way, you can set the "disc number" for the tracks so that multiple discs are seen as part of the same album.
You can also rename the iPod as you please (though I can't remember exactly how - try right-clicking/Cmd-clicking on the iPod's name), so you're not stuck with that silly name forever.

Itunes Aero Interface

Good day,
I am a long time Itunes user. I recently upgraded to Windows 7 RC1 and was wondering if it is possible that Apple will finally enable the Aero interface to work with Itunes. I didn't use Aero back when I was on Vista because it would just slow down my system too much but now with 7 I have it turned on. Every single application I have support it but Apple products (with the exception of the new Safari).
What is the reason Itunes is not able to support it? Is there a way to enable it (workaround)? If not, is Apple considering supporting the Aero interface. I know it's not a big deal butit would be nice
Thanks!

The iTunes SDK has not been updated, so I can only recommend you logon to your developer account and raise the issue through channels at their site, probably a bug report would be appropriate.

OCS Content services web user interface

Greeting all,
Is Oracle drive client required to perform the edit feature when attempting to select edit under the web based content services on a file. When I select edit from the web based user interface on a file I get a error saying that oracle drive is not installed.

I reinstalled with the newer version as the upgrade from the previous version was not to smooth, and I was left over with to many broken pieces after the upgrade attempt.
I suspect that I'm going to find out that the file versioning and check in and check out features are going to require oracle drive installed as well. This is not a option for us, as our remote clients need to use a pure web type interface/connection. It seems as if oracle still has some work to do to get the content services Web UI to were we need this to go.

Broken iTunes User Interface

Similar Messages

Maybe you are looking for