Page 1 of 2

Please help proof-reading this manual

Posted: Wed Apr 08, 2020 8:38 am
by spacef
Hi there,
Could you please help proof-reading this new device manual (grammar, spelling, clarity).
docx word document in the attached zip.
It would help tremendously (and nobody will need to tell you "RTFM" after that :-) )
Counting on you
Many thanks !
Mehdi

PS; not to disapoint anyone, and to reassure everbody, this new Prodyssey CV requires an activation key for the Prodyssey. In other terms, it will be free for all current and future Prodyssey owners.
-------------------------------
EDIT:
-------
The English manual is done and you can get the final PDF here as well as a few audio demos and preset list screenshots.

Re: Please help proof-reading this manual

Posted: Wed Apr 08, 2020 9:34 am
by Spielraum
[o]beautiful[o]
you will receive a German Handbuch from me, proofread. ...in few days

Re: Please help proof-reading this manual

Posted: Wed Apr 08, 2020 9:46 am
by nebelfuerst
Spielraum wrote: Wed Apr 08, 2020 9:34 am [o]beautiful[o]
you will receive a German Handbuch from me, proofread. ...in few days
.. which I could proofread, if you'd like 8)

Re: Please help proof-reading this manual

Posted: Wed Apr 08, 2020 12:34 pm
by Liquid EDGE
Will check it.

Re: Please help proof-reading this manual

Posted: Wed Apr 08, 2020 3:04 pm
by Bud Weiser
While I´m reading ... (just because I have keys for SCOPE PCI and XITE) ...
Wow,- cool features !

English isn´t my native language,- but I understand (almost ?) everything already.
So, I think I´d be able to work w/ the manual as it is.

But I have a question ...
Multimode LFO 3,- is it freerun or always dependent to note on event w/ the option to change phase ?

:)

Bud

Re: Please help proof-reading this manual

Posted: Wed Apr 08, 2020 3:09 pm
by Bud Weiser
12. delay and outputs

you doubled then line:
"The Delay effect can be sent to the main mix (“Out”) or to the Aux outputs (“Aux”). The terms refer to the project module outputs. The On/Off buttons act as “Mute” and can be used to bypass the delay sound."

below the graphic images on page 12.

:)

Bud

Re: Please help proof-reading this manual

Posted: Wed Apr 08, 2020 3:36 pm
by spacef
Hey thanks guys, good response so far, very good and energizing vibes :-)

For other languages, please wait a couple of days because I might remove or add stuff here and there. Also, with the english revisions from all of you, and your remarks, it will be better. It will be great to have several languages. "familyware" as said Spielraum ? ;-)
Bud Weiser wrote: Wed Apr 08, 2020 3:04 pm Multimode LFO 3,- is it freerun or always dependent to note on event w/ the option to change phase ?
All LFOs (except Vibrato LFO) can be synced to BPM or run in hertz mode (free run). The phase of LFOs needs to be reset when you change the shape of the LFO (as well as on device load or project load).

You can resync the LFOs with "notes-on" or by "manual trigger" (press a button, with mouse or midi CC, which is actually a nice way to create unexpected rythmic pattern in a "more or less" random way or "on the fly"). Retriggering should not be dependant on the hertz or sync modes.
Also, you need to resync the LFO once and it will stay in sync forever (at least until you stop & restart your sequencer). (forever= tested for more than 6 hours, which is generally enough for most songs/projects ;-) ). in sync means "in sync with the tempo of your daw".

I realize this function is not described in the manual. On the small image on page 4, the retrigger functions is placed at the left of #20 (sections "Seq/LFO start", which is just above the "shuffle" knob). I should add this in the manual. you can see it better in the cover page (may be zoom in a bit, it will be easier to zoom in once saved as a pdf).

I haven't checked what happens in free run (hertz) mode when you change the shape, nor wether phase is actually changed "live" (i don't think so, but as it is not my workflow, i must check). I will check this and add it to the manual.

Re: Please help proof-reading this manual

Posted: Wed Apr 08, 2020 9:10 pm
by dawman
My English is terrible according to the schools.
But I never let schooling get in the way of a good education.

Will check it out.

Re: Please help proof-reading this manual

Posted: Wed Apr 08, 2020 10:24 pm
by dawman
First paragraph an s needs to be on Month to make it plural, as in months.
Second paragraph, the word technics needs to be techniques.

I. New Features section, line 12.
leds needs to be LED’s....
Line 14....17 modulators (14 + 4 External CV) ....spelling is fine but 14 + 4 is 18 if my math is true.
Be back tomorrow as I’m passing out.
Line 15-35 perfect.






Looks awesome though Mehdi.
But if perfection in literature is preferred, I will be a dick and point out minute details.

Cheerz

Re: Please help proof-reading this manual

