|
And tomorrow we reveal the Predator's real name!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Chinggis wrote: I am the punishment of God. If you had not committed great sins, God would not have sent a punishment like me upon you.
--Predator and protector and servant of the Lord of the Universe.
|
|
|
|
|
So good, they named a vodka after him!
Chinggis (vodka) - Wikipedia[^]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Sorry Greg,
With my current schedule I can't guarantee my availability at 0900 GMT+1 so I had to pass on being the Setter. I'm surprised it wasn't solved.
You should have set an anagram! Those are solved quickly!
|
|
|
|
|
Greg, I predict you will be "Oi'd" tomorrow morning before you are out of bed
|
|
|
|
|
Prophecy is a strange thing: it only works if you tell no one ...
The Lounge[^]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
vessel for French supertonic to mediant mixture (9)
|
|
|
|
|
Antidote ?
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
|
Don't hold out much hope for this one ...
Greg Utas wrote: vessel for French supertonic to mediant mixture (9)
supertonic (in what I believe is a French notation) would be Re (Do-Re-Mi)
Mix it with mediant - anagram = dermatine which is a name for the skin, which is, sort of, a vessel.
If I'm right, shoot us both.
|
|
|
|
|
No one gets shot.
|
|
|
|
|
|
|
My work here is (badly) done.
|
|
|
|
|
|
|
I keep coming back to Champagne but the vessel part is throwing me off.
To err is human to really elephant it up you need a computer
|
|
|
|
|
I get to bouteille as a French vessel for wine or perfume and is 9 letters, but that has nothing to do with a musical third note (mediant) which I'm assuming is part of an anagram that I can't decipher. So in other words - I'm stuck
|
|
|
|
|
@GregUtas
Where's the CCC?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
He's struggling with ambisinistry.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
|
I'm working on complicated MIDI wizardry for IoT gadgets, so I can make MIDI "smart" pedals and controllers and such.
Playing a multitrack MIDI file without reading it into memory is a bear.
I have just not been able to get this code right.
The trouble is each midi event has a delta attached to it that is the offset in "MIDI ticks"* from the previous event.
*A midi tick is a fixed time duration based on the tempo and timebase.
With a multitrack midi file, each track has its own sequence of events and the deltas are all relative to that track.
However, in order to play them, you must merge all the tracks into one event stream, adjusting the deltas.
The actual adjusting of the deltas isn't so bad, but the logic to figure out when to pull from what track - I'm not even sure I have it right yet, because my code has other issues.
My point in all this, is MIDI is early 1980s protocol and multitrack midi isn't exactly brand spanking new. Sequencers with scant amounts of RAM were doing this.
I feel like in so many ways MIDI was designed to make it possible to do things on little devices without much RAM.
But this particular operation - in C# I just merged the tracks in memory before I played them. I can't afford the RAM or the CPU to do that here. I have to stream everything.
And I've convinced myself I'm overcomplicating things.
I hate when I do that - it means I have tunnel vision, and/or am missing something big and important.
I don't like knowing that I don't know something I need to know, you know? It bugs me, like a song that's stuck in my head I can't remember the entire hook to.
To err is human. Fortune favors the monsters.
|
|
|
|
|
honey the codewitch wrote: However, in order to play them, you must merge all the tracks into one event stream, adjusting the deltas. Why? Why not have a 'pre-stream' of events that are the absolute times of next 'event' of each track? Then you just keep polling the track with the next playable event until its 'time' falls behind the next track with an upcoming playable event. Poll that one until ...
|
|
|
|
|
That's what I do essentially as far as the deltas. My pre stream is n contexts where n is the number of tracks. I use those to pull events out in the right order
To err is human. Fortune favors the monsters.
|
|
|
|
|
Isn't this effectively a merge sort from N sources.
Each source is already sorted. I admit my ignorance in how you calculate your context.
But I assume that EITHER you have an incoming stream of N contexts pre-sorted (which would make outputting it more trivial as you output it in the order it arrives).
Or you have an incoming stream with N tracks, where each track is at a specific offset, but the magic is that while track 1 has a small delta, track 3 could have an excessively large delta, so it is played at the right time. And you might not hear from track 3 for some time.
I often find it helpful to imagine how they implemented the player at the hardware level.
For my take, I would write something that played only 1 of N contexts correctly...
Then I would look hard at how to implement simply adding a second context to that. Based on how the data shows up.
Because by the time you get to the third or fourth, I think you usually have a decent approach.
The other comparison I would make is a Multiplexer. is this similar to CDM or TDM (Code or Time division Multiplexing).
Another comparison is Stereo, where you get L+R and a 2L (I forget the actual), but taking -2L + L+R => -L+R + L+R = 2R
But they did it that way to take advantage of simpler hardware.
I remember learning from that example that coding stuff versus building components you have to think differently about what is easy/hard.
==
Finally, your problem reminds me of a Computer Engineering Class, where we built circuits that were run through a simulator. The simulator used a queue design, where "events" would trigger through the queue, and the simulator was able to be fast, because it ignored the timing signals, allowing it to "not wait" any time before processing an item. (I got in trouble in the class, because I wrote obscenely inefficient but SIMPLE code, reducing the homework to a TRIVIAL problem, avoiding the timing issues others were busy coding around).
anyways, I could envision a queue that is managing N queues of inputs, and only when you take off an item, do you go to the stream to pull in another item.
|
|
|
|