Look promising. FamiTracker is GPL, however it isn't really a free software because it depends on non-free software. Your port will remedy to that situation.
Thanks for the "thanks"! It's nice to know people actually want this.
I've been thinking. My work on porting the FamiTracker source code has become more of a fork due to the drastic differences. Because of this, I'm not sure if I should keep the name "FamiTracker". What I have right now, aside from the core FamiTracker engine, is only a really good imitation of it.
I was actually thinking of just making a general purpose tracker with strict FamiTracker compatibility. I don't know what to call it yet.
What would everyone think about this?
However, when i move window into another desktop, Control Panel turns off spontaneously - it just disappears, and an option in menu View->Control Panel becomes unchecked. I'm using Awesome WM.
Good to hear it works!
I've gotten that myself sometimes. It's probably a Qt bug. For now, just turn it back on and forget about it.
PJ wrote:
Also, when window is too narrow and you can't see all five channels, there is no horizontal scrollbar.
Edit: I just noticed that there were some icons on the screenshots. I don't have any icons, there are just titles.
The horizontal scroll bar in the pattern view isn't fully implemented yet. I totally forgot about it.
The buttons will become text if Qt can't find your theme's icons. I plan to put in fallback icons later.
I think keeping the famitracker name would be appropriate if your fork were to only support .ftm files, but if functionality is added later down the road for other things (Whether that be conventional sample-based tracking or other sound chips), then I would certainly change the name.
It would probably make sense to keep it named "famitracker" given the similarities in the user interface (as it is now, at least.), but it's your choice really.
I think keeping the famitracker name would be appropriate if your fork were to only support .ftm files, but if functionality is added later down the road for other things (Whether that be conventional sample-based tracking or other sound chips), then I would certainly change the name.
It would probably make sense to keep it named "famitracker" given the similarities in the user interface (as it is now, at least.), but it's your choice really.
Yeah. If it's called FamiTracker, then I'm expected to copy every single solitary detail, which doesn't give me a lot of creative freedom. :/
I had this crazy idea of supporting all types of modules as their own separate thing (eg. FamiTracker, wavetable/oscillator instruments, possibly Gameboy), then connecting these modules with audio filters in post. If I wanted to do all of that, a name change would almost be compulsory.
Perhaps I'm overplanning what was going to be a simple FamiTracker port...
Something like "Octal Tracker" or "Octave Tracker" to emphasize the 8-bit origins, if you expand past FT features?
By the way, I'm really excited about this. I have a MacBook and wouldn't mind trying to compile when Jack support is in. (I'm pretty sure there's no OS X port of ALSA, but if I'm wrong then I could try it now.) FamiTracker is one of two programs currently binding me to Windows, the other being foobar2000.
Does GPL really allow you to change the name of the program? I think even if you do end up adding features, still FamiTracker should be somewhere in the title; rainwarrior's suggestion, "FamiTracker LX" is actually a pretty good one I think.
If I'm correct, the GPL does not require using the same name for derived works or any works that use it.
I've pretty much turned FamiTracker into a component of the main program, and is no longer the whole program. It'd be one component of possibly many. This is a big reason I have reservations to keeping the name.
On the other hand, people may have trouble identifying a Linux/Mac version of FamiTracker if I call it something else.
Using a name like FamiTracker LX wouldn't be a big deal, I suppose. I do have a question for rainwarrior: What does the LX stand for? Sixty?
I've always wondered about the licensing since MFC libraries aren't exactly what anyone can consider free software...
But yeah; GPL doesn't make it mandatory to name derivative works after the works their derived from, but if you choose GPL version 3, it requires that all derivatives & deriving sources follow the same license (so that no non-free derivatives are made using GPLed code).
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
The MFC libraries are not included with Famitracker's source. There's no conflict there, I don't think. (I'm not 100% sure on that, though.)
Edit: Okay, I looked it up. Under some interpretations MFC is acceptable under GPL's provisions for "system libraries", since the library is included with the Visual Studio compiler, and not something you are simply withholding from the source. (The compiler itself isn't free, but that's not a requirement of the GPL.)
Just one thought, I've done some work with wxWidgets in the past and it seemed very similar to MFC. I wonder if that wouldn't be faster to use when porting?
Under some interpretations MFC is acceptable under GPL's provisions for "system libraries", since the library is included with the Visual Studio compiler, and not something you are simply withholding from the source.
Ah; good call. I had to double-check the license myself (if only it were as simple as the MIT license). :P
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
) 