HziLooper by HZI Tools

[audiojunkie]

nope, 1 shot mode is not implemented atm. There are midi options (check them.on file menu) for chromaticaly playing all loops with keys - also a "trigger" mode for your white keys. Mute and Solo each is also available. Somehow performative, but not really synced triggering.

But i know what you mean now, i already thought of optional more loop circles per track (you can iterate between them) , to make even 1 instance of hzilooper super performative and flexible. But this is the funny part, you are not limited in Instances, yeah, could also drop 8 Plugin Instances and similar result. It would break somehow my 1 Interface Window Idea, but also those implementations wouldnt be destructive to this. Many ways to use it
so...
- Optional Radio Button toggling for Track 1-8 triggers
- "play next" toggle.
Makes Sense, think i can implement it. Mute Solo is already available per track

Nice! Midi controllable, remember!

[herzihelmut]

Hi people,

quick update: I decided to kill the DRM heartbeat calls to server to keep this Plugin activated. You should be able to work fully offline if you wish to. And use it forever.
Should have known better since this was always a pain for me as user. wisdom comes with time, so...
You can DL V1.2.1 on https://hzitools.com/

Also v1.3 is in pipeline, this will be supercool (Scenes, Subloops, Audiojunkies Wishlist and more...).

BR Helmut

[audiojunkie]

Hi people,

quick update: I decided to kill the DRM heartbeat calls to server to keep this Plugin activated. You should be able to work fully offline if you wish to. And use it forever.
Should have known better since this was always a pain for me as user. wisdom comes with time, so...
You can DL V1.2.1 on https://hzitools.com/

Also v1.3 is in pipeline, this will be supercool (Scenes, Subloops, Audiojunkies Wishlist and more...).

BR Helmut

Oooh! Cool! So now there is no DRM? Or now there is DRM, but it is just a serial number or keyfile?

[herzihelmut]

Hi people,

quick update: I decided to kill the DRM heartbeat calls to server to keep this Plugin activated. You should be able to work fully offline if you wish to. And use it forever.
Should have known better since this was always a pain for me as user. wisdom comes with time, so...
You can DL V1.2.1 on https://hzitools.com/

Also v1.3 is in pipeline, this will be supercool (Scenes, Subloops, Audiojunkies Wishlist and more...).

BR Helmut

Oooh! Cool! So now there is no DRM? Or now there is DRM, but it is just a serial number or keyfile?

exactly,local license file generated from serial number, still DRM - but internet connection only needed on init activation, not a permanent license check on server - calls. This was a bad idea (still learned some stuff from it thou )

[URM]

Thanks for the update, looking forward to 1.3. Great that you killed the DRM heartbeat.

Would love to have a mix out knob for the stereo output. If possible, maybe meters or a clip indicator light for the mix output too. Looks like there's space in the bottom right corner of the GUI for it all.

Really nice looper, having a lot of fun with it.

[herzihelmut]

Thanks for the update, looking forward to 1.3. Great that you killed the DRM heartbeat.

Would love to have a mix out knob for the stereo output. If possible, maybe meters or a clip indicator light for the mix output too. Looks like there's space in the bottom right corner of the GUI for it all.

Really nice looper, having a lot of fun with it.

yes, you already noticed the free space, it cries for an output meter . Some basic end of chain compression maybe.
Glad you like it, which OS are you on?

[URM]

Awesome - was hoping that space wasn't reserved for something else. Compression would be great too as would a basic eq, but that might be too much to squeeze into that tiny spot.

Win 11 - so far it's been solid although I've had a couple of random crashes in the previous version. They seem to happen when engaging record sometimes, but it's random and rare as most times it records without problem. When it does happen, my host (Bidule) kills it's audio and pops up a warning to save now. Haven't tried recording yet in the new version as I got a nice loop going in the previous version and started building a piece around the loop, but I'll report back if these rare crashes continue once I get back to playing with the new version.

[herzihelmut]

Awesome - was hoping that space wasn't reserved for something else. Compression would be great too as would a basic eq, but that might be too much to squeeze into that tiny spot.

Win 11 - so far it's been solid although I've had a couple of random crashes in the previous version. They seem to happen when engaging record sometimes, but it's random and rare as most times it records without problem. When it does happen, my host (Bidule) kills it's audio and pops up a warning to save now. Haven't tried recording yet in the new version as I got a nice loop going in the previous version and started building a piece around the loop, but I'll report back if these rare crashes continue once I get back to playing with the new version.

