Nomical

I only know Autechre and i thinks it's a shame to listen to it with headphones. But that's my opinion and you have yours. You should listen to it coming out of a massive soundsystem which blows you away!

What kind of headphones do you got? Who would want to make music only by means of listening to it with headphones? Both are important, speakers as well as headphones. Tuning the (sub)bass on headphones makes it sound crap when listening back to it on speakers. But making those fine adjustments in the programming makes headphones to a must.

I've used Cubase SX and i like it very much. But it's just not what i'm looking for. I want just the sequence stuff, without all the VST stuff. I couls also not use the extra features of Cubase SX, but what would be the point of using a program of which half of the functions aren't used.... I would use something like cubase 2 or cubase that's running on a Atari ST.

I didn't know that, i always thought Logic had their own standard. But i was right about the good sound quality of the Logic instruments, wasn't i? Are VSTi's still supported now that Apple has bought Logic?

Why don't you have a look at Ableton Live (v2...) This program rocks when it comes to live usage. It's made for live usage. Almost all functions can be used in realtime, even in-sync sample loading during performance, realtime timestretch and lots more! Lots of assignable functions for midi controlling!! And as i remeber, someone is already building an interface for ableton Live, so you can ask construction/design/layout question to the appropiate person.

Logic has their own standard for instruments and as far as i can remember no VST instrument runs under Logic, except if it's specially made for Logic too. And as far as i know, most of the Logic fx and instruments are very good quality. I heard the Logic Enviroment is really good, you can totally customise you're complete interface to your needs.

I heard Imac's suck for making music. But i've only heard and read about it, never actually tried it myself. I've seen test though, which prove that the powerbooks, especially the Titanium powerbooks, are one of the best Mac's for making music. Or Sony VIAO's for pentium based systems.

And buying Logic means you've got to have a MAC in order to use the new Logic and all feature updates since Apple bought Logic. :( But you could also use an older version, either legitimate or cracked that runs nicely under Windows. ;D

Sony Philips Digital InterFace Coax(ial), that's a cable type, but it's also something else which i can't remember.

Sony Philips Digital InterFace Coax(ial), that's a cable type, but it's also something else which i can't remember.

Voor het geval je het nog niet wist: Op www.microchip.com kan je gratis samples van hun produkten bestellen, waaronder de PIC18F452I/P en bankstick chip (ben even het typenummer vergeten). Je hoeft alleen wat gegevens in te vullen voor de registratie. Iedereen die niet graag zijn gegevens invult op internet heeft pech, want ze moeten toch echt een adres en dergelijke hebben om je bestelling naar toe te sturen. Microchip claimt dat er eventueel wat importkosten bij kunnen komen, maar ik hoefde niks aan de FedEX koerier te betalen, handtekening was genoeg. Ik had mijn bestelling binnen 5 a 6 dagen binnen!!

