Synching to session tempo

If I use a third party delay plugin that synchs to the tempo set in the DAW, will that work in CS6? I suspect the answer is 'yes' but I want to make sure. (How can a third party plugin know what the tempo is in the DAW?)

Echo boy works in sync for me but only after hittin the little "midi" switch under the tempo display. On Panman you have to select "rhythm step" and then look for the same switch. On the h delay you have to hit the "host" button. Super tap set synch to auto. I'm on 9.1.6 in os 10.6.8

Similar Messages

How to Take Existing Audio and Match to Session Tempo?

I have an existing piece of an old song, that I would like to hear pop in here and there in a new song I'm doing. The two are not MILES apart in tempo, but the old piece is somewhat faster.
When it does show up in this new song it will only show up for a bar or two.
Thanks for any help here...
Tom

Try this, excellent results each time……..
In my explanation of tempo curving in Logic I will assume that the audio tempo should change gradually over time without affecting the pitch.
Let's go:
- open your project
then
- open <Global Tracks> and choose Tempo
- insert audio you want to manipulate on to track 1 and activate <Flex>
- Hit Cmd I to open the inspector
- in the Track Parameter Box choose next to Flex Mode -> Polyphonic and also check <Complex> underneath it
- go to <Options>
<Tempo>
choose <Tempo Operations>
See screenshot to get started
- alternatively you can also edit the tempo curves with your mouse.
- You can now BIP this track and do whatever you want with it.
Trying to manipulate two different audio tracks with different tempo curves at the same time, needs a different approach and although possible, is very slow, complicated and therefore inefficient in Logic.
Have a nice day!

Adobe 3.0.1 BUGFIX PATCH is released

Okay, something that a lot of you have waited for for quite a while, and some simply didn't believe would ever happen...
You can get it
here. Quite a lot of small things have been attended to, and quite a few of us haven't managed to crash it at all, despite trying quite hard!
Additional information from forum host:-
Download size is less than 14MB - it's not anything like the size of the original program download.
In case you missed the link in SteveG's post, it's as follows -
http://www.adobe.com/support/downloads/product.jsp?product=92&platform=Windows
The changes in Adobe Audition 3.0.1 are as follows:
Spectral tools no longer crash machines with more than four CPU cores.
The Graphic Phase Shifter effect has been reenabled.
Performance while recording MIDI data has been improved.
The Sequencer will now record MIDI data even if the panel is closed.
Adobe Audition will now launch on Windows Vista® systems where the My Documents folder was moved from the default location.
The application will now ignore Windows "Locale" settings to format decimal data in comma-delimited XML settings files.
A Healing Brush crash issue has been addressed.
Crossfades are no longer incorrectly added to grouped clips when overlapped with non-grouped clips.
Invalid crossfades will no longer be added to the end of a previously trimmed clip after enabling or disabling looping.
Invalid crossfades for clips after enabling non-session tempo-based looping have been addressed.
Dragging crossfaded clips onto the master track no longer creates two additional tracks and an error in the crossfades.
Inserting MIDI from the Files panel would cause the application to hang in Edit mode for an audio file whose sample rate didn't match the session.
Several scenarios where crossfade changes could corrupt a session were addressed.
Closing a session without exiting the rewire app no longer causes Adobe Audition to save a blank session.
Undo no longer becomes disabled after undoing the creation of unique copies of two crossfaded clips.
Crossfaded clips no longer disappear after undoing move clips.
Canceling VST scan no longer causes Adobe Audition to become unstable.
If a selection existed, a full session mixdown would only process MIDI data through the end of the selection.
The Open MIDI dialog box was not completely modal and could cause a crash.
MIDI Host had problems with some Spectrasonics VSTi instruments, where it wouldn't show the entire UI.
CD burning would sometimes create a corrupted disk but still report a successful burn.
Applying the Clip/Pop Eliminator no longer crashes the application.
Crash recovery is now more reliable when using Auto-Save For Recovery.
When the application detects the possible saving failure that causes a corrupted session, a warning dialog box now appears so users can retry the save.
Transport controls are no longer disabled if a new session is opened without closing the existing session.
Crossfades will now retain their original shape when clips are moved and the session is reopened.

