Jump to content

Sonarman

Members
  • Content Count

    80
  • Joined

  • Last visited

Community Reputation

24 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I see. Thanks for the info. U said abt loopback and finding the correct RTL. But I'm not sure how to do that correctly. Also not sure if the RTL will stay constant.
  2. I would blindly select wasapi. But asio4all is handy since it reports latency. Of course not gonna record audio with that, but roundtrip latency also affects midi recording process. I also wonder if folks could create wdm wrappers they certainly can create wasapi wrappers.
  3. Perhaps, but I like to click and open these kind of operations. Could you reproduce the bug while double clicking on the input or output names of synth in the channel it does open the synth interface but also opens the dropdown list which is supposed to happen with single click.
  4. Yes that I understand. I wanna know in what ways wasapi is superior to wdm wrappers(asio4all in particular) despite not reporting latency. Pc's Internal audio is useful when the interface is turned off or while travelling without carrying the interface.
  5. Hi John, when u say wdm wrappers don't perform as good as wasapi mode what exactly does that mean. I mean I would like to know what exactly are the disadvantages of using them? Later you said only the asio reports correct latency. In that case isn't it a better option to choose ASIO by installing something like asio4all?
  6. I just figured out! Double clicking the synth name displayed in the input output section opens the UI. Should have the in/out module enabled in console view. However there seems to be a bug here. While double clicking the single click behaviour is also executed.
  7. How do you open synth UI of an instrument task from console view. I always thought this was possible, but couldn't find an option to do this.
  8. A Big Thanks to Dave for helping me with this, I was able to learn abt SM/BAN. SM/BAN is definitely a working method to alter the grid to fit into midi. What I didn't understood before or the key to handling SM/BAN is to count the number or measures and set Measure/Beat accordingly. The tab & shift + tab command is a god sent and it is what makes this procedure easy. However, every method has its own perks. I tried out the other methods available outside of cakewalk like the time wrap tool in S1 and also the locking the midi to absolute time. Although both yielded quicker results every method has its own perks. The locking midi method is like the best while handing multiple cues in single project, while trying to do this in one particular clip in large project. It would be of great use for scoring for picture. It is also the best and a 10sec solution if the scenario is like you already know the tempo and just want to correct the grid to that. But it might not be the best when trying to set the grid every few bars. SM/BAN and Time wrap are best for that. I guess SM/BAN can do everything Time warp tool can do but it just need a little more attention and meticulous handling while doing it. To have the midi locking feature in CbB would be a great addition. Generally, Cakewalk is not targeted on film scoring people, although it has the basic necessary features its not full featured in that. Yet since CbB already has a Time base option in the inspector and it locks only the start of the clip, it would be great if bakers improve it and make this option available. This option is useful for non scoring people too on different situations.
  9. Yes, apparently what I requested was doable. I had to set a tempo node of 79bpm at 21st measure then I placed the Now Time at the point where the cue ends (62nd measure in this case) and set SM/BAN to various different values until I figure out where it would give be a tempo change of 102bpm. So after trying different incremental and detrimental values I figured out by setting the 62nd measure to 74th measure I was able to get the bpm of 102.12(Not precise yet but that will need a little more fiddling). So although doable its a lot of work and much more work compared to being able to lock the midi to absolute time. This I think is actually a fairly simple scenario. Lets say there are multiple tempo changes, lets say this cue again changes to its original tempo from 62nd measure, that now looks a lot more complex. I tried doing that by setting a 79bpm node at 62 and then using the SM/BAN at 62 that now messes up things setting 62 to 74 at 79bpm. I tried setting a node of 79bpm at 62 and set SM/BAN from 63th measure and perhaps that didn't work. If I tried to change from 61st measure it shows error. Might be an easy task for a mathematical genius. One way to achieve this would be to do the steps I did to change everything after 21st measure to 102bpm and then make a new SM/BAN at where the cue again slows down and ofcourse again try different values and figure out. Or set a node exactly where the tempo change would put the region where the cue slows down prior to making the change itself. Its too complex isn't it for a fairly simple process.
  10. After spending some time with it, it seems like its not doable using SM/BAN. Which is why this feature is necessary and its a very simple and straight forward method to get this done.
  11. If you say so I must spend more time with it and figure out everything SM/BAN can do. I also usually like the mouse free methods. Here is one of my project situation. Do guide me how to achieve the necessary. Its a 3min long cue starts with tempo of 79bpm. A minimalistic Rhodes riff with some melancholic effect. It stops around the end of 18th measure. Then there is a pause for about 10seconds (abt 3 measure in 79bpm) followed by the same riff now in fast tempo providing a cheerful transition(I figured out its around 102bpm) . Goes on for abt 2mins and ends with a rit. The project is set at 79bpm. So basically I need to change the tempo to 102 from somewhere around the 21st measure without changing the midi durations. How will I change the tempo to 102 from 21st measure without changing the tempo of 79bpm from Measure 1-20. The rest of the tempo changes like pause and rit. or rubato can be taken care with SM/BAN. But how to make a tempo change from 79 to 102 on 21st measure using SM/BAN.
  12. Apparently its a very important feature than some might assume. I read some old threads abt this feature and I could see some folks questioning 'Why would you record something without tempo?' "Why would you have a diff tempo?" "Why don't you just rerecord everything" "Wow that's an old case scenario". But in truth I have seen this feature used regularly on day to day basis by composers in professional scoring environment. For eg: I know this composer who just sits down on this Kawai VPC virtual piano controller starts improvising and starts creating melodies and motifs just like that he lays down diff kind of melodies one after another everything gets recorded as midi in his cubase running virtual piano libraries. Later he chops the midi file to separate each individual melodies and starts figuring out their tempo either by taping or simply using the grid likes. Then he changes the midi to Linear timebase and fix the tempo. He then rerecords if req or simply do some edits and finalize the melody. He says he does the same procedure from old times but using real piano and audio files and these days its handy that its possible with midi aswell. And then here's another composer who like many likes to set the tempo prior to laying down something, but midway through he slows down the piece and there seems to be some accelerando and ritardando and may be some tempo change aswell. By the time he finished laying down the whole thing the tempo and metronome is no way in sync with what he played. I was curious how he is gonna handle that project grid. He said that's nothing he will just figure out the tempo changes by locking the midifile to linear time. Provided this being the case I don't think this feature is a wanna be additional feature its a crucial must have core feature for midi centered scoring and music production.
  13. Hi David, yes the ref guide could be incorrect but since other daw's have similar option and it works by locking the midi to absolute time I believe its possible bakers had the same intention when they implemented this option in the inspector. The Set Measure/Beat to Now is handy to tempo map pieces with dynamic tempo but might not be useful in all situations. May be I should spend some more time with it and figure out. But these days other daw's have even easier way of doing what Set Measure/Beat to Now does. Just came across this video, have a look https://www.youtube.com/watch?v=d4sjIPontHA Not a big deal for me but if someone is trying to do this for a really lengthy project it makes a difference.
  14. Very useful feature on scenarios where you have a recorded midi data that doesn't fit into the tempo of the project. And you wanna change the tempo without altering the timing of midi data. There are different situations that lead to this and there are many threads on old forum where people request this feature for various reasons. This is still do able in CbB with complex procedures like stretching the midi clips post tempo change or using other methods like 'Set Measure/Beat At Now' or 'Fit to time'. The problem is not only that these procedures are bit complex they don't easy provide accurate result. Recently figured out this is way too easy to do in Cubase and S1. In S1 just change the Time base in inspector from Beats to Seconds and change the tempo. Easy-peasy! Its just the same in cubase you have to change the Timebase from Musical to Linear. What's more surprising is that CbB actually has the same feature for ages! In inspector change the Timebase from Musical to Absolute. Only it doesn't work! The manual states that it will work but it doesn't work. Either this feature was given up half way under development or it ended up not working due to bug.
×
×
  • Create New...