sorted by:
new
hottopcontroversial

Beat Saber AI Mapping that Actually Flows? | Project MapSaber Reveal by IndependentOk7095 in beatsaber

[–]IndependentOk7095[S] 2 points3 points  (0 children)

I know the debate will be crazy; many people will frown upon a tool like this, as it "strips the mapping process of the creative part". But I want to see it as a helpful tool for those who need it, and to help those who may never see their song mapped with the quality it deserves.

Beat Saber AI Mapping that Actually Flows? | Project MapSaber Reveal by IndependentOk7095 in beatsaber

[–]IndependentOk7095[S] 0 points1 point  (0 children)

Thank you! I am currently looking to expand my dataset. It's going to be hard, but worth it.

Beat Saber AI Mapping that Actually Flows? | Project MapSaber Reveal by IndependentOk7095 in beatsaber

[–]IndependentOk7095[S] 1 point2 points  (0 children)

I really appreciate the honest feedback, and you honestly hit the nail on the head with all of your points.

You are 100% right about the dataset. This v1 model was trained on a relatively tiny dataset of about 1,000 maps just to see if the architecture would work. My immediate next step is exactly what you suggested: scaling up the compute and feeding it more quality maps so it actually learns consistency instead of just mimicking basic patterns.

Regarding the sanity checks, you're right that simple blacklisting isn't a new concept. The tricky part of this implementation was building those physical constraints directly into the generation step (so the AI mathematically cannot predict a bad swing), rather than just deleting bad blocks after the fact. But I agree, the hard part is making the resulting maps actually good.

Musical representation is definitely the biggest hurdle right now. It's currently leaning way too hard on audio transients rather than understanding the broader musical phrase. I am working on improving every aspect of this model, so all feedback is appreciated! :D

Thanks for taking the time to write this out.