Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

13 Good

Recent Profile Visitors

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

  1. During extended sessions and upon reopening a project, I often have to reselect the input setting on a track before it will respond to my external midi keyboard. To clarify, CbB does visually respond (PRV), but the signal does not echo through the intended external or softsynth. My setup takes all midi inputs through a usb2 midisport patchbay (legacy driver for the product ended development in 2013). I haven’t determined the conditions for when this occurs. I’ve noticed it sometimes when returning from sleep mode (Win 10 64) on my laptop, and sometimes just in reopening a project, but I’m not certain that it follows as a rule. Sometimes (but not always), the established input for tracks gets arbitrarily reassigned to the last port in my pick list. Are there any settings within CbB that would mitigate this issue, or at the very least would make it less cumbersome to restore desired function. Hitting the midi/audio reset button, does not solve my problem. Currently, I find myself having to reselect a preset input for all effected midi tracks whenever this occurs.
  2. Thanks for both responses. This got me away from thinking of this as an OS or Manufacturer problem. I'm relieved and little embarrassed to admit that this was entirely self-inflicted and recoverable. I had been chasing down a problem with a flaky chain preset (BT-stereo was embedded) over several days. I've since resolved that issue, but during the course of my "troubleshooting", I had applied the J-wrap load option on BT-stereo. This was the sole cause of the reported "warning" message. Because this was over a number of days, I had conflated the chain preset issue with the "warning" message. After reading @Scook post, I fired up my Splat installation for the first time in about 2 years and realized that the problem only existed in CbB.
  3. Has anybody else seen the following warning. It just started popping up during the last few days, during project load. This has been popping up in all projects that contain BT-stereo-imager by Nomad, widely used since my SPLAT days. True to its word, the warning bypasses this effect (and, I assume all other resident Nomad plugins). I’m currently upgraded to latest greatest on CbB, and Win 10. I also tried porting it through J-bridge in an act of desperation, but the first attempt did not improve my situation and I'm skeptical whether any settings would help. Any suggestions? Thanks
  4. @Barry Seymour, I'm glad to hear that the mfr driver got your DAW purring. If, moving forward, you see any further issues with audio drivers, consider also disabling Realtek HD Audio for sessions where the Behringer is connected. You didn't mention it above, so I'm just assuming. Years back, realtek generated all kinds squirrely interference with my Roland Studio Capture, at the weirdest times. Because, I rarely undock my laptop from the studio, I opted to disable realtek at startup (Task manager) rather than the device manager.
  5. Somehow during the course of a project, my autozoom behaved as though it had rusted in place. As I wrote up the problem, I discovered my own fix (described below). Can anyone explain what happened here, and why these steps were necessary? I've attached a skeleton version of the project, for reference. Thanks Towards the end of a project, I found that the auto track zoom feature had stopped working I finished working under this limitation and then made a copy to isolate the problem. After deleting track by track, I never really determined the source of the problem, but I did figure out the following solution: 1). When I select track1, it doesn’t expand automatically. 2). If I select and expand track1, then select track2, track2 does not expand, but track1 returns to minimum height. 3). By accident, I hit the following resolution. Select multiple tracks (at least 2). Expand by dragging any of the selected tracks. Return these to minimum height. Select and expand 1 track to desired auto zoom. Now, when I select any track, auto track zoom works again. I don’t know whether the problem was triggered by user action, a restart of the DAW, or corrupted data. I do know that autozoom worked earlier in the project. No auto zoom.cwb
  6. I just completed a project that sounded way above my pay grade because articulation KSs were absolutely not more trouble than I deemed them to be, this time. Thanks articulation maps. One peculiarity that I did notice in the last stage of midi cleanup, was that articulation did not carry over into a flattened comp. In this case, I had 4 take lanes (muted after flattening) and a soloed "Comp” lane. After playing around, I found the articulation working in the muted Take Lane 1. After wiping all other data from take 1, and unmuting, articulation was recovered for the track. It’s not a showstopper, but this first time, it took a learning curve to recognize that I had a problem, and backtrack through tasks to resolve it Is there a better way for users to flatten a track that contains articulation?
  7. @Promidi, Your explanation above helped me to add needed cc's to my PRV controller list. So now, of course, I'd like to push my luck. Is there a way to configure multiple selectable lists of controllers for the PRV? For example, I would like one controller list for GM instruments, and another to handle controllers related to JABB brass instruments, and perhaps another for Garritan string instruments?
  8. With all of the Covid downtime, this year produced the most studio improvements and much needed maintenance since I first started to dabble. My best 2020 purchase was TB_morphit headphone correction, because I've never worked with monitors, and I finally appreciate the value of getting a "flattish" response out of my "good" headphones. Mixing, mastering, and ear fatigue have all improved.
  9. Nigel, Your suggestion is absolutely correct in noting the height tradeoff and that "+/-" are a simpler method for folding up all tracks within the Trackview. My above suggestion was also aimed at taming the Console view as well, especially for that gangly project phase when I still have a wealth of empty midi tracks or spitballed ideas that are not quite ready to be archived or deleted just yet. 1). Clicking on a Folder Midi/Audio-Qty hides/unhides tracks in both Trackview and Console views with a single click. Conversely, when you click on "+/-" in trackview, folded tracks still remain visible in Console view. For those many talented CbB users on this site, who can hear an original song in their heads and accurately reproduce it one track at a time, this tip may not make much of a difference, and your smug displays of musicianship have earned my boundless envy. Honestly, I'm not at all ashamed to admit that my workflow is well, slightly less hygenic than that; and it requires hanging on to far too many slop MIDI tracks, until I'm beyond convinced that even the tiniest bit of gold can no longer be dredged or tweaked out of the excrement. In any case, if one carries excess tracks, I find it very handy to control what you can see in console view at the click of a button, rather than scroll across many pages of minimized faders that you don't need to worry about right now. 2). My projects tend to start by loading a Multitrack Synth (like TTS, Aria, and legacy Hardware Synths) to its own folder and add Singletrack synths (Studio instruments, Addictive Drums, TruePianos, AAS and sample libraries) only as needed to a composite folder that I call "Standalones". There are exceptions, but that's the general path that I take, using project templates, and track templates (including buss assignments) wherever possible. As the project progresses, I usually reassign (and move) some of the scratchpad TTS (or hardware) tracks to custom Singletrack synths for more textured sounds. I think this process grew out of necessity, when available RAM, CPU, and storage had proven insufficient to fend off crashes, audio dropouts and latency. Even with hardware upgrades, it's remained a useful discipline for me to follow. Particularly for the Multitrack synths, the Console view gets unwieldy when I start with a canvas of 16 available midi tracks and however-many output tracks that are needed to shape the audio. Until I'm ready to move/delete/archive the excess tracks, I find it useful to view the midi-only tracks while Recording/Editing, and view audio-only tracks while Mixing frozen or recorded audio. The same approach is also useful when recording Kick/Snare, Hihats, Toms, and percussion as separate MIDI tracks. I haven't done much with loops, but I'd probably isolate those to their own Loop folder, just as I would Vocals to a Vocal folder. My best organization practice has been to establish an "Archive" Folder to hasten moving archiveable tracks out of the way. These folder tracks remains a hidden part of the project until mixdown, when I'm ready to delete. I've settled on an obnoxious bright yellow color for the archive folder and tracks. There's something therapeutic about finally removing the folder from view. I believe there's also a CPU/RAM overhead benefit in selecting the archive button for these unneeded tracks. Overcrowded console view may be much less of a concern for those who work exclusively with Singletrack synths and/or recorded audio, since you don't technically need separate midi/audio tracks. I'm sure there are plenty of other valid strategies for project and folder organization. This is simply mine. Sorry for being so thoroughly verbose on the subject, but I just haven't found this feature documented anywhere in the manual and I find it to be really very useful. I believe it's fair to credit Craig Anderton for first bringing it to my attention years ago in one of his many tips.
  10. Thank you!! My projects were getting way too unorganized. 😂 Here's an additional folder tip that I use often... Once you have successfully added tracks into your newly organized drum folder, increase the height of the folder track, so that you are able to see the table of Midi and Audio tracks contained within. Based on your example above, I'll assume you'll have some nonzero qty of Audio drum tracks listed. If you click directly on that number, CbB conveniently hides all audio tracks into the folder in both track and console views. Click it again, and they reappear. There are other ways to accomplish the same action, but this methodis particularly efficient. For larger projects, it is common for me to have only track folders in view until I'm ready to unhide the specific folders that I'm ready to work on. I also have a tendency to alternate hiding either midi or audio tracks depending on whether a synth has been frozen. Once everything is frozen to audio, the midi tracks are best hidden unless, I have to unfreeze for additional edits.
  11. The ability to select a patch from an ins file for VSTi's wasn't meant to be a full-blown feature; it was added more as a convenience for users such as yourself using emulations of older hardware. The current ins mapping relies on being mapped to a fixed MIDI port, which is fine in the case of hardware ports, but software MIDI ports come and go. The effort in making it more integrated with VSTi's is not trivial. FWIW I'm using the standard "Yamaha XG" definition with the S-YXG50 (running using the JBridge wrapper), and auditioning patches via the patch browser is working fine for me.... as long as I have an output channel set on the track. The only gotcha with the Yamaha XG definition is that it's bank 0 defaults to "none", which results in no bank select being sent out. Attached is a modified version of the Yamaha XG definitions which forces a bank select 0 to be sent for those patches. Yamaha XG - fixed bank 0.ins 22.89 kB · 1 download Mark, My Q2 and Q3 were definitely wishlist, so I fully appreciate the considered response. After running the plugin through JBridge per your suggestion, the patch browser live-audition request works as desired (Q1). For kicks, I switched it back off and it still worked. I'm not sure whether JBridge fixed the problem, or an earlier reboot, or a rescan, but I'll keep it selected moving forward.
  12. Thanks to all of the bakers and testers for a most substantial release. While Articulation is understandably sucking up a great deal of oxygen, I just wanted to focus a few comments on the VSTi instrument definitions feature as well. Using the S-YXG50 VSTi, and a custom instrument definition, I was able to select defined patches using the patch browser. This is a great improvement over looking up banks, patches, patchnames from a separate table document. However, it also leaves me considering the limitations of this new feature. During my test, I performed the following: With a valid channel selected, and the patch browser window open, I selected “List Patches From” to choose SYSG50 (my custom instrument definition). The browser then displayed the available defined instruments in the window, which can be successfully auditioned only after I selected OK and closed the browser. Q1). Is it possible to audition patches based on where the cursor points in the patch browser, rather than requiring the user to hit OK and close the patch browser? In other words, I would like to audition live parts by scrolling through the patch list just using the arrow keys. Q2). Is it possible to show the selected bankname and patchname in the console track? I believe that this linked information currently comes directly from the VSTi internals, but perhaps it could be redirected to the output of the “List Patches From” feature whenever <default for instrument> is not the selected list? Q3). Once a patch has been selected using “List Patches From”, the task of changing to a second patch requires repeating the whole process from scratch. Instead is it possible for this feature to store/remember any portion of previous selections on the same track? (Selected instrument definition, Selected Patch). By the way, I've attached a copy of the SYXG50 instrument definition that I created. I couldn't find one elsewhere. SYXG50 custom.INS
  13. Thanks for the experienced feedback, gentlemen. These are all better suggestions than my initial plan of tweezing. The possibility of pushing rather than pulling the tip through seems more prone to success for me. I should have an opportunity to open up the interface over the weekend. If the jack doesn't allow for a push through in either direction, I'll move to the "glue technique". If it does come down to this, I don't necessarily trust my skills in the game of operation with a random rod, but I'm thinking about dabbing glue on the remaining portion of plug that did not break off. I'm assuming the trick is to get the glue viscosity to where it absolutely will not drip, but is still capable of bonding.
  14. After years of hobbying with rack gear, I'm experiencing a first-time dilemma. While removing a pair of 1/4" inputs from my audio interface, I actually had the tip break off of the left input. The situation is not a showstopper for me, because this truly is an optional pair of channels in my setup. But after two days of ignoring this, it still does eat at my soul, thinking that I've made my interface less functional than it could/should be. My hope in writing this, is that someone in the community has already developed a clever hack for this very problem. I do have a few extraction implements that tempt me, from needle-nose pliers to pseudo forceps, and tweezers. My concern with misusing any of these tools is the potential of introducing a short, where one does not currently exist. The interface is long out of warranty, so I'm also free to pop the hood to get a closer look. Ideas? Anyone? Anyone?
  15. I had a similar problem pop up about a month ago. In my case, the cause was a newly detected conflict with the optional midi device provided by my audio interface. This was one that had never been used, but a windows upgrade started to engage. I was able to resolve my issue by disabling the unused midi interface in the device manager. If you're having he same problem the evidence will be in the device manager.
  • Create New...