Transparent Tap Tempo means changing a tempo while a delay is on doesn’t cause the realistic warping effect of delay repeats. Not all delays have that behaviour, but on most modelers you can select whether that effect happens or doesn’t.
1 Like
first of all, thanks for joining this conversation . it was much appreciate as you can see.
i will speak for myself and ill be as honest i can be.
i really hope those words are truth. i mean no disrespect when i say it.
i love your products , and i am sure there are many here like me that given up a lot to be able to afford the QC.
that is exactly the reason i am still on the fence at the moment. only time will tell if things will go differently . (i don’t say it lightly)
for now, this is a step for better relation between us the customers and you .
if i may, i would like to suggest , since a lot of us are very active here , and the way i see it , our wish is your goal to make the QC the best it can be, maybe consider to add us to the testers to help with the progress of the QC.
I am Japanese.
I am using a translation tool, so my English may be funny.
I purchased this item in the initial stages, although it is not a pre-order.
Unfortunately, Japanese users think the same way as james.tan.
Several of my friends have given up their products because they are dissatisfied with the way Neural disseminates information.
I like the product very much, but the current situation makes it difficult for me to recommend it to interested users.
I don’t see delay in updates as a sin.
What is a sin is not speaking out “late”.
For example, if you send out information “soon” and then have a problem, you can send out a statement right away saying that the update is going to be delayed.
When we, the users, are in a situation where we have no answers, it leads to debates and fights.
If the official says one word, “It is delayed,” the discussion will be settled, saying, "Since it is delayed, let’s wait.
There is no problem with multiple reports of delays.
The most worrisome situation is when no information is sent out. Users will feel ignored.
Of course, Neural does not have to disclose all information. Everyone understands that major updates take time and cause trouble.
However, many users expect to hear “soon” or “soon”.
Currently, QUAD CORTEX is not available with the originally planned features. Once a set of features are updated, users will be less sensitive to updates.
Once the features that were announced in the product description are included, the number of users fighting about the update should decrease.
Some are waiting for the plug-ins to be included, while others, like me, want the marketplace functionality. (Many people seem to want a system to send paid RIGs in bulk.) Right now, I have them sent one at a time. I like to buy professional paid RIGs. Hahaha.
In any case, I think the safest thing to do is to publish a roadmap, even after the 2.0 update is done it will be fine - spring 2023, summer 2023, winter 2023, after 2023, etc.
Plug-ins are harder than you think, and I think it is safe to answer that they are not on the horizon for loading. I hope no one comes forward with a lawsuit…
If the commitment to update every two months is also difficult, I think you can reschedule.
Ideally, once 2.0 is released, we should reset and announce a clear policy for the future.
Through QUAD CORTEX, I have made new friends in Japan and friends overseas on Facebook. I am very grateful. We look forward to receiving your information so that we do not become separated from those friends.
7 Likes
Honest question, and I’m really not trying to stir anything so I really hope it’ll coming across that way.
What did he say that you didn’t already know? He reiterated the same updates that have already been shared. In many cases, word for word from the original updates published over the past months.
His follow up question appears to be asking the same thing I am.
Was it just that he engaged and you knew your frustrations were being heard? Even if he had nothing new to share at all? I’m not at all saying that’s a bad request or need. I’m just trying to understand.
1 Like
I appreciate your contributions here, I would not have wanted the topic closed before you had a chance to voice them. I am on general principle pretty much against a fellow forum member, or even a moderator, deciding unilaterally when a topic should be closed. For the most part, I think closing of topics is over utilized. When the moderators’ prerogative to close a topic is exercised, it should be for policy reasons, you know, rule of law, not the divine right of kings.
Unless a topic has descended into rudeness, misinformation, or is a technical question that has been definitively answered, just let it age out. I probably neglected to mention a couple of other legit causes for topic closing but those describe some of the major ones. Most topics left to their own devices will naturally and organically fall down low enough in the queue not to be reposted to. Just as effective as closing/locking without the taint of censorship.
As this forum gains more members, as one hopes it will, it becomes more and more difficult to predict when everyone who has something to contribute to a topic has finished chiming in. Leave the opportunity open for them to do so. Take a look at how many more views this particular topic has than most on the forum. Clearly there is enormous interest here and it makes for a healthier dialog.
This topic has been a breath of fresh air and elicited more direct involvement from NDSP. I cannot think of a more positive outcome (other than the 2.0 update dropping, heh). Hearing the, dare I say, honest opinions here is refreshing. I hope it ushers in a new standard as to what a healthy forum should look like.
5 Likes
Dan, thanks for the updates and info. Add to that we need to hear from you more than every quarter year and the beer is on me…
3 Likes
@anon22728977 and everyone else, let’s be very careful not to get riled up about a desktop editor [yet] if NDSP have not explicitly stated that it will be included in 2.0.0.
… it was at least “mentioned” in Development Update - June 2022.
For sure. We know it’s being worked on. But just as Hybrid mode and the redesigned file manager are explicitly called out to be included in the CorOS 2.0.0 update, in the same June 2022 development update, the desktop editor is not. Just trying to save some people a lot of heartbreak.
@HonestOpinion I brought “closing” into consideration, because the subject of this Thread has been met. Personally I would rather prefer having a general discussion board that also can be found when searching for future release informations and discussions…
… and on the other hand it was my very first post in a forum. For me it is quite exhausting to hold up the thin line between people expressing their concernes in a reasonable way and not beeing a moderator… which maybe also was an important component. (if a moderator would have asked for staying with the topic I assume it would be read differently)
But I am open for all opinions regarding closing of threads. 
1 Like
I’m low key hoping it gets rolled out real quick but not counting on it
Bumped it, but feel free to upvote (or whatever the appropriate term is) the feature request ha.
Yup, this is a pretty critical feature if you want to provide max flexibility when switching tempo, or even delay settings between scenes without getting wacky alien noises the way you might when quickly twisting a knob on an analog delay pedal. Hope it is in their development queue. Or… maybe you are looking for alien noises and don’t want “transparent” mode.
1 Like
At the risk of going off topic here - I find myself needing both.
Transparent should only affect tap tempo / scene changing / preset changing.
Turning of knobs should still keep the ‘accurate’ response. I do use the self oscillation every once in awhile.
1 Like
Definitely what I was getting at, the more options regarding this, the better.
You posted a question in a public forum, so I posted an answer publicly. Cheers.
1 Like
Hi Dan, I wonder if you could shine some light on the upcoming new NDSP Power Supply for the QC ?
It`s been said that this is in the works and have been said in e-mails to people that this is being worked on, and that this Power Supply is going to take away the Hum problem ( floating power supply )
As I have this Hum problem…it would be good to know.
Yes I can/are using the Input Gate option, but I would like to know that I don`t need to use CPU on this in the future.
Hoping to get some news on this
Kind regards
Morten
That. Especially while being the company’s official forum used by their customers for the most part.
4 Likes
I think, that the update given by Dan was everything I wanted right now. A Q&A would be a good idea, too.
As for the complaints: I got one two month ago and bought it without the promises made, before the release.
For my taste it’s everything I hoped for it to be. Great connectivity, great sound and great UI.
I had a Helix, a Ampero 2 and used multiple vst-Plugins from Neural/TH-U and others.
If the communication get’s better, for me, they’re absolutely nothing to complain. It speaks for Neural, that they reacted and try to get better.
The release windows given, were out of excitement. At least that’s how I perceived them. So it’s goo to see dedicated and motivated people at work.
6 Likes
Good move from Dan and NDSP. I appreciate the hard work on the device I value so much. Keep up the good quality and reliability of the software!
Cheers
1 Like