Punch in/out latency issue!

I'm having a pause in my audio when I punch in and out of logic. The song is still rolling but the music stops for a second. I know this is a simple hardware setting. I can't remember if it's the buffer size. Anyway, is there a standard buffer size, etc...?
Thanks!!

Enable "punch on the fly" in Options->Audio

Similar Messages

  • Latency issue Logic pro 9.1.3.

    Hey,
    At the same time as upgrading to Logic from Garageband
    I bought a Cakewalk Roland UA25EX ext usb soundcard because i was told
    i'd have latency issues if i used the caps lock keyboard for midi
    or direct input thru the input jack of
    my MacBookPro
    (5,3 Intel Core 2 Duo 2.8 GHz)
    Sometimes i use the caps lock keyboard to sketch in midi ideas and mostly it's ok.
    Other times it's delayed and there's no smile on my face.
    When recording with guitars/303/generators DI thru the soundcard
    I have latency issues that don't seem to be very regular.
    Sometimes it's worse than others.
    I make sure i have nothing else running on the computer,
    just Logic Pro 9.1.3, so it's not like i'm overloading macbrains.
    I have tried all the rebooting, i/o buffer size changing (down to 256), headfones from the mac output/headfones from the soundcard/ etc
    but still no luck.
    I can record with the low latency button on
    and it's kind of better, nearly, but that means i don't get to record with the effects on the channel strip
    that affects the recording/playing quite a lot, as i'm used to recording with effects/guitar amps if i go DI.
    This was the selling point - that i could record DI wthout disturbing Thee Neighbours.
    It seems to have gotten worse recently.
    I wonder if it's been corrupted somehow because it also has been acting funny when i bounce down -
    the play head is set to 1111 and i save - then in the bounce window
    the start position says a silly random number and it takes a few attempts of fiddly changes to get it to stay at 1111...frustration!
    Is there something i can do or is this normal? -
    it seems weird that a Pro app that cost me so much £s wouldn't work in a simple recording/bounce down set up?
    or has anyone else had this problem and fixed it?
    If i wipe Logic and install again would i have to go from my Logic Express and then up to my Logic Pro upgrade/extension again?
    Any pointers would be greatly appreciated.
    Thanks in advance

    Hey Fox,
    Thanks for that info -well umm, yes i installed the correct drivers.
    I use just the AU plugins or the basic logic ones on the channel strip
    but even when i was going in dry there was still a delay.
    I had experimented with the buffer size, as mentioned, but not gone down that low cus
    last time i tried that i had other strange things happen!
    But i will try again.
    Sample rate was at zero, btw. Always says zero.
    But today, when i just opened logic, the sample rate had changed. Strange. I need to understand this side of things so i'm gonna read up.
    Also, if plugins are involved, i installed some novation bass station and some freeware TAL bass synth
    stuff recently but don't have them up when i'm recording.
    Maybe they sit there quietly and interfere just by their facial expressions or sumthing!!
    I booted Mr MBP just now and i pulled out the USB and he's shining me a big ole red optical light
    out of his output jack!!
    In SysPrefs it has only optical digital as an output option.
    In the last few days as i was playing around trying to correct the latency issue i noticed that the output options had changed to the UA25 and the 'digital optical' options - rather than the UA25 and 'line out'.
    I'm off to go and read up on how to get my line out back, and try this buffer thing again.
    Thanks again
    Gravity

  • Video Latency Issue On The Mac Book Pro 2.4 With Leopard 10.5.5

    Gear: Macbook Pro (early 2008 model) - 2.4gigs cpu 2gigs ram - all the latest updates... no other applications running during the test
    Hi folks. Currently I am having a latency issue when trying to record directly into iMovie using the built-in microphone and iSight camera. Basically, the video seems 5 - 7 frames late to the audio. I found that a good way to demonstrate this issue was simply doing a few handclaps as a test.
    This is a quick handclap test displaying some video latency during recording with the iSight camera in iMovie 08.
    - Just download this link — and import it into iMovie 08 - Here is a link to a zip file that you can import into iMovie 08 - It's 2.5meg - .m4v export - Also it was recorded as standard format and audio midi setup app: audio was set to 44.1:
    http://www.brainbeast.com/37/clap-1-large.zip
    - Play from beginning. As soon as you hear a clap sound — pause with the space bar - then back up before the clap with the left arrows
    - Then click the right arrow several times until you hear the beginning of the clap sound ( This is the audio: start frame)
    - Now — you will notice the video still has an open hand. At this point click the right arrow, counting as you go several times until you see the hand close. This is the amount of frames that the video is late to the audio. For me it seems to be an average of about 5-7 frames late.
    Unfortunately iMovie 06 nor QuickTime will not scrub audio as you go frame by frame with the arrow keys so you cannot test it there. If you have some other application such as final cut Pro, you could test it with that.
    ! IF YOU WOULD LIKE TO PERFORM THE TEST YOURSELF:
    - Just record a new movie in iMovie 08 - using the built-in mic and i-Sight camera — and see if it is also slightly out of sync
    Note: to be as fair as possible — I did a slow handclap ( in order to not challenge the frame rates) - also, in order to get the maximum volume I used an open palm ( clap on the palms with your fingers spread out as you can see I did.)
    Please let me know if this latency appears to be the same for you as it does for me.
    Q: Is it just my machine or does it happen to you too?
    Q: Does anyone know a way around this latency issue?
    Q: Does anyone know if Apple is aware of this latency issue?

    I am experiencing the same incredibly frustrating problem as well. When I record directly into iMovie
    '08, the video lags the audio by a fraction of a second.
    I have tried shutting down all other applications and having only iMovie up. Same problem.
    I tried recording the video into QuickTime instead of iMovie and experienced the same problem. (Which makes me think it is perhaps a hardware or operating system issue.)
    I tried the technique suggested here and on other sites of "double-dragging" the clip from the Events pane into a project (one normal drag and one Shift+Cmd drag) so that I had the audio and video as two separate tracks. After muting the audio on the video track, I then attempted to slide the audio over to sync it with the video, but even down at the 1/2 second zoom setting I didn't seem to have enough granularity to move the audio so that it was exactly in sync with the video. I was wishing I could use the arrow keys or something like that to move the audio just one frame at a time.
    All I want to do is record a video directly into iMovie '08 - this would seem to be something trivial to do!

  • I am running on OSX 10.10.1 and have a 2009 imac intel and I am having severe latency issues.  I am not familiar with macs as this is my home computer used by other family members.  Any help on how to troubleshoot why such latency issues?

    I am running on OSX 10.10.1 and have a 2009 imac intel and I am having severe latency issues.  I am not familiar with macs as this is my home computer used by other family members.  Any help on how to troubleshoot why such latency issues?

    When you see a beachball cursor or the slowness is especially bad, note the exact time: hour, minute, second.  
    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad and start typing the name.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
    Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
    Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • What interface works best for GB? NO delay, latency issues please!!!

    What is the best way to record electric guitar or a microphone (for acoustic & vocals) into Garage Band? I tried plugging directly in to the mic input and selected low latency but there still is a bit of delay. I assume I need a USB or firewire interface. What are some good ones that are ultra portable? This is for the road. Thanks for reading.

    Zadamanim wrote:
    wouldnt getting a super CPU fix latency issues? even if it did have to be routed through a thousand places, a fast processor could get it done without latency issues, no?
    Yes and no!
    First, Garageband gives you limited ability to change the size of its buffer, which impacts latency. So even if your CPU were fast enough, I'm not sure if GB would allow you to dial down the buffer size in order to fully take advantage of it.
    Second, latency isn't only a function of CPU speed. There are other places where the audio can get bottlenecked as it makes its way in and out and through the computer. That's why some of the systems that market themselves as ultra-low latency for professional work use PCIe cards in order to shovel audio back and forth faster than is possible via USB or Firewire. For example, Apogee's Symphony System connects via a proprietary PCIe card in order to offer phenomenally low latency rivaling dedicated systems that use the computer only as a host (Garageband is a native system that uses the computer for everything).
    So while a fast CPU is at the heart of the latency issue, there are a number of surrounding issues that also influence it. The workaround of having an interface with its own routing system - so you can listen to your audio as you record before it has a chance to go through the computer and get delayed - is a cheap and elegant, if imperfect solution.

  • Dell 24" Latency Issues & Features?

    I have a Quad on the way, and I'm looking at LCD displays for it. I've been reading the postings about Dell's 24" LCD, which looks like a winner in most respects, but was wondering about the "latency issue" I've read about here and there regarding LCD use for Photoshop still work vs. Final Cut video work. Does anyone know anything about this "issue?" Or if it is an "issue?" So far, the Dell spanks the Apple 23" in most aspects, especially price.
    Are all of you Dell 24" owners happy with your purchase?
    Can an Eye-One calibrator calibrate this Dell?
    Are there any connection issues with the Dell for a Quad/Geo6600 OEM card?
    Thanks!!

    I know I can still read this forum post at 90° off center...there's some brightness change around 45° off center, and ever-so-slight contrast shift at around 70° off center, but colors on my desktop seem to be 'still there'. I can litterally put my head on the 'side' of the display, so 1 eye is looking almost at the back of the display and the other at the front, and I can still define objects, colors and shapes, and read the 12-point text on this page. I just gets out of focus real easy since it's almost 2 feet 'distance' for my eyes to re-focus between the 'left' and 'right' of the screen :-D
    The only complaint I do have of this monitor is that it's a 'bit' TOO bright, even set to the lowest brightness in the display's calibration. Although as LCDs get dimmer with age, I think it will work out in the long run...
    (I just bought it last week).

  • Help !!! LogicPro 9.1.8 Latency Issue on OSX 10.6.8 with Apogee Duet

    Help !!! LogicPro 9.1.8 shows 10.52 ms roundtrip latency with ApogeeDuet (FireWire) I/O Buffer size set to 128 samples ?!
    Also I have Low-Latency mode turned on when I track .... as checked above.
    Using a condensor mic (AT250), I am trying for days to track vocals and I swear I can ALWAYS 'feel' the latency creep in ....
    Can someone shine me a light pls, would be most kind of you...
    Thx in advance,
    Cheers,
    A

    Got that.. Thx.
    But... How do I feed any of  Logic's channel strip settings into my headphones while direct-monitoring off the Maestro Mixer ?
    Trust me, it really helps to bring out a great performance from a singer if they hear the vocals that are being tracked with a few effects like reverb n' echo in their headphones WHILE they sing/track the vocals.
    But what we want recorded is a dry signal, without any of the effects the singer is hearing on his/her headphones while they sing.
    Now when I was working exclusively on Garageband, I could do this pretty easy. There weren't any latency issues too till my hard-drive bloated and OSX got sluggish.
    Since a clean install and the move to Logic, it's been a mess really. I can't seem to get my way round this yet.
    I always have Maestro open btw... In the mixer, the 'From Software' and 'To Hardware' faders are set to 0dB each. And Input 1, where my mic goes, is at 0dB too.
    Where do we go now ?

  • Help needed on Fixing replication latency issues

    Hi Team,
    Good day!!!
    I am new to replication setup and I am working on the issues with replication latency.
    Can you please provide us your experience and expertise on fixing and troubleshooting replication issues.
    Below are some queries on that,
    1) How to check the replication errors?
    2) how to find out the replication latency?
    3) What are the steps to fix the replication latency?
    4) how to teoubleshoot the issues coming on replication latency?
    Awaiting your valuable response and replies.
    Thanks in advance,
    Sarvan.N

    Hi Sarvan,
    Firstly, usually, we check replication errors via the Replication Monitor or by viewing replication agent job history. Besides the two methods, we can also check replication errors from the SQL Server error log and so on. For more details,
    please review this
    article.
    Secondly, based on my research, the latency issues always occur in Transactional Replication.  We can check that if there are latency issues by using Replication Monitor as well as Transact-SQL commands. Below is an example that posts a tracer token
    record and uses the returned ID of the posted tracer token to view latency information. Refer to :
    Measure Latency and Validate Connections for Transactional Replication.
    DECLARE @publication AS sysname;
    DECLARE @tokenID AS int;
    SET @publication = N'AdvWorksProductTran';
    USE [AdventureWorks2012]
    -- Insert a new tracer token in the publication database.
    EXEC sys.sp_posttracertoken
    @publication = @publication,
    @tracer_token_id = @tokenID OUTPUT;
    SELECT 'The ID of the new tracer token is ''' +
    CONVERT(varchar,@tokenID) + '''.'
    GO
    -- Wait 10 seconds for the token to make it to the Subscriber.
    WAITFOR DELAY '00:00:10';
    GO
    -- Get latency information for the last inserted token.
    DECLARE @publication AS sysname;
    DECLARE @tokenID AS int;
    SET @publication = N'AdvWorksProductTran';
    CREATE TABLE #tokens (tracer_id int, publisher_commit datetime)
    -- Return tracer token information to a temp table.
    INSERT #tokens (tracer_id, publisher_commit)
    EXEC sys.sp_helptracertokens @publication = @publication;
    SET @tokenID = (SELECT TOP 1 tracer_id FROM #tokens
    ORDER BY publisher_commit DESC)
    DROP TABLE #tokens
    -- Get history for the tracer token.
    EXEC sys.sp_helptracertokenhistory
    @publication = @publication,
    @tracer_id = @tokenID;
    GO
    Thirdly, transactional replication latency issues could be caused by many factors, such as network traffic or bandwidth constraints, transactional load on the publisher, system resources, blocking/locking issues and so on. I recommend you troubleshoot latency
    issues referring to the following blog.
    http://blogs.msdn.com/b/repltalk/archive/2010/02/21/transactional-replication-conversations.aspx
    Thanks,
    Lydia Zhang

  • DPC Latency issue, need to update BIOS?

    I'm into recording music and latency is of great importance. I did a DPC latency check and noticed I was getting some major peaks, constantly. I tried everything, removing sound card, disabling drivers, etc, etc and nothing works. Then I did a google search and found this: https://forum-en.msi.com/index.php?topic=125206.0
    I have...
    Model name: 7519 v1.0
    M/B ERP Version: 06
    I have NEVER flashed BIOS before and have no idea how to do it. I don't even have a floppy drive. I really need to fix this latency issue though, otherwise I will have to buy a new computer :(
    Can someone help me? I sent en inquiry to the support, but did not get a reply.
    Thank you.

    Quote from: Jack on 29-March-11, 00:00:44
    What is the model name of your mainboard?  There are many MS-7519 mainboards with different PCB and ERP numbers (your ERP number is incomplete, there must be three digits):
    http://eu.msi.com/service/search/?kw=7519&type=product
    The best way to approach this, is to check your current BIOS Version as displayed on the P.O.S.T. Status Screen:
    Write down the full BIOS ID String as it appears in the red box in the example picture.  When we know the BIOS Version, it is possible to check whether or not there is Latency Fix for your board out there or not.
    Have a look here and make yourself familiar with our MSI HQ Forum USB Flashing Tool:  >>Use the MSI HQ Forum USB flasher<<.

  • AA3 Rewire latency issues...

    Why is it when I Re-Wire AA3 with anything, Reason4 for example, when I load redrum there will be a 50 msec delay or so when i hit the pads before I hear it. Im tired of this. The reason I use AA3 with beat production is for recording samples, guitar, etc on top of whatever midi is in Reason. Plus, I like to mix in Adobe. Well, I LOVE Reasons mixer but I hate Fruity Loops and when I use that I like to use Adobes mixer. But whats up with this latency? This hasnt always been a problem and I cant think back to when it first started. It worked fine when I used my Fast Track Pro to record, now in addition I have a Fast Track Ultra8r that is used most of the time and ive never had any latency issues in adobe itself or reason by itself on this computer.
    Is aa3 really that much of a resource hog? Anyone else have the same problem or any ideas?? I cant play keyboard when i hear the sound 2 secs after i hit a chord it reaallly messes with my ears and throws me off beat. It would be cool if this happened during post production where I could just up my sample rate. but its happening while recording.

    Most obvious to try first is to try changing the I/O buffer size - go into the Audio/MIDI Setup (Applications>Utilities>AudioMIDI setup) and adjust there. Generally speaking you're looking for the lowest value you can get away with before you start to experience digital distortion and drop-outs. I think the default setting is 512 samples - you should be able to reduce it quite a bit depending on your computer's processing power. Hope that helps.

  • New iMAC giving huge latency issues.

    HI everybody,
    Im new to these forums as I have just recently purchased an iMAC, 3.06Ghz, with 6 GB of RAM for my studio.
    Before this I was running an INtel based pC with Pentium processor, which worked as fairly well and absolutely without any latency issues.
    Here's the problem:
    i hooked up a MAckie ONYX 1640 mixer with Firewire I/O into the iMac and setting anywhere between 64 samples to 128 samples shows me theoretical latency of between 5 to 8 Ms, which is alright, I used to work with similar settings on the OC and it is hardly percievable. The problem is , the Latency sounds much higher!!
    Its definitely not 8 Ms. and with lower buffer sizes, obviously the audio starts clicking and popping.
    I then hooked the iMac with my Presonus Firebox which iv used smoothly with the PC for three years, without ever having latency issues...but this time too, the IMAC is adding latency and audi coming back from the DAW is very percievably late. Definitely around 25-30 Ms at such low buffer sizes!
    Can someone help me out here, in case there s any optimisation to be done for the mac to make audio its top priority etc, and to better performance?
    Highly appreciated!
    Much thanks
    Gucci
    www.myspace.com/headroomdelhi

    Headroomdelhi wrote:
    So basically,
    I am software monitoring, with just one micropohone, with a powerful Mac with 6 GB to spare.. and yet im getting a huge delay!
    You poor boy!
    Apparently you had some unrealistic expectations.
    Many
    plugins
    just NEED
    a lot of
    latency
    to calculate the processing to the sound. In fact, there is a rough law stating that you can't have top sonic quality and NO latency using software only, especially mastering compressors and reverbs.
    You could try the *Low latency mode* button, it also immediately shows you which plugins have a significant latency, as they will be bypassed in LLM.
    This is especially true for 'high end' plugins like Space Designer, AdLimiter, Multipressor and a whole load of others. If you need reverb on voice just to have a 'moral support' when recording, choose a 'simpler' reverb, or, better even, use direct monitoring and a HARDWARE reverb that only adds reverb to the monitoring path.
    Plugins are meant more for mixing than for tracking.

  • Time Capsule stuck at Preparing for Backup, and internet TC latency issue

    I have an iMac that backs up to my 1TB Time Capsule. I have had it since March. Suddenly it stopped backing up. It get's stuck at "preparing for backup" and never actually completes a backup.
    I am also experiencing a HUGE latency issue with my internet connection. I am constantly having to use the 'refresh' page button in Safari.
    help....

    TB,
    *_Time Machine May Report "Preparing..." For a Long Time_*
    Consider these factors regarding an extended period of "Preparing...". Consider each topic separately and do not attempt to act on all of them at once.
    *Recent Crash or Other Major System Event* (Deep Traversal)
    The reasons for this process are described in an article by George Schreyer. “During the preparation step it checks the FSEvents log for consistency. If it determines that something isn't quite right it has to rescan the whole disk. This can take quite awhile. A full rescan is always triggered by a crash, an unplanned shut down event or by booting from some other bootable disk between backups…. After a crash, Time Machine must scan the whole disk to determine what it has to do because it cannot trust the information that it left behind. Connected via an Ethernet connection, this phase would typically take 20 minutes on an older PowerBook. Being connected wirelessly stretches this phase out to over 3 hours.” [http://www.girr.org/mac_stuff/backups.html]
    According to the following KB article it can sometimes take a very long time if Time Machine begins this “deep traversal” and has to compare data inventories. This may apply to your situation, particularly if many Gigs of data are involved. (http://support.apple.com/kb/TS1516)
    *Anti-Virus Software*
    Running anti-virus software can interfere with the backup process. Either disable it altogether, or try the suggestion outlined here, “If you use third-party anti-virus scanning software and have issues, make sure your Time Machine back up folder (Backups.backupdb on the Time Machine disk) is excluded from virus scanning.” (http://support.apple.com/kb/TS1516)
    *Software Updates* #
    Installing new software, upgrading existing software, or updating Mac OS X system software can create major changes in the structure of your Macs directories. Time Machine will backup every file that has changed since the installation.
    If you take a look at the Console logs Time Machine may be reporting that your backups need "deep traversal". That's fine. Time Machine knows what is wrong and how to fix it. If you have a great deal of data, it may take quite awhile.
    After an OS update (like 10.5.5) Time Machine realizes the system no longer matches what it looked like during the previous backup. So it has determined that it's earlier catalogue of what-should-be-where is 'untrustable'. So it is going to go item-by-item comparing the before and after of your system. If you have just performed an OS Update then Time Machine knows what it's doing - let it do it!
    *Spotlight Keeps Indexing Backup Drive* #
    It may be that Time Machine can’t proceed or complete a backup due to a Spotlight indexing error. During this period, take a look at the Spotlight icon in the upper right corner of your screen. Is there a tiny dot pulsating in the center of the spyglass? Click on the icon. Is there a progress bar displayed? Generally Spotlight indexing is a good thing. But at time it may hang and never progress, preventing backups from taking place.
    Go to System Prefs --> Spotlight --> Privacy Tab.
    Drag your Time Machine disk into the window. It should now be among the items to exclude from indexing.
    Now quit System Prefs.
    Reopen System Prefs and remove ("-") the Time Machine disk from the window.
    This should clear out Spotlights cache. Naturally, Spotlight should begin indexing again (maybe even for a few hours depending on how much data there is), but it should eventually stop.
    *Reboot Time Capsule* #
    Stop the backup from the Time Machine menu.
    When the Time Machine icon stops spinning, unplug the TC from the wall outlet.
    Wait 10-15 seconds.
    Re-plug it in again.
    After it has restarted (30-60 seconds), attempt another backup.
    Time Machine will report “Preparing…” again, but it shouldn’t be lasting more than a couple of hours.
    Let us know if any of the suggestions above helped in your case.
    Cheers!

  • Consistent Latency Issue since upgrading to 75/25

    A couple months back I upgraded to 75/25 on my account, ever since when playing one of my games I get massive amounts of packetloss on the very first hop right after the Verizon hops. Sometimes it is a little, under 4% and playable, most times though it is well past 10-15%, even as high as 50% and I just can't do anything, even connect. The trace is below.
    Tracing Zone: SSCE Hockey/Football Zone IP Address: 208.122.59.226
    Hop IP Address Host Name Loss(%) Min/Avg/Max Ping
    1 192.168.1.1 Wireless_Broadband_Router.home 0.0 0 0 10
    2 x.x.x.x L100.BFLONY-VFTTP-06.verizon-gni 0.0 0 0 100
    3 130.81.216.8 G0-0-5-2.BFLONY-LCR-21.verizon-g 0.0 0 0 20
    4 130.81.209.8 xe-4-1-6-0.NWRK-BB-RTR1.verizon- 0.2 10 20 130
    5 130.81.23.184 xe-1-0-2-0.NY5030-BB-RTR1.verizo 0.2 10 20 70
    6 152.63.10.57 0.xe-6-1-1.XT1.NYC4.ALTER.NET 37.7 10 30 90
    7 152.63.22.225 GigabitEthernet6-0-0.GW18.NYC4.A 0.0 10 40 80
    8 65.217.199.202 internap-gw.customer.alter.net 0.2 20 30 230
    9 216.52.95.4 border3.po1-20g-bbnet1.nym008.pn 0.0 10 30 210
    10 63.251.26.2 inapvoxcust-8.border3.nym008.pna 0.0 10 30 70
    11 208.122.44.201 0.ae59.tsr1.lga3.us.voxel.net 0.0 10 30 240
    12 173.231.161.2 4000.te1-49.esr2.ldj1.us.voxel.n 1.1 20 40 90
    13 173.231.134.186 <unknown> 0.0 10 40 80
    14 208.122.59.226 zone.rshl.org 0.0 10 40 100
    Cycles: 339
    As you can see, I let it run a few minutes. The game has a built in trace program. The 6th hop, very first after Verizon, has 37% packetloss. I'm guessing this is a major hop somewhere and something I have no control over. I've tried restarting after doing a dhcp release and it normally doesn't work.
    thanks

    Alter.net is the old UUNet/MCI Backbone that Verizon currently owns. So, your packet loss issue is found right there on the Verizon backbone. The question now is, are you only seeing latency and packet loss to that router or does it continue onward on a consistent basis? It's fine if a single router drops packets since they can be set to do that, but it's not OK if it is going from one router and continuing to the end
    To rule out any issues with FiOS in the Buffalo area, here's a WinMTR AND a Traceroute to that server from my DSL connection which has some light web browsing and some games running on it.
    Tracing route to zone.rshl.org [208.122.59.226]
    over a maximum of 30 hops:
    1 <1 ms <1 ms <1 ms 192.168.3.1
    2 7 ms 6 ms 7 ms 10.41.15.1
    3 6 ms 6 ms 7 ms P1-0.BFLONY-LCR-02.verizon-gni.net [130.81.195.222]
    4 20 ms 19 ms 21 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
    5 20 ms 20 ms 19 ms 0.so-6-0-3.XT2.NYC4.ALTER.NET [152.63.10.25]
    6 20 ms 19 ms 21 ms GigabitEthernet7-0-0.GW18.NYC4.ALTER.NET [152.63.22.229]
    7 21 ms 19 ms 19 ms internap-gw.customer.alter.net [65.217.199.202]
    8 21 ms 20 ms 20 ms border3.po1-20g-bbnet1.nym008.pnap.net [216.52.95.4]
    9 36 ms 47 ms 36 ms inapvoxcust-8.border3.nym008.pnap.net [63.251.26.2]
    10 20 ms 19 ms 19 ms 0.ae59.tsr1.lga3.us.voxel.net [208.122.44.201]
    11 23 ms 23 ms 20 ms 4000.te1-49.esr2.ldj1.us.voxel.net [173.231.161.2]
    12 21 ms 21 ms 21 ms 173.231.134.186
    13 20 ms 65 ms 22 ms zone.rshl.org [208.122.59.226]
    Trace complete.
    WinMTR Statistics
    WinMTR statistics
    Host
    Sent
    Recv
    Best
    Avrg
    Wrst
    Last
    192.168.3.1
    0
    535
    535
    0
    0
    1
    1
    10.41.15.1
    0
    543
    543
    7
    9
    67
    7
    P1-0.BFLONY-LCR-02.verizon-gni.net
    0
    543
    543
    7
    8
    55
    7
    so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net
    0
    543
    543
    18
    25
    133
    19
    0.so-6-0-3.XT2.NYC4.ALTER.NET
    14
    358
    311
    26
    43
    150
    31
    GigabitEthernet7-0-0.GW18.NYC4.ALTER.NET
    1
    537
    536
    46
    60
    114
    64
    internap-gw.customer.alter.net
    1
    535
    533
    18
    23
    218
    20
    border3.po1-20g-bbnet1.nym008.pnap.net
    0
    543
    543
    19
    25
    202
    20
    inapvoxcust-8.border3.nym008.pnap.net
    0
    542
    542
    25
    46
    84
    30
    0.ae59.tsr1.lga3.us.voxel.net
    2
    501
    491
    58
    67
    259
    61
    4000.te1-49.esr2.ldj1.us.voxel.net
    0
    541
    541
    26
    45
    87
    26
    173.231.134.186
    0
    543
    543
    19
    21
    79
    20
    zone.rshl.org
    1
    533
    531
    19
    40
    105
    42
    So yeah, there is certainly some loss with that router but it's hard to say for sure if that router is problematic. The two hops in PNAP are not losing data so it suggests that things may be fine but the alter.net router may be under a good amount of load. They have been problematic like that since Sandy though!
    ========
    The first to bring me 1Gbps Fiber for $30/m wins!

  • Ping/latency issues.

    I've recently had my line upgraded from a 500k to a 2500k ip profile, and for a short period of time it worked great, consistent speeds etc. Roughly a week ago my ip profile was lowered to 2000k, at which point I suffered frequent broadband connection drop out, phone call after phone call ensued and now my improved ip profile has returned however I am receiving in excess of 300ms ping (according to several different online testers) which has rendered almost every online application useless. Any ideas?
    P.S I recently had an engineer to run teests on the line and he reported no faults, I don't understand the problem.

    chris6273 wrote:
    Hmm i've never made anything worse (as far as ping/latency) issues are concerned by restarting my router (Even though I get a 15ms ping so I wouldn't know). The only thing (which I know of) that will be disrupted by restarting your router is the DLM but that shouldn't do anything over 1 restart.
    A hub reset will also force dynamic IP setting from the RAS, most if not all ping issues are to do with which RAS you are connected to, and the traffic on the backhaul.
    High latency can be experienced at level 32 interleave, noticeable especially on gaming.
    Dynamic Line Management runs constantly and only changes the connection if it is "flapping"...
    A re-sync makes no changes to line configuration, other than to sync at the highest possible rate for the line condition.

  • Bus latency issue

    I am sure there is a simple solution to this ... I haven't found it on my searches yet.
    In Logic 7.2 I am routing BFD auxiliaries to one bus and running some overall compression and eq. Now I have latency on the bus and it is lagging behind the rest of the tracks. What can I do to compensate and pull it back up to speed with the other tracks?

    I am sorry no one has seen fit to help you with this problem however help is at hand please take time to read this very carefully. I believe this is your answer you seek, The reason I have gone into such depth is simple so that you will have a grounded understanding of how logic address the problem and also what plugs in Logic have Latency within them by default. Well here goes
    Logic Pro 7.1: Full Plug-in Delay Compensation can cause late recordings and increased latency
    In Logic Pro 7.1, if you set Plug-in Delay Compensation to All, any new tracks you record will be late and out of sync with previously recorded tracks. You may also experience increased latency when playing Audio Instruments live. Here are some concepts behind the issue and tips for resolving it.
    About full delay compensation
    One of the new features in Logic Pro 7.1 is full delay compensation across busses, aux channels, and outputs. This means you can place plug-ins that normally induce latency on busses, auxes, or outputs, and the audio routed through these plug-ins will be in sync with everything. Logic achieves this by calculating the amount of delay caused by plug-ins assigned to a bus, aux, or output, and delaying the streams sent to other busses, auxes, or outputs by an appropriate amount to line everything up. This ensures that all tracks will be synced to sample-accuracy.
    Example scenario
    To give you a better understanding of what's going on here, let's say you have a simple song with a few drum, bass, guitar, and vocal tracks. All the drum tracks are routed to a bus with several plug-ins inserted that together induce 500 ms of latency. The vocals are routed through another bus that has a set of plug-ins that induce 250 ms of latency, and the bass and guitar tracks are routed straight to the main outputs without going through any latency-creating plug-ins. If latency were not corrected, then the bass and guitar tracks would play 500 ms in front of the drums. The vocals would be 250 ms in front of the drums but 250 ms behind the guitar and bass.
    With full delay compensation engaged, Logic Pro will delay the streams sent to the outputs for guitar and bass playback by 500 ms to line them up with the drums, and will also delay the bus the vocals are streamed to by 250 ms to line them up with the drums and guitars. The precise calculations are handled for each stream automatically. During playback and mixing, the delay created to compensate for plug-in latency is imperceptible, but it can cause problems if you do any tracking after turning on full plug-in delay compensation. These recordings will be late because of the delay that Logic imposes to compensate for latency. The degree of lateness will vary, depending on which plug-ins are in the signal chain.
    Eliminating latency
    There are several ways to deal with these latency issues. The best way is to simply avoid setting up any signal routing that involves using plug-ins that create latency on busses, auxes, or outputs until you are done tracking. Once you start mixing, go ahead and set up any routing you like, including setting Plug-in Delay Compensation to "All."
    If you can't avoid recording tracks after setting up such a routing scheme, then bypass any plug-ins you have on busses, auxes, or outputs that create latency, and change your delay compensation setting from "All" to "Audio tracks and instruments" while you are recording. You can quickly bypass plug-ins by Option-clicking on their inserts in the Track Mixer. You can toggle the Plug-in Delay Compensation setting by choosing Logic Pro > Preferences > Audio > General, or by setting up a key command for "Plug-In Delay Compensation: All." This key command will toggle the delay compensation setting between "All" and "Audio tracks and instruments." When you finish recording, re-enable the plug-ins on the busses and toggle the delay compensation setting back to "All."
    Note: Bypassing plug-ins on Outputs will not eliminate the latency that they create. To eliminate it, you must remove these plug-ins entirely from the Output's insert slots.
    If you are recording audio, another strategy would be to choose Audio > Audio Hardware & Drivers, then disable Software Monitoring. You would then need to monitor your recording via an external hardware mixer, or third party software mixing application that may be provided with your audio interface. When Logic is not providing software monitoring of incoming audio, then it can correctly position audio recordings even when full delay compensation is enabled. It is important to note that this technique will not help with recording Audio Instruments.
    For the same reasons as described above, you may get increased latency when playing Audio Instrument tracks live if the delay compensation is set to All. As with recording audio tracks, try to complete any Audio Instrument recording for a song before turning on the full delay compensation. If you find it necessary to add a new audio instrument recording after setting up a signal routing that involves latency-causing plug-ins on busses, auxes, or outputs, then follow the same advice stated above for adding recorded audio. You may also notice that the meters on busses, auxes, or outputs that have delay-compensated plug-ins will not be in sync with the tracks that are routed through them—however, the audio will be sample-accurate. Additionally, the Song Position Line's visible position will not be compensated. Unless you are using an exceptionally large set of delay-compensated plug-ins, this should not be particularly noticeable.
    Another effect with delay compensation set to All is that MIDI tracks triggering external sound modules will be out of sync. This is because Logic has no direct control over the audio output of external devices. A possible solution for this would be to route the audio outputs from the external MIDI devices to inputs on your audio hardware and monitor them through Logic. This way, the audio streams from the MIDI devices can be compensated during playback. Using Logic's External instrument to route MIDI to your external devices is an ideal way to work in this situation.
    Here is a list of Logic plug-ins that cause latency:
    Adaptive Limiter
    Limiter
    Multipressor
    Noise Gate
    Silver Gate
    Linear Phase EQ
    Match EQ
    EnVerb
    Space Designer
    Denoiser
    Pitch Correction
    Pitch Shifter II
    Vocal Transformer
    Some third-party Audio Unit plug-ins may also cause latency—refer to the user guide for the respective products to see about this. All plug-ins that run from DSP cards such as the PowerCore or UAD card have inherent latency. Logic Pro compensates for the latency of any of these third party plug-ins, but as with Logic's own plug-ins, avoid assigning those that exhibit latency to busses, auxes or outputs until you are finished with tracking.
    You may also find that simply bypassing plug-ins that run from DSP cards will not be sufficient to correct the latency they induce. If you are using these plug-ins, there are a couple of ways to deal with this. One would be to remove the plug-in entirely while you are recording tracks, and then re-insert them when you're done recording. Be sure to save your settings for each of these as a preset first, so that you can recover the appropriate settings when you re-insert them. Taking this idea a bit further, you could save the entire channel strip setting for each bus, aux or output that uses plug-ins that cause latency and then easily reassign everything for each channel in one go.
    I hope you will get something useful from this good luck

Maybe you are looking for