Wepeel

Glad you got it working.

You have to use the Toolkit version that is linked in the instructions for El Capitan. It may take up to 20 minutes for it to open the first time. But it won't open at all if you didn't follow the previous instructions correctly.

You're not typing it in correctly. You need a space between the mkdir command and the directory you want to create. It needs to be just like it is in the instructions: mkdir /usr/local/bin Same with the chmod 777 command.

Make sure you're typing in the commands into terminal correctly then. mkdir is a standard command, and you shouldn't be getting a "command not found" error making a directory.

You installed Mono version 4.0.4.4? It's been confirmed by a few users that the Mono installer has been corrected now and should install properly without the additional steps. You can verify by typing "mono" in Terminal. You can also type "which mono" and terminal will show you where Mono was installed.

What version of OS X are you running? And is your user account an administrator account?

As already mentioned, simply changing the tuning won't give you the result you're looking for. You're better off buying yourself a pitch shifting pedal like a Digitech Drop, Morpheus DropTune, Boss PS-5, etc.

The instructions are listed in the second post of this thread.

Nice job! Looks pretty sweet. What pups did you put in it?

No worries. I appreciate you moving it.

The icon changing is normal. It's done that for the last 15 or so versions. To quit the Toolkit, you have to hit exit in the file menu of the actual Toolkit. Hitting cmd-Q doesn't work. I tried both of those files, and both converted without issue for me. However, after successfully converting another file afterwards it crashed immediately and closed. Not sure if the problem is with any of those files, or just a problem with the Toolkit itself. I'll do some investigating and see. Previously I had been using an older revision of the Toolkit that had been stable and working for a long time. Since most of the creation tools in the Toolkit don't work on Mac anyway, I tend not to update the Toolkit so long as converting and extracting tabs still works.

Thanks for confirming. They must have fixed the Mono installation package then. I'll take that part out of the instructions.

@@gomer11, just wanted to let you know that I got the Toolkit working on El Capitan myself. I'll be posting instructions on how to do it soon. ** Edit ** The instructions are now posted here: http://customsforge.com/topic/10547-how-to-add-custom-songs-on-mac/ Let me know if they're clear enough, and easy to follow. The steps require using Terminal to create a directory and change the permissions on another. Hopefully I made it easy enough to follow.

You should be able to use the Toolkit to convert it then. I believe there is an import/update tool for RS customs.

What songs are you trying to convert? It might be easier to just see if there are current versions posted here. They would likely be more up to date.

I never found the Wineskin version to be that stable. Most of the features didn't work either. It was also over 1gb in size, instead of a few MB. I had no problems running the Toolkit on Yosemite, and found it perfectly stable. Anyway, it shouldn't take too long for the Toolkit's code to get corrected. It's not actually the Toolkit itself, but the script used to call Mono and launch it. The problem is basically that Mono is now being installed into a different spot. On a side note, I think it should be part of the rules that each charter upload their customs for both Mac and PC. Usually though, if you ask the charters they'll upload a Mac version. Or you might get lucky and another user will upload one for you.

No, it's not working. I posted a note about it in the "How To Use Customs On Mac" thread. @@Alex360 has been trying to edit the code to get it working, but so far has been unsuccessful. Part of the problem is that Apple has made changes to the framework of OS X El Capitan that no longer allows users to write or install things in the /usr/bin, which is where Mono is usually installed. Although you've reinstalled Mono, it hasn't actually been installed on your system. You can verify by opening Terminal and typing in "which mono". Instead of displaying the location of the mono installation, it will show nothing. You can also just type "mono" which will tell you that the command cannot be found. This is because the installer for Mono is broken as well, and actually fails during the installation without giving an error. I can give you instructions on how to get Mono installed properly if you'd like, but the Toolkit still will not work afterwards.

There's a tool on the forum here that will allow you to repair your profile. I can't remember what it's called. It may also be part of the Toolkit now, but I'm not sure. However, you'll need to figure out the cause of the problem if you want to avoid it in the future. Sometimes it can be caused by bad customs, or you may have quit the game during an autosave which caused your profile to become corrupted.

@@Backto0151, no it's not just you. As far as I know, none of the tools to create or import customs work on Mac. All I've ever been able to do is convert songs and extract the tabs.

There is a version for Mac, available from their website. However it doesn't work with the Toolkit.

I really hope Blind Freddy Blindman is part of next week's Blues DLC pack :stuck_out_tongue_winking_eye:

My list would include: Your Touch Set You Free (to remove the bad suggestions that I made the last time you updated it) Sister (slightly out of sync in different spots throughout the song) Till I Get My Way (You followed my suggestions last time you updated this one too, but I think it should be done like the tab book)

You can use the Toolkit to add DD to songs that don't have it already. You can also use the Toolkit to extract the tab from customs.

It's not the AppID, since almost all of the customs here use the Cherub Rock AppID. I think @@Liquidlizard meant the other song ID (I can't remember what it's actually called off the top of my head) that each song is generated with. Sometimes though, songs just conflict with each other or won't show up. I would say that at least 1 out of every 10 times I play the game a few of the customs I have won't show up in the game. It could be happening more frequently too and I'm just not noticing because I have too many customs to pay attention to them all. Usually, for me, forcing the song list to enumerate again will get songs to show up. You can do this by restarting the game (obviously) or also by just going back to the main start screen (by hitting esc from the main menu) and then entering the game again. Also, have you tried removing all of your other customs from your dlc folder and just loading the ones that aren't showing up? That will help narrow down if it's a problem with the custom(s) itself or if it's a conflict of some kind.

I'm glad you got it working :) However, I can't take any credit for RSInjector. It was here before I was. In fact, I used to play on Windows before RSInjector came around. All I did was put up the instructions on how to get everything working on Mac. You have Xavatar to thank for the patch.