this is something that has been suggested by a few people. theres a couple extra features im going to try to add to midi goblin before shipping (more info on that down the road) Theres definitely a way to run more than one instance of a midi lfo in theory, though to prevent flooding the synth with midi messages the speed and resolution would probably need to be decreased per midi lfo (i think) - on that note, running multiple instances of the sequencer might be possible though i havn't tried this yet...
It can definitely transmit cc and program change messages to guitar pedals using the patch send feature. but as for the goblin receiving messages from guitar pedals to trigger things (like turning on and off apps/sending patches) - no..... that is to say not YET! I'm actually working on it....planning on re-using a lot of the code from the user defined buttons for this. A few people have requested this feature so Im definitely adding it. Writing the triggering function for it is really simple, but presenting the info on screen, setting things up so multiple triggers can be added and saved to the sd card is a bit tricky. Ill be posting an update specifically about this feature when its done. Honestly i dont own a midi pedal so Itll have to wait until a couple weeks after the campaign ends before i can order one (im on a real shoestring budget until then!)
Great job! As I understood, synths/plugins should be able to receive MIDI CC for MIDI Goblin to save a preset. Do we also have to KNOW those numbers? My question is if Goblin can save with MIDI Learn function from a DAW? (In this case we don't really see the CC numbers but the hardware controller still gets connected)
edit: we only need to know the parameter numbers. not their values. midi goblin listens for any and all midi cc messages and keeps track of values for parameters users define. Yes we need to know those numbers (of the parameters)but thankfully you only need to know them for a few minutes. Adding devices requires listing the numbers and their parameter names in a txt file and dragging it onto the goblins sd card. Takes a minute or two but it only has to be once (and ive actually made quite a few of them already thatll be ready to download off midigoblin.com to make things easier for people. all of the synths on my channel will have this txt file ready to go on day one) Its relatively easy to find this info in any synths midi implementation chart though if you want to add a synth that I havnt added on midigoblin.com. I've considered creating a wizard for adding new devices to take the leg work out of the process but realized entering the names of each parameter using the up, down, left, right buttons winds up taking exponentially more time than simply typing the list of numbers and names into a txt file. Having the parameter names is really quite necessary when it comes to using the midi lfo and theres a midi monitor in the works as well thatll make good use of the names (it lists each parameter name and their current value so you can troubleshoot things if need be). I could see this being annoying if you have boatloads of synths but for the average person, its about 5 minutes of set up time followed by a lifetime of being able to save patches. worth the effort.
bonus feature...I also created a little monitor that displays the midi cc number of anything received. So if your synths implementation chart is confusing and you dont know for sure what the number associated with a parameter is, you just need to plug your synth into midi goblin, move the slider, knob or switch and midi goblin will display the number for the paramter. Its pretty dang handy and automatically switches between midi cc and nrpn depending on whats been received.
Woww The fact that it can display received MIDI CC numbers is pretty impressive! I have few hardware synths(they all have MIDI chart) and I don't mind entering the numbers manually. My problem is with plugins. They can receice MID CC (via Midi Learn), their implementation chart is not available in general. I hope MIDI Goblin can receive CC numbers from plugins like it does from hardware synths. In any case, I am funding the project! P.S. Great update on the sequencer. I believe the Sequencer and the Arp could be its another selling point. btw to save the running Arp into the Sequencer would be a great feature.
@@spacekid5609 what plugins are you running and in what program? In general after a plugin has learned the midi cc's numbers of controller, the program hosting the plugin or vst should be able to save the learned cc numbers and also save their values(patches). Also are you running the vst on a pc or in one of those new arturia thingamabobs?
Thank you for your interest. I am using Tracktion Waveform and my hardware controller is Novation SL MK3. I use various VSTs on a PC. Yes, the DAW is able to save learned MIDI as plugin presets, but if a plugin gets updated it gets forgotten. SL MK3 has a software where you can enter MIDI CC numbers and save them templates. It is much more convenient for me this way. That's why I need to know those CC numbers.
Love the changes. Especially putting the note names in - seems simple but I'm excited about it. Can't wait for my green one!
that multitask is awesome. itd be incredible to be able to send the lfo to multiple CCs. or run multiple lfos simultaneously
this is something that has been suggested by a few people. theres a couple extra features im going to try to add to midi goblin before shipping (more info on that down the road) Theres definitely a way to run more than one instance of a midi lfo in theory, though to prevent flooding the synth with midi messages the speed and resolution would probably need to be decreased per midi lfo (i think) - on that note, running multiple instances of the sequencer might be possible though i havn't tried this yet...
I just saw this project with 20 hours left. There are just over 15 hours left. I'll be backing in like 2 hours when I get out of work.
ah sweet glad you found it in time! thanks :)
Missed your Kickstarter but have been watching closely in hope that there might be other opportunities to grab me a Goblin. Any news?
im interested also, especially in green option:)
Oh you know it
ruclips.net/video/8_KB-aKXKiM/видео.htmlsi=s8wTGhNEfsappNps
Great project. I am a 0 knowledge midi aquantaince. Can the goblin be used with guitar pedals with midi out and/or midi in? Thanks
It can definitely transmit cc and program change messages to guitar pedals using the patch send feature.
but as for the goblin receiving messages from guitar pedals to trigger things (like turning on and off apps/sending patches) - no.....
that is to say not YET! I'm actually working on it....planning on re-using a lot of the code from the user defined buttons for this. A few people have requested this feature so Im definitely adding it. Writing the triggering function for it is really simple, but presenting the info on screen, setting things up so multiple triggers can be added and saved to the sd card is a bit tricky.
Ill be posting an update specifically about this feature when its done. Honestly i dont own a midi pedal so Itll have to wait until a couple weeks after the campaign ends before i can order one (im on a real shoestring budget until then!)
Update: yes it can
ruclips.net/video/8_KB-aKXKiM/видео.htmlsi=s8wTGhNEfsappNps
Great job!
As I understood, synths/plugins should be able to receive MIDI CC for MIDI Goblin to save a preset.
Do we also have to KNOW those numbers?
My question is if Goblin can save with MIDI Learn function from a DAW? (In this case we don't really see the CC numbers but the hardware controller still gets connected)
edit: we only need to know the parameter numbers. not their values. midi goblin listens for any and all midi cc messages and keeps track of values for parameters users define.
Yes we need to know those numbers (of the parameters)but thankfully you only need to know them for a few minutes. Adding devices requires listing the numbers and their parameter names in a txt file and dragging it onto the goblins sd card. Takes a minute or two but it only has to be once (and ive actually made quite a few of them already thatll be ready to download off midigoblin.com to make things easier for people. all of the synths on my channel will have this txt file ready to go on day one)
Its relatively easy to find this info in any synths midi implementation chart though if you want to add a synth that I havnt added on midigoblin.com.
I've considered creating a wizard for adding new devices to take the leg work out of the process but realized entering the names of each parameter using the up, down, left, right buttons winds up taking exponentially more time than simply typing the list of numbers and names into a txt file.
Having the parameter names is really quite necessary when it comes to using the midi lfo and theres a midi monitor in the works as well thatll make good use of the names (it lists each parameter name and their current value so you can troubleshoot things if need be).
I could see this being annoying if you have boatloads of synths but for the average person, its about 5 minutes of set up time followed by a lifetime of being able to save patches. worth the effort.
bonus feature...I also created a little monitor that displays the midi cc number of anything received. So if your synths implementation chart is confusing and you dont know for sure what the number associated with a parameter is, you just need to plug your synth into midi goblin, move the slider, knob or switch and midi goblin will display the number for the paramter. Its pretty dang handy and automatically switches between midi cc and nrpn depending on whats been received.
Woww
The fact that it can display received MIDI CC numbers is pretty impressive!
I have few hardware synths(they all have MIDI chart) and I don't mind entering the numbers manually.
My problem is with plugins. They can receice MID CC (via Midi Learn), their implementation chart is not available in general.
I hope MIDI Goblin can receive CC numbers from plugins like it does from hardware synths.
In any case, I am funding the project!
P.S.
Great update on the sequencer.
I believe the Sequencer and the Arp could be its another selling point.
btw to save the running Arp into the Sequencer would be a great feature.
@@spacekid5609 what plugins are you running and in what program? In general after a plugin has learned the midi cc's numbers of controller, the program hosting the plugin or vst should be able to save the learned cc numbers and also save their values(patches). Also are you running the vst on a pc or in one of those new arturia thingamabobs?
Thank you for your interest.
I am using Tracktion Waveform and my hardware controller is Novation SL MK3. I use various VSTs on a PC.
Yes, the DAW is able to save learned MIDI as plugin presets, but if a plugin gets updated it gets forgotten.
SL MK3 has a software where you can enter MIDI CC numbers and save them templates.
It is much more convenient for me this way. That's why I need to know those CC numbers.