Apparently the changes in Adobe Audition 3.0.1 are as follows:
Spectral tools no longer crash machines with more than four CPU cores.
The Graphic Phase Shifter effect has been reenabled.
Performance while recording MIDI data has been improved.
The Sequencer will now record MIDI data even if the panel is closed.
Adobe Audition will now launch on Windows Vista® systems where the My Documents folder was moved from the default location.
The application will now ignore Windows "Locale" settings to format decimal data in comma-delimited XML settings files.
A Healing Brush crash issue has been addressed.
Crossfades are no longer incorrectly added to grouped clips when overlapped with non-grouped clips.
Invalid crossfades will no longer be added to the end of a previously trimmed clip after enabling or disabling looping.
Invalid crossfades for clips after enabling non-session tempo-based looping have been addressed.
Dragging crossfaded clips onto the master track no longer creates two additional tracks and an error in the crossfades.
Inserting MIDI from the Files panel would cause the application to hang in Edit mode for an audio file whose sample rate didn't match the session.
Several scenarios where crossfade changes could corrupt a session were addressed.
Closing a session without exiting the rewire app no longer causes Adobe Audition to save a blank session.
Undo no longer becomes disabled after undoing the creation of unique copies of two crossfaded clips.
Crossfaded clips no longer disappear after undoing move clips.
Canceling VST scan no longer causes Adobe Audition to become unstable.
If a selection existed, a full session mixdown would only process MIDI data through the end of the selection.
The Open MIDI dialog box was not completely modal and could cause a crash.
MIDI Host had problems with some Spectrasonics VSTi instruments, where it wouldn't show the entire UI.
CD burning would sometimes create a corrupted disk but still report a successful burn.
Applying the Clip/Pop Eliminator no longer crashes the application.
Crash recovery is now more reliable when using Auto-Save For Recovery.
When the application detects the possible saving failure that causes a corrupted session, a warning dialog box now appears so users can retry the save.
Transport controls are no longer disabled if a new session is opened without closing the existing session.
Crossfades will now retain their original shape when clips are moved and the session is reopened.

Adobe Audition CS6 (5.0.1) update patch released

UPDATE: A new 5.0.1 update build has been made available as of July 20, 2012, due to an issue discovered in the Dynamics Processing effect. If you previously updated Adobe Audition CS6, please visit the links below and install the new update. This update is not available via Adobe Update Manager and must be downloaded via the website.
Today we released an update to address several bugs in Audition CS6. Many were minor workflow issues, but a few could cause Audition to crash under certain circumstances.
Download the patch installer directly from:
Windows: http://www.adobe.com/support/downloads/detail.jsp?ftpID=5419
Mac: http://www.adobe.com/support/downloads/detail.jsp?ftpID=5418
bugs fixed in Adobe Audition CS6 5.0.1 update:
APE files with metadata inserted by other editors cause Audition to crash (Windows)
If previous session directory no longer exists, Audition leaves the Folder Location field empty
Multitrack fades no longer respect the fade type preference. (Worked in CS5.5)
Audition may crash when users choose to create unique copies of selected MT regions
Playback stutters when creating a unique copy of a clip while right-click dragging
Channel Mix settings not honored on export when not exposed in dialog
EUCON Soft Key set contains keys that do nothing
Session Tempo broken on systems using commas instead of decimal points
Bounce to New Track > Selected Track bounces AFTER passing through track output
If a favorite was recorded on subset of channels, the favorite will fail if those channels are disabled
Sending a stereo bus side-chained to a mono track may crash the application
UAD-2 plug-ins missing from Windows Effects menu
Audition may crash on launch when CoolType encounters certain installed fonts (Mac)

I'm really happy to see this update out, but I haven't been able to install it on my Mac yet.
The Updates item in the help menu is greyed out for me. When I try running the installer from the direct download it says 'Updates have been suppressed by your administrator.'
I can't imagine that I would have disabled updates.
Any advice?
Joseph

What is in the Audition 3.0.1 bugfix?

