Jump to content

seadude

Members
  • Content Count

    78
  • Joined

  • Last visited

Everything posted by seadude

  1. Thanks Scook, that's done it. And thanks Robert for your inpout as well. How could I have missed that........
  2. Aside from the UR44 are there any other entries in HKEY_LOCAL_MACHINE\SOFTWARE\ASIO Oh yes, the darne thing is there. I guess I should delete it
  3. Well I can see that driver (Yamaha Steinberg USB ASIO (3 in, 3 out) and I can select it but it doesn't stick.
  4. ....which Cakewalk insists on defaulting to (Preferences > sync and caching > record latency adjustment) instead of my Steinberg UR44. When I select the UR44 option and hit apply it doesn't - just defaults back to realtek. Clean install of CW. I've looked at previous posts about this and no-one really seemed to solve it. The on-board realtek audio has been disabled in the bios. The realtek driver has been uninstalled (and hasn't magically been reinstalled while I've not been looking). I have edited the AUD.ini file in appdata/roaming/cakewalk/cakewalkcore and deleted all references to the realtek audio. So it appears Cakewalk is referencing something which isn't there. Audio performance appears fine with usual latency when recording. I have thrown every softsynth I could lay my hands on in a test project and CW stood up well. I should also add I am using the ASIO driver for the UR44. And when realtek shows up that is also shown as realtek asio. Interestingly when I go back to the AUD.ini file the reference to realtek has reappeared. In Device Manager the on-board realtek audio is not shown at all. Any ideas?????? Anyone?????
  5. Thanks for the suggestions. I still can't replicate it even with the Fantom switched off and with this particular project. The issue applied specifically to a re-opened project with midi outs to Fantom (via Steinberg UR44) and Addictive Drums. Maybe it has something to do with what Robert suggested because obviously when this happened I re-routed the relevant midi tracks to the Fantom outputs and maybe doing that has solved the issue. And adding another one or two soft synths hasn't changed that. Re-opening the project now everything is fine. I have noticed this behaviour before and will post here again if the same ithing happens and if I can replicate it. Otherwise problem solved. Thanks guys.
  6. Hmmmm....interesting. I can't reproduce this when I create other projects. It just seems to happen with this particular project I'm working on. Strange.
  7. Midi out on track 1 set to my Fantom X instrument definition, e.g. piano. Insert Addictive Drums (or any other soft synth) and my Fantom X output on track 1 defaults to Addictive Drums. Why? What am I doing wrong?
  8. Problem solved! Thanks to Star Tekh. This is what I did:- Flashed bios to 1802 update. Reinstalled original Asus (Intel) chipset drivers. CbB works completely normally as does everything else. So it seems to have been a chipset driver issue. Many thanks everyone for your input.
  9. Well in the interests of trying to get to the bottom of this I'll try it again and this time pay attention to the chipset driver - although I thought I had updated that too. (Did I say I wasn't going to do this ever again?). And if CbB repeats its behaviour I'll try and get a screencapture of the lightning fast popu-ups as Neil suggests. StarTekh, thanks for the input and I'll let everyone know what happens. I'm trying to get a song finished as well.......
  10. Well I've taken the line of least resistance and rolled back the bios to the previous version and - session drummer roll please - CbB is now back to normal. I am never updating the bios ever again.
  11. Okay, this is now getting technical - how do I go about that?
  12. Yep, did all that. I'm watching for other issues but so far everything - soft synths, midi, audio, tracking etc all working fine in Platinum.
  13. Yes, well, possibly you are correct. However as everything else is working normally I'll probably revert to Sonar Platinum.
  14. ......like always keep drivers and os and bios updated to the latest versions? So I updated my bios yesterday (Asus Prime 370A board with i7 8700 cpu, 32gb ram, 4 x pcie nvme hard drives plus assorted sata ssds, using Asus integrated graphics, running Windows 10). And CbB is now unusable. Terribly slow opening, seconds delay responding to input - and throwing up small windows pop-ups which flash on and off so quickly I can't read what they say. Now the really interesting thing is that Sonar Platinum still works fine and another well-known programme beginning with C and ending with e also works normally. All the usual drivers are visible and working normally in these two progs. I thought a reinstall of CbB would do it but, no, still the same issue after doing that. And I can't even get at the Preferences menu to try to find out what may or may not be going on. I guess I could roll back the bios to the previous version.......
  15. Agreed. There is such a thing as over-producing using Melodyne. I hold my hands up - guilty as charged. Melodyne will not make an iffy vocal into a good vocal (will it?). What I think the multitrack version does brilliantly is help tighten up timing. Being able to see the blobs for each track and adjust them is great. But the tuning needs real care and attention and I always tend to overdo it before either going back to the original or re-record the take. Interestingly I am using v. 4.2 and because of the way I work with it haven't come upon any real problems other than the algorithm detection being inconsistent.
  16. Well reading this thread has prompted me to sort out my screensets. Due to time and work pressures I just hadn't used them and always wondered why when I hit, e.g. M for Mixing Console it would always come up in a smallish window which then needs resizing. I now know that screensets remember the sizes of things like the mixer, prv, score (staff) and so on. Thank you forum. Looked at and learned about lenses and I now understand what they are intended for but I for me personally I haven't a use fopr them and will stick with screensets on their own.
  17. Yes, in the spirit of 'If it can go wrong it will go wrong' the only one I would quibble with is S - split clips at now time. It's terribly easy to hit D for MultiDock, finger slips, and when I next look at the screen I wonder what on earth has gone on. I always like single key shortcuts to be non-destructive to avoid destruction.
  18. It would aid workflow if there were keyboard shortcuts for lenses.
  19. Try highlighting the instrument you want to play in Play? And then select that midi track in Cakewalk?
  20. Many thanks, very good of you - again! Will check this out.
  21. Don't know if this will be of any use to anybody.......not even sure how useful it is for me......attached are two .xls files. The first contains the Cakewalk keystroke codes as seen when opening a key bindings file in a text editor (.kbn). The second contains all the Cakewalk command numbers (again as seen after the = sign in .kbn files) and their actions. For me, this allows me to include a number of extra key binding commands that otherwise I wouldn't have known about. I have been able to find 932 commands which are listed in the file. There appear to be 379 Global commands shown in the Cakewalk editor along with an extra 539 under other headings, e.g. Console View, Step Sequencer, etc. However some of these 539 are duplicated under Global. I've just not had enough time to find out all those which are duplicated, so the structure in the commands file may be a bit haphazard, I tried to code which commands belonged only in which views. It is possible that there are more which I haven't found. Certainly there appear more on the various lists which forum members were good enough to send my way. Another point to note is I have listed unused numbers as 'unassigned' whether or not they are actually reserved or not assigned. Errors and ommissions are welcome as are howls of anguish. Cakewalk Key Codes Check-02.xls Cakewalk Keyboard Actions.xls
×
×
  • Create New...