@thomasotto exactly! like a computer! like QC pretty much
… not here is another discussion! there is a problem and it is talked about a lotThis is how I do It :
- QC as the only audio interface in my macbook via USB.
- Set USB 5 on the QC input, USB 7 on the Output.
- In Logic Pro, I use the IO Plugin (used to Ping and measure external hardware latency, it’s like a console insert, doesn’t take into account the QC roundtrip latency)
- The IO plugin returns a sample number which I divide by the sample rate (48000) and then multiply by 1000 : (number of samples/sample rate) * 1000 or 1000 / (sample rate / number of samples) if you prefer
Is this a feature request at this point? There are already posts about this. I feel like it would be more valuable to consolidate your basic data @thomasotto, add it to an existing request, and then solicit people to vote to raise the attention for it.
As it is this is less about a feature request and more becoming like a gripe session which isn’t the point of this category.
4 Likes
But in this config you are measuring qc as audio interface via drivers comunication.
And this doesn’t rapresents the behaviour of qc itself
Or
Are you Shure that qc connected via USB has the same behaviour as standalone?
For me no.
Discussing, yep
2 Likes
I feel like it would be more valuable to consolidate your basic data @thomasotto
Already did that here
add it to an existing request
Already did that here
As it is this is less about a feature request and more becoming like a gripe session which isn’t the point of this category.
For me it was more about helping out and finding explanations & solutions than joining a “gripe session”
I’m out.
2 Likes
@Niksounds @thomasotto I measure like this:
- I plug the guitar into a Radial Shotgun Input
- Shotgun Output 1 to Neve preamp then to Pro Tools
- Shotgun Output 2 to Quad Cortex to Neve preamps to Pro Tools
I play various “hits” on different strings and also tap with a screwdriver on the pick ups poles so I obtain supersharp transients.
Press record of both tracks then measure the timing differences
Doing like this you have the true latency that the QC or other digital machines make VS the analog DI signal 
I drove a 1989 Opel Senator in the 90s and I loved it.
3 Likes
You make a solid point. Are there other existing feature requests for lowering latency? The title on this one is a little confusing due to the use of “solved” in the title, although it is aspirational and sums up the ultimate goal nicely. That said, at the very least the request could use a proper description, even if it is short and sweet, such as “minimize latency on QC across all paths, splits, block, loops, and global EQ usage”.
Latency is clearly an area of legitimate concern but no cause for panic. Just something that has to be constantly measured and reduced as the QC’s codebase matures. I am sure the developers are working towards it. It is one of those pieces of core functionality that isn’t as exciting as many of the other bells and whistles but is of vital importance to the QC’s usability.
I can see the QC’s potential and just hope reducing latency remains a priority over its entire lifespan, or at least until it is no longer of any consequence. I have some fairly well populated presets that I am happy with that present no showstoppers regarding latency.
Maybe this is one of those feature requests that should never be closed but used as a way to track positive milestones as execution time improves. More of an overarching goal for the device rather than a typical feature request per se.
This QC still goes “vroooom” when you hit the pedal. Just needs a little adjustment so turning on the air conditioner or windshield wipers doesn’t bog it down. It’s a sleek machine. 
3 Likes
Good measurement method
1 Like
More appropriate place for the current stream of information. Moving there would be just fine
@HonestOpinion I know that this is a pedalboard with great potential, I’m just saying that the neural instead of picking up where its predecessors like line6 left off, fractal kemper restarted at least 5 years ago! I hope for them that we are trying to solve the most serious problems of this QC such as latency, effects loop unity gain, preset swapping!!! and that in the next firmware they solve them and don’t put another 300 useless amplifiers as there are already enough good amplifiers! and let’s not forget that inside there is a vibe that really sucks! fingers crossed for the next firmware! 
3 Likes
In the title of this topic for “solved” I meant W O R K A R O U N D of course
Don t know if I can resist without using the 3rd row of blocks connected to the 1st! hehe
2 Likes
pochi ma buoni, concetto eterno =)
100% with you on that. In general, I think more attention needs to be paid to issues that involve more complex and populated serial routes on the QC. Those include getting rid of the stranded eighth block on rows 1 & 3 when using a splitter, allowing row1 to be routed from the output block to row2, and row3 to row4, without requiring a splitter, more I/O options for the output blocks, and of course optimization when all rows and many blocks are used.
Sometimes it seems like the QC started with a little too much sales focus on using it as a “band mixer/modeler” with each row being used for a separate musician/input/output. It is an outstanding tool for this, but I would wager that is not how the majority of users employ it.
2 Likes
@HonestOpinion but there are no administrators so we tag them and they see that the problem exists and is it serious!?
you can email the support, and link the forum discussion.
Then, I think that their explanation here would be a good thing
@HonestOpinion @Ringo it’s practically like having a Lamborghini and not being able to go more than 100km/h!
3 Likes