YEEEeee...I noticed that, too, the stupid mouse focus issue?! No idea when that snug in, but I certainly want to get to the bottom of it. I translated the project to visual studio 2010 and something might've twisted the code a bit the wrong way. I sure hope I'll solve that and another kink that happens more frequently, that is the missing effects section in the bottom portion of a synth that happens from time to time. Weird. But the code is a bit, uhmm....crude or cluttered.
Anyway, I'm really happy you're enjoying it, too! I wished we could fire up the forum again some more and do more fun stuff as we had done with the Challenge thread. That was great!
I wished we could fire up the forum again some more and do more fun stuff as we had done with the Challenge thread. That was great!
That should be fun. Even if not reviving the forum, at least some new challenge like things would give us/me something to aim at. Maybe we could make it even more simple then last time: where the list got rather long.
Hehe, if i dont see a new challenge thread appear soon, i might go cook something up and post it?! ^^ Or we could do a chain, where the challenge is set by the last one to finnish the previous one. Altough that idea might need some tweaking to keep it going.
Although I like something more defined it came to me we could make it a bit more open than last time. As to set a topic or theme and don't impose a form. So part of the challenge would be to find a form. For example the theme could be something fuzzy like "Entropy" or "Voice", and people can interpret that in whatever way.
It's actually harder of course, but there won't be an intimidating list that might discourage people to join in in a later stage. And meanwhile we could "copy" eachothers forms if we see fit.
Awww, bummer. Well, hope you'll have some fun with it until then. It's a bit buggier than previous versions, though. I switched compilers and it caused a few annoying issues. Upcoming versions will hopefully have them solved again. I'll try my best!
Ahh, I was wondering why this version was so buggy. I was about to rant about how my config was completely overwritten with zero...not to mention...the chip instrument... *shudders*
I get the feeling musagi needs a complete re-haul. I can feel it's messiness. I feel like I ought to learn C++ just so I can clean it up a bit, or at least help YOU do it. Looking beyond the bugs, it's a great release. I love the new blend/bias features! Though, Im still unsure what 'bias' actually does lol
Whatever it is, it sure makes for some fun accidents!
You should definitely include more instruments with the download, like what DrPetter had with the original...
Ah yes, never thought about that, adding instruments to my releases. Good idea! I tucked bias into normalize for lack of space but sufficient relation. Bias of the waveform allows you to skew the waveform to the left or ride side of it. This is particularly obvious, if you have a higher frequency waveform, two or more swings to raise the octave of it. There's also the "double frequency" button (next to noise), which doubles your wave and thereby raises it by one octave. You can blend that over the original, leading to some excellent effects.
CHIP is generally not buggy at all, except the pesky initialization bugs that can totally screw up playback every now and then. I only noticed that this can happen especially when you play with the arpeggios. If a sound appears to explode, reset the arps to default position and save it again. Funnier even, sometimes you can just lift the arpeggios to one octave higher and all is well. No friggin clue what's doing that either. The noise section is very different now, which has old sounds not act the same anymore. If anything had noise, it will most likely need some adjustment. It has changes so radically, that I couldn't just hook up some compatibility.
The config thing is weird (I never ran into that either), but a possible side effect of some of the funky stuff. Funkier stuff is mouse interaction on the song editor, which can reach through an instrument's interface, for example. Doesn't happen all the time, but some initializations can go wrong and then this happens along with other funky stuff of that nature. There is a general issue with the init of stuff. No clue what or why, yet. Ain't my code, you know, and I'm not clever enough to defragment and analyze it properly. When things go wrong, I recommend restarting it until it works right again...<cough, cough>...well hell.
You can remedy the "mouse going through part editor interface issue" (M.G.T.P.E.I.I) by hiding the song area (F9)...
But yeah, cleaning up the code a bit would require lots of time and devotion, and it'd be boring as heck, but it seems the more you add the worse it gets! My only complaint with musagi is that it doesn't feel solid, it feels quite clusterfudged in fact. It wasn't like that in v0.23. I suppose I cant complain too much, seeing as you're working voluntarily on a program you didn't originally create...
...but still, I cant help but flex my whining. Too bad DrPetter is too busy at his fancy new job to save us lol
Oh oh oh! I just thought of a great feature to add to the "chorus" effect! Is there any way to read the waveform of the synth being played and generate a duplicate waveform an octave lower? That would be spiffy.
Thanks for the encouragement. DrPetter abandoned musagi, because he knew it was getting wacked out. But the worst was my last round when I transitioned to doing a visual studio compile as opposed to the rogue style command line compiling he's been doing. However, it saw a great many unusual maneuvers and decided to try correcting them, which screwed it all up a good deal. I'm just not a windows code wizard, yet, and still feel juvenile when it comes to C++ coding at such a level. Needless to say the trouble of taking on somebody's complex code. It's all a big challenge, but some of what comes out of it is just too wonderful to regret regardless to your insensitive ramblings and regret inspiring efforts there. So, fudge you, dear, I'm doing my sorry best. ;D
I'd be thrilled if it was something I don't know as opposed to confirmations of some defeat, you know. I have a choice to either share the progress or just keep it to myself. That way I don't have to carry any responsibility until the time it is solid, should it ever get to there. And I think you're perfectly right in making me realize that. So... no worries, you won't have to be troubled about buggy releases beyond t1.68. In some ways, maybe that choice is yours, actually. I can keep releasing and you can choose not to try them out, how about that?
If you find an issue, mention the issue and not how fudged up it is! That would be a start. I'm just a human being, you know, not some sponge for punches.
Well, I think you've greatly misconceived my "punches". Honestly, I've always been been proud of my ability to see internet criticism as constructive, even if the dude's a jerk about it. I understand we're all different, so I should definitely remind myself of how hurtful my words can be...
So Im sorry for any of that. Any harshness was truly inadvertent.
I'd like to bring something to focus though. You spoke of "confirmations of defeat", but you're the first one to say anything of the sort. You who seem to be against competition, feel defeated by a quitter?