Jump to content

bvideo

Members
  • Content Count

    43
  • Joined

  • Last visited

Community Reputation

12 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. One way: any controller can be modified using the event inspector in the control area. After selecting a range, that inspector can change values by n% or by increment +n or -n. By % would flatten or exaggerate the dynamics, while + or - would change the over all level, keeping the same dynamics.
  2. What a pain. The Nord should have just shifted the notes before sending them. As it is, the track you record from the Nord would probably play back correctly on the Nord, but not on other synths. Also, most likely, the octave shift CC will not be sent when switching to a program preset that has a programmed octave shift. Again, not friendly to other synths. It's possible a CAL script could run through a track and replace all the CC 29s with the appropriate octave shifting. Hopefully the CC event has an included value to indicate which direction to shift. And beware sustain (CC-64) messages and also notes held across a CC-29. But the shift in a patch change probably won't be seen and may confuse your entire strategy. Also, what happens when you send MIDI notes to the NORD outside of the configured range? Would a track restructured this way still play back correctly? CAL is a custom scripting language built in to Cakewalk. If you have a programming background you could do it. There are also a few people on this forum that are so skilled that they might volunteer to do it for you.
  3. Occasionally I notice late buffers show up when the song is just over, not while it is playing. No artifacts are heard... Also, my guess is the hidden "safety buffer" in some interfaces overcomes artifacts for slightly late buffers.
  4. Useful info here! But just to clear up my understanding about scheduling VSTi's? Normally there's just one VSTi serving any audio (synth) track. That is to say, the "synth rack" for that track only has one item in it, not a stack. This is clearly different from the case where an FX rack with multiple audio effects serves a single track (or bus). My understanding of plugin load balancing is that each audio effect in such a rack could get a thread simultaneously. That per track concept of load servicing does not even apply to synths. Your last paragraph implies a slightly different concept for synths; it doesn't sound like there is anything preventing running simultaneous threads on individual synths in the synth rack (it's global). In this sense, doesn't it make sense to say there is load balancing among the synths in the synth rack (and there probably always has been)? In this view, for a synth instance that has multiple parts, a single thread has to serve all the parts, even if the parts are directed to separate audio tracks (i.e. for the majority of VSTis, not supporting multithreading). Are there situations where Cakewalk would do multithreading to a VSTi that supports it? That would clear up most of my question (post 5?) about "overhead" of stacking synths. RAM is another part of the equation. For a VSTi that can support multiple ins & outs, how much difference in RAM does it take for multiple instances each with a single voice vs. a single instance with multiple voices. The code part should be shared. For a sampler, if samples can be shared between instances, I imagine there is relatively not a whole lot of difference. But how about for a synth like TTS-1? Does it wind up using a lot more memory for multiple instances?
  5. I'm interested to know how mildly and how substantially overhead might be increased by stacking a mono-timbral synth. Also, I wonder if a multi-timbral synth can run multi-threaded.
  6. I had the problem of my Korg M1 (64-bit VST2) opening properties all blank/white in an existing project. I tried Korg Wavestation (also 64-bit VST2), and the same thing happened. I use the Intel onboard 630, no MSI, no gaming software, only one monitor. The project is fine in Sonar latest Platinum. I worried! The project was last saved by Sonar X2. I resaved it from Platinum, and then those VSTi's worked OK in Cakewalk. Lucky me to have Platinum still around.
  7. I guess my notions of mute and solo come from mixing equipment, where they apply to any signal on a channel. The "soloing tracks" article you posted doesn't say whether it applies to MIDI or audio, and it doesn't refer to the input echo control, or make a distinction between recorded or live signal. The MIDI echo article doesn't refer to mute or solo. So really, the behavior is not spelled out, so it could be anything. It's potentially confusing in its description, and maybe as well in its implementation, since recorded and live signal are merged somewhere along the signal chain, but it's not spelled out for MIDI. I did notice, though, that the behavior for audio tracks is different from MIDI. In particular, solo on one audio track shuts off the incoming live signal on a separate, echo-enabled, track. (simple: project with two empty audio tracks, both echo enabled; listen to audio input through one of them, then solo the other; the audio stops) That is how I expected MIDI to work, too. Here's Cakewalk's audio signal flow. The little tan M and green S operators come well after recorded material merges with live input, so it's pretty clear how audio should work, and it does seem to work that way. I haven't seen the MIDI equivalent signal flow diagram. Sorry I was so late to respond. By the way, I don't use "Always Echo Current MIDI Track". But that possibility just brings up the notion that the echoed "Current MIDI track" with a mute, or some other track with solo, would cause the same behavior as I observed for a conventionally input-echoed track. Bill B.
  8. You could write for Stephen Wright. Actually, here is a Stephen Wright line: "Last night I played a blank tape at full blast. The mime next door went nuts." Your line is funnier.
  9. support@cakewalk.com, for reporting, but no tracking that I know of. It sounds like a bug. Can it be isolated to the playback of just one track or does there need to be a stream from multiple tracks? Generally, people find that those initializing MIDI messages need to be spaced out in time in front of all the notes, otherwise the first notes are all skewed depending on how long the synths take to engage program changes, not just sysex messages. The same might be said for controls & program changes on the same track, namely leaving time after a patch change before the next control. (I come from a world of dino-synths, so maybe today's synths process patch changes or sysex instantly.) Also, MIDI is pretty slow, on the order of just over 3 bytes per ms. That's 1.6 bytes per Sonar's tick at 120 bpm. So putting a sysex in there is guaranteed to delay some of the other messages "on the same tick". Still, order is certainly important.
  10. Oh no. Now I'm getting the impression that solo combined with input echo is goofy too. I echo-enabled two MIDI tracks and soloed one. Data from the keyboard still gets through the non-soloed one. What's more, after I played around with mute, solo, and echo enable, there came a point where all solos and mutes were off, input echoes on, but one of the tracks would not register input on its meter. A few clicks later and it did register. Sorry, no recipe just yet. I sent the original report to Cakewalk support.
  11. Apparently smart mute makes the synth track follow mute operations on the MIDI track, but not vice versa. Not clearly described in the manual.
  12. Gswitz, The icon in the plugin window I referred to is meant to globally set / unset upsampling individually for the particular plugin. It does indeed modify AUD.ini (the list) automatically. From Sonar's Help: To globally enable/disable upsampling for a plug-in, click the FX icon in the upper left corner of a plug-in window, and select Upsample on Render or Upsample on Playback on the drop-down menu. These options globally persists for all instances of the plug-in in all projects, so it only needs to be set once per plug-in.
  13. Dave, Some of those MIDI activity flashes seem weird! Too bad MidiOx wouldn't work there. There is an explanation of instrument track muting in the Sonar help file. There's a reference to "smart mute". "Smart mute" describes a setting that can be accessed in the Synth Settings menu. Maybe you and I have different settings there. My "Enable Smart Mute" is checked. For quick reference: --------- from Help: ----------- Smart Mute for Split Instrument Tracks When a virtual instrument MIDI track is soloed or muted, SONAR automatically manages muting or soloing the related set of audio/MIDI tracks in order to properly playback the soloed/muted tracks. In order to facilitate audio recording on Split Instrument Tracks, Smart Mute is no longer the default behavior for Split Instrument Tracks. By default, you can now individually mute individual split MIDI/audio tracks for soft synths. If you want to enable Smart Mute for Split Instrument Tracks, open the Synth Rack view, click the Synth Settings menu and select Enable Smart Mute on the drop-down menu. Bill B.
×
×
  • Create New...