Will.

Then you have a serious problem on your system. No one on this forum ever complained about them. Maybe you should contact their support team. Fabfilter never give problems. Try to remove the VST 2 DLL file if you have it installed. If you would like to keep it . . . get the JBridge Software to convert it to 64bit.

Been working fine here for 2 years. Make sure it's in the correct path folder and that your 3.5dotNet is updated.

Why doesn't the "flatbed menu" work on plugin preset menus too?

Can we have the "Bounce to Track" to commit the midi file to "Audio" as a shortcut on the right click menu on the clip too.

Exactly.

Don't know why you're repeating what I've said.

100% Agree with you. But there's also room for software intelligence.

Bro, I'm with you on this one too. 😂

Just asking: Shouldn't it be that way? Having the I/O to read as "Mono/Stereo-in" | or | "Mono/Stereo-out?" What defines the strips I/O as "Mono or Stereo?" Maybe I'm just confusing myself with this. 😂

I Understand. Although it would make more sense for the input to follow the interleave as well. It's not a big deal - just a naming/visual thing. Just thought some might find it confusing to read.

Hi Noel. Thanks for responding. No, I'm sending to a normal Aux track. I'm just asking, shouldn't the input display follow the interleave as well. Example: "M: Reverb" to indicate that it's in fact in Mono on the input too.

Always appreciate new features and changes. Awesome work guys. Been at it for 4hours with no issues to this update. Just a Question: When changing the interleave to MONO on a send aux - shouldn't the Input Names Reads/Change to Mono too? Right now it say's L+R Filter instead of following the interleave on the channel and reading as MONO FILTER (M: Filter) when the interleave on the "FX Aux channel" has been changed.

It can be done in Cakewalk already. It's just displayed differently.

Its just a time ruler format change and not as what/how you describe in your original post. FWIW: Cakewalk has had this for years.

You're referring to "TIMECODE-STAMPS."

😂 I'm just gona laugh at that. 😂 You're sending back information i'm giving you in answer here. LAST TIME: Zero is One | and | One is Zero and that's why the count starts at 1. So i'm gonna say this "EXACTLY" a 24hr clock only starts at 01:00 Here's the thing. We've all worked an 8hrs shift before right? But out of that 8hrs you get 1hrs lunch so basically you're working only 7hrs right? So from the start you go on lunch until the end of your lunch - thats "1" hour. not 0 hrs right? Now to come back to you "Wikipedia" research. There's 24hrs in a day correct! But the day ends on iets 23hr with the minutes and seconds making up for it. Now heres the question: what happens to that 24th hr? Answer: That's that "LUNCH BREAK" in your 8hr shift. So now on the world clock that count starts at 01:00 again. So between 1am and 2am thats One Measure. Your 1 metronome measure counts (Or 4 beats count.) So on the clock 00:00 to 01:00 will be your 24th Measure and whole note count. ("96 Beats on a 1/4 Note.)

As I've said before! Thats because "0" is 1 and "1" is "0" a 24hr clock ends at 00:00 and starts at 1:00. Where the last count of 12 is at 00:59 "AKA" the start of "1." The fact that you make an example of an Olympic clock is disappointing, because although it DISPLAY "00:00:00" the count starts at "1" That is why "0" represents the number "10" on the abacus. Because the count just starts back at 1 again - which then gives you "11." and every time as you go higher 21; 31 etc. I can go on all day with this to why it will never work. Unless you want to read the music score wrong.

Yes. But it's time based - as in reality, "real-life." Meaning 0 is 1 | and | 1 is 0 - so this tells you that between the "0" and 1 is a negative count. It's the law of time. We don't start to count at "0" we start by 1. Your house clock starts at 1:00 not at 12:00 because 12 ends at the beginning of 1:00 O'Clock (exactly like your metronome counts.) So you see why "0" can't be added to the score as this will add a negative clock count? That is why they teach you this in music schools (Not that i've been to one.) So all this comes down to a count-in at the end of the day. It is what you're basically asking, but not in so many words. FWIW: The metronome count-in does not only applies for recording it's playback. That's why your loop points keep your time and song length in order. And like I said: I totally understand what your asking. But do you see the complications? Yes, we all want a way to have that silent free count to make up for starting times for rendering purposes, but this why it cant be done. That's why the only way is to draw it in yourself once production is finished. Isn't there an easier way with the arranger?

We just drag out/in silent spaces and add in fades to prevent clipping.

What you want to do then - is to change your metronome count-in to 1 measure or 4 - beats in the drop down menu seen below. This will give you a pause of 1 measure (Bar) count before the actual recording starts. It is a global tradition in music and video for the timeline to start at 1. This has been the law since the beginning of music. Reason for this is: Every count starts at 1 and return back to 1 count. Whether that's in triplets or dotted - and its just mathematical correct for 4 measures (Bars) to end at the 4th measure before you get the 5th measure (Bar.) This rule cant be changed as it agrees with "time" in general. Meaning: The 1 you see in the timeline (irrespective of what clock method or counts you use) those beats in between a measure - counts down the seconds. Again: Time in general. Thats why a 1/2 note is 1 second and a whole note count/measure/bar is 2 seconds long. It's the principle and law of time itself to have it immediately start at 1. I totally get what you're saying and asking - I get it and understand it. That's why a count-down | or | count-in, are so important in music applications on recording. Who knows maybe it is possible to make a visual aspect of it - like a blank count-in area on the time ruler. I wouldn't know. Cheers ✌

All good here. ☺

@Jim Fogle It sounds robotic and it adds glitches when transient gets moved ever so slightly. That's what I meant.

Dude. When someone say's something is broken - that means its broken. It does not work. What else is there in it? It doesn't retain its information as it suppose too. The original post explains it clear enough.

Only in Cakewalk, yes. I have had the privilege to work with it in various other daws - and it works as expected and perfectly in them. Reaper? OMG! Smooth! Best one by far is FL. Obviously PT too.

Did you read the original post? It has been broken for years in cakewalk. Cakewalk is problem the only DAW where this doesn't work correctly or not as advanced as other DAWs. Hack even Audacity's Audio Snap and stretch mode works better. minor tweaks in cakewalk and It sounds robotic and stretched out. You can be the best guitarist or drummer, there's always transients you want to tighten more, to have things sound more tighter. This is especially important with a live performance project on client requests. A good example for you to understand what im saying is - would be to use a vocal piece and move it's transient to hear what we're talking about here. This goes for hats, snares too.