Just a quick "out there"

**STD_Sappy** · 08-19-2013, 07:39 PM

So, I stumbled upon the new engines, and I was like neat, there's a new interface that looks pretty spiffy. Played a song, and was like, oh neat, there's stricter timing windows. Played a song, and was like, oh neat, it's so off sync that I can't even time it correctly.

Perhaps there should be a day dedicated to the resync of songs so people can actually play the song to the rhythm, if people are taking this new engine seriously.

Just sayin~

Also hi

**Tim Allen** · 08-19-2013, 07:43 PM

you and devonin are the only two people that have had this problem lol guess it's just bad luck

mi40 · 08-19-2013, 07:45 PM

use offsets

**STD_Sappy** · 08-19-2013, 07:46 PM

mi40, yeah, i just noticed that.

woohoo

Tim Allen, i'm not sure what luck has to do with any of it

**Fission** · 08-19-2013, 07:52 PM

nah, it's definitely not luck. sync should really be normalized though. basically everybody uses a 1 or 2 frame offset universally so it's kind of silly that it hasn't already been fixed.

**TC_Halogen** · 08-19-2013, 07:52 PM

If you used an offset of 0 on the Legacy/Velocity engines and are playing R^3 with 30 FPS, apply this offset to R^3:

Global offset: 2
Judge offset: 1

If your offset differs from 0, add 2 to your global offset.

If you play > 30 FPS, use 0 for global and judge (if it differs on Legacy/Velocity, add by that number).

**XelNya** · 08-19-2013, 07:55 PM

Or you could actually do some reading and could have figured out the following.

1. If you're playing on R^3ed, a lot of people use a global offset of 2, a judge offset of 1.

2. The windows aren't any stricter. You're just earnestly not as good as you probably where.

3. It could be that you're using outdated equipment. If you're using an HP desktop with a screen that's at least a ruler thick, your equipment is outdated.

Just throwing it out there, but you obviously didn't do any research or talk to anyone seriously about it first. That's your mistake.

However, there are a few songs with issues. Such as the stutter in Bowser The Shredder, and I would like to see those kind of mistakes fixed. I give you that one.

Choofers · 08-19-2013, 07:57 PM

posting after the textbook definition of white noise

sappy don't listen to this fagroid

**Tim Allen** · 08-19-2013, 08:00 PM

guess i'm the lucky one who can use 0 global offset x.x i thought arc fixed this long ago

**axith** · 08-19-2013, 08:09 PM

Quote:

Originally Posted by Tim Allen

guess i'm the lucky one who can use 0 global offset x.x i thought arc fixed this long ago

I use a 0 global offset. Then again I wasn't much good with either velo or legacy, so I really didn't have issues with crossing over to R^3.

**Fission** · 08-19-2013, 08:12 PM

Quote:

Originally Posted by XelNya

If you're using an HP desktop with a screen that's at least a ruler thick, your equipment is outdated.

lol, you're the one that should be doing research. you do realize that CRT monitors are vastly superior for gaming unless you drop at least $300 on a high refresh rate LCD/LED monitor, don't you? you probably didn't.

**rCaliberGX** · 08-19-2013, 08:14 PM

Quote:

Originally Posted by Fission

lol, you're the one that should be doing research. you do realize that CRT monitors are vastly superior for gaming unless you drop at least $300 on a high refresh rate LCD/LED monitor, don't you? you probably didn't.

ninja'd

but then again not every CRT can go 120hz+ and can only run those refresh rates on certain resolutions.

**Fission** · 08-19-2013, 08:16 PM

true enough. more often than not, they do though. i'd be pretty hard pressed to find one that doesn't.

Wayward Vagabond · 08-19-2013, 09:17 PM

hey sappy

justin_ator · 08-19-2013, 09:27 PM

Quote:

Originally Posted by Choofers

sappy don't listen to this fagroid

I lol'd hard

mi40 · 08-19-2013, 09:33 PM

Quote:

Originally Posted by Choofers

posting after the textbook definition of white noise

sappy don't listen to this fagroid

Jimmymi1 · 08-29-2013, 09:40 AM

Quote:

Originally Posted by Fission

