[FujiSkunk]

Oh dear, I think I found a bug.

 

I’m building a song with a single instrument, keys, and I have a background and a (silent) crowd track also. I was getting ready to compile the song when I realized I had set the wrong audio files for keys and background. I reset those entries to the correct files, and then hit compile. I got a complaint I was using audio stems with different bits per sample. It then listed two tracks with 16-bit samples and three tracks with 24-bit samples. It’s supposed to be using only three tracks, and they all have 24-bit samples.

 

I erased the entries for all three audio files, then browsed to those files again. Now when I hit “Build” I get a complaint with a list of eight entries: “Keys (16-bit), Backing (16-bit), Keys (24-bit), Backing (24-bit), Crowd (24-bit), Keys (24-bit), Backing (24-bit), Crowd (24-bit).” Something’s getting stuck in the accumulator!

 

Restarting Magma seems to clear the issue.

[TrojanNemo]

Small update.

 

v3.3.0

FIXES

- Improved audio encryption strength (don't worry, it's still optional for non-C3 authors)

- Fixed bug where not supported audio tracks would accumulate and list multiple entries

[StackOverflow0x]

Does anyone still care about themes? Some updates ago fixed some issues with themes so here are some flat light and dark themes I made that anyone can use.

http://ge.tt/2b9Kn6D2/v/0?c

 

 

[FujiSkunk]

- Fixed bug where not supported audio tracks would accumulate and list multiple entries

 

Thanks, Nemo! ” src=”/wp-content/uploads/invision_emoticons/default_SA_biggrin.gif” />

[TrojanNemo]

I should have said “should have fixed” – should work but I have no way of testing since my audio files always match ” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif” />

[FujiSkunk]

Yeah, well, I don’t usually do that. I was just lucky that day. ” src=”/wp-content/uploads/invision_emoticons/default_SA_cheeky.001.gif” />

[BobQuentok]

Does anyone still care about themes? Some updates ago fixed some issues with themes so here are some flat light and dark themes I made that anyone can use.

http://ge.tt/2b9Kn6D2/v/0?c

 

 

Wow, thanks!

[Linos Melendi]

Been getting this since the new update, tried with 3 different songs and recompiled twice too.

 

[TrojanNemo]

Well, derp.

 

The 10 of you who downloaded it before now, re-download if you want encryption to work.

[psiven]

I encountered a little quirk / feature I didn’t know existed when trying to compile a project with only PART DRUMS (+Events/Venue/Beat) and it kept insisting that I had a 2X track and it would compile both. Since there was no such track it gave some strange errors but I realized it was triggered by having “2X” in the file name.

 

Assuming this feature does work with a proper setup what should the 2X track be named?

[TrojanNemo]

The feature should only work based on the track name in the MIDI, not the file name itself. If it’s mistakenly reading off the file name itself, that’s something to fix. Confirm and let me know.

 

As far as how you use it properly, you have PART DRUMS and PART DRUMS_2X in the midi file. There should only be one midi file, and the name shouldn’t matter. What matters is how you name the tracks, as I just said. If there’s no 2x, then just name it PART DRUMS and that’s it. You should never have PART DRUMS_2X unless you have a PART DRUMS because that’s not how this works ” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif” /> The game only accepts PART DRUMS.

[psiven]

Thanks for the info!

 

If I understand correctly the REAPER track title doesn’t matter but the Track Title event does? In both cases they were “PART DRUMS” but the midi file name was “othafa wip6 2x bass pedal done.mid” It worked when I named the file “othafa wip6.mid” instead. (I hadn’t yet reduced the 1x part)

 

I’ll double check tonight but I probably ran it through the MIDI Cleaner first, which may have “fixed” the track title before the compiler saw it.

[TrojanNemo]

The REAPER title is not seen anywhere except in REAPER because that’s just a REAPER thing.

The actual TRACK NAME event, which is the first event in your track, is what matters to the game and what matters to Magma and all the other tools we have that work with the MIDI files.

Those need to be PART DRUMS and PART DRUMS_2X.

[Linos Melendi]

Unlikely request, but for Pro Keys, could you allow sharp/flat notes that are a semitone out of range to pass?

 

Ex. C#2/F3# in a D2-F3 range, D#2/G#3 in a E2-G3 range, etc.

 

I figured it wouldn’t be a big deal since I see stuff like this on C3 charts anyways

[Farottone]

I figured it wouldn’t be a big deal since I see stuff like this on C3 charts anyways

http://puu.sh/hfktP/195c660845.jpg

 

That’s embarassing, can you open a ticket in our bug reporting system?

[Author]

Posts