Posted: Thu Apr 09, 2020 4:22 am
by spacef
I have uploaded manual v2 in the first post. It includes your correction/suggestions as well as corrections received from "Mr Arkadin" :-).

I have room to add a "Trig" button on the Sine and Pulse LFO without using additional resources, so I will do that to the synth, so all LFOs can be phase synced or "free running".

Re: Please help proof-reading this manual

Posted: Thu Apr 09, 2020 5:00 am
by Spielraum
:P

Re: Please help proof-reading this manual

Posted: Thu Apr 09, 2020 10:30 am
by Bud Weiser
spacef wrote: Thu Apr 09, 2020 4:22 am I have uploaded manual v2 in the first post. It includes your correction/suggestions as well as corrections received from "Mr Arkadin" :-).
Where´s the link in 1st post ?
It´s gone ...
spacef wrote: Thu Apr 09, 2020 4:22 am I have room to add a "Trig" button on the Sine and Pulse LFO without using additional resources, so I will do that to the synth, so all LFOs can be phase synced or "free running".
excellent,- thank you !

:)

Bud

Re: Please help proof-reading this manual

Posted: Thu Apr 09, 2020 10:34 am
by spacef
oops, you are right, I don't know why it was gone. Probably mismanipulation due to multiple windows opened on the same page.
Reuploaded.

Re: Please help proof-reading this manual

Posted: Thu Apr 09, 2020 12:28 pm
by spacef
I will be waiting for your (participants of the thread) to send the pack to SC (device+presets+ manual(s) .
I can wait monday, or may be it is not important that the German manual comes later?
just let me know !!

Re: Please help proof-reading this manual

Posted: Thu Apr 09, 2020 5:03 pm
by Bud Weiser
spacef wrote: Thu Apr 09, 2020 10:34 am oops, you are right, I don't know why it was gone. Probably mismanipulation due to multiple windows opened on the same page.
Reuploaded.
I´m reading and I´m on page #5 (The Add Page) ...

There´s the "project device" graphics w/ CV-Inputs #36.

I miss the explanation what these inputs are when connection ext. hardware like other synths/ euro-rack modules.
I say because not every AD/DA converter handles analog CVs perfect or at all.
Does p.ex., a Creamware or S|C A16U handle analog CVs on it´s inputs ? I dunno.
So, how to get analog CVs from outside world into SCOPE ?
Do we need special hardware,- p.ex. DC-decoupled ?
AND,- is there possibly a way getting "CV" modulation signals out from ReasonStudios "Reason" devices into SCOPE/Prodyssey CV ?
Maybe by virtual (audio-) cable or such ?

Otherwise,- I like your manual very much,- as far as can say w/o using "Prodyssey CV" while reading.
I´m german, but I don´t need a german manual urgently,- I understand everything pretty well and I´m used to read FUBAR Yamaha manuals from the 80s which were obviously translated using hexaglot machines or such,- already from japanese to english and then to german ...
:lol: :lol:

IMO, your manual is already very detailed and easy to understand.
I´d wish I´d got such manuals for everything in the past.

I really like the sound of Prodyssey,- so I can´t wait checking Prodyssey CV out,- even not every single feature, just because I don´t own a euro-rack system.
I hope I´ll have SCOPE v7 x64 up and running when you´ll release it.

When I read this Prodyssey CV manual and WHEN all the functionality is working flawlessly,- I can imagine and w/ all the extra options,- this is the best ARP Odyssey software clone out there.
I never understood why "clones",- beside the authenticity soundwise,- urgently need the limitations of the original hardware.

I´d wish someone dives into Minimax the same,- maybe Profit-5 too and since it´s already in the works for Vectron (in fact Prophet VS) ...

:)

Bud

Re: Please help proof-reading this manual

Posted: Fri Apr 10, 2020 1:25 am
by spacef
In fact "cv" is just a generic term that I have been using for a couple of years on my devices.
The advantage is that it takes only 2 letters + 1 extra character for a number.
That said, it can take actual Controlled Voltage signals (once converted to audio range).

So "cv" inputs could have been called "Audio Modulation" or "Mod". But "cv" looks better eventhough it is not "CV" per se. It also makes a relation to actual hardware gear and what you can do with "hardware CV" or electric signals.

With the "cv" inputs, you can use any audio/sync modulator such as :
- sync modulators from Modular Patch or Devices
- modulators from a vst instrument/modulator that is available through an ASIO bus
- Controlled Voltage converted to audio through an appropriate "CV to Audio" equipement - or without a converter when an Eurorack oscillator can be slowed down to act as an LFO, which is an audio signal.


