Jump to content

Terry Kelley

Members
  • Posts

    880
  • Joined

  • Last visited

Posts posted by Terry Kelley

  1. 20 minutes ago, Noel Borthwick said:

    Guys I think there is some disconnect about what Sonar is. We aren't changing the core Sonar code from what Cbb is so its not changing the user interface. You can think of it as exactly the same as what you are using but with some new features. i.e. treat it similar to a major point upgrade over CbB. The UI will look nicer and be more modern as well.

    So it sounds like:

    1. CbB will get updates with some new features but that will be the end of the road for it.

    2. The CbB core will get a new UI and become Sonar. This is the main product going forward.

    3. You're releasing a totally new product called Next directed towards song writers. This will also be ported to MacOS.

    4. You're also porting Sonar to MacOS to compete with the big boys. <--- Not true per Noel.

  2. On 6/5/2023 at 11:13 AM, msmcleod said:

    The documentation mentions selecting the sections first... you don't actually have to do this.  If no sections are selected, clicking the "Add sections to arrangement" button will add them all in their current order.

    So @Starship Krupa:

    1.  Make sure nothing is selected
    2.  Click the "Add All Sections to Arrangement" button
    3.  Delete the section you want to skip from the arrangement
    4.  Click the Arrangement play button.

    Well FMD!

  3. 2 hours ago, bitflipper said:

    I'm not battling anyone, nor am I blindly defending my preferred DAW. Just basic troubleshooting while trying to avoid a classic causation vs. correlation logical fallacy. Let me explain my reasoning, and feel free to correct any logical errors I may make in the process.

    Let's start at the beginning, by looking at what a c0000005 error is, and how it comes to be raised. 

    This particular error code represents an access violation, which means the software has attempted to write to an address location that it does not have permission to write to. Usually, this is the result of an uninitialized pointer, a variable that contains a memory address but that hasn't been given a value. Because all variables initially default to zero, the pointer is pointing at address 0. Although 0 is a valid memory address, it's in a part of memory that's reserved for the operating system kernel and cannot be written to by user applications. The O/S protects itself by refusing the operation and raising an error so that the offending application can deal with it.

    How does a pointer get initialized? That's up to the programmer who wrote the code. That's why it's safe to assume that a c0000005 error is a bug in the code that raised it, and ultimately human error.

    I apologize if you knew all that already, but it's important to understand how this error happens and why. The key concept is in your statement that "...This is not the only plugin that has generated a c0000005...". The salient point is that it was the plugin that attempted to write to protected memory, not the DAW. The error was raised by the plugin, not the DAW.

    Granted, the plugin may have been referencing an invalid pointer that the DAW supplied it with, that's not impossible. However, any pointers passed to the plugin (e.g. input and output buffers) would be the same pointers the host passes to all plugins. If they were invalid, the DAW would crash every time you attempted to use any VST plugin. From a software developer's perspective, it is always the module's responsibility to validate arguments, and to never assume that the caller guarantees they are valid. Usually, that means the plugin will refuse the invalid pointer and notify the host that the call has failed, in which case the host would be tasked with processing the error. When this is the case, it won't be the plugin that was identified as the offending module in the dump, but rather the DAW. But if the stack dump shows a plugin's DLL as the failing module, then that's where the problem originated.

     

    That and girls. I've had many an access violation.

    Seriously, great overview of the issue. C0000005 is frustrating to deal with. And there have been times where the developers were able to point to the specific issue and contact the VST company. It's not silence like some believe.

    • Like 1
  4. I'm staring at my Cakewalk for DOS floppy and thinking about how far we have come (users and the developers.) Given some of the issues with the past (such as how Cakewalk ended in 2018) there is no reason people can't express their doubt and concern and it IS justified even if those that made that happen are no longer involved. As one person said (paraphrasing) 'Engineers go about things often far different from marketing.' 

    But considering how CbB and the developers themselves have treated us since 2018, I willing to give them a lot of leeway. And I'll bet they don't forget about us. Maybe we will be the ones that benefit from our willingness to try and help (even when I did ask extraordinarily stupid questions that caused them to burst out laughing.)

    As long as I can use Cakewalk, I will continue to use it. Hopefully I can. With a little want included. :)

    • Like 2
  5. I said want. And it's not impossible but certainly unlikely. And if I disconnect from the internet Windows will continue to work even if it never connects again. The fact that companies do it now doesn't mean it's desirable.

    Get ready, your heated seats, remote start and entertainment system in your car will be subscription.

    Want.

    • Like 1
  6. Considering the fact that CbB barely gets honorable mention if any mention at all in DAW reviews, management has to know they can't expect to compete with the current favorite DAWs by pricing in their range with these new products. Maybe they will go for generating a user base to pay the bills first and price it somewhere very inciting.  At least, I hope so. 

    But as said, we have to see what reality turns out to be.

    • Like 3
  7. I always assumed this "free" thing was temporary. Maybe that change is at hand. If I have to pay, I will judge the cost vs value and go from there. If I get a decent break, cool. If I don't - I have wandering eyes.

  8. Sorry Bruno, I don't get what you are saying.  I can see the PC controls in the track view when the inspector is closed?

    I can see the track controls in the inspector, yes but not the PC controls on the track. I didn't mean to suggest otherwise. I want to have the inspector closed and know the PC is active.

  9. Not in my opinion. I want to know if PC is active if I don't have the inspector open. I want to the track to tell me. I often don't have the inspector or PC open. I don't want to use the inspector when I don't want to use the inspector LOL. But hey, what do I know, eh?

    I don't think there's any risk of the developers jumping on this and doing anything.

    😀

     

  10. image.thumb.png.8762c4cc1af8c152584931445691e4f2.png

     

    HI Mark, 

    I don't see anything. Maybe I'm not being clear. In the Track View, I don't see any indication that Pro-Channel is active. You can certainly see it's active in the Pro-Channel window itself but if that is off or the Inspector window isn't open, there is nothing in the track section itself that lights up. For example, track 15 has Pro-Channel on. Maybe I'm missing something. I did switch back to stock the themes in case Flat White Matcha doesn't show it but I still didn't see anything.

     

     

     

    image.png

    image.png

×
×
  • Create New...