OutrageProductions

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.

2 hours ago, T Boog said:

I only have CbB. I havent done the new update yet. When I do, will I lose access to the TTS-1? (I have current projects that use the "piano 1" in the TTS-1). Thanks!

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.

6 minutes ago, profwacko said:

Now, to see if it works using the offline activation process.

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.

3 minutes ago, Bajan Blue said:

liked the video - what did you do that in?

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.

5 hours ago, jono grant said:

No, most productions run video at 23.97 fps now. Not a typo. I'm a film/TV composer. It's been the norm for more than a decade. It started with animation but now everything I get sent is at 23.97.

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. 😁

5 hours ago, Misha said:

I believe openGL is one of pre-requisites of Kontakt 7.  Strange that this only happening in Cakewalk.  

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...])

19 minutes ago, Helios.G said:

Whut?

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. 

35 minutes ago, Frank DeFede said:

My keyboard is a Yamaha YPG-635.  I don't see any place to turn off "Local on/off.  I will check deeper into it.

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.

Actually, the instrument library is installed via Native Access. Starting Kontakt in SAL mode allows it to find and read the library in the database. You should be able to just start Kontakt and scan the DBF and then load one of the instruments (violin for example) and test it for all the notes, articulations, etc. That will confirm if the instrument is completely & correctly installed.

If not correct, then reinstall the library using NA. Ditto with the other strings. Then we can move on.

Open a new blank project in CbB, load one instance of Kontakt with just one instrument. If it plays and you can hear it, record some midi notes into a track & see if it will play back and you can hear it.

@craigb proving my point exactly!

1 hour ago, Steve Schultz said:

Thank you for your response.  I am using an instance of Kontakt for each instrument.  I don't have anu other Kontakt instruments.  It hasn't happened with other VST's other than Kontakt.  I am using individual channel/tracks for each instrument.  Thanks again.

OK. Progress (sort of). 

Now; if you don't have any other Kontakt instruments, may I suggest that you obtain some freebies like maybe THIS, so that you can try to discern if it is actually an instrument issue or a Kontakt issue or a CbB issue (which, from your answer, is highly unlikely at this point). If you are familiar with the MIDI & Audio input routing procedures in CbB (which I'm guessing work for other VSTi's) then it is probably a Kontakt issue.

If The Free Orchestra fails, then you need to submit the issue to the NI/Kontakt forum HERE.

IMHO Kontakt 7.x has still some serious issues in installation & operation. Kontakt 6 is solid as a rock.

EDIT: When ever you add a library to Kontakt, you MUST start Kontakt as Stand Alone (SAL) and rebuild/scan the library database before first use as a plugin in your DAW! Please test each instrument in SAL mode for correct articulation/operation first.

EDIT2: Please either quote fully or partially the post that you are responding to, or tag by UserName [type @outrageproductions for example] the person that you are responding to, so that we get notification that you're commenting. Otherwise, I just happened to see your response by browsing the incoming list. Makes thing go faster.

45 minutes ago, Bapu said:

Can I run Cakewalks with a Sound Blaster using ASIO4ALL?

Oh great Bapu OZ (behind the curtain)... I'm pretty sure that particular question has been asked and answered ad nauseum. LOOK IT UP! LOL!
(Altho I'll be the first to admit that the "search" function of this forum leaves MUCH to be desired in terms of complex functionality!!!)

17 minutes ago, jono grant said:

Not sure where I'm locked to smpte. The markers aren't locked to smpte. I'm working with a film that is at 23.97 fps.

Just checking: Drop frame video (color, the most common) is at 29.97fps. Actual film usually runs at 24fps (+/- calibration error). You may have a typo there.

6 minutes ago, Jonathan Sasor said:

Please note that the installer link has been updated to build 29.02.0.093. This new build includes an improved experience for offline activation as well as some additional improvements for analytics. Please grab the latest. Thanks!

Is this still the EA or now considered the Release version?

14 minutes ago, craigb said:

Join the target forum and pretend to fit in before introducing what you are really selling.

Your extreme cynicism is duly noted and ignored. Serious inquiries & interaction only.😁

Is it my imagination, or are we having a steady stream of new folks joining in this forum?

Are we really that interesting to watch?🤔

On 2/18/2024 at 5:14 PM, sjoens said:

When dragging clips to desktop, etc., the names change to reflect the project name followed by sequential numbering system.

Instead I would like drag-exported clips to retain their clip name.

This helps identify what the clips are once they leave the project without having to rename them, which can be tedious when migrating several clips.

I don't know what your issue is; when I drag a named Audio clip to either the App Browser OR to the desktop/drive it retains the exact name of the clip from in the project with the addition of an iteration number; ex: "filename(4).wav" depending on how many times that I've dragged it out of the project to a different location.

ends up in the app browser as this:

and on the desktop as this:

2 hours ago, PavlovsCat said:

I'm now going to take another look at the Autograph Grand.

It also reminded me a lot of the C6 that was at Caribou Ranch... which, due to the altitude, was never evenly tempered.😆

Come to think of it, I'd have to say that my favorite piano of all was the Bosendorfer Imperial that we had at studio A at Chicago Recording Company. It was the personal piano of the studio owner... wonder where that is now??

Worst piano ever was the 9' Steinway that got pushed off (and I actually mean dropped off) the back of the truck one hour before a Ramsey Lewis solo concert at the Chicago Hilton. Seems there was a small issue with the local cartage & stage union that evening. LOL!

1 hour ago, sjoens said:

Not funny is having to reenter the menu for each setting you want changed.

Yeah, but, as has been discussed ad nauseum, that is pretty much standard Windows context menu API operation, regardless of the application. 

1. Not a good idea to put your email addy out in the open.

2. Look into a way to alter the velocity curve of either your controller output or the curve/sensitivity of the Virtual Instrument. 

3. If it is a 'real' acoustic piano, work with mic gain & placement first, followed by a hardware limiter (not compressor) between the mic preamp & the analog input to your recorder chain.