OutrageProductions

I look at it like flight training; you must learn how to take off, fly level, and land using VFR rules, then graduate to IFR experience, and then you are free, after growing a pair, to do the barrel roll and split-ess to your hearts desire. But you never lose sight of the horizon, the floor, or the ceiling, else you be in trouble.

Login to your NI account and find out what your possible upgrade path is. There has been much debate on their forum as to the K13u to K14s pathway. It may be possible. Generally they only upgrade to equivalent or greater. This question is best answered there. As to the Lunaris license, the free bundle addition is not resellable, but your original may be... on the open market.

Not really sure that you have a 'new' system, as the 'intelLok(R) device drivers' are from an AVID PT install requirement from 10/11, the last of the 32bit systems, mostly for AIR plugins aka BF76 on WIN7. That error is a flag on WIN 10. You may have to clean out some old 32bit plugs first.

And still no negative pre-roll measures or on-board sampler track... no surprise.

The synth that you are using (TTS-1) is one instance of a single DXi instrument, hence when you freeze it, any & all tracks running through it will freeze also.

Definitely send a CDR to the bakers as this is specific to your system. I have tried every possible way to export a mix as MP3 (which is not my common workflow, I always export as WAV and convert post facto) and cannot recreate your issue.

@jkoseattle: IIRC you are using solo strings, each in an instance of Kontakt, right? What I do is convert each MIDI track and all data therein to MIDI channel 1 in the event viewer using any of the available filters & tools, delete any CC data that I don't want/need, set the MIDI input to channel 1 of my specified keyboard controller, and then proceed. [NOTE that this will only work if each instance of Kontakt is on ch1, and does not work well if Kontakt is running as a 'multi'.] When you focus a track (Echo Input), the kbd [sending on ch1 only] will drive that track and only that track allowing all controllers to be written/ edited in that track. Your keyboard probably has a volume [CC7] pedal input, pitch wheel [NRPN], and Mod wheel [CC1] as defaults. Some keyboards allow one to change the CC# of the pedal and/or the mod wheel to operate on CC11 expression in MIDI mode. That may be worth investigating. On 'pre-built' MIDI files, it is generally useful to set the volume CC7 and expression CC11 to a continuous static level of approximately 101 and then use any of the myriad ways to modify them in automation lanes, either in the PRV, or in track automation lanes, post facto. I can swap my keyboard controller between several MIDI templates on-the-fly so that my pitch & mod wheels can be changed to things like CC2, 3, 7, 11, 14, 32, etc. I also use one of these for more complete control of CC's in most of my orchestration projects.

@Grem; there do seem to be some 2 port & 4 port I/O devices still available, but for a suite of HW synths (more than two) it seems that selection is extremely limited. My old (20 years +) Midisport had 8/8 I/O ports for a total of 128 MIDI channels... only ever had (back in the Paleoscene Era, pre USB) 3 keyboards & 1 MPC-60, which are now fossilized.

After some investigation, it would seem that MIDI I/O's of multi-port nature are dinosaurs, so even though I rarely use it anymore, I'm not going to pull my midiman midisport 8x8 anytime soon. I wonder, if one had a bunch of HW devices to connect, would it be possible to use several 5pin DIN devices as noted previously on a POWERED USB hub? Curious...

If it only happens on THIS particular project (as stated) then I might suggest that you start the troubleshooting process by MUTING all tracks but one, export, and compare. Add another track by unmuting an additional, rinse & repeat. At some point you may find the combination of tracks that is causing the issue, and can then investigate further. A less helpful way to pinpoint is to disable ALL EFX and print the mix in case it may be an FX plugin misbehaving, but then you have to go back and use a process of elimination.

If you feel adventurous John, you might try THIS and report on it as well. Personally, I haven't used anything GM for years.

In this mockup the Trumpet is from Blue Street Brass (Indiginus), really nice muted growl, Bone & Tenor sax from NI Session Horns Pro.

Latency can also affect the amount of time between when you send a MIDI note, the VST receives it, and the VI plays the note back out as audible. Though up to 15 - 20 milliseconds can be functional for some folks. Most prefer less than 10ms RT.

If you currently have TTS1, the update to latest/last CbB should NOT affect it. If you update via the in-app toast it is about ~52Mb, if you use the Cakewalk Product Center, it will DL the entire installer (~500Mb). But... it might be a good time to re-visit those old projects and sub in another piano instrument to make them bomb-proof for a little longer. Or at least label the tracks and notes so that changes can be made down the road.

Many others on this forum have already reported success with no issues, so...

@profwacko: if you go to this post & DL the Cakewalk Product Center, it will allow you to bring down the entire installer to an online machine and then move it to another one. The in-app toast only installs the update.

@freddy j, @whoisp; not to excessively self-promote, but you might also like my Django Reclaimed track, which is just some riffing on a Django Reinhardt theme from early last century if you're into jazz figures.

That is just a screen captured visualization from WinMediaPlayer, then I slam it into PinnaclePro to edit. Basically one real time pass and about twice that for edit, titles, fades, & render out. Simple & fast.

I find that interesting. Good to know. I've done work on three movies in the last 10 months and all of their edits and director reference cuts are sent to me at 29.97fps. I just checked with my music director buddy, and he has rarely heard of video at 23.976fps being used in the production/edit process outside of the digital distribution chain. He said they do reduce the frame rate when sent to some theatres or streaming. Maybe your sources are later in the chain than I am, or it could just be your MD/Edit house preference. But that makes sense in saving a little bandwidth, cuz average hoomans generally can't really discern the difference of anything higher than 24fps film. Maybe my sources just know that I'm still stuck in NTSC from 1999. 😁

Tis strange indeed. The graphics Req's for K7 are: Graphics hardware support for OpenGL 2.1 or higher and Direct 3D 11.1 (Feature Level 11_0) or higher. Maybe check your system specs just to be sure. (I know that both of my graphics cards are near EOL support. [big sigh...])

Obviously they never experienced the constant ProTools pay-to-play upgrades in the 90's that every studio had to endure to stay competitive. Poor pookie...

ProjectSam releases an instrument per month. TFO1 is complete (12 instruments IIRC), TFO2 is on about #5 or #6 so far. You may have to enable 'legacy' instruments in NA2 for TFO1 to show up. I haven't switched to NA2 yet, still on NA1 for the rest of the month. I do know that this months TFO2 (percussion) is only available using NA2. I'm in the middle of a large film score and just don't need any changes or headaches until it's wrapped. Maybe someone else can chime in & help. @msmcleod maybe? Or @PavlovsCat? EDIT: if you're interested in organic orchestration you could also get the entire BBC Symphonic Orchestra Discover HERE, which is also free and has a relatively small footprint. You can DL the Spitfire Audio App to get it and all of the free LABS line too. Have your CS solo strings started to behave correctly?

Investigate if you can disable openGL in your computer.

You would have to look deep in the manual for the keyboard. I had a Yamaha at one time and it would always play the on-board sounds when I was trying to drive other instruments via MIDI until I turned local off.

Most Yamaha keyboards have a setting for 'local on/off' which basically disconnects the built in sound engine.