iamspuzzum

Members
  • Content count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About iamspuzzum

  • Rank
    Newbie

Previous Fields

  • Your Current Device(s) Samsung Galaxy S3
  1. I'm trying to use the voice command option for the music player... it works when using the mic on the phone itself, but I'm trying to use the mic on the headset instead. The main reason for using voice commands with the headset, is that you can rewind by saying "previous".. there's no button for that. I'd also like to be able to control the music.. in wintertime... without taking my gloves off. :P I "thought" I had it working, but it seems it was the phone's mic that was picking up my voice... it didn't work once I put the phone in my pocket. The voice commands works with voice-to-text in notepad and messaging with the headset, so it's not the mic. Am I wrong in assuming I can use the headset's mic to control the music player with voice commands? Thanks in advance.
  2. Turns out it was a conflict with Ubuntu and Android. I finally got Kies working in Windows XP.. needed to upgrade from WMP9 to WMP11, and did a "clean boot". After that, the MTP driver loaded properly, and I had full communication with the phone. And I was able to transfer 7gb's worth of music.. wav and mp3's. So it definitely was ubuntu not communicating properly with the device. Still says there's only 4.1gb's in total. :P
  3. Figured it out...... 1 click = pause 2 click = ff hold = Google S-Voice pops up "speak now" no reverse. But there's Headset Droid on Google Play Store. https://play.google.com/store/apps/details?id=tvk.headvol&hl=en
  4. My mistake.. it wasn't the last number dialed. I think it's that S-Voice saying "speak now.. are you still there?". But it did dial last number once when the headset plug was loose and I reinserted it better.
  5. I opened a support ticket.. will see what Samsung says.
  6. Is the pause button on the Samsung GS3 LTE earbuds supposed to dial the last number called? Sometimes it pauses, then resumes play again with another push, and sometimes it dials last number instead of resuming play. Am I just using it wrong or something? I can't find documentation on the button functions.
  7. Just as the title says... GS3 LTE has 16gb storage, with 11gb available. Go to transfer a 3.4gb concert in wav format.. 400mb too big. Why?? I shouldn't need an sd card just for music.. I should be able to utilize more than 3gb of that 11gb.. no?
  8. Well.. no matter what I tried, jerkiness always came back. Think I found the issue.. not bitrate, not the aac audio, and not the upsizing as a 720x480 clip had same results... it was the format of the storage, ie: fat16 (fat) vs fat32. Fat32 and video's choppy, and always at different frames. Fat16 and everything's smooth as silk. Guess the winmo os prefers 16 bit data flow.. cheers
  9. Success :). .. Adobe was spitting out 23.976 as 'mixed framerate', which might have been the issue. Commandline encoding, using x264.exe, and besweet/neroaacenc.exe, then muxed with mp4box.. smoother, but still flutters here and there.. never in same place twice. Must be buffer settings. .. Came across 'xmedia recode'. Edited 'Samsung i8910 HD' to allow 480x320, even though it 'says' it defaults as that - it actually defaults to 640x480. Used 1000kbps, and aac at 44100, 160kbps. .. Best encodes so far B) XMediaRecode2142_setup.exe
  10. Well... looks more like a 'human interface' type error :) .. Just realized 'audio effects/srs' was enabled in touch player... woops :) The jerkyness has reduced to a flutter. Playing around with the settings in after effects, set the composition to 'sdtv ntsc' colour space, figuring that would help with the omnia's decryption/play. Dropped the audio to 128kbps, with frequency having precedence over bitrate. Doesn't sound as tinny as I thought it would, but definitely not as full as the original 48000/192 ac3.
  11. AndyCarrol... you're right about the aac, and actually beat me to the post :). I'd fought with it all night, from nero aac encode, to faac in 'belight', even dropping down to 32000/128kbps. Readme for ipod even suggested 160kbps or less, and a thread for android said same thing. .. I even tried different muxers, from cli's mencode and ffmpeg.. same thing. .. Found 2 freewares: "winff" and "mpeg streamclip"/"yamb". Both have presets for various handhelds, and both still jumpy on omnia. .. It's the damn driver/codec in these things. I'm up north, and we started at wm6.5. My understanding, is verison's had few updates already. Even read 1 update caused video/audio issues that last version didn't have.. typical windows :). .. We also have a "quick media player" from bell, opens automatically when selecting mp4 from 'my storage' folder itself. Plays a bit smoother, but not much. .. By the way.. h264 with cabac, plays completely smooth.. without the aac :).
  12. Found some tips. It's not the bitrate, it's the level of compression. That's why smooth on 3ghz P4, but choppy on 800mhz Omnia. H.264 needs a lot of horsepower. Tips found along the way: baseline, disable all "high" and "main". no Adaptive 8x8 DCT transform. no 8x8 DCT Spatial Transform. no CABAC (CAVLC if possible). no B-Frames (set to zero). no Weighted P-Prediction. "Flat" quantization matrix. no interlaced (but why would you want to). play with VBV Buffer. This gives larger file, but play with 2-pass, with a higher target rate. cheers....
  13. Found some tips. It's not the bitrate, it's the level of compression. That's why smooth on 3ghz P4, but choppy on 800mhz Omnia. H.264 needs a lot of horsepower. Tips found along the way: baseline, disable all "high" and "main". no Adaptive 8x8 DCT transform. no 8x8 DCT Spatial Transform. no CABAC (CAVLC if possible). no B-Frames (set to zero). no Weighted P-Prediction. "Flat" quantization matrix. no interlaced (but why would you want to). play with VBV Buffer. This gives larger file, but play with 2-pass, with a higher target rate. cheers....
  14. Progressing along... seems constant bitrate might be the culprit with my encodes. A single pass vbr of 1mbps, max of 1.2mbps, plays a lot smoother than a cbr of even 600kbps. Not sure why, but transitions from slow to busy scenes are definitely smoother. .. Now to play with 2 pass encodes :)
  15. Bell replaced the omnia yesterday... got my 16gb's back B) Still as jerky in busy scenes though. Source is ntsc 23.976p, "Weeds", episode 1. Clip is actually telecined, so used virtualdub and it's internal IVTC (3:2 pulldown removal). Plays great on pc, but still jerky on omnia. Tried adobe's after effects, letting it decide the pulldown removal... tff, wwssw (5 frames= 2 progressive, followed by 2 interlaced, followed by 1 more progressive). Same thing... plays smooth on pc, jerky in busy scenes on omnia. Tried the 'HTC Encoder'... same thing. Handbrake, set for iPhone... same thing. Maybe that's my issue... trying to make so the vids can play on both my omnia, as well as my buddy's iPhone, and other buddy's iPod touch. They only play h264. If they played xvid, then the xvid's are fine... smooth at 1500kbps at 'unrestricted', 480x320. AndyCarroll... you suggested 700kbps h264 in place of the 1500kbps xvid... trying right now, encoding as I type. As for h263 though... it does have 'some' aspect limitations: 128x96 176x144 352x288 704x576 1408x1152 Although the pc will play h263 at non-native resolutions, the omnia will not. And if encoding with ffdshow's h263, it will warn you if you try a 480x320 h263 encode. Says to use h263+ instead. .. Just read there's even a h263++ as well :) Side note... anybody else have issues posting a reply here, while surfing with the omnia? I tried posting this twice from the phone... came up blank(?). Using opera10. cheers....

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.