Reminder: The best way to report bugs is to email Dreamtonics

If they don’t come here during the beta phase at least to give a cursory glance then they are more narcissistic than I had ever given them credit for. No, I’m not being inflammatory for fun. If they really care whether their code runs as best as possible then they would gather feedback from wherever they could. They don’t even have to engage us.

Why not at both places it helps everybody up and down the line I could sit here for hours working on a problem and then read about sombdy else with the same problem instantly and I know it’s not just me, it would take hours or days before your people would get back to me.

Yep, that’s why I recommended linking to your forum post in your email to support in addition to describing the problem.

Plus if they get more emails saying “hey I’m having this issue, I also made a forum post about it” maybe Dreamtonics will be more inclined to monitor the forums in the future.

I’m just a user, I have no affiliation or connection to Dreamtonics.

Then how did your post get pinned/banner’d to the top?

I think @LinR_PN has the ability to do that, and they’ve been the one to pin important posts in the past. My forum role only gives me the ability to recategorize and retag posts.

Both of us are still just users though, I’ve personally never spoken directly to anyone from Dreamtonics, except for receiving confirmation after reporting bugs by email.

I’ve sent email to support at dreamtonics, but that was a few weeks ago, and no response. I wonder if anyone actually reads them. The biggest shortcoming with Synthesizer V remains its inherent inability to sync to tempo tracks in DAWs, namely Logic. For that reason alone, I find Synth V unusable. No way to line up midi markers and bounce any SV tracks down for use in anything like MainStage. No sync, no use. Had I known about this issue when I first saw SV, I would never have purchased it. Let me know if you ever hear from Dreamtonics about solving this problem. Until then, this is just a kid’s toy.

We should all be grateful for all Mr.Hua has given us.
I can’t sing for s**t.

But the culture has become very black box since Dreamtonics. This is unfortunate and might be their ultimate demise should another entity come along with the goods and excellent installed base relations.

I don’t expect Karu to engage us as historically, engineers don’t make good marketers due to the fact that we tend to blurt the truth. Hardware and software can’t lie, if it does, it doesn’t work right and nobody will buy it.

Dreamtomics and the installed base all owe a debt of gratitude to our Claire as good heavens, Claire does all this babysitting and is not apparently marched out here by corporate.

I can’t speak to how they decide which emails to respond to, but they do at least read them. I received this response to a bug report regarding 1.9.0b1:

Dear Claire,

Thank you for reaching out.

We have forwarded your issue to our dev team for consideration and fixing it when further optimization is possible. We hope you have a nice day.

Best,

Dreamtonics Support Team

On a separate note, I would expect your issue is unlikely to be addressed anytime soon. This is largely speculation, but is based on the nature of the limitation. It might be one thing to implement ARA2 and detect tempo changes from an entire timeline and automatically insert tempo changes in SynthV Studio, but adapting to Logic Pro’s Smart Tempo feature is a whole other endeavor.

For most people, the tempo limitations are a minor inconvenience in which you enter a handfull of markers manually and call it done. Smart Tempo in Logic Pro only seems to have existed since 2018, and it seems very few DAWs have a comparable feature (Ableton Tempo Follower is the only one I found in a quick search, which was introduced in 2021).

Since SynthV Studio is not a real-time synth and needs to render the output before playback starts, I expect it would be a major obstacle for it to match a tempo which is constantly changing in unpredictable ways. I would love to say something more optimistic, but it seems unlikely to be prioritized when it’s such a niche use case.

I wonder rhetorically if GPU rendering has been tried in the lab at DT

… Narcissistic? For what, expecting bugs to be reported via email? Bugs only found in an opt-in beta version???

GPU = email
I fail to follow you …

Don’t follow me. I don’t know where I’m going.
GPU: Graphics processing unit = High speed rendering graphics card that can be harnessed for auto processing too.

Dreamtonics has created a Google Form to collect feedback about the latest Pitch Mode changes:

Thanks. I shared my feedback with them there. Hopefully they’ll listen.

