sharke
Max Output Level: 0 dBFS
- Total Posts : 13933
- Joined: 2012/08/03 00:13:00
- Location: NYC
- Status: offline
Re: Why does Sonar's audio engine have such a big problem with looping?
2018/01/25 15:16:36
(permalink)
John
Its funny I never got out of the habit of stopping the transport before I do anything to a project. I do this with every DAW I have ever used. I would exempt automation. I have and do write automation while the project is playing back.
If I insert any plugin I always stop. Doing any routing I stop. Adding a track or bus I stop.
I also use freeze when I am done with editing a MIDI track and or a synth.
I have been known to mute tracks I no longer want in the mix.
The problem isn't really about turning things on and off during playback though. That was really just a side discussion about Sonar's engine. The problem is with looping.
JamesWindows 10, Sonar SPlat (64-bit), Intel i7-4930K, 32GB RAM, RME Babyface, AKAI MPK Mini, Roland A-800 Pro, Focusrite VRM Box, Komplete 10 Ultimate, 2012 American Telecaster!
|
marled
Max Output Level: -85 dBFS
- Total Posts : 251
- Joined: 2015/01/22 04:50:52
- Status: offline
Re: Why does Sonar's audio engine have such a big problem with looping?
2018/01/25 17:03:56
(permalink)
I've had also some out of sync issues with MIDI and synths in Sonar. But only if I was looping a section and changed the length of that section during play. When I stopped and restarted then there was no issue in my case.
I don't know if it helps you Sharke, but I can tell you that I always use the audio of synths for mixing. But in my workflow I have first a "synth" project for the song, then export the synths to audio files and mix in a NEW project. Like that I have almost no problems with Sonar, also with my computer's performance.
... many years before ...
|
amiller
Max Output Level: -73 dBFS
- Total Posts : 876
- Joined: 2006/01/28 19:54:49
- Status: offline
Re: Why does Sonar's audio engine have such a big problem with looping?
2018/01/25 17:10:49
(permalink)
I’ve had similar issues with looping. So far, it’s ALWAYS been a plug-in issue especially Izotope plug-in’s. To verify I simply toggle the “FX” button off. That has always immediately allowed looping to “work.” I then know I have a plug-in issue and I manually turn them off a class at a time to discover the culprit. Now that I think about it, Izotope plug’s have always been the guilty party.
This has been my experience.
RAWK!!! . SONAR Platinum: 2017.10
System specs: Purrrfect Audio: http://www.studiocat.com/open_cart/ • Case Silent Mid Tower • Power-Supply 600w quiet • Haswell CPU 4790k @ 4.4GHz • RAM 32GB DDR3/1600 • OS drive 1TB HD • Audio drive 2TB HD • Samples drive 1 3TB HD • Burner 24x DVD/RW • Video HD4600 • Add TI chipset Firewire For all others • Operating System Windows 10 x64 Home Edition . MOTU 828 mkII . Lucid 9624 A/D . Millennia HV-3b pre . Dual 24" Widescreen Monitors
|
sharke
Max Output Level: 0 dBFS
- Total Posts : 13933
- Joined: 2012/08/03 00:13:00
- Location: NYC
- Status: offline
Re: Why does Sonar's audio engine have such a big problem with looping?
2018/01/25 17:47:47
(permalink)
marled
I've had also some out of sync issues with MIDI and synths in Sonar. But only if I was looping a section and changed the length of that section during play. When I stopped and restarted then there was no issue in my case.
I don't know if it helps you Sharke, but I can tell you that I always use the audio of synths for mixing. But in my workflow I have first a "synth" project for the song, then export the synths to audio files and mix in a NEW project. Like that I have almost no problems with Sonar, also with my computer's performance.
Yeah I could do that, but of course it makes things difficult if you decide you need to tweak the synth later.
JamesWindows 10, Sonar SPlat (64-bit), Intel i7-4930K, 32GB RAM, RME Babyface, AKAI MPK Mini, Roland A-800 Pro, Focusrite VRM Box, Komplete 10 Ultimate, 2012 American Telecaster!
|
marled
Max Output Level: -85 dBFS
- Total Posts : 251
- Joined: 2015/01/22 04:50:52
- Status: offline
Re: Why does Sonar's audio engine have such a big problem with looping?
2018/01/25 19:49:43
(permalink)
sharke
marled
I've had also some out of sync issues with MIDI and synths in Sonar. But only if I was looping a section and changed the length of that section during play. When I stopped and restarted then there was no issue in my case.
I don't know if it helps you Sharke, but I can tell you that I always use the audio of synths for mixing. But in my workflow I have first a "synth" project for the song, then export the synths to audio files and mix in a NEW project. Like that I have almost no problems with Sonar, also with my computer's performance.
Yeah I could do that, but of course it makes things difficult if you decide you need to tweak the synth later.
I agree that there is little extra effort. But to reduce that, I export the audio files of the synths to my song audio folder and then reference them only in the 2nd project (no copy to Sonar project) and if I have to change the synth afterwards I just repeat the export and voila, the audio file is automatically the new one when I open the mixing project!
... many years before ...
|
tlw
Max Output Level: -49.5 dBFS
- Total Posts : 2567
- Joined: 2008/10/11 22:06:32
- Location: West Midlands, UK
- Status: offline
Re: Why does Sonar's audio engine have such a big problem with looping?
2018/01/25 19:51:54
(permalink)
msmcleod
The way I work around it is to always start projects on bar 3, using bar 1 & 2 for my count-in. I know I can set the metronome to count in 2 bars, but this way it any potential stuttering is gone before the actual music starts.
That’s not a bad policy in any DAW. It gives MIDI clock a bit of time to settle down and run steadily as well as things like PDC. I generally start around bar 9, that way I get plenty of time to send CC messages to synths as well.
Sonar Platinum 64bit, Windows 8.1 Pro 64bit, I7 3770K Ivybridge, 16GB Ram, Gigabyte Z77-D3H m/board, ATI 7750 graphics+ 1GB RAM, 2xIntel 520 series 220GB SSDs, 1 TB Samsung F3 + 1 TB WD HDDs, Seasonic fanless 460W psu, RME Fireface UFX, Focusrite Octopre. Assorted real synths, guitars, mandolins, diatonic accordions, percussion, fx and other stuff.
|
tlw
Max Output Level: -49.5 dBFS
- Total Posts : 2567
- Joined: 2008/10/11 22:06:32
- Location: West Midlands, UK
- Status: offline
Re: Why does Sonar's audio engine have such a big problem with looping?
2018/01/25 19:54:49
(permalink)
MagickT
I think that I have similar problems when connecting ableton to sonar via rewire. I create a simple loop in ableton drum rack such as 4x4 kick. And sonar chokes every time when I press play button at the loops start. When I try record it to audio in sonar (create audio track and route sound from instrument track with ableton to this audio track) I have similar thing: first kick of recorded loop is corrupt as if 2 DAW do not work synchronously and ableton starting first and sonar recording audio not from beginning.
The two DAWs have to sort out MIDI clock and other timing information before they will run in time with each other. Which takes a little time to happen. Trying to record from beat one of bar one is always a gamble, it might work or it might not. MIDI controlled synths have the same issue - it takes a little time for everything to get in sync.
Sonar Platinum 64bit, Windows 8.1 Pro 64bit, I7 3770K Ivybridge, 16GB Ram, Gigabyte Z77-D3H m/board, ATI 7750 graphics+ 1GB RAM, 2xIntel 520 series 220GB SSDs, 1 TB Samsung F3 + 1 TB WD HDDs, Seasonic fanless 460W psu, RME Fireface UFX, Focusrite Octopre. Assorted real synths, guitars, mandolins, diatonic accordions, percussion, fx and other stuff.
|