[AJFOne23]

Don’t know if this has been mentioned but with v3.2.1 magma is making single and double pedal versions of a song but using the single pedal chart for both files ” src=”/wp-content/uploads/invision_emoticons/default_SA_frown.gif” />

[TrojanNemo]

Haven’t heard of that and didn’t happen with my testing. Post the MIDI you’re using so I can check.

[AJFOne23]

http://www.mediafire.com/download/u7ojw … Choose.rar

[TrojanNemo]

Good catch. Seems you are right. I’ll take a look at why. Also, if you’re ever sharing song files, each song has a .c3 file that goes along with the .rbproj file for all the extra C3 goodness.

[TrojanNemo]

v3.2.4

NEW FEATURE

- Added feature to automatically back up and restore (will ask you to confirm) the configuration file and song counter so nothing is lost from one install of Magma: C3 Roks Edition to another going forward



FIXES

- Modified behavior to assign and display a numeric ID the first time you save a project so you don't have to wonder what the ID assigned will be

- Fixed building of double bass pedal songs that would use the 1x MIDI in both CONs

- Fixed loading and saving of custom audio encoding quality (was reversed before if you chose anything other than default)

- Removed annoying pop-up when building a song that reminds you it's got 2x MIDI in the file - it was supposed to and now only shows up when you throw the MIDI at the project

- Fixed interface bug where context menu would have the text right-aligned if the path to the audio file was too long

 

Hopefully this works as intended

[AJFOne23]

Thanks for the quick turnaround Nemo. I have a pending release for tomorrow and this will help a lot

[TrojanNemo]

Hopefully it works as intended.

 

I just made a small update that won’t get a new number ’cause it’s not worth it. Small graphical bug I noticed but forgot to fix earlier today. Now it’s fixed ” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />

[Captainoffun22]

The maximum year you can go to is 2112 ” src=”/wp-content/uploads/invision_emoticons/default_SA_biggrin.gif” />

[TrojanNemo]

Yep. I’ll let someone else worry about adding support when we get to working on songs released after that

[TrojanNemo]

Here’s a question.

I recently revisited a few projects that were saved before Magma was updated to use numeric IDs. The cons produced by these projects have all been converted to numeric IDs using the batch tool. I’d like to add more tracks to these projects while retaining their current ID. I know Magma re-uses IDs saved in new projects, but how can I get it to re-use the IDs assigned (to my projects) during the batch conversion process?

 

Good question. I might take a look at integrating this better in an update later on, but for now you can make this happen if you follow these steps:

 

1) Open the CON file in CON Explorer and click on the song ID to copy it to your clipboard. Or just get the song ID however else you like.

2) Import the CON into Magma: C3 so the project files are created.

3) In the project folder created by Magma: C3, you’ll see a .c3 file that corresponds to that song. Open that with a Text Editor (I recommend NotePad++).

4) Find the line UseNumericID= and make sure it says UseNumericID=True.

5) Under that should be the line UniqueNumericID=, paste here the numeric song ID you want Magma: C3 to use for that song.

6) If that song had a 2x version as well with it’s own unique numeric ID, enter it underneath that on the line that says UniqueNumericID2X=.

7) Save the changes.

Magma: C3 will now use that numeric ID for that song going forward.

[Dash Riprock]

Thank you. Your instruction leads me to wonder if I could just paste the following into any existing song.c3?

 

UseNumericID=True

UniqueNumericID=xxxxxxxxxx

UniqueNumericID2X=

 

With the appropriate ID, of course.

[TrojanNemo]

That’s correct. But you should allow Magma to issue the IDs so there are no conflicts.

[Dash Riprock]

Yes. All new projects get a new ID. I just want all my pre-conversion projects to use the ID assigned by the batch conversion. So I’ll obtain it from the con, and insert it into the project file. Bob’s your uncle.

[TrojanNemo]

Close. Bob is my sister’s uncle on her father’s side, so he’s like family but the bastard is not related to me.

[Dash Riprock]

OK. Here’s a bit of weirdness.

 

I’ve inserted the IDs successfully, but found that for songs built with Magma 3.2.4, CON Explorer reports that song id was not found in dta.

[Author]

Posts