Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4

[d.healey]

@Mighty23 Is 3/16 and 3/4 the same as triplets?

[Mighty23]

@d-healey said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

@Mighty23 Is 3/16 and 3/4 the same as triplets?

Are you saying that We can represent 3/4 as a triplet of half notes. In this case, we would write the duration as 1/2T, indicating that we are dividing each half note into triplets?

5 measures of 3 BEATS, is 3/4.

[ulrik]

@Mighty23 this is what I use (this is for extended tempo range

//	NOTEVALUE LOOKUP TABLES	------------------
const NVLookUpString = ["8/1", "6/1", "4/1", "3/1", "2/1","1/1", "1/2D", "1/2",
"1/4D", "1/2T", "1/4",
"1/8D", "1/4T", "1/8",
"1/16D", "1/8T", "1/16",
"1/32D", "1/16T", "1/32",
"1/64D", "1/32T", "1/64",
"1/64T"];

const NVLookUpNum = [8, 6, 4, 3, 2, 1/1, 3/4, 1/2,
3/8, 1/3, 1/4,
3/16, 1/6, 1/8,
3/32, 1/12, 1/16,
3/64, 1/24, 1/32,
3/128, 1/48, 1/64,
1/96];

[Mighty23]

@ulrik I understand , but at the moment, I'd like to figure out how to 'unlock' myself to understand the time signature. Multiplier and Tempo are from this script node.

[ulrik]

@Mighty23 Ok

[d.healey]

@Mighty23 said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

Are you saying that We can represent 3/4 as a triplet of half notes

Nope. I was asking you if they are equivalent because the triplet times are built in to HISE's tempo sync mode.

@ulrik said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

const NVLookUpString

You don't need to do this manually. There is a built in function.

const tempos = []

for (i = 0; i < 18; i++)
	tempos.push(Engine.getTempoName(i));

[ulrik]

@d-healey said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

You don't need to do this manually. There is a built in function.

Yes but I use an order from slowest to fastest, and the factory settings in Hise is not working like that, Hise has another order of tempo increase like 1/8D, 1/8, 1/8T etc

[Mighty23]

@d-healey said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

Nope. I was asking you if they are equivalent because the triplet times are built in to HISE's tempo sync mode.

Ok, sorry, I didn't understand.

Should I 'round' to the nearest tempo ?

[d.healey]

@ulrik Aha that makes sense

@Mighty23 said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

Should I 'round' to the nearest tempo ?

I'm not sure, I was just trying to see if the built in system already had what you wanted but with different terminology

[Mighty23]

@d-healey said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

'm not sure, I was just trying to see if the built in system already had what you wanted but with different terminology

I've already used the 'converter' node to go from frequencies to milliseconds. I could use non-integer Multiply values to achieve other time signatures (maybe), but I can't figure out how to calculate, so it's probably not the right way.

[Mighty23]

@ulrik said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

@Mighty23 Ok

How do you calculate 3/4 ?

[ulrik]

@Mighty23 said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

@ulrik said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

@Mighty23 Ok

How do you calculate 3/4 ?

You mean in scriptnode I suppose, I'm not very familiar with scriptnode.
What project are you using? You say "Music 101" where can I find that?

[ulrik]

@ulrik Ok, I opened up a project, and I think I have the same setup as you have.

First I am unable to get the tempo_sync node to follow Hise internal tempo
How do you do that?

It seems a tempo of 114bpm in Hise internal tempo relates best to the tempo_sync node tempo

So you have the usual note value settings, so setting that to 1/4 and the Multiplier to 3 seems to be near 3/4, but as I said, I don't know how to sync the tempo_sync node with Hise internal tempo so this is what I hear when listening to the metronome and the pulse together

[ulrik]

@ulrik Ok, the scriptnode tempo_sync node doesn't seem to follow Hise internal tempo but when the plugin is compiled it will follow the host tempo (at least in Logic)
However I can't get it to start on note on or start with the daw transport play
(So ignore the terrible out of beat in the video )

Anybody knows why, is there something lacking in my head or in Hise ?
@Christoph-Hart ?

@Mighty23 so your questions
3/16 = tempo 1/16, multiplier 3, same with 3/4, tempo 1/4, multiplier 3

as I show in this video
video

1/3 meaning 1 third of 1 bar (4/4) = 1/2T

[Mighty23]

@ulrik said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

@Mighty23 so your questions
3/16 = tempo 1/16, multiplier 3, same with 3/4, tempo 1/4, multiplier 3

as I show in this video
video

1/3 meaning 1 third of 1 bar (4/4) = 1/2T

Thank you for the time spent trying to understand together. I am on Windows and have not yet tested on Mac if tempo_sync follows the values of the DAW. The title of the post is ironic and means that I have failed the basic concepts of music theory. Thank you again for your time. I'll try to run some tests myself

[ulrik]

@Mighty23 said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

Thank you for the time spent trying to understand together. I am on Windows and have not yet tested on Mac if tempo_sync follows the values of the DAW.

Does it follow tempo on Windows?

[Mighty23]

@ulrik said in Failing at Music 101 , tempo_sync values. 3/16, 1/3, 3/4:

Does it follow tempo on Windows?

It works well