Studio One 3?

[LawrenceF]

Yes but then when you drag clips it won't snap to grid.

Yeah. That's what on and off switches do, turn things on and off.

Is there even such a thing as an audio editor whose range selection drawing doesn't actually snap when snap is turned on?

[EvilDragon]

Where's NRPN, SysEx, MIDI event list?

[LawrenceF]

Delay Compensation for Automation would be welcomed in such a revolutionary DAW with automation out of time, though it's only a few samples out of time, but it builds up and screws your mixes.

I agree that the automation in S1 is not sample accurate in some cases, I have tested it. I also think "sample accuracy" is something people stress over far too often. There certainly are times when sample accuracy is more important. Those times are not nearly as widespread as people seem to think.

I've done ton of mixes in S1 (and I use tons of automation) and I don't personally think it has screwed any of them, mmv on that. I don't sweat the small stuff, I only mostly worry about what comes out of the speakers.

It's one thing to test a workstation out of curiosity. It's quite another to accurately assess the practical impact of various tests. Modern daw users seem to obsess over everything but the really, really important stuff.

It will be 2015 and S1 will be on version 5 and someone will still be posting that video. While others are making albums in it.

[LawrenceF]

Where's NRPN, SysEx, MIDI event list?

Non existent?

I don't personally care much about the first two but a midi event list would be a nice add indeed. Some of the filtering you'd get with a list (CC's) is already there on the "CC Bar" but a list would allow better note filtering and all that so yeah, it needs one.

As far as I can tell, Maik (pronounced "Mike" I think) does most of the midi in S1. He's probably a very, very busy guy... like Schwa over at Reaperland.

[nIGhT-SoN]

Yes but then when you drag clips it won't snap to grid.

Yeah. That's what on and off switches do, turn things on and off.

Is there even such a thing as an audio editor whose range selection drawing doesn't actually snap when snap is turned on?

Well in Cubase or Reason for example, you have snap on and the selection start point end end point are free, they don't snap on the grid.

LE: About the automation problem stated above, I don't actually look at what's doing, I'm listening. As long as it sounds good and I can do my work without problems, it doesn't bother me.

[ObsoleteAcc99]

[DELETED]

[ObsoleteAcc99]

[DELETED]

[ObsoleteAcc99]

[DELETED]

[LawrenceF]

I hear you loud and clear Theo.

Walking away from Cubase's 4-5+ or so discreet and task-focused midi editors was initially a very, very difficult thing to do. It was actually the main reason I went back and forth for awhile before making a final decision. Cubase's midi list editor in particular is - imo, mmv - pretty spectacular, a combination list + graphic key editor with exceptional filtering.

I eventually had to make a choice so I let them go for (hopefully) the short term. It took awhile but I'm pretty comfortable with that decision now.

[LawrenceF]

does this happen only when plugins with latency are being automated? Or on a mix that has plugins with latency somewhere in the chain at all? or on any mix, even with no latent plugins? Also, did you test it with rhythmic material, like using the square automation to do a chopper effect (just an example) to see if it matters in the context of a mix? Or have you only done non rhythmic critical automation. I guess i don't know what music you write hence asking

The testing I did was with all (or most) of those kinds of things, rendering automated things and comparing, viewing, nulling, etc, etc, and (on my system with my drivers at any latency it seems) the only thing I really found to be potentially occasionally problematic as a real practical matter was mute automation. Knowing that, knowing that some of my tests have revealed that to be (again, on my own system, mmv as usual) somewhat inaccurate, I always listen and review carefully when I draw in mute automation.

I've reported what I found a couple of times so I assume they're looking at it. The last time I tested it was in the early 2.x cycle. Haven't tested it lately. I can't even say for sure if it's happening for anyone else because I dont think any other user there chimed in on it when I reported it.

The other stuff is all irrelevant to me. If EQ automation is 10 samples early or late turning on or off or whatever.. that's not anything that would ever be an issue for me or even be detectable unless I born on Krypton.

Mute automation has to be pretty dead on though, or you'll often immediately hear it... if you mute at a zero crossing or something but the actual mute isn't dead on.

[Alfalfa]

Walking away from Cubase's 4-5+ or so discreet and task-focused midi editors was initially a very, very difficult thing to do.

I can't do it. Doesn't stop me from continually trying though.

I eventually had to make a choice so I let them go for (hopefully) the short term. It took awhile but I'm pretty comfortable with that decision now.

Hopefully for the short term. Some of the MIDI stuff that's been requested would make a transition to Studio One 3 a whole lot easier for me.

[Alfalfa]

God i just don't know how i could ever leave Logic. But i really am disliking apple so much beginning around the release of the new Imacs and failure to update mac pro, and the forced OS updates heading towards IOS toydom.

I went to the Apple store and the Microsoft store yesterday (both in the same mall). Row after row of portable devices in the Apple store. I had a Logic question. Nobody in the store knew the answer. Granted, at the nearby Microsoft store, nobody would even know about music production on a computer at all. It's hard to want to pursue Logic (currently trying it out) when I don't really like any of the hardware it normally runs on. The Microsoft store is such a cheap knock-off of the Apple store it's embarrassing (for Microsoft). I sympathize with your plight, because Logic has (roughly) a number of key requests I have for Cubase (or Studio One) -- best of both to some degree (but not so in some others).

[nIGhT-SoN]

Logic Pro is far from my taste. To me it looks like it need a lot of polish. When I try to resize midi notes in the pianoroll it's a nightmare, it doesn't move as it should, also, most of the time when I try to duplicate small audio parts like a kick, in the arrange window, I find myself timestreching it. For me it's kind of a nightmare, I have to zoom in so far that it makes hard to duplicate and time consuming. And when you think these are simple tasks that you use them everytime.

That's just my oppinion, I don't want to start a daw war or something like that.

[Alfalfa]

No, that's cool. I don't think your post was flame bait (and I certainly hope mine was not. I worried about that after I posted).

What I'd like most out of Logic is the per-clip looping. Studio One or Cubase -- somebody please implement!

I'm wondering if Studio One has spoiled me for any other interface.

[fluxmind]

does this happen only when plugins with latency are being automated? Or on a mix that has plugins with latency somewhere in the chain at all? or on any mix, even with no latent plugins?

It happens when you have a plugin inducing latency anywhere in your mix, it throws off all automation on all channels by some amount usually a few samples, the more plugins with latency you have in a mix, the more automation is out of time
So if you have something automated by ear and then you add some plugin with latency anywhere in a mix, it nudges your automation by few samples from where it suppose to be on all tracks.