are you recording via rec or with retrospective? Was LFO automation going on ?
I fixed 2 (rare) OOM problems in upcoming 1.3 already, maybe you faced this. Leaded to instant crashes. Its not a big deal, but distracting.
The new Version 1.2.1 does not behave differently, its only for the local licensing.

[URM]

Just by hitting the rec button in the loop ring. Not sure what retrospective is, but there were no re-recording or overdubs attempted on any of the loops. Not even sure if it can do sound on sound or what the looping time limits are as I've only skimmed the manual.

There were other loops going already and I was onto recording a 3rd or 4th loop when the crashes happened so I likely had lfos running on the previously recorded running loops. The running loops also would have had pitch, stretch and other tweaks.

It only happened a couple of times and second time was likely oom as I remember letting it record for a while and wondering about how long of a loop it would record so the record time was definitely a lot longer than the other loops. It crashed when recording was stopped. Fortunately everything was saved with the Bidule project including the loop I was recording. It sounded good, but I'm not sure if it was playing back the full time that recording was engaged or a truncated version if it ran out of memory when it crashed as I wasn't paying close enough attention to the recording.

Don't really remember the first crash other than clicking the record button, but I may have clicked the record button a few times in rapid succession which may have turned record on and off a couple of times quickly. It was my first time playing with it so I was just poking at things as I learned how it works. Again I had other loops going with lfos engaged and all were saved with the project after the crash.

So all in all nothing was lost other than time to save and reload which like you say is not a big deal, just distracting.

Hope this helps, but I'm guessing 1.3 already has fixed it so looking forward to its release. I'll report back if I can repeat the crashes or if anything else turns up.

Thanks for the support.

[herzihelmut]

Just by hitting the rec button in the loop ring. Not sure what retrospective is, but there were no re-recording or overdubs attempted on any of the loops. Not even sure if it can do sound on sound or what the looping time limits are as I've only skimmed the manual.

There were other loops going already and I was onto recording a 3rd or 4th loop when the crashes happened so I likely had lfos running on the previously recorded running loops. The running loops also would have had pitch, stretch and other tweaks.

It only happened a couple of times and second time was likely oom as I remember letting it record for a while and wondering about how long of a loop it would record so the record time was definitely a lot longer than the other loops. It crashed when recording was stopped. Fortunately everything was saved with the Bidule project including the loop I was recording. It sounded good, but I'm not sure if it was playing back the full time that recording was engaged or a truncated version if it ran out of memory when it crashed as I wasn't paying close enough attention to the recording.

Don't really remember the first crash other than clicking the record button, but I may have clicked the record button a few times in rapid succession which may have turned record on and off a couple of times quickly. It was my first time playing with it so I was just poking at things as I learned how it works. Again I had other loops going with lfos engaged and all were saved with the project after the crash.

So all in all nothing was lost other than time to save and reload which like you say is not a big deal, just distracting.

Hope this helps, but I'm guessing 1.3 already has fixed it so looking forward to its release. I'll report back if I can repeat the crashes or if anything else turns up.

Thanks for the support.

retrospective rec: you can left click the separated windows (1/4 - 4) Bars where the audio visually comes in to "grab" the loop immediately and assign it to a loop circle. You can also midi map the grab areas. super flexible way for looping, cherry pick looping you could call it also

You could have faced thos OOM issue i was talking about. Patch is on the way.

Regarding Looping Time: Max 60 Seconds, but you are able to drag in much longer loops if needed.
This is still somehow inconsistent but works for now. Think about to limit it to 40 sec, because:
In future Subloops will join: Mainloop + 3 additional subloops which can not differ in length, but are mutable. You can also activate stacked recording to them (if needed) and drag drop merge as you wish, also to free up space again.
Also 8 Scenes / Tracksets will join, so you have 8 Scenes * 8 Tracks, each Track contains 4 subloops. AND Undo/Redo buffer for each circle.

So memory allocation is a thing here, had to make it more robust for this architecture , not prereserve anything which is not needed.
So if you have 6GB RAM for hzilooper, you are able to build a complete set in it in future, Ableton Style. You can still use it with only 1 Scene like it is now if not needed, so this will be no destructive addition, just a possibility.