| |||
| |||
|
You are logged in as a guest. ( logon | register ) |
File Format Support Jump to page : 1 Now viewing page 1 [25 messages per page] | View previous thread :: View next thread |
reViSiT - Tracking Software for VST hosts -> Testing & Development | Message format |
chrisnash |
| ||||||
Developer Posts: 746 Location: England | One plan for v1.5 Pro, is to extend the number of file formats that reViSiT can import - for samples, instruments and songs. A major addition that has already been implemented, in this coming release, is MIDI file import. Use this poll to vote for other file formats you'd also like to see in reViSiT. reViSiT currently supports:
(* as well as importing individual samples/instruments from modules.) | ||||||
CS_TBL |
| ||||||
Expert Posts: 512 Location: Netherlands | How would this midi import work? You scan track 01 for the max polyphony and reserve that amount of channels in the pattern editor? Then scan track 02 for the max polyphony and reserve channels again? Or is everything mixed up? | ||||||
chrisnash |
| ||||||
Developer Posts: 746 Location: England | The first one: the code scans the whole MIDI file, works out how many tracker channels are needed per MIDI channel, then reserves them. Effectively, you're talking 64 note polyphony, but this will eventually become more like 64-voice multitimbrality, once multiple pitches per channel is coded. It's the time dimension that gets tricky - deciding what stretches of MIDI music to put in each pattern. The code tries to use all the key signature changes, time signature changes, etc. that it can find in the file, to define the boundaries, but otherwise tries to put music in groups of 4 bars. Some MIDI files are tidier than others, of course, so down the road I'll think about some features to help tidy up the MIDI bar to pattern mappings. Oh, and it's not "how would it work", it's "how does it work". I've already tested it against about 45,000 MIDI files - with very positive results! It should make light work of remixes - then, again, I'm not sure I wanted to make things easier, as then where's the challenge? | ||||||
CS_TBL |
| ||||||
Expert Posts: 512 Location: Netherlands | Multiple pitches per channel wouldn't solve everything, would it? Afaik each note in a midi file can have its own velocity, and currently - if you only add multiple pitches - chords share one volume entry. | ||||||
chrisnash |
| ||||||
Developer Posts: 746 Location: England | True, but in cases where velocities don't match I have the option of averaging the velocity or distributing them over multiple tracker channels. Anyway, that's an implementation issue, for when the time comes. | ||||||
fegi |
| ||||||
Veteran Posts: 102 Location: Austria | soundfont 2.0 support would be very, very awesome | ||||||
fegi |
| ||||||
Veteran Posts: 102 Location: Austria | any news regarding this? | ||||||
chrisnash |
| ||||||
Developer Posts: 746 Location: England | I was actually looking at the SF2 file format specification just the other day. Can't see any specific difficulties (the format is designed to allow programs to cherrypick the features it supports) - Creative still appear good at supporting developers (with sample code, test files, etc.). Also, the format itself is similar to that used by Microsoft's WAV files (RIFF), which reViSiT already supports. So, I will certainly be adding SF2 support. However, there are a number of other reViSiT features which must be completed first. So, for now, we'll call it a v2.0 feature. reViSiT v2.0 development ("Manhattan") is already underway, and there will be closed alpha and beta versions in the coming months, and public versions hopefully before the end of the year - but I can't yet say where SF2 support will fall in that timeframe. | ||||||
Jump to page : 1 Now viewing page 1 [25 messages per page] |
Search this forum Printer friendly version E-mail a link to this thread |
(Delete all cookies set by this site) | |