Clockramp not reliably running.

[d.healey]

@Christoph-Hart That's really nice :D

[lalalandsynth]

@Christoph-Hart Excellent I was having a problem with seeking and loop points !

[lalalandsynth]

@Christoph-Hart After building this version I cannot export my plugin.
Has not been a problem before although I dont know if its related to the new version?

As for the feature itself.
Seeking seems to work in HISE (cannot export and test in daw)

As far as I can tell the loop feature does not work.

When this counter hits zero , it crashes , what is this counter btw?

[d.healey]

@lalalandsynth The answer I think is in the message. You have shared code (intermediate files) from a previous build. Try cleaning the build folder before compiling.

[lalalandsynth]

@d-healey I am a bit insecure when it comes to that , what should I delete specifically?
Is that cleaning just needed because I updated HISE ?
I always just built without cleaning anything ?

I have seen the yellow warning before but it built without problems, seems like the red text is the problem.

[d.healey]

@lalalandsynth In Visual Studio there is an option in the build menu to clean the build. If in doubt you can just delete the binaries folder (assuming you don't need anything in there)

[lalalandsynth]

@d-healey I am building via HISE, not sure how to build a plugin with VS.
Deleted the build folder and I get this.

[d.healey]

@lalalandsynth

I am building via HISE

No you're not :p

All HISE does is run visual studio for you. That's what that black terminal window is that pops up. Open the Autogenerated.jucer file in Projucer and it's just like building HISE.

I'm not sure about that second error.

[lalalandsynth]

@d-healey Yes, I was aware of that, just not aware of how to build it manually in VS, thanks for the tip :)

Yep, the red message is the showstopper and started after I updated to the latest version to test this.

[d.healey]

@lalalandsynth How many copies of the HISE source code do you have? :)

[Christoph Hart]

@d-healey Actually there was an issue with compiling the plugins but I've fixed this just now.

There was also an issue with the default tempo set to -1 BPM, but that is also resolved.

[lalalandsynth]

@d-healey Stopped that bad practice, one folder via github, get new version , build. :)

[d.healey]

@lalalandsynth No t-shirt for you then :D

[lalalandsynth]

@Christoph-Hart Am I right that the looping does not work ? It does not seem to work in HISE but I can build again, export and test in daw.

[Christoph Hart]

@lalalandsynth Does the playback ruler move in the new display? If it's set to -1 (or 30 which is the lowest value of the tempo slider), it won't move and play. Try moving the tempo slider up to 120BPM or something (or recompile HISE which fixes the default value).

But you shouldn't need to export to the DAW to test this (this is the entire point of this new feature). Ideally it behaves 100% like from a DAW as it basically creates the same playhead that is picked up by the internal rendereing as a sane DAW would do (it even splits at the loop point to make sure that the looping is sample accurate like REAPER and Ableton do).

[lalalandsynth]

@Christoph-Hart oh I see . It seems to work now !
Seeks and loops in Reaper ...way awesome, this was the only thing left for our plugin, thanks so much and have a happy new year :)

[lalalandsynth]

@Christoph-Hart Quick suggestion , being able to drop an audio file or midi onto that timeline would be amazing ;)

hehe.

[Christoph Hart]

Actually why not? :) I thought about that too already so maybe it's a good idea.

You can now drop audio and MIDI files on there and it should play (the audio files will also play through the master container so you can simulate the FX signal flow better).

There's a context menu where you can save the current timeline as default which will get restored when you load up HISE.

[d.healey]

@Christoph-Hart HISE edges closer to being a DAW :)

[Christoph Hart]

FL Studio here I come!