The biggest change is selection + drag and drop support in the frame editor, so feedback on that is welcome.
This is great! Could you maybe modify it so that Shift+Click+Drag will automatically copy+paste (like the equivalent function in the pattern editor)?
Edit - Also, perhaps Ctrl+Click+Drag could also copy+paste, but use new pattern numbers (very much like a cross between 'duplicate frame' and 'new frame')? Not sure how anyone else feels about that one.
_______________________
The only things certain in life are death and uncertainty.
don't you think this deserves it's own topic, jsr?
There are only minor changes in this version so I was gonna release it without a beta at all if it wasn't for this thread. Though now I'm glad I did, I will fix the comments crash bug.
Necrophageon: Ctrl+drag should copy a selection now, but yeah I can move that to Shift+drag and assign Ctrl+drag to copy and paste to new pattern numbers.
Fezuke found a bug with the Sxx command. His FTM (which I attached) sounds fine in 0.4.1, but in 0.4.2b1, some notes immediately after S02 does not play.
EDIT: I only just took a closer look at the FTM, and realised S02 is useless on those rows because there isn't time for the mute to take effect (because it's already going at a rate of 2 frames per row), but still, I think it's worth mentioning. There could be a more dramatic bug hiding somewhere behind this one.
Or better yet, an external program that takes exported TXTs and turns THOSE into MML files. Because then you could use TXTs from NSFPlay once that gets implemented. :3
Sorry, this is very offtopic and probably not THAT related to making composing faster, but I don't want to create a new thread just for this...
Basically my idea is: Fixed duty/wave macros, and once they end, the channel gets set to whatever the last Vxx command was. (no previous Vxx = V00, or it continues to output the last value of the macro)
Maybe it could save making different instruments for every kind of "pluck" or "PWM" sound you want to use.
Or better yet, an external program that takes exported TXTs and turns THOSE into MML files. Because then you could use TXTs from NSFPlay once that gets implemented. :3
My thought exactly. I'm already working on such a tool for Renoise -> FTM conversion. Though I'm not sure if anyone will use it besides me.
Sorry, this is very offtopic and probably not THAT related to making composing faster, but I don't want to create a new thread just for this...
Basically my idea is: Fixed duty/wave macros, and once they end, the channel gets set to whatever the last Vxx command was. (no previous Vxx = V00, or it continues to output the last value of the macro)
Maybe it could save making different instruments for every kind of "pluck" or "PWM" sound you want to use.
It's more related than you might think, IMO. Currently, the last Vxx command IS saved, but it won't just take over on it's own when your macro ends, you have to either use an instrument without a pulse-width macro, or throw in another Vxx command. Macros take priority, so the latter option only works if there is no active macro when FT hits the Vxx command (example attached).
An option for "fixed" and "absolute" like arpeggios might be a quick fix, or it could just behave the way you're talking about normally and you'd have to loop the last step of the macro sequence to sustain the desired pulse-width.
Either way, it'd still shave off some time (and effect column usage) when doing this sort of thing.
_______________________
The only things certain in life are death and uncertainty.
Thanks, I fixed the crash bug. Both problems was related to playing notes with missing instrument numbers. That may happen when playing single rows, but that FDS file should initialize the instrument column when playing from start.
Necrophageon & za909: Changing that would break old behaviour, but I'll think about it.
Alright, that's why I mentioned a "fixed" duty macro. You could add it in the same manner as you did for arpeggios, so there would be no issues with backwards compatibility.
