jackson white

First time I've ever seen an SM7B on sale...

@cclarry Thanks for the heads up on this special, will be checking to see if Vintage Horns shows up. It's the only horn section I've been able to find with anything like a "vintage vibe". And... it works with Kontakt Player! ? Been mangling a Korg M1 patch and while an OK placeholder, just not suitable for a final.

as a bit of idle speculation... perhaps Fender + Presonus see some potential to promote low latency tracking for guitar players? IIRC, Presonus/S1 claimed some of the lowest numbers out there with the newer Thunderbolt i/fs.

Or full kontakt. (Thx to all who already do this.)

Holding out for the box set.

Maybe they'll offer it for free.

https://www.cakewalk.com/Documentation?product=SONAR&language=3&help=EditingMIDI.10.html "Filter (Professional and Platinum only). The track filter determines which tracks are listed in the Track pane, while track selection determines which tracks show data in the edit view. Add individual tracks to the filter, then click the Filter button to list only those tracks. For details, see Filter mode (Professional and Platinum only)." ... There's a lot of really useful information in the documentation. Might be worth getting familiar with it.

fwiw, I've noticed this recently as well. Specifically with SGear and a PA Console as well as the Korg M1 on the very few occasions it's seen use. Not sure about Bank/Patch selection, but in my case, the settings have been tweaked and saved as a custom preset, and at times the project has loaded with some other preset, most def not the one that was expected. It might be triggered by some combination of FX disable or Track Archive/Freeze, haven't had a chance to do any meaningful troubleshooting yet... Or some glitch with VST3 presets? (still complaining about PA plugins in Cakewalk.)

I rarely use samples (other than drums) and had ignored Spitfire Audio as yet another high end strings for film but find the LABS to be an interesting collection of somewhat unique samples suitable for ear candy in arrangements. Arguably more useful than yet another amp sim or compressor clone. But beware, they are high quality marketing hooks which could contribute to you missing something from your wallet... I've bought a couple products since.

...

"Is it confusing, yes" ... Used the Theme Editor to clear that one up. ... My original response to the OP was simply "Tracking?" but Noel's post below is much better. Meant to note the use of custom color coded buttons to highlight "audio flow", which includes both PDC and FX enable/disable. I end up toggling these for live tracking on projects as they get "heavier" with assorted FX/amp sims.

@LAGinz it's been working better, but no definitive statement yet. Drew's been posting a bit more information here... https://gearspace.com/board/product-alerts-older-than-2-months/1349865-bfd3-4-update-inmusic-migration-20.html

Latency? As in how far from the speakers? If so... The speed of sound is 343 meters per second. Latency = distance / speed of sound Guitar players can usually live with a few ms (2-5ms), so in round numbers; 1m ~ 3ms 2m ~ 6ms = something similar to performing on larger stages. Apparently there is a claim that humans can perceive 0.5ms https://news.ycombinator.com/item?id=28069695 Bass players...? ... Obsessive tone freaks (i.e. guitar players) might be more concerned with the capacitance of longer instrument cables. I've heard discussions favoring 2m or less.

haven't seen it but an interesting article on the sound design for it. https://www.nytimes.com/2021/10/22/movies/hans-zimmer-dune.html?campaign_id=9&emc=edit_nn_20211025&instance_id=43710&nl=the-morning&regi_id=98110677&segment_id=72580&te=1&user_id=0561979f4c950adb778ad5da65811b04 my fave quote from the article; "bagpipe PTSD". seems like it would be a fit for Spitfire Audio.

Rimclick/Side Stick/Cross Stick are all gonna sound pretty much the same for practical purposes. Most drummers would acknowledge a difference between these and striking -just- the rim with a stick as the snare head contributes to the overall sound. Snares can be fairly complex, depending on where you strike it (center to edge), how hard and which end of the stick you use. Mallets, hot rods, brushes, hands, etc. all expand the palette.

The 3 fundamental articulations (hits) for cymbals are; Edge (of the cymbal) Bow (middle) Bell (center, raised area) Not every cymbal supports every articulation. HHs can have a lot more depending on how open it is. Any drum can be struck with; The tip (small end) The shank (middle of the stick) Snare Rim = hitting the snare rim with a stick Snare Sidestick = usually means "cross stick" which anchors one end (usually the tip) on the snare head and hitting the rim with the other Not a big AD2 user, but IIRC, the flexi slots are for specific articulations unique to that drum piece. (i.e brush strokes)

My suggestion for the Plugin Alliance survey... fwiw, still using BFD3 here but can't in good conscience recommend it until they sort out the current issues.

The main issue for me. You can explore a trail of user frustration here... https://forum.bfddrums.com/t/preempt-reauthorization-so-as-to-avoid-c-f-s/1162 ... Of course completely depends on what you're looking for. The strength of BFD has been quality acoustic samples/features capable of hanging with real drums in a recording. Been using BFD since v1.5, originally for their cymbals and since then made great use of kits with multiple ambient/alternate mic options and features like proper swells/dynamics. It is deep and takes more than a bit of effort to sort out, but once you get it working, is hard to beat. They also had 3rd party partners which nicely extended the available options. Given the current state of BFD with InMusic, a group of us have started to explore SD3. The key factor (for us) is the ability to craft unique sounds vs presets/grooves. Most of the standard options (at the time) were found to be over-processed/canned and limited wrt to dynamics/range/variety of sounds (geez, how many versions of the Bonham kit are there?). SD3 seems to be a major step up up from SD2 (their HH articulations could be a nice improvement) and they list four kits which note raw samples. However a switch would entail a non-trivial four figure investment with fewer options. Some of the original key players from FXpansion are on board and a v4.0 has been mentioned but InMusic has yet to prove they can add value. Wishing them all the best, but there is plenty that could be improved and the jury is still out. just my experience...

