OSC Receiver and Sender

[sunmachine]

I'd have to check on the exact details of licensing and how it would work for using an open source dll in a commercial project, but here's an idea of the worst case: https://juce.com/get-juce (i.e. it might need a splash screen)

I found the following regarding the splash screen:

The splash screen only affects an exciting new free tier - If you want to release a closed source JUCE-based product, and your revenue/funding is less that $50k, you can do so for free using the Personal license, but you will need to display a splash screen.

Source: https://forum.juce.com/t/splash-screen- ... e/21908/43

Directly in the information section next to the option for turning off the splash screen, it says that the splash screen can be disabled if the app is released under GPL v3

Source: https://forum.juce.com/t/how-to-turn-of ... ects/22329

Based on that, my understanding is as follows. Please correct me if I'm wrong!

1. As per the quotes above, the splash screen is only needed for closed software and when the developer's revenue is less than $50k. If the software is open source under GPL 3, the splash screen is not needed.

2. So, since the ScopeOSC package is released under GPL 3, there's no need for the splash screen.

3. Every SCOPE device that includes the OSC package has also to be released under GPL (and thus has to be open source).

There's also something noteworthy in the Juce 5 License Agreement by the way (highlighting done by me):

We may collect and process information about you and your use of our Program, some of which may amount to personal data. ROLI may also collect IP addresses associated with your end-users’ use of your Application solely for ROLI’s internal operations in providing you the JUCE Program. Personal data will be collected and processed in accordance with our Privacy Policy. Users of free versions of JUCE, such as JUCE Personal or JUCE Education, may not opt out of the tracking of IP addresses associated with the use of your Application by end-users. You agree to inform the end-users of your Applications about our collection of their IP addresses, if applicable, and have your end-users agree to such collection.

Source: https://juce.com/juce-5-license

[w_ellis]

I think it doesn't apply in quite the same way to DLLs, based on my reading of various threads on this topic. Essentially, as long as the closed source project does not Distribute the DLLs, then it does not need to become open source to make use of them. People will need to download and install the ScopeOSC modules separately. I've already created a release for these here.

Re. the data collection, I just need to disable that in the build of the DLLs, as confirmed by ROLi here. See this comment:

"Another option to opt out, if you’re so inclined, is to use JUCE under the GPL license. As long as you release the code alongside the application, you can do what you want with it."

If all else fails, they're not very complicated to reimplement without the JUCE dependencies, but it's certainly nicer to use if I can.

[sunmachine]

Ok, great! Thanks for the clarification! All this licensing stuff is quite complicated. At least for me...
So did you intentionally include the older version 2 of the GPL here?
https://github.com/bcmodular/scopeosc/b ... icense.txt

[w_ellis]

Yeah, still have a little bit of tidying up to do with licenses through the source code, but was planning to go with v2 for now, as that's what we're using in ScopeSync and what Juce demands. We could use v3 alternatively, but doesn't seem like it'll make too much difference. I'm still re-reading the material though, as it's really complicated!

[faxinadu]

gonna try to release the server device tomorrow

meanwhile if anyone feels like it:

https://play.google.com/store/apps/deta ... oscaeolian

[sunmachine]

Looks like the OSC dlls need the msvcp120.dll which was not on my Windows XP system.
The installer installed the 2010 C++ redistributable, but msvcp120.dll comes with 2013.
So installing the following vcredist_x86.exe fixed it: https://www.microsoft.com/en-US/downloa ... x?id=40784

[w_ellis]

Ah, yes, that's why I always used to build the ScopeSync DLLs on VC++2010. I think there might be a problem for people on really old versions of Windows. I'll check with Simon, as I think he had the problem at one stage. I'll just rebundle with the 2013 version for now to fix it for most people.

[sunmachine]

My Windows PCs are offline and I'm only using them for music stuff, so I don't have installed many applications and usually don't do Windows updates.
I'll try to install it on my Windows 7 box later today.

[w_ellis]

I've updated the setup.exe to include the 2013 Redistributable instead now. I'll wait to hear if this causes anyone any issues!

The latest version can be downloaded here

[sunmachine]

Installation on my Windows 7, 64-bit system worked fine!

[w_ellis]

New versions of the OSC Sender and Receiver available for testing here: https://github.com/bcmodular/scopeosc/t ... ipt/Output

Sender:
- Added Snapshot (Snap) - change value of this inpad to force an OSC message to be sent for all values
- Added Sending Messages (Send) - 0 = don't send, > 0 = send (doesn't catch up, so you can use snapshot after re-enabling if needed)

Receiver:
- Added Listening to Messages (List) - 0 = don't listen, > 0 = listen

When using in SDK, be careful about loading new version in old project, as the new pads mean that there could be weirdness. Recommend deleting old modules first and then loading new ones. Then save project, close SDK and re-open, just to be on the safe side.

I'm not planning other changes to the pads now, so hopefully there won't be other breaking changes, but if I do, I might version the DLLs instead. Let me know what you think.

[faxinadu]

confirmed to work, also it does not break connections on devices using older versions, so all good

[w_ellis]

Good to know!

The only further change I have planned before looking into integrating these into ScopeSync is to load a config for listening port from a file. If there are any other needs that people have (or bugs!), please feel free to raise them here: https://github.com/bcmodular/scopeosc/issues

[w_ellis]

Now reads listener port from C:\Users\xxx\AppData\Roaming\ScopeOSCReceiver\ScopeOSC.settings (or equivalent for different versions of Windows). File is created on first load of OSCReceiver module and will only be re-read at startup, so changing setting will require Scope to be restarted. I'm assuming that this won't be an issue for people as they won't need to change it very often.

https://github.com/bcmodular/scopeosc/t ... ipt/Output

N.B. Defaults to 8000 still.

[JoPo]

Hi !

After those 7 thread page and code discussion, I'd really like to know how OSC is working on Scope !
I downloaded the setup file, installed it but I don't know what to do next !

I must say that I don't know what to do with all the 7 pages of this thread : I'm not a OSC developer. I just found 2 receiver & sender DLL files but I don't know how to transform them on usable scope devices with some GUI I would deal with ! I don't find either any useful info for a guy like me on the github OSC pages...

Thanks for help !

[w_ellis]

Hi JoPo,

This definitely isn't the thread for you if you're not using the SDK! faxinadu has integrated these modules into some devices that he announced elsewhere in the forum and I'm beavering away in the background to hook them into the updated version of ScopeSync that's been a couple of years in the brewing. In the time-honoured tradition here, it'll be done soon

Thanks,
Will

[JoPo]

Ah ! Ok. Thanks a lot, Will !

[faxinadu]

to be honest i was sure people would be going crazy about it and all over this. but somehow it seems its only interesting for a few of us. :/

[JoPo]

to be honest i was sure people would be going crazy about it and all over this. but somehow it seems its only interesting for a few of us. :/

Wait a bit ! I think that if any of you release some OSC Scope devices, other people would be interested. For instance, the amazing Falcon and many new very good vst's have OSC features. I could modulate things in Falcon from Scope. A device that convert audio signals into OSC signals and in the other way, would be awesome !

How are OSC signals time accurate ? Are they as bad as midi ? What is the resolution in frequency and in bits ? I have no idea : I never used OSC. I affraid that if OSC signals are carried by wifi or ethernet, the timing could not be as good as needed for some precise rythmic applications but in fact, I don't know.

[faxinadu]

See announcments forum