Is DAW and SynthV set to the same tempo?
I have exported .wav files from stand-alone SynthV and they run perfectly in sync as wav imports (yes, I know…) on my el-cheapo DAW for a three minute song

Is there any info of use to you in this old thread…
Midi and Instrumental Track out of sync - Uncategorized / 未分类 / 未分類 - Synthesizer V Forum

I’m starting from a track that’s already in Logic, not SV. The tempo changes a lot, and because SV’s tempo control is so simplistic, it can’t stay in sync. Even if I produced a static wav from logic and pulled it into SV, I don’t see a way to make a tempo map inside SV that’s going to work. I guess it might be possible if I could turn off all concept of tempo in SV and use absolute times, but that would be extremely unpleasant to work with, having to align every beat in milliseconds manually! I’m also quite likely to want to change the tempo, or reorder parts of the song, and not be nailed to sync with a fixed audio file. All this is standard production processes, it’s not like it’s anything new. I understand that some tempo things might be tricky (like Logic’s smart tempo, which I’m not using), and I would be quite happy with it working with some limitations, but at the moment I literally can’t even get a single note to play in time – starting from the same initial tempo, by the time the first sung note arrives, SV is already over a bar out of time.

That article is suggesting something very simple – if you have a fixed tempo for the entire duration of the song, it can stay roughly in sync, but this is more coincidence than any real sense of sync. I do have some tracks that are like that, but not the main one I hoped to use SV for, which contains a tempo map extracted from a live performance, and doesn’t maintain the same tempo for more than a couple of beats at a time.

So you want to write in the DAW in free time and somehow have SynthV know the whole tempo map in order to render the vocals which is not instantaneous? I agree this would be super-cool.
I realise any synth or sample player will follow tempo, but they are fundamentally different insomuch as they are retriggered note-by-note. SynthV, by its very nature has to render the whole file in advance.

Most plugins are little more than signal processors (or generators). They accept either MIDI input or an input signal, and then create or modify the signal accordingly in real-time.

SynthV is not a real-time synth. It must render its output before playback starts, so of course if the tempo changes during playback it will no longer match.

The main limitation is the inability to change tempo gradually. If you change your gradual tempo changes to stepwise ones and enter the same tempo markers in SynthV Studio then the timings should line up without issue (barring any DAW compatibility problems, which can be easily worked around by rendering a wav file).

I wouldn’t expect this to change any time soon, SynthV’s main competitors don’t even have DAW integration, all use the same “render before playback” approach, and (as far as I can tell) all only support stepwise tempo changes.

(to be clear, I know Vocaloid5/6 has DAW integration, but as far as I’m aware most users who have Vocaloid4 still use the V4 editor which is standalone-only, so I’m considering V4 the more relevant competitor software from a user-experience and composition perspective)

I’m mainly thinking of Melodyne here, which (while it’s not a synth) has more or less the same approach (own timeline, pre-renders), but has no problems with sync. I would have zero objections to waiting for SV to render a “frozen” track before playback (while it may not be instant, SV is still quite fast, and most DAWs can do this for their own built-in tracks anyway), as that would be a massive improvement on what I can do at the moment, which is nothing at all. It could also possibly provide a low-quality mode with instant-ish playback that might make it much easier to work with, and then add a rendering step to produce a high-quality version.

As you say, I could try to make step tempo change markers, however, SV could improve this massively by importing a snapshot of the entire tempo map from the host, or perhaps via a MIDI file (though MIDI file imports don’t currently seem to retain tempo?); I really don’t fancy creating several hundred tempo markers manually, and be faced with the threat of accidentally knocking the whole thing out of sync if I so much as breathe on it… I don’t see that the synthesis method has any bearing at all on tempo management.

I haven’t tried the following tricks yet, I do strict tempo stuff, but…
Are the following any help for a work-around?

I have read somewhere that some DAWs don’t export tempo in their MIDI files but that is a DAW issue, not SynthV’s import at fault.