~ OPENSOURCE USB CARTRIGE DEVELOPMENT ~

LocalH · Post by **LocalH** » Tue Feb 05, 2008 4:43 pm

It's not a native XM player, it's an XM to SMPS converter.

TmEE co.(TM) · Post by **TmEE co.(TM)** » Tue Feb 05, 2008 5:39 pm

Why hasn't anyone made a SMPS tracker yet ? I'd add a SMPS exporting option to my tracker, BUT I need clear and detailed info on the SMPS format and I haven't found any.

LocalH · Post by **LocalH** » Wed Feb 06, 2008 6:23 am

Does this help?

TmEE co.(TM) · Post by **TmEE co.(TM)** » Wed Feb 06, 2008 7:48 pm

Something in such format would be much more helpful :

Code: Select all

TµEE co.(TM) Music File (TMF) format specification


TMF 0.1 specs are removed form this file. MDT still accepts the old format
but converts it to new format once you save the file.


TMF 0.2 Header (128 bytes):
1.  ID      - 16 - "TµEE co.(TM) TMF" - File identifier
2.  Type    - 4  - "MDM "       - Mega Drive Music
3.  Version - 2  - 0002h        - Version; L=minor, H=major, Little Endian
4.  Title   - 32 - "This is the title of the song  "
5.  Author  - 32 - "Author of the song             "
6.  Notes   - 30 - "Put here anything you like..."
7.  Date    - 10 - "01-02-2007" - Date
8.  Speed   - 1  - 00h...FFh    - Song speed (49.4Hz)
9.  Song l. - 1  - 00h...FFh    - Song lenght (in orders)

Number of patterns on channel n (7 bytes)
10. NoPttrn - 7  - 00h...FFh - Number of patterns

Default instruments (5 bytes)
11. ChInstr - 5  - 00h...7Fh

Default volumes (5 bytes)
12. ChVols  - 5  - 00h...7Fh

Default pans (5 bytes)
13. ChPans  - 5  - 00h...7Fh

Default reverbs (5 bytes) (ignored on MD)
14. ChRevs  - 5  - 00h...7Fh

Custom looping point
15. LoopRow - 1  - 00h...FFh

Absolutely nothing, maybe used for hidden data, expansions...
16. Nothing - 100 - 00h

Order table (1792 bytes)
17. ChOrder - 256 bytes for each of 7 order tables.
    Each byte represents an entry to channels pattern table

Channel n patterns (Lenght = (NoPttrn(n) * 256) bytes), always starts
after the 2048th byte.

Channel 0 to 4 (FM)
18. NoteData - 4 - 00h...09h, 00h...0Eh, 00h...7Fh, 00h...7Fh
    1st byte - NoNote(00h), Note(01h...0Dh), NoteOff(0Eh)
    2nd byte - Octave(00h...07h)
    3rd byte - Effect code
    4th byte - Effect value
...
Channel 5 (PCM)
18. NoteData - 4 - 00h...7Fh, 00h...7Fh, 00h, 00h
    1st byte - MIDI instrument 1 (00h...7Fh)
    2nd byte - MIDI instrument 2 (00h...7Fh)
    3rd byte - Unused
    4th byte - Unused

Channel 6 to 8 (PSG)
18. 1st byte - PSG channel 0 - MIDI note (2Dh...5Fh)
    2nd byte - PSG channel 0 - Note volume (0h...10h)
    3rd byte - PSG channel 1 - MIDI note (2Dh...5Fh)
    4th byte - PSG channel 1 - Note volume (0h...10h)

    1st byte - PSG channel 2 - MIDI note (2Dh...5Fh)
    2nd byte - PSG channel 2 - Note volume (0h...10h)
    3rd byte - Unused
    4th byte - Unused




MIDI note = ((Octave * 12) + Note) - 1

Effects

*** This field will be completed when the tracker gets beta ***
Feel free to tell me how these should be

00 - NO EFFECT
01 - Set channel volume
02 - Set pan position
03 - Volume up
04 - Volume down
05 - Volume slide up
06 - Volume slide down
09 - Random panning
0B - Pattern break
0D - Jump to order
0E - Change instrument
0F - Change speed
10 - Change MIDI bank



TµEE co.(TM) YM2612 instrument file format specification.

Each file is 32 bytes long, containing data for straightforward loading
into YM2612 registers - very little code reqired to load an instrument.

Each entry except 8 (and 9) are for all four operators.

1. DT/MUL  - 4 - Detune(D6...D4) and multiplicator(D3...D0) value
2. TL      - 4 - Total level (D6...D0)
3. RS/AR   - 4 - Rate scaling(D7, D6) and Attack rate (D4...D0)
4. AM/DR   - 4 - AM enable(D7)(ignored ATM) and Decay rate (D4...D0)
5. SR      - 4 - Sustain rate (D4...D0)
6. SL/RR   - 4 - Sustain level (D7...D4) and Release rate (D3...D0)
7. SSG-EG  - 4 - SSG-EG value (D3...D0)
8. FB/ALGO - 1 - Feedback (D5...D3) and algorithm (D2...D0)
9. STRING  - 3 - "TYI", ignored, for padding and optimization ;)

File extension should be TYI (Tiido's YM2612 Instrument file)

tinctu · Post by **tinctu** » Sat Feb 09, 2008 8:37 am

tinctu · Post by **tinctu** » Sun Feb 17, 2008 12:52 pm

Is "Molehill" good name for cart???

Christuserloeser · Post by **Christuserloeser** » Sun Feb 17, 2008 3:43 pm

"Molehill"... - I like it!

xenepp · Post by **xenepp** » Sun Feb 24, 2008 10:46 pm

Hasn't this gone a little off target?

I think a simple SD reader dev would suffice for now.

-Joel

Jorge Nuno · Post by **Jorge Nuno** » Sun Feb 24, 2008 11:22 pm

A simple SD reader is not that simple, because it's slow and you have to navigate through the FAT filesystem... but now I've been busy with my MD program... and the lectures start tomorrow, which means very litle time for this

xenepp · Post by **xenepp** » Sun Feb 24, 2008 11:34 pm

A simple SD reader is not that simple, because it's slow and you have to navigate through the FAT filesystem

I should think simpler than implimenting MIDI and USB.

Be great if someone can carry this on, I've looked into it but just have no idea what I'm doing.

-Joel

Jorge Nuno · Post by **Jorge Nuno** » Sun Feb 24, 2008 11:55 pm

Well for the USB support I sugested a retail USB card reader, mounted inside the cart... For the MIDI support, I have nothing to say...

tinctu · Post by **tinctu** » Wed Feb 27, 2008 6:18 am

OK OK
NO MIDI

Chilly Willy · Post by **Chilly Willy** » Wed Feb 27, 2008 9:16 pm

Looks nice, but you might be able to save some space by putting the ram slot on the back of the cart. Also, you should be able to do the USB from the FPGA, thus eliminating the PIC.

tinctu · Post by **tinctu** » Mon Mar 10, 2008 1:55 pm

OK I will:

- make new "molehill" logo
- redraw concept -> V6
- make 3d case visualization [BLENDER3D]

tinctu · Post by **tinctu** » Tue Aug 12, 2008 8:12 pm

Well I am still ready to do DIY casing for cart...
Transparent...
But I am not good at PCB...