piz midi looper (beta!)
-
- KVRAF
- Topic Starter
- 2237 posts since 12 Nov, 2002 from swordfish
you can double-click the big name to rename the loop. this will also be used as the filename.
i guess what you want is fixed-length recording, as in pressing record once and having it stop after a certain length of time. this was always part of the plan, but i never got around to it... i'll see what i can do.
i guess what you want is fixed-length recording, as in pressing record once and having it stop after a certain length of time. this was always part of the plan, but i never got around to it... i'll see what i can do.
wrongtastic, baby
tucson's number one gothic rock band since 1995
tucson's number one gothic rock band since 1995
-
- KVRAF
- 6111 posts since 18 Oct, 2007
Very nice! It works perfectly.insertpizhere wrote:you can double-click the big name to rename the loop. this will also be used as the filename.
Not sure of the Juce implementation, but you could consider adding a loop that scans the files within the midiloops folder that would retrieve the specified files names. Then you could add down/up arrows and or a selectable dropdown menu that would display the next/prev saved file one at a time. Would make it easier to recall a given file
I was confusing Loop Step Size with a fixed recording length. The length aspect is fine then, just needs a way to auto stop. Your suggestion sound exactly what it needs. Hope its not a difficult addition.insertpizhere wrote:i guess what you want is fixed-length recording, as in pressing record once and having it stop after a certain length of time. this was always part of the plan, but i never got around to it... i'll see what i can do.
I do notice that (in FL8) if I have a selected area or loop playing it only records within the loop bounds. The downside is if you go over the loopbounds it resets the startpoint of recording. Perhaps stopping at the end of the loopbounds can be an option.
Anyway I'm having tonnes of fun with this
edit:
Not sure if this is on purpose but I can't access the file name input section if the host is playing. This is probably going to be hard to resolve but would make playback switching 'on the fly' if possible.
-
- KVRAF
- 6111 posts since 18 Oct, 2007
-
- KVRAF
- Topic Starter
- 2237 posts since 12 Nov, 2002 from swordfish
i can probably fix that, but if you just want to switch between playing different midi files, you can use vst programs. there's no selector on the gui so you have to do it from the host.Optomadic wrote:Not sure if this is on purpose but I can't access the file name input section if the host is playing. This is probably going to be hard to resolve but would make playback switching 'on the fly' if possible.
wrongtastic, baby
tucson's number one gothic rock band since 1995
tucson's number one gothic rock band since 1995
-
- KVRAF
- 6111 posts since 18 Oct, 2007
I just tried this and it does switch but theres a huge pause when loading the preset.
I was able to trick it by loading a file then entering a new name (of a pre recorded file). When I playback I get the current loaded file and then when I hit load again the file from the entered name loads immediately insync.
Hmm what about drag and drop of the file onto the GUI...
I was able to trick it by loading a file then entering a new name (of a pre recorded file). When I playback I get the current loaded file and then when I hit load again the file from the entered name loads immediately insync.
Hmm what about drag and drop of the file onto the GUI...
-
- KVRAF
- 6111 posts since 18 Oct, 2007
Found some bugs.
Can only load one instance in FL8. Opening a 2nd crashes it.
**edit**
This is the reason why it crashed earlier when I tryed to open it as an instrument in FL. Tryed to open it again be itself as an instrument and it work. So scratch what I said before.
**
Can open unlimited instances in eXT main window. Crashes if I try to open more than one in a sequencer track.
Can only load one instance in FL8. Opening a 2nd crashes it.
**edit**
This is the reason why it crashed earlier when I tryed to open it as an instrument in FL. Tryed to open it again be itself as an instrument and it work. So scratch what I said before.
**
Can open unlimited instances in eXT main window. Crashes if I try to open more than one in a sequencer track.
-
- KVRAF
- Topic Starter
- 2237 posts since 12 Nov, 2002 from swordfish
wrongtastic, baby
tucson's number one gothic rock band since 1995
tucson's number one gothic rock band since 1995
-
- KVRAF
- 6111 posts since 18 Oct, 2007
Ok everything seems to work exactly as it should now
.
The memory slots are a great addition
. The fact that they save direct to MIDI files makes this an extremely flexible feature.
About I/O chn on the Thru. Don't understand that right now. I tried using it to block thru after I record and I get 0 events. Will keep messing with it. I'm sure I'll figure it out.
I know I keep bringing this up but any chance for an auto stop feature on record?
To make it a tad easier on you it could stop when the end of a loop is reached. I mean if you consider that if you have loop bounds of say 2 bars long, and you record over that now it resets the recording head now anyway and starts recording a brand new take. Maybe this could instead send a command to stop the record and kick in the 'loop after rec' trigger.
It can be kind of difficult to try to stop the record manually right at the end of a given loop, especially if its being played live, and this can mean the loss of a good take. I'm sure you know what I mean right?
Anyway, cant wait to try to create a full song with it (just to see if it can be done). I think this will perfectly aid my other experiment I was telling you about earlier. Will pm you on this soon.
This is the makings of a really innovative, useful, and intuitive plugin Piz! Please please please keep up the wonderful work.
The memory slots are a great addition
About I/O chn on the Thru. Don't understand that right now. I tried using it to block thru after I record and I get 0 events. Will keep messing with it. I'm sure I'll figure it out.
I know I keep bringing this up but any chance for an auto stop feature on record?
To make it a tad easier on you it could stop when the end of a loop is reached. I mean if you consider that if you have loop bounds of say 2 bars long, and you record over that now it resets the recording head now anyway and starts recording a brand new take. Maybe this could instead send a command to stop the record and kick in the 'loop after rec' trigger.
It can be kind of difficult to try to stop the record manually right at the end of a given loop, especially if its being played live, and this can mean the loss of a good take. I'm sure you know what I mean right?
Anyway, cant wait to try to create a full song with it (just to see if it can be done). I think this will perfectly aid my other experiment I was telling you about earlier. Will pm you on this soon.
This is the makings of a really innovative, useful, and intuitive plugin Piz! Please please please keep up the wonderful work.
-
- KVRian
- 1492 posts since 29 Apr, 2004
Optomadic wrote:Ok everything seems to work exactly as it should now.
The memory slots are a great addition. The fact that they save direct to MIDI files makes this an extremely flexible feature.
forgot about this very nice plug. nice to see this improvement.
thanks!
-
- KVRAF
- Topic Starter
- 2237 posts since 12 Nov, 2002 from swordfish
the "i/o channel" is the same as "channel" was before (input filter, output transformer). it's separate from the thru button, just grouped because they're global midi settings. what i did is add a new channel setting only for the note triggering.Optomadic wrote:About I/O chn on the Thru. Don't understand that right now. I tried using it to block thru after I record and I get 0 events. Will keep messing with it. I'm sure I'll figure it out.
you mean when the host is looping? that makes sense. if it detects that the host went back in time, it should stop recording.I know I keep bringing this up but any chance for an auto stop feature on record?
To make it a tad easier on you it could stop when the end of a loop is reached. I mean if you consider that if you have loop bounds of say 2 bars long, and you record over that now it resets the recording head now anyway and starts recording a brand new take. Maybe this could instead send a command to stop the record and kick in the 'loop after rec' trigger.
It can be kind of difficult to try to stop the record manually right at the end of a given loop, especially if its being played live, and this can mean the loss of a good take. I'm sure you know what I mean right?
more later...
wrongtastic, baby
tucson's number one gothic rock band since 1995
tucson's number one gothic rock band since 1995
-
- KVRAF
- 6111 posts since 18 Oct, 2007
-
- KVRAF
- Topic Starter
- 2237 posts since 12 Nov, 2002 from swordfish
it only records and plays one channel at a time. i did this for simplicity, but eventually it will be able to record all channels, with an option to record each channel to a different slot, so after recording you could play them independently. of course by then it will also have to be able to play multiple slots simultaneously.
wrongtastic, baby
tucson's number one gothic rock band since 1995
tucson's number one gothic rock band since 1995
-
- KVRAF
- 6111 posts since 18 Oct, 2007


