Recent Posts

Pages: 1 ... 8 9 [10]
91
DAW - Vision & Studio Vision by Opcode / Re: Drum matrix weirdness
« Last post by Syntho on February 21, 2018, 08:22:51 PM »
I was actually editing a patch name document that I already subscribed to. I also tried creating a new one (from within Vision) and was subscribed to that, but the behavior above is what happens. Let me go try this one more time, this time from Galaxy...

All of them pop up in a new sequence? Do tell.
92
some better choices:
i think that using the older green pcb options is preferred in the case of the yikes g4 and B+W g3

(2002 at the latest, 2001, 2000, 1999) dates
rather than (2003, 2004,2005 +)
93
I just have to note for the record that:

If you search "Firewire 410" on the Forum, you will find an endless series of posts complaining how the 410 simply won't work in OS9 because they never bothered to release a decent driver for it.
94
DAW - Vision & Studio Vision by Opcode / Re: Drum matrix weirdness
« Last post by GaryN on February 21, 2018, 07:23:47 PM »
PS: In regards to the last few posts, being able to click on an exact time to paste drum hits you've copied is what I wanted to do. I'm not sure what the benefit is of having that inexactitude as you mentioned. Hmm... guess it'll always be a mystery.
This is what you get when you use a DAW that was chopped off at the knees in the middle of its evolution. Everybody develops their own preferred workflow and good software developers do their best to accommodate that. There are ways to drop / paste copied notes at an exact point in a sequence in SVP. There is the "exact" box that enebles you to specify where all the way down to a 480th. You can open the drum track in the Graphic Window where you can be as precise as you want. You can even have the track open in both the Matrix and Graphic windows simultaneously and click in whichever one you like.! Try that in Performer or whatever! As I said, given an ongoing business, they would have continued to tweak the operation as needed to respond to the user base comments.
Gary: Something I always ignored were the note names in Vision. Now I actually want to use them. The problem is that after typing the note names for drum samples into either the 'Default' patch area, or into the normal specific patch area in the Names window, I only get three "..." when I click into the patch names list in the pulse edit window. When it knows I typed something into that particular note name number, it shows three ... but otherwise it's blank. But funnily, the name shows up properly after selecting three ... like it should. I've fooled with this for an hour and it's still giving me crap.
It's not giving you crap - you need to dig into the process - you're going at it wrong. You need to create and then subscribe to a Notes Names Document. This is either created from scratch or pulled from (subscribed to) Galaxy. Note names are different from Patch Names. They can be altered at will. You're using a D4. It came with the drum sounds arranged in an arbitrary way decided by a long-lost soul at Roland. Many units stay that way forever, but many get changed over time - especially if the triggers are being used. Folks rearrange them to their liking so they're NOT set in stone. So, you create a Note Names Document. You can make one covering the basic drum sounds from scratch easily (unless you just have to have ALL of the sounds across the entire 4 or 5 octaves listed). Note however, they change if you change the patch. the drums are basically the same (mostly) but they need different names just like different synth patches would.

The best way to do all of this is to use Galaxy. Then you can just have your D4 dump all of that into a Galaxy Patch bundle, have SVP subscribe to it and it's all good. You WILL have to create some Note Names Docs yourself, 'cause they don't exist for the reasons described above.

This is waay more than I can instruct you to do in a post. Welcome to the learning curve. This is the basic path:
Windows > Names
Click: D4 / Patch Name Doc column
   Nothing there? You'll have to make one
   Got it? Open Patch Name window… click Notes column next to active patch - that opens Note Names window
Scroll to note, type in drum name. Repeat over as many notes as needed.
Store docs in Opcode folder.
In patch name window, next to D4, subscribe to Names doc you created.

Wasn't that easy? If/when you get that far, holler back and I'll give you a tip how to make them all pop up in a new sequence.
95
HELP BOARD ! Installing & Troubleshooting the Classic Mac OS / Re: File type not correct
« Last post by GaryN on February 21, 2018, 06:18:49 PM »
Not sure I really know why it started on OSX today, but my problem is solved, at least temporarily. Could this be related to the dead battery/date problem ?
YES.
96
HELP BOARD ! Installing & Troubleshooting the Classic Mac OS / Re: File type not correct
« Last post by mb66 on February 21, 2018, 04:20:21 PM »
I found the problem and I had completely mis-diagnosed what had happened. When I started the computer earlier this month for the first time in about a year, the date had come up to some time in 1956 or so and I couldn't open the Quickbooks files.  I have restarted it about a half dozen times in the last two weeks and it always booted fine on OS9. Today, I was trying to run a version of Netscape (the only browser on the machine), so I could hopefully download a new browser and then Filebuddy. The machine crashed (froze), and upon power-cycling it came up on OSX (10.2.6) from, I believe, 2003. Everything (Quickbooks, the only application used on this machine) worked fine - the datafile was accessible.

