|
Post by zergpower314 on Jul 27, 2009 14:42:22 GMT -6
I'm pretty sure 10000-10001 (very minute gap though, so probably not one), 15000-15001, and 20000-20001 are tempo gaps. There are not any significant enough to be between 20001-30000 (not that anyone would go that high anyways '>_>) I could help with the recording, as I don't even know my tempo limits yet, lol. If you don't mind waiting for forever, then yes, you can help record.
|
|
|
Post by buckyboy2009 on Aug 6, 2009 6:08:45 GMT -6
Hey, I think I found one at 1395. Can anyone else confirm this?
|
|
|
Post by RehdBlob on Aug 6, 2009 19:45:44 GMT -6
I think I found... not really a tempo 'gap' per se, but a tempo 'transition' from 832 to 833 to 834. Each difference of 1 makes more difference in tempo than any other tempo 'change' in the regions close to this.
|
|
Moo
Piranha
卐
Posts: 114
|
Post by Moo on Oct 30, 2009 16:20:18 GMT -6
I seem to have found the same breaking point as JF there, 8572. This list really needs to be updated.
|
|
|
Post by RehdBlob on Jan 2, 2010 17:54:31 GMT -6
It has been updated with lots of new BP's and a revision to the 2308 gap; the BP is actually at 2223.
|
|
|
Post by Colin Comard (Delay) on Jan 2, 2010 18:24:45 GMT -6
I'll tell you this: The tempo gap is NOT 8752.
At least, I'm quite certain. It's kinda hard to tell sometimes. (like it's only a teeny bit slower at 8700 than 8752, or I could be imagining it.)
|
|
|
Post by lih on Jan 5, 2010 22:49:54 GMT -6
It has been updated with lots of new BP's and a revision to the 2308 gap; the BP is actually at 2223. 2223 would be a new tempo gap then 2308 is quite a bit faster than 2307
|
|
|
Post by RehdBlob on Jan 5, 2010 23:03:02 GMT -6
Ok, fixed yet again.
|
|
|
Post by Jeffburtonfan on Jun 24, 2010 23:59:43 GMT -6
I think you guys should check out 8571 and 8572. That seems to be another tempo gap
|
|
nolimits
Piranha
dun dun dun d-dun dun
Posts: 121
|
Post by nolimits on Sept 12, 2010 12:50:40 GMT -6
This is a really helpful thread that I just found
|
|
|
Post by That One User on Feb 1, 2011 15:13:53 GMT -6
Umm...
Either 882 is in a tempo gap or the 3530 BP is wrong.
|
|
|
Post by MrTanookiMario on Mar 25, 2011 11:19:44 GMT -6
Hey, I think I found a tempo gap not shown in the OP's post. It's at the 1176-1177 border. The lower end goes down to at least ~1154.
|
|
|
Post by vengeance on Sept 19, 2011 12:07:40 GMT -6
5000/5001 is a tempo gap
|
|
|
Post by RehdBlob on Sept 19, 2011 13:38:00 GMT -6
^ That's already been documented on the first page.
|
|
|
Post by tommy73 on Oct 24, 2011 8:59:18 GMT -6
Just discovered a new tempo gap. 1395/1396. There doesn't seem like a difference between 1429 and 1396 so yeah.
|
|
|
Post by satoriga on Mar 22, 2012 19:08:58 GMT -6
nice work on this. hate gaps =(
|
|
|
Post by RehdBlob on Aug 25, 2013 21:32:32 GMT -6
I have discovered the origin of tempo gaps:
Because MPC decides its tempo by dividing 60000 by whatever you enter as a number for the tempo, and then truncating / rounding / doing something to the number, this causes the program to actually change the resultant tempo only when the division actually produces a different number.
For example: 60000 / 2222 = 27.00270027 => truncated to 27 60000 / 2223 = 26.9905533 => truncated to 26 => 2223 is a tempo gap.
60000 / 2726 = 22.01027 => truncated to 22 60000 / 2727 = 22.00220022 => truncated to 22 60000 / 2728 = 21.99413489736 => truncated to 21 => 2728 is a tempo gap.
Using this rationale, we can find all of the tempo gaps of MPC...
|
|
|
Post by lih on Aug 27, 2013 3:05:37 GMT -6
249 250 251 251 252 252 253 253 254 254 255 255 256 256 257 257 258 258 259 259 260 260 261 262 263 263 264 264 265 265 266 266 267 267 268 269 270 270 271 271 272 272 273 273 274 275 276 276 277 277 278 279 280 280 281 281 282 283 284 284 285 285 286 287 288 288 289 289 290 291 292 292 293 294 295 295 296 297 298 298 299 300 301 301 302 303 304 304 305 306 307 307 308 309 310 310 311 312 313 314 315 315 316 317 318 319 320 320 321 322 323 324 325 326 327 327 328 329 330 331 332 333 334 335 336 337 338 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 355 356 357 358 359 360 361 362 363 364 365 366 368 369 370 371 372 373 375 376 377 378 379 380 382 383 384 385 387 388 389 390 392 393 394 395 397 398 400 401 402 403 405 406 408 409 410 411 413 414 416 417 419 420 422 423 425 426 428 429 431 432 434 435 437 438 441 442 444 445 447 448 451 452 454 455 458 459 461 462 465 466 468 469 472 473 476 477 480 481 483 484 487 488 491 492 495 496 500 501 504 505 508 509 512 513 517 518 521 522 526 527 530 531 535 536 540 541 545 546 550 551 555 556 560 561 566 567 571 572 576 577 582 583 588 589 594 595 600 601 606 607 612 613 618 619 625 626 631 632 638 639 645 646 652 653 659 660 666 667 674 675 681 682 689 690 697 698 705 706 714 715 722 723 731 732 740 741 750 751 759 760 769 770 779 780 789 790 800 801 810 811 821 822 833 834 845 846 857 858 869 870 882 883 895 896 909 910 923 924 937 938 952 953 967 968 983 984 1000 1001 1016 1017 1034 1035 1052 1053 1071 1072 1090 1091 1111 1112 1132 1133 1153 1154 1176 1177 1200 1201 1224 1225 1250 1251 1276 1277 1304 1305 1333 1334 1363 1364 1395 1396 1428 1429 1463 1464 1500 1501 1538 1539 1578 1579 1621 1622 1666 1667 1714 1715 1764 1765 1818 1819 1875 1876 1935 1936 2000 2001 2068 2069 2142 2143 2222 2223 2307 2308 2400 2401 2500 2501 2608 2609 2727 2728 2857 2858 3000 3001 3157 3158 3333 3334 3529 3530 3750 3751 4000 4001 4285 4286 4615 4616 5000 5001 5454 5455 6000 6001 6666 6667 7500 7501 8571 8572 10000 10001 12000 12001 15000 15001 20000 20001 30000 30001 60000
every tempo gap using rehd's maths (unless there's an insignificantly small one earlier i missed) i couldn't be bothered to take out the ones that weren't gaps
|
|
|
Post by Mr. Sub on Aug 27, 2013 18:50:37 GMT -6
Interesting to see a lack of a basic (and logical) rounding up system, rounding 26.99 to 26, that explains it!
|
|
|
Post by tommy73 on Sept 1, 2013 11:24:02 GMT -6
I have discovered the origin of tempo gaps: Interesting to see a lack of a basic (and logical) rounding up system, rounding 26.99 to 26, that explains it! Because it's truncating and not rounding? It's right in Rehd's message.
|
|