Tiker 1000 Real or Illusion?

[DigitalWhiteByte]

I think it is impossible to achieve, but the thing I do not understand is why the count of ticker100 go slower.

Edit: Uploaded new version.

[malc]

All the timer components use Windows timers. They are only accurate to about 10ms and can sometimes be even worse than that.

The reason they are inaccurate is because they use the normal Windows event system. Callback events are posted on the message queue alongside other Windows events like mouse, keyboard and commands. The timer events have a very low priority so during busy periods, where there are many other messages in the queue, timer messages can get delayed.

The timer components in SynthMaker are not intended for tasks where accuracy is required. They were originally introduced to provide a way of performing simple animation and for that purpose the inaccuracies are acceptable.

Hope this helps!

[DigitalWhiteByte]

Thanks Malc, in fact we have already addressed this issue at length,
but my hope is in the seriousness of the updates for this application,
to make sure in future the best existing solution for generating high-quality audio software,
the first step I think it is just that.

You are a great developer,
and the community is excellent, many people believe that this software will become a tool of professional development.

[mcfadden555]

we really need this tiker (1000 or higher)

[infuzion]

we really need this ticker (1000 or higher)

"Need"? For what please?

[mcfadden555]

We need it , to have the option, to trigger faster (Mono to Float) .....
I need a faster tick then 100 to finish one of my projects (My dream would be a tick44100, but 1000 ticks is also good -it would be an enhancement to 100 ticks......

I'm not the only one who need a faster Tiker.... there are many posts of people who want it....

I think:

faster Ticks = New Options for development

if you have the choice between a Ferarri and an Audi,

what car would you take ???

I want a faster Tiker !


musical greetings,

[monx]

Illusion

[mcfadden555]

why ?

[oddson]

Not necessarily a faster ticker (although it would likely become possible as well) but a means of sending triggers from the code module and having them actioned in a much more precise time-frame than is currently possible (i.e. relying on sampling a stream output with a ticker and an M2F) even if it's still not sample accurate.

The biggest area this would open (IMHO) is note event processing as currently the timing inaccuracies are far too great for musical applications.

Or full sample-rate accuracy for all events would be good.

[Tzarls]

http://synthmaker.co.uk/forum/viewtopic.php?f=2&t=8887&st=0&sk=t&sd=a#p62468

That would do it.

[infuzion]

We need it , to have the option, to trigger faster (Mono to Float) .....
I need a faster tick then 100 to finish one of my projects (My dream would be a tick44100, but 1000 ticks is also good -it would be an enhancement to 100 ticks.

Well if you need to process at sample rate, then use stream Code at sample rate.

Then only place where more accuracy is needed IMHO is for MIDI. And SMX/SM2.0 is supposed to do that.

[mcfadden555]

Thanks infuzion,
Thanks oddson,

Many thanks for your efforts and your quick reply.

Do you mean : stream the mono in (with 44100 hz) to float ???

it sounds to me like a ray of hope.
do you have an example OSM/ or Picture or do you know somthing like that in the Forum ???

musical greetings,

[rl]

Why would you want a float with changes at samplerate? Tell us, what you want to accomplish, and we might find a solution.

[mcfadden555]

I hope you do not understand me wrong.
I do not want to talk about my idea and for what I need it.
because my idea should remain my.
I hope I have said clearly enough what I want.

you said it:

I want a float with changes at samplerate (mono to float in samplerate)

I just want to know, is it possible ???

[trogluddite]

A float changing at sample rate is a stream. The green floats could never run at anything like that speed because of the overhead of passing the triggers through the schematic (to calculate which calculations need calculating - if that makes sense?) - your CPU would melt down!
Code is the only way to go - a code module is executed at sample rate by definition.
The limitations this imposes on MIDI and the GUI are well known, but unavoidable at the moment - the division between sample rate streams and 'run on demand' green/GUI is part of what makes SM relatively user (and CPU) friendly - IMHO, the way this opens up VST design to amateurs is a key point of SM. To have the kind of power/flexibility available to people like Native Instruments, there's nothing for it but to program in C++/ASM.

The Luddite.