looks cool on the amiga, how "fast" does this work?
Reminds me on those tools for renoise.

well... those screnshots were taken from an emulator + they function very fast. the resampler runs very slow on a real amiga 600 (68000 cpu @ 7mhz) --- approx 1 minute to resample a breakbeat. i personally find it faster than resampling on a pc + transferring it to an amiga, plus all the handy calculations are done for you. the other 2 run fast on a real amiga.

resampler - basically resamples your sample data to match the tempo. it uses SoX as its resampler, so the results sound great + are precise. currently only resamples RAW files... but before i release this i'll add support for the other formats (iff, 8svx, etc).

transposer - instead of resampling data to match tempo, transposer automatically adjusts the transpose and finetune options of your octamed instrument to match tempo. works very fast. results are accurate to within .0625 of a cent. however depending on either the sample frequency or due to a bug in octamed, or due to playback limitations of the amiga's soundchip... certain transpose results may not be the results you expected, especially for extremely high transpositions. then it is better to use the resampler.

chopper - basically chops your sample based on how many chops you want. it can select precise regions, ie 1/4 note, 1/8th, etc. and create new instruments out of them. the ranges that the chopper select are accurate to within .5 of 1 sample (length). im planning to add some features to this... a scrollbar for cycling thru the sample manually, a preview range button, an instrument destination button. whatever i add i'll be sure to keep it very simple with as little user interaction as possible to achieve results. plus keep them 68000 compatible.

these were fun to make. if anyone has some ideas for other types of plugs, let me know ;)

Hey, these look great. Nice work...this is always something I wanted to get around to doing.

I have a few questions about these though. I think I may not understanding, perhaps it's all the politics I've had to soak in lately.

Resampler: Would using this be of any benefit to me if I normally use Octamed's "Record to disk" function? How does this differ from the "Resample" function in the instrument editor?
Transposer: Would this be of any use if I normally just cut breaks/resample?
Chopper: How does this differ from that Stanley plugin? I use that on occasion, but find it quicker to just manually cut everything. Also, how would the scrolling functions/preview range functions differ from the ones built into the sample editor?

I do have a semi-related question...the Amiga crashes whenever I try to call on plug-ins like the kick drum generator or cha_filter. Any idea why this is? Stanley works fine.

no perhaps not. they arent really related. this resampler basically takes the waveform length (in samples) and resamples that data to match the tempo of your project. for instance, lets say you either sampled a breakbeat thru an amiga sampler, OR you transfered a breakbeat from your computer to the amiga. --- basically this tool takes that sample and "resamples" it to match the "frequency" (rate) you provide --- ie 16574 is C3 on a pal machine --- if you choose resampler and provide 16574 as the frequency argument, then whenever you enter the note C3 in the ediitor it will play back in time with the tempo of your project. if you select 11084 (F3) as the frequency, then the sample will be resampled so that whenever you enter the note F3, it will be in time.

the transposer is exactly the same as the resampler, except that it is much faster because it uses octameds transpose/finetune variables to adjust speed instead of resampling. --- it is almost identical to the NSM plugin cha_autotempo, except its a bit more forgiving for tempos that are out of range (of cha_autotempo). however, the results are a little unpredictable when changing to extreme low or high tempos (depending on the length of the sample). thats why i made the resampler... its dead on accurate, but slow. both only work with BPM and not SPD. if someone could provide a mathematical formula for converting from SPD to BPM id be happy to include it, im too lazy to research it because i rarely use SPD.

its somewhat similar to the stanley plugin... i tried that too, but found it faster to just manually do everything as well. basically it does the same thing as stanley except it selects ranges for you (ie almost like the old program ReCycle). basically its similar to stanley except everything is automated as long as you provide the correct # of beats/chops you want. i think im gonna add some features to this one. --- i basically made all of these because i smoked too much pot over the weekend and had fun doing it + i wanted to make something that made my life easier. i didnt know a thing about programming for the amiga (rexx) before friday, but i thought it was fun and challenging. i want to make all of these better and/or come up with some other plugs that will be useful.

i can help you with this later... they all run fine on my 600. perhaps there is a library that you either dont have installed that they require, or a mismatched version of a library, ie a 68030 version vs a 68000 version - just a guess. i'll have a look at the bassdrum and filter docs and see if theres anything that looks likely.

getting a little closer...

the transposer is exactly the same as the resampler, except that it is much faster because it uses octameds transpose/finetune variables to adjust speed instead of resampling. <--- That sounds great, I mean especially that they use the variables instead of resampling.

