Mod Archive Forums Mod Archive Forums
Advanced search  


Please note: Your main account will not work here, you must create a forum account to post on the forums.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - DasKreestof

Pages: 1 2 3 4 [5] 6
MilkyTracker Community / Re: MilkyTracker Wikipedia Entry
« on: January 27, 2009, 18:57:44 »
I've edited the page again. Hopefully it will stave off commercial interests in having the page killed again.

Having more reference pages would certainly help stave off the critics.  Who's in charge of posting pages on the Mod Archive pages?  What's the process?

BTW: I'm nearly finished with the Operations Manual skeleton, and it's partly fleshed out as well.

I appreciate your suggestion Klez. When a MilkyTracker wiki does come to be, I do hope that a downloadable db is also available.

It sounds like a tricky feat. Here's why:
1. Wiki's I believe are usually run as SQL or MySQL server backends to a PHP or Asp front end.  That means that the db backup would likely have to be done offline for it to be done simply. A live sql server can be backed up while it's online, but in my experience that frequently requires costly applications. (Granted my SQL experience is limited.)

2. Wiki's that have downloadable backups of the database that are regularly created for end users to download tend to be rare in my experience. (Wikipedia does allow you to download theirs)

3. Converting said DB to a format presentable as standalone documentation may frequently be an incredible and time consuming feat.

4. I never know that a wiki might or is going to vanish until it is too late.  This is why it's incredibly ideal to have a document/manual that is included with software package.  Years later, the manual is still located in the download or extraction of the program, easy to find and not requiring hours of labor to answer the simple question of "How porous paste works" or something.

See here's the thing. I'm old and I'm stubborn. I will use a software package from 15 or even 25 years ago. (I recently replayed Zork)  I don't know if you've ever tried to find info or documentation about software from 10+ years ago, but trust me, it's usually vanished off the face of the earth.  The company is usually gone, and if it's not, anyone familiar with that product usually is. The answer you'll get is "buy the new supported product" regardless of whether it performs some obscure function of the old product that's made you keep it around, and regardless of whether it's compatible with the rest of your operating environment.

I'll restate: I like wiki's. I really do. But as a computer scientist/engineer I've came up with a saying: "Never put a computer in a position where a light switch would do." It's a way of illustrating the concept of KISS or (Keep it Simple stupid!) A small efficient html or even a bloated pdf is a fantastic resource to include with the Milkytracker package.  It's viewable on a PocketPC (which I use Milkytracker on) and by having a copy I know I can read it as long as I have something that will run milkytracker, regardless of whether I have Internet access or if the wiki still exists.

Wiki editing might be more inviting to geeks, but it's also harder and requires learning another code base.  The method I suggested above requires only simple document editing abilities, to later be cleaned up by someone and parsed into an efficient document. It also doesn't require anyone to learn how to build a wiki server and can be done quickly and easily.

Putting my money (or in this case time) where my mouth is: I have started the skeleton document and should be able to upload it in the near future. I have taken most of the screen captures necessary from the PC version, filled out a rough structure, and even filled in some parts already.  At current the skeleton document is a word document at 790kb. It's bloated but simple to work with at current.  I will convert it to html, and parse it down to HTML 3 standards for very simple and easy to manipulate code.  This will make it easier for Raina to convert to a CSS style addition or addendum to the manual later.
It is likely that in it's work phase we'll keep in the .doc format because most people can read and write that format and it's relatively easy to convert from that format to one that is more ideal for distribution of a read only document. (less people can edit an html or pdf document than a .doc)
I think raina had a good idea about breaking the document into smaller parts for updating. It may prevent people from doing overlapping work, and by breaking it into smaller steps it might make the job seem more appealing and less taunting to contributors.

I don't know what the ideal way is to crowdsource working on the document is. I appreciate the fact that a wiki would be the easiest way. But this is something we can get done now, and will have the advantages outlined above.  If I had a public IP I would donate a server to the cause. But I don't :(

BTW: If there's a simple way to convert/view/reformat wiki databases on a desktop and pocketpc, I'd love to here about it! :)

I have a bunch of instant messengers, but honestly I only log in to them a few times a year. Email is the best bet. Send me an email at misterfun at optonline dot net and I'll send you a reply from my real email address.

