I'm still mourning, ok?
Jud
@Jud
Best posts made by Jud
Latest posts made by Jud
-
RE: I already miss the old name
Alex,
It's not "what's in a name" in business, it's "it's all in a name".
Do you plan on responding to 6 pages of comments from your loyal readers?
-
RE: ID3v2
[quote user="Jud"]
It's too bad the site is down. The spec is really quite a treat.
If ANYONE can tell me what I'm supposed to do when the event type is 0xFF, I'll do a backflip and a cartwheel for you. Is it padding, just keep reading 0xFF until you hit a real value, or is some kind of chain implied? I can't figure this one out.
[/quote]
OK I think I got this. I think it's intended to take care of values over 0xFF, so if a future revision uses "0x100" it will be encoded as 0xFF 0x01. The SYTC frame uses this convention for BPM over 255.
Or I could be totally wrong.
-
RE: ID3v2
It's too bad the site is down. The spec is really quite a treat.
If ANYONE can tell me what I'm supposed to do when the event type is 0xFF, I'll do a backflip and a cartwheel for you. Is it padding, just keep reading 0xFF until you hit a real value, or is some kind of chain implied? I can't figure this one out.
[quote user="id3.org"]4.6. Event timing codes
This frame allows synchronisation with key events in a song or sound.
The header is:<Header for 'Event timing codes', ID: "ETCO">
Time stamp format $xxWhere time stamp format is:
$01 Absolute time, 32 bit sized, using MPEG [MPEG] frames as unit
$02 Absolute time, 32 bit sized, using milliseconds as unitAbolute time means that every stamp contains the time from the
beginning of the file.Followed by a list of key events in the following format:
Type of event $xx
Time stamp $xx (xx ...)The 'Time stamp' is set to zero if directly at the beginning of the
sound or after the previous event. All events should be sorted in
chronological order. The type of event is as follows:$00 padding (has no meaning)
$01 end of initial silence
$02 intro start
$03 mainpart start
$04 outro start
$05 outro end
$06 verse start
$07 refrain start
$08 interlude start
$09 theme start
$0A variation start
$0B key change
$0C time change
$0D momentary unwanted noise (Snap, Crackle & Pop)
$0E sustained noise
$0F sustained noise end
$10 intro end
$11 mainpart end
$12 verse end
$13 refrain end
$14 theme end$15-$DF reserved for future use
$E0-$EF not predefined sync 0-F
$F0-$FC reserved for future use
$FD audio end (start of silence)
$FE audio file ends
$FF one more byte of events follows (all the following bytes with
the value $FF have the same function)Terminating the start events such as "intro start" is not required.
The 'Not predefined sync's ($E0-EF) are for user events. You might
want to synchronise your music to something, like setting of an
explosion on-stage, turning on your screensaver etc.There may only be one "ETCO" frame in each tag.
[/quote]
-
ID3v2
Ever read the spec for this fun little toy? I'll quote a few of my favorites parts from http://www.id3.org/id3v2.3.0.txt.
"This flag indicates wether or not the frame is enrypted."
"$11 A bright coloured fish" (enumeration for picture type)
"$0D momentary unwanted noise (Snap, Crackle & Pop)"
It's all fun and games until someone loses a brightly coloured fish :( -
RE: C# - compiler WTF
[quote user="Tann San"]are there any performance differences between the language primitives and the framework implementations?[/quote]
No - it's a direct map.
-
RE: C# - compiler WTF
Luke, I was prepared to refute any explanation with "they're the same!", but, what you said does make sense. It still makes me sad I have to use ushort instead of UInt16.
-
RE: C# - compiler WTF
Anyway, if it doesn't make sense it doesn't make sense. I'm trying to use BCL types instead of language specific types in code and came across this one snag. Not a big deal, I can certainly use the language specific way, just made me scratch my head and go "WTF?". Hope someone enjoyed it :)
-
RE: C# - compiler WTF
[quote user="fluffy777"]It looks like enums in C# must derive from integral types to remain compatible with C++ and other legacy languages supported by the managed runtime. What's the WTF here?
[/quote]
OK, "byte" is just a language convenience. It's mapped to "System.Byte" (see tooltip). What's WTF is you are required to use the language specific form when creating an enum that inherits from any of the primitives.