That's what it offers as a minimum on my Mac. Obviously this is for single plugins, I like latency as low as possible when playing, for actual playback of projects it doesn't matter if it's higher.Jim Roseberry wrote:Agreed that the driver quality makes a HUGE difference.aMUSEd wrote:Even USB 2 RME interfaces can go just as low, my Fireface UC can manage 32 samples easily for non cpu demanding plugins like Sunrizer, and 64 for most of the rest (I usually need more for granular plugins but low latency doesn't matter as much for them anyway). If I'm playing my Virus Ti, which is a zero cpu hit plugin, I can go down to 16 samples. The quality of the drivers makes a huge difference.
RME units are exceptional.
My only question is how are you getting RME USB units to go down to 32-sample and 16-sample ASIO buffer size?
The Fireface UFX offers a 48-sample buffer size as minimum.
NEW Studio One v3 updates incoming.
-
- KVRAF
- 37412 posts since 14 Sep, 2002 from In teh net
-
- KVRian
- 888 posts since 9 May, 2005
At this point in time... I'd say running at a 16-sample ASIO buffer size is not practical for most users. What I like about it is (essentially) no software imposed limitation. Let the hardware determine what it can sustain. Ultimately, the hardware will grow into it becoming practical.LawrenceF wrote:Given that, what's the likelyhood of most systems running 1ms or less "true" round trip? I know many or most converters these days are pretty low latency wise but is 1ms round trip (literally speaking) something that is a reasonable expectation? What's the typical latency of converters these days?Jim Roseberry wrote:Round-trip latency is the sum of the following:
- ASIO input buffer
- ASIO output buffer
- Driver's safety-buffer (usually hidden)
- A/D D/A
(just asking the tech-wise guys here like Jim, not suggesting anything either way)
Running at a 32-sample ASIO buffer size (with fast well-optimized machine) is practical for many folks (especially prior to mixing).
With the UFX, I mostly run at 48-samples... then bump up to 64-samples if necessary.
Rarely do I need to go above 64-samples.
-
- KVRian
- 888 posts since 9 May, 2005
OSX allows for smaller buffers...aMUSEd wrote: That's what it offers as a minimum on my Mac. Obviously this is for single plugins, I like latency as low as possible when playing, for actual playback of projects it doesn't matter if it's higher.
Spend nearly all my time under Windows.
-
- Banned
- 5357 posts since 7 May, 2015
Ok, gonna say it.
Why are we talking about this crap in 2016?
Buy this time we SHOULD be running with 1ms in/out and able to have as many plugs as possible. They should generally work, there shouldn't be the tude of the "well I don't use that even though it's a feature so don't understand why you care" nonsense.
Christ, you could easily spend enough to send your kid through college at a decent place on this crap* and have a shitload of issues that are NOT user fault with compatibility, stability and "A"bility.
FFS!
*Oh, I did that. Oh well, glad I found reason.
Why are we talking about this crap in 2016?
Buy this time we SHOULD be running with 1ms in/out and able to have as many plugs as possible. They should generally work, there shouldn't be the tude of the "well I don't use that even though it's a feature so don't understand why you care" nonsense.
Christ, you could easily spend enough to send your kid through college at a decent place on this crap* and have a shitload of issues that are NOT user fault with compatibility, stability and "A"bility.
FFS!
*Oh, I did that. Oh well, glad I found reason.
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- KVRAF
- 16977 posts since 23 Jun, 2010 from north of London ON
incubus wrote:Ok, gonna say it.
Why are we talking about this crap in 2016?
Buy this time we SHOULD be running with 1ms in/out and able to have as many plugs as possible. They should generally work, there shouldn't be the tude of the "well I don't use that even though it's a feature so don't understand why you care" nonsense.
Christ, you could easily spend enough to send your kid through college at a decent place on this crap* and have a shitload of issues that are NOT user fault with compatibility, stability and "A"bility.
FFS!
*Oh, I did that. Oh well, glad I found reason.
Barry
If a billion people believe a stupid thing it is still a stupid thing
If a billion people believe a stupid thing it is still a stupid thing
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- KVRist
- 436 posts since 7 Apr, 2010
Theo, what do you mean by S1 being flat out broken? I use S1 pro V2 and I find it a lot more usable and stable than Bitwig on my PC (Windows 7). Since I have no frame of reference what are you comparing S1 to when you say it's broken?TheoM wrote:... S1 is *flat out* broken performance wise, you are right. And even if one major platform is broken, that's enough to be asking about a potential fix.
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- KVRAF
- 3959 posts since 10 Sep, 2010 from A shit hole (Ireland).
I dunno'... Studio 1 (V3) runs pretty well on my Mac. I've had no major issues with it while writing or finishing tracks. However, 2.5 was a disaster until they came out with a fix.TheoM wrote:[
Performance of S1 on mac is indeed broken. to give a rough guide, imagine that in some cases there are effects i can get 50 instances of in logic and 2 in S1.. that's how big the difference can be. It's pretty darn bad.
What FX are you talking about here. I'd like to have a go on my machine and see if I can replicate it.
I moved from Logic (9) to Studio One V2, and I've no regrets. Primarily because I will go back to using a PC in the future. Not because I don't like Macs, but I can get certain software that is not available on a mac - Like 3ds Max, etc.
I prefer S1, over Logic but that's just a personal preference. I do like Ableton as well (with V9).
I will take the Lord's name in vain, whenever I want. Hail Satan! And his little goblins too.
-
- KVRist
- 436 posts since 7 Apr, 2010
TheoM wrote:kev2525 wrote:Theo, what do you mean by S1 being flat out broken? I use S1 pro V2 and I find it a lot more usable and stable than Bitwig on my PC (Windows 7). Since I have no frame of reference what are you comparing S1 to when you say it's broken?TheoM wrote:... S1 is *flat out* broken performance wise, you are right. And even if one major platform is broken, that's enough to be asking about a potential fix.
as the poster i was quoting said, we were talking about S1 V3 on *mac* only.. we specifically said PC version great.
Performance of S1 on mac is indeed broken. to give a rough guide, imagine that in some cases there are effects i can get 50 instances of in logic and 2 in S1.. that's how big the difference can be. It's pretty darn bad.
If they fix that, and work around osx's inherent audio performance problems like DP, PT, Logic, Cubase8, Nuendo do.. then it will be a much better experience. so just to word it correctly, "S1 V3's performance on OSX is flat out broken".
Sorry about that
Ah, ok...thanks for clearing that up. I have found S1 to be really solid on PC and the mac issues sound like a proper mess.
-
- KVRist
- 467 posts since 24 Oct, 2003 from Adelaide
"Raising the Bar" image on the latest email .... wishful thinking but some form of vertical scrolling?
KVR - the many headed beast.
-
- KVRAF
- 1991 posts since 12 Mar, 2004
Reaper OSX two examples, the media browser only supports a single column on OSX , no matter the width, theming does not always remember set sizes, there are plenty of other OSX only issues.TheoM wrote:bungle wrote:The GUI does not need fixing ? If you mean you do not like the GUI then say so, do not call things fixes if you just dont like them (Personally i think it is the first full time usable GUI for S1)TheoM wrote:i wonder if they are going to fix the gui and performance.. that could be a big change, as well as making a bunch of midi improvements.
At least very curious to hear the announcement.
The performance does not really need fixing, OSX version needs fixing, performance on Windows, while not as good as something like Reaper, is however within usable ratios, OSX version is just broken full stop (But so is Maschine OSX, Reaper OSX and i suspect a few others on OSX)
Since when is Reaper OSX performance broken? It seems fine in the demo here. S1 is *flat out* broken performance wise, you are right. And even if one major platform is broken, that's enough to be asking about a potential fix. As far as the GUI, all i meant was if they would allow a bit more customisation other than just colour, for example contrast between elements, so people could make more diverse skins that really help the workflow. Yes this is more of a personal pet peeve, sorry about that, cause i find the gui overwhelmingly busy and i can't tell what parts or tracks are selected at a glance, like i can in cubase and logic. PS i'd be curious to know more about maschine in osx being broken, can you share any links?
Maschine in OSX, the list here is so long its ridiculous, lets just do two that make it unusable for serious users, no memory of default folders (yes the beta testers missed this haha) no way to change drag n drop output format, always 32bit floating, if your other software doesnt support it, no drag n drop (again, really, beta testers ? )
Duh
-
- KVRian
- 1158 posts since 6 Jan, 2015 from London, England
No, they just moved the timeline further up the screenpapawillow wrote:"Raising the Bar" image on the latest email .... wishful thinking but some form of vertical scrolling?