The "cv" inputs are just "audio/sync to modulation dest" and are not limited to the "converted CV range" but will take the full DSP range. This means that actual CV signals, as well as modulations from VST modulators might need Gain Adjustments. I give you numbers below:
- DSP Range: let's say the DSP Integer range is -21 to 21
- CV range (converted): - 7.5 to 7.5 (approximately) (I do not have a CV to audio converter so I am not sure converted CV is bipolar)
- VST or Audio Range: native modulators are generally working the same as DSP modulators but on a range of +12dB. So for scope users, it can be told as "VST=DSP+12dB".

It means that you may need gain adjustments to get the right range of the modulation you are using.
- DSP = directly compatible
- Converted CV to audio: generally require a multiplication of approx 2.5 / 2.75 - eventhough x 2 is enough for most modulators. The multiplication is done with a Gain Boost (for example something like +6dB gain boost but more is possible too).
- VST modulator to DSP synths: - 12dB (in the other direction, i.e. Scope to VST , you need +12 dB).

All these signals must of course be available as "audio" or "sync"
You can adjust the gains with whatever is convenient: for ex, with your DAW bus outputs or with a Gain module in Scope.

It is not always necessary to adjust the modulation input gains because the modulator in question does not always use the full range: in your devices, the modulation levels are not always at maximum: you adjust them with attenuators to find the right amount of modulation for your current sound. For example, it is very unlikely that an "LFO to Filter Cutoff" is used at its maximum gain. You generally lower the modulation amount to find the right amount for the sound you are making.

Because of the variety of sources and destinations, I do not include any gain boost levels of modulators inside the devices because for many users, they would never be used and would take unecessay resources. You can only lower/attenuate the levels with the CV levels (which is another generic term for "Modulation Amount"').
A gain booster for modulation inputs actually only concern people with Hardware equipments where signals are "electricty streams" and not digital streams. Other people need either nothing (DSP to DSP) or would use ASIO bus levels to attenuate the signal by 12 dB (or other values).

I will add a few lines in the #36 to tell people that actual CV modulations may need a "CV to Audio" converter.

Re: Please help proof-reading this manual

Posted: Fri Apr 10, 2020 2:09 am
by spacef
I've added this:

36. CV inputs are inputs for modulations from other Scope devices, VST Modulators, hardware synths or Eurorack modules. The term “cv” is a generic term for modulation inputs that actually means “sync modulation input”. To use a hardware CV modulator, you need a “CV to Audio” converter. Also, signals coming from hardware may require – once converted - a gain boost of +6dB or more before the “cv” inputs. This boost can also be achieved inside the Prodyssey CV by adding the signal to itself in the "Adder" modulator. Signals coming from the VST/Native world are received by Scope through the ASIO busses, and may sometimes require a gain attenuation or boost of up to 12dB, that is achieved with the bus or send levels of your DAW.


Updated doc v3 in the first post of this thread.

Re: Please help proof-reading this manual

Posted: Fri Apr 10, 2020 6:58 am
by Bud Weiser
spacef wrote: Fri Apr 10, 2020 2:09 am I've added this:

36. CV inputs are inputs for modulations from other Scope devices, VST Modulators, hardware synths or Eurorack modules. The term “cv” is a generic term for modulation inputs that actually means “sync modulation input”. To use a hardware CV modulator, you need a “CV to Audio” converter. Also, signals coming from hardware may require – once converted - a gain boost of +6dB or more before the “cv” inputs. This boost can also be achieved inside the Prodyssey CV by adding the signal to itself in the "Adder" modulator. Signals coming from the VST/Native world are received by Scope through the ASIO busses, and may sometimes require a gain attenuation or boost of up to 12dB, that is achieved with the bus or send levels of your DAW.


Updated doc v3 in the first post of this thread.
Thx for in-depth explanation above !
Well, the only CV-to-audio converter I can find comes from ReasonStudios as a plugin/RE ...
https://www.reasonstudios.com/shop/rack ... -to-audio/
When I google for "CV to Audio converter", the results are mainly the opposite,- Audio-to-CV.

I hoped there exists a hardware device converting analog CV to audio.
Are there eurorack modules doing that ?

Anyway ...
The addition to #36 in the manual is great.
Downloaded v3 and will read later again.
But at 1st glance, the manual is well done,- at least for me.

:)

Bud

Re: Please help proof-reading this manual

Posted: Fri Apr 10, 2020 7:10 am
by spacef
Expert Sleepers has a bunch of these stuff in particlar the ES 3 and ES 8 , or the ES 9
The ES8 looks like it can convert CV to audio. You can contact Expert Sleepers for more info.
Some eurorack modules might also be able to convert cv to audio (such as multiples or mixers that can take both CV and Audio and mix them together - but you will need to find someone to confirm they can do what you want to do).
There are also preamps and sound cards with dc coupled i/os that might work. But I am not a specialist in this area.

Re: Please help proof-reading this manual

Posted: Fri Apr 10, 2020 7:26 am
by dawman
where is Tony Arkadin?
Miss him, he was always busy.

Many friends are nervous about the internet, they see policemen in their soup.