Jump to content

LarsF

Members
  • Content Count

    188
  • Joined

  • Last visited

Everything posted by LarsF

  1. It's fairly easy - there are plenty clicks without guitar in the tail, two bars or so. Then it seems he took off phones and you hear more ambience, leave out that part. I duplicated track, isolated a couple of those, and reversed phase - dead silent. Then dragged this into parts with guitar sounding. Fed these two track into a bus to sum. Just identify accent, so they are paired and they should cancel out. Increase visual level so half periods are easily spotted. But it need to be really well aligned, not just about.
  2. I did this kind of removal with an electric fence pulses where I live, came into electric guitar fading out. Best if you can isolate a single click, or even better a couple, with silent enough guitar, and duplicate that and invert phase on it. It need to be same level, and that part is there in the actual recording. Picking a separate series, level must be precise as adjusted. So feeding separate track with pulses in opposite phase to a bus to sum it. It will probably take an hour 1st time doing this, but doable. It must be exactly in time, and recognizing what is click part in signal may be tricky at first, but you learn how to spot it. Good part about click track is that click is persistent in time, everyone, this electric fence varied enough to not pick a series.
  3. If I follow - 16 instances of the same plugin on different tracks? I'm thinking the quick grouping the tracks, and hold control when you do anything like that - and it duplicates to all selected. But the same thing with multiple chains, have not tried that. Or you talk about something all different....
  4. How lovely, thank you. Since the commit does what exactly what I hoped, it's not a biggy to cut paste fills or similar like that after a commit - and then mix, do automation and finalize it all. It usually takes a good while for me to feel something is missing and want a bridge/break in there and can for starters just add to the end somewhere and even make versions of that. Other longer intros are common too. I'll probably save as copy before doing commit either way. Incredibly good job, this is major contribution to CbB.
  5. Arranger track seems really nice. #1. Can you generate a new project from arranger setup - I think Cubase call it flatten project? So you get a new project with all the tracks, some clips duplicated and in order as arranged etc. That you can use as an intermediate tool and finalize without arranger. #2. Can a section be jagged, and bit different from a certain track. Thinking about that drums often has a small fill crash+tom before going in full - but want that kept with full drum track. So define clips to be part of section could be one way of looking at it. You can always split yourself like this.
  6. Yes, we posted on top of each other. And really weird if you get midi activity on midi track meters in Cakewalk for notes, but moving pedal not.
  7. The most useful tool to troubleshoot this kind of thing is a midi monitor http://www.tencrazy.com/gadgets/mfx/ PortDiag will tell the live input when monitor is on. TrackDiag will tell what is played back from recorded material. Very useful stuff. If you notes when playing keys on A800 come through, it could be a midi channel thing. Some controllers send controller on a global channel which can differ from keys in some cases. Others are if omni or all channels are input on midi track in Cakewalk. Not getting activity on meters suggest you might have sustain on a different channel as it is coming.
  8. There are various restrictions of staff view and triplets over all. All notes must be present - and no pauses allowed. Pretty much useless as far as notation goes, I would say. It's been of highly requested for more than 10 years to give some attention to staff view - but so far no luck.....I moved to Cubase for notation because of it.
  9. You can always see if this setting for UTF-8 for worldwide langauages is set to on - turn it off and reboot. https://www.dell.com/community/Windows-10/Default-setting-for-quot-Beta-Use-Unicode-UTF-8-for-worldwide/td-p/7356751
  10. Yes, live movement of those works grouped in Cakewalk. What you don't have is parent/child relation to just write automation on one channel and apply to the rest in group. And you don't have nested groups to have one track control other groups - like vca usually work(unless Reaper and Samplitude which are fake and don't do nested). In Cakewalk now you can only do live write of automation to those and they will follow - not just draw automation in one lane and all will follow. Not record write automation on one track and then apply to others either. As I see it, calling it vca or something else, what is missing is parent/child relation between tracks automation. And in arbitrary levels, that one become master of the others. But if to, in Cakewalk, just do relative movement on arbitrary number of tracks automation - all over the track as they are - the quick grouping thingy I explained above work well. And doing it live with write automation works too - but all is applied that instant and undo will work if to redo again right then . If to draw and nice fade in or out as a ramp is what I do a lot - and to apply that to a number of tracks with vca is nice. So you can work your way to have 6-7 vca's that control like a stem how you want it. You adjust the ramp over and over and when you feel it all is set - burn/freeze/merge that into automation on all tracks as you please. During this process you have double automation lines everywhere - one with final result and one with relative applied by vca.
  11. Most have fake VCA in the sense it only handle faders - and in that case post fader insert effects, like a compressor would be affected by VCA. This is the case for Cubase, StudioOne, Reaper and Samplitude. In Cakewalk you can freely group any individual control, like gain on each track that hits the compressor if first in chain on tracks. It is only ProTools, I believe, that has true VCA that you can group for VCA on any controls. But VCA means parent/child or master/slave relationship between VCA control and anything else - that does not exist in Cakewalk, but highly wished for. In this case you can apply automation to a vca and also apply in a relative way to all the controls that are part of that group. With Cakewalk grouping you can move one control part of a group - and in write automation mode you can have to applied to all controls in that group. Both as absolute or relative(offset mode in Cakewalk). Through extensive testing I managed to move a bunch of tracks automation the same amount, full length over track, by this procedure: - have all tracks in Track View visible with automation lane visible - select them, this will quick group them - then on one of automation lanes hover mouse in upper part of lane, press and move automation up/down. This worked really well, and if having post fader sends on those, those will also be correct in level - so dry/wet relationship does not change by this operation. So would be the same effect as moving a vca the same amount of dB and have that relative movement be applied all over. But true VCA would really be nice, to have parent/child relation from one vca track to all part of that group. Also ability to nesting vca into controlling other vca groups - really nice. But Cakewalk control grouping in general is better than most daws I tried for extensive time, which ProTools was just a short while trialing. Most daws work strictly between the same control being grouped - like pan - and moving pan all pans in group move. In Cakewalk you can use a fader to control pan in a group if you like - you set min max stuff, and can even have reverse on one. Like button maintain the state they are in when put in a group - so some buttons can be on and some off, and flipping one will flip all of them to other state. This is really useful.
  12. Maybe a clue what to look for that can be different - not sure if relevant, just an idea... While I was in transition between StudioOne and Cakewalk, I noticed difference that Cakewalk always handle NRPN as if it is 14-bit values, meaning both MSB+LSB - which StudioOne did not. In StudioOne it was not put together but as separate recorded CCs 0-127. It's possible to send just LSB or MSB, I mean if that matters in how config is done from REV2. You can look in event list view how it looks as recorded. There are some useful midi monitor MFX plugins here for looking at what is sent from your gear here: http://www.tencrazy.com/gadgets/mfx/ PortDiag och TrackDiag both show midi, but PortDiag from live input and TrackDiag what is played back from recorded.
  13. Just a hunch from manual p1475 pdf about a setting "Create Default Drum Map for Non-Cakewalk Files. This option ensures that when you load a Standard MIDI File, you won’t have to create a drum map from scratch—Cakewalk creates a basic one for you." Not tried it - but it could outmap some toms for you.
  14. p317 manual "To use a secondary Snap to Grid resolution By default, Cakewalk uses the global Snap to Grid settings when snap is enabled. However, you can also specify a secondary Snap to Grid resolution that is in effect when holding down the N key. To assign the secondary Snap to Grid settings, hold down the N key while selecting the desired snap settings in the Control Bar’s Snap module. To momentarily apply the secondary Snap to Grid resolution, hold down the N key while dragging or editing data that is snapping to the grid. When the N key is released, the main global snap settings are restored. To swap the primary and secondary Snap to Grid settings, press CTRL+SHIFT+N." Is this what you were looking for?
  15. Interesting how you do Dorico, I'm done with Steinberg though. Keep Cubase installed for notation alone. That Steinberg released Dorico in itself says that there is a damand for good notation, this despite pretty good in Cubase/Nuendo. So really stumped that Cakewalk always rejected the idea to update it. It were among 3 top feature request on old Forum. As long as I did 4/4 only in Sonar 4, and got by quite well for my needs with notation. But as soon as I started playing drums and took lessons and stuff I wanted to start using more interesting beats and it just fails. 4/4 with triplets like shuffle fails already - you must do all 3 triplets, no pauses or anything. Some things I noticed are really simple to do in Staff View is switch a midi track into a double bass+treble clef - which I do a lot mapping strings all over keyboard, cello on left and violins midle and up. So practical to do, as double for readability. Not useful for an orchestra with conductor, just good readability with double staves if doing two handed anything. I do the same with horn section and do baryton saxophone on left hand and trombone+trumpet on right. Easy to read as bass+treble clef. Musically f-ked, but just for own reference. I evaluated Finale full version 2 years ago - and it was a mess with some buggy plugin and result were not good. Only on import could I do split/fusion like that. I had on old Finale Guitar from 2003 that I used before as well, so upgrade would be only $200 or so. But no, did not work. Staff view in Cakewalk is a breeze doing this, just have the midi track and decide split note, and bass+treble and done. If you go a bit wrong, you just redo it again. So some things are a good base to build from. How complicated is this - and so few get it? I ran Notion 6.5 with StudioOne, and it was only on import to Notion if midi track happend to be named Piano you could get double clef/staves whatever you call it in english. And also doing recording could you do into Grand Piano staff as they called it. But not once in Notion you could do this, if you change your mind which is the split note???? A lot of good thinking put into Staff view, and it's a mistake not building further on that, I think.
  16. Yes, it's weirdness above the most for me - never had those PC visible anywhere. I heard only good things about PC stuff, but for me I bought all in Waves 7 years ago - SSL, NLS, CLA compressors, HLS strip - which I use everywhere. So switching daw, I don't need to relearn anything. So what shapes the sound - always the same that I know well. I've was led astray from Sonar, kind of, looking for real good notation built in and landed on Cubase, since that was not more expensive than top notch notation. Figured I continue use Sonar and just do notation in Cubase - but migrated to Cubase Pro all the way for VCA, chord tracks, arranger tracks and whatnot. But waiting forever for new video engine in Cubase after MS deprecated quicktime, I was severly disappointed once it came - so went to StudioOne which did video really well(1/5 cpu same project), and had smooth conversion of Cubase track archives to StudioOne songs in a flash. But now back on Cakewalk, really had forgotten how good it is.....so it was a good thing having everything in 3rd party plugins that I knew well..... ...so a hint to Bakers what can happend when you cannot do triplet based stuff like shuffle in Cakewalk.....true story...
  17. It's like any plugins - there is a limit depending on computer you have. If I were to be aware of it was plugins, put there by intention, I could just freeze tracks and the plugins are releasing resources again. So the effect would be merged into the new audio. In my case unaware they were running realtime, and no need for them either, I didn't do that - just removed them. So remember, any plugins including VST instruments running realtime while mixing can be frozen and you got a system with headroom again. Cakewalk freezing is the best in the business - very easy to do, and you get audio on all outs from instruments as well - this is very uncommon. So smooth to see the audio from instruments and helpful as doing automation, if any, later. As easy to undo as well, if any more recording or editing needed. Easy to forget about freezing....
  18. I did check the template, and it had all gray look as module in console - like it did actually when you first tipped on that that. In Inspector Pro-tab it's so cluttered with fields I don't even know how to see it there. I never had that visible, ever, since I ran Sonar Artist before and did not have it. Really weird, I would certainly have seen that clear lit orange marker that it's active as I short displayed that module in console. Rahter big orange button on gray background. It had activated both compressor and tube saturation on 47 tracks, 94 instances, and also on the bus version extra 2. I guess some kind of macro operation I did with all tracks selected, or some Undo. But only did 3-4 Undo I think on total of this. Not a serious recording serving anything but just reference test which guitars and pickup and amps and processing to use on them, as a training course, kind of. So don't think it was there from start - even if duplicating every track would have picked that up for every new track. Since tracks also were made stereo interleave, which I know I sat and recorded as mono from start. Computers.....can't live with them....can't live without them.... isn't that what they say....;)
  19. It turns out you were all right about that - how the heck did this get turned on. I did check right after you posted - and everything gray in console pro channel module - but now it were orange showing active somehow. Also extra 10% cpu was added that tracks became stereo - and no clue how that happend either. I am 100% sure it was all set to mono with mono input and all tracks marked as mono interleave while recording. So all playing in 11% cpu now.
  20. Thanks, but never used those. I did more test, will add comment in first post.
  21. Hi EDIT. so it turns out prochannels was activated by something, no clue what did that. Project template I started with made - MyBlank - did not have it active - nor did I have it visible, i close that module first thing. Never been in tab in Inspector Pro either either. But I do use Ctrl+A a lot and to makro operations, clicking buttons on/off, inserting sends, changing output destination and stuff. Just relieved I found reason for it, puuuh Discovered some strange stuff today, and didn't really look at cpu before it started crackling. I recorded 40 simple mono audio tracks, each 2 minutes yesterday and all seemed to be below limits - so no crackles or anything. I do solo only one track at a time, so 39 not playing. Added two sends, one to reverb and one to an ir on two busses - routed to master. All fine still. Added 7 more tracks I recorded today, and then it crackles severly every 5-10s or so - on playback thank god, recorded stuff seemed clean. I think it started reaching limit at about 45 tracks total, and last two I recorded crackles a lot while recording. So looked at task manager - just having project loaded it uses 60% on 5 cores, and doing playback on 6 cores - 4 core with HT, of 8 logical cores. So looked at thread scheduling, it was at 1 but set to 2 to try out, restarted and so forth - but no difference. I tried archiving all but 2 tracks - and cpu went down to 5%, hardly noticable. So unarchived again, and tried turn off always run audio through fx in preferences. Then it only uses same cpu while doing playback But what is consuming so much cpu, one wonders? 47 tracks, and one soloed and only playing. I tried disabling the effects, but noticed no difference. I tried disabling sends on tracks and maybe did 2-3% or something. The only thing that made a difference was archiving all not playing. But in simple terms this means I cannot run projects larger than 45 tracks total - with just simple audio - not good. I will export as omf to Cubase and check, and do track archives from Cubase over to StudioOne and come back with report on all. But thought I'd here what is your experience as soon as project grow a bit? This was an experiment just recording electric guitars, with various settings and amps and stuff. I don't even remember when I had crackles on my RME HDSP 9632, if ever. Projects mixed midi and audio summing up to 33 tracks+10 busses and plugin use 30% on 4 cores(15 total as shown) and works fine, as other projects I have in Cakewalk as well. But those originate in Sonar. A bit worried about this. So did tests in Cubase Pro 9.5 and StudioOne Pro 4.6, Cubase 8% cpu, evenly distributed over all cores. StudioOne 6% cpu, evenly distributed - no core higher. Cakewalk 40% total, 60% or 6 cores. I don't run 64 bit audio engine in any of them. EDIT2: I did to complete an import of omf again to Cakewalk - and result was interesting. Cakewalk - 4% cpu same conditions. So difference is two missing sends on each track that seem to be real costly. I will continue and add sends to this imported and see what happends - to be continued.... EDIT 3: So I added three busses, master and two effect busses with same plugins. Then added two sends from each track to these two busses. Result Cakewalk cpu 11% spread on 4 cores. That was a relief. Opening old project cpu 60% on 6 cores. As far as I can tell - exactly the same project. What might go on here? Thanks for any ideas....
  22. I just don't get why manufacturer keep installing these crap piezo's. A couple of years ago I played a Yamaha A3R in a shop. lovely sounding guitar acoustically. But they put this stupid electronic system inside that do this IR thingy, and make it sound miked and a mix knob for that. Not all bad IMO, but still stupid thing when they could either create something like KKsound Pure mini or make a deal with them as OEM or something. Yamaha ruined a perfectly nice build of an acoustic, put very heavy eletronics inside weighing like electric solid body, almost. At least the LL series just have a small passive piezo you can just rip out and replace with kksound. I have a Recording King RP1 with kksound pure mini that I installed. The same with Martin D16GT. Then do a DPA4099G on those as a second mike getting nice stereo and even little phase/chorusing effect from time difference for sound in each mike. Virtaully no room sound, all guitar and wood is what comes through. Taylor ES2 are really good as well, and do DPA4099G on that too, same loveliness. Just overall, why do they do this piezo that nobody wants? Obviously real good guitarmakers - and they put the stamp "cheap" all over it - just don't get it? - Ok, I feel better now doing this rant.....;)
  23. I find that hardware emulating plugins like Waves CLA series and HLS don't like too hot input. Gain knob adjust as said how hot it hits first plugin. If they are going for -18 dBFs or something. So either clip gain envelopes or this overall gain on track is very helpful. If to wish for something it would be that they work on monitor of input as well, which I recall is not the case - only playback. Useful to just increase what you record there as well for more gain, even if using dim on solo.
  24. Many thanks for taking the time. I am on windows 7 - will see if about older project or something, or if different if inserted on bus or track and similar.
  25. Thanks a lot for the effort. But to see redrawing issues you probably don't need the midi stuff, if that was the intent. Clicking to the right of Preset field there should come up a really long preset list menu, all over screen almost. Nothing happends for me, unless running it inside Patchwork. And without that part the midi input is no good anyway. The controls on panel seem to work and changes how it sounds etc. But no cow on the ice, I have functionality through Patchwork right now. But if can confirm I could link to this thread reporting to Cakewalk.
×
×
  • Create New...