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?

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

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 =)

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.

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

i want a transport module that i can put where ever i want.on a track...in the corner..upside down..anywhere except that big bulky controlbar with everything in it..actually...i like the control bar..i just want to have a transport control to be a seperate module.so it doesnt block the whole veiw.when i want to lay it next to where im working..and i know what your thinking..i can always use the shortcuts..not like the transport can.

I'd love to see the pro-channel removed and make each of the elements a VST instead.  This way I have control over how I want to use them.  As an example, if I want to include a tape simulator between the compressor and the EQ, I could.

I do like the pro-channel.  I think they did a good job with it and I would like to use it with my other plugs, but I can see times where I'd like to put other FXs between.

Tom

1. Fully baked!!! I don't like meat uncooked and I don't like software half baked either.
2. Either separate FREEZE Synth - just the synth frozen and Freeze Track - freeze the audio and FX, or the ability to use Pro-channel on frozen tracks the way we have been able to re-enable and use sonitus EQ on frozen synth tracks in 8.53.  Synths are frozen during tracking to save RAM.  ( 6 broadway big band horns use 6 gigs of RAM just for the attacks) For some time now, we've been able to have all synths frozen first, then come back to mix and enable the EQ....  That's gone as of X1B! So now were supposed to bus all those tracks, or copy the audio to new audio tracks.  Phewy on you!
3. Metronome to work properly when clicking around the timeline when snap is off.
4. Higher midi resolution.
5. Metronome to be changed to eighth notes, 16ths, dotted 16ths, etc.
6. Metronome to be bouncable, freezable... (still might want to add pro channel to metronome after freeze though...)
7. Animated conductor window for following and animated conductor (mickey mouse, old dude, robot, Blogman...)
8. Recordable tap tempo for conducting the tempo with the space bar ( like finale, or like I do with my Wii-mote and Glove pie and my own personal tap tempo preset in Bome's midi translator)  Then we need nodes to be lassoable and movable like the midi control data.
9. 64 bit of Perfect Space and all other non 32 bit plugs...
10. the ability to create and use midi timers and translators within midi tracks such as with Bome's to be able to process midi translations offline in the fast bounces.  (Or maybe help Bome's be a fast bouncing midi plug in.
11. Midi notes to NOT drop out when using midi Quantize on a state of the art computer with the midi buffers as high as they go, running no audio fx at all.
12. STABILITY< STABILITY<STABILITY!!! Wait till next March if you have to..... Consumer needs to be able to trust the product out of the box.

---Blogman

1. well cakes midi has come a long way since ver 5 so i'd personally like to see the Staff View/Notation guys get there due. (theyve been asking for years now).

2. i'd like to see DP get updated to a multiout synth since its 4 part multitimbral (and any other included cake synth thats falls in this category). DP really needs this.

3. my last request is that the quick fix program remains a part of the cake philosophy forever! i didnt **** in the forums about X1 but i was here everyday watching and honestly i almost gave up on it. X1 kept quitting on me in front of my clients and it was hella embarrassing. everyone who knows me know i swear by Sonar but i almost through in the towel. i love the quick fix program and now X1 feels better that 8.5.3 to me - keep it up!

Per daryl1968's suggestion, here's a summary of some tempo editing suggestions I proposed in another thread.  For details and discussion, look at Sonar Tempo Editing.
 
1. Provide a simple tempo recorder you could invoke from the tempo view that allows you to input your tempo with successive MIDI notes for a selected range of measures and at whatever beat resolution you want to use.
 
2. Make the tempo view consistent with the piano roll view: provide grab handles to adjust individual tempo values, make multiple tempo events selectable and drag-able, provid the heads-up-display there.
 
3. Allow the tempo map to be temporarily disabled (like MIDI track mute) for purposes of practice or data entry.  A user-specified constant tempo would be used when "muted".
 
4. We have a process/fit-to-time capability, but it ought to be a function in the tempo view where such things should be available.
 
5. Lastly, this one is a little hard to explain briefly.  I'd like to have the option to keep my PRV window and tempo view window syncronized.  When syncronized, horizontal scolling or zooming in one would be tracked in the other.  So in switching between tempo and PR views, you'd always see the same measures displayed.

Sigh...

VST3 Support please

Blogman


3. Metronome to work properly when clicking around the timeline when snap is off.
 5. Metronome to be changed to eighth notes, 16ths, dotted 16ths, etc.
6. Metronome to be bouncable, freezable... (still might want to add pro channel to metronome after freeze though...)
8. Recordable tap tempo for conducting the tempo with the space bar ( like finale, or like I do with my Wii-mote and Glove pie and my own personal tap tempo preset in Bome's midi translator)  Then we need nodes to be lassoable and movable like the midi control data.
 ---Blogman

I'm in the process of updating my old compositions based off the mp3s and I completely agree that the metronome in this program needs some serious work. One minor gripe of mine is that when inserting a different tempo, the time ruler stays constant and the audio clip move to match the new tempo. It always psyches me out, thinking I've stretched my audio inadvertently.


Ultimately I'd love to be able to build my own click tracks quickly and easily. If I have a piece that alternates between 4/4 and 6/8 [8th note constant] every two measures, why can't I go into a metronome view, set up a click track for that pattern one time [complete with meter accurate accents], and then copy/paste that "metronome block" over and over for however long I need it, similar to copy/pasting a drum loop. I'm sure this probably doesn't effect a ton of people, but it would be very helpful to those of us dabbling in pieces that constantly change their accents and time signatures.

I have Sonar 3 LE from my soundcard and use it sometimes, my other "daw" is Reason, but i want upgrade for daw with VSTi and i like Sonar for workflow and ease of use for me. I dont know how about staffview in other new versions but, in S3 LE is staffview not very useful.

1. Add to staffview time signature

2. key signature

3 .allow change all signatures and clefs change anywhere in score - for example i want in 24bar change bass clef to other clef.

4. allow change note duration in score (if i wont change note duration i must switch in pianoroll and change duration here, or right click mouse button on note and change number)
example for change note duration:
    - select note or more notes
    - click on note duration
    - selected note are change on your note duration selected

  5. add transpote line(/sign?/signature?) if my notes are very high or low.  
      or make automatic distance between staffs if my note are very high and cross with another staff  

    or allow change distance between staffs

i think this is very important because if i have only one instrument (or on my forst instrument in staff view) and my notes are very high, i  see nothing because notes are out of staff and you cannot scroll up in staffview, because there are fixed spaces between staffs.

  6. Allow make special upper(over) and lower(under) staff for each one miditrack. 
For example:
- under and over each staff will be small icon with plus
- if i click on plus, it create another staff, and this staff will be connected with sign/brace? like piano staff (i dont know how it say in english)
- special staff will by editable like normal staff
  - you can create only two special staff - under and over staff for each miditrack  

evansmalley


...All the attention to "file browsing", "plug-ins", "GUI's", "virtual instruments", and on and on... golly, dang... Does it mean ANYTHING anymore that none of these things are involved in PLAYING music?! It totally freaks me out...

Hiya, evansmalley - I've always thought it would be good to have true Varispeed in Sonar, no argument there. 

But - "...All the attention to "file browsing", "plug-ins", "GUI's", "virtual instruments", and on and on... golly, dang... Does it mean ANYTHING anymore that none of these things are involved in PLAYING music?! It totally freaks me out..."

That's an overly broad an inaccurate statement, and I felt the need to point that out.  You're saying "virtual instruments"  don't have anything to do with playing the music - ?!-- Come on, you know that a lot of people play their virtual instruments - Keyboardists with a huge array of possible sounds/instruments to use beyond the piano is pretty much what MIDI was all about when it began, and it still is for a lot of people.  When using software instruments Or hardware instruments, there are many approaches available, including actually playing the instrument ---And I'm sure you didn't mean that "virtual instruments" aren't actually instruments, since of course they are, -they're software instruments.  It was the implication that no playing is ever involved with their use that inspired me to write.

DMX - "...i think this is very important because if i have only one instrument (or on my forst instrument in staff view) and my notes are very high, i  see nothing because notes are out of staff and you cannot scroll up in staffview, because there are fixed spaces between staffs..."

Good one - And the problem you're talking about exists not only on the staff for the first instrument - There's a fixed space between all staffs, as you also point out, so high notes are always a problem.  If you're working in the Staff View and want to insert high notes in a staff somewhere in the middle of your project- you literally can't- they'll automatically go to the instrument's staff above the one you're working in.

No arguments about how primitive the Staff View is, rendered even more primitive with the absurd streamlining of everything in X1 all for the sake of having a simplified GUI - (classic error of valuing form over function).  --Personally, I hardly ever actually use the Staff View - I sometimes take a look to see what's going on with my notes, but I adapted to using the PRV years ago.  That's the heart of MIDI production in Sonar, since you have access to all controllers, --and problems like this high note problem you're talking about doesn't exist in the PRV. 

I understand how alien the PRV can look at first to someone used to working with notation - that describes me when I first started using Sonar.  But it's an extremely worthwhile adjustment to make because you can do much more with your music if you focus on the PRV instead of the Staff View.

Randy B.

,

...wicked

windsurfer25x
No more plugins PLEASE!

Wouldn't mind a Rapture 2 (updated GUI and stuff), Z3ta 2, etc.. 

Um, is this post a self-created paradox? 

Not exactly haha, at least that wasn't intended! I wouldn't mind them working on and improving stuff we already have basically.