There are a lot of pros and cons to wikis. I'm obviously a fan of them since I joined the forum to ask people help flesh out the resurrected Milkytracker entry I added to wikipedia.

The biggest pro is that it might encourage crowdsourcing the work in a way that no other method will. It's also nice that it can help BS the work as you put it.

The biggest downside IMHO is the lack of portability.  This affects me in two ways. One, I can't access it when I need it when I'm offline. (and that's frequent) Two, that the wiki won't be around forever.  I have a lot of trouble getting information about equipment and software that I got 10 years ago that only had information online in a fashion that wasn't downloadable.  I have seen wikis vanish after mere months, and sometimes they were the only source of info. (example: an IPTV show on electronics, put all the show notes and schematics on in their wiki. I still have the shows, but their wiki is gone making the show projects impossible.)

I suppose someone could copy and paste all the wiki articles into a single downloadable document, but obviously that's a lot of work to assign to someone.

I don't know how to setup a wiki server, but I do know how to put together a document.
I love Milkytracker. I want to contribute to it. If it had been programmed in BASIC on an Apple IIe I'd be all over it's source code.  But since it's written in C and my C skills are only slightly above null, the way I can contribute is I can help flesh out more documentation.
I've started a skeleton document, sort of like a FAQ with sections to be filled in later.  I will plagerize the FAQ and some threads for some info, and when I think it's in a non-embarassing form I'll either upload here or send it to you.
My suggestion from there is: We break it down into tiny sections that people can download/fill out-expand upon/and then send back.
You as the maintainer of the official manual can then decide whether to include the new chapters in the official manual or keep them as an addendum.

I am hoping that I actually get this done and all of this isn't a bunch of talk and promise!

I was going to mention this on another thread, and I suppose it deserves it's own thread, but I'm going to mention it here anyway.

I am very grateful that Milkytracker has the amount of documentation that it has. It really has a lot for a free program in such a niche market. I respect the tremendous amount of work that has gone into creating and maintaining that documentation.

That said: As one can deduce from the forums, sometimes the documentation is lacking. Obviously someone has considered crowdsourcing to expand the documentation through a wiki.  I love wiki's but the downside of a wiki is that I can't keep the wiki on my PDA and read it on the airplane. (I was excited to be using Milkytracker on a plane this weekend)

In leau of a wiki, perhaps a skeleton document could be created, one that could be uploaded to the site. Crowdsource contributors could copy and paste updated sections to this site or perhaps mail contributions to a gmail address. Then you as the official maintainer of the manual could update the official manual through copy and pasting.  If that idea is bad, it could be a manual addendum.

I realize that this only works if people actually contribute. I realize that's rare, and that talk is cheap. There's a big difference between wanting to volunteer, and uploading finished work.  I know I would like to help. But I also know that I am frequently over reaching the limits of what my schedule will allow.

Anyway, what I would add to the manual is:
A chapter listing the differences between the Pocket PC version and the full version. (which isn't many)
A chapter broken down by section of each page of Milkytracker. Each section documenting all features of each page.
I realize this is a huge job, and will create a huge manual. But if the crowd steps up to the job, it's becomes a much easier task.  It will also allow many questions about undocumented features to be answered with RTFM!

Does this make sense?
For example - The boost function doesn't just boost the amplitude of a waveform, it also alters it's EQ right?  This kind of documentation of a feature can result in creativity. (I believe I learned about that in one of the tutorial videos.)

If you think this is a good idea, perhaps I will start on creating a skeleton addendum document. That way my idea is a way of volunteering you to do more work.

Bug Report Archive / Re: Possible bugs in Milkytracker 0.90.80
« on: December 11, 2008, 01:29:22 »
Luckily the third issue is easy to work around.
I'm also a milkyplay user and you're right it doesn't exhibit the same issue. As you point out it's a different beast and by it's nature as an always ready to go audio app, this minor issue probably can't be resolved in Milkytracker.

Someone should definitely donate an iPhone to pailes regardless.

Here's what I've thought of towards that end, and remember- I don't know what I'm talking about: I believe the only way to install apps on the iPhone legally is to do so through the Apple apps store, which is probably iTunes related(see I don't know).  I have a feeling that apples won't release free applications through their apps store because: a) there's no profit for them to get a cut of, and b) there's no profit to pay for their peer review process.

So why not charge a dollar for it?  : I don't know if the current Gnu License that Milkytracker is release under would allow that. But like I said, I have no idea what I'm talking about, I could be totally wrong about everything I've just said.

Either way, I have a pocketpc already, and I love it, because it has Milkytracker.

Now I want to buy a keyboard for it. Anyone have any keyboard recommendations for pocketpc?  I don't think the one that pailes has is made anymore. I've bid on a few on ebay but they're pricey.  (maybe there's the only ones worth getting though?)

I can't tell you about what others are using but I can tell you what I'm using.
IPAQ 2750 running Windows Mobil 2003 Second edition
Processor PXa270 Memory 128MB
Milkytracker runs off my SD 2gb card.
I bought the IPaq used off craigslist.

I haven't used a keyboard with the Ipaq so I don't know how much that augments Milkytracker.  It would be worth it if I could for example use the CTRL-I function in Milkytracker on the PocketPC

Milkytracker is really amazing on the PocketPC.
I use it as my main sequencer and audio editor on the PocketPC.
I also use the demo version of AudioBox to add reverb to samples or create synth sounds remotely.  Obviously it's easier to do that with a full PC, but when all you've got is your pocketpc...
Another neat audio package is Syntrax. It has a unique synthesis paradigm.  You can export to wav and load it into milkytracker. It's free.
Griff is a full mobile studio, but the demo version was buggy on my PocketPC so I never got into it.

One of the primary advantages of Milkytracker is that is cross-platform. Milkytracker is the reason I don't ever want switch to an iphone or smartphone that wouldn't run Milkytracker. (for example, most smart phones don't have touch screens) Someday when they stop making pocketpcs, I'll buy a bunch of them on ebay so that I won't ever have to live without it.  It's amazing to have so much power in pocket. It's more powerful than all the music equipment I owned combined 15 years ago.

Tracking is fun. It's different then other composition forms but it quickly becomes very intuitive.  There are limits to the mod tracking paradigm, such as no pitch envelope, but you learn ways around that: pitch bend fx in the track data.

If you want a music studio in your pocket, I totally recommend picking up a pocketpc.  It's not as full featured as a laptop, but a laptop won't fit in your pocket nor start in 1 second.

Bug Report Archive / Re: Possible bugs in Milkytracker 0.90.80
« on: December 08, 2008, 05:43:40 »
The problems were unique to the PocketPC version.
Thank you very much for fixing them.  I look forward to the next release!

Bug Report Archive / [fixed] Possible bugs in Milkytracker 0.90.80
« on: December 06, 2008, 18:22:08 »
1. In the instrument editor, the swap function is unresponsive.  From that screen I am unable to select instruments or samples, but the cancel button does function and allows me to move back. I went back and checked it in version 0.90.60 and it worked OK. Put 0.90.80 back in and got the same results. :(

2. From the instrument editor, if using the internal browser, if you select save instrument the result is difficult to describe.  Part of the windows is overdrawn with the contents of the internal browser window, but the rest of the window is not. (ie other buttons and control) What is displayed is what's actually shown on the screen, so pressing on an empty space on the lower right hand side will provide you with an exit function, etc. 
What is on the screen is an instrument list, sample list, keyboard in the middle with a keypad and some remnants of whatever wasn't drawn over in the lower half of the screen.  When exiting this screen, the screen displayed is not the one you're interacting with. If you change screens a few times, you will eventually see the screen you're interacting with.
When I went back to version 0.90.60 I believe I replicated the error using the internal browser.
The workaround is to use the external browser, but of course that does not allow the selection of deeper subfolders.

3. And this is no big deal. If I have milkytracker running, and turn of my PocketPC, when I turn it back on Milkytracker won't play.  I assume this is a Windows Mobile audio driver issue.  The obvious workaround is to close milkytracker everytime I shutdown the pocket PC for a few minutes to save power.

I have deleted and recreated my milkytracker config file to see if that would fix the problem.

I LOVE Milkytracker. Because of it I don't ever want to live without a PocketPC again.

Information about my environment in case that helps.

IPAQ 2750 running Windows Mobil 2003 Second edition
Processor PXa270 Memory 128MB || 4.60mb storage free, 16.87 program free.
Milkytracker runs off my SD card. The SD card has 6.13 megabyte free
Only other program running is File Explorer.

Pages: 1 2 3 4 [5] 6