Not sure I really know why it started on OSX today, but my problem is solved, at least temporarily. Could this be related to the dead battery/date problem or is it likely to be something else? Any thoughts?
97
DAW - Vision & Studio Vision by Opcode / Re: Drum matrix weirdness
« Last post by Syntho on February 21, 2018, 03:21:03 PM »
Gary: Something I always ignored were the note names in Vision. Now I actually want to use them. The problem is that after typing the note names for drum samples into either the 'Default' patch area, or into the normal specific patch area in the Names window, I only get three "..." when I click into the patch names list in the pulse edit window. When it knows I typed something into that particular note name number, it shows three ... but otherwise it's blank. But funnily, the name shows up properly after selecting three ... like it should. I've fooled with this for an hour and it's still giving me crap.

PS: In regards to the last few posts, being able to click on an exact time to paste drum hits you've copied is what I wanted to do. I'm not sure what the benefit is of having that inexactitude as you mentioned. Hmm... guess it'll always be a mystery.
98
Mac OS 9 on Unsupported Hardware / Re: iBook g4 1.42GHz 14 inch
« Last post by darthnVader on February 21, 2018, 02:46:27 PM »
Ati's 'NDRV's' live in the Apple NDRV folder.

Code: [Select]
/System/Library/Extensions/AppleNDRV/ATIDriver.bundle/Contents/MacOS/ATIDriver
Open it with Hexedit, and search for the name of your display " compatible" property. Then for the last Joy!peffpwpc to the next Joy!preffpwpc, that is the ndrv for your card.

Copy and save it with Hexedit, then open it with resedit, and let resedit do a little magic on it. Then open the data fork and copy it.

Take the driver I posted and open it in resedit, replace the date fork with your's. Then find the resource that has ATY,Snowy and replace it with the " compatible" property of your display. Also fix the length of the data fork just above ATY,Snowy.

Save and exit, put the new file in the extension folder, and reboot.

This in no way will make the ATI Graphic's Accelerator work, for 2d, but it is a necessary step if your ATI card doesn't have a Rom based 'NDRV'.

The ATI Accelerator looks to be 68k code only, no data fork, and I haven't figured out how it loads and matches.
99
Mac OS 9 on Unsupported Hardware / Re: iBook g4 1.42GHz 14 inch
« Last post by MacOS Plus on February 21, 2018, 11:17:11 AM »
Working off the old thread at Think Classic I made a version of iMac's ATI Via Extension with the 'NDRV' for the Radeon 9550.

No more ghost display, and now all screen res and color/grey scale work in OS 9.

  Does this change replace another device entry or does it incrementally add it?  I'm hoping that we can eventually expand compatibility using one all-inclusive file rather than a number of exclusive customised variants.  Perhaps discussion of that deserves a development thread of its own.  Conceivably this method can be applied to some AGP cards in full-scale desktop machines also?

I just replaced the 9200 'NDRV' with the 9550 'NDRV', but we should be able to add to the ATI Rom Extender ndrvs for any ATI/AMD cards that had OS X support. Just a little magic needs to be figured out about it.

Also, using the Mac OS Rom nanopico posted in this thread, we can get the brightness settings for the backlight.

Open the ROM in Hexedit and go to the address 0x20D4AD, swap ati with mnca, save and reboot.

  I'd like to be able to repeat this method when experimenting with other Radeon devices, but after reading the info here and at ThinkClassic I'm feeling a bit dumb about the exact procedure.  Perhaps you could expand a bit on your method?  The card I'm interested in trying at the moment is the 9800 Pro to see if I can get 2D acceleration.  I've read that the 9800 uses the 9700 driver in OS X.  Looking inside AtiRadeon9700.kext on a 10.4 drive I see an NDRV entry point, but the question I have is how much data from that point on do you copy and how much data do you replace?  What would be the starting and ending HEX addresses I should paste it at if I want to have it over-write the 9200 NDRV?  Also, is this sufficient without editing PCI device IDs elsewhere?

  If I can get this one right then I should be able to retrieve a number of other NDRVs and save them individually in temporary files for future experiments.  It would be nice to have a simple library like this at our fingertips.
100
Video Cards, Monitors, & Displays / Re: quadra 700 XGL
« Last post by MacOS Plus on February 21, 2018, 09:39:52 AM »
http://themacelite.wikidot.com/kext-mod
i believe this is the page that mac os plus was making reference to above

That is correct.
Pages: 1 ... 8 9 [10]