stryd_one

Thanks Moebius. I think I am now starting to fully comprehend the meaning of that advice... The C-Debug that audiocommander has written would be a good example? I think this is the difference between REAL software developers and the rest of us... I mean, I can alter most applications on most different platforms to customise them to my needs, but when it comes to the nitty-gritty stuff like debugging procedures and writing apps from scratch, I think things become far more complex... I'll get there eventually, I'm sure. I just have to keep learning (and trying hard not to bother the forum too much) ;)

Ahh I didn't quite realise what the C-Debug stuff was all about... Like, I knew what it was a debugging tool but didn't realise it was a simulator, that's mad... I should have read the source code before! I'm sure it will help me no end, thanks man! I'll have to extend it's capabilities somewhat, but that's not a problem, and of course then I will be able to share that with everyone too :) Looking forward to seeing that bankstick support added, of course ;) What's mac-tools? Man if I need to run a mac to get a perfect solution, then I'll run a mac :)

All good man, thanks for the advice though :) For the coding/debugging, I've done the same as you in the past, but I think it might be a bit much for developing a whole new app from scratch :\ The good news is that the C-Debug stuff seems to be far more powerful than I had previously realised, and I think that using that, and then later on taking TK's method ( http://www.midibox.org/forum/index.php?topic=199.msg888#msg888 ) Should keep me in good stead... Although the ICD2 did seem like it would be great, if it would work... But I suspect that it will not? The circuit emulation stuff is actually for other MBHP-related things like the MBFX, MIDI Guitar, SRAM interface, etc... I'll live without it I think, as you said - they are reaaaallly expensive. Thanks again for the advice :)

Only a year or two planning this thing ;) I can clearly tell that you've been thinking about something very similar though! :) I love it :) Keep em coming man :D Absolutely :) I mulled this one over a LOT... Basically I see two ways of doing this... Sending the MIDI to a different device, or setting the channel on the mixer to only play through the headphone buss... The first was in my original design, but at the time, multiple MIDI outs on a MIDIBox were not really feasable... Now that they are, we can just switch the track from one MIDI port to another, or maybe just change MIDI channel, or send a command for some kind of automation...For eg, I use a Behringer DDX3216 mixer, I could send automation to that to swap the buss of the audio channel playing the track... But I must admit that it seems a bit of overkill when the mixer would most likely be sitting directly next to the seq... Yeh I think the mutes are so heavily used that they'd have dedicated buttons... Well yeh you could :) Of course the tracks are monophonic (Geez I'd like to change that...vX version 2 perhaps) so if Part A Step 1 had that function, it wouldn't be able to have a MIDI note ... yeh that prev/current/nextpattern stuff doesnt really apply in the case of the vX, because you've got all patterns running concurrently and independently, and 'cueing' a pattern just means that you've set a bit that tells it to play the next step when the assigned clock ticks, as opposed to not even checking whether the clock has ticked, and moving onto the next pattern... :) I think at this point that I'll probably start with the clockbox and build it up from there. I don't know if you are comfortable with C, but TK has advised me that C is preferable over ASM, and seeing as we have AudioCommander's badass C sim, I think that's definitely the way to go. Any thoughts?

Adjusted, according to my poor Spanish translation... I will resume a state of steady scepticism. ;)

Well shut my mouth, I have the source code here! :D If anyone's interested let me know. Don't let me catch you using it without permission or at least solid credit to the original names though!!!!

Wow that was a deathly silence :'( Did I get no response to this because: A) Noone else knows the answer either B) This is one of those stupid questions that is answered somewhere else and you're all ignoring it in the hope that I'll look around the site some more and find the answer (honestly, I looked for many hours! I found *some* info, but not a lot, and certainly nothing that solved my problems) C) Nobody likes me D) Other Please don't take this as a "hurry up" :) I'm not trying to rush anyone! Just not sure if I am waiting for something that isn't coming...

http://www.midibox.org/forum/index.php?topic=6566.0 http://www.deremate.com.ar/accdb/viewItem.asp?IDI=11535504 http://www.midistation.com.ar/ You decide... No response to emails yet....

