Replying to:
raimondzHi, I tried to use it on my O3DS but it doesn't work well. You forgot to use gpage before and after rendering the gui to draw everything in one step.
Yep, I cringe a bit now thinking that I didn't do this, but lesson learned about understanding how my programs will behave on various target devices, and not being lazy.
Replying to:raimondzHi, I tried to use it on my O3DS but it doesn't work well. You forgot to use gpage before and after rendering the gui to draw everything in one step.
"I was expecting something more like FastTracker II or Famitracker but this I think is more fitting for the nature of MML itself. Can you even call this a tracker?"
I'm not actually sure what technically constitutes a tracker, but I grew up in the days of ModPlug Tracker, which has similar interface ideas, but I tried to tailor the program to fit the strengths of the 3ds. I'm not particularly attached to calling it a tracker though.
Wow. The screen flashes spasmatically. increasing the vsync seems to have little effect. You must be using a different hardware 3ds, i am using an older 3ds.
Replying to:
MZ952Make it so that it does not redraw the screen unless you offer input. That could at least minimize the flickering, plus its not really necessary to continuously redraw the screen when its not changing.
Alright, so ive added this code to your code, and it works OK-ish.
REPEAT
TOUCH OUT TM,TX,TY
UNTIL BUTTON() OR TM
Ive placed it just before the Vsync. Ive also edited vsync, setting it to 5. I think theres a command which can recognize the 3ds hardware version, you could use this to optimize (if im correct about its existence).
For those who want to optimize it themselves this way, go to line 872 and insert the code i wrote above the VSYNC command
Thanks MZ952, that's the plan. I'm going to do draw optimizations tonight, and overall profiling to make sure there's nothing else creating a bottleneck.
The VSYNC changes would work in most cases, except for when playback is happening, as it expects 60 FPS, but I could also fix this too.
Now, I'm just wishing I didn't give my old 3ds to a friend so I could use it to test (>_<).
EDIT: There is a system variable, HARDWARE, that specifies whether you are using an old or new 3DS but it's read only. This would be a nice feature to have though for debugging.
Update is now available. I've taken a quick pass at optimizing the draw functions (they only refresh when input is polled or states change). So this should look much better on the O3DS, or at least it will be functional for now. If you are a O3DS user, please let me know what your experience is like, so that I can make it better overall.
This update is sort of a bandaid, as I think more can be done performance wise, but it should be functional now. Thanks for your patience.
Replying to:
glennxsergeUpdate is now available. I've taken a quick pass at optimizing the draw functions (they only refresh when input is polled or states change). So this should look much better on the O3DS, or at least it will be functional for now. If you are a O3DS user, please let me know what your experience is like, so that I can make it better overall.
This update is sort of a bandaid, as I think more can be done performance wise, but it should be functional now. Thanks for your patience.
Thanks, this runs pretty well now! There's still a good amount of flickering whenever s change is made, but that can probably be fixed with the double buffering (or whatever it's called) that people have been talking about. It also seems to be running too slow during playback. (Song plays at proper speed, but the tracking bar and time are way too slow.) It also kept crashing while messing with the ASDR settings. (But the auto backup kept my project from being lost!) This will be really nice once it's fully optimized!
Replying to:glennxsergeUpdate is now available. I've taken a quick pass at optimizing the draw functions (they only refresh when input is polled or states change). So this should look much better on the O3DS, or at least it will be functional for now. If you are a O3DS user, please let me know what your experience is like, so that I can make it better overall.
This update is sort of a bandaid, as I think more can be done performance wise, but it should be functional now. Thanks for your patience.
hi mystman12, thanks for trying the new version out. It'll probably take a little back and forth to get this sorted, since I rely on feedback from 03DS users to identify issues.
I expected that playback would still be slow, because it needs to draw every frame to update the timer and the progress bar, but I'm thinking of ways to optimize that as well. I might just disable playback on the bottom screen for older models so that the top screen timer still works correctly.
The ASDR crash, is very unexpected, so I would be grateful for any line number or error feedback regarding what the context was when that happened. Thanks again!
EDIT: Oh, and I meant to ask, is the flickering present in every mode or just the note editor? For example, does the splash screen flicker too?
Replying to:glennxsergeUpdate is now available. I've taken a quick pass at optimizing the draw functions (they only refresh when input is polled or states change). So this should look much better on the O3DS, or at least it will be functional for now. If you are a O3DS user, please let me know what your experience is like, so that I can make it better overall.
This update is sort of a bandaid, as I think more can be done performance wise, but it should be functional now. Thanks for your patience.
The flickering only seems to be when you toggle things on the main editing screen.
Replying to:glennxsergeUpdate is now available. I've taken a quick pass at optimizing the draw functions (they only refresh when input is polled or states change). So this should look much better on the O3DS, or at least it will be functional for now. If you are a O3DS user, please let me know what your experience is like, so that I can make it better overall.
This update is sort of a bandaid, as I think more can be done performance wise, but it should be functional now. Thanks for your patience.
Thank you, MZ952, that helps me focus my efforts.
I just crashed on ASDR too, the very first time I was messing with it. I was dragging in all directions after tapping the various elements and IIRC it crashed while dragging. The error is "Out of range in 0:2187(SPSET:1)"
One request I would like to make it to be able to use the "hidden" instruments past the drum sets, like we can in NCF-MUSEQ. I just want access to that hollow flute square wave and raw noise. :)
Replying to:
UnclesporkyI just crashed on ASDR too, the very first time I was messing with it. I was dragging in all directions after tapping the various elements and IIRC it crashed while dragging. The error is "Out of range in 0:2187(SPSET:1)"
One request I would like to make it to be able to use the "hidden" instruments past the drum sets, like we can in NCF-MUSEQ. I just want access to that hollow flute square wave and raw noise. :)
Yep, that's the error I was getting.
I'd actually like to have those instruments, too, and even the ability to load custom instruments into the editor. That would be really handy!
Replying to:UnclesporkyI just crashed on ASDR too, the very first time I was messing with it. I was dragging in all directions after tapping the various elements and IIRC it crashed while dragging. The error is "Out of range in 0:2187(SPSET:1)"
One request I would like to make it to be able to use the "hidden" instruments past the drum sets, like we can in NCF-MUSEQ. I just want access to that hollow flute square wave and raw noise. :)
Ahh, that bug is related to my sprite optimizations. I know how to fix it. The hidden instruments I didn't even know about, but I will be sure to add them too.
EDIT:The custom instruments is on my list of extra features. I just need to think more about how to bundle them with the MML export so they are not troublesome to deal with.
Should have called it Flickerbox am i rite
Update is live. This addresses the sprite bugs Unclesporky and mystman12 discovered. I also added the additional hidden instruments 144-151 and fixed the timer so that it can keep track even when VSYNCs are missed during playback.
I still have more to do, but this should get rid of the problematic errors. Please let me know if you see anything else.
I think I can make this even more stable at 30FPS, but I'm wondering what people think about lowering the frame rate.
More bugs:
- I hit B a lot on one note, just playing around with portamento, but I can't select and delete those split up notes any more. Tapping on that space instead creates a new note, very short, rather than selecting the existing notes. I noticed that normally when you split up a note and delete part of it, it automatically selects another part of that split up note so you can delete the rest. After some messing around, I think they become permanent after you've done one playback.
- Very weird things can happen when you select notes and press right. If you are further along in the pattern, they will warp backwards, with the backwards movement more extreme the further you are into the pattern.
- After saving a new song, I was unable to reload that same song I had just saved. I had to exit out of the program and go back in, and then the song appeared in the load list. Also, could there be a button to exit and go back to the main menu?
- This isn't a bug, but is there really no way to choose a volume and have all notes placed after that point take on that volume? I have to adjust the volume of every note individually?
- Sorry to make more requests, but MUSEQ also has a series of instruments at the bottom of its second page that are all the same, 224 to 255. I assume these are custom instruments that haven't been customized. However, even in their uncustomized state they have a cool sound to them. Could we get one of these as an option too, even if actual customization isn't in yet?
Replying to:UnclesporkyMore bugs:
- I hit B a lot on one note, just playing around with portamento, but I can't select and delete those split up notes any more. Tapping on that space instead creates a new note, very short, rather than selecting the existing notes. I noticed that normally when you split up a note and delete part of it, it automatically selects another part of that split up note so you can delete the rest. After some messing around, I think they become permanent after you've done one playback.
- Very weird things can happen when you select notes and press right. If you are further along in the pattern, they will warp backwards, with the backwards movement more extreme the further you are into the pattern.
- After saving a new song, I was unable to reload that same song I had just saved. I had to exit out of the program and go back in, and then the song appeared in the load list. Also, could there be a button to exit and go back to the main menu?
- This isn't a bug, but is there really no way to choose a volume and have all notes placed after that point take on that volume? I have to adjust the volume of every note individually?
- Sorry to make more requests, but MUSEQ also has a series of instruments at the bottom of its second page that are all the same, 224 to 255. I assume these are custom instruments that haven't been customized. However, even in their uncustomized state they have a cool sound to them. Could we get one of these as an option too, even if actual customization isn't in yet?
I noticed the same issue with selecting the smaller notes, however you can still select them by selecting the previous note and then pressing A to select the next note.
Replying to:UnclesporkyMore bugs:
- I hit B a lot on one note, just playing around with portamento, but I can't select and delete those split up notes any more. Tapping on that space instead creates a new note, very short, rather than selecting the existing notes. I noticed that normally when you split up a note and delete part of it, it automatically selects another part of that split up note so you can delete the rest. After some messing around, I think they become permanent after you've done one playback.
- Very weird things can happen when you select notes and press right. If you are further along in the pattern, they will warp backwards, with the backwards movement more extreme the further you are into the pattern.
- After saving a new song, I was unable to reload that same song I had just saved. I had to exit out of the program and go back in, and then the song appeared in the load list. Also, could there be a button to exit and go back to the main menu?
- This isn't a bug, but is there really no way to choose a volume and have all notes placed after that point take on that volume? I have to adjust the volume of every note individually?
- Sorry to make more requests, but MUSEQ also has a series of instruments at the bottom of its second page that are all the same, 224 to 255. I assume these are custom instruments that haven't been customized. However, even in their uncustomized state they have a cool sound to them. Could we get one of these as an option too, even if actual customization isn't in yet?
Thanks Unclesporky, you're providing me a huge service by testing so thoroughly. No need to apologize, I'm happy to add the extra instruments, I just figured I'd wait until I understood how to do the custom instruments, but if they are immediately useful in their default state, then I'll add them in my next update.
The volume can be set on the first note in a channel and the rest of the pattern/song should maintain that volume (for the channel) until it's changed. Are you finding that not to be the case? The volume controls are in one of the fx modes, just to the left of the note button on the top row. You can visually tell when an effect has been applied to a note because a blue or orange dot will show up above or below it.
The song saving/loading issue when it's first made, is something I'm aware of, the file list just needs to be refreshed. This one will be easy to fix.
The note zooming left issue is a bit weird, I see it now under the same circumstances you mentioned, so I'll try to figure out why that's not behaving properly.
Portamento's shouldn't be able to continually be made if further subdivisions can't be visually represented, and notes in the same channel aren't supposed to occupy the same space. So I'll double check that as well.
Thanks again Unclesporky, this is hugely helpful info.
EDIT: oh and mystman12, if you hold L/R and press A it will select the previous note from your current selection too.