same for me, but specifically it's the mandatory online authorization implementation which they have been struggling with since the relaunch in April. fwiw, it's finally quit deauthorizing everything I own on my system, but they have yet to release a version with a definitive (and working) policy that doesn't severely compromise the user experience. These are good prices, but imho their development would have been much better spent on enhancing/improving the core product.

@jwnicholson78 you could start with this...

Classic. Centerfield bleachers used to be pretty much whatever goes, you must have had good seats.

What, no Stroh's? (And thus the reason they made Slapshot.)

Hmmm, nobody has ever listed that fine venue in their classic hockey arena reverb pack. Seems like it would have been a natural for Echoes.

Agreed on all points above and piling on with the unwanted "ability" to "micro-select" a range in the timeline when merely intending to set the Now time. Just a casual observation, have not spent any time on detailed analysis, but does not appear that "range selection" is context aware of the timeline scale, It's less of an issue once the coffee starts to wear off.

@George D fwiw, I've been working through what sounds like a similar problem. I've always built my own PCs and am very comfortable with all aspects of fine tuning for audio performance. My current cfg had been running flawlessly for years but starting "acting up" around Mar 2021. This particular project was an older one that a client wanted to revisit and used to run just fine with absolutely no problems. The symptom was a serious degradation/smearing of sound quality on playback, like running the audio through a meat grinder (or putting your thumb on the reel for a tape machine). It would only happen for 10-30 secs and then somehow "recover'. Not sure how this compares to your "clicks and pops" but the performance monitor would go crazy when this happened, super erratic, cores jumping/spiking all over the place. This would also happen when opening a VST or the browser (i.e. to open a user manual, not to check on sports scores...) something that -never- used to happen. The project isn't super large, only a drum VST and a few amp sims in addition to std audio tracks with FX. I don't generally freeze these as I've never had to before SO... not thinking the project/VSTs itself is the problem. Additionally, the ability to run at low latency has been significantly compromised. Used to track just fine on the very same project down to 64 samples. Then only way I could get reasonable playback now was to raise it to 512, which is pretty useless for tracking. The major areas of focus were; 1. WIN 10 updates - Running WIN 10 Pro with updates disabled except for security updates. Always an issue, but I've got a good checklist and always managed to restore the changed settings quickly and easily when they happened, which was not often. Decided to update to the latest version (last update was over a year ago) to solve the problem. = Didn't help. 2. VST updates ? Possibly some update to an existing VST? - Couldn't pin it down on any in the project. They're all by reputable proven devs and run fine in other projects (and DAWs) with no issues reported for any of them. = no obvious suspects 3. Other SW updates (like other applications phoning home) - rechecked / reinstalled the native A/I drivers (they were always the latest update, but...) - I've added some new VSTs/suppliers with various means of authorization. Tried freezing those and disabling any service that looked like it might be trying to do something. - tried running the project completely off-line (Internet disconnected, actually boot cfg is off-line, have to manually go online) = no improvement 4. Checked my system services again. Ran Latency Mon and for the first time on this system, it would show some issue when running the project but w/o much of a clue as to a specific cause. The highest DPC counts were for the Kernel Mode Driver Framework Runtime. The second highest were for LatMon iteself... Multiple sessions were rather uneven and hard to pin down. FYI, no BT, WiFi, etc, active, only Window Defender running for when online, never been a problem in the past. ? Not sure where to go with this, still looking into it with no idea what changed, so the challenge is to hunt down what might have made it worse. 5. CxB changes/updates. - CxB has never been the problem (despite the number of outraged posters in this forum ?), but there have been a -lot- of changes and had me considering the possibility of some newer potential stability issues. Not that I have any insight into the development, but it is a very feature rich (=complex) program. NB This project has since crashed several times and flagged an issue with Cakewalk core. Doesn't mean it wasn't caused by some VST issue, but despite the best efforts of the Support team (they've been super responsive), no clear cause has been noted. > Worked through a matrix of Record/Playback IO buffer sizes, A/I buffer sizes and was able to confirm a few settings which helped, but mostly raising the A/I buffer. Changing the Record/Playback IO buffer sizes generally made it worse. = All changes were correlated with Performance Monitor specs during playback but they generally behaved as expected... > Tried various settings in the Initialization file. = Back to the original settings as none of the changes made much sense and generally only made things worse. ... In the course of working through this, it's started to behave a bit better, which makes it sound like a moving target, or maybe it just takes a few reboots for everything to settle down? I still have a problem project with repeatable symptoms at a specific spot in the playback, trying different states/cfgs to see what might expose the culprit. And also noting the issues are only with older projects so far (like 3-5 years old) being opened in this years version of CxB. FWIW, all of my newer projects are running fine atm, so I'm considering the possibility of some project specific corruption or as yet undiscovered backwards compatibility issue? Don't know that this does you any good but just hearing about something similar might help. I don't expect to find any answers here as I'm assuming it's something specific to my system, but stuff like this comes with the territory (infinite cfg possibilities + ongoing dev) I'll come back if something useful gets figured out.