SynthModules

Has anyone established standards or guidelines for uploading programs?

I wanted a real time clock in my MIDI input and ouput code so I could
do timestamps.  I used the timer interrupt methodology in
syncable.bas and adapted it to keep a 1mS resolution counter.  I have
both the timer interrupts and the MIDI input interrupts working.

Right now I'm simply using this capability to flash the stop led when
a MIDI byte is received and to blink the run led for a program
operational mode.

So, do I replace the code I uploaded with one with more capability?
Do I announce this to the group?
Or, do I add another program?

What's the norm here?  I would be tempted to just keep updating the
same file with more capability.

Dave

There is no formal methodology here. If you think that your program
is useful as a module impementation or as a model for how to do something
then you should post it. It sounds as though your modifications are a
useful model for how to use a timer interrupt and a MIDI (serial) interrupt
at the same time, I say, post it!


--- In SynthModules@yahoogroups.com, "djbrow54" <davebr@e...> wrote:

> Has anyone established standards or guidelines for uploading programs?
> 
> I wanted a real time clock in my MIDI input and ouput code so I could
> do timestamps.  I used the timer interrupt methodology in
> syncable.bas and adapted it to keep a 1mS resolution counter.  I have
> both the timer interrupts and the MIDI input interrupts working.
> 
> Right now I'm simply using this capability to flash the stop led when
> a MIDI byte is received and to blink the run led for a program
> operational mode.
> 
> So, do I replace the code I uploaded with one with more capability?
> Do I announce this to the group?
> Or, do I add another program?
> 
> What's the norm here?  I would be tempted to just keep updating the
> same file with more capability.
> 
> Dave

Hi Dave,
    What a very good question.
    
> Has anyone established standards or guidelines for uploading 
>programs?
> 
No-
there are no official standards or guidelines. I work in a 'big-shop'
coporate IT dept so i'm well acquainted with the benefits of
shop-standards and i admit that it's kind of a close call with a
software/hardware hybrid. There is no harm in developing 'islands' of
standards (note the plural)
BUT
IMHO the PSIM environment will reap more benefit from the
'wild-growth' model than the 'row-crop' model.  i have urged Brice to
refrain from endorsing any 'official' rules. The best practical
conventions will emerge on their own, but it will take a pretty long
time.
(sorry for the lecture but your question is the best catlyst for a
dialogue i've seen on this subject so far)

(sheepish ahem)
so... for the reasons pedantically elaborated above, i suggest that
you purge and replace your versions as long as you are adding
features, that's what i do. The exception is when i remove a feature.
i leave a back-rev'd copy even if the feature doesn't seem valuable
-to me-. 
For me it is always easier to remove features from someone elses code
 regardless of their style, than it is to add or integrate features.
but that's just one fatuous old farts opinion.

BTW
(and i apologize for being too slothful to look this up for myself)
but does your MIDI-in code support MIDI beat clock? (OxF1byte), not
midi time code but the old system-common beat clock?
in all cases,
 thanX for your efforts & generosity
-doc

PS
(to the group)
i apologize for being missing in action a lot. i'm in a pitched
courtroom battle with a school board these past weeks with no end in
sight for the near-future. To those of you who have asked questions
off-list i will work out some answers but please be patient with me



--- In SynthModules@yahoogroups.com, "djbrow54" <davebr@e...> wrote:
> Has anyone established standards or guidelines for uploading
programs?
> 
> I wanted a real time clock in my MIDI input and ouput code so I
could
> do timestamps.  I used the timer interrupt methodology in
> syncable.bas and adapted it to keep a 1mS resolution counter.  I
have
> both the timer interrupts and the MIDI input interrupts working.
> 
> Right now I'm simply using this capability to flash the stop led
when

> a MIDI byte is received and to blink the run led for a program
> operational mode.
> 
> So, do I replace the code I uploaded with one with more capability?
> Do I announce this to the group?
> Or, do I add another program?
> 
> What's the norm here?  I would be tempted to just keep updating the
> same file with more capability.
> 
> Dave

Hi Dave
   please ignore that last question about midiinout.bas (duh!) 
   i just re-read the code and realized that it's a generalized 'get a midi byte in' frame (very clear & nice) , not a note-on/note-off application, sorry for the  superfluous question and thanX again for your hard work.
best,
-doc

Initially, I just wanted to prove that the interface worked since on
my panel it's built from the inside out.  The MIDI interface is
buried and was the first to mount on the panel.  I didn't want to be
debugging wiring, hardware, and software all at once.  It is just the
basic I/O as you have determined.

Eventually, I'll add to the code.  I have a Kurzweil ribbon
controller so I'll probably write the code for that.  I'll also take
suggestions of what people want to see next.  I was thinking of
perhaps using this as the basis to convert MIDI to CV for one of the
sequencer applications that's written.

I'd be happy to look into the beat clock.  I don't exactly anything
about it.  What is it?
Dave


--- In SynthModules@yahoogroups.com, "drmabuce" <drmabuce@y...> wrote:
> Hi Dave
>    please ignore that last question about midiinout.bas (duh!) 
>    i just re-read the code and realized that it's a generalized
'get a midi byte in' frame (very clear & nice) , not a
note-on/note-off application.
> -doc

Hi Dave
--- In SynthModules@yahoogroups.com, "djbrow54" <davebr@e...> wrote:
> I'd be happy to look into the beat clock.  I don't exactly anything
> about it.  What is it?
You're very kind to offer but don't worry about it. For one thing i'm probably the only disnosaur out there who has a need for it and i have experience implementing it (although it was back in 1984 or so!) 
Your code framework has done the heavy lifting - the rest is 'recreation' 
(right!?)
;'>

thanX again & best wishes,
-doc