[CharityDiary]

Not sure if this will help entirely, but I set up a shortcut for converting midi’s to half/double time depending on the tempo of the existing midi and what i’ve mapped. Assuming you were using an existing chart (and thus, has a tempo map), and the nightcore version of that song is double time (or something like that, I’m not entirely sure how much those songs differ from their original versions), then this method might help.

 

In Reaper, you can set up a custom action to speed this up. Name it whatever you’d like, and for Double Time, add “Item properties: Increase item rate by ~6% (One Semitone” 12 times. For whatever percentage you’d want, you’d want to add/remove that action to get to your desired percentage.

 

I played around with this a bit, and it changes all the MIDI tracks without actually changing the tempo map. If it just changed the tempo map too, it would be perfect.

[CharityDiary]

 

Do you HAVE to change pitch or does it just need speeding up? Not that it changes the amount of time needed though.

 

My personal preference is to have the pitch shifted up as well, which is a natural byproduct of increasing the speed in Reaper without checking the “Keep Pitch the Same” box.

 

 

Although if you were planning to do this a lot, coding this event would be faster in the end.

 

I would do it for every custom if I had an efficient method, but I’m not great at coding, so I’ll probably just stick to the manual method.

[CharityDiary]

Not as fast as the “Change Entire Project % Speed and Pitch” key I was hoping existed ” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />

 

Thanks, I’ll just do that then.

[CharityDiary]

 

You’re way too kind, I feel like I’ve only scratched the surface of venues. That being said though I’m more than happy to help with anything ” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />

 

I will send you a friend request and possibly ask questions when I have them!

[CharityDiary]

[directed_all]

Sweet, thanks!

[CharityDiary]

Ask Ultimate_MANG0! He’s a wizard with that!

 

And as far as I know literally all the actual events are right here.

 

Thanks, that list is the majority of what I was looking for!

[CharityDiary]

I’ll try that and report back later!

[CharityDiary]

I’m on Windows 10 with no problems. Try loading up one of the specific commands on top of the generic CAT function and launch one of those. Try create_triplets.py, in example. The command should fail in this case with a message.

 

Hmm “Script execution error”. Can’t copy and paste the error message, so I’ll just transpose the last couple lines of it here.

 

File “CPython26Libdecimal.py”, line 649, in _new_

“First convert the float to a string”)

TypeError: Cannot convert float to Decimal. First convert the float to a string

 

Also found this somewhere online:

“Direct conversion from float to Decimal was implemented in python-2.7, both in Decimal’s constructor and with the Decimal.from_float() classmethod. Python-2.6 instead throws a TypeError suggesting to convert to string first”

Do I need to be using 2.7+ instead of 2.6.6?

[CharityDiary]

Are you sure it compiles in Magma?

 

I’m actually having the same problem, but instead of with drum autoreductions, it’s with *every function in CAT*. It acts like it does something, but no changes are made in the MIDI.

 

I’m trying to use it on projects that have already been compiled in Magma and are already playable in Rock Band, so that can’t be the issue. I’m also using the template, and have went through the checklist in the CAT to make sure everything is correct. I have the correct version of Reaper installed, the correct Python installed, etc, and I’ve even went and uninstalled / reinstalled all of my programs to try to fix it.

 

Seems like upgrading to Windows 10 caused this issue for me, and I can’t find a way to fix it. I have no hope that my issue will ever be resolved, but I figured I’d toss my experience in here just in case, in some way, it could help you guys resolve something.

[CharityDiary]

My tip is: suck it up! ” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” /> I do a ton of play/stop with my thumb and initially, more than 4 years ago now, it hurt like hell. You probably just need to build some strenght or resistance.

 

I’ll try! ” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />

[CharityDiary]

[deleted because Farottone’s reply makes a great end to the thread]

[CharityDiary]

Found it!

 

You’re not supposed to surround your track name text events in square brackets.

 

[PART REAL_KEYS_M]

 

[Commits seppuku internally]

 

Thank you so much!

[CharityDiary]

Depending on how you cut and paste MIDI events from the higher difficulty tracks to the lower difficulty ones, you may have gotten some extra cruft in the hard and medium tracks that is keeping Magma from parsing them correctly. On occasion I’ve had the event for track name get copied along with the other bits I was trying to copy.

 

If you’re willing to post your RPP project files, someone might be better able to see and explain what’s going on.

 

I checked the MIDI events, and everything looks fine.

 

Here’s a link to my RPP.

 

Pls halp. I’ve been beating my head against a wall here all day trying to figure this out ” src=”/wp-content/uploads/invision_emoticons/default_SA_frown.gif” />

[CharityDiary]

Here, I’ll open up the RPP again and post a screenshot. You can see the range markers in all four difficulties, and all sections under the overdrive marker are the same. Still says there are no notes, and no range markers, but only for Medium and Hard difficulties.

 

[CharityDiary]

Open your exported MIDI to check what’s in there.

 

Good idea. Let’s see here…

 

All difficulties of the Pro Keys track are in here, and they all look exactly the same, minus the overdrive phrases, which are only in the Expert track. They all have range marker notes as well.

[Author]

Posts