http://www.bioroid.com

Enjoy,

Martin
bioroid

Sorry to hear that Martin .... Turntablist Pro is great.

what of creakbox then ?

Someone else will hopefully release it.

Martin
bioroid

So, what next then, Martin?

- m

Why?

I love the GUI, the look and feel of the silver knobs ....

And especially the sound

What's with Frank Reitz? Does he plan to release it finally?

I'm very sad about this, believe me.

Markleford:
Hrmm.. what's next? Well, it won't be any more plugins. I am going to be spending my free time getting back into drawing and writing.

JonnySun 1.0:
I don't think Frank has time to work on it either. We both hope someone else will take the code and make something great out of it.

Martin
bioroid

I couldn't seem to find any of the source releases the news item mentioned on the web site. The only thing I could find were the demo's. Did I miss it?

Good Luck in the future Mate & Thanks for the plugins you brought to the table.

I wonder if anyone has brought this to gols attention

Hey Martin,

Sorry to see you go man, TTPro is the best!

Anyway, I'm thinking of getting into programming plug-ins soon. If one were to use the Bioroid source code on a project and release it publicly, what kind of licensing scheme would you demand of the programmer (if the plug was released for free, for a price, etc.)?

I ask because there are a couple of things missing from TTPro that if added would make it the ULTIMATE DJ plug-in, and in the coming months if I can get my head around the whole programming thing, I would like to deal with the issue of adding .mp3 support, BPM readout, integrated scratch mixing console, and maybe even Ms. Pinky support. Again these are pie-in-the-sky ambitions that before I start working on I would want to know what future they have. Let me know the deal, Thanks!

ATA

There is a license.txt file which states the conditions of the license.

Martin
bioroid

Gosh, it is too bad to hear that you don't want to work on your plugs any more, but way to go releasing the source code in the process! You are one of the few responsible devs out there, hardly any release their source when they ditch their work, go under, whatever.

I love Turntablist, so I did a bit of work on it since it was released and, most importantly to me (being a Mac OS X user), I ported it to Audio Unit. You can check out a beta here, if you'd like:

http://destroyfx.org/audiounits.html#turntablist

There are still a few things left to do (I didn't implement the parameter value read-out yet, I will put in the MIDI learn since I already have 99% of the code written in our DFX Library, and I want to switch from libsndfile to the AudioFile and AudioConverter APIs, so that MP3 and AAC and stuff will be supported and the download will be much smaller), but it's mostly working well now. Please let me know if you encounter any problems...

Okay, here's one thing on which I'd appreciate input... Does anyone else think that the "pitch amount" knob should just be removed? I don't get it. Why would I want to make the pitch slider not work, or work in a more limited fashion? Why wouldn't I just always want the pitch slider to give me control over the full range of pitch values? If it's about fine tuning control, then you can just use the shift key with the pitch slider and get fine control (plus still have access to the full value range).

Anyway, I really don't get it, but I may be missing something. So I'm just wondering: does anyone have any insight as to why the "pitch amount" parameter exists, and whether it's a good thing? If not, I'm inclined to toss it out.

Quote:

Okay, here's one thing on which I'd appreciate input... Does anyone else think that the "pitch amount" knob should just be removed? I don't get it. Why would I want to make the pitch slider not work, or work in a more limited fashion? Why wouldn't I just always want the pitch slider to give me control over the full range of pitch values?

I don't really use the plugin in question, but I know from other wave-transversers it is nice to automate the transversal with a synced LFO, and then you can make variations with the "amount" knob to give the scratching a non-robotic pitch without going nuts on your automation.

-Steve

Marc,

It's great to see that you are keeping the Turntablist alive.

I created the pich amount knob because I know some turntables have a switch for the range of the pitch slider. I was trying to emulate that functionality and also give the user more freedom. Another good use for it is if someone lays down some pitch slider automation they can play it back and just mess with the pitch amount knob to try out different variations. Maybe even jam with it in real time. I def think it is a feature that should stay in.

Are you only going to doing an AU version? I am prob going to be selling my Mac soon and be Windows only.

Martin
bioroid

Okay, I think I get it now, thanks for the responses about pitch range. I will let it live...

About AU, yeah, that's all I'm doing cuz I don't do VST and I don't do Windows (I don't even have a Windows computer). However, the way that I ported it is that I ported it to our internal DfxPlugin format and used our DFX GUI graphics library. So it's not really written as an AU or VST plugin, it's written as a DfxPlugin. DfxPlugin then has layers that glue to the AU API or the VST API. Currently we have it designed to work for AU on Mac and VST on Windows.

However, DFX GUI really only builds for Mac. Tom (the other half of DFX, and a Windows user) is working on the Windows graphics stuff, but extremely slowly, and it's far behind the Mac code. But if Tom finishes that up, then it would be more feasible to build the code I've written for Turntablist for Windows VST as well.

However... I also, in my changes, have made Turntablist's source code less portable. I have ditched all of the path and FSSpec-based file handling and it's all done with FSRefs. DSP <-> GUI communications are done via AudioUnitProperty notifications. The file browser is direct Mac API code now (and uses the AudioFile API to filter readable audio files). And next on my list is to axe libsndfile and use the Mac AudioFile and AudioConverter APIs instead, since then more file types will be supported, any new support comes automatically with OS updates, and the executable binary size goes down to about half. Though I can leave the libsndfile code in there, commented out, I guess for a possible future Windows version. But so anyway, it would really but up to Tom to 1) finish his side of stuff for DFX GUI and 2) be motivated to port my Mac-specific code. So we'll see... For now, just AU.