I sold my amiga a time ago, cause octamed didnt run that well and I didnt want to fiddle around to get the CF HDD format stuff.
On the other hand, I think I can get more into (before) cryptic structures, cause I get my ass beaten by assembler in the summer for some serious
PIC action. (to get my synth into shape and stuff).
:D

Looking good :3

just an updated screenshot... will be finished soon + on to testing. will post a video during testing.

a video update below... sorry for the shitty vid, i cant stand making them. it was my 3rd take and i got annoyed. anyways the vid shows the sample chopper. i'll make vids of the others soon.

teeth!: is a sample chopper. it has a randomize function for randomly rearranging a sample. it also has a lock feature for locking areas you don't want rearranged. you can also manually rearrange a sample using the lock feature, or you can manually edit + chop a sample using the select/copy/paste tools. they automatically adjust to select/copy/paste convenient areas (1/8 1/16 1/32, etc). you can also rearrange/chop/paste multiple samples together. theres also a random retrigger feature that will randomly retrigger areas of the audio... eventually i'll make this like the lock feature so you can force retrigger (or not).

timebomb!: will automatically resample a sample to match the bpm of a project. it supports any range of both bpm and spd. i spent a lot of time coming up with the equations that actually calculate this... it was a bitch because there is no documentation anywhere about it + it was fairly complicated math. timebomb can also automatically transpose a sample using octamed's instrument settings rather than resample.

earache!: is basically a frontend for some of octamed's built in effects. handy to have everything conveniently located. (inspired by anakirob)

destroy!: not pictured, is basically a frontend for sox with a few features of timebomb! supports high pass, low pass, bandpass filters, compression, timestretching (instead of resampling), a bitcrusher (2bit 4bit), and a destroy option that will insanely distort the audio.

everything runs fast on an emulated amiga 4000. i've run them all on my real amiga 600 + they are pretty slow... ~ 1minute for resampling with sox, ~15 secs to resample with octamed's internal resampler, ~10 secs to chop a breakbeat. although slow on a 600, they are all %100 compatible with a 68000 cpu as well as workbench 2.1. sorry for the lame video, i hate making videos. will try to post some vids of the others later.

TEETH!

lookin snaaazy :D

That sounds pretty damn awesome.

Regarding my crashes: I may have narrowed it down a bit.

- I did a fresh install of everything...made sure there was no bullshit in the startup (except for memtrailer, which helps with octamed crashing when editing samples)

- I edited the octamed#! file to point to the proper directories, and it starts/launches NSM/arexx port/whatever (although, it doesn't actually launch octamed...)

- I started the patched version of octamed, entered the amigados shell, ran cha_bassdrum but crashed *specifically* when I used the "to=" command