lol, you're the one that should be doing research. you do realize that CRT monitors are vastly superior for gaming unless you drop at least $300 on a high refresh rate LCD/LED monitor, don't you? you probably didn't.

hahahahahahahahahahaha no.

mabye in some cases.

**popsicle_3000** · 08-29-2013, 09:55 AM

Quote:

Originally Posted by Fission

nah, it's definitely not luck. sync should really be normalized though. basically everybody uses a 1 or 2 frame offset universally so it's kind of silly that it hasn't already been fixed.

nope, 0.5 & 0.5 for me

**TC_Halogen** · 08-29-2013, 10:10 AM

The offsets are frame-rate dependent. If you use > 30 FPS, you'll have different results from 30 FPS.

My settings for 30 FPS are 2/1, but my 120 FPS settings are typically 1/0.

08-19-2013, 07:43 PM	#2
Tim Allen B^) Join Date: Jul 2013 Age: 29 Posts: 1,129	Re: Just a quick "out there" you and devonin are the only two people that have had this problem lol guess it's just bad luck __________________

08-19-2013, 07:45 PM	#3
mi40 ᅠ Join Date: Aug 2008 Posts: 3,652	Re: Just a quick "out there" use offsets __________________

08-19-2013, 07:52 PM	#5
Fission no Join Date: Jan 2004 Age: 33 Posts: 1,850	Re: Just a quick "out there" nah, it's definitely not luck. sync should really be normalized though. basically everybody uses a 1 or 2 frame offset universally so it's kind of silly that it hasn't already been fixed.

08-19-2013, 07:52 PM	#6
TC_Halogen Rhythm game specialist. Join Date: Feb 2008 Location: Bel Air, Maryland Age: 32 Posts: 19,376	Re: Just a quick "out there" If you used an offset of 0 on the Legacy/Velocity engines and are playing R^3 with 30 FPS, apply this offset to R^3: Global offset: 2 Judge offset: 1 If your offset differs from 0, add 2 to your global offset. If you play > 30 FPS, use 0 for global and judge (if it differs on Legacy/Velocity, add by that number).

08-19-2013, 07:55 PM	#7
XelNya [Nobody liked that.] Join Date: Sep 2012 Posts: 3,358	Re: Just a quick "out there" Or you could actually do some reading and could have figured out the following. 1. If you're playing on R^3ed, a lot of people use a global offset of 2, a judge offset of 1. 2. The windows aren't any stricter. You're just earnestly not as good as you probably where. 3. It could be that you're using outdated equipment. If you're using an HP desktop with a screen that's at least a ruler thick, your equipment is outdated. Just throwing it out there, but you obviously didn't do any research or talk to anyone seriously about it first. That's your mistake. However, there are a few songs with issues. Such as the stutter in Bowser The Shredder, and I would like to see those kind of mistakes fixed. I give you that one.

08-19-2013, 07:57 PM	#8
Choofers FFR Player Join Date: Dec 2008 Age: 33 Posts: 6,205	Re: Just a quick "out there" posting after the textbook definition of white noise sappy don't listen to this fagroid __________________

08-19-2013, 08:00 PM	#9
Tim Allen B^) Join Date: Jul 2013 Age: 29 Posts: 1,129	Re: Just a quick "out there" guess i'm the lucky one who can use 0 global offset x.x i thought arc fixed this long ago __________________

08-19-2013, 08:16 PM	#13
Fission no Join Date: Jan 2004 Age: 33 Posts: 1,850	Re: Just a quick "out there" true enough. more often than not, they do though. i'd be pretty hard pressed to find one that doesn't.

08-19-2013, 09:17 PM	#14
Wayward Vagabond Confirmed Heartbreaker Join Date: Jul 2012 Age: 35 Posts: 5,858	Re: Just a quick "out there" hey sappy __________________

08-29-2013, 10:10 AM	#19
TC_Halogen Rhythm game specialist. Join Date: Feb 2008 Location: Bel Air, Maryland Age: 32 Posts: 19,376	Re: Just a quick "out there" The offsets are frame-rate dependent. If you use > 30 FPS, you'll have different results from 30 FPS. My settings for 30 FPS are 2/1, but my 120 FPS settings are typically 1/0.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode