Jump to content

ptheisen

Members
  • Posts

    87
  • Joined

  • Last visited

Posts posted by ptheisen

  1. If you look at the page for this on the UA site, there are several questions with answers. I'm not sure what to make of the one quoted below:

     

    Is this plug-in included in the LA-2A Collection?

    No, this plug-in is brand new, and is not included in the LA-2A Collection.

     

    So it is evidently not the same as any of the previously developed plugins, but how is it different?

  2. I knew I should have stayed out of it. 🤨 But gosh, everyone else was expressing their opinions, why can't I? I've used Cakewalk since Pro Audio 5 and easily spent more than $1000 dollars on the DAW alone.

    As I said, it was just a suggestion, trying to keeping things simple, and basing it on what is perhaps likely to have been common experience for various users. It is also similar to how some other companies do things.

    I'd say the examples you gave are somewhat less likely, chosen to make your point. But they are certainly possible and I understand your point.

    So you are probably right, the "fairest" way would be to have everyone provide all of their receipts and the cost scale would be based on those totals.

    I've learned my lesson, I won't be contributing to this controversial thread again.

  3. I tried to stay out of this, but I couldn't. Here's my suggestion to Bandlab, trying to be "fair" to all users and Bandlab as well:

    If you purchased lifetime updates, the initial crossgrade to the New Sonar is free, but future upgrades are whatever Bandlab's upgrade policy will be.

    If you purchased Sonar Platinum, or any of the "X" series, the initial crossgrade to the New Sonar is $50, with upgrades as above.

    If you purchased any version of Sonar Producer from, say 5 - 8.5, the initial crossgrade to the New Sonar is $100, with upgrades as above.

    Purchasing the New Sonar outright would be $200, with an option to pay in 12 monthly installments that would let you receive updates for the year and keep that version if you make all 12 payments.

     

  4. I'm no longer using my AlphaTrack since I purchased other control surfaces, so I don't remember the detail or have thems handy. But until then I was using the AlphaTrack quite successfully  in CbB for quite a while, and AZ Controller is definitely the way to go. Maybe AZSlow will see this thread and provide some more  info for you.

  5. On 4/4/2023 at 7:48 AM, msmcleod said:

    I wouldn't go quite that far, but it's very old and complicated code, and of course the original developer is not available.

    I'm sure you're aware that the original developer used what he had done in Cakewalk to develop the stand-alone notation application Overture. And about the time Gibson was starting to lose interest in Cakewalk, that developer had some initial conversations with Cakewalk/Gibson saying that he thought it was possible, and not extremely difficult, to somehow incorporate about 80% of the functionality of Overture into Cakewalk, but Gibson wasn't interested in working with him. (This is according to my memory of some statements made by that developer in the old Cakewalk forum.)

    I'm sure most of the people that want to see Cakewalk improve the staff view would be more than happy with that level of functionality, I know I would. Do you see any possibility of going in that direction, maybe just consulting with the developer, sometime in the future? The developer is still alive and theoretically supporting Overture, but I realize he has not been very active for more than two years, so that certainly makes things more difficult.

     

  6. 1 hour ago, smallstonefan said:

    I decided I didn’t need all those extra mic positions for over a half terabyte of space. 

    It was a difficult decision for me as well. And yes, I had to move all of my Native Instruments libraries to another drive to free up enough space on my largest and fastest SSD.

    I'm sure I don't need 20 mic positions either, but I wasn't thrilled with the single mic position in Core, and Spitfire's demo of the mic positions convinced me I'd have choices in Professional I could be happy with.

    The other major factors for me were the addition of solo strings, and that it appears Spitfire's approach on this library was to include pretty much everything they were ever going to include for the BBCSO in Professional, instead of who knows how many other separate libraries that you'd have to purchase to get everything. For my needs, I may never be tempted again. Whereas, with their other orchestral stuff, and pretty much everyone else's as well, you'd end up spending thousands on many separate libraries if you wanted anything close to the "complete" set. For example, even with the Cinesamples "glitch" sale at ~$80 per library, I would have had to spend a lot more to get something comparative to BBCSO Professional, since I didn't have any Cinesamples orchestral libraries to start with.

    So I think it was very practical for me. YMMV.

    • Like 1
    • Thanks 1
  7. In my experience, this happens more often when some of the midi devices configured in Cakewalk are not turned on when Cakewalk is started. For example, I have about five midi devices configured in Cakewalk. A few of them are USB powered, so they are always on when Cakewalk is started, but I also have two midi devices that are not USB powered. If I consistently turn those two on before starting Cakewalk, the midi ports in Cakewalk are quite stable. If I sometimes don't turn one or both of them on before starting Cakewalk, the midi ports are likely to become jumbled eventually, and it is the first thing I check if a midi device is behaving unexpectedly, because I know I don't always turn on the two externally powered devices.

    I'm not aware of any way to lock the midi ports that Cakewalk assigns to devices.

    • Great Idea 1
  8. You are right, they are two separate things and the DAW compatibility kits are optional. But for the people who hope to be able to use their keyboard as a control surface for their DAW without having to do a lot of  work, that is what the DAW compatibility kits do. You just install them, get the midi and control surface inputs/outputs configured and everything magically works. Without them, very little, if any, of the control surface functionality works out of the box, it is just a midi keyboard.

  9. Just in case you missed this, the LX series have custom software that enables quite good integration with Cakewalk. It has to be downloaded separately from Nektar after registering your keyboard with them. Looking at your screen shots where the keyboard was identified just as MIDI1 and MIDI2 leads me to believe you have not downloaded and installed this software. Cakewalk should see two inputs [Impact LX88+ and MIDIN2 (Impact LX88+)] and one output [Impact LX88+] for your LX keyboard. If you use other DAWs as well, they have separate software for each DAW, you can download and install as many as you want.

  10. Stephen, for what it is worth, the Nektar P4 is not designed to fully integrate with Cakewalk, but the Nektar LX+ series is. I have the Nektar LX49+, it works completely as advertised and I am happy with it. The trade-off is that the LX+ series is not as technically advanced in some ways as the P series, which is more focused on plugin and instrument control.  So neither is perfect and each person has to decide what is more important to them.

  11. Thanks so much for the wealth of information. I think it explains what I'm seeing.

    The mappings appear in the ACT tab of AZ Controller, but they are not "connected" to the M32 knobs because they are associated with the ACT rotors, not the ACT sliders, and it's the ACT sliders that are associated with  the M32 knobs. And since I'm starting with a clean slate, I'll have to manually convert all of the FX and instruments I want to control in this way. Do I have that right? I'll experiment over the next few days and see what I can do.

    Do you know if there would be any way with the M32 to have a selectable "flip" in mix mode, where the knobs control pan instead of volume? I know the shift key does this, but you have to maintain the press of the shift key while turning the knobs. Since I don't have a right hand, that's not really possible. It would be great, even if I have to give up some other functionality, say the Loop toggle, if that could function as a latching shift key. Maybe it's not possible, since the shift functionality seems to be strictly internal to the M32, but if anyone could think of a way to do it, you could!

     

  12. Thanks so much for doing this Azslow3, I'm trying it out with my M32!

    Most things appear to be working as you explain on your web site, that is great.

    When I first installed it, the ACT sub-mode was partially working, a few parameters of focused effects would be mapped to the knobs and work as expected. Then I saw your instructions to delete all of the XML files, so I did that, thinking that the ACT sub-mode might work even better. But it's not working at all now. I even reinstalled the NI M32 preset, but no parameters are mapped in ACT sub-mode, though the Metro light is bright indicating it went into that mode. Do you have any idea what I might have done wrong and/or how I can get the ACT sub-mode working as intended?

    Thanks in advance for any advice you can provide!

  13. Reading about the CPU load for B-3X in multiple places scared me away from it for quite a while. But yesterday I decided to try the demo and see what happens. I could run the stand-alone application at 48k and a 32 buffer with no more than about 4.5% CPU load. Even at 96k and a 64 buffer it didn't go over 9%. Is that what other people are seeing as a high CPU load, or are they seeing significantly higher loads? My computer isn't fancy by today's standards: I7 4770k @ 3.9Ghz, 32Gb ram, a couple of SSD drives.

    I didn't think the CPU load was too high, and since my crossover price with jam points came to $70, I bought it and I like it.

    • Like 1
×
×
  • Create New...