Magma: C3 Roks Edition v3.3.2 [07/28/15]
- This topic has 697 replies, 6 voices, and was last updated 1 year, 8 months ago by
.
-
Posts
-
Yes, I’m sure I have the latest public version of MagmaC3 (although the about screen says v1.3.4, the readme is 1.3.5). And I’m definitely not confusing vocal_tonic_note with song_tonality.
I hope you don’t mind, but I did some snooping around, and it looks like the bug lies here (MainForm.cs, readC3Fix() ):
if (str1.Contains(“TonicNote=”) && !str1.Contains(“-1”))
{
this.ComboTonicNote.SelectedIndex = Convert.ToInt32(str1.Substring(str1.IndexOf(“=”, StringComparison.Ordinal) + 1, 1));
this.chkTonicNote.Checked = true;
}
This will not work correctly if the vocal tonic note is more than one character long.
Well that’s certainly old code. Next version is much more sophisticated and does not have that problem. So I guess sit tight!
Dumb question time. I did a GH conversion in Reaper and got a MIDI file exported from Reaper. When I set everything up in the latest version of Magma: C3 Roks Edition and click the “BUILD AND AUDITION” button or just the “BUILD” button I get an error message that says:
Unable to save your project file. Please make sure the location you are saving to is writeable and not full.
I am trying to save it to the same directory where I have been storing Reaper project file, MIDI’s and all my song info so I know it’s writable and I know it’s not full. Any ideas why it would say that? I didn’t know if it made a difference but I tried running Magma regularly and then running as Administrator and got the same message. Any help is appreciated as I really just wanted to see what all errors Magma gave me and kinda work backwards from there.
The not-so-good news (depending on who is looking at it): this will be the last version of Magma I intend to release, except for occasional minor bug fixes.
I am trying to save it to the same directory where I have been storing Reaper project file, MIDI’s and all my song info so I know it’s writable and I know it’s not full.
Just because it’s writable to one program does not mean it’s accessible to all programs. Make sure this is not on a networked drive, or a MAC drive running on Windows by some magic tricks, or Windows running through an emulator or something, or any other non-standard scenario. Magma is intended to work only with “this is a hard drive on a real windows operating system” scenarios. I know that this issue was brought up in the past and was resolved for that user, but don’t remember how. Maybe do some searching on here or read back through the thread. Or just wait until Magma v2 comes out
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />UPDATE
Here we go. This feel like it has been a never-ending BETA, so I’m going to finally push it live before I go crazy.
v2.0
SKINS!
- Magma now includes three built-in skins: "Old & Dark" (default), "Shiny & New" and "C is for Colorful"
- Also added support for custom skins - create a .skin text file and put it in the (MagmaDirectory)/skins/ folder. Choose it from the Options - Skins menu, or drag/drop it to the form. Will remain default skin even after closing Magma until you change it to another skin. Many things can be skinned, refer to the template files for more information. Share your skins!
- Added ability to take a screenshot of Magma for those of you who want to display and/or share your skins: just press the Print Screen button and a screen capture is saved to Magma's install directory. By default, the image will also be uploaded to Imgur and the link will be copied to your clipboard, so you can just paste it anywhere you need to link to the image. The Imgur page will also be opened so you can verify the image. You can disable the uploading feature under Options - Skins.
TO DO LIST!
- Added feature to keep track of up to 15 to-do items per song. Each item can be marked as Important and/or Completed. Important items are marked yellow, Completed items are marked green for easy visual reference. Any Important items that are not Completed will prevent you from compiling the song and will remind you when you click Build. Each project gets assigned the items in default_template.todo. You can modify this file manually with a text editor or edit the To Do List in Magma, and click on the Hard Drive icon and choose 'Save current list as template' and name it default_template if you'd like to change the default template used for every song. You also have the choice of keeping a variety of templates, just click on the Hard Drive icon and choose 'Load existing template'.
MIDI TESTER!
- By popular request, added yet another way to simplify your life. Want to know if a MIDI you were given or found online is ready to compile without having to first set up a Magma project, track down the audio, etc? MIDI Tester will do it all for you, all you have to do is drop your MIDI file onto it, and sit back. MIDI Tester will create a project based on the MIDI information and try to compile it, and let you know what problems, if any, the MIDI file has, all in 2-5 seconds! Among the things it does, MIDI Tester will let you know if the MIDI passes a basic EMH check for reductions. You can click "Open MIDI" to select one or multiple MIDI files. You can also drag/drop one or multiple MIDI files. Files will be opened and processed in turn. If you open MIDI Tester while you have a project open in Magma, the current project's MIDI file is automatically loaded into MIDI Tester.
- MIDI Tester can be opened via command line: use "-miditester " and it'll be loaded straight into MIDI Tester. Replace with the full path to the midi or a relative path to Magma's installation directory (i.e. if it's in MagmaFolder/test.mid you can use "-miditester test.mid")
IMPROVEMENTS
- Massive consolidation and cleaning up of the code into single NemoTools class = more efficient, easier to maintain and significantly less lines of code overall
- All instances where there is image handling should now be more efficient and accurate
- No longer using x360.dll, using my own modified and considerably slimmer version of the code (you can safely delete x360.dll from your directory)
- Expanded MIDI validation to included 5 lane keys and pro keys - this is to work around the bugs in MagmaCompiler from the hacking we've done. This ought to throw errors at you similarly to how MagmaCompiler does and should prevent random unexplained crashes when building. Moved to the Build form to display inline with the rest of the compile log.
- Expanded MIDI Validator to ensure Pro Keys has BRE marker when Standard Keys has them (original MagmaCompiler would not flag this)
- Expanded MIDI Validator to check for lower difficulties being present for Pro Guitar/ Pro Bass charts (original compiler did not check for this at all)
- Added MIDI validation to Export MIDI function
- Moved MIDI Autogen (generates fake pro keys, keys animation, adds drum mix events) to Build form to display inline with the rest of the compile log
- Expanded MIDI Autogen to automatically replace "section " with "prc_" to make [most] old section names compatible with RBN2.0
- Expanded MIDI Autogen to account for disco flip as well as old, unsupported mixes (will be replaced). Also will now process the entire drums chart, rather than only the first four drum mix events (mainly useful for charts with disco flips)
- Added support for 24-bit silence tracks (included in the audio folder)
- Enabled typing in of song preview minute field
- Added workaround (hopefully) for issue when you move your project folder around and files can no longer be found
- Cleaned up and improved logging during song build
- Cleaned up Magma directory, moving most of the .dlls and other files to bin
BUG FIXES
- Fixed bug where animation speed would not be loaded when reading project file
- Fixed bug where Song Name and Artist Name would not be saved to Project File during importing of CON/LIVE file
- Fixed bug where attenuation values were not being saved correctly
- Fixed bug where some song IDs would be corrupted when importing a CON/DTA file
- Fixed bug that left HOPO Threshold drop-down enabled even when the song had no guitar/bass/keys. Now it is disabled unless either Guitar, Bass or Keys are present in the song
- Fixed bug that assumed your Magma project file was in the same folder as the RBA file (would cause problems with the overriding features)
- Fixed bug where if audio file saved in your project was not found might lead to a crash depending on the path
- Fixed bug where Audio Compiler would throw an error based on incorrect file path to the audio stems
- Fixed various other minor bugs
Huge, huge, huge update. This is not even a suggestion. It’s a requirement.
Everyone must update to this version. I will not offer support for anything earlier than v2.0.
I re-structured and re-did the OP, since the details that were there were outdated and made no sense at this point. You may want to read through that. In case you’re being lazy today (just today, I understand), here’s the relevant part I want everyone to read:
I want THIS or THAT added to Magma
Sorry, you missed the chance to make requests! As of 10/16, Magma: C3 Roks Edition v2.0 was released and no further development is planned except for minor fixes. No new features will be added or requests considered.
Download link in the OP. Enjoy.
Let’s hope when I wake up, I don’t wake up to the forums up in arms because I broke customs
So, I know I said I would stop. But I thought of one last thing I would do for you guys with Magma (besides a bunch of bug fixes I got worked out in the meantime).
Coming sometime next week.
Pretty nifty.
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif”>Congrats on the release Nemo!
For those interested, it is possible to run the MIDI tester directly by using the normal Windows Open With… and Send To… commands on any .mid file. Since v2.1, this doesn’t need any special tweaks; it just works like any other Windows program.
HOW TO ADD MIDI TESTER TO WINDOW’S OPEN WITH AND SEND TO COMMANDS
You can associate MagmaC3 with MIDI files by using the usual Right Click -> Open With -> Choose Default Program command (Or whatever its called for your particular OS version) on any .mid file.
To make it work with the Send To… command, create a shortcut to MagmaC3 in your SendTo folder, which is in C:Users[YourUsername]AppDataRoamingMicrosoftWindowsSendTo . However, this will make it an option for ANY type of file, regardless of whether MagmaC3 supports it.
Damn, I knew I was forgetting something. Well, there’s a 2.1 coming so i’ll make sure to include your script then. Thanks!
An automatic 1x bass pedal maker? Sounds nifty. Certainly that’ll come in handy if I get the skill to take on some of that heavier metal. Looking forward to it.
ehhh I think you’re jumping the gun there and hoping for too much
” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif” /> dial it back so you won’t be disappointed ” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />Here we go. Last update I have planned to do. Going forward, I may release bug fixes after enough bugs have been reported and if time permits. But this is it for me.
I have poured over 300 hours over the last 5 months into this project, and I don’t regret a moment of it. But life moves forward and I have to prepare for the next step in my life, so I can no longer dedicate time to Magma.
Don’t worry, i’ll still be around for the foreseeable future.
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />
v2.1
(NEW!) - Added ability to compile 1x and 2x bass pedal songs with only one MIDI file / project! To do this, you must have PART DRUMS and PART DRUMS_2X in the MIDI. When adding that MIDI to the project, Magma will pick it up and mark the song as 2x Bass Pedal. When you "Build" the song, Magma will do all the MIDI magic necessary and you'll have both the 1x and 2x CON files, as well as the 1x and 2x RBA files if you choose to keep them. Each track is compiled in turn to ensure both comply with all requirements. This ensures that all other MIDI tracks and project metadata is always correct across both versions since you only have to maintain one! And of course, saves you time. YOU DO NOT HAVE TO USE THIS. Old way of doing things still works the same.
- Added ability to use TIFF (*.tif), GIF (*.gif) and DDS (*.dds) images for the album art
- New method for creating png_xbox images will generate better looking album art with less artifacts than before
- Expanded ability to open MIDI Tester by sending a MIDI file to Magma via command line without needing to include -miditester in the argument. This means you can now right-click, Open With and send MIDI to Magma and go directly to MIDI Tester.
- Fixed bug where using File - Save As would also alter the old project file and old Custom ID would be carried across projects
- Fixed minor bug that would prevent HOPO notes on 5-lane keys
- Added ability to bypass MIDI Validator ... this is in case there is anything else that I broke and I am no longer around to fix it.
- Fixed bug where preview start would not default to the intended 0:30 unless you modified it in some way
- Fixed HOPO Threshold selection being disabled when opening Magma by double-clicking on an existing project
- Fixed bug that would lead to crash if you cancelled out of the Select Le Fluffie Path screen
- Fixed bug that would assign recording and re-release dates incorrectly when importing a CON
- Fixed bug that would make the "Send to Audacity" prompt disappear when importing a CON if "Show Toast Notifications" was enabled
- Fixed bug that would make drag/dropping of audio files after importing a CON file not work unless you closed/reopened the project
- Fixed bug that would fail to add drum mix events if none were found in the PART DRUMS track
- Fixed bug that would not display the errors when audio files loaded into Magma were not in the correct sample rate or have the correct amount of channels
- No longer using Tao.DevIL.dll or ILUT.dll (you can safely remove them if you still have them, no longer included with the program files)
HOW TO USE DDS IMAGES IN ALBUM ART (BETTER QUALITY IN GAME!)
– Make sure you have enabled ‘Override album art’ in Options – ADVANCED SETTINGS
– Place .dds file in the same folder as your project (*.rbproj) file. You can drag/drop it on the album art image and Magma will convert it to BMP just so it can show you something in the project window, when compiling Magma will use the DDS file itself.
To make the DDS file:
I recommend Photoshop + nVidia Texture Tool (Google it, it’s free).
Resize the image to 256×256, File, Save, DDS/D3D format. Leave the default format, but in case it’s modified, you want “DXT1 RGB 4 bpp | no alpha” (not DXT1a or DXT1n or any other DXT#), 2D Texture, ENABLE ‘Generate MIP maps’. All other options unchecked.
This (at least in Photoshop), gives you a slightly higher quality DDS image than what any source code/external library I have used can give you. From there to png_xbox nothing is lost, so this means you can have superior image quality in game!
This may be doable in Paint.NET or GIMP, I’ll let you figure that out.
HOW TO USE THE NEW 2X BASS FEATURE:
Normally (as I understand it), we create one REAPER project which contains both the 1x and the 2x bass pedal tracks, then we mute one and export, mute the other and export, and then compile each separate Magma Project.
NO MORE!
Keep both charts in REAPER, set the track name as “PART DRUMS_2X” for the 2x bass chart, and export the midi with BOTH drum charts enabled. I know this goes against how we’ve done things for a long time, but trust me, it works.
You only need to have one Magma Project. You don’t even have to mark is as 2x bass pedal. It will do so on its own when you feed it a MIDI that contains PART DRUMS_2X in it. If you already have it marked as 2X Bass Pedal in your project, don’t even need to change anything either.
When building, the MIDI is separated into two MIDI files, 1x.mid and 2x.mid. Each MIDI only has one drums track left in it, with the PART DRUMS_2X being renamed to PART DRUMS for the 2x midi. Each midi is assigned to the project, saved, and compiled in turn. This ensures that MagmaCompiler approves the MIDI before the RBA and CON are created (rather than just compile one version and replace the midi for the second version, which would allow problems into the song).
Nothing changes in your project files you have now.
You DONT have to use this new feature. You can continue to do separate Magma Projects for each track and nothing will change from the behavior you’re used to unless a PART DRUMS_2X is found in the midi file.
– Both 1x and 2x RBAs are created, both 1x and 2x CONs are created. Only the 2x version will prompt you with the “Visualize” and “Send to LeFluffie” buttons if this process is happening.
- You must be logged in to reply to this topic.