Changes in Adobe Audition 3.0.1:
• Spectral tools no longer crash machines with more than four CPU cores.
• The Graphic Phase Shifter effect has been re-enabled.
• Performance while recording MIDI data has been improved.
• The Sequencer will now record MIDI data even if the panel is closed.
• Adobe Audition will now launch on Windows Vista® systems where the My Documents folder was moved from the default location.
• The application will now ignore Windows "Locale" settings to format decimal data in comma-delimited XML settings files.
• A Healing Brush crash issue has been addressed.
• Cross-fades are no longer incorrectly added to grouped clips when overlapped with non-grouped clips.
• Invalid cross-fades will no longer be added to the end of a previously trimmed clip after enabling or disabling looping.
• Invalid cross-fades for clips after enabling non-session tempo-based looping have been addressed.
• Dragging cross-faded clips onto the master track no longer creates two additional tracks and an error in the cross-fades.
• Inserting MIDI from the Files panel would cause the application to hang in Edit mode for an audio file whose sample rate didn't match the session.
• Several scenarios where cross-fade changes could corrupt a session were addressed.
• Closing a session without exiting the rewire app no longer causes Adobe Audition to save a blank session.
• Undo no longer becomes disabled after undoing the creation of unique copies of two cross-faded clips.
• Cross-faded clips no longer disappear after undoing move clips.
• Cancelling VST scan no longer causes Adobe Audition to become unstable.
• If a selection existed, a full session mixdown would only process MIDI data through the end of the selection.
• The Open MIDI dialog box was not completely modal and could cause a crash.
• MIDI Host had problems with some Spectrasonics VSTi instruments, where it wouldn't show the entire UI.
• CD burning would sometimes create a corrupted disk but still report a successful burn.
• Applying the Clip/Pop Eliminator no longer crashes the application.
• Crash recovery is now more reliable when using Auto-Save For Recovery.
• When the application detects the possible saving failure that causes a corrupted session, a warning dialog box now appears so users can retry the save.
• Transport controls are no longer disabled if a new session is opened without closing the existing session.
• Cross-fades will now retain their original shape when clips are moved and the session is reopened.

All of the available updates for Audition 3, including the 3.0.1 bugfix, are available from here.

Volume Adjustment per Instrument

I am working on some music in Audition, and what I really need to know is if there is a way to speed up or slow down a piece during specific parts of a piece without changing the overall speed. Gradually, of course. Instantaneously is not very good music-wise.
I also want to know how to adjust the volume of individual instruments (gradually as well) during individual parts of the song without adjusting the entirety of the instruments' volume through the piece.
Thanks in advance, guys
=)

There is no really good way to change tempos. I have created a session at one tempo, rendered or exported a mix down then import that to a new session at a different tempo. I have also set markers at my differing tempo positions and time stretched or shrank the clips between those markers to fit the new tempo. There is no dedicated session tempo lane or tempo markers as in Reaper, Cubase, Studio One, ect.
As for the volume try opening up the volume envelope. You can directly add nodes to the envelope for volume evolutions. Or look in the manual for Automating track settings. That will give you a really good idea of all the different track automations, besides volume.
Duff

My option-scissor function isn't working!

When I use the command to slice the region at equal subdivions, it doesn't work Instead, it slices normally (one slice) even though the little plus sign by the scissor still shows.
Any idea why this might be? I haven't updated anything except QT and iTunes lately.

Okay, it's because the audio file had its anchor point set at the end of the file. It was a reverse cymbal that I use in a template. I keep the anchor point at the end so that the file always climaxes at the beginning of a beat, regardless of the session tempo. I had forgotten that.

Updating playhead in Pro Tools (slave) from Logic (master) using MTC.

Hey there,
I have setup MIDI over LAN using the Audio MIDI Setup between two Macs and it works so far as when I hit play in Logic the Film in my Pro Tools picture machine seems to be in sync with the music coming from Logic. Questions:
1) When nudging the playhead in Logic left and right the corresponding timecode changes are not updated on the Pro Tools machine until you hit play again in Logic. Is there any way Pro Tools can update it's play head, timecode values and picture as I nudge the Logic playhead without pressing play again? It would be great to nudge the Logic session by one frame and see the update in Pro Tools accordingly.
2) When I hit play to stop the music in Logic the time code readings are not the same in each DAW how can this be remedied so that they are? Is something going wrong here? e.g. stopped @ 01:00:03:04 in Logic and Pro Tools reads 01:00:03:09.
Using Pro Tools 9.05, Logic Studio 9.1.8 (64-bit).
Thank you!
Ben

