Jump to content

Michael McBroom

  • Content Count

  • Joined

  • Last visited

Community Reputation

11 Good

Recent Profile Visitors

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

  1. Nope, I'm using CW's TTS-1 for GM, and just its default setup protocols. The audio trace is there before I do any bounce to combine tracks. And yes, since it's actually a chord that's bleeding through, I suspected it might be a MIDI track, so I checked the most likely culprits -- MIDI guitar and keyboard tracks. Nope, nothing there. It was definitely in the audio. I ran into this again with the same piece of music, but in a different spot with a different guitar. This guitar is a Gibson with P90 single coil pickups that can be rather noisy. There's a four bar intro to the piece, before the guitar part starts and, during playback, I couldn't help but hear a rather pronounced bit of line noise in the guitar's audio track while I waited for the Intro to complete. So I highlighted the noisy "dead" area before the guitar started, then I used the Edit>Cut command to remove the snipit from existence -- or so I thought. Now, the way it sits, the audio channel has no signal from the beginning of the tune to the end of the fourth measure, but if I solo that track, I still hear those four measures of line noise. Strange, eh? I got to thinking that it may actually be the Auto Save function causing this, since a save was done right before I deleted that section, and I was wondering if that, somehow, was messing with things. So I deleted the Auto Save file and tried again. Nope, line noise is still there. Not a huge issue, but an annoying one. I used the "Write" function to reduce the audio track's volume to "0" prior to the start of the 5th measure.
  2. That's just it, though. I deleted the audio track -- or at least I thought I did. It doesn't exist anymore, far as I know. It certainly doesn't appear anywhere. I've never hidden a track before -- I'd have to consult the CW online Help just to find out how to do that. Frustrated over this whole business, I learned a lesson. I should have saved the file before I recorded the audio. But I didn't. And in fact, I'd done a lot of work on the project before recording the guitar part, to make things worse. I ended up having to rebuild the entire piece. Fortunately I had clean components of it that I was able to reassemble, but it was still a time consuming process. Took me all afternoon yesterday getting the project back to where it was before I made the recording. Lesson learned. I'm still baffled and really curious as to why this happened, though. Hopefully it doesn't repeat itself.
  3. Thanks for the additional info, guys. Well, for starters, I did try WASAPI but it was giving me problems. The piece of music I'm working on right now is fairly large and, even though all tracks are MIDI, there are 22 of them, although only 10 and 12 instruments are playing at any one time, respectively. Nonetheless, at least about half the time, roughly halfway through the piece, it would fall into a state of total distortion. If I paused and restarted it, the distortion would clear up and usually go away for the remainder of the piece, but this was unacceptable to me, so I went back with ASIO. And yes, my interface has ASIO-specific drivers that have always worked very well. I've been running the amp's audio out into the interface. I prefer this method over a microphone because of the ambient noise level I have to deal with here. Some CPU fan noise and also a cockateel in the background who likes to chirp at unpredictable times. And occasionally the dog decides to bark. The downside to running straight from the amp to the interface is I'm picking up some line hum now. Nothing very serious, but it's there, raising the audio floor. I can probably nail the hum with a parametric EQ -- haven't tried yet. Next time I'm working on a smaller piece, I'm gonna give WASAPI a try and see if CW will recognize the amp as audio. I never did try and see if that would work, since I was running into problems with that driver mode.
  4. Thanks, I'm gonna give WASAPI a try first. I don't like ASIO4All, I've had problems with it taking over my system and not wanting to let go.
  5. I'm working on a piece that, at the moment, is 100% MIDI. Earlier, however, I recorded an audio track of guitar. But I wanted to keep this file clean of audio, so I renamed the file with the audio, then I deleted the audio track and saved it to its original name. When I bounce to tracks so I have an audio copy of the song, there is at the end a leftover sound from the audio track. Immediately after completing the bounce, this sound, well it's a chord, actually, continues until I stop the playback. But it is only recorded up until the end of the piece. That in itself is strange. It reminds me of when a MIDI instrument will sometimes get stuck on a note or a chord, but this is audio. This sound is only audible after I've bounced to a new track. When I play the song back, there is no trace of this leftover audio, and there shouldn't be either since there are no audio tracks anymore. To attempt to rectify this, I exited the file, and called it up fresh from memory, then did the bounce to tracks again. Same thing, the audio "ghost" is still there. Taking a look at the bounce options, I decided to try setting the Source from "Entire Mix" to "Tracks," reasoning that, since only MIDI tracks are present, it couldn't pick up any leftover audio. But it still does. Next, I tried different driver modes. Normally I use ASIO, but I switched to WASAPI Exclusive. Same result. Then I tried WDM/KS. Again, same result. I didn't bother with any of the others, figuring I'd get the same result. Well, I'm stumped. I don't know what else to try -- and I don't have a clue as to what is causing this. One thing I just thought of. What if I record an empty audio track to this file. Would that possible overwrite whatever has gotten stuck in the works somewhere? I'm gonna give that a try and I'll report back. Welp, that didn't work either. So I just recorded an empty audio track, saved the file, then tried bouncing to tracks, but this time I selected "Entire Mix." Reason why was because when I selected "Tracks," the Bounce routine created two tracks -- one a recording of the MIDI and the other a recording of the blank audio track. I didn't want that, so I went with Entire Mix instead.
  6. I almost always use ASIO. Which other one would you recommend? I guess I can just start with WASAPI Exclusive and go down the list. I don't know what WDM/KS is used for.
  7. I have a Marshall CODE 50 amp and I'm trying to use its USB out to record audio in CW (I just installed the latest version of CW btw). The CODE comes with no drivers and there are none available from Marshall. Marshall claims that its CODE amps are fully USB compliant, so they need no drivers. I have gotten this amp to work in Band in a Box just fine. It found the CODE and recognized it as an audio device. But in CW it shows up only under the MIDI inputs and outputs, which obviously doesn't do a bit of good. I guess I'm wondering, is there a workaround for this, or must I use my audio interface and forget about the amp's USB out?
  8. Okay, I've run into two separate issues with two different pieces, but the problems are at least somewhat related, I suppose. In the first instance, I have a piece of music where I spliced in a few sections from other MIDI files into a single track. The instrument traces that are shown in the track view are not complete. There are large gaps where no trace is showing, even though the notes are being played. They're visible in the Staff and Piano Roll views, just not the traces. This is mildy annoying, and it's a problem I run into on occasion. I would like to figure out how to get all the notes in every MIDI track to display in its trace. The second instance is worse. It's another example where I have pasted in excerpts from MIDI files into a single track. In this case, the trace is complete -- no gaps. The Piano Roll shows the complete piece, which is 32 bars long. But the Staff view shows only 12 of the 32 bars. I've never run into this before. I tried selecting different editing tools (Smart, Select, Move, etc.) and even double checked that I had highlighted all 32 bars before clicking on the Staff View (I had). Since I had imported MIDI files into a New file, and hadn't saved to Cakewalk format yet, I thought that might be the problem. So I saved it as a Cakewalk file, and then called up the file from the disk. Still nothing past bar 12. The music is there. Playback works fine. I just can't see past bar 12 in the Staff View. Now, this is a big deal for me since I do almost all my editing using the Staff View. Not being able to see the music as I move forward will be a big problem for me. So, got any ideas what I might have done to cause this? EDIT: Something else I just tried. I used the "scrub" function (hit the "J" key to activate and deactivate) to scrub through the notes and all the notes in the measures beyond 12 scrub just fine. So they're there -- just the Staff View is refusing to "see" them.
  9. Thanks much for your replies, guys. I've been quite busy these past few days and this is the first chance I've had to check back in. Looks like I have some homework to do. Thanks for the recommendations. I'll check into them. I agree that the term 'multitimbral' can be misunderstood, but this is the term that is used when one is referring to a synth that can play more than one track or part or instrument at a time. My DAW is an older machine that still has respectable numbers -- on the surface at least. It has a quad core AMD processor and 16 GB RAM, and I learned recently that the thing to look for in multi-core processors, especially when they'll be used in a DAW application, is the speed of the individual cores. I think that's where my machine is taking a hit. I haven't run a test on it yet, but it's the only thing I can think of that will explain the overhead issues I'm experiencing with some of my larger pieces of music. I've found that some synths have more demand on resources than others and that when I stack them, I quickly run into overhead issues -- Rice Krispies in the playback (snap, crackle, pop, donchaknow) and even playback audio dropouts. When I incorporate audio tracks the problem quickly becomes worse. I don't know what you mean by "multi-threaded," unless you mean multitimbral.
  10. Cakewalk's TTS-1 is the best multi-timbral synth that I know of. But I would like to find others that have instruments besides the standard set of MIDI instruments. So far, I haven't found any worth mentioning that are available for a reasonable price (say from Free to under $100). I'm sure they exist though. Care to mention any of your favorites? I'm interested in finding other multi-timbral synths in order to keep the overhead to a minimum. Sure, I can stack mono-timbral synths, but with the increased overhead, which can range from mild to substantial.
  11. Scook, thanks, I'll take a look at that link. mdiemer, that's a good point. I have MuseScore3, which I do use on occasion, and I've found that it translates MIDI files very well. But when it comes to fixing aspects of the notation, I'm not so sure it would be any sort of time saver. It definitely looks prettier when it comes time to print something out, though. Actually when I print a file I prefer the traditional jazz leadsheet look. You know, melody on a single staff with chord symbols above it. I find this to be most useful if I want to read through a piece. And for that, I find that Band in a Box still works best for me. Only problem with BiaB is it does a lousy job of handling MIDI imports, tending to make a complete hash of things, so it's only really useful if I've built the tune in BiaB. By the way, I did find a much faster way to edit my MIDI file, changing those dotted halves with leftovers to whole notes. I saved the symbol for the whole note, "4:0" to the clipboard, and then in the Event List, I was able to edit the time values by double clicking on the value, which pops open an edit window where the current value is highlighted, did a CTL-V to paste, then proceeded to the next instance. Lather, rinse, repeat. This method is about 20 times faster than having to right click on each note, then replace the value in the popup. It should be worth noting that other values in the Event List can be similarly edited, although not with the greatest ease in some cases. EDIT: Scook, I took a look at your link. The text seemed to indicate that values from 1 to 2 quarters could only be converted to a value of 1 quarter. I doubt this, so I took a look. Yeah, I've taken a look at this screen before, and honestly didn't know what to do with it. So I tried plugging in some values into the min and max duration fields, hit OK, and nothing happened. So I'm still puzzled by what this window actually does. I guess I'll need to read up on it some more.
  12. Regarding a Global Search and Replace feature, something else has just occurred to me, as I'm working on another piece. This one has about 100 measures where one part is playing -- or supposed to be playing -- whole notes. But the MIDI got recorded as dotted half notes with a bit left over. Four part harmony, no less. So, again, mostly for the sake of appearance, I'm having to go in and edit the time value of some 100 x 4 = 400 notes from the dotted halves with change to whole notes. Not looking forward to this. I'm procrastinating; I'm about 13 measures into it. The only bit of time saving I've been able to come up with is to save the new value with a CTL-C shortcut to copy the new value and then CTL-V to paste it in replacement of the old values. Still tedious, but it saves a lot of typing. So it would be nice if any global search and replace feature also had the capability to do searches and replacements of time values as well -- where you can specify one or more tracks. With confirm, of course. Oh, and if Cakewalk has this capability -- that I'm not aware of -- please tell me how to access it.
  13. Cakewalk's enharmonic misspellings have become something of a pet peeve of mine. I realize that enharmonic misspellings don't matter acoustically. But if you're reading through the score, or if you want to print out a copy of it, then the spellings matter. Now, granted, it does a decent job of correcting many, once I bother to set a key signature. Like for example, setting the key signature to A Major changes all those pesky Db's to C#'s. But there are other instances where this doesn't happen. Cakewalk has a preference for certain spellings, which end up being rather inconvenient. Say, for example, I'm working on a piece in E minor, and I make a brief segue to E Major. Well, Cakewalk spells the G#'s as Ab's, necessitating my having to go in and replace every misspelling by hand. Currently, I'm working on a piece in E Major. It's about 120 measures long and has 10 parts. The chord structure is complex, with lots of modulations. There are several instances in this piece where modulations occur where C naturals are called for, but Cakewalk insists on spelling them as B#'s. This is highly annoying. I'm about halfway through editing this work, changing all the B#'s to C's, except for one measure, in which B# is the correct spelling. I mean, when a C Major 7th is being indicated, why can't the program have enough sense to recognize this chord and spell it correctly? Or F Major 7th, or A minor 7th? Etc. When I think about the key of E Major, in this instance, and its relationship to other keys, you have to get all the way to C# major before you have a B# in the Key signature -- 7 sharps! True, it's a move of three sharps either way, to get to either C natural or B#, but which is gonna be the more common spelling? When's the last time you've seen a B# in a score? Even if the bakers were able to correct this misspelling habit, I recognize the likelihood that it can't catch all of them, which is why I'm also asking for a global search and replace (with confirm) feature, where I could type in the existing spelling and the requested spelling, then be able to confirm each replacement -- just in case there might be an instance where the spelling is correct. So, should it be too big of a project to fix the misspelling problems, adding a global search and replace feature to the Staff View would go a long way toward being able to deal with this issue.
  • Create New...