[Coco] CoCoTracker 6809 bug/issue

[Bill Pierce]

BTW... running CocoTracker through the Orch90 in full stereo through a 750 watt PA system has to be heard to be believed!
Even plugging the Audio Out jack on the Coco 3 into the PA is impressive. The fidelity is much better than you would think for 6-bit output (Orch90 is full 8 bit stereo)
CocoTracker in VCC in Orch90 through the PC speakers is equaly impressive!
 

Bill Pierce
"Today is a good day... I woke up" - Ritchie Havens
 

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com


 
 
-----Original Message-----
From: Bill Pierce via Coco <coco at maltedmedia.com>
To: coco <coco at maltedmedia.com>
Sent: Thu, Mar 26, 2015 1:10 am
Subject: Re: [Coco] CoCoTracker 6809 bug/issue



Sean, I don't have any drives connected to my real Coco , so I cannot test
CocoTracker on a real drive at the moment.
But... testing in VCC under RSDOS,
RGBDOS, & HDBDOS, CocoTracker loads and plays from drives 0-3 just fine. I had
mod disk images in all 4 drives and was bouncing back and forth between
them.
About 3 years ago when I still had my drives connected, I distinctly
remember playing mod files from Drive 1 as I was trying different mods I had
downloaded and was playing through an Orch90 pak through my studio PA system. My
Coco 3 has a 6809 CPU.

First, I would suspect the Drivepak as it was rather
flakey in certain areas from what I've read. As for the CocoSDC, I would check
the dip switch settings as that seems to be a regular solution to problems with
the unit, again from what I have read.
I do not own either one of these units so
I cannot test any results for these.

In CocoTracker, the drive dir & load
commands are issued from the BASIC part of CocoTracker and therefore are the
same commands (BASIC is not modified) used to load any other programs in BASIC
including from the command line so I doubt the problem you are seeing is
CocoTracker related. Have you tried putting the CocoTracker disk in drive 1 and
the mod disk in drive 0? This would tell you if you even have acess to drive 1.
You would need to issue a "DRIVE1" command for this to work as the Basic part of
CocoTracker expects to find the ML part on the "default" drive.
Try other
programs that load files and see if they load from drive 1.
 

Bill
Pierce
"Today is a good day... I woke up" - Ritchie Havens
 

My Music from the
Tandy/Radio Shack Color Computer 2 &
3
https://sites.google.com/site/dabarnstudio/
Co-Contributor, Co-Editor for
CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail:
ooogalapasooo at aol.com


 
 
-----Original Message-----
From: Sean
<badfrog at gmail.com>
To: CoCoList for Color Computer Enthusiasts
<coco at maltedmedia.com>
Sent: Thu, Mar 26, 2015 12:00 am
Subject: [Coco]
CoCoTracker 6809 bug/issue


I have discovered a problem with Sock Master's 6809
version of
CocoTracker.  (I
can't test the 6309 version since I don't have a
CoCo with
one)

I was wondering
last year why it wasn't able to load songs that
I had on
drives 1,2, or 3 with
the Drive Pak.  They would never show
up.
However, playing around today with the
CoCo SDC, I was able to determine
it
never actually looks at those drives, only
drive 0.  If I copy a .mod
file
from drive 1-3 to 0, and then run the program,
it shows up.  If you
choose
any other drive from the in-program menu, it still
only shows the file
from
drive 0.

-- 
Coco
mailing
list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco




-- 
Coco mailing
list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco