Jump to content

kc23

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

10 Good

Recent Profile Visitors

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

  1. Then google this stuff and read. Newsflash: you are not unique in this world, others have had the same questions, although have expressed them in a polite and respectful manner... and they have been answered. So, go do your homework, instead of coming here complaining about and demanding stuff you ignore because you just don´t want to take the time to research about it. Want some help? start by helping yourself. Don´t like what´s being offered? then don´t install, nobody is forcing you.
  2. This observation was already made, so I posted about both issues on the feedback forum. Thanks for that link, I actually looked around and didn´t find it. Got a couple of other request, so will put it to good use. Great! Actually I thought it was related to my system, so I endured it till it was time for my usual system restart. I just did it, and also just got the chance to confirm it on another system. Any way, thanks for the attention and quick addressing of the issue. Will try and be more careful about keeping things on topic.
  3. Hi On this option, documentation says: "Single Bounce Per Track Check this if you want to create a single clip for all the bounced audio. If you don’t check this, each separate clip on a track creates a separate clip when you freeze the track." However, when unchecking "Single bounce per track" option in the Freeze Options dialog box, freeze function will only bounce first clip and make disappear remaining clips in the track. It has been like this for several past versions of CW, including present 2020.07 Early Access version. Already tried this in two different computers with same behavior on both. To verify: -Open a track with several audio clips in it. -Right click on freeze button to open options dialog box. (Fig 1) -Uncheck "Single bounce per track" option. Hit "Ok". (Fig 2) -Click Freeze button. CW Freezes only the first clips, and remaining clips disappear. (fig 3) -Dotted line indicating presence of clips remains, but they are not visualized and can´t be played. (fig 4) -Press Control-Z to undo, CW unfreezes only first clip, remaining clips still can´t be visualized, even though dotted lines indicate their presence. (Fig 5) -Upon opening take lanes, disappeared clips can be visualized only in main track lane but not on take lane (Fig 6), but still can not be played. (Fig 7) As stated, have tried this in two different computers with exactly the same behavior, even after complete system reformatting/restart. and clean install. It doesn´t matter what audio clips are present. It happens with and without plugins instantiated in the fx box. This has been happening since at least the last three CW updates, including present 2020.07 EA version. Please fix this evident bug, as it has been always working and has ceased to function, and is clearly not intended behavior. Thanks. P.S.: Also, please fix the External Insert plugin, for it to have true mono routing, as requested in this thread: Thanks.
  4. Hi Noel Thanks for answering. Regarding the freeze bug, it is present on the actual official release, and on the Early Access release, so I think it is relevant to this thread. Regarding the External Insert fix request, I have posted about it in the Feedback forum more than twenty days ago (July 11), and it has not been addressed by any staff member yet. Since this is also present in the Early Access release, it may also be relevant to this thread. Abiding by your answer, I will also post this report to the Feedback forum. Hope both issues can be addressed and fixed. Again, thanks.
  5. Bug Report: Uncheck "Single bounce per track" freeze option is broken Hi On this option, documentation says: "Single Bounce Per Track Check this if you want to create a single clip for all the bounced audio. If you don’t check this, each separate clip on a track creates a separate clip when you freeze the track." However, when unchecking "Single bounce per track" option in the Freeze Options dialog box, freeze function will only bounce first clip and make disappear remaining clips in the track. It has been like this for several past versions of CW, including present 2020.07 Early Access version. Already tried this in two different computers with same behavior on both. To verify: -Open a track with several audio clips in it. -Right click on freeze button to open options dialog box. (Fig 1) -Uncheck "Single bounce per track" option. Hit "Ok". (Fig 2) -Click Freeze button. CW Freezes only the first clips, and remaining clips disappear. (fig 3) -Dotted line indicating presence of clips remains, but they are not visualized and can´t be played. (fig 4) -Press Control-Z to undo, CW unfreezes only first clip, remaining clips still can´t be visualized, even though dotted lines indicate their presence. (Fig 5) -Upon opening take lanes, disappeared clips can be visualized only in main track lane but not on take lane (Fig 6), but still can not be played. (Fig 7) As stated, have tried this in two different computers with exactly the same behavior, even after complete system reformatting/restart. and clean install. It doesn´t matter what audio clips are present. It happens with and without plugins instantiated in the fx box. This has been happening since at least the last three CW updates, including present 2020.07 EA version. Please fix this evident bug, as it has been always working and has ceased to function, and is clearly not intended behavior. Thanks. P.S.: Also, please fix the External Insert plugin, for it to have true mono routing. Thanks.
  6. It would seem this issue does not merit the developers engaging on the subject, even after so many years of it being mentioned and without a solution. With the latest updates (a few of the last ones at least) being directed more towards composing and production features (as well as bug fixes) which are always welcomed, I hope the next ones tend some more to mixing and audio features and fixes, like the one being requested in this thread. Cakewalk being such a powerful daw, it should not be left behind in this area. If the bakers think that hybrid mixing is not as relevant in this day and age, therefore not implementing features for it but also not even fixing what is already in the software, I´ll leave a couple of resources about this topic, bearing in mind that these are from the last year. I hope this will shed light on how relevant and contemporary is the use of audio hardware not only as a front end, but during the mixing and post-production process in today´s professional environment. Again, to the bakers, please address this issue and fix the External Plugin so it can work with true mono inputs and outputs. Thanks. VintageKing article: https://vintageking.com/blog/2020/07/the-state-of-hybrid-mixing-in-2020/ MixbusTV video:
  7. Hi You asked me about this in the other thread... actually my I/O is named a bit different although similar, but I get the point of what you are requesting. In the meanwhile, I found this thread from the old forum which mentions the names being in the aud.ini file... maybe renaming them there would help you? I haven´t tried myself, as I´m already used to this quirk... Anyway, hope your request is taken in to account! http://forum.cakewalk.com/Where-Can-I-Rename-My-Device-InsOuts-m1449022.aspx
  8. A while ago I had a Scarlet and it always had latency... never tried to route hardware through the mix control though, didn´t have the highest opinion of focusrite drivers... is your computer really powerful that it "compensates" enough for roundtrip latency? at the very least the buffers should introduce some, and even 5 to 10 ms is something that would make parallel processing feel phasey... But yeah, that´s another advantage of hybrid... no cpu consumption on external hardware...! Man... that´s a shame, with sooo many channels... Not only that, but since the external plugin defaults to stereo, any plugins used after it (or in your case, the Antelope ones) are using double the cpu processing... so the problem is not only the half I/O capabilities, but also the double cpu taxing... C´mon BandLab... score us some points!
  9. Well, "proper implementation" would be the one not with, in your own words, "a plug-in that assumes I want to eat up a stereo pair." I posted a couple of videos of the way StudioOne is doing it, one is of the first iteration, and the next one of the update done sometime later to it. I haven´t tried StudioOne, but just checking those videos out and thinking that they did well and then felt the need to update it, makes me salivate. Reaper I have tried and still use, and is as simple as it could be. You instantiate a plugin, route it to mono or stereo, patch, ping, and go. Mono is mono and stereo is stereo. ProTools takes a bit of setup, but once it´s done, again, mono is mono and stereo is stereo. And yes, I agree that Cakewalk´s routing is indeed powerful... so it´s even more baffling that this feature´s state is as it is. I so want to keep mixing in CW, but it takes the fun out of using my Distressors and DBXes and WA76es... and it IS fun using them! Just had a look at the Firepod, and it should be able to do this, even more so with two of them. You have eight line outs and line ins in each one, although six of the ins are on combo jacks on the front, but with the aid of a patchbay you should be totally able. A couple of friends that were fed up with Avid and Macs (actually one of them used Logic a lot too), decided it was time to look for alternatives, and I recommended CW. As i said, I´ve been using it for quite some time... done records, pot production for video, mastering, mixing, original music... never found a thing ProTools did that CW couldn´t. But... one of the first things they tried was how to incorporate their high end hardware and multi I/O with it... and once they found out they would be forced to use half the pieces they were used to use, it was a no go. They both ended up in Reaper, as it seems to be the most popular destiny for the Avid exodus. Hehe, I thought it was only my agenda, but thanks for chiming and collaborating in the thickening of the plot!
  10. I think doing it this way is even more troublesome, as you don´t have latency compensation. I see how in mastering it would work, as you just have to go out on a stereo pair to your chain and then return for printing. But in mixing, there would be no way of correctly auditioning your hardware adjustments in real time with all the other itb tracks, or do parallel processing, and will end up having to print and nudge the printed track every time an adjustment is made. In mastering I would think it being useful, maybe for some custom M-S patching of plugins in between hardware, as an example. Also, I think many users with hardware don´t use the external plugin anymore because of this problem, and most likely are using another daw with a better implementation. I know people who have just passed up on Sonar because of this, however liking it in many other regards. So, it´s not that it´s not used because it isn´t needed, I think it´s not used because it´s implementation is archaic and not up to par, therefore making CbB obsolete in this regard. Which, again, is a shame, as Cakewalk has always been ahead of so many "industry standards" regarding implementation of new tech. So please BandLab, hope you guys update and fix this feature.
  11. Exactly! The external plugin won´t let you use the second output. Indeed, a BIG waste of I/O. I have tried this and it "works", but it´s not only "inelegant" but really clumsy... It requires way too many steps more: sending to Aux a track, panning, patching, sending another track to same Aux, panning, patching, making sure gain staging works for both tracks on the same plugin, finally sending each return to their track, and now you´re using five tracks for every two hardware outputs, when it could be just the two. It gets messy quickly and it´s a workflow killer. With a mono able plugin, it would be just instantiating the plugin, patching, gain staging, done! No extra tracks and routing. It has been forever like this, so sadly it doesn´t work as a temporary workaround if it becomes a permanent workaround (with all the good intentions your suggestion comes). If you look around the web, you´ll find this plugin has not changed at all since it was released in 2007 (thirteen years ago!) with Sonar 7. I would think a proper temporary workaround would be to release a mono only version of the same exact plugin, while they work on the development of a proper implementation of this feature. I think it should be worthy of the developers attention. Really hope they´ll do something about it, as it is one of the things (have a couple more listed, but first things first!) that still makes CbB feel kind of stuck in it´s old ways.
  12. Please fix and update the External Insert plugin behavior. As of now, and since it was released, it is forcing stereo outputs, and if you choose a mono output, it hijacks the second mono output of whatever pair you selected first. Even if you set interleave to mono, External Insert will remain in stereo. This is reducing the interface I/O capabilities to half. Even just making another identical but only mono plugin would be an acceptable solution. I made a post about this, with pretty pictures and all, but it has not received any feedback. Hope it gets sorted out.
  13. Hi Is really no one from the development team going to even make a slight comment about this? Is it really going to keep being ignored? Even just making another identical but only mono plugin would be an acceptable solution. All other daws have implemented this in their workflow, so there is still a need for this kind of tool. Haven´t anyone thought that maybe the lack of this implementation is one of the reasons mixers aren´t using CbB for hybrid mixing, therefore having to use the more developed features of those other daws? Is there another way of requesting this other than this forum? Maybe a support email where to write directly to the developers with this request for fix? I have looked but couldn´t find it. Thanks.
  14. The way these drum instruments work is to simulate a normal multitrack workflow for recorded drums. When recording drums, you don´t have an isolated mic/track for each cymbal, you just have overheads and/or rooms.
  15. If you have multiple envelopes in the same clip, just doing it without changing focus to clip automation would result in dragging all envelopes present in said clip. So, I would think that amounts to confusing behavior. If you want to save the mouse trip over to the envelope selection menu, clicking on it to display the menu and then selecting automation-clip gain, you could just shift-click on the gain envelope so this will change focus to it (or any other envelope you shift-click on to), adjust, and then shift-click again on the clip itself to focus on it again. Its really fast and just a couple of clicks more with modifier. Hope this helps.
×
×
  • Create New...