A little translation... This looks like a MIDIBox, and they're making profit from it... :'( What's the course of action here guys? Thankyou HunterK for telling us about this! :)

What a freakin monster! :D If it were for me, I might try and bring the controls closer together, for fear of tiring myself out - it'd be like doing aerobics, running from one side of that controller to the other ;)

I don't see it? I see me writing doco for you guys at midnight, then a.c being a mac geek, but no SID goodies :'( ;) hehehhe

Pretty. No idea what it does, but I know it looks good when it does it ;)

Way to go dude :) I love it, can't wait till it's done, and I can copy it like a mad percussion plagiarist ;D

Yeh, you're banned ;)

Thanks moogah :) Some thoughts: This is already done, as the patterns are currently only a single track... This is a really good idea. I'm not sure if it would work out quite like you've explained it, but something similar should be doable... There is no edit mode in the vX because it is essentially always open for editing... Currently the design is such that each row of buttons on the UI can be set to display/edit the contents of a certain track, so you would get 8 patterns displayed at once. They could be patterns 1-8, or patterns 1,6,8,10,2 and 15 or whatever tracks suit your needs... But it should be possible to create a "UI Template" that will set the UI to expose the contents of a certain set of patterns together for viewing and editing. Does that sound OK? This one would be pretty easy, just need a "Copy & Edit" feature (Combined with UI Templates as above)... but it couldn't be automatic - because the sequencer is always in 'edit mode', how would the seq be able to tell which changes you make require copying to a new track and which do not? Anyway, because you don't have to change modes, there's still the same amount of button-presses to get the same functionality... Would this suit your needs? The triggers part is real tricky... One of the scenarios you mentioned is already possible. For this one, you would have a third part (Part C) which would be synced to the same clock as part A, and it's first step would run a function which mutes Part B For the other one ...that's tricky... I am not sure it's doable though, but I really like the idea... Here's a couple of thoughts, I hope you can find ways around these, I couldn't :( Certainly, it would be impractical to scan the database for changes, firstly, how often would you scan it? It would be far too large to scan every tick, and you'd need to do it that often in order to be effective, and also without knowing which function was calling the data, it would just be a change of a value, and for example it would be impossible to tell if a note number had been changed or a CC number, as the functions that send that data both use parameter 1.. Likewise, if a step had a value change for parameter 3, then you wouldn't be able to tell if it were a note length, an NRPN byte, or a divider for a clock to be setup... The use of the value would vary depending on what function was set for the step... I won't go on, obviously it would only work if it also scanned for other data, meaning it would take too long. This means that the sequencer would have to check for the changes as they were written to the DB, not later. If a set of parameters were defined in a table as conditions, and a matching set of parameters and a function number to pass them to, then the table could be scanned before values were written to object parameters in the DB, and if it matches, then run a function. You could easily set several conditions to match up like this too... but there is a problem with this - again, table lookups aren't quick, and this could severely effect the realtime functionality of the sequencer. These issues could be avoided by reading ahead of time, but this won't work either, as if you read ahead and then a value is changed, then the conditions would no longer be met, but the function would still be run as it was set to do so ahead of time. Likewise, it could read ahead, find none of the conditions met, and then not run the function, when a parameter could be changed to meet the conditions.... As for not stopping the sequencer, thats already in there :) Definitely a must-have for me, as the vX is designed for live improv, and having to stop would make it far less useful.. The way the seq works, is that as long as the master clock is running, it's always reading from the database and performing functions according to what it reads. If it reads that a pattern is playing, then it will check it's parameters for it's assigned clock, play the next step if it has ticked etc. If the track is set to record, then when the step is triggered, it will set it's parameters according to received MIDI notes or CC's. If you want to manually enter the notes then you can use the UI, by assigning a row of buttons to a pattern and selecting the step using one of the buttons and editing the step, or by expanding the track out so that each of the 12 rows of buttons is a pitch and each of the columns represents one step... it's like a piano roll. All of these modes operate simultaneously, only recording from MIDI input can be turned on and off. I do like the idea of allowing the step buttons to have another function, but I can't think of what kind of things would be playback specific IE not writing to the DB? The EUSART bug no longer concerns me so much. MIOS 1.9 has made this matter more straightforward :) It will also mean that the vX will support multiple outputs for sequencing more than 16 channels of MIDI. The trick with the LFO's and envelopes and FX and such is that it could end up being rather CPU intensive (vector math...), so it would interfere with the operation of the sequencer... Don't give up on the concept though, because as you might have noticed, NorthernLightX and I have been brainstorming on concepts for MBFX, and I want to make them MIDI Clock syncable and remote controllable, so you could use the vX (or any other MIDI sequencer or controller) to program the LFO's and envelopes via MIDI or CV input, sync them to MIDI Clock or Sync24 and send their output either to the AOUT, the Digipots, or MIDI CC's. I suspect I will include something similar in the vX, but not as advanced... You will of course still be able to use the patterns to send CC's etc, but the patterns are only 16 steps long... Fine for rough control, but not for smooth filtersweeps. I had hoped to include the ability to do interpolated values between steps, so that the seq would automatically smooth out the curves, but that's where the vector math comes in, too many divide operations :( An option I have considered is, the Envelope tracks and LFO tracks would have an extended number of steps... If the LFO pattern has a fixed MIDI output port, channel, and CC# with each step containing a value to be sent, then there are at least three unused parameters for each step which could be used inbetween steps. The problem with this, is that the LFO has to be triggered four times as often, meaning it would need a clock setup especially, and that you would have to draw the LFOs and envelopes in manually which means special UI handlers. Regarding splitting up the project, definitely :) I must admit that I have a pretty solid idea of how this should be put together, and I do want to follow a certain method of construction, which will not only maintain the modular nature of the code, but build it from the ground up, adding one feature at a time, building up a set of frameworks for others to create sequencers according to their needs... I'm no dictator though, if we start work on this together and need to branch it in our separate ways then I don't see any harm in that :) I'm just stoked that you're interested, and thankful that you're interested in helping :D Maybe with your help, we can find a way around the whole conditionally triggered functions thing... I don't know if it would be too complex, but it might take more resources (processing time) than a PIC has to offer :( Don't be discouraged though, see if you can find a way :)

Go for it!

Hi illogik! I have a few good schematics for VCR's sitting around as a result of my study on the other thread, if you need them just PM me an email addy :) Thanks for that mate :) I have found a schem for a delay based on that too so if you want to grab it to use as a start just say the word :)

Nice... Now just waiting to see if he'll ship down under... :-\ Thanks for the tip rowan!

.... the unstoppable TK ;D

Nice work! I love those customisations!!

Hehehe you wouldn't believe how fast I clicked the link to read this ;) Seems I've come across this before... It's a shame that the original VHDL source seems to be lost :( ... Not to mention the difficulties that illmenator mentioned. I wonder if FPGA will ever reach a point where it is more accessible to DIY...

Looks good but you might want to do something about those airwires... Especially the ones in the bottom right corner that touch/cross over each other... What PCB design software is that?

Thanks for the awesome feedback mate :) Some great ideas! I'm updating the doco tonight to include all those things, I'll put it in here in a nutshell too.... Stay tuned. Edit: Moogah, before I go ahead, would you mind explaining the third one for me (differentiating between patterns and tracks)? Just want to make sure I've understood you correctly, which I don't think I have :\ Thanks!

ehhehehehe :)

Hey cats, I'm going to buy some of the following ICs for my own use, and I know that some of them are rare, hard to find, or expensive, so if you're interested, let me know... SpeakJet $50 (Speech synth) SSM2044 $15 (VCF) MN3007&MN3101 $5 (BBD Delay and Clock IC's) MN3207&MN3102 $2 (BBD Delay and Clock IC's) PT2399 $2 (Analog Delay) Plus all manner of opamps and OTAs and miscellaneous bits, just let me know if you're after something. All either new or New Old Stock. The prices will vary depending on whether anyone else wants some. If you're interested, let me know, and if I don't hear back after a short while, I'll go ahead and just get what I need. Cheers! :)