Apparently Cakewalk 7 Studio dates from 2007 - am open to later things if better, but only if they're as simple for laying and editing tracks. I've been changing them manually as tracks play all these years, but if there's a better solution let's have it. Ditto when it's time to use them during a church service. It may recall them fine right after setting them, or not. Suggestions as to what General MIDI should have been called - Standard Soundbank?Īlso, do you folks have any idea how I can get Cakewalk Sonar to register those sounds reliably on my circa 2005 Rodgers church organ, as it does the organ stops per se? IOW, I can set any combo or variant of its organ's sounds - those reach through tilting stop tabs - and Sonar will record and recall them perfectly, but the organ's orchestral patches (wrongly called 'MIDI' right on the console) only irregularly. But this misnomer has been built into how many million instruments now It merely is set up to respond to midi data received, and emit the actual sounds generated.Įxactly the answers/confirmations I wanted. The 'midi sound module' you refer to is really NOT midi at all. #REAPER CAKEWALK INSTRUMENT DEFINITION FILES SOFTWARE#The above stays the same for virtual devices, and virtual synths, where you should see the soundbank setup as being a software implementation of the old style sound module or keyboard, which receives midi instructions from a midi 'controller' (or software), even though the two devices might be within a single computer and appear to be a single unit - still - the midi data is being generated by one part, and being implemented (and turned into the actual sounds) within the soundbank part. samples) which MIGHT change this current answer, but I think even the new spec will work mostly i the same way the current spec does. I think that the new (coming) midi spec could allow some sound data to be sent WITHIN midi (i.e. If both devices are GM, then the results could be very similar, but still different. Hence the same set on instructions sent to one device could produce a different result from the same instructions sent to another device. The actual sound is totally the responsibility of the device that receives the midi instruction. Midi is simply instructions to tell other devices what sounds to play, and to make certain modifications to those sounds. Thanks.I think from your comments that you do understand that there is actually no such thing as 'midi sounds'. If this info would be better in another sub-forum section, please move it. #REAPER CAKEWALK INSTRUMENT DEFINITION FILES ZIP#(That forum did not allow zip files or any other odd filetype to be uploaded, hence the simple copy-from, paste into notepad, save-as *.ins. #REAPER CAKEWALK INSTRUMENT DEFINITION FILES CODE#When copied from their respective code list-box in that post and saved as an INS file these can be loaded into Reaper, as-is, with the add-on plugin pack that includes the ReaControlMIDI plugin. They can be found in another forum, posted here CTK-4000/5000 WK-500 Instrument Definition for Cakewalk () While doing so I created three INS files for the 8 following Casio keyboard model numbers:ĬTK-4000, LK-270, & WK-200 (all use the same file)ĬTK-5000, WK-500, & CDP-200R (all use the same file)ĬTK-6000 & WK-6500 (both use the same file) I tried to find an Instrument Definition file for my keyboard model number and realized I'd have to create my own. Unfortunately, not many people realize how much Casio boards have improved in the last few years and 3rd-party support for them is sorely and mistakenly lacking. A heads-up for anyone needing an Instrument Definition file for some Casio keyboards.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |