![]() Of course, individual instruments can choose how they respond to any CC, such as some orchestral libraries that tie CC1 to volume to make it easier to automate swells. There is, I believe, a SysEx command for setting the master volume (similar to the master tuning SysEx command), but that's rarely used and certainly wouldn't be applied by default. Those are normally the only way volume information is conveyed. Yes, that's what I meant - that CC7 and/or CC11 messages are included in the data stream. Next time I'll be sure to do it the right way. As this is a large-scale, 16 minute piece, with lots of tempo changes, well it took me a while. I had to go back to the original project in Reaper and copy them down, then put them in CbB. On this occasion, although all the notes were there, as well as all CC events and velocities, it didn't have any tempos. Unfortunately I'm not always consistent in how I do things, and I don't do a midi transfer that often. I think I have done it other way in the past. Not sure what you mean by "embedded in the midi data." Do you mean embedded in CC events, or that the midi data itself contains volume information? The imported midi does have all the volume events (CC 7 & 11), and also the velocities are correct. I would think you would need all the midi tracks on different channels before you save it otherwise they might get jumbled. file in the original DAW and OPEN that file in Cakewalk to preserve important data. So the standard practice is to SAVE AS a MID. If you have nothing checked under Preferences/Midi/ Devices/ output then Cakewalk will insert the TTS-1 and all the tracks will play correctly if the file was a GM file. Now if you take that same file and "open" it Cakewalk will create a new project and all the original data should be 100% intact. It will have Velocity, I just did this and checked. It will have nothing, no tempo no synth etc. Take a downloaded midi file, open a blank project and import the file. The project will dictate a lot of parameters, example the projects tempo. This why I'm warning against "Importing" It is well known that if you import a midi file to an existing project a lot of data is not going to be there. If there is, then I'd expect Cakewalk to simply process them without modification, in which it comes down to how each synth interprets volume and expression, as there is no standardization here. You should be able to look at the event list to see if there are any CC7 or CC11 events in there. If the value over the volume slider says "(101)" that means "not sending anything". By default, Cakewalk does not send any MIDI volume commands to soft synths unless they are already embedded in the MIDI data. So I'm guessing volume or expression CCs would be a more likely candidate. That would seem to eliminate velocities as the problem. From your description, it sounds as though the music sounds correct but is just too loud. Of course, if that was happening it would be obvious because every note would have the same velocity. If somehow there is no velocity data in the MIDI file (if that's even possible), then Cakewalk would set everything to the default value of 64. You'd have to examine the original data in another application or (even better) open it in a hex editor to make sure you know what some of the velocities actually are. I don't have a great deal of experience importing MIDI, but my recollection is that velocities are not altered on import. There are two possible explanations (assuming we can ignore the VIs): changes to volume (including expression and aftertouch) or velocity data. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |