bvideo

Was surprised to hear an external synth playing notes from a muted track. Input echo was enabled, and a keyboard controller (independent of the synth) was sending notes matching that track's input and output channel. The notes previously recorded on the track were properly muted, but the notes received live were not muted. With the track muted, the MIDI meter does not move even when incoming notes are echoed. This is different from the way the audio signal works; incoming audio on an echoed track is immediately silenced when the track is muted. It's also different from the way an instrument track works. MIDI being echoed is immediately silenced when the track is muted. However, when the instrument track is split, it is revealed that both the MIDI track and the synth track are being muted & unmuted together when the instrument track is muted/unmuted. With the track split, operating the MIDI part's mute operates the synth track mute as well. However, operating the synth track mute can be done independently. Then ( after the scenario described below) it is revealed that when the paired MIDI track is muted and the synth track is unmuted, the synth plays incoming (echoed) notes! The MIDI track meter does not move, while the synth track meter does move. A further oddity is that the behavior of the paired MIDI/synth track changes after an unrelated audio track has its echo button turned on. Before doing that, the unmuted synth does not play the notes from its muted echo-enabled MIDI track pair. Afterwards it does. I can't guess why this would be intended. Generally, that behavior of mute on a MIDI track wouldn't seem logical to me and I don't remember it being that way. But it seems to work that way on both the most recent Sonar and the most recent CW. The changing behavior of the paired MIDI-synth tracks also doesn't seem logical. Did something change? Did everyone else already know about this?

Thanks for that info, guys. TC has maker's access to DICE driver updates. The drivers for my Alesis were last updated June 2010. Have used them in less recent W10. Just now I tried them on W 1903 and they worked, but twice there were weird events that made me have to restart. W10, 8700K, 16G, Alesis Multimix F/W 16 Roland A90EX, JV80, D50-MEX, some Korgs.

Uh oh, Some of those Saffires are DICE-based. Drivers were always dicey. Any word about any other DICE-based interfaces going belly up in 1903?

OK, right. I was thinking of the per-track PRV

Give a try holding shift while dragging the notes up or down to another track.

I'm going to guess that the inclusion of the reset message at the end of the song could be troublesome in another way: you played the song to the end and now you want to play from somewhere in the middle of the song. Too bad, the GS got reset and the setup messages don't get sent, so the synth doesn't play right. Other MIDI events, such as CCs and program & bank changes (and optionally notes) are "chased" up to the point of starting playback. (Meaning Cakewalk sends the contemporaneous values of those events, and optionally notes, before starting playback at a given point.) But that sysex message that changes channel 11 to rhythm doesn't get chased.

It's possible to turn off the rechannelizing of a midi track so that the channel numbers of the notes in the track are not modified when sent to the synth. Then you can use all 16 channels in one track, if that helps you access all the articulations. Look in the MIDI track strip for the Channel parameter and set it to "none". When you need to change the channel numbers of individual notes, you can use the "Event Inspector Module" in the control bar to operate on selected notes. OTOH for 2) moving notes in place can be done while holding shift when dragging selected notes.

Arvada, CO

There are many kinds of MP4 files. The mediainfo program is a good way to report the detailed video properties of a file you have problems with. Maybe someone on this forum will be able to match up with your file and help you. If not, send the mediainfo details to the Cakewalk team.

When the machine crashes and reboots, it may be that the only available info is the system event log.

There are some subtle house power wiring mistakes that can cause large 60 Hz EMFs intermittently. If the hum goes off and on with nearby lights or appliances, there could be a split neutral.

Copying a vvocal (or melodyne) clip is naturally more complex deep in the s/w. Not just audio needs to be copied, but all the parameters that were made in editing. E.g. each copy should then be able to be further edited independently. Early region fx of Melodyne had an easily reproducible bug in that regard. Just to offer help tracking down the situation, is it possible to get a different result using explicit (separate operations) copy and paste?

A project of mine had weird popping during silence and I traced it to "plug-in load balancing". If you still have a version of the project that has those pops, and it's not too much trouble, maybe you could try turning off plug-in load balancing (Edit > Preferences > Audio - Playback and Recording, just below the "Use Multiprocessing Engine") to see if your weird phantom noises go away. If so, maybe you could send in your trouble report. (Mine in the old Forum)

Just to set expectations for dump popups posted in the forum: There is very little in the popup that can be used by us users to "help the OP" with any substantial info. The only readable detail in this one is that the code that failed by referencing a non-existent memory address was in the plugin, not the host. That doesn't really prove one way or the other whether it's the host or the plugin that is behind the failure. We've heard a few times about how a plugin "does things differently", and the host wasn't expecting that, and the host can tweak code to make it work (an example of Starship Krupa's grey area). But given how many plugins have needed fixing, I agree with John's observation to this extent: it's less often the DAW's fault (but I guess there is no data available to prove that). In this case it just confirmed the OP's observation that the crash probably happened while the plugin was processing parameters (or e.g. could have been processing audio while a parameter changed in an "inconvenient" way) after a freeze (which could be a clue as to why it would crash in one DAW and not another, given different or non-existent implementations of freeze). Some future poster might not have a directly observed cause & effect. Then if the crash happens in the code of a plugin, the popup would be giving the possibly helpful clue of the module name.

Setting the tempo from the control bar inserts a tempo change at the current "now time". That may be why it seems like you are changing tempos only for certain areas. You can view and edit/delete all the tempo changes in the Tempo Map view as Cactus Music guy says.

There are restrictions on Region FX. Maybe regions that have audiosnap or groove clip looping are denied region FX. The reverse is true, namely that looping and audiosnap are disabled within a region FX.

A comment about the rewind and playback problem when you have advanced the timing on a track or some notes: it is possible to enable MIDI note chasing so that notes that started before your playback point are triggered. From the manual: You can now start playback from the middle of a MIDI note and the note event will trigger and sustain for the remainder of its duration. You no longer need to start playback before the note start time in order to trigger the note. To enable/disable MIDI Note chasing, go to Edit > Preferences > Project > MIDI and select MIDI Event Chase on Play and Include Note Events.

@Phoen1xPJ: PCI for your Layla may be getting harder to find on a MB.

A quick look: track 4 has patch changes. Around 41:04 is where I see a patch change and hear it change from synvox to accordian. Have you checked the view menu to make sure patch changes have not been filtered out?

Good news! Dave Baay, the poster above, was is brundlefly!

If the start time is the problem, and if the whole performance is off by the same amount, then it is not quantizing you need, but just shifting the performance to the right start time. If that's it, the root cause could be that there is some inherent latency in the playback of whatever you are playing against in the project, be that a metronome or a prearranged accompaniment. Usually, a recording is aligned (after the fact) when played against a project with latency, but sometimes things can go wrong with that.