Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by LarsF

  1. Hi Got a reminder to refresh and logged in to assistant and downarrow and Refresh Activation. Is there supposed to be a confirmation or something? I noticed nothing. Is there a way to see expire date or something? I am on 2020.09 and am not going to update Cakewalk now, just fix nag screen. Thanks.
  2. When I select 2 midi track and open piano roll view from View menu - I get the multiple track piano roll view. I'm sure there are other ways too. I mostly open one track only, and on top right of piano roll view there are double arrows that expand a panel to easily switch which track you are editing. If the midi is part of same destination you can select a couple and they show at the same time too. If you have clips on different tracks that have same destination you can have all visible. Rather smooth I think. Experiment with screen sets and you find a way to revert to one that is locked, so easily go back and forth. I have a vague memory there is a feature to go back to previous zoom level as well.
  3. - Select the tracks - Rightclick menu on one - Show Selected Tracks And just these two are fitted vertically But I use Screensets extensively, so save away current screen set with copy in the menu that popup when pressed the current. Some I lock also so I never change them - the current one always is updated otherwise as you go along. Then lit ExclusiveSolo on command bar, and you solo one and then solo the other without any further clicks.
  4. ..forgot one thing See to that Dim on command button is not engaged. It will make full project sound, but at a dimmed level ´set in preferences. Not sure if this can be kept from last session, just check that it is not engaged.
  5. Try solo Master channel as well - sometimes that is what you have to do. Sometimes it soloes full project doing that and override what you wanted to solo - soloing everything feeding it. Other times it seems to try and understand that you don't want to mute Master - like you can solo a track and Master is sounding. Like a built in Solo Overrride but you cannot see it. There are some things regarding solo that needs devs attention, I think. It's not consistent. I liked how StudioOne did it - when you solo - all the mute button lit where it is muted - so you get a visual if what is to sound as soloed. That's a really good approach, I think. Other things I reported are Solo Override(shift solo thingy) that behave like no other daw do for this feature. In Cakewalk it soloes as engaged, other daws just have this ready for when you are soloing something.
  6. From time to time in a session this happends to me too. Solo is a bit flaky, it seems. I can solo one track and one bus - they sound fine, then I remove solo on track - but it goes all silent instead - bus is not heard. Most of the time I need not solo Master as well, sometimes I must unsolo master. Restart Cakewalk usually works.
  7. IMO most common for CC11 is to add to velocity - so it also affects timbre of the sound. Something like a percentige added to velocity to a max of 127 on velocity of course. (CC11/127)+ velocity or something. Nordlead synths handle CC7 as gain amount on amp envelope and tells overall volume on a preset. Using high resonance settings in filter usually give volume is scaled down not to clip digitally. So gain can compensate for that, within headroom of course. Hammond use expression as pure volume, but you can select if pre- or post- amp section affecting saturation etc. But you usually don't use velocity, it's fixed, as playing organ, so used extensively compared to like a piano or something. Part of playing style of organ. In Dimension Pro you have to assign midi CC to something as I recall.
  8. I only managed to place markers at a frame for SMPTE, no fixed placement on ms what I managed to do.
  9. LarsF

    Cakewalk MIDI

    Clicking [R]-button so not lit will disable reading automation at all. There is a Sonitus plugin - disable that too for troubleshooting purposes.
  10. Yes, and it's not just about setting a number on the faders or meters - internally you have to adjust since digital has a max number limit. 12 dB that is 4 times up from 0 dBFs. So number cranking inside has to handle this. If you have a 24-bit file of samples, that peak at 0dBFs(meaning integers inside are +/- 8 miljon), and load that together with others you cannot boost that 6 dB and store again(it would be +/- 16 miljon). So some clever processing is going on how you treat it. My assumption was that it is treated as being +/- 4 miljon(down 6 dB if headroom is 6 dB), which leaves room for 6 dB boost without overs. I described what I think they do internally - and how it might affect what goes into plugins as well - which could change sound. Especially if some non-linear thing is going on. But as many stated - just having a loudness difference of 1-2 dB is enough for ears to perceive differently in frequency content. So my theory might be off regarding headroom thingy.....
  11. Hmmm....somebody correct me if I am wrong.... Whatever headroom there is I assume is adjusted for from start of a daw project. If you have +6 dB headroom, you from start adjusted down all levels 6 dB from start, or you would have nowhere to go when boosting. 0 dBFs is ceiling in the end, now adjusted to be -6 dBFs. But is plugin aware of this - I think it sense whatever comes in from clip and hits it - but in fact is 6 dB adjusted. Same if +12 dB headroom, that all numbers(or what to call levels) are adjusted down internally to fit 0 dBFs + 12 dB. This is a theory, sombody that knows chime in. I remember running Cubase, there was a remark in manual for a version about these levels and how they would be handled since sounding louder. From Cubase manual "Volume Max Allows you to specify the maximum fader level. By default, this is set to +12 dB. If you load projects that were created with Cubase versions older than 5.5, this value is set to the old default value of +6 dB." Another thing I noticed running some of Waves hardware emulating plugins is that they did not like to be hit too hard from clip, they were like hardware made to be hit with -18 dBFs peaks as I recall. I have to adjust not too hot clips, or just use Gain knob in console. If you were still well within 0 dBFs peaks was not enough. I got overs all the time and no presets were even close to work, had to turn down input level to zero just about. Sounding different, could it be here some plugins are more sensitive which levels they are hit with? In particular if emulating analog where level significantly affect what harmonics you get. Some plugin overlooked this adjustment daws make with different headroom. Correct me if I am wrong.....
  12. I could add something to Azslow3 comments about Reaper and an issue I had Reaper never convert and do sample rate conversion on import. It always just resample in realtime. And there are different resample/stretching algos for playback and rendering in Reaper. I had an issue I had reference track on another tab in Reaper that were 44k. And my project at 48k in another tab. And listening to reference track I got overs, professional bought recordings, I got overs - so it resampled to 48k in realtime. First I got 1.6 dB overs. Increasing quality to highest on playback algos resampling for this went down to 0.6 dB overs. Of course playback of professional recording in 44k so no resampling - no overs on that when I tried that. This tells a story that resampling does things to material - it is severly affected - depending a quality chosen. To save cpu Reaper usually have less quality setting for playback as default. So if to do critical compare one have to consider many things....
  13. Would you mind posting an export from each doing this in Reaper and Cakewalk? Just 15-20s or so. Which reverb is it, and assume on an effect bus so sends are used? Inserts may cause issues usually stereo and if not on stereo interleave setting. There are some plugin manager setting as well if on a mono track. And assume you use a saved VST preset from that reverb doing it in another host. Using Waves mostly, I save presets in their plugin menu so easy to use same in any daw. I have Reaper 4.7 at least(VST2 only) if I happend to have same reverb, I could try it out. Things that happends to me in Cakewalk, I forget to watch a new busses output - being defaultet to hardware outs, to get through master instead. Just a thought - one thing to check out? So when putting mix so limiter on Master is limiting I had returns from effect bus not going that route and appeared stronger due to that. Just assuming there is a natural explanation why it would sound different - whatever we might find.... There is a lengthy thread at KVR Audio how crap a guy claimed Cakewalk sound compared to Cubase, as one guy digitized vinyl at 96k/24. Looking closely into this, I found this anomaly that poster did not know about obviously, looking like a 8k boost in there suggesting wrong capacitance on RIAA amp And it was Cubase that sounded a bit muffled in my tests, will of course sound more normal if having a treble boost. (done in Sonar 8.5 32 bit I happend to have Ozone on) The guy went silent after that discovery, he overlooked something. I kind of like digging into these kind of issues. One always learn new stuff going deeping into things....
  14. From StudioOne manual "Studio One uses a -3 dB pan law for all channel panning. On stereo Channels, the panner adjusts the balance of left and right signal levels." so if setting 0dB center in Cakewalk there is the difference - on track out - on send level. There are pans on sends as well.
  15. Pan laws are applied to sends as well obviously. If you've got 3 dB difference in pan law center - it affect send too. So when comparing daws, don't compare apples and oranges. If using 3rd party, and same effects it would sound the same as well. It could be you like a stock plugin better from one daw, that is fine. Just compare in a fair way. Over the years there has been floods of threads stating that one daw sound better than the other like on KVR Audio forum. Go with what you believe - just don't confuse it with facts. One thing when starting to load plugins that can be different is how inserting mono->stereo plugins on mono tracks. These things can be different and you don't have full control in Cakewalk. Cubase and Reaper allow full control which channel goes where etc. StudioOne does not. Also setting stereo interleave or not makes a big difference with various plugins in Cakewalk. Waves have clearly stated plugin components, mono, stereo, mono->stereo etc - not on all plugins - is it a stereo component and put on mono track it can be quite different result in different daws. Various versions of StudioOne I ran handle this according to different rules it seems, v2.x filtered out stereo plugins in listing if on mono track etc. Something was changed in StudioOne v4.x regarding this - but no real control how channels are routed. So when building full project to compare daws many things may affect how it sounds. So be aware of such things - and it will sound the same with the same plugins. But I had incidents with Cakewalk Prochannels was active with no activity from me, so as said - check that out. I'd like to disable PC completely not having it happend over and over again. Having that module hidden in console may show what is active.
  16. That is to do with pan laws, some daws have center -3dB - so there you have it. Choose pan law to liking in Cakewalk and it will be the same. StudioOne does not even have a setting for pan laws, you have to use some special plugin for that to deviate from default.
  17. "Where would I check on the pagefile setting etc?" Starship Krupa mentioned it above, rather early task manager Performance tab. How much physical memory are you having free just booted computer? You have 24 GB in your specs for computer. So around 20 GB free is probably close. How much free as Cakewalk is started? How much after first project loaded? How much after 2nd project loaded? ....and so forth. Are you getting less and less free memory all the time? A little is normal depending how much a project contains in sampler plugin instances etc. So when getting to 17th - what does it say in free memory in Performance tab? You can also look at memory in the Processes tab, how much Cakewalk alone is using. But overall free memory in system will probably do - it probably says available physical memory somewhere. When you start getting above 75% of physical ram memory used, windows is starting to use pagefile swapping to virtual memory, This is simply using a file on disk as temporary storage to extend capabilities overall what can run. But just below 10 GB memory or so available might having system use pagefile, so just get the number of what task manager Performance says is free when you feel system is getting slow. Since you had harddrives earlier this would use some memory as read cache for things you loaded. Now using SSD this read caching is not needed in the same way, since reading arbitrary spot on disk is so much faster and read caching. So mission is - put a number here on forum for taskmanager available memory as you getting a slow system(17th load or whatever) - size of pagefile or virtual memory also put that number here That will give clues what is going on....
  18. First I come to think of if 17 projects are open at the same time? - mean if closing one before opening next There is a setting in preferences if to allow more than one project at a time. Then current project is replaced as another is opened. And OP never answered how much free memory task manager show as new projects are opened(or I missed it)? 24 GB is plenty for one project, for 17 project not so much. Behavior is typical for pagefile is starting to be swapped with physical memory, that is reeeeeeeeeeeeeeeeeeeeeeeaaaaaaaaaaaaaaaaaaalllllllllllly slow. And the advanced settings to automatically save every x changes or a time span is also under suspicion.
  19. If OP got expression pedal - that is usually CC11, so can also be easily tested what instrument respond to. Run fader on midi track - CC7. Move expression pedal - CC11. So either or both can be part of how it responds, as Bitflipper mentioned. I avoid medling with CC7 as much as corona, can result in unwanted changes if fader is ever touched. Some synths have VCA amount on CC7, like Nordlead as one. Best to disable it in daw.
  20. Touching fader on pure midi tracks will send CC7, so easy to test how it responds. It does as you move fader, and do resend last value once starting transport after touching it. After sending it once starting transport it never sends again starting/stopping - it is considered done - and equipment should know it current value. I did a full walktrhough for myself what happends with various midi CC, some like pan and reverb are always sent every start transport and some are like latch type as volume CC7 https://discuss.cakewalk.com/index.php?/topic/11252-midi-fader-gainvelocity-offset-pan-chorus-reverb-this-big-resource-how-it-works/&tab=comments#comment-99629
  21. Thanks, no it was pure editing. I used some cal scripts to raise level so in this case foot controller was high enough to close hihat. Also raised in between so no dips, but could not see this. Answer was that as standard they only draw controllers where enough change in them - not to clutter clip I assume. Is seen very clearly as you switch between edit filter Clips and the Edit Filer Show Notes->Foot controller, took a while to find that inline editing - not in menues, not in preferences and not in keyboard shortcuts. And it's not called Inline PRV or something, it's called Show Notes.
  22. I have a midi clip and it nicely draw overlayed the controller on it as presented on track. You see where you used foot controller on drums, or sustain pedal on piano takes etc. After editing controllers a lot, I still get the same pic as the clip is draw. Tried closing and opening project, but no difference. Content in prv view is as I edited, and what is draw does not look anything like it. Is this carved in stone forever, or can this be recalulated so represent how it actually looks? There is for audio clips, but have not found this for midi. Thanks. EDIT: It might be a misconception by me. Controllers are never drawn in full in main window, only when dynamic enough. I discovered as I did inline editing and showing controllers it's seen more clearly in full. Cool feature. So wanting it in full, I can set track to show controllers, and they are shown on top of notes.
  23. I find the easiest is to turn on FX button in command module in toolbar. That bypass all effects. Another one to try is PDC button, to just ignore plugin delay compensation. Using large asio buffers can delay your own echo monitor through Cakewalk and you compensate by playing early. Then Cakewalk adjust a clip backwards for the full roundtrip delay as well, and become too much since midi is not roundtrip audio - it's only oneway audio delay of the buffers. Midi delay input may be smaller. Is interface recording the correct delay? I create an audio loopback, and record metronome this way to see if on grid. There is a setting also to adjust recording offset, in Sync and Caching in Audio in Preferences. This value is added to whatever interface report. So if not on grid - one thing to adjust. Last resort - adjust clip manually after record. There are 3 nudge settings, where you can adjust a clip in various ways you can try what works best. So a keyboard shortcut can make this done in one go, as you find it differs for midi. A bunch of ideas....
  24. I have a project where midi was imported, and project happend to be at 120 bpm. Then I imported an audio track, and found when that plays together they don't match correct tempo. Figured this is perfect for just saying to Cakewalk - Set Measure/Beat at Now thingy. I locked audio clip in position/data so would not be affected. What I expected was - a node would be inserted keeping 120 bpm from that spot onwards, but adjust tempo from previous node up to Now as something else that make chosen measure end up there. - no other thing should happend to midi - in this way I figured I could line up project tempo so audio and midi align. What happends is - a node is inserted in tempo map, lets say 133 bpm before BUT then also makes it 133 from that point, AND ON TOP also stretch midi so it will sound as played before this operation but saying 133 bpm. - so you now have same tempo before and after that Now pos - not what I wanted Since midi is now stretched to some other tempo as played and I could not just adjust tempo node to play midi as it were, but to tempo from node at Now. I don't get what kind of situation this should happend? How should this midi align with anything? Manual describes as you should be able and go through a freely made recording with no notice of project tempo from start. How can this possibly happend? Both StudioOne and Cubase has really smooth operations for this - you just set midi clip to timebase time so not affected - then an operation lets you drag any measure boundary on timeline like a rubber band as you wish and drop at any midi note. - when done you just unlock clip and the midi there is the same - midi is never altered itself, just plays according to new tempo I thought at first Cakewalk approach would be much simpler and better if it worked like I expected at top in post. And it would be if just adjusted tempo up to Now - not after Now and also stretch everything after Now to a tempo you don't want anyway. With clip aligned to grid, I thought I just continue and adjust tempo node from Now as inserted, to make midi align with audio - but now that was stretched to did not work. It's a small embryo for a song idea, so I remake it - just wondered over how this operation really should work for future reference? - Why is it adjusting tempo after Now to new tempo before Now?????? - and to do that is also stretch everything midi after Now If you want to slide measure/beats to align - before the chosen point would be enough, or? - you sort of move a measure boundary to another position in time, why adjust things after as well? Thanks for an alternate idea how to do this? And what situation did you successfully use this Set Measure/Bat at Now - what was the situation you solved? I saw in Sonar Artist 2015 was the same, so been like this forever. Thanks.
  25. Click on metronome symbol in toolbar, and see which track metronome is output to. By default there is among busses Metronome track, which is where to set volume. But you can set level of the clicks as well in that dialog. Other related setting are dim on solo, and you can increase level on soled track, which could the one you record to hear better. A couple of ways to go about this....
  • Create New...