bvideo

All the references above to "zoom" are not referring to the clips pane zoom controls but the per track zoom, which refers to the range of midi notes that can fit in one track display. (There is an audio version of that as well that refers to the waveform display.) Did you try sjoens' instructions?

Perhaps that track is zoomed in too far to see all the notes.

A multiport midi interface supplies a group of ports in one USB connection. When that is the one and only MIDI interface on your computer, the order and friendly name assignment is never lost. Example: midi express 128.

There's a basic issue with USB MIDI interfaces: the standard for device configuration does not include a serial number or any other unique ID for MIDI interfaces. Therefore, it is difficult for the OS to distinguish one from another. Only if you are lucky, when you boot Windows it will find the interfaces in the same order it did last time, and thereby match up with the friendly names. If you ever unplug/replug one, or if reboot or sleep/wakeup finds them in a different order, they will not match up. There are some other discussions about this (example)

Sending the DRM from Cakewalk should be asking for a channel number. That number needs to match a global setting in your M1. I can't find my old M1 manual just now, but is it possible the channel number is 1-16 in the global setting but 0-15 in the DRM dialog... Same consideration when sending a sysex dump; the channel number in that sysex needs to match the M1 setting.

Does this happen with more than one particular synth? There have been unfreeze problems before related to at least one specific synth (sektor).

In the manual, it seemed I could see a playback mode (how to transmit your composition) to an external synth|host (cf Cakewalk) in such a way as to transmit the bank/prog numbers. When cakewalk receives them, it will populate the track header widgets with the corresponding names from your .ins file. As far as your latest problem, it is best to save your project as a cakewalk native project (.cwp) for reopening to continue editing. You can write your .mid file separately for sending directly to your synth. A .mid file can't hold all the information of a Cakewalk project, so is not good for revisiting / reediting.

I wonder what you are actually doing in Cakewalk. Almost sounds like you are composing on the PA900 and just using cakewalk to create a midi file. But it looks like you don't really need cakewalk for that. Isn't there some way to save your PA900 composition to a midi file on a local thumb drive or to local storage? Most likely, that file will have all the required sound setup. It looks like you can make the PA900 look like a hard drive to your PC. Then save your composition to the PA900 internal storage and then copy midi files from your PA900 to your PC. I looked very briefly at the manual, and it looks like you can do without Cakewalk. Or if you want to use cakewalk, it looks like you can configure your synth to send program/bank changes so CW will have them for writing a midi file. (See pg 121)

If you chose banks/programs for your tracks in Cakewalk, they will get saved to your midi file and sent to your PA900 before playing notes. But maybe you set up the sounds in your PA900 instead of in Cakewalk. If that's so, playing the MIDI file has no information how to set up your sounds. Whatever sounds the PA900 already has set up by default will play, probably piano. You can: 1. see if the PA900 has a way to save a setup of your sounds, then load that setup when you play that MIDI file. 2. look into how to set up bank/program numbers in cakewalk. First, see if there is a publicly available .ins file for the PA900. And check the cakewalk manual for how to install and use it. Otherwise, try to read out the bank and program numbers from your PA900 setup and enter those raw numbers into each track's bank and program number widgets in the headers of the tracks. Either way is how Cakewalk knows which sounds to play in your PA900. 3. there may be a way to transmit your PA900 setup into cakewalk so it can be made part of the MIDI file. That involves transmitting a sysex dump from the PA900 into your Cakewalk project so that when you save the project as a midi file, that setup dump will be sent to the PA900 in preparation for playing back with the correct sounds. See your PA900 manual for how to send the sysex dump and see the CW manual for recording it and putting it in the song.

The usual reason is mismatching sample rates between Cakewalk's setting and the audio interface.

It's an odd choice in the Korg SV-1 if, as it seems, note-on velocity 0 is treated as a note off at max-velocity.

Which synth are your G2s being sent to? Does that synth actually play G2s or does it have a limited range (as some synths do when they are trying to emulate real instruments)?

When you are in INTRANET mode do you have a DNS that will return a failure notice right away when some program makes a name request?

Interesting - when I go to start a disk check from properties->tools[check] on an NTFS drive, it says: " You can keep using the drive during the scan. If errors are found you can decide if you want to fix them." That makes it sound like it's not unmounted. Perhaps you are using CHKDSK differently for a special purpose.

What format is your D drive?

Supposing that it is taking time loading up audio files to start playback (more files, slower startup), maybe it's worth playing with the file I/O settings, such as buffer size and caching. If other daws are very different in this scenario, maybe they are optimizing by preloading the audio whenever the playback cursor lands, not waiting for a "start playback". Hard to imagine any other differences. Related issues may be the speed of your drive and the fragmentation of your recorded audio.

Besides DC offset it could also be an extreme low frequency component. Also, it could be the nature of the waveform, which could have equal energy but different maxima on the plus or minus side of center. There's some discussion about these things here.

In Kontakt. Do they let you edit or view the instrument definition? But then what can you do about it? Can you do a single tempo change just before that note is played? Or just after it stops?

Check inside the instrument definition for that MIDI piano. That same thing happened to me with Dimension.

Tempo change ought not affect a sample. Could be a tempo-based effect, either part of the instrument definition or on the audio path.

"Pressing Enter": this may trigger focused buttons.

You can create a junction on your new F: that directs the system to find the files in the folder on H:.

FYI for future reference: the term "class compliant" does not apply to ASIO. Most operating systems provide a common driver for "class compliant" devices so they will work with the driver model(s) built into the OS. But Windows does not provide ASIO, so class compliant doesn't apply. P.S. The term "class compliant" refers to compliance with the USB specifications for device classes. Device classes include audio, mass storage, midi, and several others.

Switching back and forth between program and combination mode: if it's a Korg, it will transmit a sysex when you push the button. Capture each button into a Cakewalk sysex bank and you can embed them in each track where you need them. Other makes probably do something or other on their MIDI out when you push buttons, so same idea.

User 905133, I'm very sorry for all the confusion. I meant to say that your rewording ("Your recent take") of my earlier post was right in its overall effect. My quoting of your modified quote of mine lost the color from your post, as well as the notion that I was requoting your modified quote from me. I haven't yet found post numbers to help make references to previous posts more precise. Now the quotes are looking nested, and that's getting confusing too. My original "strictly speaking" post was in response to trying to draw a parallel between Cakewalk's echo input and standalone MIDI module connections. I think that was 12 or 13 posts back*, so a lot of posts have intervened. As far as the workflow you mentioned in the post 2-back* from here, yes I agree it's convenient to automatically mute previously recorded stuff that we are rerecording. I think Cakewalk might have attempted to cover that with the various modes for recording and take lanes and such, so previous takes are not heard while we are rerecording. Same situation for audio too, I'm guessing. The old old original resurrected post was not about recording. * my post counting does not take into account what happens when someone posts while I am still typing.