Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

41 Excellent

Recent Profile Visitors

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

  1. "Don't forget to inflate shoes before crossing water" I got a new code in my account - that worked Syphus
  2. Site says coupon limit has been reached . . . No more free for the code in my user area . . . Syphus
  3. Thanks - I know it makes perfect sense - I just expected it to continue past that end note Syphus
  4. Ok - Interesting scenario - I was just messing around and I was just using MIDI notes to drive and instrument. No audio recorded When I played back the the midi, at the end of the last note, the transport jumps back to now time. Now I expect that behavior, at the end of an audio recording, but I never had just a plain midi track. This effect sounds funky and at first I though there was something wrong. It just sound like the note ends too abruptly. I got around this by recording some blank audio so my transport kept going and all sounded as I expected. I know that I can use "Ctrl-W" disable the "Return to Now Marker", but I did not expect that from a MIDI track. So My question is this - Is this normal behavior for just midi tracks (last note abruptly ends and then Return). Thanks, Syphus
  5. I had to disable my USB 3.0 Ports due to a USB error when disconnecting my Focusrite. Also came up randomly by it's self (BSOD) and traced down to the driver for USB. Since I was using the latest driver for USB (not Focusrite driver), I just disabled the 3.0 ports. After that, not more random or pulled cable BSOD. I was getting desperate due to the recovery from it was getting risky - once I had to spend four hours recovering . . . Since then I do weekly back ups of the C drive - just in case . . . Since this was a laptop - I don't believe I had any other choice (can't replace USB easily) Syphus
  6. Well I can verify that V5 will not work on Win 7. I did not think about it and just updated. No Go! Fortunately I always have the original install files backed up and I just reinstalled the last version. I was actually just searching to verify if anyone else would have run into a problem installing on win 7 . . . . I guess I got my answer . . . Win 10 . . . Hmm, one day. Syphus
  7. I think this should have been posted in the "Cakewalk Early Access for 2020.05" area. It might have gotten more attention. But I checked the VST on the developers page and found this to be interesting, That being said, do post back here if it still remains broken after the release (I might install it myself). if it is (still broken) - there will be the feedback on 2020.05 release. You should mention it there. Syphus
  8. It seems this has come up before: IMHO: I do not think that per the midi standard that "*.midi" is valid file extension for midi. I'm not saying that it is not used (because there are programs out there that will only output "midi" extension), but I believe that it was not a file type back in the day. Personally, I would not expect a MIDI file to have that extension. I saw the Reaper forums talking about the same issue and now Reaper recognizes that extension. Just some observations . . . Syphus
  9. Additionally I saw this: Cakewalk SFZ+ does not read .sfz files, it reads .sf2 (soundfont) files . . . Be sure that is not your problem See this link: https://www.kvraudio.com/forum/viewtopic.php?t=532700 Syphus
  10. I'm assuming that you are referring to the player as being 32 vs 64 bit. I believe the soundfont file does not come in a 32 or 64 bit version . . . it is just a file to load into the player (which could be a 32 or 64 bit application). So as long as the player matches your installation (64 bit), the file should load. If the app (SFZ Player) is 32 bit, you may have to update the player (or to a player) that is 64 bit. If need to use a 32 bit version . . . then that could be problematic because you will need to use another program to run it (such as BitBridge) in CbB. Do note that the soundfont file can be *.sf2 or *.sfz. sfz is a compressed format and not all players can play them (decompress). Hope that helps . . . If you do a search on the forum . . . there are several threads about Soundfonts and players. If you still need help . . . It would be advisable to include specific info as to what you are trying to do and what your failure mode is . . . I'm sure some will be able to chime in and help What player ? What font file? What error if any? What is the failure mode . . . Syphus
  11. Thank for the confirmation . . . I had done some looking but I did not come across that. At least I know it is a known problem . Syphus
  12. Hi All, The title is a bit misleading after doing some work. Perhaps someone can enlighten me as to why I'm see this behavior . I just spent the last hour combing through the threads and reading the manual when I fixed my problem. Here is what I saw: I had "screenset" 1 set in a new project I started today. I was working with some samples using the "Media Browser". To make extra room, I had "removed" the "Help" module. This gave some room and left a module header bar that said "Help Module" and contained the ">>" marker (or button) that would allow me to collapse the "Media Browser. After working a bit I started to set up some screensets for my workflow and what I kept running into was a problem with screenset 1. I would collapse the "Media Browser", then switch to another screen, but when I came back to 1, the "Media Browser" would be open again. This started making me crazy as I knew that I was doing it correctly (or so I thought). What I discovered (just as starting this thread) was that IF you close (collapse) the "Help" module, the header remains on the screen to support the ">>" marker. If that condition exists and you collapse the "Media Browser" to the right side, then go to another screenset, when you come back the "Media Browser" is there again. It is almost like the screenset save is weirding out for 1. Well the "workaround" is to un-collapse the Help module (you can type "Y"), re-collapse the entire right side panel (including the Media Browser) using ">>", go to another screenset and "BOOM" it works now. How strange is that. The reason I went to this length to type this that I thing this my be a bug, but maybe not?? What do you think? I think it may be something that is not supposed to happen (i.e. a bug). I try messing with the workspace setting to fix it but that was not the problem. Syphus
  13. I ... could... be only arguing in my spare time!
  14. Syphus


    No problem - that is what I saw . . . Just checking Later - Thanks Syphus
  15. Syphus


    Ok, I'll bite . . . Free from where? I only see a pay version . . . Just curious . . . Thanks, Syphus
  • Create New...