David Baay

Oh, c'mon... - Ability to run a lower ASIO buffer in a given project without crackles/dropouts? - More even load-balancing across cores? - Faster/smoother GUI response? - Faster edit/bounce/freeze/export processing? - Projects open/save/close more quickly? - ...?

I would suggest it's just common courtesy to share the bandwidth of the front page of the songs forum, and not post so many individual threads so quickly that one is taking up an undue fraction of the available 'slots'. If one really has no interest in self-promotion, gratification or getting feedback on individual tunes with the goal of improving them, why not just link a bunch of stuff in a single post or just link the top level of your site? I would also suggest that one needs to be doubly conscious of this when posting stuff from a large historical body of work. It seems to me that the primary intent of the forum is to showcase, celebrate and engage in critiquing what people are actively working on at the moment.

Define "better".

It probably is time it came up, given how the thread has evolved, but the OP was asking specifically about acoustic guitar VSTis for parts he had already transcribed to MIDI from acoustic guitar. I assume guitar trackers are optimized to work with DI signals from e-guitar pickups.

Sounds like a plan. A big part of making a sampled/synthesized patch of a real instrument sound convincing is playing with articulation, voicing and melodic countours appropriate to the instrument. Rhythm guitar strumming patterns are difficult or impossible to simulate in real time on a keyboard; finger-picking is easier.

Is this an audio loop that's been rolled out or a normal audio clip with looping enabled in the timeline? If it's looping in the timeline, possibly you're hearing a phasing shift against another track/bus as the timing drifts with each iteration. Otherwise it's pretty hard to envision a mechnism by which the pitch of a 'loop' would drop with every iteration.

Wow. Nice work there, ZincT. Guitars sound great, and vocals are not too shabby, either. ;^) I'm still resisisting buying a full version of Kontakt, but some of the libraries do sound pretty dang good. EDIT: I see OTS supports Kontakt Player. Will keep it in mind.

I'd be interested in having a go at helping you analyze the timing of a track. I mostly record without a click now and snap the timline to the performance after the fact if necessary to quantize or add parts that need to follow a rubato performance. The rhythms of my stuff also tend toward jazz/swing and odd time signatures with inter-mingled triplet and straight 8ths or 16ths. I've gotten pretty good at figuring out what's going on after the fact, often not even being aware of time signature or oddball tuplets (e.g. 3 in the time of 5 16ths) that I'm playing while improvising. PM me if you want to share something.

Which MOTU? I run a 2408 mkii with a PCIE-424, and have not seen this. You might also try resetting the config file completely, using the Reset button in Preferences. A backup is made automatically so you can restore if the reset doesn't help, or compare old and new files if it does. Could also be something about the specific project or template from which is was created.

If I'm understanidng correctly that the clips are not showing any note 'lines', the only think I can imagine is that the track is scaled such that they're not in view. Double-click the scale between the tracks pane and the clips pane to restore full scale. I don't have any bright ideas about the staff view.

Project > Insert Time/Measures is present and working fine here in CbB. Possibly your Workspace selection is hiding it? My Workspace is 'None'. TTS- is also working fine here. Can you share a project in which is crashes? What version of the DLL do you have here: Program Files\Cakewalk\Shared DXi\TTS-1

Anyone have demos they've done themselves of any of these synths? I'd be interested to hear how they sound in the hands of ordinary mortals with middling keyboard skills and limited patience for tweaking synth parameters. ;^) I occasionally write stuff on the piano that lends itself to finger-style guitar. Here's an old example: Red Mountain Reel Pretty sure this used an Alesis QS-8/QSR patch called 'Quiet Time' with very little processing.

When you say it won't play, do you mean the transport runs, but the track is silent, or the transport won't run, or...? To simplify the process, and potentially resolve the issue, try this iin place of export > import > loop construction: - Bounce the tracks to a new track with Source = Buses, and only the Master bus (or some upstream bus to which they all output) selected. - Select the new clip, and Ctrl+L to enable Groove Clip Looping. - Roll it out and check playback.

