David Baay

TLDR

Sure sounds like the pedal is not generating the full range of resistance. I'm not sure off the top of my head what the convention is, but would guess theres a high-resistance connection somehwere so it's never getting as close to zero as it should and limiting how far down the messages will get. It could be the opposite - that there's current leakage when it should be open circuit - but that seems less likely. Maybe take the pedal apart and check for cold/broken solder joints, etc.

The pedal just presents a variable resistance to the keyboard's pedal input. The circuit behind that input passes a small current through the resistance to translate it to a voltage drop which is in turn used to determine the level of controller mssages. It's the keyboard that generates the message, not the pedal. If the messages are not covering the full range, it's likely down to some keyboard configuration estting, but it's possible the pedal isn't generating the full range of resistance from near zero/closed to effectively infinite/open circuit. You can test the keyboard by plugingon/off-style sustain pedal into the input, and verifying you get 0 and 127.

CbB has been slow to open Keyboard Shortcuts for a couple-few years now. The Bakers have never really acknowledged that this changed suddenly from one release to the next. It's only 2-4 seconds on my machine now. The response time can vary, depending on some unknown factor, but I don't think I've ever seen as much as 15 seconds (!).

Okay, I stand corrected. Weird. Tools seem as sharp as everything else here on both my displays (3072 x 1920, and 1920 x 1200) though their styling has not changed so they don't have the fine, crisp lines of many new elements.

Imperfect 17.06:8 aspect ratio? Seems unlikely. I'm thinking maybe you confused the width with a 3070 RTX model number...? A more conventional 16:9 aspect ratio would be 2560 x 1440. If it's really 3070, I wouldn't be surprised that you might encounter scaling issues.

That was my approach originally, but I actually found it more 'fiddly' and error-prone to get all the notes deselected without accidentally de-selecting articulations or altering the range. But it just now it occurred to me to try Edit > Select By Filter, and Articulations are there in the Special Events section. So you can make your selection in the track view, then Select by Filter, click None, re-check the Articulations box, and paste.

MIDI files do not have the capability to store time offsets of any kind, ticks or milliseconds. CbB generally renders any non-destructive MIDI effects/transformations into the MIDI events on saving as MIDI, basically the same as it does when rendering MIDI through a soft synth. I haven't tested this with articulations but I would expect that to be the case.

Yes, this makes it much more flexible and useful for accomodating the variable attack times of an instrument's various articulations throughout a track. The appropriate offset can be built in to each articulation so it's completely transparent. I understand the desire some users have expressed to be able to just plug in a fixed absolute time offset at the track level like the Time+ offset in ticks that we've always had, but once you've defined a particular absolute time offset and saved it in your articulations library, it's quite easy to add it across the entire length of any track that needs it.

I hear you. That put me off as well.

Immediately to the left of the Read button in the Mix Module. Enable it to set an offset, and then disable it get back to Envelope mode in which mix changes and automation envelopes 'ride on top of ' the offset. When in Offset mode, there are '+' symbols on the controls that can be offset. You need to remember to turn it off after making a change or your mixing will get confusing.

More like excluded on Saving. Track templates are only setting routing data, not content.

Haven't checked plugin scan, but export notification and location is working here. Check Preferences > Customization > Display > Notifications. All should be enabled on by default but maybe it inherited a non-default setting from somewhere.

Yes, in the Tracks pane for the PRV select the the last track you want articulations from and Lasso or Ctrl+Click the articulations you want. Then select the next highest track and Ctrl+Lasso/Click to add to the selection. If there are more then two source tracks, keep working your way up until you've got articulations in the highest (i.e. lowest-numbered) track selected, then Ctrl+C to copy, set the Now time for the paste, and Ctrl+V. The reason you want to start selecting from the last track is so that the uppermost track you select from will be the starting point for the paste so everything goes to its respective track. But beware of targeting issues that may occur if there are uninvolved tracks in between. Ultimately you may find it more predictable to just do the tracks one at a time, depending on the complexity and whether all the tracks are adjacent. The other option is to do it in the TrackView, but then you have to jump through some hoops to exclude notes from the copy.

