![]() Cosmetically I dimmed the LEDs so you get less noise from boards while working. We'll see if it works using the stuff I've got. It looks like I might actually be able to implement detection of which revision the chip is using some adapted code from the Commodore 64. I fixed the Atari 2600 initialization and also detect both SID revisions (6581/8580) as the same kind of board for now. Definitely need zap, config, instrument and board subscreens.Īnyway, let's cull the changelog from last week: I'll definitely have an import feature at one point or another to pull in projects. I haven't decided whether I want to relocate Disk Operations into a Disk op or leave Load/Save outside. I do like how most trackers let you click on a position in the order to jump to editing/playing it, so I implemented that. ![]() I probably won't have scopes but you'll be able to mute the channels using the channel header, near where you reassign things. FT2 and Milky relocated Noisetracker's channel mute to just clicking on the scopes. There are a lot of things I care about and a lot of things I plan to relocate. Milkytracker, an FT2 clone by demogroup TiTAN Noisetracker, quite possibly FT2's inspiration It's pretty lonely up there, but I'm sure it'll get better with time. I realised I don't have any, so I tore up some UI code I wrote ten years ago and put the beginnings of a button cluster in. You also have to be able to click buttons. For the time being, I'm just calling out to Tk, but eventually I hope to put a file selector in the tracker itself. To be able to load and save, you gotta have file dialogs. Shift-Ctrl-Alt Left+Right move between songs that are open and you can have multiple files open at once. As a side bonus, I cleaned up the way songs were initialized some as a direct result of the load/save routines. I think adopting a system similar to how FamiTracker handles WAV exporting would greatly improve Deflemask's user experience.Failed at getting my recap in over the weekend, because I was working hard on a new feature for the tracker: Load! And it's got a co-conspirator as well: Save! That means I'm officially at a non-negative version number, because I don't want to deal with storing negative values where I store the version of CTM that wrote the file in the tracker file. In my opinion, this is highly inefficient, and becomes a serious problem when doing multi-channel exporting for mixing or oscilloscope rendering, since even short songs take about a minute to fully export, forcing me to spend 10 minutes on exporting the channels of a single song, time I could be spending on more productive work. This slows down the exporting process significantly, since the user can no longer step away while the song is exporting, and the program has to take time graphically displaying the pattern editor so that the user knows when to stop. In Deflemask, however, there is no such menu, so the user must stop the export manually. In FamiTracker, my usual tracker program, exporting is an extremely quick process after a brief menu where you input how long you want the exported file to be and which channels you want to include, the program handles all of the actual exporting. Although I'm enjoying most of the program's features, I feel like the WAV export function could use some improvements. I've been using Deflemask a lot recently for YM2612+SN7 music.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |