rbowser

amiller

---um, what?  A "scrub tool" is exactly that--You scrub the tool with your cursor/mouse.  It kind of loses its point if it continues to play...

Ahhh...you couldn't be more wrong.  If you've ever worked with Roland's VS2480 recorder you would know what I was talking about.  I want to be able to stop moving the mouse and still hear sound so that I can then very slowly move the mouse backward or forward to find the very very beginning of a piece of music...with my ears not my eyes...

Hi, Amiller - I'm sure you're describing a scrub behavior you'd like, but I'm not understanding - The example you gave is exactly the sort of thing you can do with a scrub tool which is precise, like the one we have.  You scrub back and forth, narrowing in on what you need to hear.  --If it kept playing, how would you know exactly what portion of the sound to work with--?-- In any case, scrub, she works for me the way it is.  Maybe I'd have to have the experience of working with a version that didn't scrub as I expect, and maybe I'd get it then.  But as it is, I come up short of imagining what you're describing as being an improvement.

It's like that with some features - Users have different expectations or needs, and I can imagine it would be difficult for programmers to decide what to do actually since there isn't a consensus about how a particular tool should operate.

RB

Yeah, it's kind of hard to explain unless you have experienced it.  I know how scrub works in SONAR but I also know how it works on Roland's VS2480.  The VS2480 scrub is more usable for me.
 
For example, lets say you an accidental but very small bit of noise at the beginning of a clip that you want to surgically remove.  Imagine moving your mouse cursor very slow just before the beginning of a clip.  Now, as you continue to move the mouse ever so slowly you begin to hear a faint whisper of the beginning of the actual clip.  If you stop at the point you can still hear the sound and you can very slowly, while still hearing the sound,  back off to the point that the sound just about disappears.  At that point you can set a marker and be confident that you are at the absolute very edge of the audible beginning of the clip.  Now you can slowly move the cursor over the beginning of the clip and you will hear the unwanted noise gradually get louder as it reaches it's peak.  As you continue to move the mouse you hear the noise gradually get quiter as you near the end of the unwanted noise until finally it's at a whisper.  At that point you can set another marker and then just snip the piece of unwanted noise right out of the clip without removing the "real" music.
 
With SONAR's scrub if you stop moving the mouse the sound stops.  At that point, how do you know if you stopped moving the mouse too soon, too late or did you get luck and stop it just right?

I would like to see the External Encoder Configuration Utility changed to allow a lot more data in the command-line (to allow more room for tags on mp3's). As it stands now, Sonar will only let a certain amount of data be processed from the command-line, and if the data is longer than the limit, it produces an error in the encoder.
 It would be awesome if this limit was removed.

Or native mp3 support like every other audio tool in the known universe? Just sayin'...

Or native mp3 support like every other audio tool in the known universe? Just sayin'... 



Except cubase
Edit: my bad Cubase does have mp3

A Mac version please
An adaption (rip) of NI's Kore for the included CW instruments, CakePlayer if you will. 
The option to run in 8.5 mode for certain tasks
+1 for the prochannel delay, fantastic idea =)

Oh, and per track/buss automation lanes.
Please...for the love of god!

chilldanny

An adaption (rip) of NI's Kore for the included CW instruments, CakePlayer if you will.

What? Did NI discontinue Kore??


Either way, Cake's Sound Center is actually quite similar to Kore in concept, assuming they expand it to start gobbling up other patch sounds as well.

That whole concept, an in-program metadata database, is something that every DAW needs to do its own way, and it needs to be done right in order for it to really be of value. I can see it being a giant PITA for the devz, but very useful for us grunts.

This is the kind of thing where a standard would be truly grand. Otherwise its gotta be TOTALLY user definable and I, for one, would never bother to tag everything properly.

Oh wait, nevermind, you meant "rip" as a verb, and not as R.I.P. Sorry for the confusion.

Would love to be able to setup a hardware synth (preconfigure the audio and midi tracks) as a simple instrument to be inserted like a vsti.

http://forum.cakewalk.com/tm.aspx?m=2286167

For Gods Sake Fix the TV and PRV separate snap settings i don't know what CW was thinking i really don't know.

ill cross my fingers