Ok after more testing I have managed to get this working using a direct midi connection between the 003 and the laptop (using a Edirol UM1 and the 003). Here is what I did.
ProTools8LE as master running on MacPro:
1. Setup->Session
1a. Set the session start time to 00:00:00:00
1b. Time code rate =25
2. Setup->Peripherals
2a. Synchronization - MTC reader Port: Digi 003, Port 1
MTC Generator Port: Digi 003, Port 1
3. Set session tempo (eg: 120bpm)
4. Transport- hit the arrow on the right hand side of the transport window and select "Synchronization" then hit the GEN MTC button
LOGIC slave running on Laptop.
1. Connect MIDI i/o interface to ports on 003
2. Set session tempo to match that in PT (120bpm)
3. Settings->Synchronization
Sync mode = MTC
Auto Enable External Sync = yes
Frame Rate = 25 (same as protools)
Auto detect format of MTC = yes
Bar position 1111 plays at SMPTE 00:00:00:00 (this matches the setting in PT)
Thats it. This setup appears to be working on my rig. I still haven't got this to work over Network midi, and I still haven't got PT8LE and Logic 8 to work together on the same machine. Let me know how you go.

LDAP Userid not present in Backend System

We are trying to implement a scenario where the user are present in LDAP but are not present in the backend system "ECC".
Case Scenario: User log into portal using "testid" and want to access the BSP view which pull up the information from the backend system. Now this "testid" is not present in ecc system so i am looking for solution to achieve this scenario where "testid" will be able to pull the information without being created in ECC system.
This is required for our external customer which we donot want to setup in ecc system.
Any suggestion or if some one has implemented this scenario and can share how they did it will be really appreciated

Hi,
1.) Licensing. Noteably the first aspect that would come from SAP themselves will be licensing. You still need to be transparent about licensing with SAP in your scenario.
2.) Traceability. If any breaches are made or if any issues occur in yoru backend system, you will need to determine the exact time and it may be that the issue was invoked by several users acting on the system at the same time.
3.) Locking/Synch and Session Terminations. If mulitple users (using the same backend ID) perform update tasks on the database you may find that they will incur locking issues from trying to update the same record. Synchronous jobs may also result in issues similarly when invoked by different users on the same ID. Session management on the backend systems (dependant on the application) may also result in situations where multiple users may be limited to the max number of concurrent connections under their ID or sessions be "locked" as a result of terminations on the client side - which would require to be cleaned up from time to time.
While the above are some of the aspects that can be encountered, SAP generally handles these situations rather well, yet from a system managnment perspective you will encounter them from time to time.
PS: Depending on how you map users - individual mapping can become cumbersome particularly if mappings need to change etc. You can also map at a group level. This will make your life easy particularly say for vendors who have several employees yet need to map to one ECC ID to transact - just create a group per vendor assign the users to the group and map the group to the ID.
You can also us mass upload to map users efficiently - see:
http://help.sap.com/saphelp_nw72/helpdata/en/48/a96f43db653206e10000000a42189c/frameset.htm
https://cw.sdn.sap.com/cw/docs/DOC-107900
example:
[User]
uid=user0002
Last_Name=Johnson
$usermapping$:BCE:user=ext_user0002
$usermapping$:BCE:mappedpassword=initial1

Logic Pro 7 : how do we coexist with PC DAW's?

I am an independent Mixing engineer using Logic Pro 7, I have just got a gig to do mixdown and mastering work for a producer. However, I use Logic and he uses sonar and samplitude.
Can anyone point me in the right direction on how to convert projects from sonar and samplitude 8 to use within logic pro 7?
G5 Mac OS X (10.4.4)

Have them export the session to AAF (I like embedded). Make sure Logic's Tempo is set to the session tempo BEFORE you import the AAF file. If there are lots of tempo changes export a midi note from the original session. Import the midi session first, then the AAF.
P.S. I've had a few weird bugs from importing midi directly to my Logic sessions. Nothing debilitation, but I've gotten into the habit of import midi into a separate new session then copying the data from one Logic session to the other.

Recreatable Bug in Audition 3

