General discussion

Discussion in 'General Off-Topic' started by Car crusher, Apr 4, 2014.

  1. workclock1©

    workclock1©
    Expand Collapse

    Joined:
    Jan 5, 2016
    Messages:
    2,555
    It's a package with 2 boxes of 12 wooden pencils
     
  2. vmlinuz

    vmlinuz
    Expand Collapse

    Joined:
    Mar 2, 2014
    Messages:
    2,409
    I leave my SSH login port open for one day and this shit happens:

    Code:
    Jan 24 15:34:27 nohostname4u sshd[2283]: Failed password for invalid user support from 46.148.18.163 port 37394 ssh2
    Jan 24 15:38:26 nohostname4u sshd[2423]: Failed password for invalid user support from 46.148.18.163 port 48765 ssh2
    Jan 24 15:42:15 nohostname4u sshd[2500]: Failed password for invalid user support from 46.148.18.163 port 50843 ssh2
    Jan 24 15:46:07 nohostname4u sshd[2547]: Failed password for invalid user support from 46.148.18.163 port 52561 ssh2
    Jan 24 16:04:24 nohostname4u sshd[3184]: Failed password for root from 1.176.214.4 port 48209 ssh2
    Jan 24 16:04:26 nohostname4u sshd[3184]: Failed password for root from 1.176.214.4 port 48209 ssh2
    Jan 24 16:04:28 nohostname4u sshd[3184]: Failed password for root from 1.176.214.4 port 48209 ssh2
    Jan 24 16:04:30 nohostname4u sshd[3184]: Failed password for root from 1.176.214.4 port 48209 ssh2
    Jan 24 16:04:33 nohostname4u sshd[3184]: Failed password for root from 1.176.214.4 port 48209 ssh2
    Jan 24 16:04:35 nohostname4u sshd[3184]: Failed password for root from 1.176.214.4 port 48209 ssh2
    Jan 24 16:11:32 nohostname4u sshd[3693]: Failed password for admin from 185.110.132.49 port 48939 ssh2
    Jan 24 16:15:35 nohostname4u sshd[3999]: Failed password for invalid user support from 185.110.132.49 port 43532 ssh2
    Jan 24 16:15:50 nohostname4u sshd[4005]: Failed password for root from 121.185.46.155 port 47194 ssh2
    Jan 24 16:15:52 nohostname4u sshd[4005]: Failed password for root from 121.185.46.155 port 47194 ssh2
    Jan 24 16:15:55 nohostname4u sshd[4005]: Failed password for root from 121.185.46.155 port 47194 ssh2
    Jan 24 16:15:57 nohostname4u sshd[4005]: Failed password for root from 121.185.46.155 port 47194 ssh2
    Jan 24 16:15:59 nohostname4u sshd[4005]: Failed password for root from 121.185.46.155 port 47194 ssh2
    Jan 24 16:16:01 nohostname4u sshd[4005]: Failed password for root from 121.185.46.155 port 47194 ssh2
    Jan 24 16:19:40 nohostname4u sshd[2036]: Failed password for root from 185.110.132.49 port 36074 ssh2
    Jan 24 16:23:36 nohostname4u sshd[2179]: Failed password for invalid user ubnt from 185.110.132.49 port 55653 ssh2
    Jan 24 16:25:59 nohostname4u sshd[2215]: Failed password for admin from 42.225.75.222 port 40007 ssh2
    Jan 24 16:26:02 nohostname4u sshd[2215]: Failed password for admin from 42.225.75.222 port 40007 ssh2
    Jan 24 16:26:04 nohostname4u sshd[2215]: Failed password for admin from 42.225.75.222 port 40007 ssh2
    Jan 24 16:26:07 nohostname4u sshd[2215]: Failed password for admin from 42.225.75.222 port 40007 ssh2
    Jan 24 16:26:10 nohostname4u sshd[2215]: Failed password for admin from 42.225.75.222 port 40007 ssh2
    Jan 24 16:26:12 nohostname4u sshd[2215]: Failed password for admin from 42.225.75.222 port 40007 ssh2
    Jan 24 16:27:30 nohostname4u sshd[2236]: Failed password for invalid user ubnt from 185.110.132.49 port 46289 ssh2
    Jan 24 16:31:22 nohostname4u sshd[2287]: Failed password for invalid user pi from 185.110.132.49 port 53864 ssh2
    Jan 24 16:33:19 nohostname4u sshd[2307]: Failed password for admin from 109.236.92.184 port 53329 ssh2
    Jan 24 16:35:19 nohostname4u sshd[2331]: Failed password for admin from 185.110.132.49 port 59095 ssh2
    Jan 24 16:39:11 nohostname4u sshd[2362]: Failed password for invalid user user from 185.110.132.49 port 35990 ssh2
    Jan 24 16:43:07 nohostname4u sshd[2418]: Failed password for root from 185.110.132.49 port 41031 ssh2
    Jan 24 16:47:06 nohostname4u sshd[2458]: Failed password for invalid user test from 185.110.132.49 port 46158 ssh2
    Jan 24 17:10:12 nohostname4u sshd[2759]: Failed password for admin from 185.110.132.49 port 53174 ssh2
    Jan 24 17:14:17 nohostname4u sshd[2806]: Failed password for invalid user support from 185.110.132.49 port 52582 ssh2
    Jan 24 17:18:13 nohostname4u sshd[2840]: Failed password for root from 185.110.132.49 port 46069 ssh2
    Jan 24 17:22:06 nohostname4u sshd[2895]: Failed password for invalid user ubnt from 185.110.132.49 port 39232 ssh2
    Jan 24 17:26:05 nohostname4u sshd[2934]: Failed password for invalid user ubnt from 185.110.132.49 port 59927 ssh2
    Jan 24 17:26:12 nohostname4u sshd[2936]: Failed password for admin from 197.52.20.222 port 43951 ssh2
    Jan 24 17:26:20 nohostname4u sshd[2947]: Failed password for admin from 54.169.74.28 port 60262 ssh2
    Jan 24 17:30:04 nohostname4u sshd[2978]: Failed password for invalid user pi from 185.110.132.49 port 45900 ssh2
    Jan 24 17:34:09 nohostname4u sshd[3035]: Failed password for admin from 185.110.132.49 port 52477 ssh2
    Jan 24 17:38:12 nohostname4u sshd[3077]: Failed password for invalid user user from 185.110.132.49 port 58969 ssh2
    Jan 24 17:42:12 nohostname4u sshd[3130]: Failed password for root from 185.110.132.49 port 37112 ssh2
    Jan 24 17:46:13 nohostname4u sshd[3170]: Failed password for invalid user test from 185.110.132.49 port 43472 ssh2
    Jan 24 18:06:40 nohostname4u sshd[3433]: Failed password for admin from 217.23.2.77 port 58253 ssh2
    Jan 24 18:07:33 nohostname4u sshd[3444]: Failed password for invalid user support from 46.148.18.163 port 38264 ssh2
    Jan 24 18:11:27 nohostname4u sshd[3499]: Failed password for invalid user support from 46.148.18.163 port 40207 ssh2
    Jan 24 18:11:57 nohostname4u sshd[3502]: Failed password for root from 180.101.143.2 port 41329 ssh2
    Jan 24 18:12:00 nohostname4u sshd[3502]: Failed password for root from 180.101.143.2 port 41329 ssh2
    Jan 24 18:12:02 nohostname4u sshd[3502]: Failed password for root from 180.101.143.2 port 41329 ssh2
    Jan 24 18:12:04 nohostname4u sshd[3502]: Failed password for root from 180.101.143.2 port 41329 ssh2
    Jan 24 18:12:06 nohostname4u sshd[3502]: Failed password for root from 180.101.143.2 port 41329 ssh2
    Jan 24 18:12:09 nohostname4u sshd[3502]: Failed password for root from 180.101.143.2 port 41329 ssh2
    Jan 24 18:15:16 nohostname4u sshd[3533]: Failed password for invalid user support from 46.148.18.163 port 40560 ssh2
    Jan 24 18:19:04 nohostname4u sshd[3569]: Failed password for invalid user support from 46.148.18.163 port 40597 ssh2
    Jan 24 18:24:03 nohostname4u sshd[3634]: Failed password for root from 106.57.58.24 port 38567 ssh2
    Jan 24 18:24:05 nohostname4u sshd[3634]: Failed password for root from 106.57.58.24 port 38567 ssh2
    Jan 24 18:24:07 nohostname4u sshd[3634]: Failed password for root from 106.57.58.24 port 38567 ssh2
    Jan 24 18:24:10 nohostname4u sshd[3634]: Failed password for root from 106.57.58.24 port 38567 ssh2
    Jan 24 18:24:12 nohostname4u sshd[3634]: Failed password for root from 106.57.58.24 port 38567 ssh2
    Jan 24 18:24:14 nohostname4u sshd[3634]: Failed password for root from 106.57.58.24 port 38567 ssh2
    Jan 24 18:52:03 nohostname4u sshd[3947]: Failed password for root from 182.100.67.52 port 16514 ssh2
    Jan 24 18:52:06 nohostname4u sshd[3947]: Failed password for root from 182.100.67.52 port 16514 ssh2
    Jan 24 18:52:10 nohostname4u sshd[3947]: Failed password for root from 182.100.67.52 port 16514 ssh2
    Jan 24 18:52:12 nohostname4u sshd[3947]: Failed password for root from 182.100.67.52 port 16514 ssh2
    Jan 24 18:52:15 nohostname4u sshd[3947]: Failed password for root from 182.100.67.52 port 16514 ssh2
    Jan 24 18:52:19 nohostname4u sshd[3947]: Failed password for root from 182.100.67.52 port 16514 ssh2
    Jan 24 18:52:24 nohostname4u sshd[3958]: Failed password for root from 182.100.67.52 port 24706 ssh2
    Jan 24 18:52:27 nohostname4u sshd[3958]: Failed password for root from 182.100.67.52 port 24706 ssh2
    Jan 24 18:52:30 nohostname4u sshd[3958]: Failed password for root from 182.100.67.52 port 24706 ssh2
    Jan 24 18:52:33 nohostname4u sshd[3958]: Failed password for root from 182.100.67.52 port 24706 ssh2
    Jan 24 18:52:36 nohostname4u sshd[3958]: Failed password for root from 182.100.67.52 port 24706 ssh2
    Jan 24 18:52:39 nohostname4u sshd[3958]: Failed password for root from 182.100.67.52 port 24706 ssh2
    Jan 24 18:52:54 nohostname4u sshd[3961]: Failed password for root from 182.100.67.52 port 27182 ssh2
    Jan 24 18:52:58 nohostname4u sshd[3961]: Failed password for root from 182.100.67.52 port 27182 ssh2
    Jan 24 18:53:00 nohostname4u sshd[3961]: Failed password for root from 182.100.67.52 port 27182 ssh2
    Jan 24 18:53:04 nohostname4u sshd[3961]: Failed password for root from 182.100.67.52 port 27182 ssh2
    Jan 24 18:53:06 nohostname4u sshd[3961]: Failed password for root from 182.100.67.52 port 27182 ssh2
    Jan 24 18:53:10 nohostname4u sshd[3961]: Failed password for root from 182.100.67.52 port 27182 ssh2
    Jan 24 18:53:16 nohostname4u sshd[3965]: Failed password for root from 182.100.67.52 port 28200 ssh2
    Jan 24 18:53:18 nohostname4u sshd[3965]: Failed password for root from 182.100.67.52 port 28200 ssh2
    Jan 24 18:53:21 nohostname4u sshd[3965]: Failed password for root from 182.100.67.52 port 28200 ssh2
    Jan 24 18:53:24 nohostname4u sshd[3965]: Failed password for root from 182.100.67.52 port 28200 ssh2
    Jan 24 18:53:28 nohostname4u sshd[3965]: Failed password for root from 182.100.67.52 port 28200 ssh2
    Jan 24 18:53:30 nohostname4u sshd[3965]: Failed password for root from 182.100.67.52 port 28200 ssh2
    Jan 24 18:53:35 nohostname4u sshd[3975]: Failed password for root from 182.100.67.52 port 28852 ssh2
    Jan 24 18:53:39 nohostname4u sshd[3975]: Failed password for root from 182.100.67.52 port 28852 ssh2
    Jan 24 18:53:41 nohostname4u sshd[3975]: Failed password for root from 182.100.67.52 port 28852 ssh2
    Jan 24 18:53:44 nohostname4u sshd[3975]: Failed password for root from 182.100.67.52 port 28852 ssh2
    Jan 24 18:53:46 nohostname4u sshd[3975]: Failed password for root from 182.100.67.52 port 28852 ssh2
    Jan 24 18:53:49 nohostname4u sshd[3975]: Failed password for root from 182.100.67.52 port 28852 ssh2
    Jan 24 18:53:55 nohostname4u sshd[3977]: Failed password for root from 182.100.67.52 port 29286 ssh2
    Jan 24 18:53:58 nohostname4u sshd[3977]: Failed password for root from 182.100.67.52 port 29286 ssh2
    Jan 24 18:54:00 nohostname4u sshd[3977]: Failed password for root from 182.100.67.52 port 29286 ssh2
    Jan 24 18:54:04 nohostname4u sshd[3977]: Failed password for root from 182.100.67.52 port 29286 ssh2
    Jan 24 18:54:06 nohostname4u sshd[3977]: Failed password for root from 182.100.67.52 port 29286 ssh2
    Jan 24 18:54:09 nohostname4u sshd[3977]: Failed password for root from 182.100.67.52 port 29286 ssh2
    Jan 24 18:54:25 nohostname4u sshd[3988]: Failed password for root from 182.100.67.52 port 29890 ssh2
    Jan 24 18:54:28 nohostname4u sshd[3988]: Failed password for root from 182.100.67.52 port 29890 ssh2
    Jan 24 18:54:30 nohostname4u sshd[3988]: Failed password for root from 182.100.67.52 port 29890 ssh2
    Jan 24 18:54:33 nohostname4u sshd[3988]: Failed password for root from 182.100.67.52 port 29890 ssh2
    Jan 24 18:54:36 nohostname4u sshd[3988]: Failed password for root from 182.100.67.52 port 29890 ssh2
    Jan 24 18:54:39 nohostname4u sshd[3988]: Failed password for root from 182.100.67.52 port 29890 ssh2
    Jan 24 18:54:44 nohostname4u sshd[3991]: Failed password for root from 182.100.67.52 port 30298 ssh2
    Jan 24 18:54:48 nohostname4u sshd[3991]: Failed password for root from 182.100.67.52 port 30298 ssh2
    Jan 24 18:54:50 nohostname4u sshd[3991]: Failed password for root from 182.100.67.52 port 30298 ssh2
    Jan 24 18:54:53 nohostname4u sshd[3991]: Failed password for root from 182.100.67.52 port 30298 ssh2
    Jan 24 18:54:55 nohostname4u sshd[3991]: Failed password for root from 182.100.67.52 port 30298 ssh2
    Jan 24 18:54:58 nohostname4u sshd[3991]: Failed password for root from 182.100.67.52 port 30298 ssh2
    Jan 24 18:55:13 nohostname4u sshd[3993]: Failed password for root from 182.100.67.52 port 30880 ssh2
    Jan 24 18:55:15 nohostname4u sshd[3993]: Failed password for root from 182.100.67.52 port 30880 ssh2
    Jan 24 18:55:17 nohostname4u sshd[3993]: Failed password for root from 182.100.67.52 port 30880 ssh2
    Jan 24 18:55:20 nohostname4u sshd[3993]: Failed password for root from 182.100.67.52 port 30880 ssh2
    Jan 24 18:55:23 nohostname4u sshd[3993]: Failed password for root from 182.100.67.52 port 30880 ssh2
    Jan 24 18:55:25 nohostname4u sshd[3993]: Failed password for root from 182.100.67.52 port 30880 ssh2
    Jan 24 18:55:30 nohostname4u sshd[4004]: Failed password for root from 182.100.67.52 port 31270 ssh2
    Jan 24 18:55:32 nohostname4u sshd[4004]: Failed password for root from 182.100.67.52 port 31270 ssh2
    Jan 24 18:55:35 nohostname4u sshd[4004]: Failed password for root from 182.100.67.52 port 31270 ssh2
    Jan 24 18:55:37 nohostname4u sshd[4004]: Failed password for root from 182.100.67.52 port 31270 ssh2
    Jan 24 18:55:39 nohostname4u sshd[4004]: Failed password for root from 182.100.67.52 port 31270 ssh2
    Jan 24 18:55:42 nohostname4u sshd[4004]: Failed password for root from 182.100.67.52 port 31270 ssh2
    Jan 24 18:55:57 nohostname4u sshd[4007]: Failed password for root from 182.100.67.52 port 31800 ssh2
    Jan 24 18:56:00 nohostname4u sshd[4007]: Failed password for root from 182.100.67.52 port 31800 ssh2
    Jan 24 18:56:03 nohostname4u sshd[4007]: Failed password for root from 182.100.67.52 port 31800 ssh2
    Jan 24 18:56:05 nohostname4u sshd[4007]: Failed password for root from 182.100.67.52 port 31800 ssh2
    Jan 24 18:56:08 nohostname4u sshd[4007]: Failed password for root from 182.100.67.52 port 31800 ssh2
    Jan 24 18:56:11 nohostname4u sshd[4007]: Failed password for root from 182.100.67.52 port 31800 ssh2
    Jan 24 18:56:26 nohostname4u sshd[4017]: Failed password for root from 182.100.67.52 port 32386 ssh2
    Jan 24 18:56:28 nohostname4u sshd[4017]: Failed password for root from 182.100.67.52 port 32386 ssh2
    Jan 24 18:56:30 nohostname4u sshd[4017]: Failed password for root from 182.100.67.52 port 32386 ssh2
    Jan 24 18:56:34 nohostname4u sshd[4017]: Failed password for root from 182.100.67.52 port 32386 ssh2
    Jan 24 18:56:36 nohostname4u sshd[4017]: Failed password for root from 182.100.67.52 port 32386 ssh2
    Jan 24 18:56:39 nohostname4u sshd[4017]: Failed password for root from 182.100.67.52 port 32386 ssh2
    Jan 24 19:02:28 nohostname4u sshd[4119]: Failed password for invalid user pi from 109.212.226.163 port 47722 ssh2
    Jan 24 19:02:28 nohostname4u sshd[4121]: Failed password for invalid user pi from 109.212.226.163 port 47724 ssh2
    Jan 24 19:04:58 nohostname4u sshd[4143]: Failed password for invalid user support from 46.148.18.163 port 49728 ssh2
    Jan 24 19:08:56 nohostname4u sshd[4187]: Failed password for invalid user support from 46.148.18.163 port 57530 ssh2
    Jan 24 19:12:48 nohostname4u sshd[4243]: Failed password for invalid user support from 46.148.18.163 port 57803 ssh2
    Jan 24 19:16:33 nohostname4u sshd[4281]: Failed password for invalid user support from 46.148.18.163 port 56819 ssh2
    Jan 24 19:41:17 nohostname4u sshd[4596]: Failed password for admin from 217.23.2.77 port 56975 ssh2
    Jan 24 20:04:26 nohostname4u sshd[4899]: Failed password for invalid user support from 46.148.18.163 port 40423 ssh2
    Jan 24 20:08:22 nohostname4u sshd[4938]: Failed password for invalid user support from 46.148.18.163 port 49486 ssh2
    Jan 24 20:10:04 nohostname4u sshd[4965]: Failed password for invalid user pi from 71.184.150.253 port 57686 ssh2
    Jan 24 20:10:04 nohostname4u sshd[4967]: Failed password for invalid user pi from 71.184.150.253 port 57696 ssh2
    Jan 24 20:12:16 nohostname4u sshd[4988]: Failed password for invalid user support from 46.148.18.163 port 49660 ssh2
    Jan 24 20:16:07 nohostname4u sshd[5028]: Failed password for invalid user support from 46.148.18.163 port 49105 ssh2
    Jan 24 20:48:24 nohostname4u sshd[5427]: Failed password for invalid user ubnt from 45.76.167.154 port 60520 ssh2
    Jan 24 20:48:26 nohostname4u sshd[5429]: Failed password for admin from 45.76.167.154 port 38834 ssh2
    Jan 24 20:48:29 nohostname4u sshd[5431]: Failed password for root from 45.76.167.154 port 43486 ssh2
    Jan 24 20:48:32 nohostname4u sshd[5433]: Failed password for invalid user 1234 from 45.76.167.154 port 49524 ssh2
    Jan 24 21:07:19 nohostname4u sshd[5692]: Failed password for admin from 182.127.128.89 port 45827 ssh2
    Jan 24 21:07:21 nohostname4u sshd[5692]: Failed password for admin from 182.127.128.89 port 45827 ssh2
    Jan 24 21:07:24 nohostname4u sshd[5692]: Failed password for admin from 182.127.128.89 port 45827 ssh2
    Jan 24 21:07:26 nohostname4u sshd[5692]: Failed password for admin from 182.127.128.89 port 45827 ssh2
    Jan 24 21:07:29 nohostname4u sshd[5692]: Failed password for admin from 182.127.128.89 port 45827 ssh2
    Jan 24 21:07:31 nohostname4u sshd[5692]: Failed password for admin from 182.127.128.89 port 45827 ssh2
    Jan 24 21:14:27 nohostname4u sshd[5797]: Failed password for admin from 109.236.92.184 port 59579 ssh2
    Jan 24 21:17:21 nohostname4u sshd[5835]: Failed password for root from 36.106.179.169 port 59559 ssh2
    Jan 24 21:17:24 nohostname4u sshd[5835]: Failed password for root from 36.106.179.169 port 59559 ssh2
    Jan 24 21:17:26 nohostname4u sshd[5835]: Failed password for root from 36.106.179.169 port 59559 ssh2
    Jan 24 21:17:29 nohostname4u sshd[5835]: Failed password for root from 36.106.179.169 port 59559 ssh2
    Jan 24 21:17:32 nohostname4u sshd[5835]: Failed password for root from 36.106.179.169 port 59559 ssh2
    Jan 24 21:17:34 nohostname4u sshd[5835]: Failed password for root from 36.106.179.169 port 59559 ssh2
    Jan 24 21:47:30 nohostname4u sshd[6332]: Failed password for admin from 182.91.222.142 port 40154 ssh2
    Jan 24 21:47:32 nohostname4u sshd[6332]: Failed password for admin from 182.91.222.142 port 40154 ssh2
    Jan 24 21:47:34 nohostname4u sshd[6332]: Failed password for admin from 182.91.222.142 port 40154 ssh2
    Jan 24 21:47:36 nohostname4u sshd[6332]: Failed password for admin from 182.91.222.142 port 40154 ssh2
    Jan 24 21:47:38 nohostname4u sshd[6332]: Failed password for admin from 182.91.222.142 port 40154 ssh2
    Jan 24 21:47:40 nohostname4u sshd[6332]: Failed password for admin from 182.91.222.142 port 40154 ssh2
    Jan 24 22:02:14 nohostname4u sshd[6551]: Failed password for root from 117.70.21.143 port 59773 ssh2
    Jan 24 22:02:17 nohostname4u sshd[6551]: Failed password for root from 117.70.21.143 port 59773 ssh2
    Jan 24 22:02:19 nohostname4u sshd[6551]: Failed password for root from 117.70.21.143 port 59773 ssh2
    Jan 24 22:02:21 nohostname4u sshd[6551]: Failed password for root from 117.70.21.143 port 59773 ssh2
    Jan 24 22:02:24 nohostname4u sshd[6551]: Failed password for root from 117.70.21.143 port 59773 ssh2
    Jan 24 22:02:26 nohostname4u sshd[6551]: Failed password for root from 117.70.21.143 port 59773 ssh2
    Jan 24 22:02:58 nohostname4u sshd[6561]: Failed password for root from 210.121.164.121 port 56744 ssh2
    Jan 24 22:03:00 nohostname4u sshd[6561]: Failed password for root from 210.121.164.121 port 56744 ssh2
    
    That's only a short snippet of my SSH log :|

    There is an attempted brute-force attack by 182.100.67.52 on my root account... I will likely be reporting this to the appropriate authorities, supposing they speak English :p
     
  3. Wild Hog

    Wild Hog
    Expand Collapse

    Joined:
    Oct 30, 2016
    Messages:
    1,142
    Unbenannt.png
    Tried this piece of shit (JRiver Media Suite) today and honestly, I can't understand why people use this over WMP. I guess it's great if you're using DACs (whatever those are)?

    Apart from that this programme looks like a strange iTunes version using the Windows Longhorn theme....
     
    #35903 Wild Hog, Jan 25, 2018
    Last edited: Jan 25, 2018
  4. SixSixSevenSeven

    SixSixSevenSeven
    Expand Collapse

    Joined:
    Sep 13, 2013
    Messages:
    6,960
    I thought you were the audio person, and ya don't know that a DAC is
     
  5. Eastham

    Eastham
    Expand Collapse

    Joined:
    Jul 10, 2013
    Messages:
    451
    Speaking of DAC's, my third Chinese speacial just died. Maybe it's time I invested in a proper DAC like a real Audiophile. (arguably, Audiofool...) Also, use Foobar. It's very customizable.
    --- Post updated ---
    When a capacitor decideds it wants to be a a resistor too...

    DSC_0907.jpg
     
  6. Wild Hog

    Wild Hog
    Expand Collapse

    Joined:
    Oct 30, 2016
    Messages:
    1,142
    What makes you think that I'm the audio person? I love listening to music, does that mean that I have to know everything about the technology involved in music playback?

    Ya know if I wanted to be a real "Audiophile" I would buy me some headphone amps for my $1000 Bowers & Wilkins headphones along with a subscription to Tidal and a high-resolution walkman (with fitting sony audio grade SD cards to store my FLAC files of course)

    Or why not go all out and buy some $100 cinch cables for my 1980's Kenwood stereo? I'm sure that'll make it sound better....
    --- Post updated ---
    I'm fine with WMP and VLC honestly
     
    #35906 Wild Hog, Jan 25, 2018
    Last edited: Jan 25, 2018
  7. SixSixSevenSeven

    SixSixSevenSeven
    Expand Collapse

    Joined:
    Sep 13, 2013
    Messages:
    6,960
    Use household mains cable, it's legit not bad as speaker wire and it's cheap.

    DAC, digital to analogue converter. Just the circuit that takes digital data in the PC and creates an analog voltage. That's fed into an amplifier which amplifies voltage and allows more current to be drawn, that then drives your speakers to produce sound.

    A bad amp, I'm sure you understand, can sound pretty shit. But equally, a bad DAC can't construct a good audio waveform in the first place and so won't sound very good
     
  8. vmlinuz

    vmlinuz
    Expand Collapse

    Joined:
    Mar 2, 2014
    Messages:
    2,409
    dear god what have i done

    absolute-creme-de-la-creme.png
     
    #35908 vmlinuz, Jan 25, 2018
    Last edited: Jan 25, 2018
  9. Godzilla!

    Godzilla!
    Expand Collapse

    Joined:
    Mar 17, 2013
    Messages:
    2,244
  10. CharredWing

    CharredWing
    Expand Collapse

    Joined:
    Feb 24, 2017
    Messages:
    552
    Humans probably
     
  11. vmlinuz

    vmlinuz
    Expand Collapse

    Joined:
    Mar 2, 2014
    Messages:
    2,409
    deleted
     
    #35911 vmlinuz, Jan 26, 2018
    Last edited: Jan 27, 2018
  12. ManfredE3

    ManfredE3
    Expand Collapse

    Joined:
    Jan 9, 2016
    Messages:
    2,275
    Sometimes video games just hate you... Sometimes the balancing department decides to not do their job and release obviously skewed statistics to defend their actions. Sometimes it's both.

    Yeah, WoT hasn't been treating me well. That statistic I am referring to is the "only 5% of rounds fired are premium rounds". Even if they include low tier games where new players can't afford gold rounds and auto cannons can fire hundreds of shots in a game, I still don't believe that. I have spent a couple hours in tier 7 and 9 today, almost no silver ammo was fired at me. Almost everything, including arty, was firing gold.

    Shells haven't been cooperating either. 260 penn AP into the side of a Skorp? Tracked with 0 damage done. Shells bouncing off of medium tanks unabgled front plates, sides of weak turrets... Shells dipping below what I am aiming at, shells hitting nothing when my entire reticle is taken up by a single enemy tank 40m away... And so on...

    I haven't been playing well for most of this, but some of these are just ridiculous. At one point I just cliff dived a T30 to try and have some fun in an otherwise terrible game for me... I am not very good at cliff diving so that didn't really work...

    Also, its apperently "every arrogant person get into a Centurion 7/1" day...
     
    #35912 ManfredE3, Jan 26, 2018
    Last edited: Jan 26, 2018
  13. SixSixSevenSeven

    SixSixSevenSeven
    Expand Collapse

    Joined:
    Sep 13, 2013
    Messages:
    6,960
    considering it sounds like you hate the game
    Why do you even bother playing?
    Cant say I had same issues when I played but I just found the game distinctly boring
     
  14. ManfredE3

    ManfredE3
    Expand Collapse

    Joined:
    Jan 9, 2016
    Messages:
    2,275
    I have fun playing it, sometimes it can just get frustrating. When it gets too bad I take an extended break and try again in a couple of months. Usually a month or two, but after a string of bad decisions from WG in early 2017I didn't play at all for several months. Also, (with one exception) I only put the negative stories on here, not the good ones.

    Since playing again I have taken steps to attempt to enjoy the game more. I call it quits when things don't go well for a couple battles in a row unless I really want to play, and I have been posting some stories here to complain; talking about it generally helps ease the frustration a lot. I try to keep everything in spoiler tabs to not spam, and as far as I can tell some people are finding them interesting enough to read (and rate back when that was a thing).
     
    #35914 ManfredE3, Jan 26, 2018
    Last edited: Jan 26, 2018
  15. Ai'Torror

    Ai'Torror
    Expand Collapse
    BeamNG Team

    Joined:
    Aug 29, 2015
    Messages:
    1,550
    Soo... both of my headsets just decided to loose what life was left in them and give up...
    -Creative Sound Blaster Tactic 3D rage wireless:
    1.one of the speaker cables fell of
    2.volume adjustment has stopped working
    (After those issues I've just sotered the cable back to the speaker and it was working like that while being held on by some glue and few wood screws for about 3-4 years.)
    3. Today the USB port or battery died, which made it impossible to charge the headset. so I basically gave up on it.
    -Creative Sound blaster tactic 3d alpha
    It had the same problem with speaker cable falling of and it was basically falling apart, but what has killed it was most likely some of the tiny wires braking

    Here are some photos: (yes, I've melted the plastic just to see if I could fix the USB port, and I had enough of those dumb tiny screws.)



    So would you reccomend any cheap, durable, comfortable and well sounding headset? (from 100-450 PLN [25-100$])
    Preferably with microphone...
     
  16. workclock1©

    workclock1©
    Expand Collapse

    Joined:
    Jan 5, 2016
    Messages:
    2,555
    *slurp pop*

    nice

    Capture.png
     
  17. Nadeox1

    Nadeox1
    Expand Collapse
    Spinning Cube
    BeamNG Team

    Joined:
    Aug 5, 2012
    Messages:
    14,683
  18. Googlefluff

    Googlefluff
    Expand Collapse

    Joined:
    Feb 12, 2015
    Messages:
    252
  19. JBatic

    JBatic
    Expand Collapse

    Joined:
    Jan 22, 2015
    Messages:
    1,048
    I did that with some ramen noodles once, it sucked because I put butter and garlic on them instead of broth and chicken flavored powder
     
  20. Flippi 284

    Flippi 284
    Expand Collapse

    Joined:
    May 2, 2017
    Messages:
    2,855
    • Like Like x 1
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice