-
Posts
10 -
Joined
-
Last visited
Reputation
7 NeutralRecent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
I would like to introduce a video. The following URL is a video of a MIDI being played using a certain Kontakt library: https://www.youtube.com/watch?v=kcqyhGpvx7Y At first, it’s played in Bitwig Studio, where playback and stopping are repeated without any issues. However, when played in Cakewalk Sonar, you can see that the CPU usage reaches 100% when stopping. This phenomenon only occurs in Sonar and did not happen in Cubase or Studio One.
-
It’s wonderful that the project file has been streamlined and the latency has drastically decreased! However, the issue of crashing more frequently compared to other DAWs still hasn’t been resolved. Additionally, there are many compatibility issues with third-party VST plugins that work properly on other DAWs but not on Sonar, making me feel that this DAW still has many unresolved problems In my environment, the following plugin manufacturers’ products do not function properly in Sonar, even though they work fine in other DAWs (The products in parentheses are their main offerings): Auburn Sounds (Graillon) Xfer (Serum, OTT) Native Instruments (Kontakt with third-party Kontakt library) iZotope (Ozone) kilohearts Many others Of course, I fully understand that sometimes the issue lies with the third-party plugins themselves and that it’s unreasonable to expect Sonar to support all VSTs. On a separate note, there has been a bug for several years now where noise occurs during export, even in small and low-load project files. This issue cannot be avoided by freezing or bypassing FX, and I have no idea how to resolve it. I have had detailed exchanges with support, providing dump files and screen recordings for both the VST-related bugs and the noise issue, but none of these issues have been resolved.
-
Thank you for the response from the development staff. I have great respect for those who have provided professional audio production tools for decades. First of all, I did not think that the development of a DAW was on a small scale. I wanted to deepen my understanding of DAWs and tried to study C and C++ just a little (not even to the level of dipping my toes in, just enough to understand if statements), but I was considering how difficult it is to handle audio with computers and programming, and how much manpower and time it would require. I could imagine that the profit margins for DAWs are low. Therefore, I was genuinely worried when Cakewalk by Bandlab became free, wondering how the development would continue. Also, I saw people in the forums asking for a one-time purchase option for Cakewalk Sonar, but I believe that subscriptions are better for ensuring revenue while continuing development. Of course, if there were a one-time purchase option, that would be nice too. I have seen many bug fixes over time. I always enjoy reading the patch notes. Seeing thousands of bugs being removed is certainly valuable. When my shoes truly no longer fit, I'll quietly buy shoes from another brand. I still have some concerns, but hearing directly from the staff that "we have accomplished more than when we were with Roland or Gibson" alleviated many of my worries. I will continue to support the development.
-
I see, considering past troubles, it is true that the events of the past few years are not particularly significant. Additionally, thanks to your insights, my perspective on BandLab has changed. After being acquired by BandLab, the continuous updates and bug fixes over the years have been remarkable. I appreciate the valuable information about the past.
-
You've been using Cakewalk software for 32 years. As both a Cakewalk user and in your music career, you are a senior to me. Did you ever feel any concern about the series of acquisitions and sales by ROLAND and Gibson? Also, after 32 years of development, it’s inevitable that the development team would change, much like the paradox of the Ship of Theseus. I can only hope that software development under the Cakewalk name will continue.
-
I see, just as everything tangible eventually crumbles, no software lasts forever. All I can do now is subscribe and diligently report any bugs as they arise.
-
Thank you for the valuable information. In Japan, the notice of Cakewalk's sale came through a Japanese company called TASCAM (a subsidiary of Gibson). Due to my youth at the time, I didn't have detailed information. You told me to think for myself, so I did my best to consider it, but does that mean it's correct to assume that the development team from that time is no longer there? Regarding the development environment and business plans, we have been significantly affected by ROLAND and Gibson's business decisions, which put us in our current situation. Why, then, can we say that we are not in a position to speak about management and business? If development is stopped due to similar failures twice, it is inevitable that paying users will become anxious about such a concept. I apologize if my remarks seemed confrontational.
-
Thank you for your valuable opinion. Unfortunately, I don't consume coffee or energy drinks at all (they give me headaches), and yet I still experience this kind of anxiety. It might even be a type of mental illness at this point. Additionally, while I do make some money from composing, if you are a professional Hollywood composer or similar, the number of my compositions would be significantly less. My skills and career are somewhere between amateur and professional, so they're not particularly impressive. Also, it is difficult to keep track of all the information in the forum, so I may be lacking in knowledge in some areas. Only two responses have come in for this topic so far, but the opinions seem more optimistic than I expected, making me feel that I might just be worrying too much. I would love to make the employees at Cakewalk wealthy, but I regret that I'm not in a financial position to give money to others.
-
Thank you for your honest opinion. I was initially excited about Cakewalk Next, but with its current features, I feel it is not a product that can be used practically or effectively. So, it seems impossible to help me. lol
-
MIDInco started following Regarding the Opacity of Bandlab and Cakewalk
-
I am a composer who has been using SONAR since 2013. I am delighted to see SONAR being renewed as Sonar, especially given the unstable transition from Roland to TASCAM and then to Bandlab. However, I have several concerns. There appear to be various issues related to the development team, development status, management, and other aspects. As users, we have to deal with this DAW, which is buggy and unstable, while continuously paying for a subscription without detailed information. Additionally, the website lacks the content volume seen in Cubase or Ableton (though this may not be crucial), and it remains simple and has not been updated even after more than two years. The community is also underdeveloped. I am quite anxious about these issues. 1. What happened to the employees before Bandlab's acquisition? 2. If the current development team consists of different members, how has the development environment been transferred? 3 .Is there a necessity to develop Cakewalk Next, even if it means delaying the release of Sonar and bug fixes? I love Sonar and hope it will be a DAW that I can use for decades. I would appreciate hearing others' opinions and any additional insights on these matters.