Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by LarsF

  1. Did you look at ScreenSets, this is pretty much what it is for? A module on transport toolbar have 10 buttons to swap in a flash. So make one for default to revert to.
  2. And when you record do you monitor through Cakewalk - this would mean that your own performance is delayed according to RTL. Many compensate by starting to play early intuitively, not hearing your own performance as it's played. And if doing midi recording - the audio heard will also have the same delay if monitored. Latency for midi can probably be ignored. So this is why I feel why OP midi arrive early - but a theory of course. PDC, the added delay by plugins can be turned off - but not the ASIO buffers. So using external zero latency monitoring is a way to go, not monitor through Cakewalk. I have 253 samples RTL(including AD/DA converters, 64 samples ASIO buffers) which I find acceptable for anything, doing audio in or midi in. On former daw I used a RME Hammerfall with only optical ins/outs - which tricked me a bit, since coverters latency were not reported by ASIO at all. You had to calibrate this and set an offset also for audio clips to end up in the right spot. So that's an idea to look at if things do not turn up where expected. Rambling a bit, all in the spirit to help OP...
  3. Yes, open sysex manager and set to start receive on a slot and perform dump and it will be collected. Save and rename etc for your own purpose.
  4. If your ASIO driver report 4978 latency something is really f***d here. Usually control panel for driver is having a setting, like 128 samples or whatever. Preferences Project Clock what settings are you using there. You said 120 tpqn, but what else, like sync? Further there are a number of things like ttsseq.ini settings which timestamp to use "IgnoreMidiInTimeStamps=<0 or 1> Boolean 0 (disable) This line determines whether or not Cakewalk ignores any MIDI time stamping that a MIDI driver does. If you’re experiencing increasing delays between the time you play a MIDI note on a controller and the time you hear Cakewalk echo it, setting this line to 1 may help. Also, if you find that Cakewalk is recording MIDI data at a different time from when the data was played, setting this line to 1 may help. If the MIDI driver is using a different clock from Cakewalk, the time discrepancy increases the longer that the MIDI driver is open, so you need to tell Cakewalk to ignore the timestamp that the MIDI driver adds to the data (set the value to 1)." Further, did you try and turn off latency compensation PDC button on toolbar "The Live Input PDC Override toggle lets you disable delay compensation on live tracks, thereby removing the latency during playback and recording of such tracks. Since it's a toggle, you can quickly turn it on to complete your tracking at low latency, and turn it off when finished to hear the track compensated as normal." Seemingly affecting if audio out is delay or not, worth a test if it makes a difference. Some claim to have pdc off due to compensating for a delay heard so starting to play early. I usually am fine having it on, and just minimizing whatever causing delays. But I would look at the basics like asio reported latency first, that is really off if saying thousands of samples. Using mostly external midi gear I use Time Offset on midi tracks to adjust to delay in external devices to respond, so their audio will fall on the grid etc. Every synth has different delays, some respond on 128 samples, others on 400 samples.
  5. I think this is what they are talking about, little different than just volume balance. https://theproaudiofiles.com/mid-side-processing/ So many libraries produce stereo stuff, and just stacking this on top of each other can create a mess. Balance panning helps, but width is not adjusted.
  6. That leads to long standing(Sonar days even) requests from many - to have automation with master/slave or parent/child relationship - in other words VCA groups. That is exactly what that does - target many from one automation curve in a relative fashion. I experimented though, and by quick grouping(ctrl down) some tracks with automation lanes visible I could move one automation curve and the others followed. So do a group and move all same amount together works this manual way. My workaround for now. Worked by writing automation too and have Offset active - but it freeze into existing automation immediately when stopping transport. So have to be done with Undo and redo that until satisfied right there. You cannot postpone till later. But truth is so many do fake VCA groups anyway, the controls are fixed what you can group, fader only or not nested grouping. Reaper and Samplitude does not have nested VCA groups. Trialing Reaper 5.4 it did not move faders either, just on meters you saw things changing which is a joke not getting visuals until merged. Cakewalk really has excellent freedom in the control grouping - rightclick any individual control and group together with others - so maybe more difficult not to break that if to do VCA stuff. Most daws have checkboxes for a control group to include pan as an example - but not for VCA stuff, as I recall. Cakewalk is more sofisticated, I think.
  7. You have surround pan in Cakewalk. What I think you mean by true stereo pan - is not there AFAIK(without a plugin of some sort). But to get binaural, virtual surround on stereo, I use Wavearts Panorama 6. But Waves S1(included in Gold bundle) also do this kind of true stereo panning, like getting a stereo between 1100-1400 hours or similar, but nothing built in. I do on like leslie for hammond stuff so not everything is full stereo. Have not looked at stock plugins, if anything there of this sort.
  8. Different daws may set different ASIO latency, and some have special features like Cubase/Nuendo ASIO guard or whatever it was. Reaper and StudioOne add processing buffers apart from ASIO buffer setting etc. So many things may differ in what daw have as load. Larger latency give more headroom before crackles and pops. Did you look in task manager what cpu load is and what is ASIO buffer setting? (With and without last plugin, and depending on preset you used) The example I mentioned it was added cpu, and when at 55-60%(task manager) or so, some crackles can appear. I run 64 samples ASIO buffers, and a 10 year old quadcore i7 (benchmarking at 5000, where modern cpu i9-9900k of today rate about 20 000) so old cpu in this regard. If not related to cpu, something close to what you suggest - something wrong with audio engine - may be relevant. I did not bother with 64-bit engine yet, if that matters. This is another setting that may differ between daws what is default. For me with Cakewalk the default threadscheduling worked the best in that it distribute even on 8 cores(4 physical with hyperthreading give 8 logical). Another setting made it use 4 cores only(don't remember which one), so changed it back. And my reasoning with what is the largest project that runs normally? Thinking that some special plugin here really raise cpu. It could be running a mono plugin on stereo interleave track or other way around. Page 191 in manual mention some special settings that are in plugin manager in how mono is handled. Overall thinking is that some default settings in Cakewalk does not make optimal result on your system.
  9. The best I saw in this was Mixcraft - very clever approach to just stack instruments and effects as you please and midi just flows down to the next. Load an arpeggiator then an instrument - and you could save it as an effect chain we are used to do with effects in a bay. And each instrument in the chain got their own outs as well. If you did two instances of Dimension Pro that just have one stereo out, you get two stereo out from that chain or folder. Reaper is good in the sense there are no track types - as I recall. You handle audio and midi on the same track, and route however you like. I requested for Sonar many years ago, feature request, to have VST midi effects go in MFX bays as well. You have for audio tracks to do both DX technology and VST technology - why not for midi bays on midi tracks to handle both? MFX is DX technology, so extend to handle VST as well - and you could do many things not as easy today. I could insert the Piz midi plugins in MFX bays too. Regardless of daw though, you have a choice to look for solutions or problems. Looking for problems you will swap daw all the time. If there are showstoppers it's nothing you can do but swap. But Patchwork makes me free to do this regardsless of daw I use. And why I don't use anything stock plugins either - all 3rd party. The plugins are the tools you need to learn - and you move them to any daw of choice without relearning your tools.
  10. ..to expand a bit - you can always chain a couple of instrument tracks together, taking midi out from one as input to the next. Then to repeat this, just save this config as a track template and this is done in a flash for you. For the smoothest operation I use Bluecat Audio Patchwork to chain a whole bunch of midi effects and instruments and whatnot on a single instance on an instrument track. I mostly use Insert Piz Here midi plugins bundle. https://www.bluecataudio.com/Products/Product_PatchWork/ Good investment for sure. But for DX type of midi effects, MFX, you can see if some are here that are useful. http://www.tencrazy.com/gadgets/mfx/ They can be inserted on midi tracks MFX bays in series if you want.
  11. You had this and everybody else must have too? Last time I had crackle in Cakewalk was when I reached 48 tracks, and sends and stuff everywhere. And this was a mistake due to that Prochannel had activated two plugins on every track, 96 instances. Removing those I now am on 80 tracks in same project and still no crackles. I run RME HDSP 9632. What is your reference with any other daw and tracks and so on? Maybe your interface is on the verge already doing what you did, and just that bit better working with other daws. So which interface is it, or your feedback is futile?
  12. Yes, reverse reverbs are fun. I heard a mix they did that on kick, and it was like it coming from outer space at you or something. Not to long on kick works, shorter reverb or delay.
  13. if you got to audio this "Process > Apply Effect > Reverse The Process > Apply Effect > Reverse command reverses audio data, making it play backwards. You may want to do this to obtain unusual sounds for special effects."
  14. chase back on play, and include note event - is a setting you can look into.....preferences->project->midi
  15. Recording is already covered by RBH. Just route these panned hard left and right later to a bus, or group faders on the two routed to master. If you want to fix a stereo from it once done, you probably can route to aux track and re-record as stereo track if you prefer.
  16. Might this serve to improve? TTSSEQ.INI settings "IgnoreMidiInTimeStamps=<0 or 1> Boolean 0 (disable) This line determines whether or not Cakewalk ignores any MIDI time stamping that a MIDI driver does. If you’re experiencing increasing delays between the time you play a MIDI note on a controller and the time you hear Cakewalk echo it, setting this line to 1 may help. Also, if you find that Cakewalk is recording MIDI data at a different time from when the data was played, setting this line to 1 may help. If the MIDI driver is using a different clock from Cakewalk, the time discrepancy increases the longer that the MIDI driver is open, so you need to tell Cakewalk to ignore the timestamp that the MIDI driver adds to the data (set the value to 1)."
  17. Did you look at pan laws p.207 in manual? What you do with mono tracks after - sum to a bus as is centered, panned full left right etc makes a difference. Difference daws have different pan laws, some can be selected - not so in studioone(you have to use a stock plugin for that). In Reaper and Cakewalk you can select what to use.
  18. This again raises need for a full document with all alternatives represented. - mono interleave - mono clips - mono interleave - stereo clips - stereo interleave - mono clips - stereo interleave - stereo clips - then all combinations of mono, mono/stereo, stereo/stereo plugins after each other - and how these will be routed. - like mono interleave and first mono/mono plugin and then mono/stereo plugin - and any combination thereof after each other Just a table showing this would be incredibly useful so you can work with that. Manual also state something about a checkbox in plugin manager to change some behavior regarding mono. I find manual really good and extensive, but could be improved with an article addendum stating this to leave the guesswork out. If a dialog just showing the pins of track plugin bay and each plugins pins - that would be awesome. Some daws allow to alter this, but as a first step just seing how things are routed would really make a difference. I once by accident inserted a plugin from recently used, of wrong kind, and you scratch your head bald over what you hear. Just pop up this kind of dialog showing routing and you can fix your mistakes.
  19. Many thanks. So if a stereo plugin last - one can count on that both those outs go to those two points directly out, instead of mono panner do some acrobatics either dropping one and panning the other or similar? So changed to stereo panner, or something. As I recall Reaper did same mono signal to both ins, if stereo plugin. Just a simple matrix to show where audio went. To be sure I put stereo plugin on a bus and use a prefader send from mono track to it(and show fader down) - so bus gets the same on both ins if panner is center. Thought about what happends if just putting plugin on track directly simplifying things, but nice if predictable. EDIT: Putting plugin directly on mono track it seems you have to set interleave to Stereo for plugin to work correctly. If in future Cakewalk get some visual showing how routings are done, preventing first getting strangeness that have to be fixed, would be great. How much strangeness will be from inserting maybe a couple of mono plugins+a stereo plugin - or going stereo plugins all the way due to how it works best - I'm not sure. And rather not spend hours finding out either.
  20. I know in Reaper and Cubase you have full control what to do with various channels on plugin, cut them, reroute them etc. Before I knew about the routing options in Cubase I got really strange result, because one channels just bypass mono plugin. In Cakewalk a) do you just set interleave to stereo and plugins of stereo kind is handled from the mono clips there? b) other way? Thanks.
  21. I found a plugin that works really well in Cakewalk, can be used on mono or stereo track. Plugin does not need to be surround channels. But you can create surround environment for parts of mixes as you please, for phones or speakers. https://wavearts.com/products/plugins/panorama-6/ Seems really cool, and good manual actually explains what every control is about, how it affect the end result. Audio bouncing on harder material and how a believable audio image of a room is created. And get exact positioning of source and listener, above, behind, below or whatever. Doppler effect as well for moving objects. For reflection model you tell which material on each wall, floor and ceiling. There is a load of binaural algorithms, meaning how the head of listener is emulated. Licensing is ok, 3 pc's of same user, and either serial number or iLok - pricetag good too. I thought it will would be perfect for my videos of timelapses and stuff and target headphones with mixes(but speakers can be used too, they have an elimination for crosstalk that appear between speakers). Ran it for a couple of hours now, and is really cool.
  22. I listened to a whole bunch of binaural stereo demos and found the same weakness for phones on all of them - they miss out on the horisontal plane that is in front of you and behind you. This needs to be created on phones and especially if doing VR which this plugin claimed to be for - but useless for that purpose since not there in any I found. Demos were made for having stereo speaker in front of you - then that horisontal plane is there automatically. But behind you still as bad not having a full horisontal plane there. I thought it would be fun to do phones targeted mixes but just getting stereo on phones it grows upwards with more reverb moving objects away, not in front of you as I expected for claiming to be for VR. If you move in a hallway and a sound source in front of you - it should be felt being in front of you, not just your head blown out of proportion. If making VR goggles for games this is essential or you don't feel this is real. I just love Wishbone Ash and this song with this kind of demo
  23. Mostly out o curiosity I saw that very few hosts were approved for Waves surround. I was thinking also on some other brand surround plugin, listing the same hosts as Waves - so just wondered. And Cakewalk is approved for just about all other Waves stuff. Thanks.
  24. Could be being used to other daws that does not have audio tracks at all on outs, only automation tracks in track view. Cubase and StudioOne as examples, you have to fiddle with extra tracks. Cubase even hides frozen audio, not visible to preview doing automation. Cakewalk implementatiton is the best there is, in my view. You just freeze and you get audio where you had meters going before, so good overview when to do automation later. Especially when doing multi out VST instruments a great feature. And unfreezing is as easy as freezing later if to continue working on that track. All other daws always created extra tracks to keep track of, and some even manual handling of freeing resources and stuff. But if you really need separate audio somewhere else, you got your answers earlier.
  • Create New...