Hey missed these?? Looking goodDarkStar wrote:Coming soon ... (probably)Lagrange wrote:PIZ I'm wondering can this (and your other plugins) work in MGUI by chance? I dont know if you've tried it at all..
L
.. Cant I just use Mgui to create this myself?
hmm so its being truncated.. I will have to know this as I'm going to put together either a frontside MIDI pool drag and drop toolinsertpizhere wrote:normally, everything you play while "Record" is on will be kept. the only exception is when you start recording near the end of a bar. i don't really like discarding anything, but it is "cleaner" if the recording starts on a bar line (or whatever step)... i already decreased the size of the zone where that feature applies... it may end up being adjustable.
that pulls from the midiloops folder or just an auto populate script for the eXT sequencers 
..sounds cool.Lagrange wrote:Ok so I like the MIDI loop dump to file! I'm considering making an auto import to eXT (1.41 & 2) sequencer app (using AHK) once the kinks have been ironed out...
i think midi thru is not very useful at the moment. i've been meaning to work on it. i haven't tested it for a while either, so there may be problems... for now i always have it off, and i use a separate plugin to control what goes through.- Record ON should probably trigger MIDI thru on (easier method to preview what your recording).
- I get strange pattern behavior in the playback after I switch MIDIthru to off.
- When I record with MIDI thru off the pattern totaly changes..
agreed... toggling record on and off without playing anything will clear it, but it should be easier.- Maybe there should be a way to clear a pattern and its corresponding MIDI file.
you should be able to stop recording a little late in the current version... or are you talking about something else? do you want long notes at the end to wrap around to the beginning of the next loop?- The 'end bar' cut off has to be as close to the end loop point as possible (I'm getting a lot of cut off notes toward the end)
maybe... i would also like to have this. i could make it a parameter, but a lot of hosts don't update the display of parameters when they're changed by the plugin...- I know theres no GUI but is there a way to show that something has actually been recorded by chance?
i don't like doing that, but i won't be offended if you rename them yourself.- Is there anyway of putting the version number in there (ie midiLooper_ver_4.dll) as I'm testing and comparing different iterations and getting quite confused!
loopstart and loopend will reset to 0 as soon as you record something. if you set them that way after recording, it will just play 8 beats of silence at the beginning and end of each loop.So far so good PIZ! Just have to address the pattern playback issues and the cutting off notes! Also I'm putting the LoopStart Point to -8 and end to 8. Is this correct?
Yea I'd rather code a VST for this but dont know howinsertpizhere wrote:sounds cool.
.. I can however kick ass in AHK AS2(flash) and AIR(multi platform) .. I'll see what I can do.I was routing it the same way. Just a simplicity thing tis alli think midi thru is not very useful at the moment. i've been meaning to work on it. i haven't tested it for a while either, so there may be problems... for now i always have it off, and i use a separate plugin to control what goes through.
...Again another ease of use angle..agreed... toggling record on and off without playing anything will clear it, but it should be easier.- Maybe there should be a way to clear a pattern and its corresponding MIDI file.
I was actually recording while playing eXT sync'd within AudioMulch's left and right loop bounds (4 bars). Dont know if this makes a difference or not...you should be able to stop recording a little late in the current version... or are you talking about something else? do you want long notes at the end to wrap around to the beginning of the next loop?- The 'end bar' cut off has to be as close to the end loop point as possible (I'm getting a lot of cut off notes toward the end)
Nah not necesary was just thinking it would be good to know that there something there.. No worries..maybe... i would also like to have this. i could make it a parameter, but a lot of hosts don't update the display of parameters when they're changed by the plugin...- I know theres no GUI but is there a way to show that something has actually been recorded by chance?
Ok cool I was already doing thati don't like doing that, but i won't be offended if you rename them yourself.- Is there anyway of putting the version number in there (ie midiLooper_ver_4.dll) as I'm testing and comparing different iterations and getting quite confused!
!!It this in the latest version? They stay at the same position for me huh??loopstart and loopend will reset to 0 as soon as you record something. if you set them that way after recording, it will just play 8 beats of silence at the beginning and end of each loop.
Haven't had a chance to play with this too much yet, so I don't really know how it currently operates. But, notes played slightly early and notes prior to the end of the loop that carry on for a while should be dealt with in a preservative fashion... A big problem with looping MIDI (for live-use) in Live (or whatever) is that this doesn't happen. Things disappearing or changing rhythmically because of a small mistake or intentional need to have the note last a while is no good at all.insertpizhere wrote: you should be able to stop recording a little late in the current version... or are you talking about something else? do you want long notes at the end to wrap around to the beginning of the next loop?
Yep you can (almost). mGUIman.exe will help you generate a default wrapper - with knobs. Then you edit the .skn file to reposition the knobs and change some to buttons.Lagrange wrote:DarkStar wrote:Coming soon ... (probably) <<snipped pic>>Lagrange wrote:PIZ I'm wondering can this (and your other plugins) work in MGUI by chance? I dont know if you've tried it at all..
L
Hey missed these?? Looking good
L
does this happen in all hosts? i haven't seen that problem in XT2 at least...ethnix73 wrote:while testing th last vesion of midilooper, i've found a bug:
For exemple, if you want to transpose a loop to one semi-tone up, the loop will be transpose before you reach the +1...if you want to transpose down, the same will happen, the loop will transpose before reaching the next value on the Gui.
It seems to happen to transpose, octave shift, loop start, loop end.
Concerning beat shift, if you reach the next or previous value on the Gui, it won't be applied. You need to go a further after the value appears on the Gui.
yes, that's on my list. there will be an option to remove any empty space at the beginning of a recording."does it help if you wait before playing the first note?"
Yes, it helps me. If i record a one bar loop (composed of four beats), i have to activate recording on the 4th beat. If i activate recordinf just before the first beat, my first note isn't recorded....This way, it works, but you have to anticipate. Being able to choose recording when the first note is played would be nice: Activating the record button will act as "arm recording"...Is this clear?
i have noticed that some synths don't play very well with this. i'm not sure why yet, but i'll figure it out. if you could see if it is caused by midi thru, that would be helpful.ethnix73 wrote:Another strange thing:
If i have got a loop played with the sequencer of XT2 through a synth (karma FX), and then i record a loop in midilooper to the same synth, some notes are not played...If i delete mdilooper, I've got always some notes played from this loop recorded in midilooper ( notes sems to be played in a random way, or it can be only a short attack sometimes).
Don't know is this could come from midi thru wich is activated in midilooper.
tested with XT 1.4, and it's the same
so, how long before the start should it look for the start of notes, and how long after the end? i agree, it would be really nice if those overhanging notes would overlap the previous and next loops... i'll see what i can do.contrast wrote:Haven't had a chance to play with this too much yet, so I don't really know how it currently operates. But, notes played slightly early and notes prior to the end of the loop that carry on for a while should be dealt with in a preservative fashion... A big problem with looping MIDI (for live-use) in Live (or whatever) is that this doesn't happen. Things disappearing or changing rhythmically because of a small mistake or intentional need to have the note last a while is no good at all.
probably. it might not work very well if the timeline is looped like that, especially if you're recording when it reaches the end and loops around again. i might have to optionally let it record for the full time (until the next loop length step) instead of cutting it off immediately when you turn it off...Lagrange wrote:I was actually recording while playing eXT sync'd within AudioMulch's left and right loop bounds (4 bars). Dont know if this makes a difference or not...you should be able to stop recording a little late in the current version... or are you talking about something else? do you want long notes at the end to wrap around to the beginning of the next loop?- The 'end bar' cut off has to be as close to the end loop point as possible (I'm getting a lot of cut off notes toward the end)
some hosts including eXT 1.x don't update the display of parameters very well, but the values are reset when you stop recording.It this in the latest version? They stay at the same position for me huh??loopstart and loopend will reset to 0 as soon as you record something. if you set them that way after recording, it will just play 8 beats of silence at the beginning and end of each loop.
So what if I have a section 4 bars and make the left and right timeline loop say 6 or 8 bars?insertpizhere wrote:probably. it might not work very well if the timeline is looped like that, especially if you're recording when it reaches the end and loops around again. i might have to optionally let it record for the full time (until the next loop length step) instead of cutting it off immediately when you turn it off...
this new version might fix it...ethnix73 wrote:"does this happen in all hosts? i haven't seen that problem in XT2 at least..."
I was testing with XT2
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026
