Topic: Real Time Charting, Order Book, and Time & Sales - page 19. (Read 85544 times)
It's been a great site except if there's any significant price movement, then very predictably nothing.
It's Standard Imperial Operating Procedure for Mt.Gox to shut off all market data feeds before, during, and after market crashes.
The feed dies reliably around market turmoil. I am attempting to secure a more durable connection to the market data feed.
Stay tuned.
Connection errors?
It's Standard Imperial Operating Procedure for Mt.Gox to shut off all market data feeds before, during, and after market crashes.
Connection errors?
It turned out that when we placed subscription to the chanel on reconnect event, this made second subscription because initial subscription was not actually unsubscribed.
I am not sure even that socket.io has special method to unsubscribe delibirately.
So we solved it just ensuring subscription is made only once on initialization.
I am not sure even that socket.io has special method to unsubscribe delibirately.
So we solved it just ensuring subscription is made only once on initialization.
I just launched an implementation along those lines. I hope it remains more stable for everyone going forward.
We faced the same problem in bitcoin-analytics.com
It turned out that when we placed subscription to the chanel on reconnect event, this made second subscription because initial subscription was not actually unsubscribed.
I am not sure even that socket.io has special method to unsubscribe delibirately.
So we solved it just ensuring subscription is made only once on initialization.
Hope this help.
It turned out that when we placed subscription to the chanel on reconnect event, this made second subscription because initial subscription was not actually unsubscribed.
I am not sure even that socket.io has special method to unsubscribe delibirately.
So we solved it just ensuring subscription is made only once on initialization.
Hope this help.
Hi, just noticed this again.
I already wote you that at some point the trades appear of double volume.
So now it is visible possibly why. You can see on screenshot that each trade is inserted twice
Hope this will help
I already wote you that at some point the trades appear of double volume.
So now it is visible possibly why. You can see on screenshot that each trade is inserted twice
Hope this will help
I believe that double-trade situation arises from the way that I'm reconnecting at the moment. I think you should only see that after the socket.io feed dies once and reconnects. It's actually connecting twice, so you're getting all the messages twice. This means that the order book will be very wrong very fast as well.
I'm working on a fix now.
Would it be better if trades were in local time or if client events were in UTC? Does either make sense? Should this be a user-selected option in the Controls?
Personally, I'd prefer local time for both, but anyway I don't think it needs its own option.
A minor annoyance
(Are you annoyed enough to donate so that it will happen faster? 
)I'm so minorly annoyed that I already spent too much time typing for what that's worth
Hi, just noticed this again.
I already wrote you that at some point the trades appear of double volume.
So now it is visible possibly why. You can see on screenshot that each trade is inserted twice
Hope this will help
I already wrote you that at some point the trades appear of double volume.
So now it is visible possibly why. You can see on screenshot that each trade is inserted twice
Hope this will help
(Are you annoyed enough to donate so that it will happen faster? )
Honestly i hadn't even noticed this. )A minor annoyance: it looks like on the console the time is displayed as local, while on the "Time & Sales" tab is UTC.
I'm displaying the trade time as it comes down from the server, which sends time in UTC. I'm displaying events that happen with the client in local time in the terminal.
Would it be better if trades were in local time or if client events were in UTC? Does either make sense? Should this be a user-selected option in the Controls?
(Are you annoyed enough to donate so that it will happen faster?
)
A minor annoyance: it looks like on the console the time is displayed as local, while on the "Time & Sales" tab is UTC.
Also I just tested with Safari 6.0.7536.25 on OSX 10.7.4 (which is Lion) and it works fine, I do indeed get sounds. Perhaps the other users trade volume is higher than they thought?
Oh man, that stinks, I really like the idea of sounds for trades, why won't it work for me?
When I first read of your success with Safari 6 on Lion I at first thought it must be some quirk of Mountain Lion that it's not working for me. But I got suspicious and tried it on my wife's Mac (also with Mountain Lion/Safari 6) and I got sound there!
Could anyone who knows more about Mac/Safari than I chime in with an idea why it's not working on my machine, but on others with same browser/OS? Yes, my sounds is on, volume is up, and HTML5 audio is working for me on other sites I've tried.
For what it's worth, the sound also doesn't work on Safari for iOS 5 (iPad/iPhone) but I have no idea if HTML5 audio is supported there.
I am having trouble distinguishing the buy and sell sounds. Its obvious when i hear them back to back. But when i just hear one alone, I can never judge fully if it was a low enough tone to be a sell or not. They are too similar imo. Maybe i just have a problem.
I thought about this too. I will probably change it soon.
also, i'm still get disconnected a lot.
I have implemented the Reconnect button up on the controls row. Use it for force disconnect / reconnect if the connection fades out. Also, it will display 'Connect' if there is a connection error. You no longer have to reload the page to refresh the connection.
I am having trouble distinguishing the buy and sell sounds. Its obvious when i hear them back to back. But when i just hear one alone, I can never judge fully if it was a low enough tone to be a sell or not. They are too similar imo. Maybe i just have a problem. also, i'm still get disconnected a lot.
One nice thing about attaching the audio elements is that they will pre-load.
I do not pre-load the sounds until the user chooses to play them, or the setting to play them is loaded from the user cookie. This saves bandwidth to the server, since the browser might require .wav files, which are much larger than their compressed counterparts. So only users who want sounds load them from the server.
Also you I would make sure that you are re-using your objects (just setting the playback position to the beginning) which in theory should be better from a memory, speed POV. (I would actually be surprised if you of all people were not doing this already.)
I am doing this already. I simply didn't include it in my code snippet above
Also I just tested with Safari 6.0.7536.25 on OSX 10.7.4 (which is Lion) and it works fine, I do indeed get sounds. Perhaps the other users trade volume is higher than they thought?
That's good to hear.
I'm not attaching
One nice thing about attaching the audio elements is that they will pre-load.Also you I would make sure that you are re-using your objects (just setting the playback position to the beginning) which in theory should be better from a memory, speed POV. (I would actually be surprised if you of all people were not doing this already.)
Also I just tested with Safari 6.0.7536.25 on OSX 10.7.4 (which is Lion) and it works fine, I do indeed get sounds. Perhaps the other users trade volume is higher than they thought?
just wanted to say thanks for the great site!
awesome. i love the sounds.
Alright! Noticed my Period setting is persistent across full refreshes now. Thanks!
Donation address available on the website or in signature
What method are you using to do the sound, HTML5 audio, Flash/Shockwave, or something else?
Apparently Safari's HTML5 audio support was somewhat broken before but supposedly it's now working in Safari 6.
Apparently Safari's HTML5 audio support was somewhat broken before but supposedly it's now working in Safari 6.
I'm added the audio in JavaScript with the HTML5 Audio API:
Code:
var A = new Audio(filename);
A.play();
I'm not attaching
Actually, it works on Windows 7, Safari 5.1.7. Any Mac-specific debug messages would be very helpful...
Hmm, that's weird. I'm seeing no debug messages anywhere, just not getting any sound.
What method are you using to do the sound, HTML5 audio, Flash/Shockwave, or something else?
Apparently Safari's HTML5 audio support was somewhat broken before but supposedly it's now working in Safari 6.
Jump to: