Jump to content

Keni

Members
  • Posts

    2,764
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Keni

  1. Yeah, I contacted them. Their recommendation? Buy the new version as the one I have is long defunct and no records of purchases that old exist. They want $149 for it and being 60% below poverty level, I let that slide. Fir me at the moment it was between Cherry Audio's at $39 and the UA at $59. I decided to try the UA as I already expect the Cherry to be excellent, but a heavy resource demand. In that respect I did ok as the UA appears very resource reasonable.
  2. BTW I also bought the dbx160 being an long time user if these. Not perfect fir everything, but fabulous tool for making things pop! Though I no longer own any hardware 160s, I do still own 1 160x which is still simply a rack mount (19”) version that I love. ...and at that price? Again I couldn’t resist! Sending me deeper into my financial trouble zone, but smiling! ????
  3. So hard to chose. There are so many that are all excellent. I really like the Cherry Audio stuff, but even tho they managed to thin it a bit recently, they are still very resource hungry. I was very happy with the Arturia version but moving to my new machine lost the authorization for it and though 64 bit, too old for Arturia to have registration info so it only runs in demo mode where it remembers no patch selection or settings and can’t save. So a bit of a pain. I also still have and use the 32bit free MinimogueVA which is actually quite good though maybe not as fat sounding? This one from UA seems quite good, but I’m not 100% happy as it doesn’t allow manual numerical input values. I’m far too OC to trust my hands anymore! ...and is it missing some switches? Maybe an earlier version than I’m remembering. And something "strange" about the modulations controls and such at bottom? Maybe I just need to get used to it?
  4. I’ve still got the hardware sitting in a rack! (In storage, of course)
  5. One shortcoming for me. I guess their' attitude to stay true to original? ...but there's no way to see or access/input specific values fir the various controls. For me that’s a modern convenience that doesn’t take away from authenticity. It can be ignored easily for anyone so inclined.
  6. Yeah. They worked both sides well. I couldn’t afford their' hardware to enable use, but now that they’re native? I see a good future for them here as well. I only own two as of now, (dbx160 yesterday and MiniMoog today) but they feel so solid/stable. If I don’t run into unforeseen issues with product or company I feel sure I will buy more in the future. Especially at these prices!
  7. Wow! I'm stoked! I just bought the UA MiniMoog and couldn’t be more pleased! (Well, owning a hardware versions makes might be?) Beautiful recreation of an astounding piece of hardware! ...and for $49? I'm broke and far below the poverty line but I couldn’t resist this!
  8. Wow! A deal I couldn't pass up! Amazing price! A MiniMoog for $50! https://www.sweetwater.com/store/detail/UADMinimoog--universal-audio-uad-moog-minimoog-plug-in So far the software appears rock solid. Sounds are thick, fat, and present! I have always loved this instrument and this is a wonderful virtual re-creation. I'm loving it!
  9. I know this is relatively a small matter, but it definitely is new as it was only recently repaired as is... In the PRV, it is not retaining the assigned note names/map once again.
  10. Likely close as this last CbB update appears to be slated for this month. I’m hoping that also means that Sonar is about to appear!
  11. I think it's somewhat obvious. They have to have a set cutoff point to all aspects of development and support to a product that will soon be only a courtesy of the people responsible for sustaining this fab product. It is time for us all to move on. With the work they allotted, this is the end of fixing for Cakewalk by Bandlab. Wonderful memories, much gratitude, tons of music, and looking forward to this products future which is now Sonar By Cakewalk! At Last! We're home again!
  12. Yes. This part was not a mystery to me... but some things start looking weird when half of an envelope gets included in the move but not the other... and then other times when track envelopes moved, but MIDI cc envelopes did not or vice-versa... I'm ok though. I've got some new procedures (work-arounds) to handle this type of situation. I doubt it happens to me often or I might have run into this sooner. I've been using automation envelopes in Sonar/Cakewalk for decades now ?
  13. Yeah, I get that... But that's why I was so confused by this. I have to select the clips on the midi track, but then select the audio TRACK so that it includes it. But I've got it working now... As to the remnants? I'm thinking they are due to nodes that somehow didn't get tied to the clip. For example... Four nodes to make the movement, but the last two happen after the clip completes, so it doen't get associated?
  14. Ahhh... Now I found my solution. My Thanks to you once again Mark! My problem was that selecting both tracks (I had tried this previously) must be done after selecting the clip(s) to be moved/copied. Selecting the tracks first selects all clips on both tracks and trying to change that selection within the time frame causes only one track to remain selected. The obvious (though not to old man me) was to first select the clips, then add the additional track selection afterwards. Then it worked fine! Whew! Edit: BTW... An oddity I've found. If I select ALL tracks and execute a move, the envelopes do not move with the tracks. My workaround is to deselect the MIDI/Audio track(s) in question and move them in a separate operation. It seems that the track selection is not including the audio track automation envelopes. An easy workaround, but curious as to why this happens. It appears that the volume envelope on the audio track moves, but not the instrument-related midi controller envelope on that track. Obviously I can work around these items, but I guess it's good to make common some of this into for others to find solutions. If I move the instrument pair as a separate operation, both envelopes move together... ...a note though. After a successful move, there are remnants of some of the envelopes left behind. As there are no midi activities in those locations (in this instance) I can easily ignore them if I'm in a hurry but need to remember if more midi events are added in that location... Edit 2: And I am also finding that all envelopes are not responding correctly. When I move Farther awy into time(right) they move correctly leaving remnants. When I move earlier, they did not move all the way???
  15. Thanks Mark! Much appreciated. I think I understand. I will experiment with this info and hopefully learn! ?
  16. First, let me apologize for de-railing this thread. It was unintentional. I thought I was posting in the EA forum. I have no idea what moved me here? Either I did somethng weird or maybe a forum manager? OK... I tried it out of curiosity and as we suspected, it works as expected. Missed a node but that may have been my quickie edit... If I unfreeze, the MIDI is unchanged from it's pre-frozen stuff... So it is that the envelopes are not relating to the midi clips on the related MIDI feed.. I don't remember this dilemma before. OK... I did just find where I can do the MIDI controller on the midi track as I would any other controller (assigned to mod wheel) and I expect moving/copying would work fine there as it becomes part of the clip. The problem exists when assigning midi controllers to envelopes as the envelopes don't record from my kybd's controller there. It does on the audio track. I also just tested that Other than recording the midi event from my keyboard as midi events, I can manually create a proper envelope on the midi track. So it comes down to I can record the performance action only as midi events. I can manually create/edit the envelope on that track but it will not record as an envelope. I can easily adjust to using the midi events for the mod wheel so I can record it on the midi track but it still leaves the problem of the volume envelope on the related audio track. There is no such creature on the midi track, so how to get the envelopes on the audio track to realize that they are connected to the clips on the related midi track? This one's difficult. It means I must manually repeat every edit manually. When the track is frozen they must already be in place and I freeze after a track is complete. So how to get those volume changes to know they are related to the midi clips on the associated track is the problem...
  17. Thanks Jonesey... I thought of that too as a workaround, but I felt so sure this used to work. I haven’t tried it but even that gets complicated if I must repeatedly freeze/un as I shuffle things around. I'm having a bit of a bewildering day myself...
  18. A few things have come to mind. The envelopes not getting copied are on the audio track of a VST instrument. Until it is frown, there are no clipcs on it. The clips being copied are on the associated MIDI track. One envelope is a volume envelope so it's obvious to be on the audio track, but the other is an instrument specific envelope (leslie speed on b3). I cannot get it to record it on the MIDI track and must record it on the audio track... Difficult situation. Especially thinking I now may have to r-do all those changes yet again if I'm not happy with the new arrangement... <sigh>...
  19. Thanks... Yes... I mentioned so... This made my morning session painful. I had to manually re-build a number of envelopes repeatedly as my arrangement was changing...
  20. once again, the PRV Assigned Note names are not sticking. I must reset them every time I open the PRV This was somewhat recently fixed... Reversion?
  21. I just ran into this? Seems EA related as I do this often and this is the first time it's not performing as expected... I have a few virtual instruments and one audio track. I have selected the copy all track envelopes with clips When I drag a group of clips, the envelopes are not being moved with them? I will explore more...
×
×
  • Create New...