Okaaay... that was interesting. I went back to my DAW and Next was nowhere to be seen, shut down, crashed, outta here, abducted by aliens. I re-launched it and none of my audio setup was recalled. It was back on WASAPI and I had to reset everything. I then closed it deliberately in hopes it will store the setup for next time. I then re-recorded, (including getting the distinctly slow metronome until I changed it), and I'm able to repro your issue. If I pre-roll from the start with a 1-measure count-in, my two-measure punch-in at bar 5 ends up being the silent count-in and the first bar I played. I'll see what I can do to get the message to the Bakers.

🤣 Sorry, but that had me seriously laughing out loud. I dunno, John. It worked for me. Sounds like it's having some issue with your audio clock, but if the same happened with a different interface... I dunno. Are you saying it places what you were playing during the pre-roll in the punch region? I realize playing along during the pre-roll is SOP to get a smooth transition, but I didn't actually do that; I started playing at the punch in. I'll try it your way.

Yes, I recorded audio from my digital piano being played in real time via Local control. No MIDI involved... but also no microphones. Line in.

Enable Offset mode in the Mix Module and offset the Volume. Volume Offset can go to -INF.

I saw your post about this previously. I hadn't really done much of anything with Next but thought I'd give this a try. I hadn't even set up my ASIO interface with it. It took a couple minutes to figure that out, and just a few more to open a default 4-track audio template, record 8 bars, and then punch in a couple in the middle. It took me a minute to figure out that looping had been enabled by default when I set up the punch, but after I got that turned off, I was able to get a pretty decent punch right away; the timing seemed fine. FWIW I was recording from my digital piano under Local control, input monitoring through Next. The only weirdness I encountered that didn't seem due to user error is that the metronome showed 120bpm, but was clearly running much slower than that initially, like 90bpm even after several restarts. I cranked it up to 150, and it was running about as fast as I would have expected for that so I set it back to 120 and it was right on what I expected in the first place. EDIT: I'm not a regular Discord user, but had visited the Next server previously and posted a couple of times. A link for it came right up when I logged in, and there are recent posts.

A basic keyboard split by note number can be done with Cakewalk's included Event Filter MIDI FX, putting the FX on multiple Instrument track to allow/block complementary key ranges . But what he's showing after that point with separate outputs per string seems clearly a function of MIDI Guitar 2 itself, and I'm not familiar with it. I would guess each string is assigned a channel.

Yes, unfortunately Track templates won't save articulations because they're stored as MIDI events, and track content isn't saved in Track templates, but Project templates can save MIDI content, including articulations.

Cool. Strange that normal clip export wasn't getting the job done but maybe there's some small difference in the way Time Signature metadata is formatted in Groove Clip files that Beat Buddy likes better.

I little bell went off as I was thinking about this. If you're "exporting" by dragging the clip out of CbB to the file system, that could be the problem. File > Export and Save As MIDI will include tempo and time signature but drag and drop will not unless you first convert it to a MIDI Groove Clip.

I don't know what the convention is for encoding Time Signature in a MIDI File, but I verified that CbB can read a non-4/4 time signature from one of its own exported/saved-as MIDI files on re-opening it, so I'm not sure why another app wouldn't, unless it's looking for some other indication. You are setting the time signature in the Transport module in CbB, correct? As you know, Cakewalk goes back almost to the dawn of software seqencers so it would be pretty weird for it to be doing anything unconventional in this regard.

I can repro that soloing the folder visually solos all the Aux tracks, but audibly solos only one (seems to always be the most recently created). And it's the Input Echo on the Aux track that's not being preserved. If there's an audio clip in the Aux, you'll hear it. I don't recall seeing this issue mentioned before.