Hello all, I believe I have found a re-createable bug in AA3 and here is how you can create it.
Load up a session, and on one of the tracks select all the clips.
Now, right click a clip and select "clip envelopes > pan > use splines". So now you have set the clip pan envelopes (NOT the volume envelopes but the PAN envelopes) to use splines.
Now play back your Multitrack session and within the clips you have set to use splines, keep creating new enveloping points and adjust these envelope points just before the cursor while the cursor is playing and moving toward the envelope points...adjust envelopes just before the cursor gets there and eventually Audition will stop functioning and you will get the message
"Microsoft Visual C++ Runtime Library
(X) Runtime Error!
C:\ProgramFiles\Adobe\AdobeAudition 3.0\Audition.exe
R6025 Pure Virtual Function Call"
It also happens (although not nearly as often) when I'm adjusting the "pan splines" whilst Audition is not playing the session, and is completely stopped.
This is the first real "bug" I have encountered, has anyone else had the same experience or are you able to re-create it? You have to play with the splines from anywhere from 10 seconds to a minute and eventually with repeated changes in the pan and the addition of more envelope points it will crash.
Just wondering if anyone else has experienced this, or if you can re-create it in 3.0.1, which I have yet to upgrade to because my friend did and he has now encountered bugs that were not in the original 3.0, can anyone confirm this bug and/or whether it's been fixed in 3.0.1?
My system has been so stable otherwise I don't want to touch it, even with this re-createable bug, after it crashed if I "control+s" and save the results, it doesn't save the session permanently, but when I choose "continue session" in the post-crash dialog box, it returns my clips with the spline envelopes set just as they were just prior to the crash.

Mark Branch wrote:
Could you possibly direct me to a list of what 3.0.1 corrects?
I can do slightly better than that - I'll post it here:
Changes in Adobe Audition 3.0.1:
• Spectral tools no longer crash machines with more than four CPU cores.
• The Graphic Phase Shifter effect has been reenabled.
• Performance while recording MIDI data has been improved.
• The Sequencer will now record MIDI data even if the panel is closed.
• Adobe Audition will now launch on Windows Vista® systems where the My Documents folder was moved from the default location.
• The application will now ignore Windows "Locale" settings to format decimal data in comma-delimited XML settings files.
• A Healing Brush crash issue has been addressed.
• Crossfades are no longer incorrectly added to grouped clips when overlapped with non-grouped clips.
• Invalid crossfades will no longer be added to the end of a previously trimmed clip after enabling or disabling looping.
• Invalid crossfades for clips after enabling non-session tempo-based looping have been addressed.
• Dragging crossfaded clips onto the master track no longer creates two additional tracks and an error in the crossfades.
• Inserting MIDI from the Files panel would cause the application to hang in Edit mode for an audio file whose sample rate didn't match the session.
• Several scenarios where crossfade changes could corrupt a session were addressed.
• Closing a session without exiting the rewire app no longer causes Adobe Audition to save a blank session.
• Undo no longer becomes disabled after undoing the creation of unique copies of two crossfaded clips.
• Crossfaded clips no longer disappear after undoing move clips.
• Canceling VST scan no longer causes Adobe Audition to become unstable.
• If a selection existed, a full session mixdown would only process MIDI data through the end of the selection.
• The Open MIDI dialog box was not completely modal and could cause a crash.
• MIDI Host had problems with some Spectrasonics VSTi instruments, where it wouldn't show the entire UI.
• CD burning would sometimes create a corrupted disk but still report a successful burn.
• Applying the Clip/Pop Eliminator no longer crashes the application.
• Crash recovery is now more reliable when using Auto-Save For Recovery.
• When the application detects the possible saving failure that causes a corrupted session, a warning dialog box now appears so users can retry the save.
• Transport controls are no longer disabled if a new session is opened without closing the existing session.
• Crossfades will now retain their original shape when clips are moved and the session is reopened.
Please note the one I bolded, and the one underneath. I also strongly suspect that this is only the list of tangible things - there have been quite a few changes 'under the hood' to make all this possible, and this has definitely been more stable than the original version - I had healing brush crashes before, and not a single one since. I'm not aware of a single report from anybody that this bugfix release has made anything worse or more unstable at all, and most reports of crashes have more to do with people's unstable OS installs than anything else, and they certainly don't relate to the bugfix, whatever you may have heard.

Anyone got Pro Tools 8 and Logic 8 to sync together?

Hi all - I have read the forums over at DUC (digidesign) regarding syncing Logic and PT via IAC on the same machine and via Network Midi or via midi ports on a 003. I have been unable to slave Logic to Protools 8 both on the same machine (using IAC) or running Logic 8 from a laptop connected via Network Midi, or via the midi ports on a 003.
The threads on this (working) seem to reflect the use of Pro tools 7.4.2 and earlier, not Pro Tools 8. I am looking for any user who has managed to get Pro Tools 8 and Logic 8 to sync together (either on separate machines, or the same machine). If so, I would appreciate a step by step on what you have done to achieve sync between the two programs, since I have now exhausted all of the solutions posted over at DUC.
I am running PT8 LE with a 003 on a MacPro Quad, and Logic 8 on a Macbook Pro. Thanks in advance.

