Jump to content

LarsF

Members
  • Posts

    223
  • Joined

  • Last visited

Everything posted by LarsF

  1. I think so too - it's easy to forget that all plugins and instruments does not need to run realtime - use freeze options. Your cpu benchmark at about 6000 and a new i9-9900k about 18000 - but translate that into project it might mean 50% larger project is my estimate. It's not 3 times bigger. https://www.cpubenchmark.net/high_end_cpus.html My old i7-860 benchmark at 5000, and have no issues running projects live plugins to about 50 tracks or so. And Cakewalk freeze is the best in the business, so quick to go back and forth. Even multi out VST instruments are cool. Troublefree daw also depend on soundcards used, and maybe look at that part too is an option. It's nothing like RME internal cards and I run HDSP 9632 at 64 samples as I mention above, no issues with crackles and pops.
  2. I just prefer external midi gear - synths and modules. - it usually is real fun and nice way of making own sounds - knobs on everything - does not compare to VST instruments - less load on cpu, but takes more analog inputs on computer - until recorded to audio clips - and usually a power on button - and sit and fool around a bit - lower threashold to actually use the gear Drums and some sample libraries are inevitable though. Everything that requires tweaking - EXTERNAL.....
  3. Hi Sometimes listen to various stuff in background while browsing Cakewalk forum - and playback suddenly become Donald Duck, every page load? Does anybody have a clue what that is about? Nothing is played back as far as I know, or is there some sound effect or something not obvious? It does not happend anywhere else on internet. Thanks.
  4. Don't get your hopes up. I bought Notion 6.5 to go with StudioOne - and it fails even to navigate midi files I have. I had a couple of bars it completely loose navigation and result was not usable. StudioOne played them alright though, just Notion - so that code into StudioOne maybe will fail as well. Notion even less succeed in splitting a midi file into two staves - for grand piano staff, or whatever they called it. Track had to be named Piano or anything twohanded you have recorded cannot be presented as two staves - at import only, or if recording directly into Notion. In Cakewalk staff view this is as easy as anything - just select bass+treble clef or whatever it was called, and select which note to split it on - done. And you can go back and forth changing until you get best readability for that notation. Staff view has so much going for it - it's such a pity it does not get more attention from bakers. As long as I had 4/4 signature and no triplets - I had really good use of it from Sonar 4 onwards. But taking drums lessons and starting to do more interesting time signatures - triplets stuff - it cannot be used. Not ordinary shuffle even.
  5. Download the trackdiag och portdiag mfx plugins here and see what is going on http://www.tencrazy.com/gadgets/mfx/ PortDiag is for realtime monitoring what is coming in, and TrackDiag capture what is played back. Very useful. Just insert on midi track plugin bay. Unless you were tweaking realtime as I read your post before, I cannot see how that would be happening. Some information is missing in how you did things. Have you set recording manual offset in config for audio device? Are PDC activated as you record or turned off on toolbar buttons? I do almost solely external midi gear, 4 synths, hammond and a digital piano, and never saw that. If your hear in realtime that audio from synth react, why should it not record audio as such? Or are you rerecording midi first, or something? Just an audio track and it does not sound right from synth if one track is armed for recording, and record is going on? Is midi cc separate midi track, or together with notes as recorded before? I set midi tracks negative time+ so audio from synth line up with grid where midi is, did you do that? I have separate values for each synth how much time is needs to respond, from 100 samples to 400 samples or so. Set in ticks on track. Please fill us in on more details....
  6. Updated 2020.01 to 2020.05 this weekend and have some strange behavior. #1. Soloing a bus - mutes metronome I can solo any number of tracks no problem. But if I turn on Dim on solo - then metronome comes back. Have not checked all options - but I only have for count in, so neither playback or record are checked. I checked output, it was on Analog1+2 on hardware, same as master goes to. Changed to master for metronome, but no different. #2. recorded midi - much too often it truncates the last bar as recorded. I know I played another bar before hitting spacebar, and I could even see it truncated. It was longer before hitting spacebar. I did not check if it just used another take in comp lanes or something. I did maybe a dozen takes, then undo with Ctrl Z and recorded again. Recording mode comp. #3. Strange things happend - and suddenly lead vocal track seemed slided so first line of vers was gone. Clip looked normal position. I also found that Start marker I always have at 5.01 was gone. And other markers were nudged 800 ticks or something. They did not line up on the grid. I luckily had a backup I reverted to from 2 days ago - that made this back to normal. Not sure if I pressed something, I forgot which modifier were to activate Solo override, tried Ctrl and Alt before finding Shift. That is all I know I did. I will see if doing the same things in my Sonar Artist 2015 works on the same project, to see if I can narrow down a bit. If anybody experienced similar, please share.
  7. Not sure I follow so just ignore if I got it wrong - you play back notes in clips with midi to external synth while touching synth knobs in realtime to add filter changes, and record final audio? a) or are you using other controller that sending a certain midi cc - thinking extra delay routes this travels? b) how large are asio buffers if the realtime delay is significant? c) this using "local off" in synth and roundtrip monitor midi cc through Cakewalk - or "local on" where knob directly control parameter in synth? There is a setting to disable that local off is sent when project load "SendLocalOff=<0 or 1> Boolean 1 (enable) This line determines whether or not Cakewalk should send a Local Control OFF message during startup."
  8. True, I ran Cakewalk Pro 3.0 late 80's and as MSDOS and it had sysex manager already then. StudioOne does not even support sysex at all, not for recording or anything. I had to go to extensive length with plugins that could program to send initializing to various midi gear as I load a project. My Yamaha piano had mixed midi CC and sysex as initialized so recorded in Sonar and used special plugins. Midi editing in StudioOne - you cannot remove midi CC at all. I had unwanted CC1 as I was playing a keyboard, mod wheel just moved, I had to move midi to Sonar to remove it. You cannot remove first value of CC in StudioOne, even if node is deleted. Some handling of chords and chord track etc is very useful in StudioOne though.
  9. I moved from StudioOne back to Cakewalk due to that all midi recording of CC is forced to automation, that was a showstopper for me. It means that first move of a control like filter attack on synth or leslie on organ always was sent at beginning of clip. So even having the actual midi CC 2 bars in from clip start - this is interpreted as initial value and sent not where recorded but at beginning of clip. In Cakewalk it remains data as long as you want, no problems at all. And you can convert to automation style if you want. Just FYI.....
  10. MFX Velocity plugin is useful for many such operations too. You can scale, limit or add and many things to velocity. A midi effect, MFX, can be run on a selection by Process Effect - or inserted on midi tracks for realtime processing.
  11. 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.
  12. 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...
  13. 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.
  14. 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.
  15. 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.
  16. 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.
  17. 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.
  18. 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.
  19. 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.
  20. ..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.
  21. 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?
  22. 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.
  23. 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."
  24. chase back on play, and include note event - is a setting you can look into.....preferences->project->midi
  25. 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.
×
×
  • Create New...