+NS345 Thanks George!

well, floating point audio is basically 24bit audio with an 8 bit dynamic ruler so to speak. it is a little tricky to explain, but the neat thing about it is, you can have about 32bit of internal DAW dynamic range if your overall dynamic range of the project is very low, which happens to be a thing with lots of electronic music. since it is not an integer value you are working with, but narrowed values, it is better displayed as a number between -1 (-fullscale) and +1(fullscale) everything in between is "floating" except, as I explained, 24bit is the base quality, and the extra 8bit of extra precision the DAW uses when you are not totally awful in mixing. 32bit float gives you not so much extra precision when you try to mix very very silent signals with very loud ones. basically they invented it cause sometimes processing chains cause rounding errors and in rare cases that might even come to a limit of 24bit processing, even though 24bit processing is ample, as it gives you 144db (from top of my head) dynamic range - I did some tests back in the day with 32bit float vs 24bit projects and found out that while complex 32bit float projects sound besser, use more disk space, and less processing power than 24bit project. that last one with the processing power had to do with the operating system and the cpu running on 32bits, and it stresses the cpu less to play lots of complex audio streams, which usually occur in a DAW, with 32bit float files vs 24bit files as a base. from what I remember, the cpu needs to do a little extra work to get the 24bit audio streams to 32bit since engines usually are 32 or double that, 64bits, those extra 8 bits cause some extra heat for the cpu ;) I did those tests on windows xp and cubase back in the day, I could clearly see differences in handling and cpu load. apart from that, I ran into quantization noise issues when feeding a 32bit float stream into fixed point DSP solution, (Creamware) so for that setup it was better to use 24 bit audio files. I guess as a rule of thumb: unless you feed your audio stream to hardware DSPs that run on fixed point integer engines, it is better to use 32bit float! .) - I just recently came to protools but from what I heard their newest DSP solutions run on 64bit float or what?

+Panagiotis Begiazis Thanks for watching :)

+Do not Question Authority Cheers. I personally rarely ever use auto increment either. Some people might find it useful though.

Thanks!

@@paulmaunder3007 absolutely.. keep the videos coming.

No problem. Thanks for watching!

No problem!

Cheers!

That's interesting. Are you using the 3 at the top of the keyboard, rather than on the num pad?

Haha, thanks :)

No problem!

I'm afraid you can't turn that feature off

Thanks I thought so. I've tried everything.

There's no way to set it up to do that as such but you can quickly recall memory locations by clicking on them in the memory locations window during playback. Playback will then jump to the marker you've just clicked. It won't be seamless but it should be good enough to give you an idea of whether something will work or not. Alternatively, select the area you don't want and from the Event menu choose Time Operations and then Cut Time. This will cut out the selected section and close the gap. Just remember to undo it if you don't like the result!

Thank you for answering my question.