Jump to content

Glenn Stanton

Members
  • Posts

    2,178
  • Joined

  • Last visited

Posts posted by Glenn Stanton

  1. in solo & mono, you might find it "thinner", but in a full mix where you've already done the HP filtering, you're less likely to notice. and if you listen with a single mono speaker with the track in stereo, you'll be able to assess if there is an issue. 

    other tricks include the Waves or Boz widener plugins, and of course using the Haas effect with a slight delay and judicious panning - as with the phase plugin, check in mono with the stereo feed to determine any ill effect.

    • Like 2
  2. according to @Noel Borthwick Sonar has been in production 2 months? i've been using it for about 45 days and it's pretty solid, i had to pull up some old plugins which i knew might crash it (and not to disappoint they did) but other than trying to deliberating crash it, i only had one incident where it crashed (an update from Karzog) which when i updated the plugin went back to working.

    • Like 1
  3. you probably should do a lookup on your OS for optimisation so your system isn't running stuff that can cause the cracks and pops ?

    sometimes it's as simple as turning off the network while you're doing stuff - making sure your apps are all off, no running discord server etc. ? gaming, etc can all make audio work tougher than it needs to be.

    the MME is not a good thing  to run esp as the UMC204HD is a good interface (i'm running the UMC202HD at the moment on my laptop) via WASAPI shared (most times) or ASIO when i need to record audio. 

  4. many times, having some details can more quickly result in getting things running.

    for example, is your "epiano" using audio or MIDI when connecting to the "interface"? my guess would be you have the stereo audio output on your epiano connected to the interface, and the interface is connected via a USB cable to CW. you note that CW recognises the interface - good sign. are you using WASAPI shared or something else for the interface? is it selected in preferences? is it selected in the audio track you are recording to? have you "armed" the track to record?

  5. i am on their blogs almost daily via the newsletter. even though it's a PT and UK focus on a lot of stuff, i find a lot of useful information on products, techniques, etc is there and sometimes a new plugin to explore as well.

    • Thanks 1
  6. 1 hour ago, Craig Anderton said:

    To be fair, The MIDI Association is an all-volunteer group with representatives from large and small companies. No company can steamroller through a proposal because the power to make changes is distributed uniformly among the members. There is no inter-company "competition" because like MIDI 1.0, the expectation is that the most universal/compatible standard possible will have the greatest benefits for all concerned. There aren't any bureaucrats in the sense of being paper-shufflers. Company representatives are almost all software/hardware engineers, or product designers. Their responsibility is to make sure that any changes or additions to the standard are rock solid. That takes a concerted group effort. 

     

    ...

     

    FWIW I was President of the MIDI Association (also a volunteer position) for two years while covid was in full swing, so I'm well aware of all the frustration that companies had as they tried to move the spec forward despite restrictions on being able to meet, trade show cancellations, and economic uncertainty. The process has been back on track for a while, but there was a lot of ground that had to be made up first. I'm still kept up to date on the latest additions to the spec and work of the Technical Standards Board, and there is a lot going on behind the scenes. However, traditionally the MIDI Association doesn't talk about what's coming up until it's actually working. 

    thanks Craig, as an enterprise architect for many years - when you factor in all the variables and if you're trying to make it real, then the bureaucracy seems to build on itself however the best of intentions and dedications. just the nature of organizing people, institutions, external forces, and then the communication complexities, in way all can understand and [co]operate. i've been eagerly following the work since early 2020. 

  7. quick review ? 

    you need to calibrate your system. input and output levels to a steady source, then match levels in the applications (DAW, media players etc) and your monitoring - speakers, headpones, etc and using stereo and mono sources etc. once you get the hang of it and you do it periodically, it's quick and you can avoid a lot of surprises. then take the mp3 to you car etc can set those levels so you know what level you get with your phone and car audio - with the car i like a flat setting and a "pop" or "classical" setting to compare esp for too much bass.

  8. On 7/25/2024 at 6:05 PM, OutrageProductions said:

    ... because of a piece of software, you're sadly delusional.

    until they get the bar low enough with most people loving AI "created" content and AI "mastering" it... judgement day is coming! ? (actual some folks having been claiming this already happened due to the 1980's)...

  9. 1 hour ago, MIDInco said:

    Regarding the development environment and business plans, we have been significantly affected by ROLAND and Gibson's business decisions, which put us in our current situation. Why, then, can we say that we are not in a position to speak about management and business? If development is stopped due to similar failures twice, it is inevitable that paying users will become anxious about such a concept.

    valid concern giving other companies dealing with users. i think for Bandlab, it's somewhat different as they're part of a well-funded media product holding company. but like anything in the future, nothing is guaranteed. Studio One could go under, Apple Logic could eventually become a proper DAW, the programmer of Reaper could decide to take the riches and retire.... ?

    so, much like anything else, only you can decide if your wallet and risk tolerance is balanced in a way that says "yes, Sonar makes sense for me", or simply acquire another product which does provide the balance.

    • Like 1
  10. note: you can use articulation maps for creating the patterns in instruments which support keyswitches (or expression maps - you can import those from another DAW).  a screenshot of articulation map (paid product) from Art Conductor for Cakewalk

    image.thumb.png.72adcd2cbac3e2e464cf199a1a2b6a5c.png

    • Thanks 1
  11. 3 hours ago, MIDInco said:

    I am quite anxious about these issues.

    maybe drink less coffee? maybe spend more time using the DAW and creating content and skip worrying about how much social media a product is using (e.g. how many times have you visited the "off-topics" area? vs tools & techniques?)

    one thing - if you are wealthy and can afford to suppliment the bandlab developer salaries, i'll bet it would be win-win -- you could become less anxious and they would have more money for cars, hot chicks, and better guitars.

    • Like 1
    • Haha 2
  12. the send would be on the track or on the shared instrument buss. having a send on a reverb which then returns to the same buss could invoke a "feedback" restriction on the routing ? 

    couple of other points - on the shared buss/aux reverbs - mix = 100% wet, no dry. on a track, reverb (or other FX) use the mix control to blend as desired - typically 100% dry and some % of wet . e.g i may have my Breverb set to 0db dry and -9db wet on a horn track where i want the reverb to ring out slight as the note ends.

    • Thanks 1
  13. some basic thoughts:

    1) if an effect (FX) is used only for that instrument - most times you can just put it on that track (either in the FX bin or using the Pro Channel) as it's not being "shared".

    2) if there are several instruments of a similar kind, those would benefit from being routed to an aux track and/or a buss. e.g. i have several acoustic guitars, or several percussion instruments - like a drum kit - those may benefit by routing those to an aux track or buss and then applying reverb there, or have a dedicated shared reverb buss you can send multiple instruments to.

    3) route the instrument tracks and aux track and busses to the master buss. 

    so:

    track + eq + reverb ---> master buss & send to "room" reverb
    track + eq + reverb ---> master buss & send to "room" reverb
    track + eq + ...FX...   ---> master buss & send to "room" reverb

    room reverb ---> master buss

    master buss ---> IO output

    you can also have drums with their own reverb as a set as well as say the snare having it's own (common)

    track + eq + snare reverb ---> drum buss & send to "room" reverb & send to "drum reverb"
    track + eq ---> drum buss & send to "room" reverb & send to "drum reverb"
    track + eq ---> drum buss & send to "room" reverb & send to "drum reverb"

    attached is a block diagram of my template which may be useful for you to study as well.

    DAW template - 02 - mix.svg

     

    • Like 1
  14. you can rem out the cakewalk core and common files, and  the executable path and reinstall, then copy over the INI etc files, reload the settings. copy back presets etc. you can do a system point, and restore if you find the install did wipe out some of your specifics.

  15. SI-Drums is pretty limited compared to say Addictive Drums and EZ Drummer, and of course for fuller control you'd probably look into Superior Drummer etc). so your're not going to have much options around placement compared to other VI drums with more outputs and flexibility in setting the triggers, positions, things like overhead, room, buss positions and options for distinct outputs.

    given the limits, and sample/triggering, you probably just need to work out what are the things you need for a given project and set your MIDI up to use it within the options SI-Drums provides. not sure if there are detailed maps for each of the provided kits or not.

  16. your configuration files (assuming  the corruption didn't overwrite those) and presets etc (assuming you didn't overwrite stock presets, templates, etc) should remain intact with a new install. i routinely reinstall after a significant MS update and sometimes after an Edge update.

  17. the folder extension of .vst3 was resolved in CbB a few months back. the challenge is some developers of plugins don't properly handle the directory with a DLL extension name correctly in their own space. once the vendor properly codes their plugin, it will work. i've had several prominent vendors not handle it correctly when they first rolled out their plugins using the new Steinberg VST3 spec, but most have resolved the issue via updates.

×
×
  • Create New...