Jump to content

Michael McBroom

Members
  • Content Count

    112
  • Joined

  • Last visited

Everything posted by Michael McBroom

  1. Hmmm, interesting behavior, but totally different from my own experiences. Prior to this one issue, TTS-1 has been extremely stable on my system and I use it a lot because of its very low drain on CPU resources. I also find that many of its instruments actually sound pretty authentic. I am in the final stages of finishing up three CDs of original compositions, in which I've made heavy use of TTS-1 and I've had zero problems with it, except for this white noise issue. Just this morning, things seem to be getting worse. Working on the same piece as above, when I loaded it and clicked Play, the white noise was there. First time I've run into this when loading a tune for the fist time. So I exited the piece, then reloaded it, which worked before, but no joy. So I went ahead and shut down the laptop and rebooted to see if that would make a difference. Well, it cleared up -- for now. I hope that I don't have to reboot the machine every time this problem appears now. I suppose it's at least worth mentioning that I don't know for sure that this is a TTS-1 problem. It just so happens that it is the only multitimbral synth -- or any synth apart from my GR-33 -- that I've been using when the problem appeared. Incidentally, what multitimbral synths do you use now that you find to be better than TTS-1?
  2. First thing I did was do a search here on this topic and I got zero hits. I'm currently editing a MIDI track that I laid down with my Roland GR-33 guitar synth -- it tends to add spurious notes to the playback, so getting rid of them is a regular enough occurrence. When doing this before, and when viewing the info in the Event List, I've occasionally noticed that some of the notes were grayed out, while others were black. I found that the grayed out notes made no sound. They were usually the spurious notes, so this made editing much easier. But just now, I've run into an annoying occurrence. I'm trying to lay down three beats worth of notes -- two eighths and eight 16ths -- using the Staff View, and I'm seeing that the Event List is showing these notes grayed out. I tried adding notes into other sections of the piece and results were mixed. Some were black, and sounded when I played the piece, and others were gray and were silent. So anyway, I have these three beats worth of notes that I need to get sounding -- and any other future occurrences, should this happen again, and I haven't yet figured out a way to convert these notes such that they will make a sound. And yes, I did make sure that all the time values were correct to eliminate any overlap, which can sometimes choke off a note's sound. So do you happen to know what I've done to cause CW to begin misbehaving, and what I need to do in the future to prevent this?
  3. Well, the title pretty much sez it all. But here are a few more details. I'm running the latest version of Cakewalk on a laptop that still has Win7. It runs Cakewalk pretty much without issues -- except for this odd situation. TTS-1 is handling 10 tracks of MIDI instruments, and I also have a Roland GR-33 guitar synth hooked up to the system via my USB audio interface's MIDI ports. This doesn't happen all the time, but it happens enough to be annoying. What I'm doing right now is editing a track that I've laid down with my GR-33. Getting rid of spurious notes it generated mostly, which is a common enough issue with the GR-33, especially if one is playing fast scale passages. So, after cleaning up maybe a measure or two of the GR-33's track, when I hit Play to see how it sounds, all the TTS-1 instruments now sound as if they've been converted into a roaring sort of white noise. The GR-33's track still sounds okay, but none of the TTS-1 tracks do. I first tried just stopping and restarting the piece, which didn't help. Then I found that, if I clear the piece from CW by hitting the 'x' in the top right corner, then reload it, everything's back to normal. But what I'm finding is, after editing a couple measures of the GR-33's track, the roar comes back. So I have to save, exit, and reload again. This is annoying behavior and I'd like to find out what it is about my activities that is causing Cakewalk -- or TTS-1 -- to behave in this manner. I don't have any VSTs loaded -- just two instances of TTS-1, but only one of them is doing anything during this section of the piece. No audio items are loaded at all, except for the TTS-1 audio outs, of course. Any ideas?
  4. Guys, thanks for clearing up the mental confusion I was having. Abacab, I had thought of trying to load two instances of TTS-1 to test it out, but I'm glad to read you've confirmed it works. I have a couple of pieces I've composed where I should go back and adjust my TTS-1 settings to avoid any MIDI confusion. Abacab, the way I'm getting the GR-33 into Cakewalk right now is through a USB audio interface with 5-pin MIDI ports. I also have a couple of Midiman MidiSport 2x2s and a Roland UM-1 or something or another that's 5-pin to USB. Currently, the only device I have hooked up that require a MIDI-to-USB interface is the GR-33, but I also have an older Yamaha keyboard that has several onboard patches I'm quite fond of, and a Roland JV-1010 that I bought back in the age of hardware synths, which also has some decent settings. More importantly,. I've recorded tunes using Pro Audio 9 that, in order for them to work properly in Cakewalk, I have to have all these old synths hooked up so their instruments are interpreted properly. Speaking of Pro Audio 9, abacab, I like your avatar. Most expensive single piece of software I've ever bought.
  5. I'm aware of the 5-pin MIDI cable being the 16 channel restriction. It sounds as if you're saying what I'd hoped to hear -- that Cakewalk has no limit in MIDI channels it can handle, but rather that the limit is imposed by the devices and/or software synths being used.
  6. I suppose I could set up a test file to find the answer to this, but I'm wondering if things might be more complicated, which is why I'm putting this question to the forumind. I've always known that MIDI is limited to 16 channels, but I'm wondering now, is this a limitation that the Cakewalk environment imposes, or does it depend on the synths and/or VSTs. For example, let's say I've got a number of MIDI instruments that I have assigned to TTS-1 -- say a dozen. But I need to load, I dunno, another five more. So that will put me at 17. But what if, for these next five instruments I choose to load VSTs and a MIDI keyboard or two? Are all these separate instruments included in the 16 channel total, or does each of these separate devices have at least one channel not included in the Cakewalk total (like TTS-1) that it can use? I found this article on the subject. It seems that, if one has the hardware to support it, one can have a large number of MIDI channels. But I guess my question remains -- will Cakewalk support this larger number of channels? http://homerecordinghub.com/midi-interface.html
  7. Folks, I thought I should come back to this thread and let y'all know that I found the solution. You know, I'd tried so many things with my GR-33 that I had probably gotten things crossed up pretty good internally. So a few days ago, I decided to reset the device to bring it back to factory default spec. Of course when I did this I lost a few presets that I'd saved, but I can recover them without too much difficulty. As I was going back over some items I'd covered before, I came across the Local Control discussion on P94 of the GR-33's manual. In the discussion a couple of things were mentioned that I had been running into, specifically collisions between the DAW and the GR, and not recognizing switches on my guitar's MIDI pickup. I had tried setting Local Control to Off before, and it hadn't made a difference, but since I'd reset the device, I decided to try it again. And guess what. It worked. I'm now reliably getting my GR-33 to lay down MIDI tracks, and I can hear what's being recorded from the GR-33's onboard patches. This is yet another example of me realizing that I have indeed forgotten more about MIDI than I know now, cuz I didn't used to make this sort of mistake way back in my Pro Audio days.
  8. OK, I have more to report. First of all, I updated the GR-33's BIOS or OS or whatever you want to call it. Then, I tried unchecking the MIDI out in Preferences and left the cable plugged in, as John recommended. Didn't make a difference. What I have been describing as alphanumeric hash still appears. I took a closer look at this "hash" just now. I greatly expanded the length of this piece's measures in the Tracks window and made an interesting discovery. The track carries a label, identifying the GR-33's patch -- in this case, A11 Jazz scat. And that is in dark gray text. But in bright white text there is a successions of, well they look like boxes, spaced evenly apart, each one occupying the equivalent of a 32nd note's space. And inside each one is the label "p0." Inside some of these boxes are broken bits of line -- indicating some sort of musical signal ordinarily. And for the first time, I heard some audio coming from this fragment. All it sounded like was a single honk from a harmonica. But then I made another interesting discovery. The audio for the GR-33 track is now working, and I can select different patches if I want. However, I also discovered that I can no longer record MIDI. I didn't do anything, other than just muck about with the playback some. So now I get to retrace my steps and see if I can figure out what I've done this time. Grrrr . . . . . Feels like one step forward, two steps back, but I'll get there eventually.
  9. Gswitz, My GR-33 works much like your GR-20, I suspect. I've never had an issue with hammers and pull-offs with mine, and string bending and finger vibrato -- it's always tracked this perfectly. I find that most of the errors I get come when I try to play really fast scale passages. The GR-33 demands ultra-precise technique when playing at high speed, and I guess my technique can be a bit too sloppy at times, although it doesn't sound like it to me when I'm playing the guitar straight -- that is, not using the synth. However, the great thing about having a MIDI guitar is I can go into Cakewalk's Staff Mode and correct any errors, even supplement the guitar part in areas where I feel it needs it. It ends up being a very powerful tool. Yeah, it's true that the synth can pick up a lot of garbage, but, while it may be a bit time consuming, it is ultimately possible to clean up the part and get it configured the way I want it.
  10. John, thanks for your response. I mis-wrote. As you can see in your above quote of what I wrote, on the second line, I wrote the true condition of the audio interface, opposite of what I wrote in the first line. So, to reiterate, I do have the MIDI out from the GR-33 running to the audio interface's MIDI in. But as I mentioned above, if I run the cable from the audio interface to the GR-33, I get alphanumeric hash appearing in the track and no recorded signal. I don't know why this is occurring. It seems to me that, if I try your technique of leaving the MIDI Out unchecked in Preferences, this is the same as unplugging the MIDI Out cable from the audio interface, yes? I'll give your technique a try, though, with the cable both plugged in and unplugged. The GR-33 came with no software, thus it is not seen as a VST by Cakewalk. But your mention of this got me to thinking, so I visited Roland's website and found that they have updated OS files for the GR-33. So I downloaded and installed them. Maybe they'll fix the problems I'm having. I'll find out momentarily -- and I'll report back.
  11. Folks, I'd like to revisit this thread -- mostly because I've finally gotten my Roland GR-33 Guitar Synthesizer to work with Cakewalk. It records fine, but that's it. Now, for whatever reason, I can't get any playback sound from the GR-33. Just to check that it was recording correctly, I copied a passage of the track I'd recorded onto a neighboring MIDI track, and then played back that track. It sounded fine -- even captured some nuances, like my finger vibrato and string bending. Given that this track was for a Hammond B3, I was quite surprised. But that's where the happiness ends. I've gone back through the GR-33's difficult to understand documentation, seeing if I can puzzle out why it isn't playing back any audio. Might it be because I have only the MIDI OUT from my audio interface running to the GR-33's MIDI IN, and I have the other cable unplugged? I tried plugging it back in, but it didn't help. I found I had to keep the OUT from the audio interface to the IN to the GR-33 unplugged, or else I got a bunch of hash in the track where the recorded signal is supposed to appear, and no recorded information was left. Just a bunch of alphanumeric hash. I don't remember having to do this -- unplug the cable that is -- years ago when I was using Cakewalk's Pro Audio and the GR-33. I also found that, after finishing the recording, when I played my guitar, the B3 track would sound along with the GR-33 track. And I found further that if I clicked on any other track, its MIDI instrument would play along as well. These are all TTS-1 instruments. So I have no idea why that's happening. But I can't help but wonder if all this mess is tied up with my not getting any playback from the GR-33. In Cakewalk, I have the GR-33's track in/out associated with the audio interface. Actually, I eventually left the input to Midi Omni, since it still worked, and was non-specific enough to avoid any conflicts, or so I'd hoped. For the Group/Bank/Intrument, I have the instrument definition file loaded for the audio interface, such that it reads "Roland GR-33," and it's sitting with its own, non-shared channel number. The bank is User, which is the correct one, and the instrument is selected from the User bank. Everything perfectly normal there. In Preferences, I don't have anything out of the ordinary selected there. So, I'm just wondering what I might have missed. I suspect the problem doesn't lie with CW, but with the GR-33. I probably have a parameter set incorrectly. Problem is, the manual is a difficult read and it's left out even minimally comprehensive explanations for a lot of the synth's settings. Much of what I've been able to glean out from it has been through trial and error. Unfun.
  12. Hey Nigel, is this Windows update for Win10? I'm still running Win7 and my last update was KB2310138. I've wondered for some time if one or more of these updates might be responsible for some problems I've been having. For example, I have a Roland GR-33 guitar synthesizer and it worked perfectly with Sonar until about two years ago, when it suddenly stopped working. To this day, it still doesn't work -- the problem has to do with Sonar (now Cakewalk) not playing the MIDI signals sent out by the GR-33. If I run it straight into an amp, I get all the MIDI instruments playing through the amp, I just can't get those instruments to sound within Cakewalk. I've suspected for some time that the problem I'm having with this synth might be related to a Windows update, although I have no idea which it would be. And of course I've been wondering for some time now if the problems I'm experiencing right now might be because of a past Windows update.
  13. Playing around with this one file some more, I didn't mention but it does have one audio track. This particular file that I was working on had seven MIDI tracks, plus the two TTS-1 tracks, plus an audio track, where I bounced the nine tracks into it. So, to see if it would make any difference, I deleted the audio track, then played the file. No difference. Very heavy distortion and dropouts about every second or so. So, I restored the audio track, then deleted the 9 MIDI and TTS-1 tracks, such that only the bounce audio track was left. Hit Play, and it played the tune back perfectly, nary a snap, crackle, or pop to be heard anywhere. Frustrating.
  14. The LatencyMon stats I quoted above were with that same MIDI file resident in CW. I tried it later when CW was not present, and the numbers were WAY lower. Like the bar charts below were mostly only an inch long or less. The message was my machine was suitable for the sort of stuff that I've been using it for. Those spikes are abnormal. I only see them that high when my machine is misbehaving, the way it is now. Otherwise, they're barely a ripple while a tune is playing. I'm running 44.1k/24 as my sample/bit rate, just to keep things simple. I'll be burning my tunes to CD once I finish editing them, so I might as well just leave it at the CD spec (I know 16 bits is spec for CDs, but my software auto adjusts for the difference). I'll bump ThreadSchedulingModel up to 2, although I doubt it will make a difference.
  15. As I mentioned above, ThreadSchedulingModel is set to 1. You recommended 2. Should I increase to 2? Plug-in Load Balancing is unchecked. I just reset the Config file. Honestly I think the new one is the same as the one that just got replaced. So, I just gave this same example file another try, and there's no change. Still heavy distortion with dropouts every second or so. I should reiterate. Sometimes this machine will play these files perfectly and sometimes I have to deal with this. And there's nothing that I've done to change things in the interim. It's as if the machine decides one day suddenly to behave after spending days misbehaving. But it's just with Cakewalk. I can load MIDI files into Band in a Box or MuseScore 3 and they play fine. Well, I should be clear here. It's the Cakewalk .cwp files in which there are MIDI tracks that I'm having issues with. I just tried something I haven't tried before. I loaded a blank file into CW, then added a MIDI track and loaded TTS-1 for the synth chores. No distortion. So I added another. No distortion. So I added another. Still none. Then I added a MIDI file that had six tracks of MIDI data, which meant I had a total of nine MIDI tracks. Sounded like crap with all the dissonance, and for the first time, there was quite a bit of distortion. So I got rid of the first three MIDI tracks such that I had just the file with the six tracks. There was still distortion, although not as bad. So I looked for another example, but what I came across was a file with five audio tracks and one MIDI track. So I loaded it and hit Play. Quite a bit of distortion -- but only one MIDI track. So I muted the MIDI track. No difference. Then I deleted the MIDI track. Still, there was some distortion, but it had dropped quite a bit. Still there though. Then I realized that TTS-1 was still resident, although not assigned to anything. So I deleted it, such that there was only audio tracks present. Distortion was gone. So this tells me that TTS-1 is actually contributing to my problem. Other synths do too, because I've noticed it with a few. But I've always liked TTS-1 because of its low tasking of the CPU. Well, it might be low tasking, but it is also part of the problem. When my machine is misbehaving, that is. Grrr. TTS-1 is the only multi-timbral synth I've used. I guess I should look for others.
  16. When I bring up the "Sound, video, and game controllers" tab in Device Manager, it shows 4 instances of a NVidia driver (0 through 3 Internal High Definition Audio Bus), plus one Virtual Audio Device (Wave Extensible) (WDM). So, which do I disable? One of the above -- and if so, which one? -- or all five?
  17. With this same file open, the performance bars are bouncing around more than I typically see, but now they're not showing me anything. When I click on the Play transport button, the distortion has gotten so bad now that it won't play for more than about a second before and Audio Engine Dropout occurs. But before it does, I'm seeing the bars bouncing up to about mid-height, which is a lot higher than I see when CW is running right. With the Windows Resource Monitor Performance Tab, if I continue to click on Play to ignore the dropouts, what I'm seeing is the resource graphs are indicating about 50% CPU tasking. When I'm not doing this the usage is close to zero. No Cubase. Never had it, never will.
  18. Yep, set to high performance, 100%. CPU speed is 3.4 GHz. It's a quad-core AMD processor, getting rather long in the tooth now. 16GB of RAM. Here's the thing, though -- I'm also running CWbBL on an old 2.8GHz laptop with 8GB of RAM and it runs it flawlessly. No hiccups of any sort. I just tried it again with buffers set to 256. Didn't make any difference.
  19. Thanks for your response, David. In one example file with MIDI content that I'll use for this note, I'm using TTS-1 as the only instrument set. I've found that TTS-1 has a very low level of CPU demand on my system. The Cakewalk performance module rarely shows spikes above 50%. Watching it just now, I'm getting an occasional spike or two up to about 50%, but with plenty of audio dropouts. ThreadSchedulingModel in my config file is set to 1. I'm assuming that if I bump it up to 2, I'll have even more problems? I've used only ASIO with the UMC. Until yesterday, Behringer's ASIO drivers have worked very well. My Playback and Record I/O buffer settings have always been at 128. I'll give 256 a try though. I just d/l'd and ran LatencyMon. It reports: "One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup." I don't recall seeing a "throttling" setting either in CP or BIOS, but I'll look for it. In the bar graph below this message pertaining to DPC, it shows my NVIDIA driver as being the culprit, with a run time of 2786 microseconds. This driver is for a graphics card I had to add into my system because I bought a monitor that had HDMI ports only and my machine didn't have any, so I bought a card with HDMI ports. And it has an NVIDIA chip. Since this chip also handles audio for the HDMI video I've wondered if a conflict might occur here, but I don't know what I can do about it other than get another card. Which, incidentally, I probably will be doing in the very near future because I think that this relatively new video card is starting to crap out on me. Another bar graph displayed that I'm somewhat concerned over is the "Highest measured interrupt to process latency" one. It's pegged all the way to the far right, deep red, reading 31657 microseconds. I take it that isn't good either. On the other hand, the "Highest reported ISR routine execution time" is "only" 238 microseconds (DirectX Graphics Kernel) The top graph, "Current measured interrupt to process latency," is bouncing around between a low of about 26 microseconds to as high as 1200 microseconds, averaging, I'd say, about 200 microseconds.
  20. This problem I'm having appears to be the way my machine is choosing to handle MIDI files in Cakewalk. I need to give you a bit of background so you can have a better understanding of what's going on. Periodically, my machine has a problem handling large Cakewalk files that have lots of MIDI tracks. I get distortion and audio dropouts, for example. But there are other occasions where this doesn't occur, even when working on the same exact file. Now, audio files in CW are a different matter -- it handles them without issues. It's always been a mystery to me why my machine behaves this way, but it does. Incidentally, I also use Band in a Box with my compositions, and BiaB handles MIDI files without problems. In fact, BiaB is just the opposite. It tends to choke up if I load files that have a lot of audio tracks. I suppose I should point out that these problems are restricted to audio playback. When I record any of these tunes, they always record without any hiccups. Recently, my machine has been very well behaved. It has handled large files with lots of MIDI tracks without any problems at all. I don't know why sometimes it's like this and other times, there is much distortion, pops, clicks, and what have you, when nothing has changed. But anyway, I was enjoying a clean sounding machine until yesterday morning when we had a power outage that knocked my machine out. Power outages around here are not all that uncommon, so I'm used to this happening, and they usually don't affect my machine's performance. But yesterday morning, something changed. When I booted CW and tried to play a file with 12 MIDI tracks, the distortion was the worst I've ever heard, and it couldn't play for more that a couple of seconds before audio dropouts occurred. I tried restarting the machine, it didn't make a difference. I even shut down the machine and then booted it back up, still didn't make a difference. I haven't yet tried shutting it down and switching off the power supply. I'll do that next, but I won't be surprised if it doesn't make a difference. So I'm wondering now if somehow something got corrupted within CW? It was not resident when the power outage occurred. In fact, no programs were up -- just the OS, which is (still) Win7. I've run the Windows Task Manager to see if the CPU loading is uncharacteristically high -- it isn't, really. It's about the same amount of loading I see when I'm streaming a Netflix video, for example, which my machine handles easily. Also, if I load a file into CW that is audio only, it plays through it without any issues at all. So for whatever reason, MIDI has become a big problem right now, and I sure would like to understand why and figure out what to do about it. Oh, I should mention my hardware. I'm running a Behringer UMC404-HD audio interface, which has worked flawlessly with my system, so I don't suspect it. Before I had the Behringer, I was using a M-Audio Delta 66 PCI card, and I was having similar problems with it, so I really don't think it was this hardware.
  21. After putting that one tune to bed -- finally -- and reflecting on it for a while, I thought I should add one more comment to this thread. First of all, let me explain that I'm just a Cakewalk user, I don't claim to be an expert. Heck, I don't even claim to be very proficient at it. I just know enough about this DAW to get done what I want to get done and I continue to find it to be superior to any other I've tried. Okay enough of that. The problem I'm still seeing with this one file in particular is it seems that the MIDI system -- if you will -- is somehow broken. I've noticed that, if I try to change patches on any other track, it does the same thing -- reverts that track to Piano 1 and then I have to manually reassign it using the TTS-1 UI. So it isn't just that one track. It appears to be all of them. Or I should probably say, all MIDI channels. It's worth mentioning that this problem is affecting only that one file right now.
  22. No, I'm attempting to change instruments from the Tracks window in Cakewalk, same as I always do. This tune has six MIDI tracks, one instance of TTS-1 and one instance of another soft synth. Obviously I took care to make sure each track was assigned a unique channel in TTS-1. TTS-1 is handling five of the instrument assignments, while the other synth is handling the sixth. I went ahead and booted up the TTS-1 UI (normally I keep it minimized). Sure enough, even though I was indicating the correct patch in CW, TTS-1 was showing Piano 1. So I changed it in the UI and now things are back where I want them. So thanks for the tip. Glad I could put this behind me.
  23. This problem crops up occasionally and usually resolves itself -- for some unknown reason -- but this time it isn't. In fact, the problem has begun to infect adjacent tracks. So I'm turning to the forumind for hopeful answers. Here's the current situation. I have a MIDI track configured with a TTS-1 patch and I decided to try another. But when I did, it loaded Piano 1 and won't unstick from Piano 1. Now, this is the sound only. The patch I selected appears in its little window; it's just I'm not getting its sound, I'm getting Piano 1's sound. I checked to make sure I hadn't changed the MIDI channel or the bank (I hadn't) and even called up the Event List to see if something had mysteriously appeared there. It hadn't. In fact, no patch notices were loaded at all in the Event List for that MIDI channel. Then I noticed that in adjacent track (with a different channel number of course) I had selected Piano 1, so I tried to see if I could change it off Piano 1. Initially it took the change, then it reverted back and now it is also stuck on Piano 1. This is less of a problem for me because Piano 1 is the patch I want for that track, but it bothers me that it's stuck. It also bothers me that this appears to be some sort of creeping condition. I don't know what else to try at this point. Maybe remove and re-install TTS-1? I have a lot of tweaks set in that synth so far, so I'd really like to avoid removing it, if at all possible. What about installing a second copy of TTS-1 and transferring all the tracks over? Hrm, that should work, but would it do any good?
  24. Poor choice of words on my part. I didn't mean "daisychain," in that comment. I just meant basically to port it into my system, which would require the use of a MIDI to USB adapter, I reckon. I don't think I've ever used MIDI "thru" before, so I had to check my devices. I have one -- an old Roland JV-1010 synth module. It has a thru port. Currently I don't have it hooked up to my system, but I guess it's worth a shot now, especially since I can daisychain other synths from it.
  25. Actually, no. I was talking about legacy MIDI synths that have the old 5-pin DIN ports only. I own a few -- four, I think. Not including the Soundblaster Live! cards I own that have MIDI/game ports. These old legacy synths I daisychained to my DAW because it had only one MIDI port -- the game/MIDI port of the Soundblaster card.
×
×
  • Create New...