SLuiCe
New member
Whoa....sorry about the double post there. Site was lagging up when I posted that....

Guernica said:
In making a midi map, would that be the same as a click? I mean, can another midi device read and lock up with the sync off of the track, or would the person receiving have to program the midi file into the device..
Yeah, and some of us (read me) use standalone units instead of software so midi isn't as easy for us either.dobro said:My software will play MIDI, but I can't generate any.

) wouldn't always do it because clocks aren't perfect and I think sometimes you might get some variations in there.

LOLdrstawl said:Was his delete finger in a cast at the time?
![]()


Guernica said:
I believe it wouldnt necessarily have to be at the very begining either...... if it were at the third second, and everyone understood this, we would get the same results. .....If im wrong, somebody please correct me.
G
) told me that the MiniDisc algorithms work much better for compressing individual tracks than they do for entire mixes. Basically because an individual track tends to have a much more limited frequency and dynamic range than a whole song.
Re: sharing tempo infor with your collab partners when using midi, ... wouldnt the tempo info already be on the midi file? Again, If im understanding correctly, .....I believe that it would serve the same purpose as sending over the original r. track (the way we do things now)...... or sending over a click track. Only, with a midi file you would have the advantage of a quick lock up to other midi devices, and the ability to just send "parts" located anywhere in the song without the click way back at the beginning.....Cordura, jump in if im missing something. Is that right?.......wow...... aint that a bitch. So, anytime a person converts a .wav file to mp3 it adds a 786 sample delay? Are there any encoders available (LAME encoder, sam?) that dont do this?A note: Creating a MP3 file in most encoders creates a 786 sample delay...