Jump to content

MikeyT

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

3 Neutral

Recent Profile Visitors

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

  1. Thanks for the suggestion JoseC, much appreciated. However, this issue is a very specific one for FL Studio and its pre-installed ASIO drivers interfering with the Zoom R24 drivers. Cakewalk does not come with pre-installed ASIO drivers.
  2. Hi @msmcleod No luck I'm afraid - I've tried all four options of this setting and it makes no difference. What is interesting is that if I go into the Preferences section and make any change and hit apply, the file will play normally. So, to recap: 1) The first file usually plays fine. So, the Zoom audio interface is working fine with Cakewalk at this point. 2) I close this and open and close the second/third/fourth/nth file and at some point, one will open and when I try to play it, the first couple of notes of midi will play and then the midi instruments fall silent, the now marker doesn't move, but the audio plays fine. So, the audio bit is still working but something is preventing the midi from playing 3) If I go into the Preferences section and make a change, such amend the ThreadSchedulingModel as discussed above or deselecting one of the Zoom audio interface channels and hit "Apply", the file will then play normally - playing the midi synths, the audio files, and the Now Marker moving. It's as if it resets the audio interface. I'm not having any problems with the Zoom audio interface working with playing other applications on the PC, although they're not really fair comparisons. It is only the midi sounds and the Now Marker not moving that are the issue. It would be useful to know (at a high level) how the midi implementation works in Cakewalk - at what point does the midi engine in Cakewalk controlling plugin synths interact with the audio interface? Surely, that must all be internal to Cakewalk - the midi says play something, the soft-synth generates the waveform and only then does it send stuff to the audio interface? And there must be some sort of protocol between Cakewalk and the interface, so Cakewalk issues a "release resources" (or something) statement and the Zoom interface is meant to implement that properly. The driver for the Zoom Audio interface is at the bottom of this page here: https://www.zoom.co.jp/products/multi-track-recorder/r24-recorder-interface-controller-sampler#downloads Do the Cakewalk developers have any way of issuing commands to the driver to test whether it is behaving properly? I've no idea how to do this or understand the results. It's only really by understanding this that I can go back to Zook and ask them to fix what is wrong - that is, assuming the Zoom interface is wrong and it's not an incorrect implementation in Cakewalk. Or indeed something completely different on my PC that is getting in the way - no idea how I could trace that! Anyway, many thanks for your help and suggestions so far, much appreciated. Mike
  3. Hi @msmcleod - many thanks for the response and apologies in my delay responding, the day-job has been getting in the way. My ThreadSchedulingModel is set to 1 (Legacy Wait-for-single-object). I'll try playing with different settings on this and see if it makes a difference :-) Many thanks, Mike
  4. Okay, apologies for the delay in responding but a quick update: I've tried a few things out as follows: Cakewalk Sonar X2 on the setup above (Zoom R24 audio interface) - same problem Cakewalk Sonar X2 and an older version of Cakewalk Bandlab on a different laptop, same Windows OS version plus Zoom R24 - same problem Current version of Bandlab on current rig using internal RealTek ASIO drivers not the Zoom - doesn't have the problem above but is not usable because of other problems (audio dropouts) I do have a work-around in that if I get the issue, I go into the project settings, de-select one of the Zoom's 8 input channels and hit apply. This seems to reset everything and allows me to then work on the project. I'm yet to try: Cakewalk Sonar X2 and older version of Cakewalk Bandlab on my old desktop with the Zoom - this has an earlier version of Windows 10 and I do not ever recall having this problem with that machine Another DAW such as Cubase with my current rig (Zoom plus laptop) - very hard to make comparisons. But I need something that's stable. While the above points to some issue between the Zoom R24 drivers, the current release of Windows 10, and Bandlab Cakewalk, it is hard to see why. The problem is arising with Midi-driven soft-synths internal to Cakewalk. So, before any of this hits the audio interface, Cakewalk must run the synth, convert it to an audio output, and then channel it to the audio driver along with the audio channels. *And* to cap it all, it all works fine (usually) for the first project I open - it's only the second or subsequent projects that have the problem. It seems like when I close a project, Cakewalk issues a call to the driver to release resources and for whatever reason, that does not happen properly. When I open the next project, the audio plays fine but the midi channels start and then immediately stop and the now-marker doesn't move. Also, how am I going to get anyone to take responsibility for this? The Bandlab developers will say it's a Zoom driver issue, Zoom will say the driver works fine and it's an issue with who Bandlab interact with it - it is a midi issue after all. Anyway, stumped for the moment and will post further updates but do at least have a work-around to get me through the current project. Mike
  5. Dear Robert, Many thanks for your reply, much appreciated. Since posting the response below, I've started going through my entire rig eliminating things one by one. I expect you are correct and it is something to do with the drivers. I'll post back if I find out what it is. My original post was: Regarding your first point, the now marker not moving is just one of the symptoms that manifests itself. I'm aware of the Scroll Lock toggle and that was the first thing I tried. To be absolutely clear, this is what I am seeing happening: 1) I open a project that contains a mixture or midi (to Session Drummer 3) and audio (a small number of guitar and bass tracks). I hit play, the now marker moves, the midi and audio play and I am able to work on the file. I then close the file but keep Cakewalk open. 2) I open, work on, and then close a number of other projects as per point 1). All are fine and I'm continuing to keep the one instance of Cakewalk running, only ever one project open at a time. 3) However, eventually, I open a project and the problem manifests itself. It may be the second, third, fourth, or whatever project I open (although it usually seems to be the third or fourth). The problem is that the first two beats or so of midi play and then the midi engine stops. The Now marker does not move (I have not pressed Scroll Lock in between projects and in any case, pressing Scroll Lock has no effect on the Now marker not moving). The audio continues to play, even though the Now marker is not moving and the midi instruments are not playing. On rare occasions, I get this situation with the first project I open. Once I have reached stage 3), the only thing I can do is to re-start Cakewalk. This generally resets me to point 1) above but on rare occasions I might get one of the following: a) It doesn't clear the problem and I have to restart Cakewalk again before it will load and play a project b) Cakewalk doesn't seem to shut down properly and remains visible in Task Manager, impervious to any attempts to End Task. I then need to reboot my PC to get back to working condition. I've tried your suggestion of clearing the Picture Cache, sadly with no benefit (the second project I opened this morning went to stage 3) above). Regarding your second point, you're talking about the drivers not releasing after shutting down Cakewalk. So, I don't think this relates to the issue I'm having opening a project, closing it, then opening a second project and having the issue outlined above. However, it could perhaps relate to why sometimes after closing Cakewalk, I get conditions a) or b) outlined above - although it is not the ASIO drivers for the Keystation-Pro and Zoom R24 I am seeing stuck in Task Manager but Cakewalk. In fact, I cannot see the drivers for Keystation-Pro and Zoom R24 in Task Manager and I'm not sure I would expect to. The options you've kindly suggested in your point 2 don't really move me forwards - on the whole, I can reset the problem by restarting Cakewalk, which is less onerous than doing the things you've suggested each time. It is a pain to have to close down Cakewalk each time I want to work on a new project (I'm working on a suite of fourteen songs at the moment). It does feel to me like this is some sort of issue with memory not being released. I had problems mixing a previous batch of audio-only tracks earlier in the year, where the first project worked fine but then I started getting weirdness as I closed and opened new projects, eventually needing to restart Cakewalk. Anyway, I appreciate this sort of problem is almost impossible for you to diagnose remotely, there are just too many variables and it's impossible for you to recreate the issue yourself. I will try longer pauses between closing and opening projects or perhaps just restarting Cakewalk each time I want to work on the next project. Many thanks for your help. All the best, Mike T P.S. Cakewalk just hung on me (after a load of unsaved edits, of course). The screenshot shows the Cakewalk Application frozen in task manager. End Task has no effect on it, it just sits there and remains until I re-boot the machine. This is a rare to infrequent occurrence for me - froze in the middle of doing some edits and did not come back. I don't think this is related to the issue discussed above.
  6. Great - many thanks. I will email them this one and the other thread I have at the moment about freezing tracks not working properly. All the best, Mike
  7. Okay, so I've attached two Cakewalk bundle files that illustrate this problem/bug with freezing tracks: Freeze_Problem.cwb - one audio track is a kick drum, one is a pad. There is a noise gate on the pad with a side-chain from the kick drum, so that the pad is only audible when the kick drum hits. If I freeze the pad track, the side input to the gate is ignored and the frozen pad just plays the whole time. Freeze_Problem2.cwb is the same but the audio kick drum is replaced with a midi triggered Session Drummer 3 kick. The result is the same - ie freezing the pad track results in the pad playing all the time. I just tried this out to check whether midi behaves differently to audio. This is actually quite a PITA. If the bass player is a bit sloppy, I often put a noise gate on it triggered by the bass drum. This tightens the bass to the kick drum with the minimal of effort. However, I'm finding these days that Cakewalk is not handling memory very well and I end up having to freeze tracks during mixdown to stop Cakewalk from crashing. Is there a specific place on these forums to post bugs? P.S. I still love Cakewalk :-) Many thanks, Mike Freeze_Problem.cwb Freeze_Problem2.cwb
  8. OMG yes - if you expand the folder, there is a big section that you can enter text into. How did I miss all this for so long! It would still be a great enhancement to be able to then export all these notes. The reason being learning which approaches get the best sounds - sometimes, you only really notice things a year on once you've cleared your headspace of the songs. You listen to a track and think "that guitar sound really rocks". I've usually archived the cakewalk files by that point - being able to have an exported .txt file would just make things easier. Anywa, many thanks for the responses on this, I will start to use these new-to-me notes sections. That said, I'm having other woes with Cakewalk at the moment not being reliable for midi or for mixing. But that's another thread.
  9. Hi Wookie - thanks for the message. I'm not sure I fully follow you - where would I report it other than this forum? By recipe, I guess you mean the content of my original message about how the problem arises? Many thanks, Mike
  10. Many thanks for your response - that's absolutely brilliant: it's possible then to add notes at the take level (ie lanes), Track level (description in the track properties), and project level. It's funny how I've never noticed that after so many years of using Cakewalk and wishing I could! Thanks so much 🙂
  11. Thanks for your response Cristiano, apologies for not responding sooner, I didn't get notified. It's the Sonitus:fx Gate. I'll see if I can create a demo project that illustrates the problem.
  12. Hi Wookie - thanks for your response. I'm using the latest version of Cakealk - 26.01.0.28 I've been trying to work all day and the workaround I mentioned above doesn't seem to work all that well - it seems to be dependent on how many projects I've opened - I don't mean at the same time, I mean open a project, close it, open the next one... and so on. It seems to be about the third or fourth one that fails to open. The fact the now marker doesn't move as well is quite strange. If a file is just audio, I can work with it because the lack of midi doesn't matter. For further information, I've tried different settings of Midi playback buffer, from the default of 200 up to 1000 milliseconds but it makes no difference. I've also tried using the Zoom and M-Audio on USB-2 ports and USB-3 ports, again no difference. As much as I hate to say it, I'm going to have to start looking at alternatives to Cakewalk. I had real trouble mixing the previous project with audio dropouts that I've simply never had before with Sonar X2 and earlier versions of Bandlab Cakewalk. I really regret this as I've been working with it since when it was just midi only (20+ year ago???). But it's just not stable on my setup and hasn't been for a few months now.
  13. First up, many thanks again to Bandlab for keeping Cakewalk going, really very much appreciated. Sorry to say that with each Windows update and Cakewalk version update, I'm seeing new problems arising, making it harder to continue using Cakewalk. The thing I've started having trouble with over the last couple of weeks seems to be related to Cakewalk not freeing up resources/memory between opening projects. The symptoms are: I open a project with a combination of midi and audio (the particular set of projects I'm using at the moment are using Session Drummer 3, which came with Sonar X2, my last purchase) I do some work on this, close it and open the next project. However, sometimes, this second project starts to play the midi track but then stops. The audio continues but the now marker does not progress. It doesn't always do this but the further through a working day I progress, the higher the likelihood of it happening. It also seems to happen more frequently if I drag Cakewalk files from the file manager into the software rather than using the File->Open route. Once this problem has manifested, the only solution is to completely restart Cakewalk However, sometimes, Cakewalk will not close down properly. The interface dissappears but I cannot restart Cakewalk. If I look in Task Manager, I can see an instance of Cakewalk running. However, it is completely immune to Task Manager's attempts to "End Task". So, now I need to re-boot my PC. All of the above happens far less if I click the "Reset Midi and Audio" button before I close projects. However, it is still the case the longer my PC is on and I am working, it happens eventually. The final symptom I have noticed occasionally is that after one of the above mentioned failures, on re-starting Cakewalk I get a message saying there is not enough memory to connect the midi devices. I'm not techie but all of the above seems to point to me towards something not releasing memory properly. My technical spec is: Dell Inspiron 15 with 16GB Ram, Core i7 (8th generation) processor, Cakewalk and Cakewalk files all running off an SSD, Windows 10 Zoom R24, with the latest ASIO drivers (which are pretty old) M-Audio Keystation-Pro 88, with latest ASIO drivers (which are pretty old) Cakewalk version 2020.01(Build 28, 64 bit) Any thoughts or suggestions from anyone else who has experienced this are very welcome. Many thanks, Mike
  14. Dear Bandlab people, I think this is a bug: I have a bass guitar track, on which is a gate. The gate is triggered by the bass drum on another track - the gate opens when the bass drum hits, so the bass guitar can be heard. The gate then shuts, cutting the bass guitar off, making it sound tighter. However, if I freeze the bass guitar track, the resultant frozen track is silent. I presume this is because the code responsible for freezing the track is not recognising the gate is triggered to open by the bass drum, and hence the gate remains closed for the entire mixdown. Many thanks, Mikey
  15. Have used Cakewalk for many year, so many thanks to Bandlab for keeping it going. My suggestions for additional features are: 1) Sub-folders (somebody previously suggested this) - would come in handy for decluttering. For example, I frequently put all the guitar takes in a folder. It would be great to have a sub-folder to then hold all the guitar takes that didn't get used. 2) A better notes facility, i.e. notes about the project. In particular, the ability to add notes to a track - I'd note things like when it was recorded, who the person was, what microphone position was used, etc. At the moment, I have to try to keep all this in the project-based notes facility. The ability to then export these notes to a file would be useful. 3) I'm finding that even with an 8th generation i7 with 16GB of RAM, Cakewalk still crashes on me on projects where I am using a lot of busses with effects processing. It would be great to be able to freeze a bus - which would of course then freeze all the input tracks as well. 4) It would be great to be able to reset a track - the reset would involve setting all faders to default values, deleting all effects, deleting all automation, etc. You can sort of do this by duplicating a track and deleting the original, so just a nice-to-have really. Many thanks, Mikey
×
×
  • Create New...