Search options (Page 34 of 39)

@ stancoolness

God.. close that pointless "website" down already. It serves no purpose except gather up about 0.2% of the links people already can find, better organized, on other more popular websites made by people who know more than you. We get it, the chip music bandwagon recently happened to roll through your hamlet so now you decided to hit the road and join the circus. Your attitude is also shit. So meh...

That will do just fine. Paint won't ever scratch off.

Space Travel Device*

Works fine now, but up to r1219 it didn't work for me for some reasons. I tested on two computers and it was the same on both, strangely.

It is indeed the same volume now, but I am not convinced this was the right way to go however. I made a few quick tests and any two instruments (or two notes of the same instrument) at default volume played at the same time will distort. Using a full volume wave + oscillator in the same instrument will distort. And using just a single oscillator in an instrument with a volume above 80 will also distort, get really noticeable around D0.

It's kind of fun to be able to explore distortion right from the instrument, but in terms of constructing songs it means that for every new channel added you need to edit every instrument's volume down a good notch to avoid distortion, or bring down the master volume of the song. In the end, since that distortion is based solely on sheer volume output, it's not possible to use it as an effect and mix distorted and non distorted sounds together.

The added distortion also changes the nature of the filter a lot. A fully high passed (7FF) noise at default volume (80) for example doesn't "fade" like it should, it enters this noisy weird place where low freqs creep back in the sound because of the distortion. Really noticeable on sweeps.

Overall, I think the best way to go about this would be to bring down the wave volume to what oscillators used to be. Because those waves had all of the aforementioned distortion problems in the first place. It's simply too loud and doesn't sum properly in the mix stage. If you do bring the volume down, I would suggest limiting how loud a wave can be to the same as an oscillator, and do a vertical zoom on the waveform in the editor, otherwise it's much much too small to free hand edit them.

So yeah. I'd revert that change and just tweak the waves instead.

Woots!

Yay!

This should probably be a toggle option IMO. It can be useful in a lot of cases, but for any instrument that doesn't use a release phase, simply a decay. it makes it impossible to properly jam with them and hear what they'd sound like in the song (where they wouldn't be any note-off events) unless you hold every key down.

This.

And this.

When i joined, I submitted a few pieces of music (and at the risk of sounding a bit pretentious, I think I make pretty decent quality music). They disappeared from the front page with not even a listen while total pieces of garbage (harsh? yes, but true) got five star two thumbs up FDA-approved intel inside deluxe ninja from hell with tacos made of midgets juggling pure balls of awesome. Then I realized people listen to music here solely based on whether or not their friends or some revered semi-mythical composer made it, then congratulate the everlasting fuck out of each other for having put all of 11 minutes into four and a half bleeps of questionable musical pupose.

So yeah.. I just removed my tracks and realized this was not a community for actual *music* discussion as much as it is a place to share a common interest/appreciation for the art. Threads for musical criticism get barely 2-3 posts. Most of what I see is either "general discussion" type stuff, or threads that are just announcements for finished products like EPs and Albums. It's not a bad thing, don't get me wrong. But I guess I was just expecting something different and that's my probably fault.

But yeah... I just stay away from the negative threads. Once I see one is going to go to hell, I don't even read it anymore... like that 8 page trainwreck that got closed recently.

Critical as in showstopper, no not really.

But there's a lot of little problems with the editing flow and a ton of grievances with the sound. I think part of the problem is the intention to keep Klystrack oldschoolier-than-thou with super low resolution settings, low-impact replay routines and small-size files. IMO it should be thought of as a music software first and not a demoscene utility.

In any case, here's my list of bugs and suggestions:

Bugs/Grievances:
- CTRL-DEL on a pattern while the song plays doesn't just delete the pattern data, it stops the song and places you back at the top of the sequence for no reason.
- Sometimes Loop From Current position just stops working and just plays the last row in a pattern in a loop instead of the whole pattern.
- Cannot copy the 64th row of a pattern in the buffer
- Sometimes the envelopes stop working properly if an instrument plays for too long and you get clicks everywhere instead of smooth fade-to-0
- Metal Sync noise is out of pitch with other oscillators and there's no fine tuning to bring it back in place, making it unusable for melodies.
- Waves (loaded or generated) are about 700 times louder than the oscillators, making them almost impossible to mix in. The volume control offered in the wave editor has two presets: way the fuck too loud at 100%, and way the fuck too loud at 25%.
- No protracker-style delete in the sequence editor constantly shifts your song's structure. (yes I know.. there's another button to do that.. but I don't see the reason why delete should act like that when backspace does pretty much the same)
- Cannot cycle around in the sequence editor, so if you're on channel 12 and you wanna go back to 1, you have to press left (or shift-tab in my case) 24 times in AHX edit mode.
- Cannot use copy/paste across channels either in the pattern or sequence editor. It would be nice to be able to select a nice block that spans more than one channel instead of copy/pasting the same block in each.
- MIDI note off messages trigger the note again so you play each note twice when using a midi controller

Suggestions I think are easy to implement:
- Extended CTR-K/CTRL-U functionalities would be appreciated, like clone all channels, or insert new patterns across all channels.
- Need zap functions to neatly delete unused patterns, or just kill all instruments, or all pattern data etc.
- Make it possible to name, and save/load FX presets
- Put KILL buttons inside the inst/wave editor interfaces instead of having them way the hell up there in the menu
- Independent noise pitch to be able to mix 'thin' noise in bass instrument. At the moment its only possible when mixing it in with a wave and it's not quite possible to get a clear oscillator (except a sine that's too loud) in the wave editor.
- Include all possible oscillator shapes in the wave generator.
- A song timer
- Highlight currently selected instrument in the patterns to quickly locate where an instrument is used.

Suggestions that I know most of the code is already there, but would definitely require more work:
- Dynamic pitch/volume adjustment in the wave editor (select target pitch/volume, and press apply)
- Filter functions in the wave editor to permanently apply filtering to a wave

Suggestions that most likely require a lot of work:
- A Live screen where the you can set up tempo-synced mutes/unmutes, loop/unloop to be able to play around with the tracks in a live environement.
- Wav export channels so people can route different instrument to different channels so you can export stuff independently and mix/master the results in a DAW.
- FM synthesis, something like Genesis-level of FM (4ops I think?) would be enough. No need to go all DX1 there.
- Distortion / Waveshaper unit in the FX section
- At least two more FX bus
- Rework the chorus because it adds a LOT of clicking noise to a sound, also separate depth mod and pitch mod.
- Proper midi support for input and output so I don't get a week of lag with my midi controller, and so people can use KT as sequencer for external machines. Maybe look into ASIO to reduce the buffer to a more usable size.
- Add separate panning positions for every tap in the reverb/delay unit

Essential you-should-listen-to-n00bstar-because-of-reasons stuff:
- Clean the code, comment it, make it run off a single codebase, and make it easier for other coders to come in and participate.
- Make a proper website to showcase the software, with a paypal button, and a community voting system on what needs to be fixed/implemented next.

I know I'm asking for a whole damn lot. But IMO this would take Klystrack out of the weird place it is right now,being mostly unheard of by most chip artists, and place it riiiiight at the top of the list for people who want a serious complete chiptracker that has the perfect balance between having all the functionalities you could want, without having it become yet another stupid semi-daw modular-ish vst-something-or-other software.

And now you know why Kometbomb probably sacrifices a kitten to the dark gods every night in the hope I die a horrible fiery death.