Jump to content

Sleetah2000

Members
  • Content Count

    27
  • Joined

  • Last visited

Community Reputation

9 Neutral

Recent Profile Visitors

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

  1. 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.
  2. 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
  3. 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.
  4. 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?
  5. 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.
  6. Sleetah2000

    Volume limit? Help

    Nigel, I'm finding your explanations on gain staging to be very helpful. I'm also starting to see why some of my older mixes have worked and others are just muddy messes, even as I was following what I thought were best practices. To top it off, you introduced me to the Creative Sauce tutorial series. Thanks or accelerating the learning curve.
  7. Windows 10 has recently been asking me to setup preferences regarding (MS) Notifications&Actions, and Focus assist settings. This is not to be confused with CbB Toast notifications, which I find to be very helpful. These MS "features" (Settings/System/Notifications&Actions) seem intended to cut down on overall nuisances/alarms for general usage in working in Windows. However I can't help but think that a failure to optimize these settings would result in either robbing resources from Cakewalk on one side, or potentially introducing untimely alarms and workflow interruptions to the recording or playing process. 1). Is this a valid concern? 2). If so, are there recommended settings or workarounds to minimize these issues? Thanks in advance.
  8. Thanks so much for the uploaded sample. It brings back memories, and I hope to incorporate it shortly into an old piece I worked on. My delay in responding was no better, but I'm happy to report that I was unplugged for some less hectic distractions. Regarding the original question of sampling plugins, I still haven't decided between the more tweakable samplerobot pro, and the simpler less expensive samplit option. My research corroborates the comparative descriptions, but it's still tough to tell which plugin would satisfy me in the longrun. I'm leaning towards simpler cheaper, but would I appreciably be cheating the samples out of control and fidelity?
  9. I was going to ask about a couple of U110 patches. It's been laying dormant in my rack for well over a decade. But go figure, I plugged it in after lunch, and I think I may be able to get it to function long enough to sample a few patches. If you ever do have an opportunity as a low priority, I would like to request S Bass 3 (MT-32: sold it in the 90s). I'm not sure what format to ask for, but I think sfz might be a safe bet. Thanks for all of the suggestions. It's exciting to look at the rack and raise the dead.
  10. Thanks Msmcleod. The product description sounds just like what I was looking for on the still functioning Roland, Yamaha, and Korg devices in my rack. I'm assuming that Roland RS-PCM samples cannot be accessed without a corresponding working device.
  11. Over the years, I've lost more the a few favorite hardware instrument patches as synth lifecycles reached failure mode. On occasion I've seen reference to sample emulation, but I'm unfamiliar with any reasonably priced products or the process to port these samples into. Theo only exception were VST plugins that I found for my dead EMU synths. I still have a couple of rack synths that haven't quite bitten the dust yet. Could someone suggest a way forward to extend patch life? Thanks
  12. Variorum, I missed this when it was first posted. Thanks for the midi plugins, especially the group transpose. I'm not sure how you do this, but it's a slick solution to a request that I had made.
  13. The limitations of my own challenge were clearly beyond me. Msmcleod's list (Spacebar, W, R, Ctrl Z, Ctrl S) is actually more accurate for my own Gotta haves. Being a shortcut junkie, these are as involuntary as breathing. Two others I forgot were transport controls of Ctrl Pgup and Pgdn (prev/next measure) Ctrl-shift Pgup and Pgdn (prev/next marker) I’d never used Alt-z before yesterday, but I can see where I’d also make use of that as well. Are there other shortcuts that would make your essential shortlist (assuming 5 is too few)?
  14. This is just a hypothetical, but I’m curious to know which shortcuts are really being used in the community. Let’s say you have a limited time to create a major project from Midi through Mastering, but you can only use 5 shortcuts (preset or custom) and no more. What do you choose? And what are the next shortcuts that regrettably wouldn’t make the cut? I’ll start from a hobbyist perspective: Gotta Haves: Expand/collapse MultiDock (D) Maximize/restore MultiDock (SHIFT+D) Show/hide Inspector (I) Show/hide Browser (B) File > Save (CTRL+S) On the Bubble: Piano Roll view (ALT+3) Tough one to lose to manual mouseclick Show Tools HUD (T) I’d just have to keep the toolbar visible in the control bar Patch Browser (;) Just learned about this one on the forum
  15. Thanks for the confirmation, Folks. It's a minor inconvenience at most. Just wanted to make sure it wasn't fixable.
×
×
  • Create New...