I got this idea about making a midi thru box that splits the signals into 4 Thru's. And now i thought of filtering some type of data out of each signal independently. In other words, is it possible to use one filter module to filter different kinds of data from different 'thru lines', in this case 4 lines? Why would i want to do this? I want for instance Thru 1 to only send data from Midi Channels 1 to 4, Thru 2 Midi Channels 5 to 8, Thru 3 midi channels 9 to 12 and thru 4 midi channels 13 to 16. I want this because i always come across equipment which seems to be responding to data it shouldn't react to or it sends data which it shouldn't send. For example, i had this with the MC303, MC505, ASRX, RM1Xa nd more i can't remember right now. And it even did so when i read through the complete manual and changed all settings normally needed to avoid the problem. And as extra addition. Can the midi monitor handle multiple 'thru lines', perhaps by switching thru the 'thru lines'? So the end result would be: [ Midi In --> Filter --> Monitor --> Midi thru 1 / Midi thru 2 / Midi thru 3 / Midi thru 4

I think i'm going to wait until Step C of the control surface is finished. As i've understood, this would be the ideal skeleton for the display interaction. And I think i'm going to have to build my own handler. The DB50Xg doesn't transmit anything, so i can't recieve into the controller. But what do you mean with 'my own table format'? Do you mean the table i have to make for all the sysex commands and stuff i want to implement instead of idea i had about putting everything in MIOS_TABLES.inc. Which was the wrong solution as i've read now. Can i put the conversion tables i discussed in the same file as the sysex commands? Or is this the same as you described by putting all stuff in one line for each parameter? Couldn't there be a permanent bankstick in case my setup is too big and i have to write it to the bankstick like you described? And couldn't there be a second (or even more) bankstick 'slot' that can be used to save other things to if nessecarry? What would happen if an incomplete Midi Event were to be recieved? Couldn't there be something like a safety program/app that filters these incomplete messages out or some other protection method? Thanks for the very 'understable' answers, Thorsten. I listened to your tracks, some of them are very nice. That 'Lovesong for my SID's' is very good stuff. Keep it all up!

Used to have dual boot up system with 2x Win98SE. One was installed using 98LITE Pro for audio use. The other one was the chubby, normal full installation for internet, school and stuff like that. After that a dual boot up system with the '98lited' Win98SE for audio and WinXP Pro for internet etc. After that 2 pc's. One running the 98lited Win98SE and a dualhead graphics card for audio stuff, the other runnig WinXP Pro for the rest. The 'audio' pc died a few weeks ago unfortunatly!! Now i only use WinXP Pro for internet etc. I don't use computers for making music no more until i finished the midi controller projects. I hate computers for making music, damn that mouse. Only benefits are a big interface and bizar editing capabilities. I like dedicated harware more now instead of all that software junk. And i can't afford an RME Hammerfall or equivalent, so there's no reason to keep on using a pc for making music. I also got a cheap and slow P1 133 laptop which i'm maybe going to use to sequence with Cubase 2 or 3 (one without all that VST crap). But it's old and i have to make some modifications to the thing to make it Midi compatible. I need something like an serial to ide device, because it doesn't have a cdrom player. It's to much trouble to install something on it. Anyone got some solutions for a familiar problem?

Isn't it a good idea to archive all the different MIOS codes that people have been making to control a particular application? In such a way, there will be more code to compare and learn from for all the people who are new to assembler langauge. Like me!!!

You could put a basic SID in a 1u housing that's being controlled by a computer. Or a midi filter and midi merger in one box! The guy you mean on Ebay is probably the guy that used them for his Oakley Sound DIY Filtrex synth projects. At least, i came across a guy that sells something similar to that, but i think that they're not that good. The backside doesn't have a real panel, but it's more like two layers that lay upon eachother. That guy will be back on Ebay, because he's got more than one to sell. I recently bought a 2U rack housing on Ebay Germany from somebody else, nice!!

Ok, I've begun to read the files from the MIOS d/l page and i'm beginning to see some structure in it. I've also d/l all the software that's needed for writing the code and all. Haven't installed it yet, so i don't understand what activeperl is for. Anyway, I looked at your SID control surface and i see something that resembles the Yamaha A3000 interface. Is it so that the rotary encoders beneath the display control the functions that are currently displayed exactly above the encoders on the LCD? If so, i could use this as a skeleton for my own control interface, right? I'm thinking about making it in such a way, is this still possible if i can't use your SID CS as a skeleton? Oh, and the rotary encoders on the A3000 can also be used as (digital?) pushbuttons. Is something like that easily integrated into MIOS? Would be very cool.... All the CC messages and sysex messages that i want to use, will have to be put in MIOS_TABLES.inc, right? I looked at the snippet you posted above for sending sysex to the DB50XG, but i don't understand something. Why is it that the number of lines in your sysex message as less than what it says in the DB50XG manual? In other words, You only input the midi channel, parameter number and the parameter value. In the manual it says that you also have to send the following sysex messages if you want to change the variation effect type to for instance Echo: 11110000 F0 Exclusive status 01000011 43 Yamaha ID 0001nnnn 1n Device Number 01001100 4C XG Model ID 00000010 02 Address High 00000001 01 Address Mid 01000000 40 Address Low 00000111 07 Data (Variation Type MSB) 00000000 00 Data (Variation Type LSB) 11110111 F7 End of exclusive So my question is, why are there less strings/messages/whatever in your snippet for sending sysex to the DB50XG? And if i have to do it like i described from the manual, can i put all of these 'blocks of messages' into MIOS_TABLES.inc? Display question. It's possible to display for example the actual delay time in ms instead of the decimal/heximal value on the lcd that you have to input in the sysex message, right? If so, do these tables with conversion values to ms (there are about 9 of them) have to put into MIOS_TABLES.inc or do they have to be somewhere else? How much space is there in the MIOS to build a menu for the LCD? You also got an DB50XG Thorsten ( that's what i've understood!), so you know how big the menu could be. I want almost every parameter to be accessed from the menu if possible. The menu should also diplay all correct values and names of effects, parameters and values. Some encoders have to control functions that are diplayed above them on the display as yoy go through the menu, other pots, encoders and buttons should control fixed functions. Would there be enough space in the PIC to implement all of this? One thing i don't understand about the bankstick. Is it possible to implement a code into the MIOS that allows two buttons to directly load and save a setup into the bankstick? Or have i overlooked it and is this code already present in MIOS? Isn't there any space in the PIC for saving user setups? Or will this space only be used to implemnt future functions? And how is midi feedback handeled by the hardware or MIOS? Do you know of any sites or ebooks that have some really good info for starting PIC programmers? When i search with google i get so many sites, i don't know which ones are any good! Thanks.

That's funny, you're the man behind that conversion. How small can this world be. Well, i took a look at the manual of the DB50XG and there are A LOT of functions to control. Far too many for the interface i was initially thinking about. So i'm thinking of something different. Could MIOS be used to make a interface that uses a menu to control certain functions? This would probably require a second and bigger display, right? Would it be possible to make a menu which has a couple of buttons and pots that control the function that's currently assigned/displayed? I guess that would take a lot of effort, making such a menu, or would it not? The idea is to have control over as many parameters in the synth as possible, except for the sequencing stuff which will be handeled by a different machine. It would indeed become more like the Midibox SID CS. I've already worked on a redesign of you're Elektor DB50XG conversion. The main idea was to get rid of the 'opamp' audio section on the card and replace it with a normal 'Line out' section that can even mix the L + R signals together if only one of the two plugs is inserted in the main audio outs.

Hi Thorsten, I looked at the bit of code you posted above and i have question about it. At only has 3 variables i can change, right? Thirst the midi channel, second the parameter number and third the parameter value. So, do i only need to write different versions of this code for every function i want to control? And can these versions be put in one file (the above file) or do these have to be seperate files that i have to load into the MIOS myself? How does the trigger part work? I 'call' upon that specific string (the one above or the ones i have to write myself)? How do i do that? Sorry for these questions, but it's getting clearer by the minute. I can learn pretty fast, but i haven't got the feel for this programming stuff yet. Yet...

You are fast Thorsten! Before i've written an reply to you, there's already a new one by you. Thanks for the fast replies and i'll try to keep up.

So if i understand correctly, 1 Every command/function i want to control inside my DB50XG has to be programmed/assigned to the button or pot/fader i want to use on the controller? 2 For the more complicated funtions i have to write/implement sysex messages (those messages are described in the manual of my DB50XG, is it not?) into an application that i have to load into the MIOS, right? 3 The easier functions that can be controlled directly with CC's/external controllers, do not have to be implemented into an separate application that has to be loaded into the Mios, but instead they can be 'learned' by the controller because there already is an application for MIOS that controls the use of CC's/external controllers, right? Thortsen: Quote:In the manual of the DB50XG it says that some functions can be controlled directly by external controllers. Does this mean i only have to use the control numbers (or CC's?) to assign the function to a pot/fader or button? I don't have to use sysex for these functions, right? yes, some functions can be controlled by CC's, but the DB50XG supports much more parameters. So if you want to control the whole parameter set, you have to go for SysEx. However, for the application this doesn't make a big difference. What do you mean with 'However, for the application this doesn't make a big difference'? Oh Thorsten, it seems as if you have more knowledge of the DB50XG and it's external conversion. Do you perhaps have some extra info for me or do you know where to find more info. The only stuff i've found is in French which i can't understand or it's from Elektor which isn't satisfying for me. Thanks

As far as i've seen in the midibox gallery, there aren't that much designs that are build in a 19" rack casing. Why is that? Is the 19" casing too expensive or does everybody just want desktop models (that in my opinion just take up to much space)? If some people have worked with rack casings, do they have any tips for stuff i shouldn't forget?

I don't know what the DB50XG can do what the SID can't. All i know is that it just sounds different because the DB50XG uses FM synthesis and i have it laying around here. I just thought it would be nice to make it as an external synthesizer instead of using that crapass pc everytime i want to use it. And i have to use an old ISA souncard to get it to work. And i'm also planning on building the SID, but i'm gonna wait until i've finished the DB50XG conversion and until the control interface + according software for the SID has been made available.

Waar kopen jullie je LCD's? Via Reichelt, Conrad, Farnell of andere particulieren? En gebruiken jullie allemaal LCD's met een groene kleur? Bij Crystalfontz.com hebben ze hele moooie displays in allerlei kleuren voor redelijke prijzen, alleen de verzendkosten zijn vrij aan de hoge kant voor een of twee displays. Vroeger waren er nog gezamelijke bestelacties om dat soort kosten te drukken. Weet er iemand of er nog zulke acties lopen op dit moment? Op de CORE module zitten twee trimpots voor de LCD contrast and 'backlight-luminescence'. Waarom zitten die op de pcb? Is het niet nodig om het handmatig in te kunnen stellen? Of is dat slecht voor het display om normale potmeters op je interface in te bouwen en regelmatig te varieren van instelling? Bedankt.

Heeft er iemand ervaring met het programmeren van MIOS? Als ik nu bepaalde funties van een synth of sampler wil besturen met een controller die met MIOS werkt, moet ik dan al die toewijzingen van functies en pots/buttons/faders in MIOS programmeren of zit er een soort 'Learn' functie in MIOS ingebouwd? Welke software op welke OS gebruiken jullie om MIOS te programmeren? Dank je.