Oszillos Mega Scope

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

TizioTizi wrote:I tried in a new project with more tracks, i tried with many instances and with 2 instances, it crash after about 1 or 2 minutes in both situations.

Images:

http://img341.imageshack.us/img341/4519/snap1t.jpg
http://img197.imageshack.us/img197/8607/snap2j.jpg
http://img32.imageshack.us/img32/2221/snap3z.jpg

DMP -> http://www.speedyshare.com/files/22241946/reaper.dmp
*g*, this was one of those < instead of <= bugs. And the messagebox you saw was just a failed assert (you could have hit ignore, but i am VERRY glad you did not!)
Can you confirm that it now works?

I also changed the location of the minidump. It is now written in the users tmp directory for compatibility with Vista and Windows 7.

New Version is out (beta 5):
http://www.betabugs.de/oszillos_mega_sc ... beta-5.zip

I also added a channel chooser (Left, Right, Mid or Side).

Guess now it's time to fix that UI.

regards and thanks again
-- Benjamin
http://betabugs.de/oszillos_mega_scope/
(not affiliated with betabugs.com!)

Post

droogie wrote: .) der "xxx beta schriftzug" ist viel zu groß! :hihi:
Der Schriftzug ist bloß dazu da um daran zu erinnern, dass es eine beta ist. Der fliegt raus, wenns dann mal final ist.

The writing is only there to remind you, that this is a beta. It will be gone in the final version.

regards
-- Benjamin
http://betabugs.de/oszillos_mega_scope/
(not affiliated with betabugs.com!)

Post

Just wanted to say thanks for this tool. Can't believe it is for free. Wonderful plugin :wink:
me

Post

Thanks again - fantastic tool!
no sig

Post

for me as cubase user this 1.1.5 update is a BIG TURNOFF :x

the waveforms are tooooo tiny!
look at the waveform in voxengo polysquasher!

http://www.pic-upload.de/view-5518994/m ... e.jpg.html

useless for me

these lil windows are annoying too, implent them into the gui bejamin!

es gehört gehört mittlerweile zum guten ton solche sachen inkl. preset browser in ner leiste oben in die gui einzubauen.

Post

droogie wrote:for me as cubase user this 1.1.5 update is a BIG TURNOFF :x

the waveforms are tooooo tiny!
look at the waveform in voxengo polysquasher!

http://www.pic-upload.de/view-5518994/m ... e.jpg.html

useless for me

these lil windows are annoying too, implent them into the gui bejamin!

es gehört gehört mittlerweile zum guten ton solche sachen inkl. preset browser in ner leiste oben in die gui einzubauen.
It might be, that the channel that is actually shown is not the left channel like indicated by the L but the mid or side channel. If your Channels are verry wide or narrow you wont have much amplitude.

Try pushing the L-Button a few times to see if the waveforms get larger.

I will also add gain-control.

Just out of interest: what is the average amplitude (in db or percent) of the channels you're feeding the Plugin with? Are your channels verry wide or narrow?

I am not quite sure, how the final UI will look like. It's a balance-act between easy accesibility and non-intrusiveness. Also the ui should support resizing of the main window.

Please report back with what happened when pushing the L-Button (the channel select button that has an L on it in your screenshot).

regards
-- Benjamin

------------------
Es kein sein, dass du in Wirklichkeit den Mid oder Side-Channel siehst. Je nachdem, ob deine Kanäle sehr Stereo oder Mono sind, würde dann die Amplitude nicht sehr groß ausfallen.

Probier mal den L-Button einige male zu drücken.

Ein Gain-Regler wird aber auf alle Fälle noch rein kommen.

Rein Interesse halber: wie groß ist so durchschnittlich die Amplitude der Spuren mit denen du das Plugin fütterst (in db/Prozent). Sind deine Spuren sehr "Stereo-breit" oder sehr Mono?

Ich bin mir noch etwas unschlüssig, wie ich die gesamte UI-Problematik löse. Auf der einen Seite sollen die wichtigen Optionen möglichst leicht erreichbar sein, auf der anderen Seite soll natürlich auch so wenig wie möglich Platz von der UI weggenommen werden. Hinzu kommt, das das User-Interface Größenänderungen des Hauptfensters sinnvoll unterstützen sollte.

Sei doch so gut und teil mir mit, was beim drücken des L-Buttons raus gekommen ist (der Channel-Select Button der in deinem Screenshot ein "L" darstellt).

Grüße
-- Benjamin
http://betabugs.de/oszillos_mega_scope/
(not affiliated with betabugs.com!)

Post

it doesnt matter if L, R, Mid or Side is selectet!
the waveform is by default too tiny! its not readable!

auch wenn du nen gain fader einbaust, muss die wellenform in ihrer default einstellung "mehr" ausschlagen, es korrespondiert nicht korrekt mit dem eingehenden signal!
ganz eindeutig!

yeah for sure lil bit tricky to implent those windows into to a resizeable gui!

i also think there is no need for those -magnifier & +magnifier buttons!
clicking on the waveform and time buttons brings the desired effect
Rein Interesse halber: wie groß ist so durchschnittlich die Amplitude der Spuren mit denen du das Plugin fütterst (in db/Prozent). Sind deine Spuren sehr "Stereo-breit" oder sehr Mono?
gain staging is very important in a DAW benjamin!
i am never hotter than -6dbfs nomatter of channel, group or bus!
in a mixscenario my masterbus is -6 dbfs -3dbfs

