Jump to content

David Duffy

Regular Members
  • Posts

    670
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by David Duffy

  1. In other news, the OSC cues can now take up to 4 arguments in string, integer or float format. I've also got the OSC control working. Some examples; /multiplay/cue/go with an arg of "current" is the same as pressing the GO button. /multiplay/cue/go with an arg of the cue number (in the list) starts that cue. /multiplay/cue/stop with an arg of "all" is the same as pressing the Stop All button. /multiplay/cue/stop with an arg of the cue number (in the list) stops that cue. /multiplay/cue/fade with an arg of "all" is the same as pressing the Fade All button. /multiplay/cue/fade with an arg of the cue number (in the list) starts fading that cue.
  2. Another question for MultiPlay users; what types of cues do you use? Are there any that you consider obsolete? For example. I never got around to implementing MSC last time. Is it worth looking into?
  3. I have the OSC cue code (transmit) 95% written now. Just need to do the actual UDP sending. I'm also looking into how to implement the OSC control (receive) code and the settings for it. EDIT: The new OSC cue is now working. The fields are host (IP address), port #, address and an optional string parameter. No doubt I'll need to tweak things, but the basics are there.
  4. I think I have my head around the OSC basics, so have started writing some code for it. The new countdown timer works well and can be set to change colours when it is within xx seconds of the end time.
  5. OSC looks pretty easy to implement and I found a code example during my quick look earlier today. Would simple static values be all that's required to be sent, or would sliding values be needed too?
  6. Thanks again to those who have donated and offered suggestions. It is appreciated. I've just added a new window for a count down timer to supplement the existing clock and stopwatch options. You can set a target time and it will count down to zero. Maybe it could change colour when the target is imminent?
  7. I've not looked into OSC before (but have done UDP tx/rx in another app) but it looks possible in due course. I'll have to read up on how OSC packets are composed and work out how to implement that in the cue properties.
  8. Next question for those that use the Serial Cues. Are the parity and handshaking options needed? I was going to pare it down to port number, baud rate, data bits and stop bits. The other improvement is graceful handling of a USB serial port being inserted / removed.
  9. That's what I was thinking. I was going to remove the close button for it since the cue list is the heart of the action. Work is progressing well and I'm still rewriting lots of code to make it more maintainable in the future. Another addition is double clicking the Pan or Pitch controls text resets them back to centre.
  10. I now have the docking controls working on the new version. This brings up a question. Is there any reason the Cue List would ever need to be hidden?
  11. Hmmm... that one will take some thinking about. In the meantime I've fixed the last production folder vs last media folder issue. I also have video cues working in a basic manner. Hopefully I can get something usable working for MultiPlay version 3.
  12. Thanks for the suggestions. I think I understand most of them. Not sure about the "option for setting a dynamic que point within a track" though.
  13. Work is progressing well and I've ordered the docking component software - thanks to some donations. :) Audio cues are sounding like they should (old audio "engine" is gone) and a lot of the functionality is there. Because of the lost later versions of the source code I'm having to revisit a bunch of bugs from 2012! I'm also taking the time to try and improve the code as I go and make everything more robust. Please feel free to chime in with what didn't work on the old version(s) so I can see if it can be sorted.
  14. I had an online FAQ for MultiPlay quite a few years ago, but it had issues and an update corrupted it. Maybe I should have another look at that.
  15. I'm using Delphi XE. I'd like some feedback from MultiPlay users on how they configure the various windows. For example, do you have the GO, etc buttons on the left, cue list in the middle and notes on the right? I'm trying to get a feel for how the docking should work and what restrictions there should / can be.
  16. Right now the lack of nice form docking controls is the main issue. I have some in mind, but they are 99 Euros.
  17. Thanks guys. I'm working on the form docking at present and may have to go with a paid solution, so the donations are appreciated.
  18. I'm the sole developer. It's being written in a newer version (XE) of Delphi this time.
  19. As per my post in another thread, I've decided to restart development on MultiPlay. Last year I put a download counter on my various software offerings and MultiPlay still gets a huge number of downloads each week. If I only had $1 for every download! The bad news is that in the 6 odd years since the release of version 2.5.5.0 I seem to have lost some source files. I do have slightly older versions of the source, so the first new version may have some bugs reintroduced. Also, some of the original source and components are not compatible with the newer development tools, so I'm having to rewrite a lot of code. The good news is that I have already got the basic audio playback working and it shouldn't suffer from the mp3 poor sound issues that occurred on Windows 7 and later OS. Please feel free to let me know (in this thread) of any outstanding issues that were with version 2.5.5.0 , apart from the mp3 playback of course.
  20. Thanks guys. I really do appreciate the donations. This is going to be a mammoth job (likely hundreds of hours) and I'm slowly working my way through the code. Hearing the first audio from the new playback code last night brought a smile. :)
  21. Just popping my head in here to say I've started work on an updated version of MultiPlay. It will be a lot of work as I'm rewriting large portions of code as I update to a new way of playing the audio. I'm hoping to make the production files compatible, but there are internal changes that may make that tricky. Anyway, that's all for now. Hopefully I'll get a few more donations to pay for the software dev tools.
  22. What the hell???? I'm hoping that's just poor wording. <_< A 2000W amplifier will put out a maximum of 2000W. What I think mkfs9 was trying to say is that the gain of the amplifier is fixed. Current draw of amplifiers is a tricky thing. Maybe best to either measure the actual draw, or use the manufacturer's spec as a guide.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.