Ok after more testing I have managed to get this working using a direct midi connection between the 003 and the laptop (using a Edirol UM1 and the 003). Here is what I did.
ProTools8LE as master running on MacPro:
1. Setup->Session
1a. Set the session start time to 00:00:00:00
1b. Time code rate =25
2. Setup->Peripherals
2a. Synchronization - MTC reader Port: Digi 003, Port 1
MTC Generator Port: Digi 003, Port 1
3. Set session tempo (eg: 120bpm)
4. Transport- hit the arrow on the right hand side of the transport window and select "Synchronization" then hit the GEN MTC button
LOGIC slave running on Laptop.
1. Connect MIDI i/o interface to ports on 003
2. Set session tempo to match that in PT (120bpm)
3. Settings->Synchronization
Sync mode = MTC
Auto Enable External Sync = yes
Frame Rate = 25 (same as protools)
Auto detect format of MTC = yes
Bar position 1111 plays at SMPTE 00:00:00:00 (this matches the setting in PT)
Thats it. This setup appears to be working on my rig. I still haven't got this to work over Network midi, and I still haven't got PT8LE and Logic 8 to work together on the same machine. Let me know how you go.

3rd Party AIFF loops tempo changes from loop library and Logic session

Hi there,
Hope somebody out there can help me out!
I've recently purchased some 3rd party loops, some in AIFF and some in WAV (Which I have converted to AIFF using the Apple Loops Utility), and i have been able to get these into the logic Loop library successfully.....Or so I thought!
The problem I am having is that when previewing one of my loops it's often double the speed that the set tempo, and this will happen to ALL of my loops. But when I drag one into my session, Logic asks if it should copy over the automation data with it, click yes, and it plays fine in the arrange window. And funnily enough, all of my loops in the library start playing at the correct tempo!
Once this has all happened, i've tried quitting logic, and re-opening....but the issue just happens again....
Has anyone else had this problem, or have any idea as to what the issue may be??
Any help would be greatly appreciated!!
- Aaron

Hi there,
Hope somebody out there can help me out!
I've recently purchased some 3rd party loops, some in AIFF and some in WAV (Which I have converted to AIFF using the Apple Loops Utility), and i have been able to get these into the logic Loop library successfully.....Or so I thought!
The problem I am having is that when previewing one of my loops it's often double the speed that the set tempo, and this will happen to ALL of my loops. But when I drag one into my session, Logic asks if it should copy over the automation data with it, click yes, and it plays fine in the arrange window. And funnily enough, all of my loops in the library start playing at the correct tempo!
Once this has all happened, i've tried quitting logic, and re-opening....but the issue just happens again....
Has anyone else had this problem, or have any idea as to what the issue may be??
Any help would be greatly appreciated!!
- Aaron

HT1349 Why do i keep getting the following message when trying to sync my ipod to my itunes? The ipod could not be synched because the sync session failed to start....

Everytime I try to sync my iPod Touch with updated music from my iTunes library, I get the following error message: The iPod could not be synched because the sync session failed to start.
Please help!

Hello easbda,
Thank you for providing the details of the calendar issue you are experiencing with your iPhone. I recommend following the steps in the section titled "Troubleshooting on Microsoft Windows (Microsoft Outlook)" in the following article to assist with syncing your calendar events between your devices:
iCloud: Troubleshooting iCloud Calendar
http://support.apple.com/kb/ts3999
Thank you for using Apple Support Communities.
Best,
Sheila M.

When synching my 4th gen ipod touch I get error msg saying ipod could not be backed up because session could not be started with the ipod. It only does synch steps 2-5. Do I have to restore it?

When synching by 4th gen ipod touch it skips the first step - backup-, does steps 2 through 5, then I get a message the ipod could not be backed up because a session could not be started with the ipod. How do I fix this? Do I have to restore my ipod? Will all my apps be erased?

You have to have an internet connection, either wireless or through a computer with iTunes. When you choose Software Update you can only update to the latest version for your iPod Touch, iOS 6.1.6

Synching to session tempo

Similar Messages

Maybe you are looking for