Stephen CarterApologies if I’ve missed any previous answer/s on same topic, have searched/read forum etc., but cannot find…
When playing back songs inside my DAW (Studio One Pro v3.5.6 Windows 10 Pro) the visual feedback i.e. cursor position is not in sync with the audio I’m listening to!
The cursor (both on the song track and/or the grid editor) is displaced from the audio by half a bar or so, which makes it very difficult to perform edits because the cursor is not on the note or block part that is sounding. The audio is synced fine.
I’m thinking that this might be a latency issue but Studio One (as I suspect most DAW’s) has latency compensation, this compensation however does not seem to extend to SD3 visuals.
Has anyone else experienced this, what is for me a serious issue and is there a fix?
Regards….
Windows 10 Pro/i7 6800k @3.4Ghz/16Gb ram. Studio One Pro, Melodyne Editor 4, Vocalign Project, Superior Drummer 3, Izotope N2-O8 and various other plugins. Focusrite Saffire Pro 40, Faderport, Focal Alpha 50's, Korg Pa3x, Korg Pad Kontrol, numerous guitars, basses & other antiquated outboard gear.
Apologies if I’ve missed any previous answer/s on same topic, have searched/read forum etc., but cannot find…
When playing back songs inside my DAW (Studio One Pro v3.5.6 Windows 10 Pro) the visual feedback i.e. cursor position is not in sync with the audio I’m listening to!
The cursor (both on the song track and/or the grid editor) is displaced from the audio by half a bar or so, which makes it very difficult to perform edits because the cursor is not on the note or block part that is sounding. The audio is synced fine.
I’m thinking that this might be a latency issue but Studio One (as I suspect most DAW’s) has latency compensation, this compensation however does not seem to extend to SD3 visuals.
Has anyone else experienced this, what is for me a serious issue and is there a fix?
Regards….
Windows 10 Pro/i7 6800k @3.4Ghz/16Gb ram. Studio One Pro, Melodyne Editor 4, Vocalign Project, Superior Drummer 3, Izotope N2-O8 and various other plugins. Focusrite Saffire Pro 40, Faderport, Focal Alpha 50's, Korg Pa3x, Korg Pad Kontrol, numerous guitars, basses & other antiquated outboard gear.
AlebluesmanHi,
I also am having the same problems as above with the cursor out of sync with play back and would be grateful for any answers. I should add that this problem wasn’t there from the start and I have created several projects without problems. It is only now after going back to make adjustments to a project that the problem has occurred. Any help appreciated.
Using Studio One 4, Mac Pro 16GB, RME babyface pro.
Henrik EkblomI also am having the same problems as above with the cursor out of sync
Henrik Ekblom - User Experience Designer
Toontrack
andy.BoultonHi I’m happy to hear that I’m not alone in this! I have exactly the same problem in Logic Pro X with a UA Apollo quad ai. I’ve tried everything buffer size, low latency mode, record arm the track and all current updates with no luck at all. Even when SD3 is running on its own with no 3rd party plugins in the chain. Oddly enough it doesn’t do it on every project I opened a project where the problem isn’t happening and copied every setting exactly as it was in the previous project. I also triple checked that every setting was identical and still there is a discrepancy between the visual display on SD3 and the audio.It’s driving me crazy is there any fix to this problem as it makes editing almost impossible and at the very time consuming.
Im running Logic Pro X 10.4.1 on a 27” late 2013 3.4Ghz intel core i5 16Gb 1600Mhz DDR3 ram with high Sierra 10.13.4
regards. Andy
Henrik EkblomOddly enough it doesn’t do it on every project I opened a project where the problem isn’t happening and copied every setting exactly as it was in the previous project.
Can the projects where you experience the issues contain high latency plugins? If you enable Low Latency Mode in Logic, does this help? You can access this by modifying the Logic tool bar, to show the Low Latency mode button.
Henrik Ekblom - User Experience Designer
Toontrack
andy.BoultonHi Henrik, thanks for your reply. Ok well I’ve finally found a work round to this annoying problem. Here’s what I found
1. Select low latency mode in the DAW
2. Select the track and hit record enable
voila! It’s in sync, the oddest thing is after you’ve added more audio tracks and your running multiple plugins on them it’s back in sync without having to record enable the midi track I’m using for SD3 and without using low latency mode?????? Figure that out?
hey ho it’s working and I can get back to creating music.
hope that this helps someone else who’s struggling with it.
2
Thanked by: 987baz and Henrik Ekblom
Henrik LassenHi.
I have the same problem concerning the cursor being 1/4 note ahead og the audio in the SD3 editor and makes it more or less useless!
It’s been a problem since 2017!
I am running the latest Logic Pro X.
Lowering buffersize, rec/ arm you name it , has been tried and nothing helps.
My MacBookPro is a 2018, 2,9 GHz and 16G ram. My SD3 is installed on a SSd running Thunderbolt 3.
Even running a small EZ Drummer setup inside SD3 is coursing the same problem.
Is there by any chance a solution on the way?? Its now more than 2 years since this problem was reported first time.
Regards
Henrik Lassen
JohnHi Henrik,
I’ve tried to reproduce in the same environment but I can’t.
Is it possible for you to ZIP archive a Project where this behavior is present and attach to a post here?
You do not need to included any Audio files.
BR,
John
John Rammelt - Toontrack
Technical Advisor
1
Thanked by: Henrik Lassen
Bear-Faced CowIf the cursor is showing ahead of Logic Pro X, then the problem is most likely to be in your delay compensation settings within logic, to which the setting governed by the presence or absence of latency inducing some plug-ins and is governed buy a present for absence of latency inducing plug-ins within your aux bus.
It’s not a set-and-forget type of setting. You are best to attach a key command to this so that you can toggle it when tracking and when mixing.
jord
Henrik LassenHey BFC.
that sounds likely.
But shouldnt SD3 adjust to the latency in the visual representation?
I will make a simple setup with no plugins and check it out.
thx!
Best wishes
Henrik
Bear-Faced CowLatency information is given for audio processing purposes as part of CoreAudio, and may not include all plug-ins, if not properly compensated for, such as in various buss and output channel setups, or may overcompensate for the same reason. Thus one of two things will happen:
I’ve witnessed this with more than just SD3 in all of my years of using Logic, even with the improvements to CoreAudio handling in Logic 8 (prior to this, even Logic’s visual cues were not immune to this). Only reason it appears to point the finger to SD3 is because of the presence of a timeline indicator in SD3.
jord
Stephen CarterAs the originator of this post it remains a frustration that no definitive solution has been found for this occurrence. However, like others on this forum I have found ways to reduce the sync problem, which is definitely due to latency issues between the DAW, in my case Studio One (now v4.6) and SD3 v3.1.5. If I initiate SD3 standalone or a new song and open the same SD3 song file, which is problematic in the main song, the sync issue is not irksome.
Why the out of sync issues between SD3 playhead and the DAW (which incorporates latency compensation) playhead arise I don’t know but dependent on the plugin latency, typically 150 – 350ms for modest song setups, it varies with the SD3 playback cursor/visual hit indication being ¼ to ½ of a beat ahead of the audio, on the Grid, Drums and Mixer views, making editing a real PITA to put it mildly!
Anyway – I’ve found that turning off all plugin inserts, then back on again maybe a few times, will often reset something in the latency discrepancy and bring the SD3 cursor back into a reasonable alignment with the song playback (discrepancies much smaller than a ⅛ beat out are difficult to detect but there is still some small mismatch there!) . One thing in Studio One that seems to exacerbate the problem is if the ‘Console Shaper’ is engaged as toggling this will toggle the sync issue between reasonable and well out, even though the latency reported for the SD3 VSTi remains the same, so I turn this off if I want to edit in SD3!
However, this is a workaround and I would (and others it seems) prefer that the SD3 playhead and the DAW playhead were in sync – AT ALL TIMES!
Regards and compliments of the season to all.
Windows 10 Pro/i7 6800k @3.4Ghz/16Gb ram. Studio One Pro, Melodyne Editor 4, Vocalign Project, Superior Drummer 3, Izotope N2-O8 and various other plugins. Focusrite Saffire Pro 40, Faderport, Focal Alpha 50's, Korg Pa3x, Korg Pad Kontrol, numerous guitars, basses & other antiquated outboard gear.
RobertHere is also the same Studio One sync problem still going strong… In Logic I need to use Low Latency mode to get everything in sync. Strange enough Cubase 10.5 is spot on, no delay visible, so it is possible. Please fix this… (MAC/Mojave everything latest updates)
RobrI’d love to concur that there are no issues in Cubase 10.5, but my recent purchase of SD3 v3.1.7 is experiencing a similar issue. This is not just a visual issue, but actually produces an offset from source sound (delayed hit) when replacing/reinforcing drum sounds. It’s also quite disheartening to find that this original post is still a problem one and half years later. This software cost me too much money to have something become next to useless
Kev777Just bought SD3 and have this same problem with Studio One 4.6
It’s directly related to the Total Plugin Delay in Studio One.
If I have no plugins, the grid editor cursor plays back in sync on the notes. If I add a high latency plugin, like Crave EQ in Linear Phase mode with 700ms of latency, the cursor in the grid editor is 700 ms ahead of the sound. The sound is in sync, the cursor is not. Take the plugin off and we’re back in snyc.
I don’t know if this something Toontrack can fix or if it’s on Presonus but that’s what is causing this….for me anyway.
Chris WilsonI have the same issue with SD3 and Digital Performer 9.52.
1
Thanked by: Henrik LassenNo products in the cart.