- I then switched from a 3.1 kickstart to a 2.04 kickstart in the emulator and it fucking worked. Fuck. (five hours later and now I'm late for work)

So basically my questions are these: What WB are you running? What is your kickstart? Might I be missing some sort of library, even though it was all a clean install? Why might the octamed#! file not launch the actual program when all the paths are correct?

Apologies for all the questions, but I would really like to get this machine ready before the next round of shows and these plugins would save me some time.

Also, do you have a paypal?

depending on my social life, i plan to have these available for download by the end of the weekend. before i do that, i'll have to do a clean install myself to make sure i have all of the required libraries available as well... when i do that, i'll make a vid of it so you can see exactly how i install it. hopefully that will shed some light on your problem. if not, then perhaps we can coordinate a time on irc or something...

another vid:

TIMEBOMB!

ok, so after going through my A1200 roms I see that 40.68=BAD and 39.106=WORKING

I managed to get cha_bassdrum (among other nsm plugins) working on both the hardware and emulated A1200 and A600 chipsets...this brings about ten years of confusion to a close

now I'm ready to take advantage of your tools...

Here's a few suggestions for plugins I thought of the other day at work. Some of these were plugins I was thinking of creating on my own when I had the time, but considering it's now going on years I figured it's time to talk -

- an easy way to merge songs (it's possible to switch between songs in the song list and copy blocks, but this is a fuckstory)
- sample names ignored when importing samples/blocks (if you have two samples with the same name when importing blocks via the song-merge method, octamed usually just imports one of the two, leaving you with copies of the same instrument when they should be different)
- possible synth editor improvement (ANY change would be a good thing at this point...I'm thinking something along the lines of AHX)
- possible MIDI improvement (again, any change would be stellar...perhaps recording of knob movements/etc)
- track names w/ instruments listed in each track throughout the song (useful for when you are disorganized and want to record tracks separately)
- instant organization of each instrument on its own track throughout the song (a simple click will organize your song to put each instrument on it's own track)
- show unused instruments (similar to "show unused blocks" where octamed puts a star next to the unused block in the block list)
- command line copy/paste/delete (just like normal, only for command lines only...might be easier for command 19xxx when time stretching large sections)
- a button or easier way to keep track of command pages (other than the shortcut, there's no way to access the other pages...I might use the feature more if I remembered that I could have more than one page)
- user interface for previous nsm plugins like cha_filter (I think you mentioned this already, but this would be awesome...fuck using amigaDOS shell when I want to be creative)
- similar effects to that of musicline (this might be incredibly difficult, but it would kick some doors open I'd imagine)
- more sample slots (pipedream and not realistic but figured I'd mention it anyway)

sweet you finally got it working. nice ideas... i did consider something related to the command pages + synth editor (as well as guis for the nsm plugins). originally i was going to make teeth chop a sample and plot data in the tracker editor - either simply entering note data, or chopping via 9x command. i eventually decided against this (for now) because it was a lot more complicated than simply writing a new waveform.

finally a download: http://www.dirtybomb.tk/destr6y!/

im terrible at documentation...

c.lha
-> varexx and VXC goes in your system:c directory
libs.lha
-> *.lib goes in your system:libs directory
rexx.lha
-> *.rexx and *.gui goes in your rexx: directory

you should have one by default, but if for some reason you don't have a rexx: directory you will have to assign one. you can then either select 'run rexx script' in octamed, or assign a keyboard shortcut to 'run arexx script': rexx:[script!].rexx

earache!: basically a frontend for some of octamed's internal effects (inspired by anakirob)
Echo: octamed's echo effect. NN = number of echoes, RR = echo rate, VV = volume decrease. numbers must be entered in pairs, ie 01 = 1
Vol: volume increase or decrease (in percent). range = 0-999
F/B: filter/boost/none. AA = averaging, DD = distance. numbers must be entered in pairs, ie 01 = 1
NC: don't clip the sample (when vol > 100)
L: load a new sample in the selected instrument
P: play the selected instrument
< and >: scroll forward/backward through instruments
Go!: do operation
U: undo last operation. i considered removing this feature because it adds approx. 8s of execution time on an A600. if you want to remove it yourself, either delete or comment out line 225 /* CALL undo */

timebomb!: resamples or transposes an instrument to match tempo.
Pitch: the default pitch of your sample (F#-3, A#-2, G#-1). must be entered as a number. its the most efficient way i knew off for entering it. 0 = C-1, 1 = C#-1, 2 = D-1, 13 = C-2, 25 = C-3, etc. when you enter this data it will also set the default pitch in the sample editor. watch vid if you get confused.
Beats: the # of beats your sample is, ie 2 beats, 4 beats, 8, etc
-AA: resample with no anti-aliasing
+AA: resample with anti-aliasing
TSP: don't resample, transpose using instrument transposition settings instead. this gets flaky when you try to transposition further than 1 or 2 octaves. in that case you should resample. there is a technical reason for this...
L P < > Go!: same as above

teeth!: a sample chopper + rearranger. read the important notes.
L: lock parts of the sample. this is in ranges of 1/8th notes. ie 1 = the range of the first 1/8th, 2 = 2nd 1/8th, etc. you can rearrange the sample by entering 1-8 here. ie 11111111 will play the first 1/8 note 8 times. 12345678 will play the sample normally. 87654321 will play the ranges backwards, 00000000 will play the ranges in random order (see note below). valid ranges are 0-8 (see note below).
S: the source and destination instruments (see note). S# = source instrument, D# = destination instrument. numbers are the only valid entry and must be in pairs, ie 01 = instrument 1, 02 = instrument 2, 10 = instrument 0A, 63 = instrument 1V. like above with the note entry on timebomb, this was the most efficient way i knew of for entering this data. basically teeth creates a new sample for you (in the destination instrument you choose) using the data you enter. ie L:87654321 and S:0102 will create a new sample in instrument slot 2 of instrument 1 played backwards. just try it. important: if you already have an instrument in the destination slot it will be overwritten without warning.
R: retrigger option (see note). this will randomly retrigger areas of the sample with a resolution of 1/16th.
L P < > Go!: same as above
the rest of the buttons are intended for when the sample editor is open (see youtube vid)
PR: play the currently selected range of the sample.
<<: move range backwards in the sample without increasing or decreasing. this has a resolution of 1/32
>>: same as above except move range forwards.
-: decrease the selected range by 1/32
+: increase the selected range by 1/32
CP: copy the selected range
PA: paste (overwrite) the contents of the copy buffer INTO the SELECTED range of the sample (watch vid). if the selected instrument is empty it will paste a new one. IMPORTANT: you cannot currently append paste. if you want to do that (you can still copy ranges) you will need to go to octamed's sample editor menu and select "paste". there is currently no way to do that with teeth, but i plan to implement it.

important notes: after a lot of consideration i removed teeth!'s randomize function. sucks. however, the reason is because it is actually pseudo-random. what this means is that there is the strong possibility of predictably generating the same content, either by the same user, or among different users. i personally think this is unacceptable. as of right now i haven't found a solution to generate true random data. it's the #1 thing on my list of to dos. i will eventually get this re-implemented either by learning a way of generating truly random data, or by obfuscating pseudo-random data to such a degree that its almost truly random. perhaps it really isn't a big deal... how many people are still using an amiga for audio production + octamed anyways? #2 on my list of to dos is to add the option of append-pasting in the sample editor.

also destroy! is not included. honestly aside from the (pseudo) bitcrusher, better quality resampling, timestretch, and high pass/low pass filters you aren't missing too much. i wasn't very happy with its performance and the gui took up too much screen space. i plan on rewriting this with just the useful aforementioned features. its my #3 thing to do. if anyone really wants it before then , just message me.

timebomb! can be sluggish when scrolling through instruments (at least on a real A600). this is because it is doing math calculations when you switch instruments.

undo features write a temporary file to your hard disk in T:temp.ds. this is why it adds approx 8s to execution time. if for some reason you have a file named temp.ds in your T: directory it will get overwritten. i considered simply copying undo data to an empty instrument, but that would have consumed more memory. if you dont have a hard drive or suspect you are getting some error because you don't have a T: directory, simply delete or comment out the CALL undo line (see above).

i've tried to anticipate and prevent errors from happening but if you use this software you use it at your own risk. my advice is to use it in an emulator first and get familiar with it. if you do get an error, please let me know... in the useful text fields of the gui it should say something like "Error! line#". included in every gui is a useful text field, sometimes alerting you to what is going on, or displaying some useful information.

general info: i made these because i wanted tools like these that didn't exist and it was a fun project once i got started. i'm not a programmer, i wrote most of this stuff when i was sick and had a lot of spare time. feel free to make any modifications you like. hopefully they are useful + save some time, or someone rewrites them better.

other stuff:
the guis require varexx (partially included above): http://aminet.net/util/rexx/varexx.lha
the guis were created using gadtoolsbox (not included): http://aminet.net/dev/gui/gadtoolsbox20c.lha

You forgot to mention you wrote it while on pot as well etc ;D

Nicely done.

I'll contact you on the IRC next time you're on, in regards to this actually. Would have these past few days, but was dealing with a few scammers on a few items i been selling and whatnot etc Threw me off these past few days really.

Ok!

So I installed per directions and I'm getting errors for each:

"Error code 20 -- Line 47

Not an IFF file"

I tried loading an .iff file...no luck. I had a "Rexxc" folder already and tried putting the plugins in there...no luck. I tried creating a "Rexx" folder and putting the plugins in there...no luck.

Let this be a lesson to everyone on why Amigas are a royal pain in the ass.

error line 47 is because the script cant find the *.gui file... make sure they are in the same directory (rexx:). open up an amiga dos shell and:

cd rexx:
dir

and make sure they are all listed. you can also open up each script in a text editor and change the path on line 10. ie:

gui_file = 'REXX:teeth!.gui'

if you change gui_file = "Work:teeth!.gui' then it will look in your work directory for the gui. not sure your preference for copying/moving files and folders, but i use directory opus. also make sure everything in the rexx.lha archive is in rexx: NOT rexx:rexx/*.gui. should be an easy fix let me know when you get this working.

haha i know... i actually started to mention it but its difficult to mention that w/o sounding silly or ridiculous. the only reason i wanted to mention it is cuz id like to see that stereotype destroyed. i also did most of the math calculations with a notebook and pencil (and calculator). each took me roughly 5-6 hours + 20 pages of math scribbles and trial/error calculations.... i got really obsessive with it + was surprised there was no information on google. they can easily be modified to calculate tempo/pitch in other trackers as well (milkytracker/renoise/etc). not sure if i'd have solved them sooner or never w/o pot though :D

for bpm: tempo = (tempo * .75 * lpb) / tpl
for spd: tempo = (tempo / tpl) / .088
for transposing: 12 * (ln(tempo/bpm) / ln(2))

ok...just figured it out after some time away from it...

the script had "rexx:teeth!.gui" on line 10, but after I fixed it with "rexx/teeth!.gui" it worked...or more specifically: "Work:rexx/teeth!.gui"

now I need to go to work...FUUUUU

@systmcrsh" PM'ed

Here's another question, does anyone know if it's possible to assign a midi function (or note) to either the Amiga's keypad or function keys in OSS? Sort of like the "input map editor," except for midi output. It's a waste of good keys when you are using the "midi learn function" with programs like Renoise or Ableton and you cannot transmit any information with any of the keys except for the main notes.

I assume it's possible using the Octamed Arexx script/"Keyboard shortcuts" menu, but I don't have any sort of Octamed Arexx guide.

For example, instead of F1 choosing octave 1-2, I could assign it with a note of C-8, a note I would never actually use. Then I could have Ableton "MIDI Learn" note C-8 to trigger a particular loop. Yeah, I could get hit the note which corresponds with C-8, but the function keys/keypad seem better suited for this. Any suggestions?

put octamed arexx doc here http://www.dirtybomb.tk/yoyo/Arexx.doc

not sure if its possible or not... maybe after some trial + error. beyond syncing 2 amigas i don't really use octamed's midi functions... maybe you can assign a key to send a midi message?

Command: MM_SENDMESSAGE MSGNUM/N
Version: V2
Purpose: Sends the specified MIDI Message. (Or current MIDI Message,
if nothing specified.)

Awesome...those docs are a real help.

Here's how to assign a note to a Function key (F1, F2, etc) for those who my find this in an online search (incredibly easy stuff here):

- Go to the keyboard shortcuts section
- Find F1 (or whatever key you'd like to change) in the list on the left
- Erase any text in the "Command" box on the right and enter "ed_playnote note *value of note to play*"

Simple as that...obviously, *value of note to play* would be a number you choose. My only advice is that you choose a note high enough you'd never really use live anyway. This will effectively allow you to map the Function keys (or whatever) to anywhere on a MIDI map in the program of your choice when using the native MIDI-learn. Just make sure that when you decide to map it in Renoise/Live/etc, you do so with the instrument enabled for MIDI in the "Instrument Properties" window, otherwise it will not work.

This would be similar to triggering loops/samples via pads (duh). The benefit would be one less thing to carry around, while making use of more keys on the Amiga.

hey, just a small update here... sorry have had a severe shortage of time lately: http://www.dirtybomb.tk/destr6y!/

earache! v0.1b: added a preset cmd (F1) + cmd to turn on/off undos (F2). to use the preset cmd you will need to add your own options to lines 292-309. enabling undos adds approx 8s of execution time on a stock a600.
timebomb! v0.1: fixed something minor not worth mentioning.

i'm currently rewriting parts of teeth and adding some stuff (pattern operations, offset calculator, + other stuff). its still small and simple to use, but much more powerful. a vid showing some new stuff: http://www.youtube.com/watch?v=a397zwmRTJc

theres a big problem with the random generator in teeth... its basically pseudo-random. this means that users could potentially generate the same content. i think thats unacceptable and decided not to release it until i fix it. i wrote down some ideas for fixing it, but havent tried it out yet. what i may do is remove the random code until then... i think it will still be valuable without it (esp w/ pattern ops + offset pasting). anyways this is my tentative timeline for teeth:

1. finish adding some new stuff
2. remove random code + upload
3. rewrite better random code + upload

Someone buy this man some more weed, post-haste. ;D

goddamnit

hi,

just signed up after finding this thread in a web search regarding octamed/kickstart....the plugins look great!

just wondering what Kickstart version is best? i am looking into buying a new A600...stock KS is 2.05 but will probably add 3.1 - rev. 40xx seems to be the one available to buy on a couple of sites... but i have read above there were problems with this rev!? has this been fixed?

thanks

ps. what version of Octamed does this work with? i will probably use Pro. v4

ive only tested these with octamed soundstudio which afaik is the lasted version made (> 4). also tested them with workbench 2/3 and kickstart 2/3. as far as kickstarts go, not sure how much of a diff thats gonna make... you are likely better off obtaining as much ram as you can which is pcmcia SRAM for an a600. pcmcia sram can be a bit pricey on ebay. personally i like the a600 cuz its small and somewhat portable, but if that isnt important to you, def get a beefier machine like a 1200 or better. for some better general amiga advice check out the english amiga board or amiga.org. there are gonna be some updates to these plugs very soon, stay tuned but dont hold your breath ;)

@blip: The plugins work with Octamed Soundstudio. Octamed Pro 4/5/6 (as well as MED 1/2/3) is a different program and will not work.

I'm not too sure on the kickstart differences for the a600 at this exact moment...