It's the count-in. Others have periodicaly reported this issue. It's rare enough that it seems to be platform/hardware-specific. I've never encountered it, myself. Usually it's an all or nothing problem. If you're seeing it intermittently with count-in enabled, and can figure out the sequence of events or preference configuration that triggers it, that would be great. Your Allen and Heath mixer-interface is a bit off the beaten path so may be a factor. You might try changing audio driver modes or enabling/disabling UseHardwareSamplePosition= parameter (affects ASIO-only) in AUD.INI (Preferences > Audio > Configuration File). I believe it's enabled by default.

I graduated from college the year MIDI was introduced, but had no awareness of it for several years after that. I had worked a bit with voltage-controlled synths (including a Synclavier) in an electronic music class, but mostly just played acoustic piano, and was not into any kind of recording. in '88, I moved to Florida from Colorado, and left the the family heirloom piano with my sister. A month into piano withdrawal, I walked into a music store to see what the state of electric keyboards was, and found a Yamaha Clavinova set up with a Roland MC-50 sequencer. Twenty minutes later, I was totally absorbed in recording and layering MIDI tracks, and another hour after that, walked out of the store with a slim publication by Electronic Musician that was a thorough introduction to MIDI - I think out friend, Craig Anderton, might even have been a contributor. A week or two later, I ended up buying a Roland RD-300s piano but no sequencer, having decided that a software sequencer would be the better way to go. Six months later, back in Colorado, I bought my first Intel 80286 computer and went looking for a MIDI interface. Cakewalk 2.0 for DOS came bundled with the MPU-401... the beginning of a great adventure.

Right-click the numeric peak value in the track header, and choose Go to Peak.

OP is recommending others to do that, not asking about it.

Or right-click the comp clip in the parent track and choose Flatten Comp to create a new, soloed lane with all clips combined. This is useful in cases where you want to keep the individual takes separate as well as having a combined one. In order not to have them appear in the PRV along with the comp clip, you will want to mute the clips and enable 'Hide Muted Clips' in the View menu. I pretty much always have this option enabled; would be nice if it honored take lane muting as well.

I'm unable to reproduce this issue. Tried with TTS-1, TruePianos, and a hardware synth. None had any volume change after editing in the staff view. Possibly your issue is related to a template as mine was. See if you can reproduce this in a new project started from the Basic template.

I will check this out, but am wondering if just using Replace Synth, and selecting the same synth would re-initialize it - or may even just re-load the patch. Another thing you might try is hitting the MIDI 'panic' button in the Transport module. This sends controller reset messages to all channels of all ports. A slight correction to what I wrote above about Cakewalk sending CC7=64: It was actually CC11 Expression, and hitting the MIDI Panic button would restore full volume by sending CC11=127. The only way to reset CC11 otherwise is to deliberately add a controller event to a track, which makes it somewhat of a 'mystery' volume control.

That's not a waveform. It's either high-density velocity/controller tails or display artifacts at that zoom level. I sometimes see a few stray vertical lines in MIDI clips when zoomed out, but never that extreme. Try zooming in a bit. Normally velocity/controller tails would only show with the Inline PRV enabled.

Hey, Dave, you should just do a quick test yourself. I don't think it's related to streaming performance or buffer settings. It seems there's just some logic issue with the way offset corrections are applied when working on a pair of inputs. Looking back at old threads, it only occured when recording each side of a stereo pair to a separate mono track, not with a single stereo track, which was not made 100% clear in the OP. This was reportedly fixed in the Newburyport release but I don't think I ever personally verified it.

It just causes a general distortion of the audio. I never looked into exactly what the nature of the distortion was.

Glad to help. It's not on by default, and works with mono inputs as you noted.

I thought it was fixed a some point , but I recall there being an issue recording stereo inputs with 'Remove DC Offset' enabled.