like in the screenshot
http://www.pic-upload.de/view-5518994/m ... e.jpg.html
(the voxengo shows this good)


no, my tracks are not super wide!
no matter how wide, always positive correlation!
superwide often sounds undefined!

mono when mono(vocals, bass, git, drums)

stereo if there is a "real" stereo information (keys, synths, etc)

Post

benjamin_schulz wrote: *g*, this was one of those < instead of <= bugs. And the messagebox you saw was just a failed assert (you could have hit ignore, but i am VERRY glad you did not!)
Sometimes I don't see the obvious things :) , my mind is in the clouds :), my mistake, i play with c++ but i didn't realized it was an assert.
Can you confirm that it now works?
I tried the new beta5, seems more stable, i hadn't crashes to report.
I will also add gain-control.
Very helpful.
Also the ui should support resizing of the main window.
Very important feature.
The window is still inactive when moved to the secondary monitor.

Post

TizioTizi wrote: The window is still inactive when moved to the secondary monitor.
i guess with that you mean the whole window? Or do you mean just the option-windows?

Unfortunately i was unable to reproduce this behavior on my test-systems. So it might be hard to tackle, considering it is a little bit like fishing in muddy waters.

Any hints what might cause this? What is your operating system/Graphics Adapter. Do you have the moast recent drivers installed?

regards
-- Benjamin
http://betabugs.de/oszillos_mega_scope/
(not affiliated with betabugs.com!)

Post

benjamin_schulz wrote:i guess with that you mean the whole window? Or do you mean just the option-windows?
The whole window if the whole window is moved to the secondary screen, if i move the window half on one monitor and the other half on the secondary monitor, the half in the secondary monitor became inactive.
Unfortunately i was unable to reproduce this behavior on my test-systems. So it might be hard to tackle, considering it is a little bit like fishing in muddy waters.

Any hints what might cause this? What is your operating system/Graphics Adapter. Do you have the moast recent drivers installed?
I don't know why, i have more than 1000 plugins installed, never had a plugin that become inactive on the secondary monitor.
My OS is XP SP3 (italian), my video card is Geforce 9800GTX+, my drivers are version 196.21, driver's release date is 19 January 2010, not old, i have not tried with the latest drivers (197.41) but i think it's not a driver problem.

Video showing the problem -> http://www.speedyshare.com/files/222779 ... ec_mon.wmv

I use dualview, the secondary monitor is on the right side, the primary on the left, reaper's main window is maximized on the primary monitor so you can consider reaper's main window as the dividing line between monitors.

Post

TizioTizi wrote:
benjamin_schulz wrote:i guess with that you mean the whole window? Or do you mean just the option-windows?
The whole window if the whole window is moved to the secondary screen, if i move the window half on one monitor and the other half on the secondary monitor, the half in the secondary monitor became inactive.
Unfortunately i was unable to reproduce this behavior on my test-systems. So it might be hard to tackle, considering it is a little bit like fishing in muddy waters.

Any hints what might cause this? What is your operating system/Graphics Adapter. Do you have the moast recent drivers installed?
I don't know why, i have more than 1000 plugins installed, never had a plugin that become inactive on the secondary monitor.
My OS is XP SP3 (italian), my video card is Geforce 9800GTX+, my drivers are version 196.21, driver's release date is 19 January 2010, not old, i have not tried with the latest drivers (197.41) but i think it's not a driver problem.

Video showing the problem -> http://www.speedyshare.com/files/222779 ... ec_mon.wmv

I use dualview, the secondary monitor is on the right side, the primary on the left, reaper's main window is maximized on the primary monitor so you can consider reaper's main window as the dividing line between monitors.

I guess i found out, what might be the cause:

"That OpenGL renders on one monitor and not on the other might be as simple as a control panel setting for the multimonitor OpenGL support."

Hence my ui and the rendering of the waveforms is using OpenGL, that might be it.

Can you try to toggle this option to see if it works?

If yes, this might be a point for the FAQ ;)

regards
-- Benjamin

PS.: further reading: http://www.gamedev.net/community/forums ... 1&#2809482
http://betabugs.de/oszillos_mega_scope/
(not affiliated with betabugs.com!)

Post

You're right, problem solved :) setting the performance mode to "multi-screen".

http://img443.imageshack.us/img443/9489/oszscreen.jpg

Post

any news benjamin?

Post

droogie wrote:any news benjamin?
News yes, new version no.

I am currently revamping the UI. Despite your slightly demanding tone of voice you where right ;o) A bar at the top seems to be the best choice to organize the controlls.

I have still no idea, what might cause the problem with the amplitude. have you really tried to push the channel selection button?

regards
-- Benjamin
http://betabugs.de/oszillos_mega_scope/
(not affiliated with betabugs.com!)

Post

sorry i dont want to be unfriendly, im a very direct person!
sometimes tooo direct
:lol:

believe me, a A bar at the top is the way to go!
this will make the plugin much more pro and less toy

in 1.1.3 beta there is no problem with the amplitude!
even though a gain fader is missin
im workin with 1.1.3 further

Post Reply

Return to “Effects”