Oszillos Mega Scope

[elektroluks]

I'm using Ableton Live Lite (Alesis Edition) 8.0.10 - the latest version available for me.

I can't make any use of the multichannel option. It seems like Ableton doesn't recognize this plugin as a multichannel one.
When I'm trying to route the output of a drum track to another track where O-M-S is inserted, there's no way to choose O-M-S input channel in the "Audio to" part of the drum track - there's only "Track In" option and I can't change it.

Is it a bug or am I doing something wrong when routing?

Besides that the O-M-S works fine

[Debutante]

This is a truly fantastic plugin!!!!!!!!!!!!!!!!!!!!!!!!

I initially had problems with it but beta 5 seems ok so far.

AWESOME!!!!!!!

[benjamin_schulz]

Hello to everyone,

a new Beta-Version is ready! The most notable features are a new UI (thanks to olli), Window-resizing and a gain slider. I also added an about-screen where all the testers (YOU!) are mentioned.

I would really like to get feedback on this Version! especialy if Window-Resizing works (on Hosts that support resizing). The other thing i would like to know is if the mouse-wheel works correctly.

So Have fun while checking it out!

http://www.betabugs.de/oszillos_mega_sc ... beta-6.zip

And thanks again and in advance for all the Feedback!

best regards
Benjamin Schulz

[elektroluks]

great! this update is an amazing improvement in terms of gui aesthetics and funcionality.

however, i still can't make it to work as multichannel, as stated above.
Ableton LIve Lite 8.1.3 this time.

i hope it's just a matter of routing and someone will explain it to me.

[benjamin_schulz]

great! this update is an amazing improvement in terms of gui aesthetics and funcionality.

however, i still can't make it to work as multichannel, as stated above.
Ableton LIve Lite 8.1.3 this time.

i hope it's just a matter of routing and someone will explain it to me.

Hello,

Multichannel works by dropping an Instance of the Plugin as an Insert into the channels you want to monitor. Hope this helps.

-- Benjamin

[gts]

Thanks for an update. Again, amazing plugin

[elektroluks]

Multichannel works by dropping an Instance of the Plugin as an Insert into the channels you want to monitor. Hope this helps.

thaaanks a loooot! the solution was so simple, i didn't even think about that
however such approach isn't the optimal for me - when i'd like to drop just one instance of the plugin on the submix channel.
are you planning to implement multiple inputs in your plugin?

it's really gorgeous! works like a charm in Ableton 8.1.3 on 1.6ghz, 1.5gb ram, win xp box.

[benjamin_schulz]

Multichannel works by dropping an Instance of the Plugin as an Insert into the channels you want to monitor. Hope this helps.

thaaanks a loooot! the solution was so simple, i didn't even think about that
however such approach isn't the optimal for me - when i'd like to drop just one instance of the plugin on the submix channel.
are you planning to implement multiple inputs in your plugin?

it's really gorgeous! works like a charm in Ableton 8.1.3 on 1.6ghz, 1.5gb ram, win xp box.

I'll possibly change the way Multi-channeling is handled in the future. The way i am doing it now has obviously some flaws. For now - i want to be able release a stable version that is usable and works STABLE on all DAWs.

I tested the current Version under Fruity-Loops, Reaper, EnergyXT, Live and Traction. Eagerly waiting on the feedback from the Cubase-guys ;o)

When i have the Feeling, that it works solid i will release 1.1.

After that i will do one more feature-Improvement cycle and Testing. That would lead us to 1.2.

I already have an idea (and basic Implementation) for another amazing and very helpful visualization Plugin - but i don't want to spoil the surprise and first things first...

Let the Bug-Reports come ...

regards
-- Benjamin

[bpblog]

this is an amazing plugin. the price is insane.

thank you.

[benjamin_schulz]

Hmmm,

no crashes, no quirks, no strange behavior?

[bpblog]

Hmmm,

no crashes, no quirks, no strange behavior?

tested in mulab 3, dualcore amd athlon (although mulab only uses one core).

no quirks whatsoever! the first version of the plugin, which was released a while ago, didn't even load on my pc, but the current beta worked flawlessly so far. low cpu usage, fast loading, no crashes. and besides that, i find it to be extremely well designed.

don't quite understand why a resizeable gui was so high on the list of priorities though, when making two versions of the plugin would be a far less pita way to solve the problem, imho. one small gui version, one standard gui version and voila! but you made it work anyway, so congratulations! :]

anyway, i have two little frs to drop here. how about adding amplitude metering labels (in dB) to the left edge of the screen? that would be nifty. also, adding a way to nudge the observed signal to the right of the screen would be a great tool to use when analyzing kicks or other hits that are on the first beat.

[elektroluks]

some great news here! especially about the new plugin - after O-M-S we can expect something unique form you i guess.

as a form of 'thank you' i can provide usage-report from Madtracker 2.6.1.
plugin also works perfectly in this host. however it initially displays bigger
amplitude then the same material in Ableton. but this might be connected with internal signal amplification in Madtracker.

speaking about feature development i strongly support bpblog with request for dB labels. in that case the "visualization gain" slider should be changed into
"zoom" of course.

best greetings! keep up the great work!

[benjamin_schulz]

Hmmm,

no crashes, no quirks, no strange behavior?

tested in mulab 3, dualcore amd athlon (although mulab only uses one core).

no quirks whatsoever! the first version of the plugin, which was released a while ago, didn't even load on my pc, but the current beta worked flawlessly so far. low cpu usage, fast loading, no crashes. and besides that, i find it to be extremely well designed.

don't quite understand why a resizeable gui was so high on the list of priorities though, when making two versions of the plugin would be a far less pita way to solve the problem, imho. one small gui version, one standard gui version and voila! but you made it work anyway, so congratulations! :]

anyway, i have two little frs to drop here. how about adding amplitude metering labels (in dB) to the left edge of the screen? that would be nifty. also, adding a way to nudge the observed signal to the right of the screen would be a great tool to use when analyzing kicks or other hits that are on the first beat.

Amplitude labels absolutely make sense, also proper scaling of the amplitude labels and the aplitude-grid would be usefull, especially in connection to the gain-feature.

I don't quite the nudging-thingee, could you please explain it in greater detail?

regards
Benjamin Schulz

PS.: It is really amazing what a myriad of DAWs is out there, before your post i did not know of that one.

[loopdon]

I think i understand what he means. Actually i was meaning to ask the same thing, before. It is difficult to see the attack phase/transient of a kickdrum for example playing on the first step of a pattern. It would be nice if you added a little 'noting' before the start of the first sound in a bar so it is more clearly visible. The way it is or at leats was in the latest beta i tested (5) is that the first sound in a pattern is almost glued to the left border making it very difficult to see what's going on in the first few ms of a sound. So i would put the sound i wanted to see the start of on say step 5 of 16 to clearly see the attack portion. I think this is what is meant.

[carrieres]

awesome !
i will test it with orion from synapse audio