-
Posts
94 -
Joined
-
Last visited
Posts posted by NokNod
-
-
-
-
23 hours ago, PhonoBrainer said:
I like this a lot! Trappish ambient fun. For variation, I think the authentic hand claps could drop out, or be messed with ocassionally with effects. But by then you are probably adding a lead instrument, spoken word, rises, suddenly it's 7 minutes long . . . all that good stuff !!! A really hypnotic foundation, nice job!
Your text has a cool glitch effect, how did you get that going?
cheers,
-Tom
Thanks for the great feedback, the video/text was done with Z game Editor (a video authoring plugin included in Fl studio)
-
19 hours ago, Wookiee said:
I think this is the Car Mix, especially if you got a pair of 15's or 18's in trunk.
But for more conventional listening the kick is way to hot.
Do you have other plans for it as it sort of goes no where and does not develop?Nope no plans for it, just having some fun learning
-
enabling Send all keystrokes to this plug-in button is not working with one of my 3rd party vst instruments, will a conflicting keyboard shortcut binding cause this
-
you are right, I think that kick drum is driving the master bus peak levels way too hot, so the overall mix got squashed when I put a limiter on the master bus to keep it from clipping.
-
-
-
-
that Real Hip Hop....Ohh
-
ok got it, current day PPQ is really about sequencer display resolution, not sequencer timing resolution....my head is spinning
-
If I'm understanding this right, even at 96PPQ a quantization setting of 1/8 will always snap the MIDI event to the nearest 1/8 note interval, but if quantization were disabled at 96PPQ there would be fewer tics between the 1/8 note intervals where a MIDI event may occur as opposed to 960PPQ ?
-
additionally, is there a relationship between the midi record input quantize function and project PPQ ?
-
3 minutes ago, Noel Borthwick said:
It should make no significant difference. Internally the MIDI engine runs at a higher resolution than 960 PPQ.
this is confusing, does this mean the Midi engine is always operating at a high resolution even when the project PPQ is reduced to say for example 96PPQ ?
-
Anyone changed the default sequencer resolution from 960 PPQ if so did Cakewalk perform better or worse ?
-
Good News...! IF you have the full version of MPC Software. Version 2.10 was released yesterday. The update seems to run pretty smooth with Cakewalk. I ran it this Am with no crashes and my test project saved and loaded without issues
- 1
-
I tried MPC Beats but...MPC Beats is too resource hungry and takes almost 700MB of ram. The load time takes too long and causes too many crashes. I would only use that stand alone mode. An option I found that works is Poise VSTi it is 64bit and has all the functions of the MPC style sampler and its free...if you are interested the link is here https://www.onesmallclue.com/
and a video walkthrough ..
- 2
-
More stable than ever for me
-
Very very nice !
- 1
-
-
Aha thanks 😁❕
-
-
Using the step sequencer with 3rd party VST drum sampler, but the midi notes are actually 2 octaves higher on the steps sequencer than the note numbers on my drum plugin, is this something I can fix in my cakewalk preferences ?
-
select notes you want to Quantize then go to the [edit] menu and select [quantize]
or
use the keyboard shortcut [Q]
The Full Version of Apisonic Speedrum was released get it for 60 bucks
in Deals
Posted
Just as Dope as One Small Clue Poise